Accessibility/Triage: Difference between revisions

Accessibility/Triage (view source)

Revision as of 01:25, 19 October 2023

603 bytes added , 19 October 2023

Add note about moving most bugs out of Firefox: Disability Access.

Jteh

Confirmed users

32

edits

Revision as of 00:47, 14 September 2023 (view source) Jteh (talk \| contribs) (Update for new Accessibility Severity field in Bugzilla. Clarify triage for components owned by the a11y team. Update triage guidance for Android and iOS. Remove a11y review triage, which doesn't reflect reality.) ← Older edit		Revision as of 01:25, 19 October 2023 (view source) Jteh (talk \| contribs) (Add note about moving most bugs out of Firefox: Disability Access.) Newer edit →
Line 26:		Line 26:

	We set severity and priority on these bugs directly using the Severity and Priority fields as described in [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html Firefox's bug handling guide]. The access keyword should not be set on these bugs, since they already exist in a component specific to accessibility. During triage, the access keyword should be removed from these bugs if it has accidentally been set previously, as this causes problems for our triage queries.		We set severity and priority on these bugs directly using the Severity and Priority fields as described in [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html Firefox's bug handling guide]. The access keyword should not be set on these bugs, since they already exist in a component specific to accessibility. During triage, the access keyword should be removed from these bugs if it has accidentally been set previously, as this causes problems for our triage queries.

			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.