A conversation with Figma's accessibility team | Figma Blog

Figma’s accessibility team describes how open beta testing and user feedback shaped screen reader support for prototypes. They learned that accessibility must account for different assistive technologies, varied user needs, and interaction between visual and nonvisual experiences. The team sees the current release as an important step, but plans further improvements to generated HTML and accessibility evaluation tools.

Lessons from the Open Beta

• Testing with real users revealed that support working well in Mac VoiceOver did not guarantee compatibility with JAWS and other screen readers.
• Figma began testing major screen reader technologies earlier in development.
• The team recognized that screen readers complement visual work rather than serving only users who cannot see.
• Low-vision users may use visual and audio information together for additional context.

Design Decisions for Screen Reader Support

• Added positioning information to the accessibility tree so sighted screen reader users can understand the cursor’s location on the canvas.
• Made “On hover” interactions activate when clickable elements receive focus.
• Enabled scrollable areas to follow the screen reader cursor, similar to native HTML behavior.
• Adjusted auto-hiding toolbars so focused controls remain visible.
• Added shortcuts to open prototype mode:
  • Mac: Option + Command + Return
  • PC: Alt + Ctrl + Enter
• Added a persistent screen reader support toggle and more guidance through Figma Community.

Feedback from Accessibility Partners

• Figma works with Fable to test product flows with people who use assistive technologies.
• Partner feedback highlighted the need to communicate accessibility controls more clearly.
• Accessibility navigation shortcuts are being added to the keyboard shortcuts panel, along with improvements to the panel itself.
• For FigJam, screen readers now receive information about the number of children or siblings associated with each item.
• Fable’s input helps Figma support different screen reader software and users with varying levels of expertise.

Future Accessibility Improvements

• Figma plans to make content available to screen reader users by default.
• The team wants to give designers greater control over the HTML generated from their designs.
• Longer term, Figma hopes to provide tools that help designers assess accessibility without requiring deep screen reader knowledge.

Figma’s experience shows that accessibility improves through ongoing testing, direct collaboration with assistive-technology users, and removing assumptions about how people work. The current screen reader support is presented as a foundation for continued product and design improvements.