Accessibility: Difference between revisions
m (miss you, Marco) |
(→Team and Expertise: removed Nathan from the list, oh :() |
||
| (8 intermediate revisions by 4 users not shown) | |||
| Line 6: | Line 6: | ||
* [[Accessibility/Roadmap|Firefox Accessibility Roadmap]] | * [[Accessibility/Roadmap|Firefox Accessibility Roadmap]] | ||
== Get Involved == | == Get Involved == | ||
| Line 19: | Line 17: | ||
=== Accessibility Reviews === | === Accessibility Reviews === | ||
You should consider requesting accessibility review | You should consider requesting accessibility review if you aren’t certain whether your change is accessible to people with disabilities. | ||
Learn more about [https://firefox-source-docs.mozilla.org/bug-mgmt/processes/accessibility-review.html requesting accessibility reviews] from the Accessibility team. | Learn more about [https://firefox-source-docs.mozilla.org/bug-mgmt/processes/accessibility-review.html requesting accessibility reviews] from the Accessibility team. | ||
| Line 39: | Line 37: | ||
=== Team and Expertise === | === Team and Expertise === | ||
==== | ==== Kim (@KimB) ==== | ||
* Product Management | * Product Management | ||
* Accessibility | * Accessibility Strategy & Process | ||
* Disability (history, theory, narrative, practical applications) | |||
==== Eitan (@eeejay) ==== | ==== Eitan (@eeejay) ==== | ||
| Line 49: | Line 48: | ||
==== Jamie (@jteh) ==== | ==== Jamie (@jteh) ==== | ||
* Mozilla accessibility tech lead | |||
* NVDA | * NVDA | ||
* Windows | * Windows | ||
* ARIA and HTML accessibility standards | |||
==== Morgan (@morgan) ==== | ==== Morgan (@morgan) ==== | ||
| Line 56: | Line 57: | ||
* High contrast (HCM) and low vision | * High contrast (HCM) and low vision | ||
* Layout-a11y crossover | * Layout-a11y crossover | ||
==== Anna (@ayeddi) ==== | |||
* Accessibility reviews | |||
* Front-end (desktop, mobile) | |||
* Testing and remediation guidance | |||
=== Slack and Matrix === | === Slack and Matrix === | ||
* '''Matrix/ | * '''Matrix/Element.io''': [https://chat.mozilla.org/#/room/#accessibility:mozilla.org #accessibility on chat.mozilla.org] Synchronous discussions about engineering-specific topics (bugs, patches, code reviews, architectural issues, etc.) should happen in Matrix/Element.io. | ||
* '''Slack''': #accessibility on Slack ( | * '''Slack''': #accessibility on Slack (mostly only Mozilla employees) 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. | ||
Latest revision as of 16:32, 28 March 2025
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 (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 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
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)
- Mozilla accessibility tech lead
- NVDA
- Windows
- ARIA and HTML accessibility standards
Morgan (@morgan)
- macOS (VoiceOver)
- High contrast (HCM) and low vision
- Layout-a11y crossover
Anna (@ayeddi)
- Accessibility reviews
- Front-end (desktop, mobile)
- Testing and remediation guidance
Slack and Matrix
- Matrix/Element.io: #accessibility on chat.mozilla.org Synchronous discussions about engineering-specific topics (bugs, patches, code reviews, architectural issues, etc.) should happen in Matrix/Element.io.
- Slack: #accessibility on Slack (mostly only Mozilla employees) 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.