Forum Discussion
WCAG 2.1 AA and Microsoft Forms
Hello Team,
Does Microsoft Forms meet the success criteria for WCAG 2.1 AA? In a previous post, I saw a Microsoft Representative stated he could navigate Microsoft Forms with JAWS in Firefox. Wondering if this includes proper aria labels to note the type of question, required responses, and handling error messaging. Are there any question types that pose trouble for those with visual, cognitive, or dexterity disabilities?
Thank you!
1 Reply
Microsoft Forms is built with accessibility in mind, and a lot of the experience lines up with WCAG 2.1 AA standards. Things like keyboard navigation, screen‑reader support, color contrast, and labeling for most question types are handled reasonably well. Users who rely on JAWS, NVDA, VoiceOver, and similar tools generally report that they can move through Forms without major issues.
That said, Microsoft hasn’t published an official statement stating Forms fully meets WCAG 2.1 AA compliance standards. The product aims for that level of accessibility, but it isn’t formally certified.
In practice, most question types work with assistive technologies. Required fields are announced, ARIA labels are present, and error messages are usually conveyed in a way screen readers can understand. For people with visual, cognitive, or dexterity disabilities, the overall experience is acceptable.
But there are a few areas where users might run into friction:
- Ranking questions can be tricky for keyboard‑only users because of the drag‑and‑drop interaction
- Drag‑and‑drop elements in general aren’t the smoothest experience for screen readers
- Complex branching logic can occasionally make the reading order feel less intuitive
- Image‑based questions depend heavily on the form author adding meaningful alt text
None of these are outright blockers, but they’re worth keeping in mind if you’re designing a form for a broad audience.
Hope this helps!
-Rob
