eaa compliance audit from $500
Manual EU accessibility compliance audits for the European Accessibility Act, led by founder Mohammad Shadab Saifi (CPACC, WAS, CPWA, 10+ years). We test key journeys with keyboard and NVDA, JAWS and VoiceOver, map findings to EN 301 549 and WCAG 2.2 AA, and deliver a developer-ready report. Fixed $500 Quick or $2,000 Complete. New to the EAA? Start with a free 30-minute call.
Start Here
New to the EAA, not sure which markets are in scope, or need a quote? Start with the free 30-minute call. Ready for a written EN 301 549 / WCAG report? Order the $500 Quick Audit (up to 5 templates) or the $2,000 Complete Audit for larger sites. Already have findings or EN 301 549 questions to work 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 EAA compliance audit starts by mapping which of your services the European Accessibility Act covers. Article 2 of Directive (EU) 2019/882 names e-commerce, consumer banking, passenger transport booking, e-books, access to audiovisual media and electronic communications services. We then test those journeys by hand with a keyboard, NVDA, JAWS and VoiceOver against EN 301 549 and WCAG 2.2 Level AA.
Auditing existing content? We sort it by what the Directive exempts before we test, so your fix budget goes where the law applies. Microenterprises providing services (fewer than 10 staff and no more than €2 million in annual turnover or balance sheet) are exempt altogether. New to the law? Read our European Accessibility Act guide.
Product pages, search, cart, checkout and account flows on your website and mobile app, the e-commerce services the EAA names directly.
Online and mobile banking, sign-in and identification steps, payments, and the information customers read about your accounts and terms.
Websites, apps, e-tickets and real-time travel information for air, bus, rail and waterborne passenger services.
E-books and reading apps, services that give access to audiovisual media, and electronic communications such as calling and messaging services.
Office files and pre-recorded video published before June 28, 2025, archives not updated since then, and third-party content you neither fund nor control are exempt. We confirm what still needs testing.
Customer portals, account settings and the shared components behind them, so one fix in your design system clears the same issue on every page.
The European Accessibility Act (EAA) has been enforceable since June 28, 2025, and applies to private businesses selling digital products or services to customers anywhere in the EU, including companies based outside Europe. It covers ecommerce, banking, transport, telecoms, and digital media, and compliance is judged against the accessibility requirements in Annex I of the Directive. EN 301 549 v3.2.1, whose web chapter incorporates WCAG 2.1 Level AA, is the technical standard most businesses use as evidence; the newer EN 301 549 v4.1.1, based on WCAG 2.2 and published in September 2026, is not yet the legal reference until the European Commission cites it in the Official Journal. Enforcement runs through each member state and has started: a French court has ordered a major retailer to make its site and app accessible under threat of daily penalties, and German businesses have received private warning letters. No confirmed monetary fine under the EAA had been reported as of August 2026, but statutory maximums reach about one million euros in some countries for the most serious violations. The main size exemption covers microenterprises that provide services, meaning fewer than 10 employees and an annual turnover or balance sheet total of no more than two million euros; product manufacturers must comply regardless of size. An EU accessibility compliance audit against WCAG 2.1/2.2 AA and EN 301 549 gives EU-facing businesses both the technical evidence and the mandatory accessibility statement the EAA requires.
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.
The European Accessibility Act has applied since June 28, 2025 to covered products placed on the EU market and services provided to consumers. Article 32 transition rules are narrow: service contracts agreed before that date can run until they expire, but no later than June 28, 2030, and services can keep using products already lawfully in use until then. A new or redesigned website or app gets no grace period.
Any business selling covered products or services into EU markets is in scope — including e-commerce retailers, banks, and digital service providers headquartered outside the EU.
Each EU country defines its own enforcement and penalties. In Spain, for example, the sanctions that apply through Royal Legislative Decree 1/2013 carry statutory maximums of €30,000 for minor, €90,000 for serious, and €1,000,000 for very serious infringements.
Obligations vary by offering — accessible fonts and formats, text alternatives, and compatibility with assistive technology — rather than a single blanket checklist.
Under Article 13 and Annex V of the Directive, service providers must publish information on how their service meets the accessibility requirements, in written and oral format. An audit gives you the findings that statement must be based on, and our $2,000 Complete Audit includes a statement draft.
The W3C says evaluation tools cannot determine accessibility on their own and human judgement is required. The WebAIM Million 2026 found detectable WCAG failures on 95.9% of the top one million home pages, and barriers such as unclear screen reader output or a broken checkout focus order can only be confirmed by a person.
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.
The WebAIM Million 2026 found low contrast text on 83.9% of top home pages, missing image alt text on 53.1% and missing form labels on 51%. Each issue in your report is mapped to user impact, the EN 301 549 clause and WCAG success criterion, severity and a practical fix.
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.
Annex I of the European Accessibility Act covers ecommerce and consumer banking journeys from search to payment. We test carts, payment forms, one-time codes and session timeouts with a keyboard and screen readers, including embedded third-party widgets, and check the WCAG 2.2 criteria for accessible authentication and redundant entry.
The EAA covers mobile device-based services, including mobile applications, and the information you provide about a service. We test native and hybrid apps with VoiceOver and TalkBack, and check PDFs and downloadable documents for tags, reading order and alternative text. See our PDF document remediation service.
| 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 |
People lead every audit, not a scanner. Automated tools give us a baseline, then our manual auditors check each template and journey with a keyboard and screen readers and map every finding to EN 301 549 and WCAG.
We confirm which of your products or services the EAA covers, which EU markets you serve and whether the microenterprise exemption applies, then pick the templates and journeys a consumer must complete, such as sign-up, search, checkout, booking and support.
We run automated tools across the defined scope to catch code-level issues quickly, giving us a baseline before manual review begins.
Our manual auditors 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, standard references, screenshots, and reproduction steps, then organized into a prioritized remediation roadmap.
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.
Directive (EU) 2019/882, applied since June 28, 2025. Annex I sets the accessibility requirements for covered consumer products and services, such as ecommerce, consumer banking, e-books, electronic communications and passenger transport, including businesses based outside the EU.
The harmonised European standard for ICT accessibility. The web chapter of v3.2.1 incorporates WCAG 2.1 Level A and AA. Version 4.1.1, published in September 2026, moves to WCAG 2.2 and awaits citation in the Official Journal before it becomes the legal reference.
The current W3C Recommendation. It adds criteria such as focus not obscured, target size, dragging movements and accessible authentication to WCAG 2.1 AA. We test to WCAG 2.2 AA so your evidence works under both versions of EN 301 549.
Directive (EU) 2016/2102 covers public sector bodies, which must make websites and mobile apps conform to EN 301 549 and publish an accessibility statement. We audit public sector sites against the same standard.
Each member state enforces the EAA through its own law, such as the BFSG in Germany or the General Law on the rights of persons with disabilities in Spain, with different authorities, fines and complaint routes. We note the markets you serve when we scope the audit.
Service providers must publish how their service meets the accessibility requirements. The report maps findings to that statement, and the Complete Audit includes a statement draft you can publish once fixes are in place.
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 accessibility statements, VPAT and ACR documentation, and procurement or legal review.
Included with the $2,000 Complete Audit: validation after remediation, showing which issues were fixed and what remains open, plus an accessibility statement draft.
Audits are led by founder Mohammad Shadab Saifi, who holds all three IAAP credentials (CPACC, WAS and CPWA), is a DHS Section 508 Trusted Tester and brings 10+ years of accessibility experience. He reviews every audit, supported by a team that handles manual testing, remediation support and documentation.
Reports are written for action. Developers receive clear reproduction steps, expected behavior, affected users, standard mapping, and remediation guidance.
We support businesses operating across multiple regulatory regions with a single audit benchmarked to the highest applicable standard.
Audit scope is tailored to your product and priorities so your team receives useful findings without unnecessary reporting overhead.
What our manual testers check on every page template and journey in scope.
Whether you are based in the EU or serve EU customers from anywhere in the world, our founder-led audit finds the real barriers in your key journeys and gives your team a prioritised, developer-ready roadmap mapped to EN 301 549 and WCAG 2.2 AA. 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 what the EAA means for you 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 EU Accessibility AuditAnswers to common questions about EU accessibility compliance audits and the European Accessibility Act.
Yes. Any business selling digital products or services to customers in the EU must comply with the EAA, regardless of where the business itself is based, including companies in the US, India, or elsewhere.
The European Accessibility Act (Directive (EU) 2019/882) has applied since June 28, 2025 to covered products placed on the EU market and services provided to consumers. The Article 32 transition rules are narrow: service contracts agreed before that date can continue until they expire, but no later than June 28, 2030, and services can keep using products already lawfully in use until then. A new or redesigned website or app must comply now.
Only service businesses with fewer than 10 employees and under two million euros in annual turnover or balance sheet qualify for the microenterprise exemption. Product manufacturers must comply regardless of size. The definitions are in Articles 3(23) and 4(5) of the Directive. Separately, a business can claim a disproportionate burden for a specific requirement, but it must document that assessment.
The EAA sets functional accessibility requirements in Annex I of Directive (EU) 2019/882. Meeting a harmonised standard cited in the Official Journal gives a presumption of conformity, and in practice EN 301 549 v3.2.1, whose web chapter incorporates WCAG 2.1 Level AA, is the reference most businesses use. EN 301 549 v4.1.1, published in September 2026, adopts WCAG 2.2 and adds an annex that maps to the EAA, but AccessibleEU notes it is not yet the legal reference until the Commission cites it. We audit to WCAG 2.2 AA so your evidence works for both versions; see our EN 301 549 v4.1.1 explainer.
Penalties vary by EU member state and can be severe. Hungary’s implementing decree allows fines of up to 5% of annual net turnover, capped at HUF 500 million, for larger operators that do not fix problems by the deadline the authority sets, and Spain allows up to 1,000,000 euros for very serious infringements, with several countries also permitting daily penalties for ongoing violations. These figures are statutory maximums, not fines that regulators have already imposed; the sources are Hungary’s Government Decree 605/2022 (section 9) and Spain’s Law 11/2023 (Article 30), which applies the fine scale of Spain’s General Disability Law.
Yes. Service providers must publish information on how their service meets the accessibility requirements, which in practice is a published, up-to-date accessibility statement. Some countries, such as France, also apply separate national rules that penalise organisations without a compliant accessibility statement.
Our prices are fixed and published: a $500 Quick Audit for up to 5 page templates with a top-10 issues report, and a $2,000 Complete Audit for up to 25 templates or key user flows, with a re-test of fixed issues, an accessibility statement draft and 90-day support. Multi-country or multi-product programs get a custom quote after a free needs assessment. A 1-hour technical accessibility consultation (audit walkthrough, developer Q&A or live issue review) is $100; first conversations are a free 30-minute call, where we learn which services and EU markets are in scope and give you a quote. See our pricing page for details.
We confirm which of your services the EAA covers, pick the journeys a consumer must complete, run automated scans for a baseline, then test every template and flow by hand with a keyboard and screen readers such as NVDA, JAWS, VoiceOver and TalkBack. Each finding is mapped to EN 301 549 and WCAG 2.2 AA with severity, screenshots and a fix. See a sample audit report.
No. The Directive does not require a third-party certificate. Product manufacturers assess conformity themselves under Annex IV and add the CE marking, and service providers must publish the Annex V information on how their service meets the requirements. National authorities can check that evidence, so a documented manual audit, a fix log and a current accessibility statement are what you keep on file.
WCAG 2.2 AA. EN 301 549 v3.2.1, the version in use today, incorporates WCAG 2.1 Level AA, and v4.1.1, published in September 2026, moves to WCAG 2.2. Content that meets WCAG 2.2 AA also meets WCAG 2.1 AA, so one audit covers both. Our EN 301 549 v4.1.1 guide lists the new criteria to fix first.
Yes. Annex I of the Directive covers websites and mobile device-based services, including mobile applications, for services such as ecommerce, consumer banking, e-books and passenger transport. We test native and hybrid apps with VoiceOver and TalkBack as part of the same audit.
No. Overlay widgets do not change the code your customers use, and the W3C says automated tools cannot determine accessibility on their own. Read why accessibility overlays do not prevent legal risk, then fix barriers in your source code with our accessibility remediation team.
No. A VPAT is the template for an Accessibility Conformance Report that procurement teams ask for, and its EU edition reports against EN 301 549. The EAA itself asks for the Annex V service information. One audit can give you the evidence for both, and our VPAT and ACR documentation service writes the report. You can request a VPAT quote here.
Work through it in this order. 1) List the products and consumer services you offer in the EU and the markets you sell to. 2) Pick the journeys a customer must complete, such as sign-up, search, product pages, checkout, account and support, plus the apps and PDFs you provide. 3) Run an automated scan for a baseline; our free AccessibilityScore.in checks one public page with axe-core and maps issues to WCAG, but it is only a starting point. 4) Test each template and journey by hand with a keyboard and screen readers against WCAG 2.2 AA and the matching EN 301 549 clauses, because scanners miss most usability barriers. 5) Log findings by severity, fix them, retest, and publish the Annex V accessibility information. Our guide to what an EAA audit must show explains the evidence, and a $500 Quick Audit covers steps 3 to 5 for up to 5 templates.
Ask four questions. Do they test by hand with assistive technology, not just run a scanner or sell an overlay? Do they map every finding to EN 301 549 clauses and WCAG criteria with steps to reproduce and a fix? Who actually does the testing, and what credentials do they hold, such as the IAAP CPACC, WAS or CPWA? And is the price, scope and retest written down before you start? At HalfAccessible, founder Mohammad Shadab Saifi holds all three IAAP credentials, is a DHS Section 508 Trusted Tester and reviews every audit; prices are fixed at $500 and $2,000, and you can see the deliverable in our sample audit report before you commit.
Each member state names its own authorities. Under Article 23 of the Directive, they must have procedures to check that services comply, follow up complaints or reports of non-compliance, and verify that the business has taken corrective action; products are covered by national market surveillance authorities. In practice a check often starts with a complaint, so the documents that matter are your published accessibility information under Annex V, your audit findings mapped to EN 301 549, and a record of what you fixed and when. Our Complete Audit gives you all three: the report, a retest of fixed issues and an accessibility statement draft.
Book the free 30-minute call if this is your first conversation with us: we find out which of your services and EU markets the EAA covers, where your site or app stands, and recommend an audit scope with a quote. It is the right first step for most businesses exploring EAA compliance. Book the $100 one-hour consultation when you need a hands-on technical session now, for example walking through an existing audit or scan report, talking with your developer about specific EN 301 549 or WCAG fixes, or reviewing issues live on screen. When you are ready for written findings, the $500 Quick Audit and the $2,000 Complete Audit are the next steps (compare pricing).
Send your public website or app URL, the key journeys EU customers use (home, product or service, checkout or signup, account area, help), and which EU markets you sell into. Add test logins if any flow is behind authentication, your product list under EAA Annex I if you know it, and any accessibility complaint or national-authority letter you have received. You can start from the $500 Quick Audit form or book a free 30-minute call first if scope is still unclear.
You receive a written report that maps each finding to EN 301 549 and WCAG, with severity, user impact and recommended fixes, plus a findings review call on the Quick Audit. Your developers can remediate in-house, or we can quote accessibility remediation and a re-test. If a buyer outside the EU also needs procurement evidence, we can align the package toward a VPAT and ACR. Still deciding Quick vs Complete? Start with the free 30-minute call; use the $100 technical hour when you already have findings and need a live developer walkthrough.
