Accessibility: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎Team and Expertise: added Natalie)
 
(68 intermediate revisions by 17 users not shown)
Line 1: Line 1:
= Mozilla Accessibility Wiki =
== About ==


* [http://developer.mozilla.org/en/docs/Accessibility Development Center] - Documentation on Various Accessibility Initiatives, Xull Authoring Guidelines, ARIA, AT-SPI, Web Development and more
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.  
* [[Accessibility/Testing|Testing Center]] - The latest on Mozilla Accessibility testing, test plans, environments, top bugs, and more.
 
*[[Accessibility/Attributes|AT-SPI Attributes]] -  proposed AT-SPI attribute support.
== Roadmap and Project Status ==
*[[Accessibility/Datatypes|ARIA Type Attributes]] -- proposed ARIA data type attributes to object attribute mapping
 
*[[Accessibility/AT-Windows-API|Gecko Info for Windows Accessibility Vendors]] - this FAQ explains how makers of Windows screen readers, voice dictation packages and magnification software can support Gecko-based software.
* [[Accessibility/Roadmap|Firefox Accessibility Roadmap]]
*[[Accessibility/IA2ToGecko|Mapping IAccessible2 to Gecko]]
 
*[[Accessibility/XForms|XForms Accessibility]] - AT API support for XForms elements.
== Get Involved ==
*[[Accessibility/csun2007|CSUN 2007]] - Mozilla CSUN 2007 Activities
 
*[[Accessibility/Firefox3|Firefox3]]
=== Guidelines and Resources ===
*[[Accessibility/Projects|Potential Accessibility Projects]]
 
*[[Accessibility/AJAX:WAI_ARIA_Live_Region_Library|AJAX: WAI ARIA Live Region Library]]
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.
*[[Accessibility/Accessible_Table_Implementation|Accessible Table Implementation]]
 
*[[Accessibility/Learning_Disabilities|Learning Disabilities]] - Resources related to learning disabilities
Please reference and share our [[Accessibility/Requirements|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 [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!
 
=== 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
 
==== Natalie (@nata11y) ====
* Accessibility reviews (design and engineering)
* Documentation
 
=== Slack and 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 (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:20, 18 December 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

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

Natalie (@nata11y)

  • Accessibility reviews (design and engineering)
  • Documentation

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.
Retrieved from "https://wiki.mozilla.org/index.php?title=Accessibility&oldid=1255992"