[A11y Audit]: Use Cases

[st0nebreaker]

Pages:

• /use-cases *index
• /use-cases/code-security
• /use-cases/onboarding
• /use-cases/incident-response
• /use-cases/code-reuse
• /use-cases/code-health

User Journey:

• Navigate to the Use Case index page.
• Navigate to each child page.
• Click hero back button.
• All links can be clicked through.
• All carousels can be experienced.
• All imagery is accessible.
• Any video can pause or play, and has CC.
• Any form can be completed.
• Any tooltip is accessible through keyboard or screen reader.

How to audit

Follow the instructions here: Auditing a user journey

Video example here.

1. Navigate user journey using only the keyboard
2. Navigate user journey without looking at your screen, using the screen reader.
3. Navigate user journey using a viewport with a width of 320px.
4. Run an ARC Toolkit test on the webpage for any changing state.
5. If the issue is trivial & you have time, feel free to address the bug now. Otherwise, raise any larger bugs using the accessibility issue template.

Note: The Front End Platform team is planning on arranging thorough third-party audit in the future, so our focus here is just to find the majority of accessibility issues. Don't worry if you feel you haven't found 100% of potential issues, it is better to focus on the core essentials to complete the journey rather than spending lots of time going through every possible problem.

Any other questions?

See the audit FAQ - add your question if it isn't there already!