Accessibility acceptance criteria
This is a collection of accessibility acceptance criteria. The criteria are unsorted at the moment.
- Work without JavaScript
- Present content in a logical DOM order
- Use a default text size that is comfortable to read
- Have a colour contrast of at least 4.5:1 between text and the background
- Use valid code
- Have a visible text label
- Be focusable with the keyboard
- Be focusable with screen reader shortcuts
- be focusable with voice
- Be large enough to tap with one finger
- Be actionable with a keyboard
- Be actionable with touch
- Be actionable with a mouse
- Be actionable with voice
- Change appearance when focused
- Change in appearance when hovered
- Change in appearance when touched
- Indicate when content is expanded
- Indicate when content is collapsed
- Indicate the relationship between the control and the controlled content
- Hide content from all users
- Indicate that it can be edited
- Indicate there is a pre-filled value
- Indicate that auto-complete is available
- Provide hints to aid interaction
- Indicate when matches are available
- Indicate how many matches are available
- Indicate when a match is pre-selected
- Return focus to the edit field when a match is selected
- Indicate that the dialogue has opened
- Constrain keyboard focus within the dialogue
- Return focus to dialogue trigger control when the dialogue closes
- Be closed with a keyboard
- Be closed with voice
- Be closed with touch
- Be closed with a mouse
- Prevent interaction with underlying content
- Remain visible regardless of scrolling, screen size or orientation changes
- Indicate character limit
- Indicate current character count
- Be understandable
- Have a short alternative description
- Have a long alternative description
- Enable identification of high-level content blocks
- Enable screen reader navigation between high-level content blocks
- Have audio description
- Have closed captions
- Have a transcript
- Have a tab order that matches the visual order of content
- Not depend on colour to communicate information
- Not auto-play on-load
- Not trap keyboard focus
- Not timeout unless as a security precaution
- Enable time limits to be extended
- Not flash or blink
- Enable navigation to the main content area with a keyboard
- Enable navigation to the main content area with a screen reader
- Correctly identify the written language of the document
- Correctly identify the written language of chunks of content
- Not change context on-focus
- Not change context on-change
- Have an accessible name
- Have an accessible description
- Move keyboard focus to the intended destination
- Be visually distinct from other content on the page
- Use the appropriate markup for the purpose
- Be a landmark region
- Indicate how many items in the collection
- Indicate the order
- Be presentational and ignored by screen readers
- Have a visible caption
- Convey the level
- Be part of a correct hierarchy
- Indicate it is a navigation block
- Indicate it is complementary content
- Indicate it is the main content area
- Indicate it is a search facility
- Indicate it is header information for the page
- Indicate it is footer information for the page