Google Calendar provides screen-reader navigation guidance for its web application. Set up the supported environment and review focus behavior before using shortcuts to create or change events. Keyboard-only navigation and a verified screen-reader experience are related but different checks.
Use the recommended environment
Google recommends Chrome with NVDA or JAWS on Windows, ChromeVox on ChromeOS, or VoiceOver on macOS. Its guidance treats Calendar as a web application rather than an ordinary reading page. Consult the relevant screen reader’s mode controls before assuming every navigation key reaches Calendar.
Orient to the main areas
The documented interface includes the banner, events area, main drawer, and right sidebar. Use Skip to main content to enter the calendar. Google recommends Schedule view for screen-reader use; its event navigation uses arrow keys within the documented focus context.
The guidance describes switching NVDA to focus mode, disabling JAWS virtual cursor, or adjusting the relevant ChromeVox and VoiceOver modes. Apply the instructions for the actual assistive technology, not every platform’s mode change at once.
Verify meaningful tasks
Navigate to a known event and confirm that its title, date, and calendar can be understood. Open the Keyboard shortcuts reference through its button when needed. Review announced labels rather than relying on color or pointer position. For creation or edits, inspect the intended fields and final save confirmation before assuming the record changed. Testing basic keyboard navigation alone does not establish a working screen-reader experience. Verify the actual assistive technology and browser together. The completed user setup should support the actual reader and browser combination, with meaningful event information and predictable focus, while leaving untested devices and screen readers explicitly outside the verified scope.
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.