While accessing SharePoint Online via Office 365 waffle from Teams Web client, it redirects to root SharePoint site (Company SharePoint site) instead of user’s (personal) SharePoint site. That's very odd behaviour and not consistent with other Office 365 apps.
Teams web client must be consistent with all other apps, where accessing SharePoint (via Office 365 waffle) must redirect user to their (personal) SharePoint site.
The current mapping of SharePoint URL on Teams web client is more painful, when you don't use root SharePoint site (Company SharePoint site) and also have removed user's access to root SharePoint site. In this it shows Access Denied to users while accessing SharePoint service via Teams Web client (Office 365 waffle).

Very important for visually impaired individuals. Lync has an option that allows you to specify the global font settings and then click a box that "applies settings to incoming messages."

This means that someone like myself, who is visually impaired, can then set the global font to say 16. Then all messages I type will be at size 16 and more importantly, all the messages I get back from people are going to be size 16 as well.

This option also allows people who Don't want to see messages in size 16 -don't have to. They can specify their own individual font preferences.

Currently, our company uses Teams and the inability to set global font sizes and control what size incoming messages are displayed at is causing difficulty. It can be set for Each individual message Every time, but that is neither convenient nor really usable as it does nothing for the incoming font size.

I would think Microsoft would want to make their products as user friendly as possible- especially for those who are visually impaired.

Up/down keystrokes from the main comment box should.... do something.

A forward slash should pull you into the command/search box from the second it's typed as the first char in the comment box.

I shouldn't have to memorize some archane 80s style list of keyboard shortcuts to navigate your app: Be easier than Slack.

To that end, I'll share feedback I also shared with them, encouraging them to add a simple "/reply" command to reply to the last message in a new thread.

How can I start a thread with a / command?

I find myself ignoring or forgetting to use threads because they pull my hands away from my keyboard. Why not support a /reply command that just replies as a thread to the last comment?

Bonus points: Add a numeric argument 1, 2, 3 to reply to the 1st item up, 2nd item up, etc. pausing momentarily to let people use the up and down arrow keys to select the post they want to reply to after they type /reply and before they add the text of a response.

This could obviously get way too complicated (think IRC clients like irssi, switching between internal windows - nightmare) but you could do this in simple enough ways that they'd at least start conversations and drive people into newly existing threads.