diff --git a/_guide/defect-priority.md b/_guide/defect-priority.md new file mode 100644 index 00000000..f0e79324 --- /dev/null +++ b/_guide/defect-priority.md @@ -0,0 +1,148 @@ +--- +layout: guide +title: Accessibility bug classification +description: Guidance for prioritizing accessibility bugs based on degree of user impact on top tasks +excerpt: +sidenav: docs +categories: + - Accessibility +roles: + - Developer + - Product manager + - Project manager + - UX designer +--- + +CivicActions teams use this guidance to prioritize accessibility issues based on the degree of content interference caused by a WCAG success criterion failure. We [treat accessibility issues as bugs](https://github.com/readme/guides/fix-accessibility-bugs), and have adapted priority definitions from [Deque's issue impact classification](https://github.com/dequelabs/axe-core/blob/develop/doc/issue_impact.md). + +Note that: +* The list is illustrative, not exhaustive, and +* A failure can belong to more than one level depending on how severely it impacts content access. + +Teams may evaluate an issue further with respect to its impact on specific content, functionality, or usability. Reasons for adjustment should be included in the ticket description, and when new patterns or examples are identified they should be considered for inclusion in the table. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Access failureIssue priorityAction
Page-level interference (Single A criteria) + + Highest user impact +
    +
  • Dire, resolve immediately
    • +
  • Forces user to abandon essential workflow
    • +
  • Users with disabilities fundamentally blocked
    • +
  • Creates immediate organizational risk
    • +
  • Everything else can wait for this
    • +
+		Do now
+ Bypass release cycle +
Primary component failure + + High user impact +
    +
  • Significantly degrades essential workflow
    • +
  • Users with disabilities substantially blocked
    • +
  • Significant frustration for AT users
    • +
  • The issue has been around a long time
    • +
  • Other work can wait for this
    • +
+ 		Do next
+ Address in next release +
Component interference + + Medium user impact +
    +
  • Degrades non-critical workflows for AT users
    • +
  • Users with disabilities are slowed down
    • +
  • Some frustration for AT users is likely
    • +
  • Acceptable short-term workaround exists
    • +
  • Low priority issue that has been around a while
    • +
+ 		Do soon
+ Address this quarter +
Page or component degradation + + Low user impact +
    +
  • Does not substantially degrade a workflow
    • +
  • Has a simple workaround
    • +
  • Hinders compliance
    • +
  • Annoyance bug
    • +
  • If the affected component is not actively used
    • +
+ 		Do later
+ Address when doing related work +
Missing best practicesLowest user impact +
    +
  • No significant user value to fix
    • +
  • Only in unsupported browser or component
    • +
+ 		Do as time allows
+ +