First-time keyboard guide
Use this short routine before following the Google Docs Screen Reader Manual procedures. It explains exactly how the keyboard directions in this manual work.
Press a single key
- Find the named key without pressing it if possible.
- Press and release the key one time. Do not hold it unless the step specifically says to hold it.
- Stop and listen to the full screen-reader announcement before pressing another key.
Press a keyboard combination
- When a command contains a plus sign, such as Ctrl+S, hold down the first key.
- While continuing to hold the first key, press and release the final key once.
- Release the first key. The plus sign is not a key and should not be pressed.
- Listen for the expected result described in the procedure. If nothing changes, verify that the correct application or webpage has focus and try the command once more.
Press a sequence of keys
- When keys are separated by commas or the word “then,” press and release them in order instead of holding them together.
- After each key, listen for a menu, tab, control, or new screen before continuing.
- If the announcement does not match the step, press Escape once to close the current menu or dialog and restart that procedure.
Know which navigation key to try
- Tab and Shift+Tab: move forward and backward among buttons, links, fields, and other controls.
- Arrow keys: move inside menus, lists, groups of choices, text, and many screen-reader reading views.
- Enter: opens the selected item or activates the focused command.
- Space: activates many buttons and checks or clears checkboxes. In a text field, Space types a space.
- Escape: cancels or closes the current menu, list, or dialog without intentionally accepting a change.
Verify before moving on
- Listen for the window, page, or application name so you know where focus is.
- Perform only one numbered step.
- Compare what the screen reader announces with the “What should happen” information in the procedure.
- If the result is wrong, stop. Use the procedure’s recovery directions, Escape to cancel, or Ctrl+Z to undo when that command is supported.
- Continue only after you can identify the result. Save completed work with Ctrl+S whenever the application supports saving.
First complete independent workflow
This rehearsal joins existing procedures into one uninterrupted session without repeating their directions. Follow the linked procedure when a step names it, then return here for the next verification.
Safety check: Confirm the active account, workspace, audience, and privacy level before entering, uploading, sharing, or sending information.
- Open Google Docs Screen Reader Manual and wait until its name, starting screen, or connected-device status is announced.
- Choose a fictional, public, disposable, or instructor-provided practice item. Do not use private client, student, medical, financial, or account-recovery information.
- Open 2.1 Create a New Google Doc. Read its “What you will learn,” “Before you begin,” keyboard-command, and expected-result information before pressing anything.
- Complete that procedure one numbered action at a time. After each key, stop and identify what changed before continuing.
- State the result aloud or record it in a practice note. If it differs from “What should happen,” use that procedure’s recovery directions before advancing.
- Continue directly to 3.1 Enable Screen Reader Support without closing the application or device session. First confirm that focus, account, file, book, conversation, or project context is still correct.
- Complete the second procedure and verify the resulting name, state, location, permission, value, or content. Do not rely only on a success sound.
- Save or synchronize when the product supports it. Wait for the completed state before disconnecting a device, closing a browser, or switching accounts.
- Continue to 4.1 Move Between Major Areas. Use the exact command listed there; if the command varies by model or version, use Keyboard Help, the product’s shortcut list, or the linked official reference instead of guessing.
- Introduce one harmless recoverable error, such as opening the wrong menu or moving focus away. Press Escape once, identify the active window or device area, and return to the correct step.
- Review the finished practice item from its beginning. Confirm its title or filename, structure, content, destination, sharing state, and saved or synchronized status as applicable.
- Close and reopen the item or return to it from the product’s main screen. The workflow is complete only when you can locate it and verify the same result independently.
Success standard: Complete all three linked tasks, explain the commands used, recover from the practice error, and locate the finished result without another person directing the next key.
Purpose: This manual teaches Google Docs from the beginning to a person using a screen reader. It explains exactly what to press, what should receive focus, what the screen reader should announce, and how to recover when the result is different.
Reference setup: Google Docs works best as a web application in a current Chrome browser. Google recommends current screen readers and current Chrome for best results.
Screen reader modes: JAWS users should generally edit with the Virtual PC Cursor off. NVDA users should generally edit in Focus Mode. VoiceOver users should turn Quick Nav off. Narrator users may need Scan Mode off while editing.
How to Use This Manual
Start with Parts 1-12 even if you already know a screen reader. Those sections teach Google Docs itself.
Press Ctrl+Alt+Z on Windows to enable or verify screen reader support. On Mac, press Command+Option+Z.
Google Docs behaves like a web application rather than a normal webpage while editing.
Use Alt+/ to search menus and commands when you know what you want but not where it is.
Use Ctrl+/ to open Google Docs keyboard shortcuts.
Use Ctrl+Alt+H on Windows or Command+Option+H on Mac to enable braille support.
Use headings, lists, comments, and tables structurally rather than only visually.
Save is automatic in Google Docs, but you still need to verify the correct Google account and document name.
Before sharing, verify both the recipient and the permission level.
Part 1 - What Google Docs Is
Google Docs is a browser-based word processor. Documents are stored in Google Drive and can be edited, commented on, suggested, shared, and downloaded in other formats.
Document body: the editable text area.
Menu bar: File, Edit, View, Insert, Format, Tools, Extensions, Help, and accessibility-related commands.
Toolbar: common formatting and document controls.
Comments: discussion attached to selected text or locations.
Suggesting mode: proposed edits that can be accepted or rejected.
Share dialog: controls who can view, comment, or edit.
Version history: earlier saved states of the document.
Part 2 - Open a Blank Document
2.1 Create a New Google Doc
What you will learn: Open a blank document quickly.
Before you begin: Sign in to the intended Google account first.
Exactly how to do it
Open Chrome.
Press Ctrl+L.
Type docs.new.
Press Enter.
Wait for the document to load.
Listen for a message such as Screen reader support enabled or the document editing area.
Type: Google Docs Practice Document.
What should happen: A new untitled document opens and text appears in the editing area.
If that does not happen: If another account opens the document, switch accounts before continuing. If focus stays in browser controls, press F6/Tab until the editor is active.
Practice: Create a new document and type one sentence.
Part 3 - Turn On Screen Reader Support
3.1 Enable Screen Reader Support
What you will learn: Make Docs expose its accessibility commands and announcements.
Before you begin: A Google Doc is open.
Exactly how to do it
Press Ctrl+Alt+Z on Windows or Command+Option+Z on Mac.
Listen for confirmation that screen reader support is enabled.
If you prefer the menu, open Tools with Alt+Shift+T on Windows or Control+Option+T on Mac.
Choose Accessibility settings.
Check Turn on screen reader support.
Close the dialog.
What should happen: Google Docs announces screen-reader-aware editing information and accessibility commands become available.
If that does not happen: If Ctrl+Alt+Z performs another system action, use the Tools > Accessibility settings method.
Practice: Turn support off and back on once so you recognize the announcement.
Part 4 - Learn the Google Docs Interface
4.1 Move Between Major Areas
What you will learn: Identify menus, toolbar, and document body.
Before you begin: A document is open with screen reader support enabled.
Exactly how to do it
Press Alt+/.
Listen for the Search menus field.
Press Escape.
Use Tab/Shift+Tab to move among top-level buttons and controls.
Use Alt+Shift+F on Windows when you need to focus the menu bar, then use Left/Right Arrow through menus.
Press Escape to return toward the document.
Move back to the editing area and type one character, then undo with Ctrl+Z.
What should happen: You can distinguish the Docs chrome from the document editing area.
If that does not happen: If typing activates a menu command, focus is not in the document body. Press Escape and return to the editor.
Practice: Move to menu bar, toolbar, and document body without a mouse.
Menu shortcut tip: Google Docs exposes many commands through Alt+/ Search menus. This is often easier than memorizing a long menu path.
Part 5 - Enter and Edit Text
| Task | Command |
|---|---|
| Move character | Left/Right Arrow |
| Move word | Ctrl+Left/Right Arrow |
| Move line | Up/Down Arrow |
| Line start/end | Home/End |
| Document start/end | Ctrl+Home/Ctrl+End |
| Select text | Shift with navigation keys |
| Undo/Redo | Ctrl+Z / Ctrl+Y |
5.1 Type and Correct Text
What you will learn: Edit text with standard Windows commands.
Before you begin: Place the cursor in the document body.
Exactly how to do it
Type a short paragraph.
Press Ctrl+Left Arrow to move backward by word.
Press Left/Right Arrow to move by character.
Press Backspace or Delete to remove incorrect text.
Type the correction.
Use Ctrl+Home and Ctrl+End to confirm beginning/end navigation.
What should happen: Text is corrected at the cursor location.
If that does not happen: If arrows move browser focus instead of text, return to the document editing area and make sure the screen reader is in editing/focus mode.
Practice: Create three errors and correct them.
Part 6 - Move Through a Document
6.1 Announce Cursor Location
What you will learn: Ask Docs where the cursor is.
Before you begin: Screen reader support is enabled.
Exactly how to do it
Hold Ctrl+Alt.
Press A, then L.
Release the keys.
Listen for Docs to announce the cursor location.
What should happen: Docs announces location information appropriate to the context.
If that does not happen: If the sequence does not work, make sure screen reader support is enabled and the browser/keyboard layout is not intercepting Ctrl+Alt.
Practice: Use the command in three different paragraphs.
6.2 Read from the Cursor
What you will learn: Have Docs verbalize content starting from the current location.
Before you begin: Place the cursor in a paragraph.
Exactly how to do it
Hold Ctrl+Alt.
Press A, then R.
Release the keys.
Listen to the document content from the cursor.
What should happen: Docs verbalizes content from the current position.
If that does not happen: If no speech occurs, verify screen reader support and focus.
Practice: Read from two different cursor locations.
Part 7 - Format Text and Paragraphs
| Task | Command |
|---|---|
| Bold | Ctrl+B |
| Italic | Ctrl+I |
| Underline | Ctrl+U |
| Clear formatting | Ctrl+\ |
| Align left | Ctrl+Shift+L |
| Center | Ctrl+Shift+E |
| Align right | Ctrl+Shift+R |
7.1 Apply and Verify Formatting
What you will learn: Format selected text and ask Docs to announce formatting.
Before you begin: Select a word or phrase.
Exactly how to do it
Press Ctrl+B.
Move the cursor into the formatted text.
Hold Ctrl+Alt.
Press A, then F.
Listen for Docs to announce formatting at the cursor.
What should happen: The selected text is bold and formatting is announced.
If that does not happen: If Docs does not announce formatting, confirm screen reader support and try Search menus for the formatting command.
Practice: Bold and unbold a phrase.
Part 8 - Headings and Document Structure
8.1 Apply a Heading Style
What you will learn: Create a real structural heading.
Before you begin: Type a section title on its own line.
Exactly how to do it
Place the cursor in the title.
Press Alt+/.
Type Heading 1.
Use Down Arrow to choose the heading style command.
Press Enter.
Move to the next paragraph and return it to Normal text if needed using Alt+/ and search Normal text.
What should happen: The section title becomes a real heading that screen readers can navigate.
If that does not happen: If you only increase font size/bold, the text may look like a heading but not be structurally identified as one.
Practice: Create Heading 1, Heading 2, and normal body text.
Heading order: Use headings in logical order. Do not skip levels only for visual appearance.
Part 9 - Bulleted and Numbered Lists
9.1 Create a Bulleted List
What you will learn: Create a structured list.
Before you begin: Place the cursor on a blank line.
Exactly how to do it
Press Ctrl+Shift+7 for a numbered list or Ctrl+Shift+8 for a bulleted list depending the list you want.
Type the first item.
Press Enter.
Type the next item.
Press Enter.
Press Enter again on an empty list item to leave the list.
What should happen: Docs creates a true list structure.
If that does not happen: If the list continues when you want to stop, press Backspace at the empty item or toggle the list command off.
Practice: Create a three-item bullet list and a three-step numbered list.
Part 10 - Tables
10.1 Insert a Table
What you will learn: Create a simple table with predictable structure.
Before you begin: Place the cursor where the table should appear.
Exactly how to do it
Press Alt+/.
Type Insert table.
Choose the Insert table command.
Use the table-size picker or dialog with arrow keys/Tab.
Choose the needed rows and columns.
Press Enter.
Type the first cell.
Press Tab to move to the next cell.
What should happen: A table appears and Tab moves through cells.
If that does not happen: If the table is difficult to navigate, simplify it and avoid merged/split cells.
Practice: Create a 3-column by 4-row table.
10.2 Ask Docs for Table Location
What you will learn: Hear row/column context.
Before you begin: Place the cursor inside a table.
Exactly how to do it
Hold Ctrl+Alt+Shift.
Press T, then N.
Listen for the table cell location.
Use Ctrl+Alt+Shift, T then R for row header and T then C for column header when appropriate.
What should happen: Docs announces table location and header context.
If that does not happen: If no header information is available, the table may not have meaningful header structure.
Practice: Move through three cells and announce their locations.
Part 11 - Links, Images, and Alt Text
11.1 Insert a Meaningful Link
What you will learn: Create descriptive hyperlink text.
Before you begin: Select descriptive text.
Exactly how to do it
Press Ctrl+K.
Type or paste the destination address.
Press Enter.
Move through the linked text with the screen reader to verify it remains meaningful out of context.
What should happen: The selected text becomes a link.
If that does not happen: If the visible text is only a raw URL and the URL is not needed, replace it with descriptive text.
Practice: Create one descriptive link.
11.2 Add Alt Text to an Image
What you will learn: Describe an informative image.
Before you begin: Insert or select an image.
Exactly how to do it
Use the image context menu with Shift+F10 or Search menus with Alt+/.
Search for Alt text.
Open the alt text controls.
Enter a concise description of the image's purpose/content.
Save/close the alt text controls.
What should happen: The image has useful alternative text.
If that does not happen: If the image is decorative, keep the surrounding document context clear and avoid meaningless descriptions.
Practice: Add alt text to one practice image.
Part 12 - Find, Replace, and Explore
12.1 Find Text
What you will learn: Locate text without reading line by line.
Before you begin: Open a longer document.
Exactly how to do it
Press Ctrl+F.
Type the search term.
Press Enter to move through matches.
Press Escape when finished.
What should happen: The document moves among matching text.
If that does not happen: If the browser's find interface captures the command differently, use Edit > Find and replace or Alt+/ Search menus.
Practice: Find three terms.
12.2 Replace Text
What you will learn: Change one or all matches carefully.
Before you begin: Use a practice document.
Exactly how to do it
Press Ctrl+H.
Type the old text.
Tab to Replace with.
Type the replacement.
Use Replace for one occurrence or Replace all only when every match should change.
Review the result.
What should happen: Only intended text changes.
If that does not happen: If Replace all may affect unintended text, cancel and replace one at a time.
Practice: Replace one word and undo.
Part 13 - Comments and Suggestions
13.1 Add a Comment
What you will learn: Attach feedback to selected text.
Before you begin: Select a phrase.
Exactly how to do it
Press Ctrl+Alt+M.
Type the comment.
Post the comment with the Post/Comment button.
Return to the document.
What should happen: A comment is anchored to the selected text.
If that does not happen: If the comment is not posted, make sure you activated the Post control.
Practice: Add one practice comment.
13.2 Hear a Comment
What you will learn: Ask Docs to verbalize comment information.
Before you begin: Move the cursor to commented text.
Exactly how to do it
Hold Ctrl+Alt.
Press A, then C.
Listen to the comment.
Use Ctrl+Alt, A then A to verbalize the comment anchor when useful.
What should happen: Docs announces the comment or its anchor.
If that does not happen: If no comment is announced, make sure the cursor is on the commented text.
Practice: Read two comments.
13.3 Use Suggesting Mode
What you will learn: Propose edits instead of changing text permanently.
Before you begin: Open the editing-mode control near the top-right or use Alt+/ and search Suggesting.
Exactly how to do it
Switch from Editing to Suggesting.
Make a small text change.
Listen for the suggestion annotation.
Open the suggestion and choose Accept or Reject.
Return to Editing mode when finished.
What should happen: The edit appears as a suggestion until accepted/rejected.
If that does not happen: If changes are made directly, you are still in Editing mode.
Practice: Create and reject one practice suggestion.
Part 14 - Sharing and Collaboration
14.1 Share a Document
What you will learn: Give another person appropriate access.
Before you begin: Know the recipient and desired permission.
Exactly how to do it
Move to the Share button or press Alt+/ and search Share.
Open Share.
Enter the person's email address.
Choose Viewer, Commenter, or Editor.
Review the recipient and permission carefully.
Add a message if needed.
Activate Send.
What should happen: The recipient receives the selected level of access.
If that does not happen: If the document is confidential, avoid broad 'Anyone with the link' access unless intentionally approved.
Practice: Open Share and inspect permissions without sending.
Permission meanings: Viewer can read. Commenter can read and comment. Editor can change the document.
Part 15 - Version History
15.1 Open Version History
What you will learn: Review earlier states of the document.
Before you begin: The document has been edited over time.
Exactly how to do it
Press Alt+/.
Type Version history.
Choose See version history.
Use Tab/arrow keys through versions.
Listen for date/time and editor information.
Open an earlier version for inspection.
Restore only when you are certain.
What should happen: Earlier document versions can be reviewed.
If that does not happen: If you only need to see who changed something, inspect history without restoring.
Practice: Open version history and return without restoring.
Part 16 - Download, Print, and Export
16.1 Download as Microsoft Word
What you will learn: Create a DOCX copy.
Before you begin: The Google Doc is open.
Exactly how to do it
Open File with Alt+Shift+F or the menu bar.
Move to Download.
Choose Microsoft Word (.docx).
Wait for the browser download.
Press Ctrl+J in Chrome to find the downloaded file.
What should happen: A DOCX copy downloads.
If that does not happen: If formatting changes after download, compare the Word copy with the Google Doc.
Practice: Download a practice document as DOCX.
16.2 Download as PDF
What you will learn: Create a PDF copy.
Before you begin: The document is open.
Exactly how to do it
Open File > Download.
Choose PDF Document (.pdf).
Wait for the download.
Open the PDF and test it with your screen reader.
What should happen: A PDF copy downloads.
If that does not happen: Exported PDFs should be tested because accessibility can differ from the source Docs document.
Practice: Download a practice PDF and inspect it.
16.3 Print
What you will learn: Review print settings before printing.
Before you begin: The document is ready.
Exactly how to do it
Press Ctrl+P.
Wait for print preview.
Review printer, pages, copies, layout, and margins.
Activate Print only after checking the destination.
What should happen: The document prints or the print dialog completes.
If that does not happen: If you only meant to inspect settings, press Escape/Cancel.
Practice: Open Print and cancel.
Part 17 - JAWS with Google Docs
Google recommends using Google Docs as a web application with JAWS Virtual PC Cursor off while editing.
17.1 Prepare JAWS for Editing
What you will learn: Put JAWS into the recommended editing state.
Before you begin: Google Docs is open with JAWS.
Exactly how to do it
Press JAWS+Z.
Listen for Use virtual PC cursor off.
If necessary, press it again depending on your Forms Mode configuration.
Press Ctrl+Alt+Z to verify Docs screen reader support.
Type in the document.
What should happen: JAWS follows Docs editing focus and Docs shortcuts can work.
If that does not happen: If H/K and other web-navigation keys take over unexpectedly, the Virtual PC Cursor may be on.
Practice: Toggle JAWS mode and type a short paragraph.
17.2 Use JAWS Help with Docs
What you will learn: Recover when a command is forgotten.
Before you begin: JAWS is active.
Exactly how to do it
Press Insert+1 for Keyboard Help when learning a JAWS command.
Press Insert+H for hot key help.
Press Ctrl+/ in Google Docs for the Docs shortcut list.
Use Alt+/ to search Docs menus.
What should happen: You can identify whether a command belongs to JAWS or Google Docs.
If that does not happen: If a Docs shortcut is intercepted, check JAWS mode before assuming the shortcut is wrong.
Practice: Look up one Docs command and one JAWS command.
Part 18 - NVDA with Google Docs
Google recommends Focus Mode for editing Google Docs with NVDA.
18.1 Prepare NVDA for Editing
What you will learn: Allow Docs to receive editing commands directly.
Before you begin: Google Docs is open with NVDA.
Exactly how to do it
Press NVDA+Space.
Listen for Focus Mode.
Press Ctrl+Alt+Z to verify screen reader support.
Type in the document.
Use NVDA+Space to return to Browse Mode only when you intentionally need normal webpage navigation outside the editor.
What should happen: Docs receives editing keystrokes directly.
If that does not happen: If letter keys trigger webpage navigation instead of editing, NVDA is probably in Browse Mode.
Practice: Type a paragraph in Focus Mode and then switch to Browse Mode outside the editor.
Shortcut conflict: Google warns that Ctrl+Alt+N is used by Docs Editors. If your NVDA desktop shortcut uses that combination, change the NVDA shortcut to avoid the conflict.
Part 19 - Narrator with Google Docs
Narrator can work with Google Docs, but Docs' own editing mode generally needs direct keyboard interaction.
19.1 Use Narrator for Editing
What you will learn: Switch Narrator out of Scan Mode when Docs needs direct keyboard input.
Before you begin: Google Docs is open with Narrator.
Exactly how to do it
Press Ctrl+Alt+Z to enable Docs screen reader support.
Press Narrator+Spacebar if you need to turn Scan Mode off.
Type and edit in the document.
Use Narrator reading commands when needed.
Turn Scan Mode back on when navigating a normal webpage outside Docs.
What should happen: Docs receives typed characters and Narrator follows focus.
If that does not happen: If H or other letters navigate page structure instead of typing, Scan Mode is probably on.
Practice: Practice editing with Scan Mode off.
Part 20 - VoiceOver with Google Docs
Google recommends Quick Nav off for Google Docs. VoiceOver's default Control+Option modifier can also conflict with Docs menu shortcuts.
20.1 Prepare VoiceOver for Editing
What you will learn: Set VoiceOver so Google Docs can receive keyboard input.
Before you begin: Open Docs on Mac with VoiceOver.
Exactly how to do it
Press Left Arrow and Right Arrow together until you hear Quick Nav off.
Press Command+Option+Z to enable Docs screen reader support.
Type in the document.
If a Google Docs menu shortcut conflicts with Control+Option, use VO+Tab to pass the next key through, or configure Caps Lock as the VoiceOver modifier in VoiceOver Utility.
What should happen: Google Docs receives typing and menu commands more reliably.
If that does not happen: If focus moves away from the editor after a dialog, press Escape and use VoiceOver interaction commands to return to the editing area.
Practice: Type a paragraph and open one Docs menu.
20.2 Return Focus to the Editing Area
What you will learn: Recover after a dialog or pane steals focus.
Before you begin: VoiceOver is running.
Exactly how to do it
Press Escape.
Press VO+Shift+Down Arrow when you need to interact with the editing region.
Use VO navigation until the document text area is announced.
Resume typing.
What should happen: Focus returns to the document editor.
If that does not happen: If it does not, move through the page landmarks/controls until the editing area is located.
Practice: Open and close a comment dialog, then recover to the editor.
Part 21 - Braille Displays
Google Docs supports refreshable braille through the active screen reader. Google recommends Chrome with NVDA or JAWS on Windows and VoiceOver on macOS.
21.1 Turn On Braille Support
What you will learn: Enable Docs' braille-optimized behavior.
Before you begin: Screen reader support is already on.
Exactly how to do it
Press Ctrl+Alt+H on Windows/ChromeOS or Command+Option+H on Mac.
Listen for confirmation.
Move through text using the braille display.
Use cursor routing buttons to move the cursor when supported.
Type with the braille keyboard if supported.
What should happen: Docs improves typing echo, character navigation, punctuation/whitespace announcements, and routing behavior for braille.
If that does not happen: If braille works in other apps but not Docs, verify both screen reader support and braille support are enabled.
Practice: Enable braille support and test output, input, and routing.
Google's braille improvements: With braille support on, Google documents better routing-button behavior, faster typing echo, faster character navigation, and improved punctuation/whitespace announcements.
Part 22 - Accessibility and Document Design
Use real heading styles in logical order.
Use true bulleted and numbered lists.
Use descriptive link text.
Add alt text to meaningful images.
Keep tables simple and avoid merged/split cells when possible.
Use sufficient contrast.
Do not use color alone to communicate meaning.
Use clear document titles and section headings.
Do not rely on visual position alone to communicate sequence.
Download/exported copies should be tested separately because accessibility can change by format.
Part 23 - Troubleshooting
23.1 Docs Shortcuts Do Not Work
What you will learn: Determine whether screen reader support or screen-reader mode is the problem.
Before you begin: A Google Doc is open.
Exactly how to do it
Press Escape once.
Press Ctrl+Alt+Z to verify screen reader support.
JAWS: turn Virtual PC Cursor off.
NVDA: enter Focus Mode.
Narrator: turn Scan Mode off.
VoiceOver: turn Quick Nav off.
Try the Docs shortcut again.
What should happen: Docs receives the command.
If that does not happen: If it still fails, use Alt+/ Search menus to perform the same action and verify the document has focus.
Practice: Memorize this mode-check sequence.
23.2 Typing Does Nothing or Activates Commands
What you will learn: Return to direct editing focus.
Before you begin: You intend to type in the document.
Exactly how to do it
Press Escape to leave menus/dialogs.
Move focus back to the document editor.
Use the correct direct-editing mode for your screen reader.
Type one test word.
Undo with Ctrl+Z if needed.
What should happen: Text appears in the document.
If that does not happen: If not, the editor does not have keyboard focus.
Practice: Practice leaving a menu and returning to typing.
23.3 Ctrl+Alt Shortcuts Behave Strangely
What you will learn: Check keyboard layout and system conflicts.
Before you begin: A Docs shortcut using Ctrl+Alt is failing.
Exactly how to do it
Confirm you are using the intended Windows keyboard layout.
Remember that some non-US layouts treat Ctrl+Alt as AltGr.
Use the menu path instead if needed.
Check whether your screen reader or another application has claimed the shortcut.
What should happen: You identify whether the problem is Docs, keyboard layout, or a shortcut conflict.
If that does not happen: Google specifically notes that non-US keyboard layouts can cause Ctrl+Alt shortcuts to behave as AltGr.
Practice: Test the shortcut and menu alternative.
23.4 Collaboration Announcements Are Too Verbose
What you will learn: Reduce distraction without disabling essential access.
Before you begin: Multiple people are editing the document.
Exactly how to do it
Open accessibility settings.
Review collaborator announcement options.
Turn off or reduce announcements about people entering, leaving, or editing if desired.
Keep essential document and comment announcements enabled.
What should happen: Collaboration is less distracting.
If that does not happen: If important changes become hard to track, restore the announcement setting.
Practice: Adjust and restore the setting once.
Part 24 - Independent Practice Course
Level 1 - Open and Enable Access
☐ Open docs.new.
☐ Enable screen reader support.
☐ Identify document body.
☐ Use Alt+/ Search menus.
Ready to advance: You can complete every checked task without another person telling you which key to press.
Level 2 - Editing
☐ Type paragraph.
☐ Move by word.
☐ Select text.
☐ Correct errors.
☐ Undo/redo.
Ready to advance: You can complete every checked task without another person telling you which key to press.
Level 3 - Structure
☐ Create Heading 1.
☐ Create Heading 2.
☐ Create bullet list.
☐ Create numbered list.
Ready to advance: You can complete every checked task without another person telling you which key to press.
Level 4 - Tables and Links
☐ Insert table.
☐ Move through cells.
☐ Announce table location.
☐ Insert descriptive link.
Ready to advance: You can complete every checked task without another person telling you which key to press.
Level 5 - Comments and Suggestions
☐ Add comment.
☐ Hear comment.
☐ Create suggestion.
☐ Accept/reject suggestion.
Ready to advance: You can complete every checked task without another person telling you which key to press.
Level 6 - Sharing
☐ Open Share.
☐ Compare Viewer/Commenter/Editor.
☐ Inspect Version History.
☐ Return without restoring.
Ready to advance: You can complete every checked task without another person telling you which key to press.
Level 7 - Screen Reader Mode
☐ JAWS Virtual PC Cursor off.
☐ NVDA Focus Mode.
☐ Narrator Scan Mode off.
☐ VoiceOver Quick Nav off.
Ready to advance: You can complete every checked task without another person telling you which key to press.
Level 8 - Braille
☐ Enable braille support.
☐ Read text.
☐ Type with braille input if supported.
☐ Use routing buttons.
Ready to advance: You can complete every checked task without another person telling you which key to press.
Level 9 - Export
☐ Download as DOCX.
☐ Download as PDF.
☐ Test the exported file.
☐ Open Print and cancel.
Ready to advance: You can complete every checked task without another person telling you which key to press.
Level 10 - Independent Document
☐ Create a two-page structured document.
☐ Use headings/lists/table/link/comment.
☐ Share with correct permission.
☐ Export and test.
Ready to advance: You can complete every checked task without another person telling you which key to press.
Part 25 - Quick Reference Commands
Google Docs Accessibility
| Task | Command |
|---|---|
| Enable screen reader support - Windows | Ctrl+Alt+Z |
| Enable screen reader support - Mac | Command+Option+Z |
| Enable braille support - Windows | Ctrl+Alt+H |
| Enable braille support - Mac | Command+Option+H |
| Keyboard shortcuts list | Ctrl+/ |
| Search menus | Alt+/ |
| Announce selection | Ctrl+Alt, A then X |
| Verbalize from cursor | Ctrl+Alt, A then R |
| Announce cursor location | Ctrl+Alt, A then L |
| Announce formatting | Ctrl+Alt, A then F |
| Announce comment | Ctrl+Alt, A then C |
| Announce comment anchor | Ctrl+Alt, A then A |
| Show live edits | Ctrl+Alt+Shift+R |
| Table row/column headers | Ctrl+Alt+Shift, T then H |
| Table cell location | Ctrl+Alt+Shift, T then N |
Common Editing
| Task | Command |
|---|---|
| Bold / Italic / Underline | Ctrl+B / Ctrl+I / Ctrl+U |
| Insert link | Ctrl+K |
| New comment | Ctrl+Alt+M |
| Find / Replace | Ctrl+F / Ctrl+H |
| Undo / Redo | Ctrl+Z / Ctrl+Y |
| Bulleted list | Ctrl+Shift+8 |
| Numbered list | Ctrl+Shift+7 |
Screen Reader Mode Reminders
| Task | Command |
|---|---|
| JAWS editing mode | Virtual PC Cursor off - JAWS+Z |
| NVDA editing mode | Focus Mode - NVDA+Space |
| Narrator editing mode | Scan Mode off - Narrator+Spacebar |
| VoiceOver editing mode | Quick Nav off - Left+Right Arrow together |
Part 26 - Official Google Resources
Use Google Docs Editors with a screen reader
Google Docs keyboard shortcuts
Use a braille display with Google Docs
Google Docs Editors with magnification and high contrast
Final Independence Checklist
☐ I can open a blank Google Doc.
☐ I can enable screen reader support.
☐ I can identify menus, toolbar, and document body.
☐ I can type, navigate, select, edit, undo, and redo.
☐ I can create real headings and lists.
☐ I can create and navigate a simple table.
☐ I can insert descriptive links and image alt text.
☐ I can find and replace text.
☐ I can add/read comments and use Suggesting mode.
☐ I can share with the correct permission.
☐ I can inspect Version History.
☐ I can download DOCX/PDF copies and test them.
☐ I can configure JAWS, NVDA, Narrator, or VoiceOver for Docs editing.
☐ I can enable braille support and test routing/input.
☐ I can troubleshoot screen-reader mode and shortcut conflicts.
Most important habit: In Google Docs, always know whether your screen reader is in a webpage-reading mode or a direct-editing mode. If letters or shortcuts behave unexpectedly, check that mode first.