Accessibility
Jump to navigation
Jump to search
About
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 of the browser's feature set. We're here to ensure that Firefox products and services are delightfully accessible to users with disabilities.
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! Got general questions, or not sure who to talk to? Find us all on slack and matrix!
Have specific questions?
Asa (@asa)
- Project Management
- Accessibility Reviews (design)
Devin (@dreams)
- Engineering Management
- Planning, process, resource allocation
Eitan (@eeejay)
- Android (TalkBack)
- Linux (Orca)
- MacOS (VoiceOver)
Jamie (@jteh)
- NVDA
- Windows
Marco (@marcoz)
- A11y QA
- JAWS
- MacOS (VoiceOver)
Morgan (@morgan)
- MacOS (VoiceOver)
- High contrast (HCM) and low vision
- Layout-a11y crossover
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.
Roadmap and Project Status
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.