Accessibility issues usually split cleanly between two groups of people. Handing them the right list saves a lot of back and forth.
Content issues
These belong to whoever writes and publishes pages. They do not require a developer.
- Images with missing or unhelpful alternative text
- Link text that says "click here" or "read more" with no context
- Headings used for visual styling rather than structure
- Tables with no headers
- Documents published as PDFs with no accessible version
Code and design issues
These belong to whoever builds and maintains the site.
- Contrast failures in colours and typography
- Form fields with no labels
- Buttons and controls that cannot be reached by keyboard
- Missing page language
- Broken or missing ARIA attributes
How to split the list
Filter by issue type in the results page and use Copy All on each group to get a clean list to paste into a ticket or a spreadsheet. One ticket per unique issue type rather than one per page keeps things manageable.
A note on forms
Forms often involve both groups. The label text is a content decision. Whether the label is actually connected to the field is a code decision. Worth being clear about which is which when you hand it over.