Issue Priorities

Issues found via OATMEAL tests are given a Priority Level from P1 (most severe) to P4 (least severe).

P1 Issues

A barrier that makes completion of a task impossible for some users.

Examples that can create a P1 issue

  • Keyboard focus trapped

    • Why: User cannot proceed through page

  • Button not operable with keyboard alone

    • Why: User cannot active call to action (e.g "Buy it Now")

P2 Issues

A barrier that makes completion of a task difficult for some users.

Examples that can create a P2 issue

  • Pinch-to-zoom disabled

    • Workaround: User can use other magnifying software or device

  • Form field lacking a visible or programmatic label

    • Workaround: User can explore adjacent elements to determine context

  • Color contrast below the contrast minimum

    • Workaround: User can provide a custom stylesheet

  • Focus indicator missing on element, but present on adjacent elements

    • Workaround: User can determine focus by navigating through surrounding elements

  • Keyboard focus does not go where the user expects

    • User has to discover how to get focus where they expect it to be

P3 Issues

A barrier that makes completion of a task tedious or annoying for some users.

Examples that can create a P3 issue

  • Widget interaction different from the established pattern

    • Annoying: User has to learn multiple of the same type of widget and then figure out which they're using each time

  • Page missing "Skip to Main"

    • Tedious and Annoying: User has to navigate through all repeated header elements on every page

  • Redundant labeling on a button, link, or input

    • Tedious: User has to listen through extraneous information

P4 Issues

A non-barrier that technically fails accessibility guidelines.

Examples that can create a P4 issue

  • Non-unique IDs on unreferenced elements

  • Duplicated attributes with the same value