Skip to content

Instantly share code, notes, and snippets.

@SteveBarnett
Last active October 15, 2023 22:09
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save SteveBarnett/b1f47456b3c72df43b39b0f89d7685c2 to your computer and use it in GitHub Desktop.
Save SteveBarnett/b1f47456b3c72df43b39b0f89d7685c2 to your computer and use it in GitHub Desktop.
Accessibility audit terminology: issue severity
  1. Is it Critical?
    • Does it stop someone doing a thing? Can they do the thing some other way?
  2. If it's not Critical, how bad is it?
    • Is it part the core task flow?
    • Will the user encounter the error frequently?
    • How much will it slow them down?
    • Is the error in lots of places?
  • Critical - The issue stops users from accessing content or completing a task. It does not have a workaround.
  • High - The issue causes serious problems or major inconvenience to users. It has a workaround but it is difficult and not obvious.
  • Medium - The issue causes problems or frustrations for users. It has a workaround.
  • Low - The issue causes inconvenience or irritation to users. It may not need a workaround.

We also use Best Practice to note issues that aren't covered by WCAG, and fall more under usability than accessibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment