Website Accessibility Audit Manchester
An accessibility audit checks whether disabled people can use your website, measured against WCAG 2.2 level AA. Our Manchester team combines automated scans with hands-on keyboard and screen reader testing, then gives you a prioritised list of fixes. It suits businesses, charities and public bodies who want a clear picture before they start changing things.
- Since 2003trading in Manchester
- 20,000+UK businesses helped
- Collect M8Unit 3, 116 Bury New Road
- A personchecks every file
Fix and extend
Every job is a fixed quote, agreed in writing before any work starts. No obligation.
- Custom Script InstallationWEB 101Quote
- Plugin and Theme CustomisationWEB 102Quote
- Website Bug FixesWEB 103Quote
- Hosting and MigrationWEB 104Quote
What the audit checks and why it matters
The Web Content Accessibility Guidelines (WCAG) are the published standard most UK organisations work to. Level AA covers text contrast, keyboard access, form labels, visible focus and how content is announced by screen readers. WCAG 2.2 added criteria such as a minimum target size for buttons and links and a rule that the focused element must not be hidden behind sticky headers.
Automated tools find a useful share of problems, such as missing alt text or low contrast, but many issues only show up when a person tests. A scanner cannot judge whether alt text is accurate or a menu traps keyboard users.
There is a legal side too. The Equality Act 2010 expects service providers to make reasonable adjustments for disabled people, and public sector bodies have specific website accessibility regulations that include publishing an accessibility statement. We work to published guidance, but this is not legal advice, so take advice on your own obligations.
Organisations that book an audit
Audits are most useful before a redesign, after a complaint or when a contract asks for evidence of accessibility.
- Councils, schools and other public sector bodies that must publish an accessibility statement.
- Charities whose service users include disabled and older people.
- Suppliers bidding for contracts that ask about WCAG.
- Online shops where a checkout barrier means lost orders.
- Businesses planning a website redesign who want problems designed out early.
How the audit runs
Agree the page sample
We pick representative templates and key tasks, such as the home page, a service page, a form and the checkout.
Automated scanning
Tools such as axe and WAVE flag contrast, missing labels, empty links and structural errors across the sample.
Keyboard and visual checks
We tab through every task, check focus states and zoom to 400 per cent to test reflow.
Screen reader testing
We test with NVDA on Windows and VoiceOver on Apple devices to hear how headings, forms and errors are announced.
Report and walkthrough
You get findings ranked by impact, each linked to the WCAG criterion it fails, and we talk your team through them.
What the report gives you
- A list of issues mapped to WCAG 2.2 success criteria.
- Each issue ranked by impact on users and effort to fix.
- Screenshots and page locations so developers can find each problem.
- Plain-English fix guidance for designers, developers and editors.
- A draft accessibility statement structure if you need one.
Barriers we find on most sites
These failures appear in nearly every audit.
- Low colour contrast: WCAG asks for at least 4.5 to 1 for normal text and 3 to 1 for large text.
- Missing or unhelpful alt text: images with no description, or file names read aloud.
- Unlabelled form fields: placeholder text used in place of a proper label, which disappears once someone starts typing.
- Invisible focus: themes that remove the focus outline, so keyboard users cannot see where they are.
- Skipped heading levels: headings chosen for size, not structure, which breaks screen reader navigation.
- Vague link text: rows of “click here” links that make no sense out of context. Good website copywriting fixes this at source.
Frequently asked questions
Is an automated accessibility checker enough on its own?
No. Automated tools are fast and catch real issues, but they cannot judge meaning, order or usability. Keyboard traps, confusing error messages and poor alt text need a person. We use tools to cover breadth and manual testing for depth.
Will the audit make my website legally compliant?
An audit shows where your site meets WCAG 2.2 AA and where it does not. Compliance depends on fixing the issues and keeping new content accessible. We work to published guidance, but we are not lawyers, so take legal advice on your obligations.
Can you fix the problems as well as report them?
Yes. Many clients ask us to work through the list afterwards, starting with the highest-impact issues. Some are template changes made once, others are content changes your editors can handle.
Do accessibility overlay widgets solve the problem?
We do not recommend relying on them. Overlays add a toolbar but usually leave the underlying code unchanged, so screen reader and keyboard users still meet the same barriers. Fixing the site itself is the approach WCAG is written around.
How often should a site be re-audited?
After any redesign or major new feature, and periodically if your team publishes content often. New pages, images and forms can introduce fresh issues, so a lighter recheck of key tasks works well between full audits.
Related services
- Web design Manchester: our hub for building and improving websites.
- Website redesign: rebuilding with accessibility planned in.
- Image optimisation: alt text and image handling alongside speed.
- Website bug fixing: developer fixes for template-level barriers.
To scope an audit, send us your site address through the accessibility audit enquiry, call 0161 315 1151 or message the team on WhatsApp at 07737 902425.
Ready to get started?
Tell us what you need and we'll come back with an honest, fixed-price quote — no obligation.