Accessibility: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (whitespace)
 
(30 intermediate revisions by 13 users not shown)
Line 1: Line 1:
= Mozilla Accessibility Wiki =
== About ==


* General
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.  
** [http://developer.mozilla.org/en/docs/Accessibility Development Center] - documentation on various accessibility initiatives, XUL authoring guidelines, ARIA, AT-SPI, web development and more
**[[Accessibility/Learning_Disabilities|Learning Disabilities]] - resources related to learning disabilities
** [[Accessibility/Testing|Testing Center]] - the latest on Mozilla accessibility testing, test plans, environments, top bugs, and more.


* Sections
== Roadmap and Project Status ==
**[[Mac:Accessibility| Mac Accessibility]] - home page of accessibility support on Mac.
** [[Accessibility/AT-Windows-API|Windows Accessibility]] - this FAQ explains how makers of Windows screen readers, voice dictation packages and magnification software can support Gecko-based software. The article is targeted on MSAA.
**[[Accessibility/XForms|XForms Accessibility]] - AT API support for XForms elements.


* Drafts
* [[Accessibility/Roadmap|Firefox Accessibility Roadmap]]
**ARIA
* [[Accessibility/Mac2020|Firefox accessibility on macOS]]
***[[Accessibility/Datatypes|ARIA Type Attributes]] - proposed ARIA data type attributes to object attribute mapping
* [[Accessibility/CacheTheWorld|Cache the World]]
***[[Accessibility/AJAX:WAI_ARIA_Live_Region_Library|AJAX: WAI ARIA Live Region Library]]
***[[Accessibility/ARIAConflictsWithNativeMarkup|ARIA conflicts with native markup]] - proposed extension of section 2.3 of ARIA implementation guide
**Accessible Tables
***[[Accessibility/Accessible_Table_Implementation|Table Implementation]] - implementation problems overlook (a bit obsolete)
***[[Accessibility/TreeGrid|ARIA grid/treegrid]] - implementation of ARIA grid/treegrid
**[[Accessibility/CustomWidgets|Custom widgets accessibility]] -  accessibility injection into XBL
**[[Accessibility/Plugins|Plugins accessibility]] - thoughts how to improve plugin accessibility
**[[Accessibility/EditorBehaviourOnUserInput|Editor behaviour]] - editor behaviour on user input when controls are contained inside of editable area
**[[Accessibility/MutationEventCoalescing|Mutation event coalescing]]
**[[Accessibility/HTML5_Forms HTML5 form enhancements]]


* Drafts Replaced by Specs
== Get Involved ==
**[[Accessibility/Attributes|Attributes]] -  proposed AT API attribute support.
**[[Accessibility/TextAttributes|Text Attributes]] -  proposed AT API text attribute support.
**[[Accessibility/IA2ToGecko|IA2 to Gecko]] - interface mapping of IAccessible2 to Gecko API
***[[Accessibility/TableHeaders|Table Headers]] - IA2's rowHeader/columnHeader implementation


* Project Coordination
=== Guidelines and Resources ===
**[[Accessibility/Strategy|Proposed Accessibility Strategy]]
 
**[[Accessibility/Projects|Potential Accessibility Projects]]
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/PlanMozilla2|Mozilla 2 accessibility plans]]
 
**[[Platform/2009-Accessibility-Goals|2009 accessibility plans]]
Please reference and share our [[Accessibility/Requirements|accessibility guidelines and resources]].
**[[Accessibility/Firefox3|Firefox3]] - the list of meta bugs targeted to Firefox 3
 
**[[Accessibility/ARIA_Coordination|ARIA coordination]]
=== Accessibility Reviews ===
**[[Accessibility/Video_Accessibility|Video accessibility]]
 
**[[Accessibility/Math_Accessibility|Math accessibility]]
You should consider requesting accessibility review frfom our if you aren’t certain whether your change is accessible to people with disabilities.
**[[Accessibility/csun2009|CSUN 2009]] - Mozilla CSUN 2008 Activities
 
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 ===
 
==== Asa (@asa) ====
* Product Management
* Accessibility Reviews (design review and audits)
* Windows (including NVDA and JAWS) Mac, Linux, Android, and iOS
 
==== Eitan (@eeejay) ====
* Android (TalkBack)
* Linux (Orca)
* macOS (VoiceOver)
 
==== Jamie (@jteh) ====
* NVDA
* Windows
 
==== Morgan (@morgan) ====
* macOS (VoiceOver)
* High contrast (HCM) and low vision
* Layout-a11y crossover
 
==== Anna (@ayeddi) ====
* 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
 
==== Nathan (@Nathan) ====
* TBD!
 
=== 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.

Latest revision as of 19:22, 16 August 2022

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 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

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

Asa (@asa)

  • Product Management
  • Accessibility Reviews (design review and audits)
  • Windows (including NVDA and JAWS) Mac, Linux, Android, and iOS

Eitan (@eeejay)

  • Android (TalkBack)
  • Linux (Orca)
  • macOS (VoiceOver)

Jamie (@jteh)

  • NVDA
  • Windows

Morgan (@morgan)

  • macOS (VoiceOver)
  • High contrast (HCM) and low vision
  • Layout-a11y crossover

Anna (@ayeddi)

  • 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

Nathan (@Nathan)

  • TBD!

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