Manual UK website accessibility audits for PSBAR and the Equality Act 2010, led by founder Mohammad Shadab Saifi (CPACC, WAS, CPWA, 10+ years). We test key journeys with keyboard and NVDA, JAWS, VoiceOver and TalkBack, map findings to WCAG 2.2 AA, and deliver a developer-ready report. Fixed $500 Quick or $2,000 Complete. New to UK rules? Start with a free 30-minute call.
Start Here
New to PSBAR or the Equality Act, preparing for a Government Digital Service check, or need a quote? Start with the free 30-minute call. Ready for a written WCAG report? Order the $500 Quick Audit (up to 5 templates) or the $2,000 Complete Audit for larger sites. Already have findings to walk through with your developer? Book the $100 technical hour.
get in touch
Tell us what you’re working on and where you need support. Our accessibility specialists can help with audits, remediation, VPAT/ACR, accessible development, and ongoing compliance.
Free 30-minute consultation (opens in new tab)
Free 30-minute call: talk through where you stand, scope a project or get a quote.
Need technical answers now? Book the $100 one-hour consultation to walk through an audit, talk with a developer or review your site live.
Indicates a required field.
Your information is kept private and never shared with third parties.
Our UK accessibility audit services start with which law applies to you. Public sector bodies, including central and local government and some publicly funded charities, must meet the Public Sector Bodies Accessibility Regulations 2018 (PSBAR): WCAG 2.2 AA on websites, intranets, extranets and public mobile apps, plus a published accessibility statement. Every UK service provider, public or private, also has the Equality Act 2010 duty to make reasonable adjustments (the Disability Discrimination Act 1995 in Northern Ireland).
We test your key journeys by hand with a keyboard, NVDA, JAWS, VoiceOver and TalkBack, and we sort out what the regulations exempt before testing, so your fix budget goes where the law applies. Public sector team? Request a government accessibility audit, or see what you get in our sample audit report.
Central government, councils and other public bodies, plus charities that are mostly publicly funded or provide essential services, tested against WCAG 2.2 AA.
Apps a public body builds for use by the public must be accessible and carry their own accessibility statement. Apps only for staff or students are not covered.
Internal sites that staff and partners use are covered too. Ones published before 23 September 2019 must be made accessible when they get a major revision.
We check your statement against what we find, including failures, exemptions and any disproportionate burden claim. GDS can publish the name of a body whose statement is missing or wrong.
Documents from before 23 September 2018, video from before 23 September 2020, live video, maps and third-party content you don't pay for or control are exempt. Forms needed to use a service are not.
Shops, banks, SaaS and other businesses must make reasonable adjustments under the Equality Act 2010. We use WCAG 2.2 AA as the practical benchmark for your website and app.
UK website accessibility law has two layers. The Equality Act 2010 (the Disability Discrimination Act 1995 in Northern Ireland) requires every service provider, public or private, to make reasonable adjustments for disabled people, and that duty covers websites and apps. The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, known as PSBAR, go further for public sector bodies: GOV.UK guidance says a site or app meets them if it meets WCAG 2.2 AA and publishes an accessibility statement. The Government Digital Service monitors a sample of public sector sites each year, and the Equality and Human Rights Commission (the Equality Commission for Northern Ireland in Northern Ireland) enforces. A UK accessibility compliance audit tests your site against WCAG 2.2 AA by hand and gives you evidence for both laws, from $500.
Think of this audit like a legal and technical health check for your website or product. Instead of guessing whether you meet local accessibility law, we test against the exact standard that law references and show you precisely where you stand.
Meeting the right legal standard protects your organization from enforcement risk and makes your product usable by more people.
Sections 20 and 29 of the Equality Act 2010 require service providers, including private businesses, to make reasonable adjustments for disabled people. The duty is anticipatory (Schedule 2): you plan for disabled people generally instead of waiting for a complaint, and that includes your website and app.
GOV.UK guidance says a public sector website or app meets the 2018 regulations if it meets WCAG 2.2 AA and publishes an accessibility statement. GDS began monitoring the new WCAG 2.2 criteria in October 2024.
The Equality and Human Rights Commission (England, Scotland and Wales) and the Equality Commission for Northern Ireland enforce the accessibility requirement and can use investigations, unlawful act notices and court action. Individuals can also bring Equality Act claims.
UK businesses that sell covered products or services, such as ecommerce, consumer banking or e-books, to consumers in the EU must also meet the European Accessibility Act, which has applied since June 28, 2025.
Public sector bodies must publish an accessibility statement and review it regularly. When GDS finds a statement missing or incorrect, the government can publish the organisation's name and a copy of the decision.
Automated tools catch only part of WCAG. The WebAIM Million 2026 found detectable failures on 95.9% of home pages, and keyboard, focus and screen reader problems need manual testing to find and fix.
We audit public websites, authenticated applications, SaaS platforms, mobile apps, documents, and design systems.
Marketing, ecommerce, healthcare, government, education, nonprofit, and service organizations use accessibility audits to make essential public content available to more people.
Product teams use audits to validate complex workflows, reduce accessibility debt, improve component libraries, and prepare for enterprise accessibility reviews.
Legal, compliance, procurement, and sales teams use audit evidence to answer buyer questions, support VPAT work, and document remediation commitments.
Evaluate public websites against WCAG 2.2 AA using manual testing, automated scanning, keyboard-only navigation, and assistive technologies.
Review authenticated user journeys, dashboards, complex forms, data tables, notifications, custom widgets, and enterprise workflows.
Test native and hybrid applications using VoiceOver, TalkBack, keyboard alternatives, zoom, orientation changes, touch target review, and gesture accessibility checks.
Assess PDFs and office documents for tagging, reading order, alternative text, bookmarks, form fields, headings, tables, and screen reader compatibility.
Identify accessibility issues in Figma files, design systems, and component specs before development begins, reducing rework and improving handoff quality.
Evaluate products and prepare accessibility documentation that supports enterprise and government procurement conversations.
Each issue is mapped to user impact, the relevant standard, severity, affected users, and practical remediation guidance.
Missing or inaccurate alternative text prevents screen reader users from understanding meaningful images, icons, charts, infographics, product photos, and linked graphics. We identify images that need concise alternatives, images that should be marked decorative, and complex visuals that need longer explanations.
Many users navigate with a keyboard, switch device, voice control, or assistive technology that relies on keyboard behavior. We test focus order, skip links, menus, modals, tabs, accordions, custom widgets, and form flows without a mouse.
Low contrast can make text, buttons, icons, form controls, and charts difficult or impossible to perceive. We evaluate contrast for normal text, large text, UI components, focus indicators, disabled states, links, and error messages.
Forms often block users when labels, instructions, required indicators, validation messages, and error handling are not accessible. We test forms with keyboard navigation and screen readers to confirm users can complete and submit successfully.
Headings, lists, landmarks, tables, and reading order help assistive technology users understand a page quickly. We identify skipped heading levels, missing landmarks, and reading-order mismatches.
Modern applications often update content without refreshing the page. We test status messages, ARIA live regions, notifications, and single-page app transitions to confirm important changes are announced correctly.
Public sector documents published since September 23, 2018 must be accessible, and older documents are covered too when people need them to use a service. We check tagging, reading order, form fields, headings and tables in PDFs and office files, and test them with NVDA.
Sign-in and verification steps lock people out when they rely on memory tests, puzzles or short time limits. We test WCAG 2.2 accessible authentication (3.3.8), timing adjustable (2.2.1) and error messages on login, payment and application forms.
| Feature | Automated Testing | Manual Testing |
|---|---|---|
| Speed | Fast (minutes) | Slower (days) |
| Cost | Low | Higher, but more accurate |
| Manual WCAG Review | No | Yes |
| Keyboard Navigation | Limited | Complete |
| Screen Reader Compatibility | No | Yes |
| Logical Reading Order | No | Yes |
| Meaningful Alternative Text | No | Yes |
| Form Usability | Partial | Yes |
| Overall User Experience | No | Yes |
A structured process gives your team clear findings, clear priorities, and a practical path to compliance.
We confirm whether PSBAR applies to you or only the Equality Act, whether any exemption or disproportionate burden claim is in play and whether you sell to EU consumers, then pick the templates and journeys people must complete, such as applying, paying, booking, checking out or contacting support.
We run automated tools across the defined scope to catch code-level issues quickly, giving us a baseline before manual review begins.
Certified specialists manually test keyboard navigation, focus order, forms, headings, and interactive components against WCAG success criteria.
We test with screen readers (NVDA, JAWS, VoiceOver, TalkBack), voice control, and switch access to confirm real-world usability, not just code compliance.
Findings are documented with severity, the WCAG 2.2 success criterion, screenshots and reproduction steps, then grouped into a prioritized remediation roadmap and mapped to the sections of a GOV.UK-style accessibility statement.
With the Complete Audit we retest the issues your team fixes to confirm they are resolved and no new barriers were introduced, then help you finish the accessibility statement draft.
The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 cover public sector websites, intranets, extranets and public-facing mobile apps. GOV.UK guidance treats WCAG 2.2 AA plus a published accessibility statement as meeting them. Some charities and public service broadcasters are exempt, and schools and nurseries are partly exempt.
Sections 20 and 29 require service providers, public and private, to make reasonable adjustments for disabled people, planned in advance for disabled people generally. The Act names no technical standard, so WCAG 2.2 AA is the practical benchmark for websites and apps.
The current W3C Recommendation, published in October 2023 and the standard GOV.UK guidance points public sector bodies to. It adds criteria such as focus not obscured, target size, dragging movements and accessible authentication. We test every page and journey in scope against it.
The European standard for accessible ICT. Under regulation 9 of the 2018 regulations, a public sector site that meets it is presumed to conform, and many UK public sector buyers cite it in tenders. Its web chapter mirrors WCAG, so our findings map to its clauses.
Public sector bodies must publish a statement in the GOV.UK format: compliance status, content that is not accessible and why, any disproportionate burden claim, how to report problems and the enforcement procedure. The Complete Audit includes a statement draft.
The Equality Act 2010 mostly does not extend to Northern Ireland. There, the Disability Discrimination Act 1995 sets the reasonable adjustment duty, and the Equality Commission for Northern Ireland enforces the public sector accessibility rules.
A clear summary of audit scope, key risks, priority themes, and recommended next steps for stakeholders.
A practical status snapshot that helps teams understand current accessibility maturity and remediation priorities.
Issue-by-issue findings with screenshots, affected URLs or screens, severity ratings, standard references, and reproduction steps.
Practical remediation guidance, code-level notes, component recommendations, and examples your developers can act on.
Findings organized to support a GOV.UK-style accessibility statement, VPAT and ACR documentation, and procurement or legal review.
With the Complete Audit, validation evidence after remediation showing which issues were fixed and what remains open.
Founder Mohammad Shadab Saifi (CPACC, WAS, CPWA, 10+ years) leads UK audits, remediation support, accessibility statements and product guidance for PSBAR and Equality Act work.
Reports are written for action. Developers receive clear reproduction steps, expected behavior, affected users, standard mapping, and remediation guidance.
One audit benchmarked to WCAG 2.2 AA gives UK teams evidence for PSBAR and the Equality Act, and maps to EN 301 549 for customers in the EU.
Audit scope is tailored to your product and priorities so your team receives useful findings without unnecessary reporting overhead.
Whether you are a public sector body preparing for a Government Digital Service check or a private business documenting Equality Act reasonable adjustments, our founder-led audit finds the real barriers in your key journeys and gives your team a prioritized, developer-ready roadmap. Start with the $500 Quick Audit, or ask for a free needs assessment and we will scope a $2,000 Complete Audit with a re-test and an accessibility statement draft. Not sure which UK rules apply yet? Book a free 30-minute call to talk through where you stand and get a quote. If you need hands-on technical answers now, such as reviewing audit findings with your developer, book the $100 one-hour technical consultation.
Start My $500 UK Accessibility AuditAnswers to common questions about UK Website Accessibility Audit Services (Equality Act & PSBAR).
For public sector bodies, effectively yes. The 2018 accessibility regulations (PSBAR) require public sector websites and apps to be accessible, and GOV.UK guidance says you meet them by meeting WCAG 2.2 Level AA and publishing an accessibility statement. The Equality Act 2010 does not name WCAG, but it requires reasonable adjustments, and WCAG 2.2 AA is the practical benchmark for showing a website or app is accessible.
PSBAR is the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. It applies to central and local government, NHS bodies, most universities and colleges, and charities that are mostly publicly funded or provide essential public services. Public service broadcasters are exempt, and schools and nurseries are partly exempt. Covered bodies must make websites, intranets, extranets and public-facing apps accessible and publish an accessibility statement.
PSBAR only binds public sector bodies. Private businesses are covered by the Equality Act 2010, which requires reasonable adjustments rather than a named technical standard, so WCAG 2.2 AA is the benchmark most businesses use to show they have made their website accessible. The duty is anticipatory, so you should not wait for a complaint. If you also sell to consumers in the EU, the European Accessibility Act may apply too; see our EAA guide and EU accessibility compliance audit.
A PSBAR accessibility statement must list any content that does not yet meet WCAG 2.2 AA, explain why, and describe the plan to fix it. It should also explain how users can report problems or ask for content in another format, link to the enforcement procedure, and record any “disproportionate burden” claim, where fully meeting the standard would cost too much relative to the organization’s size and resources. It must be kept up to date as issues are resolved. GOV.UK publishes a sample accessibility statement and guidance on publishing one.
The Government Digital Service (GDS) monitors compliance on behalf of the Minister for the Cabinet Office by testing a sample of public sector websites and apps each year (see its monitoring guidance and how GDS tests). GDS sends the organization a report of its findings, allows 12 weeks to fix issues and report back, then retests. Enforcement sits with the Equality and Human Rights Commission (EHRC) in England, Scotland and Wales and the Equality Commission for Northern Ireland (ECNI).
HalfAccessible publishes fixed prices: the $500 Quick Audit covers up to 5 page templates with a top-10 issues report, and the $2,000 Complete Audit covers up to 25 templates or key user flows with a retest of fixed issues, an accessibility statement draft and 90-day support. Not sure which fits? Start with a free 30-minute call to talk through where you stand and get a quote. If you already have findings and need a hands-on technical session with a developer, book the $100 one-hour consultation. See the pricing page for details.
We scope the templates and journeys that matter most, run automated scans, then test by hand with a keyboard and with NVDA, JAWS, VoiceOver and TalkBack against WCAG 2.2 AA. You get a report with each issue’s severity, WCAG success criterion, screenshots, reproduction steps and fix guidance, organised so it can feed your accessibility statement. See a sample audit report.
GOV.UK guidance now points public sector bodies to WCAG 2.2 AA, and GDS began monitoring the new WCAG 2.2 success criteria in October 2024. The regulations also presume conformity for sites that meet the harmonised European standard EN 301 549, whose current web chapter is based on WCAG 2.1. Because WCAG 2.2 includes all of WCAG 2.1 AA, testing to WCAG 2.2 AA covers both.
Yes, for public sector bodies. Public-facing mobile apps must be accessible and have their own accessibility statement. Documents such as PDFs published since September 23, 2018 must be accessible, and older ones are covered when people need them to use a service, such as an application form. Under the Equality Act, private businesses also need accessible documents and apps when customers rely on them. Our PDF document remediation service fixes the files we flag.
Often, yes. The European Accessibility Act has applied since June 28, 2025 to covered products and services offered to consumers in the EU, such as ecommerce, consumer banking, e-books and electronic communications, wherever the business is based. Microenterprises providing services are exempt. A WCAG 2.2 AA audit gives evidence for both UK law and the EAA.
No. Neither the 2018 regulations nor the Equality Act accept an overlay as proof of accessibility, and overlays cannot fix the underlying code that keyboard and screen reader users depend on. In 2025 the US Federal Trade Commission ordered accessiBe to pay $1 million over claims that its tool could make any website compliant. Manual testing and code fixes are the reliable route.
A disabled person can bring an Equality Act claim for failure to make reasonable adjustments in the county court (the sheriff court in Scotland), normally within 6 months, and courts can award compensation, including for injury to feelings. The EHRC and ECNI can also investigate, issue unlawful act notices and take court action, and public sector bodies face GDS monitoring and possible publication of a failed accessibility statement decision.
Yes. The $2,000 Complete Audit includes an accessibility statement draft based on your findings and the GOV.UK model: compliance status, content that is not yet accessible and why, any disproportionate burden claim, how to contact you and the enforcement procedure. Publish it once your fixes are in place and review it regularly.
Have a short list of the templates and journeys that matter most (for example a homepage, a form, a login flow and a PDF people need to use a service), plus any existing accessibility statement or prior scan. A free automated pass on AccessibilityScore.in is a useful starting point that complements a manual audit; bring those results if you have them. Public sector teams should also note any GDS monitoring letter and the GOV.UK statement template they plan to publish.
You receive a prioritized, developer-ready report mapped to WCAG 2.2 AA. We walk through the findings on a call, help you plan remediations, and for Complete Audits we retest fixed issues and draft an accessibility statement. If you prefer to start with discovery only, book a free 30-minute call; if you need to review findings live with your developer, book the $100 technical hour.