19
edits
Accessibility/Triage: Difference between revisions
added information for the Triaging incoming accessibility review requests and the link to the Review Prioritization Rubric
(→Search Queries: updated the Android search query to exclude "Disability Access APIs" bugs when their "severity" is set (to not to check for Accessibility Severity there)) |
(added information for the Triaging incoming accessibility review requests and the link to the Review Prioritization Rubric) |
||
| 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 still encourage early outreach and collaboration to help ensure accessibility is considered from the start. | |||