- New Untriaged Bugs in Bugzilla: https://mzl.la/3pjFR8R
- Older Untriaged Bugs in Bugzilla: https://mzl.la/35kLz2h
- Untriaged Fenix Bugs: https://github.com/mozilla-mobile/fenix/issues?q=is%3Aopen+is%3Aissue+label%3Aneeds%3Atriage+label%3Ab%3Aa11y+created%3A%3E2020-07-28
- A11y Reviews Tracker: https://docs.google.com/spreadsheets/d/1VApqSeSg4DEpsszfrhb0wvZLxjLj_kHWcdDVgfAi15c/edit#gid=0 (Internal Mozilla-only Google Sheet)
Triaging Firefox and Gecko feature defects
The Firefox Accessibility Team helps to assess accessibility issues across most Firefox and Gecko components. For accessibility issues reported in components not owned by the Firefox Accessibility Team (bugs with the access Keyword) we set a Whiteboard severity flag which communicates the team's assessment of the user impact of the issue. Below find the Whiteboard flags, their descriptions, and some examples of the types of bugs that warrant those flags.
[access-s1] Accessibility of the entire product is broken. Examples include the accessibility engine failing or a critical piece of the browser's functionality like the URLbar not working. These bugs represent catastrophic failures and should be rare.
[access-s2] Feature completely unavailable/inaccessible. Examples include lack of keyboard support for screen reader users, insufficient contrast or missing focus indicators, or missing controls in HCM (due to no background images) that make a feature not discoverable/actionable by users with low vision, UI that disappears or becomes otherwise inaccessible with large zoom factors, etc. These bugs should absolutely block a feature from shipping to our stable release audience.
[access-s3] Feature available but difficult to use. Examples include inconsiderate tab order, missing alt text for non-text content, visually hidden but not accessibility hidden content, inconsistent heading levels, dialogs that should be role=document, difficult to see focus indicators, etc. These bugs should be fixed and may or may not block a feature from shipping to our stable release audience and will be evaluated for blocking status on a case by case basis.
[access-s4] Feature available with minor defects. Examples include … These bugs should be fixed but probably do not block a feature from shipping to our release audience. This is the backlog.
Triaging for Disability Access and Disability Access APIs
The Firefox Accessibility Team is also responsible for triaging bugs in the Disability Access and the Disability Access APIs components. As these components are owned by the Firefox Accessibility Engineering Team, we set severity and priority on these bugs directly using the Severity and Priority fields.
Triaging Fenix (Firefox for Android) GitHub Issues
The Firefox Accessibility Team is responsible for triaging all Fenix bugs with the b:a11y label. We use P1 to describe completely broken features, P2 to describe difficult to use features, and P3 for general backlog bugs.
Triaging and Reviewing Accessibility Reviews
- Add items that come in
- Check for "due" items that need follow up
- Assign Owners