From MozillaWiki
Jump to: navigation, search


The Firefox Accessibility Team is responsible for the core disability access APIs in Gecko and we share responsibility with the Firefox front end team for the accessibility (often abbreviated as "a11y") of the browser's feature set. We're here to ensure that Firefox products and services are delightfully accessible to users with disabilities.

Roadmap and Project Status

Get Involved

Guidelines and Resources

We have published, and will continue to produce and share, resources and guidelines to help you better understand digital accessibility and to make your product as accessible as possible.

Please reference and share our accessibility guidelines and resources.

Accessibility Reviews

You should consider requesting accessibility review frfom our if you aren’t certain whether your change is accessible to people with disabilities.

Learn more about requesting accessibility reviews from the Accessibility team.

Report Accessibility Bugs

See also: our Accessibility Bug Triage Guidelines

Contact Us

If you have accessibility questions that pertain to a particular sub-component or platform, you should get in touch with the member of the accessibility team best suited to help!

If you have general questions, or are not sure who to talk to: find us all on Slack and Matrix!

Team and Expertise

Kim (@KimB)

  • Product Management
  • Accessibility Strategy & Process
  • Disability (history, theory, narrative, practical applications)

Eitan (@eeejay)

  • Android (TalkBack)
  • Linux (Orca)
  • macOS (VoiceOver)

Jamie (@jteh)

  • NVDA
  • Windows

Morgan (@morgan)

  • macOS (VoiceOver)
  • High contrast (HCM) and low vision
  • Layout-a11y crossover

Anna (@ayeddi)

  • Accessibility reviews
  • Frontend (desktop, mobile)
  • Testing and remediation guidance

Nathan (@Nathan)

  • Accessibility Interop
  • Windows
  • Accessibility reviews

Slack and Matrix

  • Matrix/Riot.IM: #accessibility on Synchronous discussions about engineering-specific topics (bugs, patches, code reviews, architectural issues, etc.) should happen in Matrix/Riot.IM.
  • Slack: #accessibility on Slack (MoCo employees and NDA'd contributors only.) Synchronous discussions about team operations, announcements, strategy, roadmap, and other banter tend to happen in Slack, but we endeavor to move as much of that as possible to Matrix/Riot.IM.