Frontend60-90 min
Frontend Accessibility Audit
Use semantic HTML, keyboard testing, visible focus, labels, landmarks, and automated checks to improve usability for more users.
HTMLARIAaxeReact
Prerequisites
- A representative page or workflow to audit.
- Keyboard-only testing access.
- Browser extension or test runner for accessibility checks.
1
Plan the implementation
Start by choosing the exact page, route, API, or deployment surface you want to improve. A narrow target makes the implementation measurable and easier to verify.
- Write down the current behavior and the user-facing problem it creates.
- Pick one measurable success signal such as bundle size, latency, error rate, security coverage, or UI responsiveness.
- Identify the files, routes, providers, and environment variables involved.
- Create a rollback note before changing production-sensitive configuration.
2
Set up the required tools
Install or configure only the tools needed for this implementation. Keep config close to the feature so future developers can find the moving parts quickly.
Implementation snippet
npm install -D @axe-core/playwrightChecklist
- Dependencies are added to the correct workspace package.
- Environment variables are documented in `.env.example` when needed.
- Local development still starts without production-only secrets.
- The change is small enough to review in one pull request.
3
Implement the core pattern
- Navigate the workflow using only the keyboard.
- Check that every input has a real label.
- Verify buttons and links use the correct semantic element.
- Add visible focus states for interactive controls.
- Run automated checks and manually verify screen-reader-sensitive areas.
Implementation snippet
<label htmlFor="email">Email</label>
<input id="email" name="email" type="email" autoComplete="email" />
<button type="button" aria-label="Close dialog">x</button>4
Handle edge cases
Checklist
- Tab order follows the visual order.
- Dialogs trap focus and return focus on close.
- Color contrast passes for text and controls.
- Icon-only buttons have accessible names.
5
Verify before production
- Run the app locally and test the normal success path.
- Test one failure path, one empty state, and one slow-network or retry path.
- Run the project build and any related unit or integration tests.
- Check browser console, server logs, and network responses for hidden warnings.
- Document the final behavior, commands used, and any follow-up work.