Google Meet exposes meeting controls as labeled interface elements that a screen reader can navigate. Use those labels and states to understand the current meeting rather than memorizing a visual button position. Google recommends Chrome with NVDA or JAWS on Windows, ChromeVox on ChromeOS, and VoiceOver on macOS for its documented computer workflow.
Explore the controls before a real discussion
In a practice meeting, use your screen reader’s normal web navigation commands to move between buttons. Locate the microphone, camera, People, chat, More options, and Leave call controls. Listen to the action named by each button before activating it. A button offering to turn the microphone on indicates a different state from one offering to turn it off.
Recognize sidebars and dialogs
Opening People or chat moves you into a sidebar with additional content. Use screen-reader navigation to inspect participants or messages, and use the Close button or Escape when appropriate. Google notes that only one sidebar is open at a time. Settings and the shortcuts list are dialogs, and a focused dialog prevents opening a sidebar until you close it.
Verify an action through its result
After changing audio or video, return to the relevant control and check its new label. In People, use the search field when finding someone is faster than reading the entire list. In chat, keyboard focus moves to the message field, while previous-item navigation can read earlier messages and senders. Some screen-reader and platform combinations require the chat sidebar to remain open for new-message notifications. Test that behavior with a colleague before relying on chat as an accessibility channel. Keep assistive technology and the browser current through your approved update process, and retain an agreed way to request help if navigation becomes unclear.
References
Reviewed against the linked official product guidance on November 4, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.