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
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.
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
- Disability Access APIs For bugs in Gecko's accessibility support.
- Disability Access For accessibility bugs in Firefox features. (Most of these will be triaged to other Firefox components.)
- Fenix GitHub Issues For accessibility bugs in the next generation Firefox browser for Android.
See also: our Accessibility Bug Triage Guidelines
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
- Product Management
- Accessibility Reviews (design review and audits)
- Windows (including NVDA and JAWS) Mac, Linux, Android, and iOS
- Android (TalkBack)
- Linux (Orca)
- macOS (VoiceOver)
- macOS (VoiceOver)
- High contrast (HCM) and low vision
- Layout-a11y crossover
- Desktop (Windows and macOS): Keyboard-only use, NVDA, VoiceOver, Voice Control, and magnification
- Mobile (Android and iOS): TalkBack, VoiceOver, Switch Control, Voice Control, magnification, and inverse colors
- Cognitive difficulties, limited mobility, color deficiency, and low vision
- Accessibility Reviews (design review and audits) and high contrast (HCM) mockups
Slack and Matrix
- Matrix/Riot.IM: #accessibility on chat.mozilla.org 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.