Audits, issues and statements

After an audit

What to do after an audit and what's included in the report.

You'll receive a report which includes accessibility and best practice issues that may affect users with disabilities.

It will tell you:

• where your product or website is failing to provide a good user experience, especially for people with disabilities
• which WCAG criteria you're failing to meet
• potential ways to fix issues. Some audit providers prioritise issues for you

Actions as a team

1. Review audit.
2. Prioritise issues.
3. Log issues in the issues and statements service.
4. Start to fix issues.
5. Update issues in the issues and statements service as they're fixed.
6. Request a retest of issues within the issues and statements service.
7. Add any unresolved issues to your accessibility statement.

Before your service goes live

Most of your accessibility issues should be resolved before users access your service.

Any high-impact issues should have been fixed and if any low-impact issues remain, you must provide a timeline in the statement for when they'll be resolved.

After your service goes live

You should incorporate budget for an accessibility audit every 12 months.

This will ensure that if you've made changes to your service, new patterns or components have been introduced, or you need to address potential user complaints or GDS monitoring findings, that budget is already in place.

If no change has been made to your service, you have resolved and re-tested previously identified issues, or the team have carried out sufficient internal testing, a new audit may not be needed.

The DesignOps team can review your service and help you decide if an audit is required. The team aim to respond within 5 working days.

arrow_circle_right Submit an audit request