21
edits
Accessibility/Triage: Difference between revisions
→Search Queries: added Firefox Enterprise in the search query for the New and Old bugs queries in Firefox Desktop
(→Triaging Firefox and Gecko feature defects: Updated formatting to highlight the use of "access" keyword and the severity labels to improve readability, and added the following 2 examples for the S4 issue: "Examples include minor overlapping of the control borders while on HCM, technically compliant with WCAG patterns that could be improved to be more delightful and efficient to use, etc.") |
(→Search Queries: added Firefox Enterprise in the search query for the New and Old bugs queries in Firefox Desktop) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Search Queries == | == Search Queries == | ||
* [https://bugzilla.mozilla.org/buglist.cgi?f8=OP&o14=equals&f22=CP&v15=Accessibility%20Tools&f12=CP&bug_type=defect&v3=---&chfield=%5BBug%20creation%5D&f4=product&f1=OP&f19=component&f2=keywords&f18=product&f17=OP&o7=equals&query_format=advanced&f11=component&f21=CP&j8=OR&o3=equals&o15=equals&v14=DevTools&resolution=---&f5=CP&columnlist=bug_type%2Cshort_desc%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cchangeddate%2Cstatus_whiteboard%2Ckeywords%2Cpriority%2Cbug_severity&v7=--&f10=product&f20=CP&v18=Firefox&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other&o10=equals&f13=OP&v4=Core%2CFirefox%2CDevTools%2CToolkit&j_top=OR&chfieldfrom=-60d&v19=Disability%20Access&v2=access&o11=equals&f3=cf_accessibility_severity&f15=component&list_id=16594388&o18=equals&v10=Core&f16=CP&f9=OP&f7=bug_severity&f6=OP&f14=product&v11=Disability%20Access%20APIs&o2=casesubstring&o19=equals&o4=anyexact New untriaged Bugs in Gecko and Firefox Desktop] | * [https://bugzilla.mozilla.org/buglist.cgi?f8=OP&o14=equals&f22=CP&v15=Accessibility%20Tools&f12=CP&bug_type=defect&v3=---&chfield=%5BBug%20creation%5D&f4=product&f1=OP&f19=component&f2=keywords&f18=product&f17=OP&o7=equals&query_format=advanced&f11=component&f21=CP&j8=OR&o3=equals&o15=equals&v14=DevTools&resolution=---&f5=CP&columnlist=bug_type%2Cshort_desc%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cchangeddate%2Cstatus_whiteboard%2Ckeywords%2Cpriority%2Cbug_severity&v7=--&f10=product&f20=CP&v18=Firefox&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other&o10=equals&f13=OP&v4=Core%2CFirefox%2CDevTools%2CToolkit%2CFirefox%20Enterprise&j_top=OR&chfieldfrom=-60d&v19=Disability%20Access&v2=access&o11=equals&f3=cf_accessibility_severity&f15=component&list_id=16594388&o18=equals&v10=Core&f16=CP&f9=OP&f7=bug_severity&f6=OP&f14=product&v11=Disability%20Access%20APIs&o2=casesubstring&o19=equals&o4=anyexact New untriaged Bugs in Gecko and Firefox Desktop] | ||
* [https://bugzilla.mozilla.org/buglist.cgi?o14=equals&f14=product&o7=equals&f7=bug_severity&j8=OR&v3=---&f6=OP&f12=CP&f20=CP&f11=component&o11=equals&f1=OP&v4=Core%2CFirefox%2CDevTools%2CToolkit&v2=access&chfieldfrom=-3000d&chfield=%5BBug%20creation%5D&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other&o18=equals&f18=product&v15=Accessibility%20Tools&query_format=advanced&f8=OP&o19=equals&v10=Core&f19=component&bug_type=defect&o3=equals&f3=cf_accessibility_severity&list_id=16594594&f16=CP&v14=DevTools&j_top=OR&v7=--&f13=OP&v11=Disability%20Access%20APIs&f17=OP&v18=Firefox&resolution=---&o4=anyexact&o2=casesubstring&f4=product&f2=keywords&f9=OP&f21=CP&v19=Disability%20Access&f5=CP&f22=CP&f10=product&o10=equals&columnlist=bug_type%2Cshort_desc%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cchangeddate%2Cstatus_whiteboard%2Ckeywords%2Cpriority%2Cbug_severity&o15=equals&f15=component Older untriaged Bugs in Gecko and Firefox Desktop] | * [https://bugzilla.mozilla.org/buglist.cgi?o14=equals&f14=product&o7=equals&f7=bug_severity&j8=OR&v3=---&f6=OP&f12=CP&f20=CP&f11=component&o11=equals&f1=OP&v4=Core%2CFirefox%2CDevTools%2CToolkit%2CFirefox%20Enterprise&v2=access&chfieldfrom=-3000d&chfield=%5BBug%20creation%5D&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other&o18=equals&f18=product&v15=Accessibility%20Tools&query_format=advanced&f8=OP&o19=equals&v10=Core&f19=component&bug_type=defect&o3=equals&f3=cf_accessibility_severity&list_id=16594594&f16=CP&v14=DevTools&j_top=OR&v7=--&f13=OP&v11=Disability%20Access%20APIs&f17=OP&v18=Firefox&resolution=---&o4=anyexact&o2=casesubstring&f4=product&f2=keywords&f9=OP&f21=CP&v19=Disability%20Access&f5=CP&f22=CP&f10=product&o10=equals&columnlist=bug_type%2Cshort_desc%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cchangeddate%2Cstatus_whiteboard%2Ckeywords%2Cpriority%2Cbug_severity&o15=equals&f15=component Older untriaged Bugs in Gecko and Firefox Desktop] | ||
* [https://bugzilla.mozilla.org/buglist.cgi? | * [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&f17=CP&o20=notequals&f6=op_sys&f10=component&o15=anywords&f12=CP&o3=anyexact&j14=OR&f23=CP&f21=CP&f1=OP&o11=isempty&f13=OP&f2=OP&f11=bug_severity&j8=OR&v4=iOS&f15=keywords&v16=%5Ba11y%5D%2CTalkback&f3=product&f22=CP&f20=component&f18=OP&f7=CP&o6=equals&o10=equals&v20=Disability%20Access%20APIs&f19=cf_accessibility_severity&v3=Fenix%2CFocus%2CGeckoView&f16=short_desc&v15=access&list_id=17395975&f4=component&j1=OR&f5=CP&f14=OP&f9=OP&o4=nowords&query_format=advanced&f8=OP&o16=anywords&v10=Disability%20Access%20APIs&v6=Android&o19=isempty Untriaged bugs in Firefox for Android] | ||
* [https://github.com/mozilla-mobile/firefox-ios/issues?q=is%3Aopen+is%3Aissue+label%3Aaccess+-label%3Aaccess-s1+-label%3Aaccess-s2+-label%3Aaccess-s3+-label%3Aaccess-s4 Untriaged bugs in Firefox for iOS] | * [https://github.com/mozilla-mobile/firefox-ios/issues?q=is%3Aopen+is%3Aissue+label%3Aaccess+-label%3Aaccess-s1+-label%3Aaccess-s2+-label%3Aaccess-s3+-label%3Aaccess-s4 Untriaged bugs in Firefox for iOS] | ||
| Line 13: | Line 13: | ||
* <code>s1</code>: '''Accessibility of the entire product is broken.''' Examples include a critical piece of the browser's functionality like the URLbar not working. These bugs represent catastrophic failures and should be rare. | * <code>s1</code>: '''Accessibility of the entire product is broken.''' Examples include a critical piece of the browser's functionality like the URLbar not working. These bugs represent catastrophic failures and should be rare. | ||
* <code>s2</code>: '''Feature completely unavailable/inaccessible.''' 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) 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, etc. These bugs should absolutely block a feature from shipping to our stable release audience. | * <code>s2</code>: '''Feature completely unavailable/inaccessible.''' 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) that make a feature not discoverable/actionable by users with low vision, UI does not adapt to HCM at all, or adapts in a way that makes it unusable such as having a foreground and background color that are the same, UI that disappears or becomes otherwise inaccessible with large zoom factors, touch targets below WCAG recommendations, etc. These bugs should absolutely block a feature from shipping to our stable release audience. | ||
* <code>s3</code>: '''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, touch targets under mobile platform recommendations, 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. | * <code>s3</code>: '''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, UI adapts to HCM and is visible but may not use semantic colors correctly for some themes (i.e. it is using a `ButtonText` system color on `Canvas` background), which may result in low visibility, touch targets under mobile platform recommendations, 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. | ||
* <code>s4</code>: '''Feature available with minor defects.''' Examples include minor overlapping of the control borders while on HCM, technically compliant with WCAG patterns that could be improved to be more delightful and efficient to use, etc. These bugs should be fixed but probably do not block a feature from shipping to our release audience. This is the backlog. | * <code>s4</code>: '''Feature available with minor defects.''' Examples include minor overlapping of the control borders while on HCM, UI that adapts to HCM and is visible but may have minor defects such as incorrect border sizing, or focus ring that slightly overlaps other controls but doesn't render them unusable, technically compliant with WCAG patterns that could be improved to be more delightful and efficient to use, etc. These bugs should be fixed but probably do not block a feature from shipping to our release audience. This is the backlog. | ||
Firefox for iOS uses GitHub instead of Bugzilla, but a similar triage process is used. The access label is used to indicate accessibility impact and the need for accessibility triage. During triage, the <code>access-s1</code>, <code>access-s2</code>, <code>access-s3</code> and <code>access-s4</code> labels are used in the same way as the Accessibility Severity values described above. | Firefox for iOS uses GitHub instead of Bugzilla, but a similar triage process is used. The access label is used to indicate accessibility impact and the need for accessibility triage. During triage, the <code>access-s1</code>, <code>access-s2</code>, <code>access-s3</code> and <code>access-s4</code> labels are used in the same way as the Accessibility Severity values described above. | ||
| Line 30: | Line 30: | ||
Sometimes, accessibility bugs in other components are mistakenly placed in the Firefox: Disability Access component. Generally, most bugs here should be moved to the component where the bug resides. For example, an accessibility bug in the Firefox address bar should be moved to Firefox: Address Bar. When a bug is moved, its priority and severity should be cleared and it should then be triaged according to [[#Triaging Firefox and Gecko feature defects]] above. The Firefox: Disability Access component should only be used for accessibility bugs that absolutely do not fit into any other component. | Sometimes, accessibility bugs in other components are mistakenly placed in the Firefox: Disability Access component. Generally, most bugs here should be moved to the component where the bug resides. For example, an accessibility bug in the Firefox address bar should be moved to Firefox: Address Bar. When a bug is moved, its priority and severity should be cleared and it should then be triaged according to [[#Triaging Firefox and Gecko feature defects]] above. The Firefox: Disability Access component should only be used for accessibility bugs that absolutely do not fit into any other component. | ||
== Triaging incoming accessibility review requests == | |||
The Firefox Accessibility Engineering Team encourages all Mozilla teams to request accessibility reviews for designs, code, and features, following our [https://firefox-source-docs.mozilla.org/bug-mgmt/processes/accessibility-review.html Accessibility Review documentation]. | |||
To help manage volume and shifting priorities, we use an [https://docs.google.com/document/d/1KIABHvkuKgn9w-6qFYu6pnAuYFqgKQ2hA2Owoj2v8JU/edit?usp=sharing Accessibility Reviews Prioritization Rubric] to triage requests based on factors like product impact, user risk, and project timelines. Reviews are prioritized based on their priority category and team availability, so turnaround times may vary. '''We encourage early outreach and collaboration to help ensure accessibility is considered from the start.''' | |||