20
edits
User:Ayeddi: Difference between revisions
Jump to navigation
Jump to search
Added a draft for the A11y Triage section update
(Updated the user profile with details) |
(Added a draft for the A11y Triage section update) |
||
| Line 17: | Line 17: | ||
... I might be able to help! You can find me on Slack and Matrix at @ayeddi, try me there first before reaching out over email. I'm also only a ni? away on Bugzilla. | ... I might be able to help! You can find me on Slack and Matrix at @ayeddi, try me there first before reaching out over email. I'm also only a ni? away on Bugzilla. | ||
= DRAFT below = | |||
== Triaging Firefox and Gecko feature defects == | |||
The Firefox Accessibility Team helps to assess accessibility issues across most Firefox and Gecko components on Bugzilla and GitHub. In components not owned by the Firefox Accessibility Team, '''reported issues that may have an accessibility impact should get the <code>access</code> keyword on the bug to indicate the need to the accessibility triage.''' | |||
During triage, the Accessibility Team will set the value in the <code>Accessibility Severity</code> field on bugs in Bugzilla and the <code>access-s1</code> through <code>access-s4</code> labels on issues in GitHub/Jira, which communicates the team's assessment of the user impact of the issue. | |||
=== Accessibility Severity values and some examples that warrant those values: === | |||
;<code>s1</code>: '''Accessibility of the entire product is broken.''' These bugs represent catastrophic failures and should be rare. | |||
:{| class="mw-collapsible mw-collapsed wikitable" | |||
|+ style="white-space: nowrap;" | Examples include: | |||
|- | |||
| a critical piece of the browser's functionality like the URLbar not working | |||
|- | |||
| Firefox crashes when assistive technology is used | |||
|} | |||
<code>s2</code>: | |||
*'''Feature completely unavailable/inaccessible.''' | |||
* These bugs should absolutely block a feature from shipping to our stable release audience. | |||
:{| class="mw-collapsible mw-collapsed wikitable" | |||
|+ style="white-space: nowrap" | Examples include: | |||
|- | |||
| lack of keyboard support | |||
|- | |||
| missing labels for screen reader users on icon buttons/links | |||
|- | |||
| insufficient contrast | |||
|- | |||
| missing focus indicators | |||
|- | |||
| missing controls in HCM (due to no background images or inappropriate CSS system colors combinations) that make a feature not discoverable/actionable by users with low vision | |||
|- | |||
| UI that disappears or becomes otherwise inaccessible with large zoom factors | |||
|- | |||
| touch targets below WCAG recommendations | |||
|} | |||
* <code>s3</code>: '''Feature available but difficult to use.''' 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. | |||
{| class="mw-collapsible mw-collapsed wikitable" | |||
|+ style="white-space: nowrap" | Examples include: | |||
|- | |||
| inconsiderate focus and/or reading order | |||
|- | |||
| missing alt text for non-text content | |||
|- | |||
| visually hidden but not accessibility hidden content | |||
|- | |||
| inconsistent heading levels | |||
|- | |||
| dialogs that not exposed to assistive technology and should have role="document" | |||
|- | |||
| difficult to see focus indicators | |||
|- | |||
| missing control borders or unexpected CSS system colors used for states on HCM | |||
|- | |||
| touch targets under mobile platform recommendations | |||
|} | |||
;<code>s4</code> (Feature available with minor defects) | |||
:These bugs should be fixed but probably do not block a feature from shipping to our release audience. This is the backlog. | |||
:{| class="mw-collapsible mw-collapsed wikitable" role="definition" | |||
| Examples include: | |||
|- | |||
| minor overlapping of the control borders while on HCM | |||
|- | |||
| UI patterns that are technically compliant with WCAG, but could be improved to be more delightful and efficient to use | |||
|} | |||
'''Note:''' If you're looking for ways to request an evaluation of how accessible is a UI or a feature is, refer to [https://firefox-source-docs.mozilla.org/bug-mgmt/processes/accessibility-review.html the Accessibility Review - Firefox Source Docs] to request a design or engineering a11y review. | |||