Google Form Accessibility | Testing with NVDA

Today’s post explores Google Form accessibility best practices by actually testing a form with NVDA.

Google Forms can be a great way to collect data, but accessibility depends on how you build the form and what the platform can and cannot do. Most of what you create in Google Forms can work accessibly, as long as you understand a few limitations and design your questions with clarity.

Video Guide

Platform Limitations

Images: no built-in alt text

Google Forms does not let you add alternate text to images. If you include images, describe them in text so screen reader users get the same information.

Put any image description in the question text or the question description.

Labels and instructions must be explicit

Write instructions directly into the question or description. Don’t rely on placeholder text or visual layout to communicate meaning. If the user needs to know something, say it clearly.

Color contrast can still be an issue

Some form elements still fall short on color contrast, including checkboxes and some focus indicators. Don’t depend on subtle visual cues to show where someone is on the page or what they need to do.

Section logic needs real testing

If you use section logic or branching, test it carefully. In some cases, it can break accessibility or make navigation confusing for assistive technology users.

Zoom and layout considerations

Some setups struggle at 200% zoom, especially if the layout or visual quality changes in a way that affects readability. Simple forms tend to hold up better across zoom levels and different user settings.

Testing a Google Form with NVDA

Launch NVDA and move through the form using only the keyboard. Focus on how the form announces structure, labels, and controls as you navigate.

NVDA should announce the form’s main heading at the top. Listen for a clear heading structure that helps you understand where you are and what the form covers.

Press Tab until you land on the first form field. Keep tabbing to confirm you can reach every interactive element in a logical order without getting stuck.

When you land on a required question, NVDA should announce that it’s required. In radio-button questions, NVDA should read the question grouping first, then each option. Use the arrow keys or keyboard controls to select an option, then Tab to move forward.

Move to a question that requires a typed answer. NVDA will read the question and may read the full description before or as you enter the field. Keep descriptions short and direct so users can respond without wading through extra text.

Use the Next button and any section navigation to confirm NVDA announces changes clearly. If the form uses branching or section logic, follow each possible path and check that navigation stays predictable.

Choices that support accessibility

Google Forms can be accessible, but the results depend on how you build the form and whether you test it with real assistive tech. Write clear labels and instructions, describe any images in text, keep layout and logic simple, and double-check contrast, zoom, and section branching so everyone can complete the form without guesswork.

Let me be your champion for inclusion. I offer tailored solutions (and self-paced courses!) to ensure your documents meet and exceed compliance expectations. For more detailed insights, tutorials, and in-depth discussions on accessibility and related topics, don’t forget to check out my YouTube channel: The Accessibility Guy on YouTube. Subscribe for regular updates!