> For the complete documentation index, see [llms.txt](https://ebay.gitbook.io/oatmeal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ebay.gitbook.io/oatmeal/priorities.md).

# Issue Priorities

## 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 backwards or forwards through page
* Interactive element not operable with keyboard alone
  * Why: User cannot complete a primary task (e.g "Buy it Now",  "Submit Form")
* Element with misleading accessible label
  * Why: User might make an action they did not intend, with dangerous consequences (e.g. a "Submit Payment" button programmatically labelled as "Review Payment")

## 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 must use non-standard magnifying software to resize text
* Form field lacking a visible or programmatic label
  * Workaround: User must explore adjacent elements to determine context
* Color contrast below the contrast minimum
  * Workaround: User must provide a custom stylesheet to make text/graphics legible
* Document missing semantic heading structure
  * Workaround: User must read entire page content to form mental model

## P3 Issues

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

### Examples that can create a P3 issue

* Keyboard focus indicator missing on element, but present on adjacent elements
  * Workaround: User can determine focus by navigating through surrounding elements
* Keyboard focus indicator does not go where the user expects
  * Workaround: user has to discover how to get focus where they expect it to be
* Widget interaction different from the established pattern
  * Workaround: 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"
  * Workaround: User has to navigate through all repeated header elements on every page
* Redundant labeling on a button, link, or input
  * Workaround: 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
* Duplicate attributes with identical value
* Non-escaped attribute values

## About

Last Updated: 2022 March 7th


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ebay.gitbook.io/oatmeal/priorities.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.