{"sections":[{"heading":"Key takeaways","content":"<div class=\"geo-tldr\" role=\"note\" aria-label=\"Key takeaways\"><strong>Key takeaways:</strong> The European Accessibility Act (EU Directive 2019/882) applies since 28 June 2025. The directive does not name a technical standard; for websites the practical reference is EN 301 549, which includes WCAG 2.1 level AA. It covers B2C e-commerce and similar services, exempting service microenterprises (fewer than 10 persons and annual turnover or balance-sheet total of up to EUR 2 million). Overlay widgets do not deliver compliance. Final legal assessment belongs to a lawyer.</div>"},{"heading":"What the European Accessibility Act actually is","content":"<p>The European Accessibility Act (EAA, EU Directive 2019/882) is the EU law requiring many digital products and services to be accessible to people with disabilities. It has applied since <strong>28 June 2025</strong>. For websites the practical question is simple: can a person using a screen reader, keyboard-only navigation or high-contrast mode actually use your site and complete a purchase?</p><p>The EAA itself does not name WCAG. It sets functional accessibility requirements, and services that meet the relevant harmonised standards are presumed to comply (Article 15). For websites the practical reference is the European standard <strong>EN 301 549</strong>, which incorporates <strong>WCAG 2.1 level AA</strong>. So \"EAA compliance\" for a website means, in practice, meeting WCAG 2.1 AA. That single mapping is the most useful thing to remember: when someone asks whether your site is \"EAA compliant\", they are really asking whether it passes WCAG 2.1 AA.</p>"},{"heading":"Does the EAA apply to your website?","content":"<p>The short version: if you sell online to consumers (B2C) in the EU and you are not a microenterprise, it most likely applies to you. The scope is defined by what you sell and how large you are, summarised below:</p><table><thead><tr><th>Category</th><th>Status</th><th>Detail</th></tr></thead><tbody><tr><td>E-commerce, online banking, ticketing, e-books</td><td>Covered</td><td>Consumer-facing digital services</td></tr><tr><td>Service microenterprises</td><td>Exempt</td><td>Fewer than 10 persons and annual turnover or balance-sheet total up to EUR 2 million</td></tr><tr><td>Pure B2B sites</td><td>Generally outside scope</td><td>Line blurs once you also sell to consumers</td></tr></tbody></table><p>Transitional periods (Article 32): services may keep using products they lawfully used before 28 June 2025 until 28 June 2030, and service contracts agreed before 28 June 2025 may continue unchanged until they expire, but no longer than five years.</p><p>Enforcement and fines are set by each member state, not by the directive itself. The amounts and the responsible authority differ by country. For your specific exposure, confirm with a qualified lawyer in your jurisdiction. We confirm the technical side in a free mini-audit.</p>"},{"heading":"What does \"accessible\" mean in practice (WCAG 2.1 AA)?","content":"<p>WCAG is built on four principles: content must be Perceivable, Operable, Understandable and Robust. For a typical business site or shop, AA compliance comes down to a concrete checklist rather than abstract theory:</p><ul><li><strong>Colour contrast</strong> — text vs. background at least 4.5:1 (3:1 for large text).</li><li><strong>Keyboard operability</strong> — every function usable without a mouse, with a visible focus indicator.</li><li><strong>Text alternatives</strong> — meaningful alt text on images, labels on form fields.</li><li><strong>Structure</strong> — correct heading order (one H1, logical H2/H3), landmarks, lists marked up as lists.</li><li><strong>Forms</strong> — errors announced clearly, fields associated with labels, no colour-only error signalling.</li><li><strong>Media</strong> — captions for video, no content that flashes more than three times per second.</li></ul><p>None of this is exotic. It is mostly disciplined HTML and CSS, which is why a clean rebuild often costs less than retrofitting a messy template.</p>"},{"heading":"What are the most common accessibility failures?","content":"<p>Most sites fail on the same handful of points, and most are cheap to fix once identified. These six issues are among the most common:</p><ul><li>Low-contrast grey-on-white body text and light placeholder text.</li><li>Buttons and icons with no accessible name, so a screen reader reads \"button, button, button\".</li><li>Images carrying meaning with empty or missing alt text.</li><li>Forms where the error state is shown only by a red border.</li><li>Custom dropdowns and modals that trap or skip keyboard focus.</li><li>Multiple H1s or skipped heading levels that break navigation for screen-reader users.</li></ul><p>The pattern is consistent: the problems are in the markup and the styling, not in some special \"accessibility layer\". Fix the source and most of the failures disappear at once.</p>"},{"heading":"Why are overlay widgets not compliance?","content":"<p>Overlay widgets do not deliver compliance. You have probably seen the floating \"accessibility\" button that promises instant conformance. It sits on top of the page and does not fix the underlying HTML. Accessibility advocates and several regulators have repeatedly warned against relying on these tools.</p><p>The risk is not only that overlays fail to help. Some have been the subject of lawsuits rather than a defence against them, so a widget bought for protection can become a liability. Real compliance means fixing the source: the markup, the contrast, the focus order and the form labels. That is what survives an audit and an actual user with assistive technology. There is no shortcut button for it.</p>"},{"heading":"How do you check your site?","content":"<p>A useful check has two layers, because automated tools alone are not enough. Scanners catch the mechanical issues; a human catches everything that depends on real interaction:</p><ul><li><strong>Automated scan</strong> (e.g. axe-core) catches the mechanical issues: contrast, missing alt text and basic structure. Many WCAG criteria still need human judgement.</li><li><strong>Manual expert review</strong> covers the rest: real keyboard navigation, screen-reader behaviour, focus management and meaningful sequence.</li></ul><p>The output you want is a prioritised list: what fails, which WCAG criterion it maps to, and the specific fix, not a generic score. Our own site scores 100/100 in the automated Lighthouse accessibility test (checked October 2026), and we run the same process on yours. The point is not a badge but a clear, costed path to conformance you can actually hand to a developer.</p>"},{"heading":"What a professional EAA audit includes — and what it costs","content":"<p>An automated scan alone cannot check every WCAG criterion. A professional audit combines two layers: the automated scan (contrast, form labels, ARIA errors, alt attributes) and a manual expert review (full keyboard operation, screen-reader flow, whether alt texts actually describe images, focus order, touch targets). The deliverable is a report with violations mapped to WCAG 2.1 AA criteria, prioritised so a developer can start fixing the same day.</p><p>Our pricing: audit from <strong>1 490 EUR</strong> (Poland: 2 900 PLN); remediation priced per project after the audit, from <strong>2 900 EUR</strong> (Poland: from 6 900 PLN), with a re-audit confirming the fixes; ongoing monitoring incl. the accessibility statement <strong>149 EUR/month</strong> (Poland: 399 PLN/month). We run the same methodology on our own site — nostressstudio.com scores 100/100 in the automated Lighthouse accessibility test. Details: <a href=\"/en/accessibility-audit/\">EAA / WCAG 2.1 AA accessibility audit</a>.</p>"},{"heading":"Where to start","content":"<p>If you sell to consumers in the EU, the safe move is to know where you stand before someone else points it out. Start with a check: an automated scan plus a manual review, a prioritised fix list and a clear scope for remediation.</p><p>See our <a href=\"/en/accessibility-audit/\">EAA / WCAG 2.1 AA accessibility audit</a> for e-commerce, or open our <a href=\"/en/offer/\">services and pricing</a>. We fix the source, not a bolted-on widget. The technical audit gives you certainty on the code; the final legal assessment of your specific obligations belongs to a qualified lawyer in your country.</p>"}],"faq":[["How much does an EAA audit cost?","Our audit starts at 1 490 EUR (Poland: 2 900 PLN): automated scan plus a manual expert review, with a prioritised WCAG 2.1 AA fix list. Remediation is priced per project after the audit (from 2 900 EUR), and ongoing monitoring incl. the accessibility statement costs 149 EUR/month."],["Does the EAA apply to me?","If you sell online to consumers in the EU and you are not a microenterprise, most likely yes. Service microenterprises (fewer than 10 persons and annual turnover or balance-sheet total up to EUR 2 million) are exempt. We confirm the technical side in a free mini-audit."],["We already added an accessibility widget — is that enough?","No. Overlay and toolbar widgets sit on top of the page and do not fix the underlying code, so they do not deliver conformance. Accessibility advocates and several regulators warn against relying on them. Real compliance means fixing the markup, contrast, focus order and form labels."],["Do you guarantee legal compliance?","We deliver a technical audit and remediation against WCAG 2.1 AA, which is the standard the EAA points to via EN 301 549. The final legal assessment of your specific obligations belongs to a qualified lawyer in your country."],["How long does an audit take?","The automated scan plus a manual expert review delivers a prioritised report typically within 48 hours. You get a list of what fails, the WCAG criterion each issue maps to, and the specific fix, rather than a generic score."]]}