16
edits
Changes
rearrange the page and explain some of our pointers a bit more
== 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 == * [[Accessibility/Roadmap|Firefox Accessibility Roadmap]]* [[Accessibility/Mac2020|Firefox accessibility on macOS]] == 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/Requirements|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 [https://firefox-source-docs.mozilla.org/bug-mgmt/processes/accessibility-review.html requesting accessibility reviews] from the Accessibility team. === Report Accessibility Bugs === * [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Disability+Access+APIs Disability Access APIs] For bugs in Gecko's accessibility support. * [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Disability+Access Disability Access] For accessibility bugs in Firefox features. (Most of these will be triaged to other Firefox components.)* [https://github.com/mozilla-mobile/fenix/issues/new?assignees=&labels=%F0%9F%90%9E+bug,b:a11y&template=---bug-report.md Fenix GitHub Issues] For accessibility bugs in the next generation Firefox browser for Android. See also: our [[Accessibility/Triage|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! === Have specific questions? Team and Expertise ===
==== Asa (@asa) ====
* Project Management
* Accessibility Reviews (design)
==== Eitan (@eeejay) ====
* Android (TalkBack)
* Linux (Orca)
* MacOS macOS (VoiceOver)
==== Jamie (@jteh) ====
* A11y QA
* JAWS
* MacOS macOS (VoiceOver)
==== Morgan (@morgan) ====
* MacOS macOS (VoiceOver)
* High contrast (HCM) and low vision
* Layout-a11y crossover
=== Slack and Matrix ===
* '''Matrix/Riot.IM''': [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/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.
