present","description":"Every page must have a descriptive title element. Screen readers announce the title when a page loads.","howToFix":"Add a unique <title> to the <head> of every page that describes its purpose."},"hasLang":{"label":"HTML lang attribute","description":"The HTML element must have a lang attribute. Screen readers use it to select the correct voice/pronunciation engine.","howToFix":"Add lang=\"en\" (or the appropriate language code) to your <html> element."},"hasViewport":{"label":"Viewport meta tag","description":"A viewport meta tag enables responsive scaling. Its absence (or a user-scalable=no value) prevents users from zooming.","howToFix":"Add <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"> and do not set user-scalable=no."},"isHttps":{"label":"HTTPS enforced","description":"HTTPS prevents network interception. Some assistive technologies refuse to load content from HTTP origins.","howToFix":"Redirect all HTTP traffic to HTTPS and obtain a valid TLS certificate."},"exactlyOneH1":{"label":"Exactly one H1","description":"Pages should have exactly one H1 identifying the page's primary topic. Multiple H1s confuse document structure.","howToFix":"Ensure only one <h1> per page, describing the main purpose."},"noSkippedLevels":{"label":"No skipped heading levels","description":"Heading levels must not be skipped (e.g. H1 → H3). Screen reader users navigate by heading level and skips break the hierarchy.","howToFix":"Review your heading structure. Each heading should be one level deeper than its parent, never more."},"noDuplicateHeadings":{"label":"No duplicate heading text","description":"Duplicate heading text makes navigation ambiguous. Screen reader users scanning headings cannot distinguish between sections.","howToFix":"Give each section a unique, descriptive heading that stands alone out of context."},"hasH2s":{"label":"H2s present (section structure)","description":"H2 headings mark major sections. Pages with no H2s suggest that content is not divided into navigable sections.","howToFix":"Organise page content into named sections, each introduced with an H2."},"hasMain":{"label":"Main landmark present","description":"A <main> element or role='main' allows screen reader users to jump directly to the page's primary content.","howToFix":"Wrap your primary page content in a <main> element."},"hasNav":{"label":"Navigation landmark present","description":"A <nav> element marks navigation regions, allowing keyboard users and screen reader users to locate and skip navigation.","howToFix":"Wrap your navigation link lists in <nav> elements."},"hasSkipLink":{"label":"Skip navigation link","description":"A skip link lets keyboard users bypass repeated navigation blocks and jump to the main content, a mandatory SC 2.4.1 requirement.","howToFix":"Add an <a href=\"#main-content\">Skip to main content</a> as the first focusable element on the page."},"multipleNavLabelled":{"label":"Multiple navs have distinct labels","description":"Where a page has multiple <nav> regions, each must have a unique aria-label so users can tell them apart.","howToFix":"Add aria-label=\"Main navigation\" and aria-label=\"Breadcrumb\" (etc.) to each distinct nav element."},"noMissingAlt":{"label":"No images missing alt text","description":"Every <img> must have an alt attribute. Missing alt entirely means screen readers announce the filename or 'image'.","howToFix":"Add alt text to every <img>. Use alt=\"\" for decorative images."},"noSuspiciousAlt":{"label":"No suspicious alt text","description":"Alt text containing 'image of', 'picture of', or just a filename provides no useful description to screen reader users.","howToFix":"Describe what the image shows, not the fact that it is an image."},"altCoverageHigh":{"label":"Alt text coverage ≥ 90%","description":"The percentage of images with any alt attribute (including empty). 90%+ is the pass threshold for this metric.","howToFix":"Audit all images without alt. Add meaningful alt or empty alt for decorative images."},"noTooShortAlt":{"label":"No extremely short alt text","description":"Alt text shorter than 5 characters (but not empty) is likely an error, single letters, numbers, or uninformative strings.","howToFix":"Review very short alt values. Either make them descriptive or mark images as decorative with alt=\"\"."},"allFormInputsLabelled":{"label":"All form inputs labelled","description":"Every form input must have an associated label (via <label for>, aria-label, aria-labelledby, or title). Placeholder is not a label.","howToFix":"Associate a <label for='inputId'> with every input, select, and textarea."},"noEmptyButtons":{"label":"No empty buttons","description":"Buttons with no visible text and no aria-label are announced as 'button' by screen readers with no indication of purpose.","howToFix":"Add visible text or aria-label to every button. Icon-only buttons especially need an aria-label."},"noEmptyLinks":{"label":"No empty links","description":"Links with no text content and no aria-label are announced as blank by screen readers. Common with icon-only links.","howToFix":"Add text content, aria-label, or aria-labelledby to every <a> element."},"noGenericLinks":{"label":"No generic link text","description":"'Click here', 'Read more', 'Here' as link text is meaningless out of context. Screen reader users navigate by link lists.","howToFix":"Write link text that describes the destination or action: 'Read our 2025 Accessibility Report'."},"noPositiveTabindex":{"label":"No positive tabindex values","description":"Tabindex values > 0 override the natural focus order and almost always create a confusing keyboard experience.","howToFix":"Remove all tabindex values above 0. Use tabindex='0' to include custom elements in tab order, or tabindex='-1' to allow programmatic focus."},"noAutoplay":{"label":"No autoplaying media","description":"Video and audio that autoplays without mute can distract screen reader users and cause seizure risk for some users.","howToFix":"Never autoplay audio. If video autoplays, ensure it is muted and has visible pause/stop controls."},"noBlinking":{"label":"No blinking or marquee elements","description":"Blinking content and <marquee> elements can trigger seizures and cannot be paused. Both are deprecated in HTML5.","howToFix":"Remove <blink> and <marquee> elements. Replace animated text with static content or controlled CSS animations with prefers-reduced-motion support."},"noLayoutTables":{"label":"No layout tables","description":"Tables used for visual layout (no caption, no th elements) are misread by screen readers as data tables. Use CSS for layout.","howToFix":"Replace layout tables with CSS Grid or Flexbox. If a table must be used for layout, add role='presentation'."}},"wcagLabels":{"bestPractice":"Best Practice","wcag242A":"WCAG 2.4.2 (A)","wcag311A":"WCAG 3.1.1 (A)","wcag144AAResize":"WCAG 1.4.4 Resize Text (AA)","wcag131A":"WCAG 1.3.1 (A)","wcag246AA":"WCAG 2.4.6 (AA)","wcag2410AAA":"WCAG 2.4.10 (AAA) / Best Practice","wcag136AAA":"WCAG 1.3.6 (AAA) / Best Practice","wcag241A":"WCAG 2.4.1 (A)","wcag111A":"WCAG 1.1.1 (A)","wcag131_332A":"WCAG 1.3.1 / 3.3.2 (A)","wcag412A":"WCAG 4.1.2 (A)","wcag244A":"WCAG 2.4.4 (A)","wcag244_249":"WCAG 2.4.4 (A) / 2.4.9 (AAA)","wcag243AFocus":"WCAG 2.4.3 Focus Order (A)","wcag142AAudio":"WCAG 1.4.2 Audio Control (A)","wcag222APause":"WCAG 2.2.2 Pause Stop Hide (A)"},"verdict":{"pass":"Pass","partial":"Partial","fail":"Fail","passUpper":"PASS","partialUpper":"PARTIAL","failUpper":"FAIL","error":"ERROR"},"evidence":{"toolName":"Competitor Accessibility Benchmark","siteUrlRow":"Site {letter} URL","siteStatusRow":"Site {letter} status","siteScoreRow":"Site {letter} score","siteChecksPassingRow":"Site {letter} checks passing","siteChecksFailingRow":"Site {letter} checks failing","siteVerdictRow":"Site {letter} overall verdict","winnerRow":"Winner","winnerValue":"Site {letter} ({url})","websiteUrlInput":"Website {letter} URL","checksPassingInput":"Checks passing, Site {letter}","checksFailingInput":"Checks failing, Site {letter}","errorPrefix":"ERROR: {message}","scoreOf100":"{score}/100","summarySite":"Site {letter}: {score}/100","summarySiteError":"Site {letter}: error","summaryFallback":"Run comparison to enable export","jsonFormatLabel":"Download JSON","jsonFormatHint":"Full check-by-check comparison with WCAG refs and fix guidance"},"docx":{"benchmarkSummaryHeading":"Benchmark summary","sitesCompared":"Sites compared","checksPerSite":"Checks per site","categoriesLabel":"Categories","winner":"Winner","winnerDetail":"Site {letter} ({url}), {score}/100","noWinner":"(no winner, errors or ties)","perSiteOverviewHeading":"Per-site overview","tableSite":"Site","tableUrl":"URL","tableScore":"Score","tableVerdict":"Verdict","tablePassing":"Passing","tableFailing":"Failing","tableCheck":"Check","tableCategory":"Category","tableWcag":"WCAG","tableHowToFix":"How to fix","siteLabel":"Site {letter}","industryGapsHeading":"Industry-wide gaps, checks where every site fails","industryGapsBody":"{count, plural, one {# check} other {# checks}} failed by all compared sites. These are likely sector-wide accessibility gaps.","failingChecksHeading":"Checks failing on at least one site","fullComparisonHeading":"Full check-by-check comparison ({count} checks)","fullComparisonBody":"Every automated heuristic check, with the result for every site compared. Includes WCAG mapping and category. Note: scores are heuristic signals, not formal conformance verdicts.","methodHeading":"Method","methodBody":"Server-side fetch of each URL, followed by {count} heuristic checks across Document, Headings, Landmarks, Images, Forms, Links, and Media categories. Mapped to WCAG 2.2 SC 1.1.1, 1.3.1, 1.3.6, 1.4.2, 1.4.4, 2.2.2, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.6, 2.4.10, 3.1.1, 3.3.2, 4.1.2 and EN 301 549 V3.2.1 (2021-03) clauses 9.x. Heuristic results signal accessibility issues but do not constitute a formal conformance audit, automated tools detect roughly 30–40% of WCAG issues."},"bulk":{"title":"Bulk Accessibility Benchmark","subtitle":"Upload a sitemap to benchmark accessibility across your entire site, 24 automated checks per page","metaScore":"Score","metaPassed":"Passed","metaFailed":"Failed","issues":{"hasTitle":"Missing page title","hasLang":"Missing HTML lang","exactlyOneH1":"H1 issues","noSkippedLevels":"Skipped heading levels","noDuplicateHeadings":"Duplicate headings","hasH2s":"No H2 headings","hasMain":"No <main> landmark","hasNav":"No <nav> landmark","hasSkipLink":"No skip link","multipleNavLabelled":"Unlabelled nav landmarks","noMissingAlt":"Images missing alt","noSuspiciousAlt":"Suspicious alt text","altCoverageHigh":"Low alt text coverage","noTooShortAlt":"Too-short alt text","allFormInputsLabelled":"Unlabelled form inputs","noEmptyButtons":"Empty buttons","noEmptyLinks":"Empty links","noGenericLinks":"Generic link text","hasViewport":"Missing viewport meta","isHttps":"Not HTTPS","noPositiveTabindex":"Positive tabindex","noAutoplay":"Autoplaying media","noLayoutTables":"Layout tables","noBlinking":"Blinking/marquee content"}}},"compliance-program":{"meta":{"title":"Compliance Programme Template","description":"Generate a full EAA Accessibility Compliance Programme, governance, scope, document management, audit cycle, remediation SLAs, training, and supply chain policy."},"header":{"title":"Compliance Programme Template","subtitle":"Generate a full EAA Accessibility Compliance Programme, the governance document that defines who is responsible, what is in scope, how documents are managed, and how compliance is maintained across your organisation.","whatItGenerates":"What this generates:","whatItGeneratesBody":"A Word (.docx) document covering governance, scope, document management (using local file references, not web links), audit cycle, remediation SLAs, training, supply chain policy, and complaint handling. Suitable for internal use, regulatory inspection, and management sign-off."},"section1":{"title":"Section 1, Programme Identity","orgName":"Organisation Name","orgNamePlaceholder":"E.g. Acme Financial Services GmbH","programTitle":"Programme Title","programTitleNote":"Leave blank to auto-generate","programTitlePlaceholder":"E.g. Acme Accessibility Compliance Programme","programTitlePlaceholderWithOrg":"{orgName} Accessibility Compliance Programme","version":"Version","versionPlaceholder":"1.0","effectiveDate":"Effective Date","nextReviewDate":"Next Review Date","reviewFrequency":"Review Frequency","reviewFrequencyOptions":{"annual":"Annual","biannual":"Biannual (every 6 months)","quarterly":"Quarterly"},"memberState":"EU Member State","selectCountry":"Select country,","nationalLaw":"National Transposing Law","nationalLawPlaceholder":"Auto-populated from country selection","harmonisedStandard":"Harmonised Standard","enOptions":{"v321":"EN 301 549 V3.2.1 (2021), WCAG 2.1, current OJEU standard","v411":"EN 301 549 V4.1.1 (2024), WCAG 2.2, not yet in OJEU"},"targetWcagLevel":"Target WCAG Level","wcagOptions":{"aa":"Level AA, minimum for EAA conformance","aaa":"Level AAA, improved conformance (not required by EAA)"},"v411Warning":"EN 301 549 V4.1.1 is not yet listed in the EU Official Journal as a harmonised standard. Conformance with V4.1.1 does not provide a presumption of conformity under the EAA. Consider also targeting V3.2.1 for legal certainty."},"article32":{"title":"Article 32, Transitional Provisions (organisation level)","description":"Article 32 of Directive (EU) 2019/882 grants a transitional grace period for products and services that were already on the EU market before 28 June 2025. If the services covered by this programme were provided to consumers before that date, you should disclose the transitional status here so it appears in the exported document. New services launched after 28 June 2025 are NOT eligible.","checkboxLabel":"Services covered by this programme were already provided before 28 June 2025","checkboxHint":"If checked, the exported programme will include an Article 32 transitional-provisions section with the relevant grace-period dates (full compliance still required by 28 June 2030 for ongoing service contracts; up to 20 years for self-service terminals lawfully in use before 28 June 2025).","planRefLabel":"Transition Plan Document Reference","planRefPlaceholder":"E.g. ACC-PLAN-2026-01 or \\\\fileserver\\compliance\\transition\\plan-v1.docx","gracePeriodNote":"The transitional period is not a permanent exemption. Service contracts agreed before 28 June 2025 may continue until they expire, but no later than 28 June 2030. This programme should commit to full conformance for all in-scope services by that date."},"microenterprise":{"title":"Microenterprise Exemption (Article 4(5))","description":"Article 4(5) of the EAA exempts microenterprises that provide services (not products) from the accessibility requirements of Article 4. This is a narrow exemption, both thresholds must be met simultaneously and continuously. If your organisation grows beyond either threshold, the exemption is lost and full compliance is required from that point. Hardware and product manufacturers are not eligible regardless of size.","checkboxLabel":"This organisation qualifies as a microenterprise (services only)","checkboxHint":"Fewer than 10 employees AND annual turnover / balance sheet ≤ €2M. Services only, hardware manufacturers are NOT exempt regardless of size.","employeeCount":"Employee Count","employeeCountPlaceholder":"E.g. 7","annualTurnover":"Annual Turnover (€)","annualTurnoverPlaceholder":"E.g. 1500000","thresholdsMet":"✓ Microenterprise thresholds met, service providers may be exempt under Article 4(5)","thresholdsNotMet":"✗ One or more microenterprise thresholds not met, the exemption does not apply","enterData":"Enter employee count and turnover to verify exemption eligibility"},"section2":{"title":"Section 2, Governance","description":"The EAA does not prescribe a governance structure, but market surveillance authorities will look for clear, named accountability. A Management Sponsor provides senior-level ownership and signs off on legal documents (Declarations of Conformity, burden assessments). The Accessibility Officer manages day-to-day programme activities, maintains compliance records, and is the point of contact for regulatory enquiries. Without named owners, a compliance programme has no enforceable authority within the organisation.","competentAuthorityNote":"The Competent Authority field is critical: under Article 14(7), any disproportionate burden assessment must be formally notified to the national market surveillance authority before the exemption can be relied upon. This field records which authority covers your organisation.","sponsorName":"Management Sponsor Name","sponsorNamePlaceholder":"E.g. Chief Operations Officer","sponsorTitle":"Management Sponsor Title","sponsorTitlePlaceholder":"E.g. COO","officerName":"Accessibility Officer Name","officerNamePlaceholder":"E.g. Digital Accessibility Lead","officerTitle":"Accessibility Officer Title","officerTitlePlaceholder":"E.g. Head of Accessibility","officerEmail":"Accessibility Officer Email","officerEmailPlaceholder":"Accessibility@example.com","deputy":"Deputy / Backup Officer","deputyPlaceholder":"E.g. Senior UX Engineer","competentAuthority":"Competent Authority (Article 14(7))","competentAuthorityHint":"Where disproportionate burden assessments must be notified","competentAuthorityPlaceholder":"E.g. Bundesnetzagentur (Germany) / ACM (Netherlands) / ANCOM (Romania)"},"section3":{"title":"Section 3, Products and Services in Scope","description":"The EAA applies only to specific product and service categories listed in Annex I. You must identify exactly which of your products and services fall within scope, and map each one to the correct Annex I section, this mapping determines which technical requirements apply and which sector-specific provisions (e.g. Banking, transport, e-commerce) are relevant.","transitionalNote":"Use Transitional for products already on the market before 28 June 2025 that benefit from the Article 32 grace period, these must still reach full compliance by 28 June 2030. Use Excluded only where there is a documented legal reason (e.g. The product genuinely falls outside Annex I scope, or a microenterprise exemption applies). Unjustified exclusions are a compliance risk if investigated.","annexINote":"The Annex I section is auto-populated from the category, you can override it if needed.","productServiceLabel":"Product / Service {index}","name":"Name","namePlaceholder":"E.g. Customer Portal","category":"Category","annexISection":"EAA Annex I Section (auto-populated)","status":"Status","statusOptions":{"inScope":"In Scope, fully covered by this programme","transitional":"Transitional, compliance in progress","excluded":"Excluded, with stated reason"},"exclusionReason":"Reason for Exclusion","exclusionReasonPlaceholder":"E.g. Legacy system, decommissioning Q4 2026","transitionPlan":"Transition Plan Summary","transitionPlanPlaceholder":"E.g. Full conformance by Q3 2026 per roadmap ref. ACC-PLAN-2026-01","addProduct":"+ Add Product / Service","remove":"Remove"},"section4":{"title":"Section 4, Compliance Document Management","description":"Article 20 of the EAA requires economic operators to retain technical documentation for a minimum of 5 years after a product is last placed on the market or a service is last provided. Market surveillance authorities can request this documentation at any time, if it cannot be produced promptly, the organisation is treated as non-compliant regardless of the actual accessibility status of the product.","description2":"This section defines how compliance documents are stored, named, and version-controlled within your organisation. A clear naming convention prevents confusion between versions and makes it straightforward to locate the current document for each product during an inspection.","storageAdvice":"Store documents on your organisation's own systems, local file paths, network shares, or your document management system (SharePoint, Confluence, etc.), not as links to external online services. This ensures documents remain available to regulators regardless of third-party service status or subscription changes.","repoLocation":"Document Repository Location","repoLocationNote":"Local path, network share, or DMS reference","repoLocationPlaceholder":"E.g. \\\\server\\compliance\\accessibility\\ or SharePoint > Compliance > Accessibility Documents or Confluence: Compliance / Accessibility","namingConvention":"Document Naming Convention","namingConventionPlaceholder":"E.g. ORGCODE-DOCTYPE-PRODUCTCODE-YYYY-vN.N.docx","docOwnerRole":"Document Owner Role","docOwnerRolePlaceholder":"E.g. Accessibility Officer","requiredDocTypes":"Required Document Types","requiredDocTypesNote":"Select all that apply","docTypes":{"statement":"Accessibility Statement (EAA Annex V), public-facing, per product/service","doc":"EU Declaration of Conformity (EAA Annex IV), legally binding, per product/service","acr":"Accessibility Conformance Report / VPAT, procurement document","burden":"Disproportionate Burden Assessment (Article 14), where applicable","auditReport":"Accessibility Audit Report, per audit cycle","trainingRecords":"Training Completion Records, per employee/module","supplierACRs":"Supplier ACRs / VPATs, for all third-party in-scope components"}},"section5":{"title":"Section 5, Audit and Review Cycle","description":"The EAA does not prescribe a specific audit frequency, but Accessibility Statements must be reviewed whenever conformance status changes, and the disproportionate burden assessment renewal obligation (Article 14(4)) requires reassessment at least every 5 years or on significant product change. In practice, annual audits are the minimum credible standard, enforcement bodies will question a programme that has not been audited within the past 12 months.","description2":"The interim review triggers are events that require an out-of-cycle accessibility review regardless of when the last scheduled audit was. Without these, a major product release or regulatory change could go unreviewed until the next annual cycle, creating a compliance gap that is difficult to defend.","auditFrequency":"Scheduled Audit Frequency","auditFrequencyOptions":{"annual":"Annual (minimum recommended)","biannual":"Biannual (every 6 months)","continuous":"Continuous / rolling"},"auditMethodology":"Audit Methodology","auditMethodologyNote":"Select all that apply","auditMethods":{"selfAssessment":"Guided EAA Self-Assessment (AccessibilityRef or equivalent structured tool suite)","automatedManual":"Automated tools (axe, WAVE, Lighthouse) + manual testing","thirdParty":"Third-party audit by independent accessibility specialist","userTesting":"User testing with participants with disabilities","screenReader":"Screen reader verification (NVDA, JAWS, VoiceOver minimum)"},"samplingApproach":"Sampling Approach","samplingApproachNote":"Optional but recommended for large sites","samplingApproachPlaceholder":"E.g. 10% random sample of pages plus all high-traffic journeys (login, checkout, account management). New content sampled at release. Full site audit annual.","interimTriggers":"Interim Review Triggers","interimTriggersNote":"Events requiring an out-of-cycle review"},"section6":{"title":"Section 6, Remediation SLAs","description":"When an audit or complaint identifies an accessibility barrier, you need a documented process for resolving it. Enforcement bodies will look not just at whether barriers exist, but at whether the organisation has a credible, time-bound plan to fix them. Defined severity levels and fix deadlines demonstrate good-faith compliance effort and protect the organisation in the event of an inspection or formal complaint.","description2":"Critical barriers, those that completely prevent a person with a disability from using the product or service, carry the highest regulatory risk. They should be treated with the same urgency as a production outage. Escalation is important: if a fix deadline is missed, the issue must automatically move up the reporting chain so that resource can be allocated.","severityLabels":{"critical":"Critical","major":"Major","minor":"Minor"},"severityDefinitions":{"critical":"Complete barrier, prevents a person with disability from using the product or service","major":"Significant barrier, significantly impairs use but a workaround exists","minor":"Low-impact barrier, causes inconvenience but does not prevent access"},"definition":"Definition","fixTarget":"Fix Target (calendar days)","escalateWithin":"Escalate if not fixed within (days)","escalationOwner":"Escalation Owner (role)","escalationOwnerPlaceholder":"E.g. Accessibility Officer → Head of Engineering → COO","verificationProcess":"Post-Fix Verification Process","verificationProcessPlaceholder":"E.g. Re-test against relevant WCAG SC, store evidence in compliance repository"},"section7":{"title":"Section 7, Training","description":"Untrained staff will continuously introduce new accessibility barriers, regardless of how thorough the last audit was. The EAA's organisational measures, referenced in Annex V Accessibility Statements, implicitly require staff with relevant responsibilities to understand accessibility requirements. Training records serve two purposes: they change behaviour and they provide evidence of reasonable diligence if the organisation is challenged.","description2":"Different roles need different training. Developers need to know how to code accessibly and test with assistive technologies. Content authors need to understand alt text, plain language, and heading structure. Procurement teams need to know what to require from suppliers. Management needs enough awareness to make informed decisions about resourcing and risk. The pre-populated rows below cover the five core audiences, edit them to match your organisation.","trainingAudiences":{"developers":"Developers / Engineers","contentAuthors":"Content Authors","uxDesigners":"UX / Designers","procurement":"Procurement / Legal","management":"Management / Senior Leadership"},"trainingTypes":{"developers":"WCAG 2.1/2.2 technical training, coding patterns, testing with assistive technologies","contentAuthors":"Accessible content writing, plain language, alt text, heading structure, links","uxDesigners":"Accessible design, colour contrast, touch targets, focus indicators, ARIA patterns","procurement":"EAA supplier requirements, ACR/VPAT review, contract clause requirements, DoC obligations","management":"EAA legal obligations awareness, enforcement risk, programme sponsorship, reporting obligations"},"trainingFrequencies":{"annualOnboarding":"Annual + onboarding","annual":"Annual","biannual":"Biannual"},"completionEvidenceValues":{"courseCert":"Course completion certificate or internal attendance record","internalRecord":"Internal training record","briefingRecord":"Briefing attendance record"},"trainingType":"Training Type","frequency":"Frequency","completionEvidence":"Completion Evidence"},"section8":{"title":"Section 8, Supply Chain and Procurement Policy","description":"Under the EAA, if you incorporate a third-party product or service into what you offer to end users, you are responsible for the accessibility of the combined result. Buying an inaccessible component and embedding it in your product does not transfer liability, the importer or distributor placing that product on the EU market is responsible under Article 7 and Article 9. This means supplier accessibility requirements are not optional extras; they are a direct extension of your own compliance obligation.","description2":"The most effective risk management tool is the contract. An Accessibility Conformance Report (ACR/VPAT) or EU Declaration of Conformity clause in the supplier agreement shifts risk and creates a paper trail showing due diligence. Requiring ACRs at procurement and renewal, rather than retrospectively, prevents inaccessible components from entering the supply chain in the first place. Document the clause reference below so it can be cited in any future inspection.","acrCheckbox":"Require ACR/VPAT from suppliers (within 12 months, covering WCAG A/AA)","docCheckbox":"Require EU Declaration of Conformity confirmation from suppliers","acrRequired":"ACR / VPAT Required","docRequired":"EU Declaration of Conformity Required","contractClause":"Contract Clause Reference","contractClausePlaceholder":"E.g. Clause 14.3 of MSA v2.1, Accessibility Warranty","supplierAuditFrequency":"Supplier Audit Frequency","supplierAuditFrequencyDefault":"At contract renewal and biannually thereafter"},"section9":{"title":"Section 9, Feedback and Complaint Handling","description":"Article 13(1) of the EAA requires service providers to include a feedback mechanism in their Accessibility Statement so that users can report barriers and request accessible alternatives. This is not just a courtesy, it is a legal obligation, and the channel must be functional and monitored. A 20-working-day response SLA is the standard used by most national implementations, though some member states set shorter deadlines. Check your national transposition law.","description2":"Complainants who are unsatisfied with the response have the right to escalate directly to the national enforcement body (the competent authority designated under Article 30). Enforcement bodies will check, at a minimum, whether a feedback mechanism exists, whether it was responded to, and whether any identified barriers were logged and remediated. Documenting your escalation path, both internally and the route to the enforcement body, shows that the organisation takes complaints seriously and has a structured process for handling them.","feedbackChannel":"Feedback / Accessibility Contact","feedbackChannelPlaceholder":"E.g. Accessibility@example.com or feedback form URL","responseSla":"Response SLA","responseSlaWorking":"Response SLA (working days)","workingDays":"Working days","enforcementBodyName":"Enforcement Body Name","enforcementBodyNamePlaceholder":"E.g. National market surveillance authority","enforcementBody":"Competent Enforcement Body","internalEscalationLabel":"Internal Escalation Path","internalEscalationPlaceholder":"E.g. Accessibility Officer → Head of Compliance → COO","escalationProcess":"Escalation Process","internalEscalation":"Internal Escalation","enforcementEscalationProcessLabel":"Enforcement Escalation Process","enforcementEscalationProcessPlaceholder":"E.g. If a complainant is not satisfied with our response within 20 working days, they may contact [enforcement body] directly. Contact details are included in our Accessibility Statement..."},"exportSection":{"title":"Export Compliance Programme","description":"Generates a full Word (.docx) document covering all 10 programme sections. Store in your compliance document repository and present for management sign-off and regulatory inspection.","exportButton":"Export Compliance Programme (.docx)","generating":"Generating...","proOnly":"Pro only, Upgrade to export","needOrgName":"Enter organisation name to enable export"},"evidence":{"toolName":"EAA Compliance Programme Template","summaryWithOrg":"Compliance programme for {orgName} v{version}","summaryFallback":"Add organisation name above to enable export","labels":{"organisation":"Organisation","programmeTitle":"Programme title","version":"Version","effectiveDate":"Effective date","country":"Country","nationalLaw":"National law","enStandard":"EN standard","wcagLevel":"WCAG level","productsInScope":"Products / services in scope","trainingItemsDefined":"Training items defined","auditFrequency":"Audit frequency","slaSeveritiesDefined":"SLA severities defined","feedbackSla":"Feedback SLA (working days)","microenterpriseExemption":"Microenterprise exemption","article32Transitional":"Article 32 transitional (pre-2025-06-28)"},"values":{"yes":"Yes","no":"No","yesPlanRef":"Yes, {planRef}","planRefNotSet":"(plan reference not set)","wcagLevelLabel":"WCAG 2.x Level {level}","enStandardLabel":"EN 301 549 {version}"},"jsonFormat":{"label":"Download as JSON","hint":"Complete programme state"}},"interimTriggers":{"majorRelease":"Major product or service release (new version, platform migration)","contentChange":"Significant change to content structure or functionality","regulatoryUpdate":"Regulatory guidance update from competent authority","complaintUpheld":"Accessibility complaint upheld by enforcement body","inspection":"Market surveillance authority inspection","acquisition":"Acquisition, merger, or outsourcing of product/service","newRegulation":"New accessibility regulation or standard published","techChange":"Change of technology supplier / CMS"},"eaaCategories":{"websiteWebApp":"Website / Web Application","mobileApp":"Mobile Application (iOS / Android)","desktopSoftware":"Desktop Software","computerOs":"Computer / Operating System","paymentTerminal":"Payment Terminal","selfServiceTerminal":"Self-service Terminal (ATM / Kiosk)","smartphoneTablet":"Smartphone / Tablet","ereader":"E-reader","consumerElectronics":"Consumer Electronics (TV / Set-top box)","telephony":"Telephony / Electronic Communications Service","audioVisual":"Audio-visual Media Service","ebook":"E-book","ecommerce":"E-commerce Service","banking":"Banking / Financial Service","passengerTransport":"Passenger Transport Booking Service","other":"Other"},"annexIMap":{"websiteWebApp":"Annex I §IX, E-commerce / electronic communications","mobileApp":"Annex I §IX, E-commerce / electronic communications","desktopSoftware":"Annex I §III, General-purpose computer hardware and operating systems","computerOs":"Annex I §III, General-purpose computer hardware and operating systems","paymentTerminal":"Annex I §V, Self-service terminals","selfServiceTerminal":"Annex I §V, Self-service terminals","smartphoneTablet":"Annex I §II, Smartphones","ereader":"Annex I §IV, Consumer terminal equipment with advanced computing","consumerElectronics":"Annex I §VI, Consumer terminal equipment for electronic communications","telephony":"Annex I §VI, Electronic communications services","audioVisual":"Annex I §VII, Audio-visual media services","ebook":"Annex I §VIII, E-books and dedicated reading software","ecommerce":"Annex I §IX, E-commerce services","banking":"Annex I §X, Banking services","passengerTransport":"Annex I §XI, Passenger transport services","other":"Annex I, identify applicable section manually","fallback":"Annex I, identify applicable section manually"},"docx":{"coverDirective":"European Accessibility Act, Directive (EU) 2019/882","coverVersionLine":"Version {version} | Effective: {effective} | Next Review: {nextReview}","coverOrgLine":"Organisation: {orgName}","fallback":{"orgName":"[Organisation Name]","sponsorName":"[Sponsor Name]","officerName":"[Officer Name]","officerEmail":"[email address]","deputyNotDesignated":"Not designated","competentAuthority":"[Identify national market surveillance authority]","memberState":"[EU Member State]","nationalLaw":"[Identify national transposition law]","productService":"[Product/Service]","transitionPlanRef":"[Document reference / DMS path for the formal transition plan]","name":"[Name]","title":"[Title]","role":"[Role / Name]","managementSponsor":"[Management Sponsor]","nationalEnforcementAuthority":"[National market surveillance authority]","transitionFallback":"Transition plan to be documented separately.","exclusionFallback":"Not stated.","autoTitle":"[Organisation] Accessibility Compliance Programme","autoTitleWithOrg":"{orgName} Accessibility Compliance Programme"},"section1":{"h1":"1. Programme Identity and Legal Framework","labels":{"organisation":"Organisation","programmeTitle":"Programme Title","version":"Version","effectiveDate":"Effective Date","nextReviewDate":"Next Mandatory Review Date","reviewFrequency":"Review Frequency","memberState":"Member State","nationalLaw":"National Transposing Law","harmonisedStandard":"Harmonised Standard","targetConformanceLevel":"Target Conformance Level"},"harmonisedStandardV321":"EN 301 549 V3.2.1 (2021-03), current OJEU harmonised standard","harmonisedStandardV411":"EN 301 549 V4.1.1 (2024-11), references WCAG 2.2 (not yet in OJEU list)","targetConformanceValue":"WCAG {wcag} Level {level}","noteV321":"Note: EN 301 549 V3.2.1 is listed in the EU Official Journal as the harmonised standard under the EAA. Conformance with this standard gives rise to a presumption of conformity with the corresponding EAA requirements.","noteV411":"Note: EN 301 549 V4.1.1 is not yet listed in the EU Official Journal as a harmonised standard. Conformance with V4.1.1 does not automatically give rise to a presumption of conformity under the EAA. Consider also conforming with V3.2.1 for legal certainty.","reviewFreqAnnual":"Annual","reviewFreqBiannual":"Biannual","reviewFreqQuarterly":"Quarterly"},"article32":{"h2":"1.2 Article 32, Transitional Provisions","body":"The services covered by this programme were placed on the EU market or provided to consumers before 28 June 2025. Under Article 32(1) of Directive (EU) 2019/882, service contracts agreed before 28 June 2025 may continue without alteration until they expire, but no later than five years from that date. Service providers may continue to provide their services using products which were lawfully used by them to provide similar services before 28 June 2025 until 28 June 2030. Self-service terminals lawfully used to provide services before 28 June 2025 may continue to be used to provide similar services until the end of their economically useful life, but no longer than 20 years after their entry into use.","planRefLabel":"Article 32 Transition Plan Reference","note":"This programme acknowledges the Article 32 grace period but commits to full compliance for all in-scope products and services no later than the dates specified in this section. New products and services placed on the market on or after 28 June 2025 are NOT covered by Article 32 and must comply with the EAA in full from the date they are placed on the market."},"microenterprise":{"h2":"1.1 Microenterprise Status (Article 4(5))","body":"This organisation qualifies as a microenterprise under Article 4(5) of Directive 2019/882 and its services are therefore exempt from the accessibility requirements of Article 4.","labels":{"employeeCount":"Employee Count","annualTurnover":"Annual Turnover"},"definition":"Microenterprise definition: fewer than 10 employees AND annual turnover or balance sheet total not exceeding €2 million (Commission Recommendation 2003/361/EC).","note":"Note: The microenterprise exemption applies only to SERVICE providers. Manufacturers of products (hardware, software) are NOT exempt regardless of size. Even where the exemption applies, the organisation may voluntarily choose to implement accessibility requirements. This programme documents the voluntary measures taken."},"section2":{"h1":"2. Programme Governance","labels":{"managementSponsor":"Management Sponsor","accessibilityOfficer":"Accessibility Officer","officerContact":"Accessibility Officer Contact","deputy":"Deputy / Backup Officer","competentAuthority":"Competent Authority (Article 14(7) notifications)"},"h2Sponsor":"2.1 Management Sponsor Responsibilities","sponsorBullets":{"0":"Champion accessibility at senior leadership level","1":"Approve the annual programme plan and budget","2":"Receive and act on quarterly programme status reports","3":"Escalation point for unresolved disproportionate burden claims","4":"Sign off on EU Declarations of Conformity (Annex IV) and burden assessments (Article 14)"},"h2Officer":"2.2 Accessibility Officer Responsibilities","officerBullets":{"0":"Own and maintain this Compliance Programme","1":"Coordinate all accessibility audits and assessments","2":"Maintain the compliance document register (see Section 5)","3":"Notify the competent authority of disproportionate burden claims (Article 14(7))","4":"Respond to accessibility feedback within the required SLA (Section 10)","5":"Submit annual compliance reports to the Management Sponsor","6":"Keep training records and manage the training programme (Section 8)","7":"Monitor regulatory developments and update this programme as required"}},"section3":{"h1":"3. Scope, Products and Services","h2InScope":"3.1 In-Scope Products and Services","noInScope":"No in-scope products or services defined.","categoryNote":"Category: {category}","categoryReasonNote":"Category: {category} | {reason}","exclusionReasonNote":"Reason for exclusion: {reason}","h2Transitional":"3.2 Products and Services in Transition","transitionalIntro":"The following products and services are subject to EAA requirements but are in a planned transition to full compliance:","h2Excluded":"3.3 Excluded Products and Services","excludedIntro":"The following products and services are excluded from this programme with stated reasons:"},"section4":{"h1":"4. Compliance Document Management","intro":"This programme requires the following compliance documents to be prepared, version-controlled, and retained for a minimum of 5 years from the date of preparation (Article 20, Directive 2019/882). All documents are stored in the organisation's internal document management system. No reliance is placed on documents hosted at external online services.","labels":{"repoLocation":"Document Repository Location","namingConvention":"Naming Convention","owner":"Document Owner Role","retention":"Minimum Retention Period"},"fallbacks":{"repoLocation":"[Local file path, network share, or DMS reference, e.g. \\\\server\\compliance\\accessibility\\ or SharePoint: Compliance > Accessibility]","namingConvention":"[e.g. ORGCODE-DOCTYPE-PRODUCTCODE-YYYY-vN.N.docx]","owner":"[e.g. Accessibility Officer]"},"retentionValue":"5 years from date of preparation (EAA Article 20)","h2Required":"4.1 Required Document Types","docTypes":{"statement":"Accessibility Statement (EAA Annex V), per product/service, public-facing","doc":"EU Declaration of Conformity (EAA Annex IV), per product/service, legally binding","acr":"Accessibility Conformance Report / VPAT, per product/service, procurement use","burden":"Disproportionate Burden Assessment (Article 14), where burden is claimed","auditReport":"Accessibility Audit Report, per audit cycle","trainingRecords":"Training Completion Records, per employee, per training module","supplierACRs":"Supplier ACRs / VPATs, for each third-party component in scope"},"versionControlNote":"Version control: All documents must carry a version number, effective date, and the name of the person who approved the document. Superseded versions must be retained but clearly marked as superseded. When a document is updated, the previous version should be archived in a dated subfolder."},"section5":{"h1":"5. Audit and Review Cycle","scheduledFreqLabel":"Scheduled Full Audit Frequency","freq":{"annual":"Annual","biannual":"Biannual (every 6 months)","continuous":"Continuous / rolling"},"h2Methodology":"5.1 Audit Methodology","methodLines":{"selfAssessment":"Structured self-assessment pipeline covering all EN 301 549 / WCAG 2.1/2.2 tool categories: automated scanning, manual keyboard and screen reader testing, document auditing, sector-specific checklists, and compliance document generation. Results recorded per tool with timestamped notes log.","automatedManual":"Automated testing (axe, WAVE, Lighthouse) supplemented by manual verification against WCAG 2.1/2.2 Level AA","thirdParty":"Third-party audit by an independent accessibility specialist","userTesting":"User testing with participants with disabilities (note: studies indicate user testing detects 30–40% of issues not found by automated tools)","screenReader":"Screen reader verification: NVDA + Chrome, JAWS + Edge, VoiceOver + Safari as minimum AT matrix"},"h2Sampling":"5.2 Sampling Approach","h2Triggers":"5.3 Interim Review Triggers","triggersIntro":"In addition to the scheduled audit cycle, an accessibility review must be triggered by any of the following events:"},"section6":{"h1":"6. Remediation Workflow","h2Severity":"6.1 Severity Classification and Fix SLAs","labels":{"definition":"Definition","fixDeadline":"Target Fix Deadline","escalation":"Escalation if SLA Missed","escalationOwner":"Escalation Owner"},"fixDeadlineValue":"{days} calendar days from identification","escalationValue":"{days} calendar days before deadline, escalate to {owner}","escalationOwnerFallback":"Accessibility Officer","h2Verification":"6.2 Post-Fix Verification","defaultVerification":"All remediated issues must be re-tested against the relevant WCAG success criterion before the issue is marked as resolved in the audit log. Re-test evidence (tool output, screen reader test note, or third-party sign-off) must be stored alongside the original finding in the compliance document store."},"section7":{"h1":"7. Training Programme","intro":"The following training requirements apply to all staff with responsibilities that affect the accessibility of products or services covered by this programme. Training records must be retained for a minimum of 5 years.","labels":{"trainingType":"Training Type","frequency":"Frequency","completionEvidence":"Completion Evidence"}},"section8":{"h1":"8. Supply Chain and Procurement Policy","intro":"All third-party products, components, or services that form part of an in-scope product or service must meet the accessibility requirements of this programme before procurement or renewal.","labels":{"acrRequirement":"ACR / VPAT Requirement","docRequirement":"EU Declaration of Conformity Requirement","contractClause":"Contract Clause Reference","supplierAuditFrequency":"Supplier Audit Frequency"},"acrRequiredValue":"Required, supplier must provide a current Accessibility Conformance Report (ACR/VPAT 2.5) dated within 12 months before contract award or renewal.","acrNotRequiredValue":"Not mandated as minimum requirement.","docRequiredValue":"Required, supplier must confirm that products placed on the EU market are covered by a valid Annex IV Declaration of Conformity.","docNotRequiredValue":"Not mandated as minimum requirement.","contractClauseFallback":"[Reference to accessibility warranty clause in standard supplier agreement / MSA, e.g. Clause 14.3 of Master Services Agreement v2.1]","procurementNote":"Procurement teams must not proceed with a supplier selection where the supplier cannot provide a current ACR or where their ACR records non-conformances that have not been remediated or are not subject to a binding remediation plan. All supplier ACRs must be stored in the compliance document repository (see Section 4)."},"section9":{"h1":"9. Feedback and Complaint Handling","labels":{"feedbackContact":"Feedback / Accessibility Contact","responseSla":"Response SLA","enforcementBody":"Competent Enforcement Body","escalationProcess":"Escalation Process","internalEscalation":"Internal Escalation"},"feedbackChannelFallback":"[email address, URL, or phone number, must be in the public Accessibility Statement]","responseSlaValue":"{days} working days","h2Process":"9.1 Complaint Handling Process","processBullets":{"0":"All accessibility complaints must be logged in the compliance document store on receipt.","1":"Initial acknowledgement must be sent within 5 working days.","2":"A substantive response addressing the reported barrier must be provided within {days} working days.","3":"Where the complaint identifies a genuine barrier, the issue must be logged in the audit remediation tracker and assigned a severity level.","4":"Where the barrier cannot be resolved within the standard SLA, the complainant must be offered an accessible alternative means of access (Article 13(2))."},"h2Enforcement":"9.2 Enforcement Escalation","escalationProcessFallback":"If the complainant is not satisfied with the response, they may escalate to the national enforcement body. The Accessibility Statement must include the enforcement body's name and contact details."},"section10":{"h1":"10. Programme Review and Reporting","labels":{"annualReviewDate":"Annual Programme Review Date"},"intro":"This programme must be reviewed against the following criteria at each scheduled review:","criteria":{"0":"Completeness: all in-scope products have current compliance documents","1":"Currency: all Accessibility Statements reviewed within the past 12 months","2":"Currency: all Declarations of Conformity reviewed after any significant product change","3":"Currency: all disproportionate burden assessments reviewed on the 5-year cycle (Article 14(4))","4":"Training: all required staff training completed and recorded","5":"Supplier: all supplier ACRs current (within 12 months)","6":"Complaints: all open complaints resolved or in active remediation"},"h2Reporting":"10.1 Management Reporting","reportingIntro":"The Accessibility Officer must report programme status to the Management Sponsor at least annually, covering:","reportingBullets":{"0":"Number of in-scope products and their conformance status","1":"Number of open accessibility issues and severity distribution","2":"Audit findings summary for the period","3":"Complaint volume, resolution rate, and escalation count","4":"Training completion rates","5":"Regulatory developments requiring programme updates"}},"section11":{"h1":"11. Programme Approval","labels":{"approvedBy":"Approved by (Management Sponsor)","programmeOwner":"Programme Owner (Accessibility Officer)","effectiveDate":"Effective Date","version":"Version","nextReviewDate":"Next Review Date"},"signatureLine":"Signature: ___________________________ Date: _______________","footer":"This document is an internal governance record of {orgName}'s accessibility compliance programme under Directive (EU) 2019/882 (European Accessibility Act). It should be stored in the compliance document repository and made available to market surveillance authorities on request. Retain for a minimum of 5 years."}}},"compliance-report":{"meta":{"toolId":"Compliance-report","title":"Compliance Report Builder","description":"Build EAA compliance reports with findings and remediation plans. Pro self-assessment tool for WCAG 2.2 and EN 301 549 audits."},"badge":"Pro Tool","title":"Compliance Report Builder","subtitle":"Build a complete accessibility audit report in 5 guided steps.","proGateFeatures":["Build a professional WCAG accessibility audit report with guided steps","Issued under the AccessibilityRef brand, defensible to regulators and procurement","Add findings with severity, WCAG criterion, location, and remediation steps","Export as Word (.docx) or Excel (.xlsx) for client delivery","Attach evidence records from the Evidence Vault"],"header":{"savedAt":"Auto-saved","startNewConfirmTitle":"Clear all data?","startNewConfirmYes":"Yes, start over","startNewConfirmCancel":"Cancel"},"stepIndicator":{"ariaLabel":"Go to step {step}: {label}","stepOf":"Step {step} of {total}"},"intro":{"heading":"What this tool produces, and when you need it","para1Strong":"An accessibility audit report","para1Body":"Is a formal document recording the conformance status of a digital product against WCAG 2.2 (or a specified level). It lists every finding, what failed, where, how severe, and how to fix it, alongside a remediation timeline.","para2":"This tool builds that report in 6 guided steps and exports it in formats your team will actually use: Word for clients, Excel for developers, PDF for board packs, and CSV for issue trackers.","whenHeading":"When you legally need one:","whenItems":["European Accessibility Act (Directive 2019/882), formal audit documentation is required evidence if a disproportionate burden claim is made, or during an enforcement investigation.","Public sector accessibility regulations across the EU and UK, public bodies must document their compliance status and publish an accessibility statement referencing known failures.","Disability discrimination litigation, a professionally produced audit report is a key mitigation document. It demonstrates good faith and scopes the remediation commitment.","Procurement, many enterprise RFPs and government contracts now require a VPAT or equivalent audit report as a pre-qualification requirement."],"tip":"Tip: Complete the Findings step (Step 3) before Step 4, the executive summary auto-generates from your logged findings, including exact issue counts and conformance verdict."},"steps":{"step1":{"label":"Project","heading":"Step 1 of 6, Project Information","description":"Enter the basic details about who the audit is for and who conducted it. This information appears on the report cover page. All fields are saved automatically as you type.","title":"Project Information","fields":{"clientName":"Client / Organisation Name","productName":"Product / Website Name","productUrl":"Product URL","auditDate":"Audit Date","auditorName":"Auditor Name","auditorOrg":"Auditor Organisation","reportVersion":"Report Version","wcagLevel":"WCAG Conformance Level","regulations":"Applicable Regulations","pagesAudited":"Pages / Screens Audited","toolsUsed":"Testing Tools Used","annexISection":"EAA Annex I Section"},"placeholders":{"clientName":"Acme Corporation","productName":"Acme Online Store","productUrl":"Https://www.acme.com","auditorName":"Jane Smith","auditorOrg":"Accessibility Consultants Ltd","reportVersion":"1.0"},"annex":{"labelBadge":"Regulatory scope identifier","selectPlaceholder":"Select the EAA Annex I section that applies,","options":{"ix":"Section IX, E-commerce / Web / Electronic communications","x":"Section X, Banking services for consumers","xi":"Section XI, Passenger transport services","vii":"Section VII, Audio-visual media services","viii":"Section VIII, E-books and dedicated reading software","v":"Section V, Self-service terminals (ATMs, kiosks, ticketing)","vi":"Section VI, Electronic communications services","iii":"Section III, Computer hardware / operating systems","ii":"Section II, Smartphones","other":"Other, specify in notes"},"helper":"Identifies which part of EAA Annex I this audit covers. Enforcement bodies use this to determine applicable requirements. Appears on the report cover page and scope section."},"branding":{"title":"Report branding","body":"Reports are issued under the <strong>AccessibilityRef</strong> brand on every plan, cover, headings, footer, and logo. The platform is the named issuer of every audit artefact, which keeps the deliverable defensible to regulators and procurement teams. If you need bespoke client branding, attach this report as an appendix to your own consultancy report."}},"step2":{"label":"Scope","heading":"Step 2 of 6, Scope & Standards","description":"Select which regulations apply to this audit (e.g. WCAG 2.2 AA for EU sites under the European Accessibility Act). List the pages you tested and the tools you used. This becomes the Scope & Methodology section of your report.","methodologyGuidance":"Methodology guidance: For a legally defensible report, the Tools Used field should include: automated tool names and versions (e.g. Axe-core 4.9), assistive technology tested (e.g. NVDA + Chrome, JAWS + Edge, VoiceOver + Safari), browser and OS combinations, and whether user testing with disabled participants was conducted. The Pages Audited field should state how pages were selected and what proportion of the site they represent (e.g. “12 pages covering all unique templates, 100% of template types, ~15% of total pages”).","title":"Scope & Methodology","regulationsLabel":"Applicable Regulations / Standards","wcagLevelLabel":"WCAG Conformance Level","wcagLevelOption":"Level {level}","fields":{"overallConformance":"Overall Conformance","samplingMethodology":"Sampling Methodology","userTestingWithDisabledUsers":"User Testing with Disabled Users","userTestingNotes":"User Testing Notes","pagesAudited":"Pages / Components Audited","toolsUsed":"Tools & Methods Used"},"placeholders":{"pagesAudited":"Home page\nProduct listing\nProduct detail\nCheckout flow\nUser account","toolsUsed":"Axe DevTools\nNVDA + Firefox\nKeyboard-only navigation\nColour contrast analyser","samplingMethodology":"Explain page selection rationale e.g. 'Pages selected to represent all distinct template types, all authenticated journeys, and all primary task flows. Sample includes home, 3 category listing templates, product detail, search, basket, checkout (4 steps), account, and 2 forms.'","userTestingNotes":"E.g. '3 blind users (NVDA + Chrome), 2 keyboard-only users, 1 low-vision user (400% zoom). Sessions 60 min each, task-based usability protocol.'"},"samplingHelper":"Document why these specific pages/screens were chosen. Procurers and courts may challenge findings if the sample is not representative.","userTestingCheckboxLabel":"User testing with disabled users was conducted as part of this audit","userTestingWarning":"⚠ Automated and expert testing detects approximately 30–40% of WCAG issues. User testing with disabled users is best practice and is increasingly required by enterprise procurers and public bodies.","conformanceOptions":{"full":"Full Conformance","partial":"Partial Conformance","non":"Non-Conformance"}},"step3":{"label":"Findings","heading":"Step 3 of 6, Findings","description":"Add every accessibility issue found during your audit. For each finding, enter the WCAG success criterion ID (e.g. 1.4.3), severity, status, a description of the issue, where it was found, and how to fix it. Add all findings before moving to Step 4, the executive summary will be auto-generated from them.","title":"Findings","tableTitle":"Findings Table ({count})","addFinding":"Add Finding","addFindingButton":"+ Add Finding","clearAll":"Clear All","clearAllConfirm":"Clear all {count, plural, one {# finding} other {# findings}}? This cannot be undone.","editFinding":"Edit","deleteFinding":"Delete","duplicateFinding":"Duplicate","newFindingHeading":"New Finding","editFindingHeading":"Edit Finding","saveChanges":"Save Changes","addFindingForm":"Add Finding","cancelButton":"Cancel","fields":{"scId":"SC ID (e.g. 1.4.3)","scName":"SC Name","severity":"Severity","status":"Status","description":"Description","location":"Location (URL / Component)","remediation":"Recommended Remediation","wcagCriteria":"WCAG Criteria Reference"},"placeholders":{"scId":"1.4.3","scName":"Contrast (Minimum)","description":"Describe the accessibility issue in detail...","location":"Https://example.com/checkout, payment form","remediation":"Describe the steps needed to fix this issue...","wcagCriteria":"WCAG 2.2 SC 1.4.3 (Level AA)"},"severityOptions":{"critical":"Critical","major":"Major","minor":"Minor"},"statusOptions":{"fail":"Fail","pass":"Pass","na":"N/A"},"severityScale":{"title":"Severity Scale Definition","subtitle":"Define what Critical / Major / Minor means so all stakeholders and auditors interpret ratings consistently.","acknowledged":"Acknowledged","criticalLabel":"Critical","criticalBody":"Prevents completion of a primary user journey for any assistive technology user (e.g. Keyboard user cannot submit a form; screen reader user cannot navigate to checkout). Blocks using the service at all.","majorLabel":"Major","majorBody":"Significantly impairs a user journey for at least one disability group, but the journey remains completable with workaround or significant difficulty. Or blocks access for a specific disability group while others can proceed.","minorLabel":"Minor","minorBody":"Creates friction or inconvenience but all user journeys remain completable. May affect user experience or efficiency but does not prevent task completion."},"library":{"title":"Common Findings Library","subtitle":"Click any finding to load it into the form. Edit the location and description before saving."},"table":{"headers":{"number":"#","sc":"SC","name":"Name","severity":"Severity","status":"Status","description":"Description","location":"Location","remediation":"Remediation","actions":"Actions"},"emptyTitle":"No findings added yet.","emptySubtitle":"Click “Add Finding” above to begin documenting issues."}},"step4":{"label":"Summary","heading":"Step 4 of 6, Executive Summary","description":"Set the overall conformance verdict and generate a professional summary paragraph from your findings. The auto-generate button reads your findings from the previous step and writes the summary for you, including the exact issue counts.","title":"Executive Summary","overallStatusLabel":"Overall Conformance Status","executiveSummaryLabel":"Executive Summary Text","issueCountsLabel":"Issue Counts","autoGenerate":"Auto-generate from findings","findingsReady":"{count, plural, one {# failing finding ready} other {# failing findings ready}}","noFindingsYet":"No findings yet, go back to Step 3 to add them first","contradiction":{"heading":"⚠ Conformance Contradiction Detected","body":"You have selected <strong>Full Conformance</strong> but this report contains <strong>{count, plural, one {# open failing finding} other {# open failing findings}}</strong>{detail}.","guidance":"Publishing a “fully conformant” accessibility statement while known open failures exist is a <strong>false declaration under the European Accessibility Act</strong> and may be treated as non-compliance by market surveillance authorities. Change the status to <strong>Partial Conformance</strong>, or resolve all failing findings first.","switchButton":"Switch to Partial Conformance"},"noFindingsWarning":"You have selected Full Conformance but have no findings recorded. Add your WCAG success criteria findings in Step 3, even passing criteria should be documented to support this claim.","issueCountLabels":{"critical":"Critical","major":"Major","minor":"Minor"}},"step5":{"label":"Remediation","heading":"Step 5 of 6, Remediation Plan","description":"Set the target date for fixing the issues and name the responsible team or person. Add any notes about your remediation approach, phased delivery, priority order, or dependencies. This appears as the Remediation Timeline section in the final report.","title":"Remediation & Completion","fields":{"remediationNotes":"Remediation Notes","targetDate":"Target Completion Date","responsibleParty":"Responsible Party / Team","retestingPlan":"Retesting & Verification Plan"},"placeholders":{"responsibleParty":"Development Team / Jane Smith","retestingPlan":"E.g. 'Each remediated finding will be re-tested by the auditor within 5 business days of vendor fix confirmation. A re-audit of the full scope will be conducted after all critical and major issues are resolved, targeted for next quarter. Verification by: [Auditor name/org]'","remediationNotes":"Provide any additional context on the remediation plan, prioritisation approach, or phased delivery schedule..."},"retestingHelper":"Without a defined retesting process, there is no mechanism to verify that remediation is effective. Include who will verify fixes and at what stage.","evidenceAppendix":{"title":"Evidence Appendix","subtitle":"Attach evidence vault records to this report. They will appear as an appendix in the exported document.","selectButton":"+ Select from Evidence Vault","loading":"Loading evidence records…","empty":"No evidence attached yet. Go to your Evidence Vault to select records and add them here.","annexLabel":"Annex IV:","wcagLabel":"WCAG:","removeTitle":"Remove"}},"step6":{"label":"Export","title":"Export Report"}},"summary":{"executiveSummary":"Executive Summary","criticalIssues":"Critical Issues","majorIssues":"Major Issues","minorIssues":"Minor Issues","overallConformance":"Overall Conformance"},"report":{"coverTitle":"Web Accessibility Audit Report","coverProductPlaceholder":"Product Name","coverClientPlaceholder":"Client Organisation","logoAlt":"AccessibilityRef.eu, European Accessibility Compliance","labels":{"productUrl":"Product URL","auditDate":"Audit Date","auditor":"Auditor","standards":"Standards","wcagLevel":"WCAG Level","wcagLevelValue":"Level {level}","reportVersion":"Report Version","auditorAndOrg":"{name}, {org}","notSpecified":"Not specified"},"scopeMethodology":"Scope & Methodology","findings":"Findings","remediationPlan":"Remediation Plan","evidenceAppendix":"Appendix: Evidence Vault Records","sectionTitles":{"executiveSummary":"1. Executive Summary","scopeMethodology":"2. Scope & Methodology","findings":"3. Findings ({count})","remediationTimeline":"4. Remediation Timeline","appendix":"5. Appendix"},"scope":{"pagesAudited":"Pages Audited","toolsAndMethods":"Tools & Methods"},"remediation":{"targetDate":"Target Completion Date","responsibleParty":"Responsible Party"},"issueCounts":{"critical":"Critical","major":"Major","minor":"Minor"},"findingsTable":{"noFindings":"No findings recorded.","headers":{"number":"#","sc":"SC","name":"Name","severity":"Severity","status":"Status","description":"Description","location":"Location","remediation":"Remediation"}},"appendix":{"wcagLabel":"WCAG 2.2:","eaaLabel":"European Accessibility Act:","eaaLinkText":"Directive 2019/882","disclaimer":"This report was generated using AccessibilityRef.eu, European Accessibility Compliance. It is provided for informational purposes and does not constitute legal advice. Standards and criteria referenced are as of the audit date stated above."}},"preview":{"checklist":{"heading":"Pre-publication Compliance Checklist","allPassed":"All checks passed","needsAttention":"{count, plural, one {# item needs attention} other {# items need attention}}","intro":"Verify these items before sharing or publishing this report. Incomplete reports may be rejected by enforcement bodies or procurement teams.","items":{"clientProduct":"Client name and product identified","auditDate":"Audit date set","auditorOrg":"Auditor name and organisation provided","annexI":"EAA Annex I section identified","regulation":"Applicable regulation(s) selected","conformanceDeclared":"Overall conformance status declared","conformanceConsistent":"Conformance status consistent (no full conformance with open failures)","scopeDocumented":"Pages / scope audited documented","toolsDocumented":"Testing tools described","summaryWritten":"Executive summary written","remediationDocumented":"Remediation plan documented (for open failures)","samplingDocumented":"Sampling methodology documented","retestingDocumented":"Retesting / verification plan documented","severityAcknowledged":"Severity scale acknowledged","userTesting":"User testing with disabled users conducted or limitation acknowledged"},"accessibilityNote":"Report accessibility: This report will be distributed as a DOCX file. Before sharing, check it with Word’s built-in Accessibility Checker (Review → Check Accessibility) and resolve any flagged issues. Consider also providing an accessible HTML or PDF/UA version for stakeholders using assistive technology."},"title":"Report Preview","proOnlyExport":"Pro only, Upgrade to export","proOnlyExportTitle":"Upgrade to Pro to export documents","exporting":"Exporting…","csvButton":"CSV","sheetsButton":"Google Sheets (.xlsx)"},"actions":{"previous":"Previous","next":"Next","exportWord":"Export as Word (.docx)","exportExcel":"Export as Excel (.xlsx)","exportCsv":"Export Findings CSV","autoSummary":"Auto-generate Summary","startNewReport":"Start New Report","saveFinding":"Save Finding","cancel":"Cancel"},"evidence":{"attachedRecords":"Attached Evidence Records","loading":"Loading evidence records…"},"autoSave":"Auto-saved","autoSummary":{"fullConformance":"The product is fully conformant with the applicable standard.","partialConformance":"The product is partially conformant. Remediation is required for the {count, plural, one {# issue} other {# issues}} listed in this report before full conformance can be claimed.","nonConformance":"The product does not currently conform to the applicable standard. A total of {count, plural, one {# issue must be resolved} other {# issues must be resolved}} before conformance can be claimed.","fallbackProduct":"[Product]","fallbackClient":"[Client]","fallbackAuditor":"[Auditor]","fallbackOrganisation":"[Organisation]","regulationsFallback":"WCAG 2.2 Level {level}","summary":"This accessibility audit of {product} was conducted for {client} on {date} by {auditor}, {organisation}, against {regulations}. The audit covered {pages}. A total of {total, plural, one {# issue was identified} other {# issues were identified}}: {critical} critical, {major} major, and {minor} minor. {conformanceText}","pagesCount":"{count, plural, one {# page} other {# pages}}","pagesFallback":"The pages listed in the Scope section"},"regulations":{"wcag22aa":"WCAG 2.2 AA","eaa":"EAA","ada":"ADA","section508":"Section 508","en301549":"EN 301 549"},"annexOptions":{"ix":"Annex I, Section IX, E-commerce services and electronic communications services","x":"Annex I, Section X, Banking services for consumers","xi":"Annex I, Section XI, Passenger transport services","vii":"Annex I, Section VII, Audio-visual media services","viii":"Annex I, Section VIII, E-books and dedicated reading software","v":"Annex I, Section V, Self-service terminals","vi":"Annex I, Section VI, Electronic communications services","iii":"Annex I, Section III, General-purpose computer hardware and operating systems","ii":"Annex I, Section II, Smartphones","other":"Other, specify in notes"},"library":{"items":{"1.1.1":{"scName":"Non-text Content","description":"Images are missing alt attributes. Screen reader users receive no information about the image content.","location":"All pages, <img> elements","remediation":"Add descriptive alt text to all informative images. Use alt=\"\" for decorative images. Ensure functional images (buttons, links) describe the action.","wcagCriteria":"SC 1.1.1, Level A"},"1.3.1":{"scName":"Info and Relationships","description":"Table data is marked up without <th> elements or scope attributes. Screen readers cannot determine column or row headers.","location":"Data tables throughout the site","remediation":"Add <th scope=\"col\"> for column headers and <th scope=\"row\"> for row headers. Add a <caption> element to identify the table's purpose.","wcagCriteria":"SC 1.3.1, Level A"},"1.3.5":{"scName":"Identify Input Purpose","description":"Personal data input fields (name, email, phone, address) are missing autocomplete attributes. Assistive technologies and password managers cannot infer field purpose.","location":"Registration, checkout, and contact forms","remediation":"Add autocomplete attributes to all personal data fields per WHATWG HTML specification: name, email, tel, street-address, postal-code, country, etc.","wcagCriteria":"SC 1.3.5, Level AA"},"1.4.3":{"scName":"Contrast (Minimum)","description":"Body text and/or UI text does not meet the 4.5:1 contrast ratio against the page background.","location":"Multiple pages, body copy and small labels","remediation":"Increase foreground colour darkness or lighten the background to achieve a minimum 4.5:1 ratio for normal text (under 18pt / 14pt bold). Use a contrast checker to verify all colour combinations.","wcagCriteria":"SC 1.4.3, Level AA"},"1.4.11":{"scName":"Non-text Contrast","description":"Interactive UI components (buttons, inputs, checkboxes, focus rings) have insufficient contrast against adjacent colours.","location":"Form controls and interactive elements","remediation":"Ensure UI component boundaries and states (focus ring, active, disabled) achieve at least 3:1 contrast against adjacent colours. Review disabled state contrast separately.","wcagCriteria":"SC 1.4.11, Level AA"},"2.1.1":{"scName":"Keyboard","description":"Interactive elements are not operable using keyboard alone. Mouse-specific event handlers (onclick on non-semantic elements) are used without keyboard equivalents.","location":"Navigation menu, custom dropdowns, modal trigger buttons","remediation":"Replace <div> click handlers with semantic <button> elements. Add keyboard event handlers (keydown Enter/Space) to any remaining custom interactive elements. Test the full user journey with Tab, Enter, Space, and Escape only.","wcagCriteria":"SC 2.1.1, Level A"},"2.4.3":{"scName":"Focus Order","description":"Keyboard focus moves in an illogical order. Positive tabindex values on multiple elements create a broken tab sequence that does not follow the visual or reading order.","location":"Header navigation and modal dialog","remediation":"Remove all positive tabindex values. Use tabindex=\"0\" only when making non-semantic elements focusable. Reorder DOM elements to match the intended reading/interaction order.","wcagCriteria":"SC 2.4.3, Level A"},"2.4.6":{"scName":"Headings and Labels","description":"Heading levels are skipped (e.g. H1 to H3 with no H2). Form fields have visible labels that are not programmatically associated with the input.","location":"Blog articles and contact form","remediation":"Use heading levels sequentially without skipping. Associate labels with inputs using the for/id attribute pair or by wrapping the input inside the <label> element.","wcagCriteria":"SC 2.4.6, Level AA"},"2.4.7":{"scName":"Focus Visible","description":"CSS removes the default browser focus outline (outline: none / outline: 0) without providing a custom focus indicator. Keyboard users cannot determine which element has focus.","location":"Site-wide CSS stylesheet","remediation":"Remove any CSS that suppresses focus rings. Implement a custom:focus-visible style with sufficient contrast (3:1 minimum, SC 1.4.11). Test with keyboard navigation only.","wcagCriteria":"SC 2.4.7, Level AA"},"3.3.1":{"scName":"Error Identification","description":"Form validation errors are indicated by colour alone (red border). Screen reader users and users who cannot perceive colour do not receive error information.","location":"Contact form and registration form","remediation":"Add visible error text adjacent to the invalid field (not just a border colour). Programmatically associate the error message with the input using aria-describedby. Consider aria-invalid=\"true\" on the field.","wcagCriteria":"SC 3.3.1, Level A"},"3.3.2":{"scName":"Labels or Instructions","description":"Required fields are indicated by an asterisk (*) with no explanatory text. Date fields require a specific format (DD/MM/YYYY) that is not communicated to users.","location":"All form pages","remediation":"Add a legend or note: \"Fields marked * are required\". State format requirements in the label or hint text adjacent to the input, not just in placeholder text (which disappears on focus).","wcagCriteria":"SC 3.3.2, Level A"},"4.1.2":{"scName":"Name, Role, Value","description":"Custom interactive components (carousel controls, accordion triggers, tab panels) do not expose their role, state, or name to assistive technologies.","location":"Homepage carousel, FAQ accordion","remediation":"Add appropriate ARIA roles (role=\"button\", role=\"tab\", role=\"region\") and state attributes (aria-expanded, aria-selected, aria-controls, aria-labelledby). Prefer native HTML elements where possible.","wcagCriteria":"SC 4.1.2, Level A"},"4.1.3":{"scName":"Status Messages","description":"Dynamic status messages (form success, cart update, toast notifications) are injected into the DOM but not announced to screen readers.","location":"Add to cart, form submission confirmation","remediation":"Add role=\"status\" (for non-urgent) or role=\"alert\" (for urgent) to the container that receives the injected message. Alternatively use aria-live=\"polite\" or aria-live=\"assertive\".","wcagCriteria":"SC 4.1.3, Level AA"},"2.5.3":{"scName":"Label in Name","description":"Accessible names for interactive elements do not contain the visible label text. Voice control users who speak the visible label cannot activate the control.","location":"Navigation buttons with icon + text","remediation":"Ensure the accessible name (aria-label or text content) includes the visible label text. If using aria-label, start the label with the visible text (e.g. Aria-label=\"Search products\" for a button labelled \"Search\").","wcagCriteria":"SC 2.5.3, Level A"},"1.4.4":{"scName":"Resize Text","description":"At 200% browser zoom, page content overflows horizontally. Text set in px units does not resize with browser text size settings.","location":"Header navigation and hero section","remediation":"Use relative units (rem, em) for font sizes to respect user browser settings. Test at 200% zoom and with browser text size set to maximum, no content should be lost or require horizontal scrolling.","wcagCriteria":"SC 1.4.4, Level AA"}}},"samplePreview":{"toolName":"Compliance Report","description":"The Compliance Report generates an audit document with cover page, executive summary, detailed findings table, remediation timeline, and legislation references. Issued under the AccessibilityRef brand."},"exportPanel":{"toolName":"Compliance Report Builder","labels":{"client":"Client","productService":"Product / service","auditor":"Auditor","auditDate":"Audit date","overallConformance":"Overall conformance","wcagLevel":"WCAG level","wcagLevelValue":"WCAG 2.2 Level {level}","regulations":"Regulations","criticalIssues":"Critical issues","majorIssues":"Major issues","minorIssues":"Minor issues","totalFindings":"Total findings","summaryExcerpt":"Executive summary (excerpt)","urlAudited":"URL audited","auditorOrganisation":"Auditor organisation","reportVersion":"Report version","regulationsCovered":"Regulations covered","wcagConformanceLevel":"WCAG conformance level","pagesAudited":"Pages audited","toolsUsed":"Tools used","samplingMethodology":"Sampling methodology","userTestingWithDisabledUsers":"User testing with disabled users","userTestingNotes":"User testing notes","severityScaleDefined":"Severity scale defined","targetRemediationDate":"Target remediation date","responsibleParty":"Responsible party","retestingPlan":"Re-testing plan"},"values":{"yes":"Yes","no":"No","fullConformance":"Full conformance","partialConformance":"Partial conformance","nonConformance":"Non-conformance"},"summary":{"withProduct":"{product}: {count, plural, one {# finding} other {# findings}}, {conformance} conformance","incomplete":"Complete the form above to enable export"},"sections":{"auditOverview":"1. Audit overview","executiveSummary":"2. Executive summary","findingsSummary":"3. Findings summary","findingsDetail":"4. Findings detail","methodology":"5. Methodology","remediationPlan":"6. Remediation plan"},"findingsHeaders":{"number":"#","wcagSc":"WCAG SC","severity":"Severity","status":"Status","description":"Description"},"docxLabel":"Evidence-stamped Word","docxHint":"With audit ID + footer","jsonLabel":"JSON","jsonHint":"For re-processing","documentTitle":"Accessibility Compliance Report","documentSubtitle":"{product}, prepared for {client}"}},"component-library":{"meta":{"title":"Accessible Component Library","description":"Copy-paste accessible UI components with WCAG-compliant ARIA, keyboard interaction, and focus management. Each component includes a live preview, code, and implementation guidance."},"header":{"title":"Accessible Component Library","subtitle":"Copy-paste accessible UI components with WCAG-compliant ARIA, keyboard interaction, and focus management.","badge":"Pro Tool"},"components":{"skipLink":"Skip to Main Content","breadcrumb":"Breadcrumb Navigation","buttonVariants":"Button Variants","formInput":"Labelled Form Input","accordion":"Accordion / Disclosure","tabPanel":"Tab Panel","alert":"Alert / Status Messages","progressBar":"Progress Bar","dataTable":"Accessible Data Table","loadingSpinner":"Loading Spinner","tooltip":"Tooltip","focusTrap":"Modal Dialog (Focus Trap)","liveAnnouncer":"ARIA Live Announcer","srOnly":"Sr-only Utility Class","figure":"Figure with Caption"},"categories":{"all":"All","navigation":"Navigation","controls":"Controls","forms":"Forms","feedback":"Feedback","data":"Data","utilities":"Utilities","media":"Media"},"labels":{"wcag":"WCAG","usage":"Usage guidance","code":"Code","preview":"Preview","livePreview":"Live Preview","howToUse":"How to use","copyCode":"Copy code","copy":"Copy","copied":"Copied!","copiedCheck":"Copied ✓","showCode":"Show code","hideCode":"Hide code","componentsShown":"{count} components","searchPlaceholder":"Search components…"},"proGate":{"feature1":"Copy-paste accessible HTML/CSS patterns: forms, modals, navigation, buttons, and more","feature2":"Live previews for every component","feature3":"WCAG 2.2 success criteria referenced for each pattern","feature4":"EAA compliance notes included"},"previews":{"skipLinkText":"Skip to main content","skipLinkHint":"(focus the skip link to see it appear)","buttonPrimary":"Primary Action","buttonSecondary":"Secondary","buttonDestructive":"Destructive","buttonDisabled":"Disabled","formEmailLabel":"Email address","formRequiredSr":"(required)","formEmailPlaceholder":"Name@example.com","formEmailError":"Email is required","accordionQ1":"What is WCAG 2.1 AA?","accordionA1":"WCAG 2.1 AA is the accessibility standard required by the EAA and EN 301 549, covering 50 success criteria.","accordionQ2":"What is the EAA deadline?","accordionA2":"The European Accessibility Act applies to new products and services from 28 June 2025.","alertErrorPrefix":"Error:","alertErrorBody":"Your session has expired. Please sign in again.","alertSuccessPrefix":"Success:","alertSuccessBody":"Your changes have been saved.","alertNotePrefix":"Note:","alertNoteBody":"This feature requires WCAG AA compliance.","tableAriaLabel":"WCAG conformance levels","tableCaption":"WCAG conformance levels and their descriptions","tableColLevel":"Level","tableColCriteria":"Criteria","tableColRequired":"Required by EAA","tableYes":"Yes","tableNo":"No","tableAACount":"18 additional","tableAAACount":"28 additional","progressLabel":"Upload progress","progressRangeAria":"Adjust demo progress","tabsAriaLabel":"Report sections","tabOverview":"Overview","tabDetails":"Details","tabReferences":"References","tabContentBefore":"Content for the","tabContentAfter":"Tab.","loadingAria":"Loading","loadingLabel":"Loading results…","breadcrumbAria":"Breadcrumb","breadcrumbHome":"Home","breadcrumbTools":"Tools","breadcrumbCurrent":"Component Library","tooltipQuestion":"What is WCAG?","tooltipBody":"WCAG 1.3.1, information conveyed visually must also be available to assistive technologies.","tooltipCloseSr":"Close dialog","dialogOpen":"Open Dialog","dialogTitle":"Confirm Action","dialogBody":"This dialog traps focus inside. Press Escape or click Cancel to close.","dialogCancel":"Cancel","dialogConfirm":"Confirm","announcerHint":"(Visually hidden, screen readers announce its contents)","iconButtonHint":"Icon button, visible label is sr-only but announced as \"Close dialog\"","figureCaption":"Figure 1: Example bar chart showing WCAG issue distribution across 10 pages.","figurePlaceholder":"[image placeholder]"},"definitions":{"skipLink":{"wcag":"SC 2.4.1 Bypass Blocks (Level A)","description":"The first focusable element on any page, allowing keyboard and screen reader users to skip repeated navigation blocks.","usage":"Place as the very first element inside <body>. The link is visually hidden until focused, keyboard-only users trigger it by pressing Tab on page load."},"breadcrumb":{"wcag":"SC 2.4.8 Location (Level AAA) / best practice","description":"A navigational aid showing the user's current location within the site hierarchy.","usage":"Wrap in a <nav> with aria-label='Breadcrumb'. Mark the last item with aria-current='page'. Use an ordered list, the DOM order communicates hierarchy."},"buttonVariants":{"wcag":"SC 1.4.3 Contrast / SC 2.1.1 Keyboard / SC 2.4.13 Focus Appearance / SC 4.1.2 Name (Level A/AA)","description":"Primary, secondary, destructive, and disabled button states with WCAG AA contrast and visible focus rings. SC 2.4.13 (Focus Appearance, Level AA, new in WCAG 2.2) requires that the focus indicator encloses the component with a perimeter ≥ the unfocused component's perimeter and ≥ 2 CSS pixels thick, OR achieves ≥3:1 contrast between focused and unfocused states against all adjacent colours. Verify that focus:ring colours meet this threshold against your page background.","usage":"Always use a native <button> element for interactive controls (not <div>). Disabled buttons should still be discoverable, use aria-disabled='true' rather than the disabled attribute where possible to keep them in focus order."},"formInput":{"wcag":"SC 1.3.1 Info and Relationships / SC 3.3.1 Error ID / SC 3.3.2 Labels (Level A)","description":"Text input with a programmatically associated label, required indicator, and inline error message using aria-describedby.","usage":"Click outside the field without entering a value to trigger the error state. Error messages use role='alert' so screen readers announce them immediately."},"accordion":{"wcag":"SC 4.1.2 Name Role Value (Level A)","description":"Collapsible content panels using the Disclosure pattern. Uses aria-expanded and aria-controls to communicate state to assistive technologies.","usage":"Each trigger button is aria-expanded='true/false'. The panel it controls is linked via aria-controls (matching the panel's id). Use hidden rather than display:none so assistive tech skips hidden content."},"tabPanel":{"wcag":"SC 4.1.2 Name Role Value (Level A)","description":"A fully accessible tab interface using the ARIA Tabs pattern with roving tabindex.","usage":"Tabs use role='tablist', role='tab', and role='tabpanel'. Active tab has tabIndex=0; inactive tabs have tabIndex=-1 (roving tabindex). Arrow key navigation should ideally be added for full ARIA compliance."},"alert":{"wcag":"SC 4.1.3 Status Messages (Level AA)","description":"Live region alerts for errors, success, and informational messages. Role='alert' interrupts; role='status' is polite.","usage":"Use role='alert' for critical errors (interrupts current screen reader speech). Use role='status' for non-critical success messages. Never use alert() or browser dialogs, they are inaccessible."},"progressBar":{"wcag":"SC 4.1.2 Name Role Value (Level A)","description":"An ARIA-compliant progress indicator with a visible label, live percentage announcement, and a draggable demo range.","usage":"Role='progressbar' requires aria-valuenow, aria-valuemin, and aria-valuemax. Link it to a visible label with aria-labelledby. Use aria-live on the percentage span so screen readers announce progress changes."},"dataTable":{"wcag":"SC 1.3.1 Info and Relationships (Level A)","description":"A data table with proper column headers using scope='col', row headers using scope='row', and an accessible caption.","usage":"Use <th scope='col'> for column headers and <th scope='row'> for row headers. Always include a <caption> (it can be visually hidden). Use aria-label on the table only when a visible caption isn't practical."},"loadingSpinner":{"wcag":"SC 4.1.3 Status Messages (Level AA)","description":"An animated loading indicator with a visually hidden status announcement for screen readers.","usage":"The spinner itself is aria-hidden. A role='status' element with the loading text is accessible but visually hidden until needed. Never rely on colour alone to indicate loading."},"tooltip":{"wcag":"SC 1.3.1 / SC 1.4.13 Content on Hover or Focus (Level AA)","description":"A tooltip triggered on both hover and keyboard focus, linked to its trigger with aria-describedby.","usage":"Tooltips must appear on focus (not just hover), SC 1.4.13 requires hoverable and dismissible content. Link with aria-describedby. Never put essential information only in a tooltip."},"focusTrap":{"wcag":"SC 2.1.2 No Keyboard Trap / SC 4.1.2 Name Role Value (Level A)","description":"An accessible modal dialog with role='dialog', aria-modal='true', focus trapped inside, and Escape key to dismiss.","usage":"On open: move focus to the dialog (or first focusable element inside). Trap Tab/Shift+Tab within the dialog. On close: return focus to the element that triggered it."},"liveAnnouncer":{"wcag":"SC 4.1.3 Status Messages (Level AA)","description":"A visually hidden live region for announcing dynamic page changes to screen reader users without moving focus.","usage":"Mount once near the top of your app. Update its text content from anywhere to trigger an announcement. 'polite' waits for the user to finish; 'assertive' interrupts, use assertive only for critical errors."},"srOnly":{"wcag":"SC 1.3.1 / SC 4.1.2, visual presentation vs accessibility","description":"CSS-only class to hide content visually while keeping it accessible to screen readers. Essential for supplemental context.","usage":"Use for: icon-only buttons (add a label), table captions, extra context for form fields, and 'visually hidden headings' to label sections. Never use display:none or visibility:hidden, these hide from AT too."},"figure":{"wcag":"SC 1.1.1 Non-text Content (Level A)","description":"An image wrapped in a <figure> with a visible <figcaption> and descriptive alt text. The alt text and caption serve different purposes.","usage":"Alt text = concise description for those who cannot see the image. Caption = supplemental context visible to all. If the caption fully describes the image, the alt text can be empty (alt='') to avoid duplication."}}},"conformity-generator":{"meta":{"title":"EU Declaration of Conformity Generator","description":"Generate the mandatory legal document required by Annex IV of Directive (EU) 2019/882, the European Accessibility Act."},"features":["Annex IV compliant structure","Article 20 legal alignment","Styled print-ready document"],"header":{"badges":{"annexIv":"Annex IV","article20":"Article 20 EAA","enStandard":"EN 301 549 V3.2.1"},"title":"EU Declaration of Conformity Generator","subtitle":"Generate the mandatory legal document required by Annex IV of Directive (EU) 2019/882, the European Accessibility Act."},"entityLabel":{"manufacturer":"Manufacturer","serviceProvider":"Service Provider","manufacturerLower":"Manufacturer","serviceProviderLower":"Service provider"},"education":{"whatIsTitle":"What is this document and why do you need it?","whatIsBody":"The EU Declaration of Conformity is a mandatory legal document under the European Accessibility Act. It formally declares that your product or service meets the accessibility requirements of Directive (EU) 2019/882. Its structure is defined precisely in <strong>Annex IV</strong> of that Directive, this tool generates a document that follows that structure exactly.","showLess":"Show less ▲","fullExplanation":"Full explanation ▼","whatIsAnnexIvTitle":"What is Annex IV?","whatIsAnnexIvBody":"<strong>Annex IV</strong> of Directive (EU) 2019/882 is the legislative appendix that defines the exact structure and mandatory content of the EU Declaration of Conformity. It specifies seven elements that every valid declaration must include, from product identification and manufacturer details, through to the specific harmonised standards used to demonstrate conformance. Without following Annex IV, a declaration, even one that makes the right claims, is not legally valid under EAA.","whatIsAnnexIvBody2":"Market surveillance authorities across all 27 EU member states have the power to demand that you produce this document on request. If you cannot produce a compliant Annex IV declaration, it is treated as evidence of non-conformity.","article20Title":"Article 20, the legal obligation to produce it","article20Body":"<strong>Article 20 of the EAA</strong> creates the specific legal duty to draw up this document. It states that manufacturers shall <em>\"draw up a written EU declaration of conformity and keep it at the disposal of national authorities\"</em> for a minimum of five years after the product is placed on the market, or five years after the last service transaction for service providers.","article20Body2":"The declaration is not a one-time task. It must be continuously updated whenever a product or service changes in a way that affects its conformity with accessibility requirements. Each update should be re-signed and re-dated.","enStandardTitle":"Why EN 301 549 is referenced, and what it means legally","enStandardBody":"<strong>EN 301 549 V3.2.1</strong> is the European harmonised standard that translates the EAA's broad accessibility obligations into specific, testable technical requirements. For digital products and services, EN 301 549 incorporates <strong>WCAG 2.1 Level AA</strong> by reference. When you cite EN 301 549 in your declaration, you are stating that your product has been tested against and meets those technical specifications.","enStandardBody2":"This matters legally: the European Commission has published EN 301 549 in the Official Journal as a harmonised standard under the EAA. Conformance with EN 301 549 creates a legal <em>presumption of conformity</em> with the corresponding EAA requirements, meaning a regulator must disprove your conformity rather than you having to prove it from scratch. This presumption is your primary legal protection.","whoMustTitle":"Who must produce this document","whoMust":{"manufacturers":"Manufacturers","manufacturersDesc":"Of hardware products in EAA scope: computers, phones, tablets, ATMs, payment terminals, e-readers, self-service kiosks, consumer electronics.","software":"Software developers and publishers","softwareDesc":"Placing software on the EU market that falls within EAA scope.","serviceProviders":"Service providers","serviceProvidersDesc":"Offering EAA-covered digital services: e-commerce, banking, e-books, audio-visual media, electronic communications, passenger transport booking.","importers":"Importers and distributors","importersDesc":"Who place products on the EU market and bear responsibility for conformity when the original manufacturer is outside the EU."},"microExemption":"<strong>Micro-enterprise exemption (Article 4(4)):</strong> Micro-enterprises providing services, defined as fewer than 10 employees AND annual turnover or balance sheet not exceeding €2 million, are exempt from certain EAA obligations. This exemption does not apply to manufacturers of products.","sevenElementsTitle":"The 7 mandatory elements of Annex IV","elements":{"1":{"title":"Product identification","desc":"Model number, type, batch or serial number, or any other element allowing unique identification and traceability of the product or service."},"2":{"title":"Manufacturer / representative name and address","desc":"The full legal name and registered address of the manufacturer or their EU authorised representative."},"3":{"title":"Sole responsibility statement","desc":"A mandatory declaration that the conformity statement is issued under the sole responsibility of the manufacturer."},"4":{"title":"Object of the declaration","desc":"A description of the product or service that is being declared conformant, sufficient for traceability. May include URLs, version numbers, scope boundaries, and exclusions."},"5":{"title":"Conformity with Directive (EU) 2019/882","desc":"An explicit statement that the object conforms with the EAA Directive and its accessibility requirements, specifying the WCAG level achieved."},"6":{"title":"Harmonised standards referenced","desc":"References to EN 301 549 V3.2.1 (and any other applicable technical specifications) used to demonstrate conformity, plus the assessment methodology."},"7":{"title":"Additional information","desc":"Signed for and on behalf of the manufacturer or service provider: place and date of issue, name and function of signatory, and a physical or digital signature."}}},"form":{"legalNoticeTitle":"⚠ Legal notice, Declaration scope must cover only fully conformant elements","legalNoticeBody":"An EU Declaration of Conformity is a legal declaration that the product or service <strong>is</strong> conformant, not that it aspires to be. Issuing a DoC for a partially conformant product is a false declaration under Directive 2019/882 and may be treated as a market surveillance non-conformity. If there are open accessibility failures, <strong>exclude them from the DoC scope</strong> using the \"Scope Exclusions\" field below rather than noting exceptions within the body of the declaration.","confirmNonConformances":"I confirm there are open non-conformances that I have excluded from the scope of this declaration in the \"Scope Exclusions\" field below","section1":{"title":"Product / Service Identification","subtitle":"Annex IV element 1, unique identification for traceability","digitalService":"Digital Service","physicalProduct":"Physical Product","productName":"Product / Service Name","productNamePlaceholder":"E.g. MyBank Online Banking Platform","modelVersion":"Model / Version / URL","modelVersionPlaceholder":"E.g. V4.2.1 / https://example.com","eaaCategory":"EAA Category","annexISection":"Annex I Section (auto-filled, edit if needed)","annexISectionHint":"The Declaration must reference the specific section of Annex I that applies to your product/service. Auto-filled from your category selection above."},"section2":{"title":"{entityLabel} Details","subtitle":"Annex IV element 2, legal name and registered address","manufacturer":"Manufacturer","serviceProvider":"Service Provider","legalName":"Legal Name of Organisation","legalNamePlaceholder":"Full registered legal name","registeredAddress":"Registered Address","registeredAddressPlaceholder":"Street, city, postcode","nationalLaw":"National Transposition Law","nationalLawRequired":"(required for regulatory validity)","nationalLawPlaceholder":"E.g. Barrierefreiheitsstärkungsgesetz (BFSG), Germany","nationalLawHint":"Enforcement bodies review national law, not the EU Directive directly. Cite the national law that transposes Directive 2019/882/EU in your jurisdiction.","memberState":"EU Member State","memberStatePlaceholder":"E.g. Ireland","accessibilityContact":"Accessibility Contact","accessibilityContactNote":"For complaints & enquiries","accessibilityContactPlaceholder":"Accessibility@example.com","statementUrl":"Accessibility Statement URL","statementUrlRequired":"(required, cross-reference in DoC section 6)","statementUrlPlaceholder":"Https://www.example.com/accessibility","statementUrlHint":"The DoC must cross-reference the corresponding Accessibility Statement. Market surveillance authorities verify this link."},"section4":{"title":"Object of the Declaration","subtitle":"Annex IV element 4, what exactly is being declared conformant","description":"Description","descriptionPlaceholder":"Describe the product or service with enough detail for traceability, include URLs, platform, version, and the scope of what is covered.","exclusions":"Exclusions from scope","exclusionsOptional":"(optional)","exclusionsPlaceholder":"E.g. Third-party embedded content; legacy PDF archive pre-dating June 2025","technicalFile":"Technical File Location / Reference","technicalFilePlaceholder":"E.g. Internal document store ref: DOC-ACC-2026-01 (retained per Article 20, 5-year obligation)","technicalFileHint":"Article 20 requires retention of the technical file (audit reports, ACR, test results) for 5 years. Document where this file is held for regulatory inspection."},"section56":{"title":"Standards & Conformance","subtitle":"Annex IV elements 5 & 6, the technical basis for your declaration","wcagLevel":"WCAG Conformance Level","levelAARequired":"Level AA, Required by law","levelAAAEnhanced":"Level AAA, Improved","standardVersion":"Harmonised Standard Version","versionMismatch":"⚠ Version mismatch: the selected standard and WCAG level are inconsistent. Regulators may flag this as an invalid declaration.","versionMatch":"✓ {standard} maps to {wcag} Level AA as its web content standard.","presumptionNoticeStrong":"Presumption of conformity notice:","presumptionNoticeBody":"EN 301 549 V4.1.1 is not yet listed in the OJEU harmonised standards list. Citing it does not provide a presumption of conformity under Article 15 EAA. The exported document will include a note confirming V3.2.1 compliance is also satisfied. Consider citing both V3.2.1 and V4.1.1 to demonstrate both regulatory conformity and current best practice.","presumptionNotice":"Presumption of conformity notice: EN 301 549 V4.1.1 is not yet listed in the OJEU harmonised standards list. Citing it does not provide a presumption of conformity under Article 15 EAA. The exported document will include a note confirming V3.2.1 compliance is also satisfied. Consider citing both V3.2.1 and V4.1.1 to demonstrate both regulatory conformity and current best practice.","methodology":"Assessment Methodology"},"section7":{"title":"Signatory & Issue Details","subtitle":"Annex IV element 7, who signs it, where, and when","placeOfIssue":"Place of Issue","placeOfIssuePlaceholder":"City","dateOfIssue":"Date of Issue","nextReviewDate":"Next Review Date","nextReviewDateOptional":"(optional but recommended)","signatoryName":"Signatory Name","signatoryNamePlaceholder":"Full name","roleFunction":"Role / Function","roleFunctionPlaceholder":"E.g. Chief Compliance Officer","signatoryWarning":"⚠ The DoC must be signed by a person with legal authority to bind the organisation (e.g. CEO, Managing Director, CDO, or Legal Representative). A product manager or developer does not have sufficient authority to sign an Annex IV declaration."},"technicalFileChecklist":{"title":"Technical File, Article 20 Retention Checklist","intro":"The following documents must be retained for 5 years from the date of this DoC and made available to market surveillance authorities on request:","items":["Accessibility Conformance Report / VPAT (ACR), the test evidence underlying this declaration","Audit report or self-assessment results with test methodology and tool outputs","Published Accessibility Statement (URL archived)","Disproportionate burden assessments (if any burden claims are made)","Supply chain ACRs / VPATs for third-party embedded components","This signed EU Declaration of Conformity"]}},"validation":{"productNameLabel":"Product / Service Name","manufacturerNameLabel":"Legal Name of Organisation","manufacturerAddressLabel":"Registered Address","objectDescriptionLabel":"Object of the Declaration","signerNameLabel":"Signatory Name","signerRoleLabel":"Signatory Function","placeLabel":"Place of Issue"},"preview":{"title":"Document Preview","exportWord":"Export Word (.docx)","exportWordTitle":"Upgrade to Pro to export documents","printPdf":"Print / PDF","copyText":"Copy text","copied":"Copied!","proOnly":"Pro only, Upgrade to export","requiredFieldsMissing":"Required fields missing"},"document":{"docTitle":"EU Declaration of Conformity","docSubtitle":"Drawn up in accordance with Annex IV of Directive (EU) 2019/882 (European Accessibility Act)","directiveAnnexHeader":"Directive (EU) 2019/882, Annex IV","section1Title":"Product / Service Identification","section2Title":"{entityLabel}","section3Title":"Declaration of Sole Responsibility","section3Body":"This declaration of conformity is issued under the sole responsibility of the {entityLabel}.","section4Title":"Object of the Declaration","section5Title":"Conformity Statement","section5Body":"The object of the declaration described above is in conformity with the relevant Union harmonisation legislation: Directive (EU) 2019/882 (European Accessibility Act). Conformance level achieved: WCAG {level} as incorporated by reference in EN 301 549.","section5Lead":"The object of the declaration described above is in conformity with the relevant Union harmonisation legislation:","section5DirectiveStrong":"Directive (EU) 2019/882","section5Middle":"(European Accessibility Act). Conformance level achieved:","section5End":"As incorporated by reference in EN 301 549.","section6Title":"Harmonised Standards Referenced","section7Title":"Signatory","section8Title":"Technical File (Article 20)","retentionNotice":"This declaration must be retained for a minimum of five years from the date of issue and made available to market surveillance authorities on request (Article 20, Directive (EU) 2019/882).","retentionNoticeShort":"This declaration must be retained for a minimum of five years from the date of issue and made available to market surveillance authorities on request, Article 20, Directive (EU) 2019/882.","signature":"Signature: ___________________________","signatureLabel":"Signature","signatureLine":"___________________________","labels":{"name":"Name","modelVersion":"Model / Version","modelVersionUrl":"Model / Version / URL","category":"Category","type":"Type","legalName":"Legal Name","address":"Address","country":"Country","accessibilityContact":"Accessibility Contact","exclusions":"Exclusions","assessment":"Assessment","assessmentMethodology":"Assessment Methodology","correspondingStatement":"Corresponding Accessibility Statement:","statementMissing":"[Accessibility Statement URL, required]","signedFor":"Signed for and on behalf of","placeAndDate":"Place and date of issue","nextReviewDate":"Next review date","function":"Function"},"placeholders":{"productName":"Product/Service Name","modelUrl":"Model / URL","modelVersionUrl":"Model / Version / URL","category":"Category","typeLabel":"Type","organisationName":"Organisation Name","registeredAddress":"Registered Address","contactEmail":"Contact Email","contactEmailOrAddress":"Contact Email or Address","objectDescription":"Description of the product or service","objectDescriptionLong":"Description of the product or service being declared conformant","organisation":"Organisation","place":"Place","placeDate":"Place, Date","signatoryName":"Signatory Name","functionTitle":"Function / Title","testingMethod":"Testing method","technicalFileLocation":"Document reference or storage location, see Article 20 5-year retention obligation"},"productLabel":"Product","serviceLabel":"Service","v411Note":"Note on harmonised standard status: EN 301 549 V4.1.1 (2024-11) references WCAG 2.2 and represents current best practice. However, as of the date of this declaration, V4.1.1 has not yet been listed in the Official Journal of the European Union (OJEU) as a harmonised standard under Directive 2019/882. Accordingly, this declaration does not benefit from the presumption of conformity under Article 15 EAA. The declarant confirms that conformance with EN 301 549 V3.2.1 (the current OJEU harmonised standard) is also satisfied.","technicalFileLocationLabel":"Technical file location/reference: {value}","technicalFileBody":"The technical file must include: the ACR/VPAT, audit reports and test evidence, the published Accessibility Statement, disproportionate burden assessments (if applicable), supply chain ACRs, and this signed DoC. It must be made available to market surveillance authorities promptly on request.","plainTextHeader":"EU DECLARATION OF CONFORMITY","plainTextDrawnUp":"Drawn up in accordance with Annex IV of Directive (EU) 2019/882 (European Accessibility Act)","plainTextSection1Title":"PRODUCT / SERVICE IDENTIFICATION","plainTextSection3Title":"DECLARATION OF SOLE RESPONSIBILITY","plainTextSection4Title":"OBJECT OF THE DECLARATION","plainTextExclusions":"Exclusions from scope","plainTextSection5Title":"CONFORMITY STATEMENT","plainTextSection5Body":"The object of the declaration described above is in conformity with the relevant Union\nharmonisation legislation: Directive (EU) 2019/882 (European Accessibility Act).\nConformance level achieved: WCAG {level} as incorporated by reference in EN 301 549.","plainTextSection6Title":"HARMONISED STANDARDS REFERENCED","plainTextAssessmentMethodology":"Assessment methodology","plainTextSection7Title":"SIGNATORY","plainTextSignedFor":"Signed for and on behalf of","plainTextPlaceAndDate":"Place and date of issue","plainTextValidUntil":"Declaration valid until / last reviewed","plainTextRetentionNotice":"This declaration must be retained for a minimum of five years from the date of issue\nand made available to market surveillance authorities on request (Article 20, Directive (EU) 2019/882).","printTitle":"EU Declaration of Conformity, {name}","printDraft":"Draft"},"afterGenerate":{"title":"After you generate this declaration, what to do next","items":{"1":{"title":"Have it reviewed","body":"This tool generates a structurally compliant document, but the substance of your conformity claims, particularly in sections 4, 5, and 6, should be reviewed by a legal or accessibility professional before formal issuance. A declaration that overstates conformity is a legal liability."},"2":{"title":"Sign it","body":"The declaration must be signed by an authorised representative of your organisation. A digital signature or wet ink signature on a printed copy are both acceptable depending on your national implementation of the EAA."},"3":{"title":"Retain for at least 5 years","body":"Under Article 20(2), manufacturers must keep the declaration available for market surveillance authorities for a minimum of five years after the product is placed on the market. For service providers, the five-year period runs from the date of the last service transaction."},"4":{"title":"Publish it alongside your Accessibility Statement","body":"For digital services, it is best practice, and increasingly expected by regulators, to link your EU Declaration of Conformity from your Accessibility Statement page, or to publish it at a stable URL (e.g. /accessibility-conformity-declaration)."},"5":{"title":"Update it when you make significant changes","body":"Any change that affects the conformity of your product or service, a major release, a new feature set, a platform migration, a rebranding, requires the declaration to be updated and re-signed with a new date."}}},"evidence":{"toolName":"EU Declaration of Conformity Generator","title":"EU Declaration of Conformity","subtitleFormat":"{productName}, {manufacturerName}","summaryWithProduct":"Declaration for {productName} ({category})","summaryEmpty":"Complete the form above to enable export","results":{"productName":"Product / service name","productModel":"Product model / version","category":"Category","type":"Type","manufacturer":"Manufacturer","country":"Country","conformanceLevel":"Conformance level","harmonisedStandard":"Harmonised standard","testingMethod":"Testing method","openNonConformances":"Open non-conformances","signatory":"Signatory","declarationDate":"Declaration date","openYes":"Yes, documented separately","openNo":"None declared","service":"Service","product":"Product","wcagLevelFormat":"WCAG 2.x Level {level}","emDash":","},"docx":{"section1Heading":"1. Product / service","section2Heading":"2. Manufacturer / service provider","section3Heading":"3. Object of declaration","section3ScopeHeading":"Scope explicitly excluded","section4Heading":"4. Standards applied","section5Heading":"5. Signature","section6Heading":"6. Technical file","labels":{"productName":"Product name","modelVersion":"Model / version","category":"Category","type":"Type","name":"Name","address":"Address","country":"Country","complaintContact":"Complaint contact","wcagLevel":"WCAG conformance level","harmonisedStandards":"Harmonised standard(s)","testingMethod":"Testing method","annexISection":"Annex I section","nationalTransposition":"National transposition","openNonConformances":"Open non-conformances","signedBy":"Signed by","roleTitle":"Role / title","place":"Place","date":"Date","nextReview":"Next review","openYesAnnex":"Yes, see Annex","openNone":"None","service":"Service","product":"Product","emDash":","},"technicalFilePlaceholder":"[See Article 20, must be retained for 5 years]","technicalFileBody":"Technical file location: {location}. The technical file must include the ACR/VPAT, audit reports, the published Accessibility Statement, any disproportionate burden assessments, supply chain ACRs, and this signed Declaration of Conformity. It must be made available to market surveillance authorities promptly on request.","soleResponsibility":"I, the undersigned, declare under my sole responsibility that the product or service described above is in conformity with the requirements of Directive (EU) 2019/882 (European Accessibility Act) and the harmonised standards listed in section 4."}},"samplePreview":{"toolName":"EU Declaration of Conformity Generator","description":"This tool produces an EU Declaration of Conformity per EAA Annex IV, the formal document required to demonstrate your product or service meets accessibility requirements."},"productCategories":{"websiteWebApp":"Website / Web Application","mobileApp":"Mobile Application (iOS / Android)","desktopSoftware":"Desktop Software","computerOs":"Computer / Operating System","paymentTerminal":"Payment Terminal","atm":"Self-service Terminal (ATM)","ticketing":"Self-service Terminal (Ticketing Machine)","checkinKiosk":"Self-service Terminal (Check-in Kiosk)","smartphone":"Smartphone / Tablet","eReader":"E-reader","consumerElectronics":"Consumer Electronics (TV / Set-top box)","telephony":"Telephony Service","audiovisual":"Audio-visual Media Service","ebook":"E-book","ecommerce":"E-commerce Service","banking":"Banking / Financial Service","electronicComms":"Electronic Communications Service","transport":"Passenger Transport Booking Service","other":"Other (specify in description)"},"annexISections":{"websiteWebApp":"Section IX, Electronic communications services and e-commerce","mobileApp":"Section IX, Electronic communications services and e-commerce","desktopSoftware":"Section III, General-purpose computer hardware and operating systems","computerOs":"Section III, General-purpose computer hardware and operating systems","paymentTerminal":"Section V, Self-service terminals","atm":"Section V, Self-service terminals","ticketing":"Section V, Self-service terminals","checkinKiosk":"Section V, Self-service terminals","smartphone":"Section II, Smartphones","eReader":"Section IV, Consumer terminal equipment with advanced computing capability","consumerElectronics":"Section VI, Consumer terminal equipment for electronic communications","telephony":"Section VI, Consumer terminal equipment for electronic communications","audiovisual":"Section VII, Audio-visual media services","ebook":"Section VIII, E-books and dedicated reading software","ecommerce":"Section IX, E-commerce services","banking":"Section X, Banking services","electronicComms":"Section VI, Electronic communications services","transport":"Section XI, Passenger transport services","other":"Please identify the applicable Annex I section manually"},"testingMethods":{"internal":"Internal accessibility audit against EN 301 549 V3.2.1 / WCAG 2.1 AA","thirdParty":"Third-party professional accessibility audit","automatedManual":"Automated testing tools (axe, WAVE, Lighthouse) supplemented by manual testing","combinedAt":"Combined automated and manual testing with assistive technology verification (NVDA, JAWS, VoiceOver)","fullIndependent":"Full independent audit by accredited accessibility specialist"},"enStandardOptions":{"v321":"V3.2.1 (2021), Current OJEU harmonised standard","v411":"V4.1.1 (2024), References WCAG 2.2 (not yet in OJEU list)"}},"contrast-checker":{"meta":{"title":"WCAG 2.2 Colour Contrast Validator","description":"Verify AA/AAA compliance with real-time luminance calculation. Enter any two hex colours."},"header":{"title":"WCAG 2.2 Colour Contrast Validator","subtitle":"Verify AA/AAA compliance, simulate colour blindness, and find the nearest passing colour.","resetColours":"Reset colours"},"howTo":{"step1Title":"Enter your colours","step1Body":"Type or paste a hex code (e.g. #1a1a2e) into the foreground and background fields, or click the colour swatch to use a colour picker.","step2Title":"Read the ratio","step2Body":"The contrast ratio is calculated instantly. AA requires 4.5:1 for normal text (3:1 for large text). AAA requires 7:1.","step3Title":"Check the previews","step3Body":"The sample text blocks show how your colour pair looks at different sizes. The colour-blindness simulations show how the pairing appears to users with visual impairments.","step4Title":"Adjust until it passes","step4Body":"If the pair fails, adjust the lightness of one colour until the ratio turns green. Use the suggested alternatives below the result if you need help."},"inputs":{"foregroundLabel":"Foreground (Text)","backgroundLabel":"Background","swapColours":"Swap Colours","invalidHex":"Invalid hex code. Use format #RRGGBB or #RGB (e.g. {example})","luminance":"Luminance"},"preview":{"livePreview":"Live Preview","headingSample":"Heading sample text","bodySample":"Body text: The quick brown fox jumps over the lazy dog.","smallSample":"Small text sample (14px equivalent)","button":"Button","link":"Link","outlineBtn":"Outline btn","cbSimulation":"{mode} simulation"},"cbModes":{"none":"Normal vision","deuteranopia":"Deuteranopia (green-blind)","protanopia":"Protanopia (red-blind)","tritanopia":"Tritanopia (blue-blind)"},"textContext":{"sectionTitle":"What are you testing?","sectionSubtitle":"Select your use case to get a precise requirement and verdict.","normalLabel":"Normal text","normalDesc":"Any text below 18pt (24px) regular, or below 14pt (18.67px) bold","largeLabel":"Large text (regular)","largeDesc":"Text at 18pt (24px) or larger, regular weight","largeBoldLabel":"Large text (bold)","largeBoldDesc":"Text at 14pt (18.67px) or larger, bold weight","uiLabel":"UI component / icon","uiDesc":"Button borders, input outlines, focus indicators, chart lines","incidentalLabel":"Decorative / inactive","incidentalDesc":"Disabled controls, placeholder text, logos, no requirement","exempt":"Exempt, no contrast requirement","pass":"Pass, {sc}","fail":"Fail, {sc}","exemptDetail":"Decorative images, disabled controls, placeholder text, and logotypes are explicitly excluded from WCAG 1.4.3 and 1.4.11.","requiredRatio":"Required ratio: {threshold}:1 · Your ratio: {ratio}:1 · {sc}","apply":"Apply {hex}"},"results":{"allCriteria":"All WCAG 2.2 criteria","pass":"Pass","fail":"Fail","sc143Normal":{"label":"SC 1.4.3, Contrast Minimum (Level AA)","sublabel":"Normal text: any text below 18pt regular or 14pt bold","detail":"This is the baseline requirement for body text, labels, links, and all standard-size content. Required by the EAA, EN 301 549, ADA (DOJ 2024 rule), and Section 508 in the US."},"sc143Large":{"label":"SC 1.4.3, Large Text (Level AA)","sublabel":"Text at 18pt (24px) regular or 14pt (18.67px) bold or larger","detail":"Large text is easier to read, so a lower contrast ratio is acceptable. The 18pt / 14pt bold thresholds come from print typography research. Required under the same regulations as SC 1.4.3 normal text."},"sc1411":{"label":"SC 1.4.11, Non-text Contrast (Level AA)","sublabel":"UI components: button borders, input outlines, icons, focus rings, charts","detail":"Added in WCAG 2.1. Covers interactive components and graphical objects that convey information. Applies to button outlines, form input borders, checkbox squares, radio buttons, chart lines and segments. Text inside components is still covered by 1.4.3."},"sc146":{"label":"SC 1.4.6, Contrast Enhanced (Level AAA)","sublabel":"Recommended best practice, not required by most regulations","detail":"The improved level is not required by the EAA or most national laws but is recommended for high-readability content such as body copy for general audiences, and any text displayed on mobile screens in outdoor conditions."}},"apca":{"title":"APCA Score","badge":"WCAG 3.0 Preview","lightnessContrast":"APCA Lightness Contrast","thresholds":"APCA Lc Thresholds (WCAG 3.0 draft)","bodyText":"Body text 14–16px","normalText":"Normal text 14–16px","largeText":"Large text / UI labels 18px+","largeBoldText":"Large bold text 18.7px bold+","nonText":"Non-text / decorative","whatIsApca":"What is APCA?","apcaDesc":"APCA (Advanced Perceptual Contrast Algorithm) is the contrast method being developed for WCAG 3.0. It replaces the WCAG 2.x ratio formula with a perceptually uniform model.","currentStatus":"Current status","currentStatusDesc":"APCA is in use in WCAG 3.0 drafts (FPWD stage as of 2026). It is not yet a legal requirement under the EAA, ADA, or Section 508. WCAG 2.x ratio requirements remain the legal standard. Use APCA as a supplementary signal."},"suggestion":{"nearestPassing":"Nearest AA-passing foreground","changeForeground":"Change foreground to {hex} ({direction}) to achieve 4.5:1","apply":"Apply"},"actions":{"shareResult":"Share result","linkCopied":"Link copied!"},"history":{"title":"Recent Pairs","clearHistory":"Clear history"},"css":{"title":"CSS Custom Properties","copy":"Copy","copied":"Copied!"},"compliance":{"title":"Which laws and standards does this apply to?"}},"contrast-palette":{"meta":{"toolId":"Contrast-palette","title":"Colour Contrast Palette Generator","description":"Generate full colour palettes that meet WCAG 2.2 contrast requirements. Pro self-assessment tool for EAA-compliant accessible design systems."},"title":"Colour Contrast Palette Generator","description":"Generate a 9-step WCAG-compliant palette from any brand hex colour, then export as CSS, JSON, or Figma tokens.","proGateFeatures":["Generate a 9-step accessible palette from any brand hex colour","Instant AA and AAA contrast ratio badges per shade against white and black","Component preview — buttons, links, badges and info panels rendered in your palette","Export-ready tokens: CSS custom properties, JSON, Figma Token Studio, and Tailwind config","Save up to 5 palettes locally and share via URL"],"infoPanel":{"toggle":"What this tool does — and why colour contrast is a legal requirement","whatItDoes":{"heading":"What this tool does","description":"Enter any brand hex colour and the generator builds a 9-step tint/shade scale (100–900, matching the Tailwind convention). Every step is automatically checked against white and black backgrounds using the WCAG 2.2 relative luminance formula, and labelled as AA pass, AAA pass, or fail."},"legalRequirement":{"heading":"The legal requirement — contrast is not optional"},"howToUseWorkflow":{"heading":"How to use this tool in your workflow","steps":["Enter your primary brand colour hex code.","Check the swatch grid — use shades 600–900 (darker) for text on white backgrounds, and shades 100–300 (lighter) for backgrounds behind dark text.","Shades marked AA pass are safe for normal body text. Shades marked AAA pass are suitable for small or low-contrast environments.","Use the Component Preview to see your palette applied to real UI patterns before exporting.","Export the tokens into your codebase or design system so every developer and designer works from the same accessibility-validated colour set."]},"important":"Contrast ratio alone does not guarantee accessibility. Also ensure sufficient font size, avoid colour as the only means of conveying information (SC 1.4.1), and test with users who have low vision or colour blindness."},"input":{"label":"Enter your brand colour","pickerAriaLabel":"Colour picker","hexAriaLabel":"Brand hex colour value","invalidHex":"Enter a valid hex colour, e.g. #004494"},"actions":{"savePalette":"Save palette","shareUrl":"Share URL","linkCopied":"Link copied!","copy":"Copy","copied":"Copied!"},"savedPalettes":"Saved Palettes","generatedPalette":"Generated Palette","contrastRows":{"textOnWhite":"This shade as text on white","whiteOnThis":"White text on this shade","blackOnThis":"Black text on this shade"},"contrastBadges":{"aaa":"AAA","aa":"AA","fail":"Fail"},"pairingsSummary":"Shades have at least one AA pairing","pairingsSummaryAAA":"Shades have at least one AAA pairing","recommendedPairings":{"heading":"Recommended Pairings","textOnWhite":{"label":"Text colour on white page","description":"Use for body text, links, and headings on a white or light background."},"whiteOnBackground":{"label":"Background with white text","description":"Use as a filled button, badge, header band, or card background with white text on top."},"lightBackground":{"label":"Light background with dark text","description":"Use as a tinted panel, alert box, or selected-item highlight with black or very dark text."}},"componentPreview":{"heading":"Component Preview","primaryButton":"Primary Button","outlineButton":"Outline Button","badge":"Badge","linkText":"Link text","infoPanel":"Info panel using 100/900"},"export":{"heading":"Export","ariaLabel":"Export format","cssVariables":"CSS Variables","json":"JSON","figmaTokens":"Figma Tokens","tailwind":"Tailwind"},"usageLabels":{"tintBackground":"Tint / background","lightBackgroundHover":"Light background or hover state","accentBorderIcon":"Accent / border / icon fill","primaryBrand":"Primary brand colour","textLinkInteractive":"Text / link / interactive","bodyTextHeadings":"Body text / headings","highContrastDarkUi":"High-contrast text / dark UI","generalUse":"General use"}},"contrast-suite":{"meta":{"title":"Contrast Suite, Contrast Checker, Palette Generator & Colour-Blind Simulator","description":"Three contrast tools in one: WCAG / APCA contrast checker, accessible palette generator, and colour-blindness simulator. WCAG 2.2 SC 1.4.3 / 1.4.11."},"tabs_aria":"Contrast suite modes","tab_checker":"Contrast Checker","tab_palette":"Palette Generator","tab_colour_blind":"Colour-Blind Simulator","checker":{"header":{"title":"WCAG 2.2 Colour Contrast Validator","subtitle":"Verify AA/AAA compliance, simulate colour blindness, and find the nearest passing colour.","resetColours":"Reset colours"},"howTo":{"step1Title":"Enter your colours","step1Body":"Type or paste a hex code (e.g. #1a1a2e) into the foreground and background fields, or click the colour swatch to use a colour picker.","step2Title":"Read the ratio","step2Body":"The contrast ratio is calculated instantly. AA requires 4.5:1 for normal text (3:1 for large text). AAA requires 7:1.","step3Title":"Check the previews","step3Body":"The sample text blocks show how your colour pair looks at different sizes. The colour-blindness simulations show how the pairing appears to users with visual impairments.","step4Title":"Adjust until it passes","step4Body":"If the pair fails, adjust the lightness of one colour until the ratio turns green. Use the suggested alternatives below the result if you need help."},"inputs":{"foregroundLabel":"Foreground (Text)","backgroundLabel":"Background","swapColours":"Swap Colours","foregroundPickerAria":"Foreground colour picker","foregroundHexAria":"Foreground hex value","backgroundPickerAria":"Background colour picker","backgroundHexAria":"Background hex value","swapAria":"Swap foreground and background colours","invalidHexFg":"Invalid hex code. Use format #RRGGBB or #RGB (e.g. #1a2b3c)","invalidHexBg":"Invalid hex code. Use format #RRGGBB or #RGB (e.g. #ffffff)","rgbLuminance":"Rgb({r}, {g}, {b}) · luminance: {luminance}"},"preview":{"livePreview":"Live Preview","headingSample":"Heading sample text","bodySample":"Body text: The quick brown fox jumps over the lazy dog.","smallSample":"Small text sample (14px equivalent)","button":"Button","link":"Link","outlineBtn":"Outline btn","cbModeAria":"Colour blindness simulation mode","cbSimulation":"{mode} simulation"},"cbModes":{"none":"Normal vision","deuteranopia":"Deuteranopia (green-blind)","protanopia":"Protanopia (red-blind)","tritanopia":"Tritanopia (blue-blind)"},"textContext":{"sectionTitle":"What are you testing?","sectionSubtitle":"Select your use case to get a precise requirement and verdict.","normalLabel":"Normal text","normalDesc":"Any text below 18pt (24px) regular, or below 14pt (18.67px) bold","largeLabel":"Large text (regular)","largeDesc":"Text at 18pt (24px) or larger, regular weight","largeBoldLabel":"Large text (bold)","largeBoldDesc":"Text at 14pt (18.67px) or larger, bold weight","uiLabel":"UI component / icon","uiDesc":"Button borders, input outlines, focus indicators, chart lines","incidentalLabel":"Decorative / inactive","incidentalDesc":"Disabled controls, placeholder text, logos, no requirement","scNormal":"SC 1.4.3 Level AA","scLarge":"SC 1.4.3 Level AA","scLargeBold":"SC 1.4.3 Level AA","scUi":"SC 1.4.11 Level AA","scIncidental":"SC 1.4.3 (exempt)","verdictInvalid":"Enter valid hex colours to check contrast","verdictExempt":"Exempt, no contrast requirement","verdictPass":"✓ Pass, {sc}","verdictFail":"✗ Fail, {sc}","detailInvalid":"One or both colour values are invalid. Use format #RRGGBB or #RGB.","detailExempt":"Decorative images, disabled controls, placeholder text, and logotypes are explicitly excluded from WCAG 1.4.3 and 1.4.11.","detailRequired":"Required ratio: {threshold}:1 · Your ratio: {ratio}:1 · {sc}","applyHex":"Apply {hex}"},"results":{"allCriteria":"All WCAG 2.2 criteria","verdictPass":"✓ Pass","verdictFail":"✗ Fail","understandingLink":"W3C Understanding document →","sc143Normal":{"label":"SC 1.4.3, Contrast Minimum (Level AA)","sublabel":"Normal text: any text below 18pt regular or 14pt bold","ratio":"4.5:1","detail":"This is the baseline requirement for body text, labels, links, and all standard-size content. Required by the EAA, EN 301 549, ADA (DOJ 2024 rule), and Section 508 in the US."},"sc143Large":{"label":"SC 1.4.3, Large Text (Level AA)","sublabel":"Text at 18pt (24px) regular or 14pt (18.67px) bold or larger","ratio":"3:1","detail":"Large text is easier to read, so a lower contrast ratio is acceptable. The 18pt / 14pt bold thresholds come from print typography research. Required under the same regulations as SC 1.4.3 normal text."},"sc1411":{"label":"SC 1.4.11, Non-text Contrast (Level AA)","sublabel":"UI components: button borders, input outlines, icons, focus rings, charts","ratio":"3:1","detail":"Added in WCAG 2.1. Covers interactive components and graphical objects that convey information. Applies to button outlines, form input borders, checkbox squares, radio buttons, chart lines and segments. Text inside components is still covered by 1.4.3."},"sc146":{"label":"SC 1.4.6, Contrast Enhanced (Level AAA)","sublabel":"Recommended best practice, not required by most regulations","ratio":"7:1","detail":"This AAA level is not required by the EAA or most national laws but is recommended for high-readability content such as body copy for general audiences, and any text displayed on mobile screens in outdoor conditions."}},"apca":{"title":"APCA Score","badge":"WCAG 3.0 Preview","lcSummary":"Lc {lc}, {desc}","lightnessContrast":"APCA Lightness Contrast","thresholds":"APCA Lc Thresholds (WCAG 3.0 draft)","bodyText":"Body text 14–16px","normalText":"Normal text 14–16px","largeText":"Large text / UI labels 18px+","largeBoldText":"Large bold text 18.7px bold+","nonText":"Non-text / decorative","whatIsApca":"What is APCA?","apcaDescription":"APCA (Advanced Perceptual Contrast Algorithm) is the contrast method being developed for <strong>WCAG 3.0</strong>. It replaces the WCAG 2.x ratio formula with a perceptually uniform model that accounts for:","apcaBullet1":"Whether text is <strong>dark on light</strong> or <strong>light on dark</strong> (asymmetric)","apcaBullet2":"<strong>Font size and weight</strong>, the same colour pair has different thresholds at different sizes","apcaBullet3":"Human visual perception, the eye distinguishes colours differently at different luminance levels","apcaLcExplain":"APCA reports contrast as an <strong>Lc value</strong> (Lightness Contrast), not a ratio. Higher is better. The sign (positive/negative) indicates polarity: positive = dark text on light bg, negative = light text on dark bg.","currentStatus":"Current status","currentStatusDesc":"APCA is in use in WCAG 3.0 drafts (FPWD stage as of 2026). It is <strong>not yet a legal requirement</strong> under the EAA, ADA, or Section 508. WCAG 2.x ratio requirements remain the legal standard. Use APCA as a supplementary signal, especially useful when testing dark mode or coloured backgrounds where WCAG 2.x ratios can be misleading.","source":"Source: SAPC 0.0.98G algorithm by Andrew Somers / Myndex Research (open source). Calculations are informational only, verify critical design decisions with the official APCA calculator.","ratings":{"lc90":"Preferred for body text, maximum readability","lc75":"Good for normal body text (14–16px)","lc60":"OK for large text or UI labels (18px+)","lc45":"Minimum for large/bold text (24px+ or 18.7px bold)","lc30":"Minimum for non-text / decorative elements","lcLow":"Too low, not suitable for any readable text"},"ratingLabel":{"lc90":"Lc 90+","lc75":"Lc 75+","lc60":"Lc 60+","lc45":"Lc 45+","lc30":"Lc 30+","lcLow":"Lc {lc}"}},"suggestion":{"nearestPassing":"Nearest AA-passing foreground","changeForeground":"Change foreground to <strong>{hex}</strong> ({direction}) to achieve 4.5:1","directionLighter":"Lighter","directionDarker":"Darker","apply":"Apply","swatchAria":"Suggested colour {hex}"},"actions":{"shareResult":"Share result","linkCopied":"Link copied!"},"history":{"title":"Recent Pairs","clearHistory":"Clear history","restoreAria":"Restore pair {fg} on {bg}","badgeAa":"AA","badgeFail":"Fail"},"css":{"title":"CSS Custom Properties","copy":"Copy","copied":"Copied!","passesAa":"Passes WCAG AA","failsAa":"Fails WCAG AA","wcag3Preview":"WCAG 3.0 preview"},"compliance":{"title":"Which laws and standards does this apply to?","passLabel":"Pass","failLabel":"Fail","exemptCallout":"<strong>What is exempt from contrast requirements?</strong> Decorative images (no informational value), disabled UI controls (e.g. A greyed-out button), placeholder text in form inputs, and logotypes / brand wordmarks are explicitly excluded from WCAG SC 1.4.3 and 1.4.11. Select \"Decorative / inactive\" in the context selector above to confirm exemption status.","eaa":{"standard":"European Accessibility Act (EAA)","ref":"Directive 2019/882/EU · Annex I Section IV","applies":"EU, products and services sold to consumers from 28 June 2025","detail":"The EAA mandates conformance with EN 301 549 v3.2.1, which references WCAG 2.1 Level AA as its web content standard. WCAG 2.2 AA is the current W3C recommendation and is considered best practice under the EAA. Passing SC 1.4.3 AA (4.5:1 normal text, 3:1 large text) and SC 1.4.11 AA (3:1 UI) satisfies the EAA colour contrast obligations.","linkLabel":"EAA Directive text →"},"en301549":{"standard":"EN 301 549 v3.2.1","ref":"Clause 9.1.4.3 · 9.1.4.11","applies":"EU, harmonised standard referenced by EAA and public sector bodies","detail":"EN 301 549 is the European harmonised standard for ICT accessibility. Clause 9.1.4.3 directly adopts WCAG 2.1 SC 1.4.3 (contrast minimum) and clause 9.1.4.11 adopts SC 1.4.11 (non-text contrast). Conformance with WCAG 2.2 AA satisfies both clauses because WCAG 2.2 is backwards compatible with WCAG 2.1.","linkLabel":"EN 301 549 specification →"},"ada":{"standard":"Americans with Disabilities Act (ADA)","ref":"DOJ Final Rule 28 CFR Part 35 · March 2024","applies":"US, Title II public entities. Title III (private businesses) expected to follow same standard","detail":"The US Department of Justice March 2024 final rule requires WCAG 2.1 Level AA for state and local government websites and mobile apps. SC 1.4.3 is a Level AA criterion. WCAG 2.2 AA is a superset of WCAG 2.1 AA, so passing here satisfies the ADA web rule. For private businesses, courts and DOJ guidance have consistently applied WCAG 2.1 AA as the benchmark.","linkLabel":"DOJ web accessibility rule →"},"section508":{"standard":"Section 508 (US Federal)","ref":"36 CFR Part 1194 · E205.4 WCAG 2.0 Level AA","applies":"US, federal agencies and entities receiving federal funding","detail":"Section 508 currently mandates WCAG 2.0 Level AA. WCAG 2.0 SC 1.4.3 (contrast minimum) is identical in requirement to WCAG 2.2 SC 1.4.3. Passing this tool's AA check satisfies the Section 508 contrast requirement. The Access Board has signalled a future update to WCAG 2.1.","linkLabel":"Section 508 ICT standards →"},"ukPsbar":{"standard":"UK Equality Act & PSBAR 2018","ref":"Public Sector Bodies Accessibility Regulations · EN 301 549","applies":"UK, public sector bodies; private sector covered by Equality Act reasonable adjustment duty","detail":"UK PSBAR 2018 (as retained law post-Brexit) requires WCAG 2.1 Level AA for public sector websites and apps, referencing EN 301 549. SC 1.4.3 is a core requirement. For private organisations, the Equality Act 2010 duty to make reasonable adjustments is widely interpreted to include meeting WCAG AA contrast standards.","linkLabel":"UK PSBAR legislation →"},"wcagAaa":{"standard":"WCAG 2.2 Level AAA (Improved)","ref":"SC 1.4.6 Contrast Enhanced","applies":"Best practice, not required by law for most contexts","detail":"AAA is recommended for content targeting older users, users with low vision not using assistive technology, or content displayed in challenging environments (outdoor screens, bright sunlight). Achieving AAA (7:1) is not required by the EAA, ADA, or Section 508 but demonstrates a high standard of accessibility commitment. Some internal accessibility policies and premium certification schemes require AAA for body text.","linkLabel":"SC 1.4.6 Understanding document →"}},"exportPanel":{"toolName":"Colour Contrast Checker","toolDescription":"This assessment verifies whether a foreground and background colour combination meets the minimum contrast ratios required by WCAG 2.2. Insufficient contrast prevents people with low vision, colour blindness, or age-related visual decline from reading text. Under the EAA, all consumer-facing digital products and services must meet these requirements for all text, UI components, and graphical objects.","outcomeNotAssessed":"Not Assessed","outcomePasses":"Passes","outcomeDoesNotSupport":"Does Not Support","verdictPassAa":"WCAG AA Pass","verdictFailAa":"WCAG AA Fail","summaryFmt":"{fg} on {bg} = {ratio}:1, {verdict}","verdictAaPass":"PASS, WCAG 2.2 AA","verdictAaFail":"FAIL, Does not meet WCAG 2.2 AA","swatchLabelFmt":"{ratio}:1, {verdict}","swatchVerdictPass":"WCAG AA PASS","swatchVerdictFail":"WCAG AA FAIL","docxResultHeading":"Result","docxTableHeaders":{"criterion":"Criterion","requiredRatio":"Required Ratio","actualRatio":"Actual Ratio","verdict":"Verdict"},"docxRows":{"wcagAaNormal":"WCAG AA, Normal text","wcagAaLarge":"WCAG AA, Large text (>=18pt / >=14pt bold)","wcagAaUi":"WCAG AA, UI components & graphical objects","wcagAaaNormal":"WCAG AAA, Normal text","wcagAaaLarge":"WCAG AAA, Large text","apcaLc":"APCA Lc (WCAG 3 preview)"},"docxPass":"PASS","docxFail":"FAIL","docxAdvisory":"Advisory","docxNa":"N/a","docxContextHeading":"Selected text-context verdict","docxContextRows":{"selectedContext":"Selected context","requiredRatio":"Required ratio for this context","actualRatio":"Actual ratio","scMapped":"WCAG SC mapped","verdict":"Verdict","exemptValue":"Exempt, no requirement","verdictExempt":"EXEMPT","verdictPass":"PASS","verdictFail":"FAIL"},"docxNearestContextHeading":"Nearest passing foreground","docxNearestContextBody":"Adjusting the foreground to {hex} ({direction}) would meet the {threshold}:1 threshold for the selected context.","docxNearestAaHeading":"Nearest passing for WCAG AA normal text","docxNearestAaBody":"Adjusting the foreground to {hex} ({direction}) would meet the WCAG AA 4.5:1 threshold for normal text.","docxApcaHeading":"APCA detail (WCAG 3.0 preview)","docxApcaRows":{"lcValue":"APCA Lc value","band":"Band","suitableFor":"Suitable for"},"docxInputsHeading":"Test Inputs","docxInputs":{"foreground":"Foreground colour","background":"Background colour","textContext":"Text context","fgRgb":"Foreground RGB","bgRgb":"Background RGB","fgLum":"Foreground luminance","bgLum":"Background luminance","naDash":","},"docxMethodHeading":"Method","docxMethodBody":"Contrast ratios are calculated per the WCAG 2.x relative luminance formula (sRGB). APCA Lc values are computed per the WCAG 3 preview algorithm (SAPC 0.0.98G) and are advisory only. Tested against WCAG 2.2 SC 1.4.3 (Contrast Minimum, AA), 1.4.6 (Contrast Enhanced, AAA), and 1.4.11 (Non-text Contrast, AA). Mapped to EN 301 549 V3.2.1 clauses 9.1.4.3, 9.1.4.6, and 9.1.4.11.","downloadJsonLabel":"Download as JSON","downloadJsonHint":".json","nextStepLabel":"Run Contrast Palette Generator","nextStepHint":"Test your full brand palette, not just one pair","whatNextToolName":"Contrast Checker","whatNextProToolName":"Colour Contrast Palette Generator","inputsForeground":"Foreground colour","inputsBackground":"Background colour","inputsTextContext":"Text context","inputsContrastRatio":"Contrast ratio"}},"palette":{"title":"Colour Contrast Palette Generator","description":"Generate a 9-step WCAG-compliant palette from any brand hex colour, then export as CSS, JSON, or Figma tokens.","proGateFeatures":["Generate a 9-step accessible palette from any brand hex colour","Instant AA and AAA contrast ratio badges per shade against white and black","Component preview, buttons, links, badges and info panels rendered in your palette","Export-ready tokens: CSS custom properties, JSON, Figma Token Studio, and Tailwind config","Save up to 5 palettes locally and share via URL"],"infoPanel":{"toggle":"What this tool does, and why colour contrast is a legal requirement","whatItDoesHeading":"What this tool does","whatItDoesP1":"Enter any brand hex colour and the generator builds a <strong>9-step tint/shade scale</strong> (100–900, matching the Tailwind convention). Every step is automatically checked against white and black backgrounds using the <strong>WCAG 2.2 relative luminance formula</strong>, and labelled as AA pass, AAA pass, or fail. You also get a live component preview and one-click export in the format your team uses, CSS custom properties, JSON design tokens, Figma Token Studio, or Tailwind config.","whatItDoesP2":"This means you can test whether your brand colour works at scale <em>before</em> it enters your design system, not after a compliance audit flags it.","legalHeading":"The legal requirement, contrast is not optional","legalRows":{"wcag143Term":"WCAG 2.2 SC 1.4.3","wcag143Body":"<strong>Contrast (Minimum), Level AA.</strong> Normal text must achieve at least <strong>4.5:1</strong> contrast against its background. Large text (18pt / 14pt bold) requires <strong>3:1</strong>. This is the baseline all the major legal frameworks below point to.","wcag146Term":"WCAG 2.2 SC 1.4.6","wcag146Body":"<strong>Contrast (Enhanced), Level AAA.</strong> Raises the bar to <strong>7:1</strong> for normal text. Required where you are targeting the highest conformance level or serving users with low vision.","eaaTerm":"EAA 2025","eaaBody":"<strong>European Accessibility Act (Directive 2019/882)</strong>, applies from <strong>28 June 2025</strong> to consumer-facing products and services in the EU. It mandates WCAG 2.1 AA as the effective technical standard via EN 301 549. Colour contrast failures under SC 1.4.3 directly constitute non-compliance and can attract fines and market-access sanctions.","enTerm":"EN 301 549","enBody":"<strong>European harmonised standard</strong> adopted under the EAA and the Web Accessibility Directive. Passing EN 301 549 (which incorporates WCAG 2.1 AA) creates a legal presumption of conformity under the EAA. Colour contrast requirements are captured in clause 9.1.4.3.","ukTerm":"UK PSBAR","ukBody":"<strong>Public Sector Bodies Accessibility Regulations 2018</strong>, applies to UK public sector websites and apps. Requires WCAG 2.1 AA. Contrast failures are among the most commonly cited issues in monitoring reports by the Central Digital and Data Office.","adaTerm":"ADA (USA)","adaBody":"<strong>Americans with Disabilities Act</strong>, federal courts increasingly apply WCAG 2.1 AA as the de facto standard for Title III ADA web accessibility lawsuits. Contrast failures have featured in demand letters and settlements.","sec508Term":"Section 508 (USA)","sec508Body":"<strong>Section 508 of the Rehabilitation Act</strong>, applies to US federal agencies and their contractors. Requires WCAG 2.0 Level AA, which includes the 4.5:1 contrast requirement at SC 1.4.3."},"workflowHeading":"How to use this tool in your workflow","workflowSteps":["Enter your primary brand colour hex code.","Check the swatch grid, use <strong>shades 600–900</strong> (darker) for text on white backgrounds, and <strong>shades 100–300</strong> (lighter) for backgrounds behind dark text.","Shades marked <strong>AA pass</strong> are safe for normal body text. Shades marked <strong>AAA pass</strong> are suitable for small or low-contrast environments.","Use the Component Preview to see your palette applied to real UI patterns before exporting.","Export the tokens into your codebase or design system so every developer and designer works from the same accessibility-validated colour set."],"important":"<strong>Important:</strong> Contrast ratio alone does not guarantee accessibility. Also ensure sufficient font size, avoid colour as the only means of conveying information (SC 1.4.1), and test with users who have low vision or colour blindness."},"input":{"label":"Enter your brand colour","pickerAriaLabel":"Colour picker","hexAriaLabel":"Brand hex colour value","invalidHex":"Enter a valid hex colour, e.g. #004494","swatchAria":"Preview of colour {hex}"},"actions":{"savePalette":"Save palette","shareUrl":"Share URL","linkCopied":"Link copied!","copy":"Copy","copied":"Copied!"},"savedPalettes":"Saved Palettes","generatedPalette":"Generated Palette","swatchesAria":"Generated palette swatches","componentPreviewAria":"Component preview using generated palette","exportAria":"Export palette tokens","contrastRows":{"textOnWhite":"This shade as text on white","whiteOnThis":"White text on this shade","blackOnThis":"Black text on this shade"},"contrastBadges":{"aaa":"AAA","aa":"AA","fail":"Fail"},"pairingsSummary":"Shades have at least one AA pairing","pairingsSummaryAAA":"Shades have at least one AAA pairing","recommendedPairings":{"heading":"Recommended Pairings","shadeRatioAaa":"Shade {step}, {ratio}:1 (AAA)","shadeRatioAa":"Shade {step}, {ratio}:1 (AA)","textOnWhite":{"label":"Text colour on white page","description":"Use for body text, links, and headings on a white or light background."},"whiteOnBackground":{"label":"Background with white text","description":"Use as a filled button, badge, header band, or card background with white text on top."},"lightBackground":{"label":"Light background with dark text","description":"Use as a tinted panel, alert box, or selected-item highlight with black or very dark text."}},"componentPreview":{"heading":"Component Preview","primaryButton":"Primary Button","outlineButton":"Outline Button","badge":"Badge","linkText":"Link text","infoPanel":"Info panel using 100/900"},"export":{"heading":"Export","ariaLabel":"Export format","cssVariables":"CSS Variables","json":"JSON","figmaTokens":"Figma Tokens","tailwind":"Tailwind","cssDescription":"CSS custom properties ready to paste into your stylesheet.","jsonDescription":"JSON token file with contrast metadata, ideal for design systems.","figmaDescription":"W3C Design Token Community Group format for Figma Token Studio.","tailwindDescription":"Tailwind CSS config colors block, paste into your tailwind.config.js extend.colors."},"wcagLegend":{"heading":"Contrast Ratio Reference","aaBadge":"AA","aaaBadge":"AAA","failBadge":"FAIL","aaBody":"<strong>4.5:1 minimum</strong>, required for normal-sized text under WCAG 2.2 SC 1.4.3 (Level AA). 3:1 is sufficient for large text (18pt / 14pt bold). <strong>This is the threshold mandated by the EAA, EN 301 549, ADA, Section 508, and UK PSBAR.</strong>","aaaBody":"<strong>7:1 minimum</strong>, enhanced contrast under WCAG 2.2 SC 1.4.6 (Level AAA). 4.5:1 for large text. Not legally mandated by most acts, but strongly recommended for public-facing content targeting the widest audience.","failBody":"Contrast is insufficient. This shade must not be used for text at its current size unless the minimum ratio is met. Adjust the shade, increase font size, or use the recommended background shown per swatch.","footnote":"Ratios calculated using the WCAG 2.2 relative luminance formula, <wcagLink>WCAG 2.2 Section 1.4.3</wcagLink>. Also see: <nonTextLink>SC 1.4.11 Non-text Contrast</nonTextLink> for UI component and icon requirements (3:1 minimum)."},"usageLabels":{"tintBackground":"Tint / background","lightBackgroundHover":"Light background or hover state","accentBorderIcon":"Accent / border / icon fill","primaryBrand":"Primary brand colour","textLinkInteractive":"Text / link / interactive","bodyTextHeadings":"Body text / headings","highContrastDarkUi":"High-contrast text / dark UI","generalUse":"General use"},"usageDetails":{"tintWithBlack":"Safe as a light background: pair with black or very dark text. Do not use as text colour, too light to pass contrast against white.","tintNoPass":"Use only for decorative backgrounds or large colour blocks. Too light for text use and insufficient contrast even for background use, use shade 300+ for backgrounds where dark text must be readable.","lightBgWithBlack":"Works as a light tinted background with dark text, hover states, or selected-item highlights. Not suitable as a text colour on white.","lightBgNoPass":"Decorative use only at this lightness, does not meet AA for text on white or as a background with overlaid text. Consider shade 400+ for interactive use.","accentTextPass":"Passes AA as text on white, usable for large headings, decorative text, or non-text elements (icons, borders, focus indicators need 3:1).","accentTextFail":"Borderline shade. Good for non-text elements like borders, dividers, and icons (3:1 required). Avoid for body text, use shade 500+ for text on white.","primaryTextPass":"Passes AA as text on white, suitable for links, headings, and interactive controls.","primaryTextFail":"Does not pass AA as text on a white page at this shade, use shade 600–700 for text.","primaryWhitePass":"Also passes AA with white text on top, works as a filled button or badge background.","primaryWhiteFail":"White text does not pass AA on this background, use shade 700+ for filled components with white text, or use black text on top.","textLinkPassPair":"Passes AA as text on white. Good for body links, caption text, and interactive control labels. Also supports white text on top as a button/badge fill.","textLinkPassNoPair":"Passes AA as text on white. Good for body links, caption text, and interactive control labels.","textLinkFail":"Does not pass AA as text on a white background. Use shade 700+ for reliably accessible text.","bodyTextPassPair":"Strong candidate for body text, headings, and navigation labels on white or light backgrounds. Passes AA. Works with white text as a filled button or header background.","bodyTextPassNoPair":"Strong candidate for body text, headings, and navigation labels on white or light backgrounds. Passes AA. Pair with black text if used as a background.","bodyTextFail":"Check ratio, may not pass for small body text. Suitable for large headings and graphical elements.","darkUiPair":"Darkest tones, ideal for primary body text, high-contrast headings, dark-mode backgrounds, or footer/navbar fills with white text. Passes AA and typically AAA for text on white. White text on this shade passes AA.","darkUiNoPair":"Darkest tones, ideal for primary body text, high-contrast headings, dark-mode backgrounds, or footer/navbar fills with white text. Passes AA and typically AAA for text on white."},"exportPanel":{"toolName":"Colour Contrast Palette Generator","toolDescription":"This assessment evaluates an entire colour palette systematically against WCAG 2.2 contrast requirements. It identifies every non-compliant foreground-background combination before deployment, enabling proactive compliance rather than reactive fixes.","brandColourLabel":"Brand colour (hex)","validHexLabel":"Valid hex format","valueNotSet":"(not set)","valueYes":"Yes","valueNo":"No","summarySingular":"{count} palette shade generated from {hex}","summaryPlural":"{count} palette shades generated from {hex}","resultsBrandColour":"Brand colour","resultsPaletteSteps":"Palette steps generated","resultsAaTextOnWhite":"AA-compliant (text on white)","resultsAaaTextOnWhite":"AAA-compliant (text on white)","resultsXOfY":"{x} of {y}","resultsPerStepLabel":"Step {step} ({hex})","resultsPerStepValue":"Text on white: {textOnWhite}:1 {textPass} | White on this: {whiteOnThis}:1 {whitePass}","resultsPassMark":"AA ✓","resultsFailMark":"AA ✗","docxSummaryHeading":"Summary","docxSummaryRows":{"brandColour":"Brand colour","paletteSteps":"Palette steps generated","aaTextOnWhite":"Steps passing AA as text on white","aaaTextOnWhite":"Steps passing AAA as text on white","aaWhiteOnThis":"Steps passing AA with white text on top","aaBlackOnThis":"Steps passing AA with black text on top"},"docxSwatchLabel":"Step {step}, best text {bestText} at {ratio}:1","docxPerStepHeading":"Per-Step Contrast Results","docxPerStepIntro":"For each generated shade, the table shows: ratio when used as TEXT on a white page, ratio of WHITE text on the shade, ratio of BLACK text on the shade, and the recommended usage label.","docxTableHeaders":{"step":"Step","hex":"Hex","textOnWhite":"Text on white","aa":"AA","aaa":"AAA","whiteOnThis":"White on this","blackOnThis":"Black on this","recommendedUse":"Recommended use"},"docxPass":"PASS","docxFail":"FAIL","docxUsageNotesHeading":"Per-Step Usage Notes","docxUsageHeading":"Step {step}, {hex}, {usage}","docxRecommendedHeading":"Recommended Pairings","docxRecommended":{"bestTextOnWhite":"Best foreground text on white pages","bestWhiteOnBg":"Best background for white text","bestLightBg":"Best light background for dark text","valueAaa":"Step {step} ({hex}), {ratio}:1 (AAA)","valueAa":"Step {step} ({hex}), {ratio}:1 (AA)"},"docxMethodHeading":"Method","docxMethodBody":"A 9-step tint/shade scale (100-900) is generated from the supplied brand colour by tinting toward white and shading toward black at fixed amounts. For each step, three contrast ratios are computed using the WCAG 2.x relative luminance formula (sRGB): (1) the shade as text on a white page, (2) white text on the shade as a background, (3) black text on the shade as a background. Pass/fail thresholds: 4.5:1 for normal text under WCAG 2.2 SC 1.4.3 (Level AA), 7:1 under SC 1.4.6 (Level AAA), and 3:1 for non-text/UI under SC 1.4.11. Mapped to EN 301 549 V3.2.1 clauses 9.1.4.3, 9.1.4.6, and 9.1.4.11.","downloadJsonLabel":"Download JSON","downloadJsonHint":"Inputs + palette + notes","nextStepLabel":"Run Heading Structure Analyser","nextStepHint":"Check page structure and heading hierarchy"}},"colourBlind":{"header":{"badge":"Free Tool","title":"Colour Blindness Simulator","subtitle":"Upload any image to see how it appears to users with different types of colour vision deficiency. Essential for WCAG 1.4.1 (Use of Colour)."},"upload":{"dropOrClick":"Drop image here or click to upload","formats":"PNG, JPG, WebP, processed locally, never uploaded","fileInputAria":"Upload image file","uploadIconAria":"Upload"},"simulationLegend":"Simulation type","simulations":{"normalVision":"Normal Vision","normalVisionDesc":"How most people see colour","protanopia":"Protanopia","protanopiaDesc":"Red-blind (~1% of males)","deuteranopia":"Deuteranopia","deuteranopiaDesc":"Green-blind (~1% of males)","tritanopia":"Tritanopia","tritanopiaDesc":"Blue-blind (~0.01% of people)","achromatopsia":"Achromatopsia","achromatopsiaDesc":"Total colour blindness (~0.003%)"},"viewModes":{"single":"Single","split":"Split","grid":"Grid"},"splitView":{"normalVsSimulation":"Normal Vision vs {simulation}","dragToCompare":"Drag the divider to compare","normal":"Normal","allSimulations":"All simulations","clickToCompare":"Click to compare in split view"},"altText":{"simulationOf":"{simulation} simulation","normalVision":"Normal vision"},"wcagInfo":{"title":"WCAG 1.4.1, Use of Colour","body":"Colour must not be the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Use shape, pattern, or text labels alongside colour."},"algorithmDisclosure":{"title":"Simulation method","body":"Colour vision deficiency simulations use colour transformation matrices based on the Viénot, Brettel, and Mollon (1999) simplified model. Results are perceptually representative for design review purposes but may differ from higher-precision spectral models (e.g. Machado et al. 2009). Use for design review and accessibility checking, not clinical diagnosis."},"exportPanel":{"toolName":"Colour Blindness Simulator","imageUploadedLabel":"Image uploaded","imageUploadedYes":"Yes","imageUploadedNo":"No","activeSimulationLabel":"Active simulation","activeSimulationDescriptionLabel":"Active simulation description","simulationDescriptionLabel":"Simulation description","viewModeLabel":"View mode","simulationsRenderedLabel":"Simulations rendered","availableSimulationsLabel":"Available simulations","colourBlindnessTypeLabel":"Colour blindness type","summaryRenderedSingular":"{count} simulation rendered (active: {active})","summaryRenderedPlural":"{count} simulations rendered (active: {active})","summaryNoImage":"No image uploaded","noteImageNotStored":"Canvas image data not stored, re-upload the image and run the simulation to reproduce results.","docxSummaryHeading":"Summary","docxSimulationsHeading":"Simulations Rendered","docxSimulationsIntro":"The uploaded image was processed through each colour-vision-deficiency simulation listed below. Each row identifies the simulation, the population it represents, and a brief description.","docxTableHeaders":{"index":"#","simulation":"Simulation","description":"Description","rendered":"Rendered","currentlyActive":"Currently active"},"docxYes":"Yes","docxNo":"No","docxActive":"ACTIVE","docxReviewerHeading":"Reviewer Tasks","docxReviewerTasks":["Confirm that no information is conveyed by colour alone (e.g. Red/green pass-fail icons should also have shape or text labels).","Confirm that interactive states (hover, focus, error, success) remain distinguishable under each simulation.","Confirm that charts, badges, and status indicators retain meaning under deuteranopia and protanopia (the most prevalent CVD types).","Confirm that text and UI components still meet WCAG 1.4.3 / 1.4.11 contrast in the simulated images."],"docxMethodHeading":"Method","docxMethodBody":"Each simulation is implemented as a 4x4 colour-channel matrix transform applied per-pixel via canvas getImageData/putImageData. Matrices are based on published linear-RGB coefficients for protanopia, deuteranopia, tritanopia, and full achromatopsia. Tested against WCAG 2.2 SC 1.4.1 (Use of Color, Level A), which requires that colour is not used as the only visual means of conveying information. Mapped to EN 301 549 V3.2.1 clause 9.1.4.1. The image bytes themselves are not embedded in this evidence document, re-upload the original image to reproduce the simulations.","downloadJsonLabel":"Download JSON","downloadJsonHint":"Inputs + simulation metadata + notes"}}},"debt-calculator":{"meta":{"title":"Accessibility Debt Calculator","description":"Translate audit findings into hours, cost, and timeline. Built for business cases, sprint planning, and stakeholder reports."},"header":{"title":"Accessibility Debt Calculator","subtitle":"Translate audit findings into hours, cost, and timeline. Built for business cases, sprint planning, and stakeholder reports.","badge":"Pro Tool"},"features":["Translate audit findings into hours, cost, and sprint timeline","Severity-weighted estimation: critical, high, medium, low issue types","Configurable hourly rate, weekly capacity, and contingency buffer","Export to CSV, ready for business cases and stakeholder reports"],"severity":{"critical":{"label":"Critical","desc":"Blocks all users of assistive technology"},"high":{"label":"High","desc":"Significantly impairs usability"},"medium":{"label":"Medium","desc":"Creates friction or confusion"},"low":{"label":"Low","desc":"Minor cosmetic or advisory issues"}},"inputs":{"auditFindings":"Audit Findings","projectParameters":"Project Parameters","hourlyRate":"Hourly Rate (€)","capacity":"Capacity (hrs/week)","contingency":"Contingency (%)","hoursEach":"{hours}h each","issuesCount":"{count} issues × {hours}h","hoursTotal":"{hours}h total"},"results":{"totalDebt":"Total Debt","estimatedHours":"Estimated remediation hours","totalEstimatedCost":"Total estimated cost","atCapacity":"At {capacity}h/week capacity","weeks":"{count} weeks","breakdown":"Breakdown","subtotal":"Subtotal","contingencyLabel":"Contingency ({percent}%)"},"actions":{"exportCsv":"Export CSV","proOnlyExport":"Pro only, Upgrade to export"},"burdenNote":{"title":"Disproportionate burden, Annex VI note","body":"This cost estimate covers the financial dimension only. A valid disproportionate burden claim under EAA Annex VI requires assessment of four criteria: (a) financial cost relative to organisation size, (b) benefits for persons with disabilities, (c) frequency and duration of use by disabled persons, and (d) contribution of accessible alternatives. Cost alone cannot constitute a disproportionate burden determination, use the Burden Calculator for a full Annex VI assessment."},"csv":{"severity":"Severity","count":"Count","hoursEach":"Hours Each","totalHours":"Total Hours","cost":"Cost (€)"}},"document-auditor":{"meta":{"toolId":"Document-auditor","title":"Document Accessibility Auditor","description":"Audit Word and PDF documents for accessibility compliance. Pro self-assessment tool for WCAG 2.2 and EN 301 549 document requirements."},"badge":"Pro Tool","title":"Document Accessibility Auditor","description":"Upload Word (.docx), PDF, or PowerPoint (.pptx) files for an instant accessibility audit. All processing happens in your browser — files are never sent to any server.","descriptionGate":"Upload Word, PDF, or PowerPoint documents. Checks heading structure, language, alt text, tables, hyperlinks, and tagging — all processed locally in your browser.","proGateFeatures":["Upload Word, PDF, or PowerPoint documents for instant accessibility audit","Checks heading structure, language, alt text, tables, hyperlinks, and tagging","All processing happens locally in your browser — files are never uploaded","Export audit results as CSV for compliance documentation"],"privacy":{"heading":"Your files are confidential.","body":"Documents are processed entirely within your browser using JavaScript. No file content is ever transmitted to our servers, stored, or logged. The file reference is cleared immediately after analysis completes."},"howToUse":{"heading":"How to use this tool","steps":["Click <strong>Upload document</strong> or drag a file onto the upload area. Accepts.docx,.pdf, and.pptx files.","The audit runs automatically — results appear within seconds.","Review <strong>Issues</strong> first. Each issue shows the severity, the failing check, and a specific fix action.","Use the WCAG links next to each issue to read the official success criterion and understand the compliance requirement.","Download a CSV report to share with your team or include in a compliance pack.","Repeat after remediation to verify all issues are resolved."]},"upload":{"dropText":"Drop document here or click to upload","supportedFormats":".docx,.pdf,.pptx supported · Processed locally · Never uploaded","analysing":"Analysing…","unsupportedType":"Unsupported file type. Please upload a.docx,.pdf, or.pptx file."},"results":{"auditComplete":"Audit Complete","issues":"Issues","passed":"Passed","score":"Score","issuesToFix":"Issues to fix","passedChecks":"Passed checks","howToFix":"How to fix:","readCriterion":"Read the full criterion →","processingNote":"Processed entirely in your browser. This file was never uploaded to any server."},"severity":{"critical":"Critical","high":"High","medium":"Medium","low":"Low"},"checks":{"docx":{"title":"Document title set","language":"Language declared","headings":"Heading styles used","altText":"Images have alt text","tableHeaders":"Tables have header rows","linkText":"Hyperlinks have descriptive text","textContent":"Document contains real text (not scanned image)"},"pdf":{"textLayer":"Has readable text layer","language":"Document language declared","title":"Document title set","tagged":"PDF is tagged (structured)","pdfuaXmp":"PDF/UA-1 XMP identification metadata","displayDocTitle":"ViewerPreferences/DisplayDocTitle enabled","bookmarks":"Bookmarks present"},"pptx":{"title":"Presentation title set","language":"Language declared","slideTitles":"All slides have title placeholders","altText":"Images have alt text","readingOrder":"Slide reading order uses placeholders","linkText":"Hyperlinks have descriptive text"}},"actions":{"downloadCsv":"Download Full Report CSV →","downloadJson":"Download as JSON","unlockWithPro":"Unlock with Pro, €999/yr","seeWhatIncluded":"See what’s included in Pro"},"ariaLabels":{"document":"Document","lock":"Lock","upload":"Upload"},"fileTypes":{"docx":"Word (.docx)","pdf":"PDF","pptxOne":"PowerPoint (.pptx) · {count} slide","pptxOther":"PowerPoint (.pptx) · {count} slides"},"auditDetails":{"docx":{"titleFound":"Title: \"{title}\"","titleMissing":"No title found in document metadata","titleFix":"In Word: File > Properties > Summary > Title","languageFound":"Language: {lang}","languageDetected":"Detected","languageMissing":"No language declaration found — screen readers may use wrong pronunciation","languageFix":"In Word: Review > Language > Set Proofing Language","headingsFound":"{count, plural, one {# heading detected using Word heading styles} other {# headings detected using Word heading styles}}","headingsMissing":"No heading styles found — document appears to use only body text","headingsFix":"Use Word’s built-in Heading 1, Heading 2 etc. Styles instead of manually bolded text","altTextNoImages":"No images found","altTextCount":"{descCount}/{imageCount} images have alt text descriptions","altTextFix":"Right-click image > Edit Alt Text > add a description. Mark decorative images as decorative.","tableHeadersFound":"{count, plural, one {# table found, header row style detected} other {# tables found, header row style detected}}","tableHeadersMissing":"{count, plural, one {# table found but no header row style detected} other {# tables found but no header row style detected}}","tableHeadersNone":"No tables found","tableHeadersFix":"Select the first row of your table > Table Design > check ‘Header Row’","linkTextBad":"{count, plural, one {# non-descriptive hyperlink found (e.g. \"click here\")} other {# non-descriptive hyperlinks found (e.g. \"click here\")}}","linkTextGood":"{count, plural, one {# hyperlink checked — all descriptive} other {# hyperlinks checked — all descriptive}}","linkTextFix":"Replace vague link text like ‘click here’ with the destination or purpose, e.g. ‘Download the EAA compliance guide’","textContentFound":"Real text content detected","textContentMissing":"Very little text found — document may be a scanned image","textContentFix":"Run OCR on scanned documents and ensure the output is properly tagged text"},"pdf":{"textLayerFound":"Text layer detected in PDF","textLayerMissing":"No text layer found — this may be a scanned image PDF","textLayerFix":"Use Adobe Acrobat’s OCR feature to add a text layer, then check for proper reading order","languageFound":"Language entry found in PDF metadata","languageMissing":"/Lang entry missing from PDF metadata","languageFix":"In Acrobat: File > Properties > Description > Language","titleFound":"Title found in PDF metadata","titleMissing":"No /Title entry in PDF metadata","titleFix":"In Acrobat: File > Properties > Description > Title","taggedFound":"Tag structure markers detected","taggedMissing":"No MarkInfo/Marked entry — PDF may be untagged","taggedFix":"In Acrobat Pro: Accessibility > Add Tags to Document. Review the tag tree to ensure correct reading order.","pdfuaXmpFound":"Pdfuaid:part marker found in XMP stream","pdfuaXmpMissing":"No pdfuaid:part XMP marker — document cannot claim PDF/UA-1 conformance without it","pdfuaXmpFix":"Add pdfuaid:part=1 to the XMP metadata stream. In Acrobat Pro: File > Properties > Additional Metadata. Use PAC or veraPDF to verify.","displayDocTitleFound":"DisplayDocTitle=true found in viewer preferences","displayDocTitleMissing":"DisplayDocTitle not set — filename may show in title bar instead of document title","displayDocTitleFix":"In Acrobat Pro: File > Properties > Initial View > Window Options > Show: Document Title","bookmarksLabel":"Bookmarks present ({pages} pages)","bookmarksFound":"Bookmark/outline structure found","bookmarksMissing":"{pages}-page document has no bookmarks","bookmarksFix":"In Acrobat: use Bookmarks panel to add navigation structure for documents over 9 pages"},"pptx":{"titleFound":"Title: \"{title}\"","titleMissing":"No title in document properties","titleFix":"In PowerPoint: File > Info > Properties > Title","languageFound":"Language attribute found in presentation","languageMissing":"No language declaration found","languageFix":"In PowerPoint: File > Options > Language > set editing/display language","slideTitlesAllPresent":"{count, plural, one {# slide — all have title placeholders} other {# slides — all have title placeholders}}","slideTitlesMissing":"{missing}/{total} slide(s) missing title placeholder","slideTitlesFix":"In PowerPoint: Insert > Text Box is not a title — use the ‘Click to add title’ placeholder instead","altTextNoImages":"No images found","altTextCount":"{altCount}/{imgCount} images have alt text descriptions","altTextFix":"Right-click image > ‘Edit Alt Text’ > enter a meaningful description. Mark decorative images as decorative.","readingOrderFound":"Structured placeholders detected — supports logical reading order","readingOrderMissing":"Slides use free-floating text boxes which can disrupt reading order","readingOrderFix":"Use slide layouts with structured placeholders. In Acrobat (exported PDF): set reading order via Tags panel.","linkTextBad":"{count, plural, one {# non-descriptive hyperlink found} other {# non-descriptive hyperlinks found}}","linkTextGood":"{count, plural, one {# hyperlink — all descriptive} other {# hyperlinks — all descriptive}}","linkTextNone":"No hyperlinks found","linkTextFix":"Replace vague link text like ‘click here’ with a description of the destination"}},"csv":{"headers":{"check":"Check","status":"Status","severity":"Severity","detail":"Detail","wcag":"WCAG","fix":"Fix"},"pass":"PASS","fail":"FAIL"},"evidence":{"labels":{"fileName":"File name","fileType":"File type","fileSize":"File size","issuesFound":"Issues found","checksPassed":"Checks passed","criticalIssues":"Critical issues","highSeverityIssues":"High severity issues","mediumSeverityIssues":"Medium severity issues","lowSeverityIssues":"Low severity issues","overallScore":"Overall score","topFailingCheck":"Top failing check","processingNote":"Processing note"},"summary":"{filename} — {issues, plural, one {# issue} other {# issues}}, {passes, plural, one {# pass} other {# passes}}","sections":{"documentDetailsHeading":"Document Details","issuesFoundHeading":"Issues Found","issuesFoundIntro":"{count, plural, one {# accessibility issue found.} other {# accessibility issues found.}} Each row shows the check, severity, the detail observed in the file, the WCAG/PDF/UA criterion, and the recommended fix.","criticalIssuesHeading":"Critical Issues (require remediation before publication)","passingChecksHeading":"Passing Checks","methodHeading":"Method","methodBody":"The file was processed entirely client-side (in your browser) and never uploaded..docx and.pptx files are unzipped via JSZip and the contained XML inspected for title metadata, language declarations, heading styles, image alt text (descr attributes), table headers, slide titles, hyperlink text, and structural placeholders..pdf files are scanned for /Title, /Lang, /MarkInfo (tagged structure), pdfuaid:part XMP markers, ViewerPreferences/DisplayDocTitle, and /Outlines (bookmarks). Mapped to WCAG 2.2 SC 1.1.1, 1.3.1, 1.4.3, 2.4.2, 2.4.4, 2.4.5, 2.4.6, 3.1.1; PDF/UA-1 (ISO 14289-1) §6.7.11 and §7.1; and EN 301 549 V3.2.1 Chapter 10 (non-web documents). EAA Annex I §VIII covers e-books."},"tableHeaders":{"index":"#","check":"Check","severity":"Severity","detail":"Detail","wcagStandard":"WCAG / Standard","fix":"Fix"},"criticalListItem":"{check} — {detail} ({wcag})"}},"eaa-ready-quiz":{"meta":{"title":"EAA Ready Quiz","description":"Test your knowledge of the European Accessibility Act, EN 301 549, WCAG 2.1, and accessibility best practice."},"header":{"title":"Are you EAA Ready?","subtitle":"10 questions drawn randomly from a pool of {poolSize}, covering the EAA, EN 301 549, WCAG 2.1, and accessibility best practice.","howItWorks":"How the quiz works:","howItWorksBody":"Each session picks 10 different questions at random. After each answer you see whether you were correct and a hint with the source reference. Restart for a new set of questions."},"quiz":{"questionOf":"Question {current} of {total}","correct":"Correct!","notQuite":"Not quite.","nextQuestion":"Next Question →","seeResults":"See Results"},"results":{"scoreLabel":"{score}/{total}, {percent}%","tiers":{"expert":"Expert","competent":"Competent","developing":"Developing","beginner":"Beginner"},"feedback":{"expert":"Perfect score, you have expert-level knowledge of the EAA and WCAG requirements.","competent":"Good knowledge. Review the questions you missed and explore our tools to go deeper.","developing":"Developing knowledge. Focus on the EAA Scope, EN 301 549, and WCAG AA requirements.","beginner":"Needs work. Start with our WCAG Checklist and EAA compliance guides before retrying."},"newQuiz":"New Random Quiz","reviewTitle":"Review Your Answers","yourAnswer":"Your answer: {answer}","correctLabel":"Correct:","notAnswered":"(not answered)"},"categories":{"eaaDeadlines":"EAA Deadlines","eaaScope":"EAA Scope","technicalStandards":"Technical Standards","wcag":"WCAG","enforcement":"Enforcement","aria":"ARIA","mobile":"Mobile","colour":"Colour","forms":"Forms","keyboard":"Keyboard","multimedia":"Multimedia"},"export":{"toolName":"EAA Ready Quiz","downloadJson":"Download JSON","downloadHint":"Questions + answers + score","topicLabel":"Topic: {category}","scoreResultLabel":"Score","knowledgeTierLabel":"Knowledge tier","correctAnswersLabel":"Correct answers","incorrectAnswersLabel":"Incorrect answers","questionPoolSizeLabel":"Question pool size","scoreValue":"{score} / {total} ({percent}%)","summaryComplete":"Score {score}/{total} ({percent}%), {tier}","summaryInProgress":"In progress: {answered}/{total} answered","methodHeading":"Method","methodBody":"Knowledge check covering EAA Article references, EN 301 549 V3.2.1 (2021-03) clauses and WCAG 2.2 success criteria. Each round draws {perRound} questions at random from a pool of {poolSize}. Each question records the question text, the option selected, the correct option, and an explanatory hint citing the underlying EAA Article or WCAG SC.","scoreHeading":"Score","perTopicHeading":"Per-topic breakdown","topicHeader":"Topic","correctHeader":"Correct","askedHeader":"Asked","reviewHeading":"Question-by-question review","questionLabelTemplate":"Q{n}. {question}","qTopic":"Topic","qCorrectAnswer":"Correct answer","qYourAnswer":"Your answer","qResult":"Result","qHintSource":"Hint / source","qResultCorrect":"Correct","qResultIncorrect":"Incorrect","qResultNotAnswered":"Not answered","inputQuestionsAsked":"Questions asked","inputAnswersGiven":"Answers given","inputPoolSize":"Question pool size"},"questions":{"q1":{"q":"When did the EAA (Directive 2019/882) enter into force for new products and services?","options":["28 June 2022","28 June 2025","28 June 2027"],"hint":"Article 31 sets the application date.","category":"EaaDeadlines"},"q2":{"q":"What is the maximum transition period allowed for service contracts signed before 28 June 2025?","options":["1 year","3 years","5 years"],"hint":"Article 32 provides for a transitional period until 28 June 2030.","category":"EaaDeadlines"},"q3":{"q":"Self-service terminals already in service before 28 June 2025 may continue to be used for up to:","options":["5 years","10 years","20 years"],"hint":"Article 32(2) allows a 20-year extended period for in-service terminals.","category":"EaaDeadlines"},"q4":{"q":"Which business type is fully exempt from the EAA's service requirements?","options":["Large corporations","Public bodies","Microenterprises (<10 staff, <€2 M turnover)"],"hint":"Recital 70 and Article 14 grant full exemption to microenterprises for services.","category":"EaaScope"},"q5":{"q":"Does the microenterprise exemption apply to manufacturers of products?","options":["Yes, all products","No, manufacturers must comply regardless of size","Only for hardware"],"hint":"Article 14 limits the exemption to service providers, not product manufacturers.","category":"EaaScope"},"q6":{"q":"Which sectors are explicitly in scope of the EAA?","options":["Banking, e-commerce, transport, telecoms, e-books, audiovisual media","Healthcare, construction, and agriculture","Only public-sector websites and apps"],"hint":"Article 2 lists the in-scope product and service categories.","category":"EaaScope"},"q7":{"q":"Are physical ATMs covered by the EAA?","options":["Yes, as self-service terminals","No, only software is covered","Only ATMs deployed after 2025"],"hint":"Annex I Section II covers self-service terminals including ATMs.","category":"EaaScope"},"q8":{"q":"Does the EAA cover e-commerce websites?","options":["Yes, explicitly","No, only mobile apps","Only B2B platforms"],"hint":"Article 2(2)(f) includes e-commerce services.","category":"EaaScope"},"q9":{"q":"Which technical standard provides 'presumption of conformity' with the EAA?","options":["ISO 9001","EN 301 549","WCAG 2.0"],"hint":"EN 301 549 is harmonised under the EAA.","category":"TechnicalStandards"},"q10":{"q":"EN 301 549 v3.2.1 (the current harmonised standard) incorporates which WCAG version as its web content requirements?","options":["WCAG 2.0","WCAG 2.1 Level AA","WCAG 2.2 Level AAA"],"hint":"EN 301 549 v3.2.1 (2021) references WCAG 2.1 Level AA. A future revision is expected to reference WCAG 2.2, but as of 2026 the harmonised standard is v3.2.1.","category":"TechnicalStandards"},"q11":{"q":"What conformance level is required for web content under EN 301 549?","options":["Level A only","Level AA","Level AAA"],"hint":"EN 301 549 references WCAG 2.1 up to and including Level AA.","category":"TechnicalStandards"},"q12":{"q":"WCAG SC 1.4.3 specifies a minimum contrast ratio for normal text of:","options":["3:1","4.5:1","7:1"],"hint":"SC 1.4.3 requires 4.5:1 for normal text at Level AA.","category":"Wcag"},"q13":{"q":"WCAG SC 1.4.11 Non-text Contrast applies to:","options":["Images of text only","UI components and graphical objects","Video captions"],"hint":"SC 1.4.11 requires 3:1 contrast for UI components and graphics.","category":"Wcag"},"q14":{"q":"Which WCAG criterion requires that text can be resized up to 200% without loss of content?","options":["SC 1.4.4","SC 1.4.3","SC 2.4.6"],"hint":"SC 1.4.4 Resize text (Level AA).","category":"Wcag"},"q15":{"q":"SC 2.4.7 requires that:","options":["Focus is always visible on keyboard-operable UI","All images have alt text","Forms have visible labels"],"hint":"SC 2.4.7 Focus Visible (Level AA).","category":"Wcag"},"q16":{"q":"WCAG Level A has how many success criteria?","options":["25","30","32"],"hint":"WCAG 2.2 includes 32 Level A criteria (WCAG 2.1 had 30; WCAG 2.2 added SC 3.2.6 and SC 3.3.7).","category":"Wcag"},"q17":{"q":"Which WCAG principle covers time-based media (audio/video)?","options":["Perceivable","Operable","Understandable"],"hint":"Guideline 1.2 falls under Principle 1, Perceivable.","category":"Wcag"},"q18":{"q":"SC 1.1.1 requires all non-text content to have:","options":["A text alternative","A caption","A language attribute"],"hint":"SC 1.1.1 Non-text Content (Level A).","category":"Wcag"},"q19":{"q":"Who enforces the EAA in each EU member state?","options":["The European Commission directly","Market surveillance authorities designated by each member state","ETSI only"],"hint":"Article 21 requires member states to designate market surveillance bodies.","category":"Enforcement"},"q20":{"q":"What document must economic operators prepare to demonstrate EAA compliance?","options":["ISO certification","EU Declaration of Conformity","Voluntary Accessibility Report"],"hint":"Article 15 requires an EU Declaration of Conformity.","category":"Enforcement"},"q21":{"q":"Accessibility statements required under the Web Accessibility Directive must be updated at least:","options":["Every 6 months","Annually","Every 3 years"],"hint":"The WAD implementing decision requires annual updates.","category":"Enforcement"},"q22":{"q":"What is the minimum information that must be in an EAA accessibility statement?","options":["Contact details and feedback mechanism","A list of all WCAG AA failures","Third-party audit report"],"hint":"Annex I Section VI specifies accessibility information requirements.","category":"Enforcement"},"q23":{"q":"Under the EAA, can a product be placed on the market without meeting accessibility requirements if it would cause a 'fundamental alteration'?","options":["Yes, if compliance would fundamentally alter the nature of the product","No, there are no exceptions","Only with Commission approval"],"hint":"Article 14(5) allows exceptions where compliance would fundamentally alter the product.","category":"Enforcement"},"q24":{"q":"A disproportionate burden assessment must be documented and:","options":["Kept confidential","Submitted to the market surveillance authority on request","Published on the company website"],"hint":"Article 14(7) requires the assessment to be available on request.","category":"Enforcement"},"q25":{"q":"EN 301 549 Chapter 11 covers:","options":["Web content (browsers)","Non-web software (native apps)","Self-service terminals"],"hint":"Chapter 11 addresses non-web software accessibility.","category":"TechnicalStandards"},"q26":{"q":"EN 301 549 Chapter 12 covers:","options":["Documentation and support services","Closed functionality","ICT with two-way voice"],"hint":"Chapter 12 requires accessible documentation and support.","category":"TechnicalStandards"},"q27":{"q":"Must help desks and customer support services be accessible under EN 301 549?","options":["Yes, under Chapter 12","No, only digital products","Only for banking services"],"hint":"EN 301 549 Chapter 12 requires accessible support services.","category":"TechnicalStandards"},"q28":{"q":"What does 'closed functionality' mean in EN 301 549?","options":["ICT that prevents use of assistive technology","Software only available offline","Products restricted to internal use"],"hint":"Closed functionality (Chapter 5) covers ICT that blocks AT use (e.g. Kiosks).","category":"TechnicalStandards"},"q29":{"q":"The ARIA `role='button'` attribute is needed when:","options":["A native <button> is used","A <div> or <span> is used as an interactive button","Any element is clicked"],"hint":"ARIA should supplement semantics only where native HTML is insufficient.","category":"Aria"},"q30":{"q":"Which ARIA attribute provides the accessible name for an element without visible text?","options":["Aria-describedby","Aria-label","Aria-role"],"hint":"Aria-label supplies an accessible name directly.","category":"Aria"},"q31":{"q":"What does a positive tabindex value (e.g. Tabindex='2') do?","options":["Removes the element from the tab order","Causes the element to receive focus before tabindex='0' elements","Has no effect"],"hint":"Positive tabindex disrupts natural DOM order, WCAG SC 2.4.3.","category":"Aria"},"q32":{"q":"Which HTML element should be used for the main navigation landmark?","options":["<div role='nav'>","<nav>","<section>"],"hint":"The native <nav> element has an implicit landmark role.","category":"Aria"},"q33":{"q":"What is the first rule of ARIA?","options":["Always use ARIA for all interactive elements","Use native HTML elements instead of ARIA where possible","ARIA replaces the need for semantic HTML"],"hint":"W3C's ARIA authoring practices recommend native HTML first.","category":"Aria"},"q34":{"q":"WCAG SC 2.5.5 requires touch targets to be at least:","options":["24×24 CSS pixels","44×44 CSS pixels","48×48 CSS pixels"],"hint":"SC 2.5.5 Target Size (Enhanced) is 44×44px at Level AAA. SC 2.5.8 requires 24×24 at AA.","category":"Mobile"},"q35":{"q":"WCAG SC 1.3.4 Orientation requires that content:","options":["Works in landscape only","Works in both portrait and landscape unless essential","Always defaults to portrait"],"hint":"SC 1.3.4 (Level AA) prevents locking orientation.","category":"Mobile"},"q36":{"q":"SC 2.5.1 requires that complex gestures (pinch, multi-finger) have:","options":["A single-pointer alternative","An ARIA description","A visible label"],"hint":"SC 2.5.1 Pointer Gestures (Level A).","category":"Mobile"},"q37":{"q":"What minimum contrast ratio does WCAG AA require for large text (18pt / 14pt bold)?","options":["2.5:1","3:1","4.5:1"],"hint":"SC 1.4.3 requires 3:1 for large text at Level AA.","category":"Colour"},"q38":{"q":"Can colour alone be used to convey information under WCAG?","options":["Yes, if contrast is sufficient","No, SC 1.4.1 prohibits colour as the sole visual means","Only if a text equivalent exists elsewhere on the page"],"hint":"SC 1.4.1 Use of Colour (Level A).","category":"Colour"},"q39":{"q":"WCAG AAA requires an enhanced contrast ratio of how much for normal text?","options":["4.5:1","7:1","10:1"],"hint":"SC 1.4.6 Contrast Enhanced requires 7:1.","category":"Colour"},"q40":{"q":"SC 3.3.1 requires that input errors are:","options":["Highlighted in red only","Identified and described to the user in text","Prevented entirely"],"hint":"SC 3.3.1 Error Identification (Level A).","category":"Forms"},"q41":{"q":"SC 3.3.2 requires that labels or instructions are provided:","options":["Only for complex forms","When user input is required","Only for password fields"],"hint":"SC 3.3.2 Labels or Instructions (Level A).","category":"Forms"},"q42":{"q":"SC 3.3.4 Error Prevention applies to which types of submissions?","options":["All form submissions","Only financial or legal transactions","Only transactions involving deletion of data"],"hint":"SC 3.3.4 (Level AA) targets legal, financial, or test submissions.","category":"Forms"},"q43":{"q":"What does WCAG SC 1.3.5 Identify Input Purpose require?","options":["All inputs must have a visible label","Inputs collecting personal data must have a programmatically determinable purpose","Password fields must be masked"],"hint":"SC 1.3.5 enables autofill for personal data fields (Level AA).","category":"Forms"},"q44":{"q":"SC 2.1.1 requires that all functionality is available via:","options":["Mouse only","Keyboard interface","Voice commands"],"hint":"SC 2.1.1 Keyboard (Level A).","category":"Keyboard"},"q45":{"q":"What is a 'keyboard trap' in WCAG terms?","options":["A shortcut key that conflicts with assistive technology","A situation where keyboard focus cannot be moved away from a component","A hidden focus indicator"],"hint":"SC 2.1.2 No Keyboard Trap (Level A).","category":"Keyboard"},"q46":{"q":"SC 2.4.1 requires that:","options":["All pages have a title","There is a mechanism to bypass blocks of content (e.g. Skip links)","Navigation is consistent"],"hint":"SC 2.4.1 Bypass Blocks (Level A).","category":"Keyboard"},"q47":{"q":"SC 2.4.4 requires that the purpose of a link can be determined from:","options":["The URL alone","The link text, or context","The page title"],"hint":"SC 2.4.4 Link Purpose (in Context) (Level A).","category":"Keyboard"},"q48":{"q":"What must pre-recorded audio-only content provide under WCAG SC 1.2.1?","options":["A transcript","Captions","Audio description"],"hint":"SC 1.2.1 requires a text alternative (transcript) for audio-only.","category":"Multimedia"},"q49":{"q":"SC 1.2.5 requires audio descriptions for:","options":["Live video","Pre-recorded video","Audio-only content"],"hint":"SC 1.2.5 Audio Description (Prerecorded) (Level AA).","category":"Multimedia"},"q50":{"q":"What does WCAG SC 2.2.2 require for moving, blinking, or scrolling content?","options":["It must stop after 5 seconds","Users must be able to pause, stop, or hide it","It must have captions"],"hint":"SC 2.2.2 Pause, Stop, Hide (Level A).","category":"Multimedia"},"q51":{"q":"Under SC 1.3.1, form fields must have labels that are:","options":["Visible and positioned above the field","Programmatically associated (e.g. <label for> or aria-labelledby)","Bold and red"],"hint":"SC 1.3.1 Info and Relationships (Level A), visible position is best practice but not required.","category":"Forms"}}},"ebook-checklist":{"meta":{"title":"E-Book & Digital Publishing Accessibility Checklist, EAA Annex I Section VIII","description":"EAA Annex I Section VIII compliance checklist, verify that your e-books and digital publications meet European Accessibility Act requirements."},"header":{"title":"E-Book & Digital Publishing Checklist","subtitle":"EAA Annex I Section VIII Compliance Checklist"},"description":"EAA Annex I Section VIII compliance checklist, verify that your e-books and digital publications meet European Accessibility Act requirements.","features":{"f1":"EAA Annex I Section VIII full coverage","f2":"17 checkpoints across metadata, structure, content & reading systems","f3":"Pass / Partial / Fail / N/A with notes per item","f4":"How-to-test guidance and common failures for every checkpoint","f5":"Links to relevant testing tools on AccessibilityRef","f6":"Progress auto-saved in your browser","f7":"Export Word report with notes","f8":"Direct links to EAA Directive and EPUB Accessibility spec"},"categories":{"metadata":{"label":"Accessibility Metadata","description":"EPUB Accessibility 1.1, Publications must declare their accessibility features in metadata."},"structure":{"label":"Content Structure","description":"WCAG applied to digital publications, reading order, navigation, headings."},"content":{"label":"Content Accessibility","description":"Images, maths, tables, and text content within the publication."},"reading":{"label":"Reading System Compatibility","description":"Publications must work with reading systems and assistive technology."}},"items":{"md1":{"text":"EPUB accessibility metadata is present, all six required schema.org/EPUB Accessibility terms.","guidance":"The OPF file must include all six required metadata terms: schema:accessMode, schema:accessModeSufficient, schema:accessibilityFeature, schema:accessibilityHazard, schema:accessibilitySummary, and dcterms:conformsTo."},"md2":{"text":"Accessibility summary describes the publication's accessibility in human-readable text.","guidance":"The accessibilitySummary field should describe features and limitations, 'This publication includes alt text for all images. Mathematical content uses MathML.'"},"md3":{"text":"Access modes are declared (textual, visual, auditory).","guidance":"Declaring access modes helps reading systems and users understand what sensory capabilities are needed to consume the content."},"st1":{"text":"Reading order is logical and matches visual presentation order.","guidance":"The document's DOM order must reflect the intended reading sequence. Side panels, footnotes, and figures must appear in context."},"st2":{"text":"Table of contents is navigable by assistive technology.","guidance":"The ToC must use proper <nav epub:type='toc'> with nested lists. Each entry must be a link to the corresponding section."},"st3":{"text":"Heading structure is logical and sequential (H1-H6).","guidance":"Chapters should use H1, sections H2, subsections H3. No skipped levels. Headings enable screen reader navigation."},"st4":{"text":"Page navigation landmarks are present (epub:type='pagebreak').","guidance":"Page break markers allow users to reference specific pages, essential for classroom use and citations."},"st5":{"text":"Footnotes and endnotes are linked bidirectionally.","guidance":"Each footnote reference must link to the note, and each note must link back to the reference point. Use epub:type='noteref' and epub:type='footnote'."},"co1":{"text":"All images have meaningful alt text in the publication markup.","guidance":"Alt text is set in the EPUB HTML, <img alt='...'/>. Decorative images use alt=''. Complex images need long descriptions."},"co2":{"text":"Data tables use proper header cells (<th>) with scope attributes.","guidance":"Tables must be structured data tables, not layout tables. Headers allow screen readers to announce column/row context."},"co3":{"text":"Mathematical content uses MathML, not images.","guidance":"MathML is read aloud by screen readers and can be converted to braille. Image-based equations are completely inaccessible."},"co4":{"text":"Text content is real text, not images of text.","guidance":"All body text, headings, and captions must be selectable, searchable, reflowable text. Images of text prevent resizing and translation."},"rs1":{"text":"Text content is reflowable, not fixed-layout unless essential.","guidance":"Reflowable EPUB allows text resizing, reflow, and custom styling. Only use fixed layout when the content genuinely requires it."},"rs2":{"text":"Font size and line spacing are adjustable by the reading system.","guidance":"Don't override user font preferences with fixed CSS. Use relative units (em, rem) not absolute (px)."},"rs3":{"text":"Text-to-speech is not blocked by DRM.","guidance":"Digital Rights Management must not prevent legitimate text-to-speech functionality. Blind users depend on TTS to read e-books."},"rs4":{"text":"Default colour contrast meets 4.5:1 ratio.","guidance":"The publication's default text and background colours must meet WCAG contrast requirements."},"rs5":{"text":"Colour and contrast are customisable by the reading system.","guidance":"Don't use CSS that prevents reading system colour overrides. Avoid!important on background-color and color properties."}},"export":{"filename":"Ebook-checklist","title":"E-BOOK & DIGITAL PUBLISHING","subtitle":"EAA Annex I Section VIII Compliance Checklist"},"links":{"eaaDirective":"EAA Directive 2019/882","epubAccessibility":"EPUB Accessibility 1.1"}},"ecommerce-checklist":{"meta":{"title":"E-Commerce Accessibility Checklist, EAA Annex I Section IX","description":"EAA Annex I Section IX, E-Commerce Services compliance checklist, verify that your online shop meets European Accessibility Act requirements."},"header":{"title":"E-Commerce Accessibility Checklist","subtitle":"EAA Annex I Section IX, E-Commerce Services"},"description":"EAA Annex I Section IX, E-Commerce Services compliance checklist, verify that your online shop meets European Accessibility Act requirements.","features":{"f1":"EAA Annex I Section IX full coverage","f2":"23 checkpoints across browsing, product pages, checkout, post-purchase & cookies","f3":"Pass / Partial / Fail / N/A with notes per item","f4":"How-to-test guidance and common failures for every checkpoint","f5":"Links to relevant testing tools on AccessibilityRef","f6":"Progress auto-saved in your browser","f7":"Export Word report with notes","f8":"Direct links to EAA Directive and EN 301 549"},"categories":{"browsing":{"label":"Product Browsing & Discovery","description":"EAA Annex I §IX, Product listings, search, and filtering must be accessible to all users."},"product":{"label":"Product Detail Pages","description":"Individual product pages must present all information accessibly."},"cart":{"label":"Cart & Checkout","description":"The purchase flow from cart to payment confirmation must be fully accessible."},"post":{"label":"Post-Purchase & Account","description":"Order confirmations, account management, and returns must also be accessible."},"cookies":{"label":"Cookie Consent & Legal","description":"Cookie banners and legal notices must not block accessibility."}},"items":{"br1":{"text":"Product images have descriptive alt text, not just the product name.","guidance":"Alt text should describe what the image shows: 'Blue cotton crew-neck t-shirt, front view' not just 'T-shirt'. Multiple images need distinct descriptions.","testMethod":"Open the product listing page and inspect each product image using browser DevTools (right-click > Inspect). Check the alt attribute on every <img> element. The alt text must describe the specific product appearance, not just repeat the product name. Also test with a screen reader (NVDA or VoiceOver) to hear what is announced for each image.","commonFailures":{"f1":"Alt text is just the product name ('T-shirt') with no description of colour, style, or view angle","f2":"All product images on a listing page share the same generic alt text","f3":"Alt text is auto-generated from the filename ('IMG_4521.jpg')","f4":"Decorative lifestyle images mixed with product images all lack alt text entirely"}},"br2":{"text":"Product information (price, availability, specifications) is available in text, not image-only.","guidance":"Pricing in images cannot be read by screen readers. All product data must be real text or have programmatic alternatives.","testMethod":"On the product listing page, try to select and copy the price, availability status, and key specifications. If the text is selectable, it is real text. Also inspect the DOM to confirm these values are in text nodes or have aria-labels. If any of this information is embedded inside an image with no text alternative, it fails.","commonFailures":{"f1":"Price displayed as part of a promotional banner image with no alt text","f2":"Availability ('In Stock' / 'Out of Stock') shown as a coloured dot with no text label","f3":"Specifications rendered as an infographic image without a text alternative","f4":"Sale price and original price shown as styled images rather than text with appropriate markup"}},"br3":{"text":"Pricing is programmatically determinable, not embedded in images.","guidance":"Screen readers must be able to announce the price. Use text or aria-label, never price as part of a product image.","testMethod":"Navigate to a product with a screen reader and listen for the price announcement. It must be announced clearly (e.g. '29 euros and 99 cents'). Inspect the HTML to confirm the price is in a text element. Check that sale prices, original prices, and discount percentages are all programmatically available, not just visually styled.","commonFailures":{"f1":"Price is rendered inside a canvas element or SVG with no accessible text","f2":"Currency symbol and amount are in separate elements that screen readers announce disjointedly","f3":"Discounted price is visually crossed out but screen reader announces both prices without distinction","f4":"Price is loaded dynamically via JavaScript but the aria-live region does not update"}},"br4":{"text":"Filtering and sorting controls are keyboard-operable.","guidance":"Category filters, price sliders, sort dropdowns, all must work with keyboard alone. Sliders need arrow key support.","testMethod":"Navigate to the product listing page and put down your mouse. Using only Tab, Shift+Tab, Enter, Space, and arrow keys, attempt to: (1) open the sort dropdown and select an option, (2) apply a category filter, (3) adjust a price range slider, (4) clear all filters. Every control must be reachable and operable. Check that focus is visible on each control.","commonFailures":{"f1":"Price range slider only responds to mouse drag, arrow keys have no effect","f2":"Filter checkboxes are custom-styled divs that cannot receive keyboard focus","f3":"Sort dropdown opens on mouse hover but has no keyboard trigger","f4":"Applying a filter reloads the page and focus jumps to the top instead of staying on the filter area"}},"br5":{"text":"Search results count is announced to screen readers.","guidance":"When results update after filtering or searching, announce 'Showing 24 results for blue shirts' via aria-live region.","testMethod":"Perform a search or apply a filter while a screen reader is active. Listen for an announcement of the updated results count (e.g. '24 results found'). Inspect the HTML for an aria-live='polite' region that contains the results count. If results update silently without any screen reader announcement, it fails.","commonFailures":{"f1":"Results update visually but no aria-live region announces the change","f2":"Aria-live region exists but announces the entire page content instead of just the count","f3":"Zero results state shows a visual message but screen reader users hear nothing","f4":"Results count is announced but uses aria-live='assertive', interrupting the user unnecessarily"}},"pd1":{"text":"Size, colour, and variant selectors are keyboard-operable and labelled.","guidance":"Dropdown menus, colour swatches, and size buttons must have accessible names and be operable with keyboard. Colour swatches need text labels, not just colour.","testMethod":"Navigate to a product page with variant selectors. Using keyboard only, Tab to each selector (size, colour, material). Verify: (1) each control is focusable, (2) it has a visible focus indicator, (3) it can be activated with Enter or Space, (4) colour swatches have text labels (not just a coloured circle). Test with a screen reader to confirm the accessible name matches the visual label.","commonFailures":{"f1":"Colour swatches are clickable divs with no accessible name, screen reader announces 'clickable' only","f2":"Size selector is a set of styled spans that cannot receive keyboard focus","f3":"Colour swatch labelled only by background-color CSS with no aria-label or visible text","f4":"Variant selection changes the product image but does not announce the change to screen readers"}},"pd2":{"text":"Interactive elements (add to cart, wishlist, compare) have accessible names.","guidance":"Icon-only buttons like a heart icon must have aria-label='Add to wishlist'. The cart button must clearly announce its purpose.","testMethod":"Inspect every interactive element on the product page using DevTools. Check that each button or link has an accessible name (visible text, aria-label, or aria-labelledby). Test with a screen reader: navigate to each button and verify it announces its purpose clearly. Icon-only buttons must announce their function, not 'button' or 'image'.","commonFailures":{"f1":"Heart icon button has no aria-label, screen reader announces 'button' with no context","f2":"Add to cart button contains only an SVG icon with no text alternative","f3":"Compare button uses a title attribute instead of aria-label, not reliably announced by all screen readers","f4":"'Quick view' overlay trigger has no accessible name"}},"pd3":{"text":"Product videos have captions.","guidance":"Demo videos, unboxing videos, and product walkthroughs must have synchronised captions.","testMethod":"Play each product video on the page. Enable captions (CC button or settings menu). Verify: (1) captions exist, (2) they are synchronised with speech, (3) they include relevant non-speech sounds like '[music]' or '[clicking sound]', (4) speaker identification is present when multiple speakers appear. If auto-generated captions are used, check for accuracy of product-specific terms.","commonFailures":{"f1":"Product demo video has no captions at all","f2":"YouTube auto-captions are used with uncorrected errors in product names and specifications","f3":"Captions exist for the narrated part but not for on-screen text callouts or annotations","f4":"Video is embedded from a third-party platform that blocks caption display"}},"pd4":{"text":"Product specifications are presented in an accessible table with headers.","guidance":"Spec tables (dimensions, materials, weight) must use proper <th> headers so screen readers can announce column/row associations.","testMethod":"Inspect the product specifications section in DevTools. Verify that specifications are in a <table> element with <th> elements for column and/or row headers. Test with a screen reader by navigating the table, each cell should announce its associated header. If specifications are presented in a <div>-based layout without table semantics, check for appropriate ARIA roles (role='table', role='row', role='cell').","commonFailures":{"f1":"Specifications are in a visual table made of divs and spans with no table semantics","f2":"Table uses <td> for everything, no <th> headers defined","f3":"Specification data is in a definition list (<dl>) but with incorrect nesting","f4":"Table headers exist but are empty cells, screen reader announces nothing for column context"}},"ca1":{"text":"Cart contents are announced to screen readers when updated (aria-live).","guidance":"When a user adds or removes an item, the cart count and summary must be announced, 'Item added. Cart: 3 items, €45.00'.","testMethod":"With a screen reader active, add an item to the cart from a product page. Listen for an announcement confirming the action and the updated cart state. Then navigate to the cart page, remove an item, and verify the removal is announced. Inspect the HTML for aria-live regions wrapping the cart count or status messages.","commonFailures":{"f1":"Adding to cart shows a visual toast notification but screen reader announces nothing","f2":"Cart icon updates its badge number visually but the count is not in an aria-live region","f3":"Removing an item from the cart refreshes the page silently, no announcement of the change","f4":"Aria-live region announces 'Cart updated' but not the specific change (what was added/removed)"}},"ca2":{"text":"All checkout form fields have visible, persistent labels, not just placeholders.","guidance":"Name, address, payment fields all need <label> elements. Placeholder text disappears on input and is not a substitute.","testMethod":"Navigate to the checkout page and inspect each form field. Verify: (1) every input has a visible <label> element, (2) the label remains visible when the field contains text (not just placeholder), (3) the label is programmatically associated with the input via 'for' attribute or wrapping. Test by typing in a field, if the only text description disappears, it fails.","commonFailures":{"f1":"Placeholder text used as the only label, disappears when user starts typing","f2":"Labels exist in the DOM but are visually hidden with display:none, making them invisible to sighted users","f3":"Label text is present but not programmatically associated with the input (no 'for' attribute)","f4":"Grouped fields like 'Expiry Month / Year' share a single label that doesn't identify each field"}},"ca3":{"text":"Checkout form errors are identified in text and describe the specific problem.","guidance":"'Please enter a valid email address' not just 'Error in field 3'. Error messages must appear adjacent to the field.","testMethod":"Submit the checkout form with intentionally invalid data (empty required fields, invalid email format, incorrect card number). Verify: (1) error messages appear adjacent to the specific field, (2) each error describes the problem in plain language, (3) errors are announced by screen readers via aria-describedby or aria-live, (4) focus moves to the first error or an error summary.","commonFailures":{"f1":"Generic error message at the top of the page ('Please fix errors below') with no field-specific messages","f2":"Error shown only by turning the field border red, no text explanation","f3":"Error message says 'Invalid input' without specifying what is expected","f4":"Errors appear visually but are not announced to screen readers"}},"ca4":{"text":"Address fields use correct autocomplete attributes.","guidance":"Use autocomplete='shipping address-line1', autocomplete='cc-number' etc. This helps autofill tools and assistive technology.","testMethod":"Inspect each address and payment field in DevTools. Check that the autocomplete attribute is present and uses the correct token from the HTML specification (e.g. 'name', 'email', 'address-line1', 'postal-code', 'cc-number', 'cc-exp'). Test by using browser autofill, if fields populate correctly, the autocomplete values are likely correct.","commonFailures":{"f1":"No autocomplete attributes on any checkout fields","f2":"Autocomplete='off' used on address fields, blocking autofill for all users","f3":"Incorrect autocomplete values (e.g. Autocomplete='address' instead of autocomplete='address-line1')","f4":"Payment fields use autocomplete='off' for security reasons, breaking autofill for users with motor impairments"}},"ca5":{"text":"All payment methods offered are keyboard-accessible.","guidance":"Credit card forms, PayPal redirects, Apple Pay buttons, all must be reachable and activatable with keyboard.","testMethod":"At the payment step of checkout, put down your mouse. Using only keyboard (Tab, Shift+Tab, Enter, Space), attempt to: (1) select each payment method (credit card, PayPal, bank transfer, etc.), (2) fill in payment details, (3) complete the payment. Each payment option must be focusable and activatable. Third-party payment iframes must also be keyboard-accessible.","commonFailures":{"f1":"PayPal button is an iframe that traps keyboard focus","f2":"Credit card payment option is a custom radio button that cannot be selected with keyboard","f3":"Apple Pay / Google Pay buttons are not focusable via Tab","f4":"Payment method tabs require mouse click, Enter and Space keys do not activate them"}},"ca6":{"text":"Order review step is provided before final submission.","guidance":"For financial transactions, users must be able to review their order, correct errors, and confirm before the charge is processed.","testMethod":"Proceed through the checkout flow to the final step. Verify: (1) a review step shows all order details (items, quantities, prices, shipping address, payment method), (2) users can go back to modify any detail without losing entered data, (3) the final submit button is clearly labelled (e.g. 'Place Order and Pay') to indicate a financial commitment, (4) the review step is accessible to screen readers.","commonFailures":{"f1":"Clicking 'Continue' on the payment page immediately charges the card with no review step","f2":"Review step exists but does not show the total amount including shipping and tax","f3":"Back button on the review step clears previously entered payment information","f4":"Final submit button is labelled 'Continue' or 'Next' instead of clearly indicating a financial commitment"}},"po1":{"text":"Order confirmation is available in text (HTML email), not just a visual receipt image.","guidance":"Confirmation emails must be HTML with proper structure, not just a screenshot of the receipt. PDF receipts must be tagged. Under the EAA, the entire service, including post-purchase communications, must be accessible.","testMethod":"Complete a test purchase and check the confirmation email. Open it in a text-based email client or with a screen reader. Verify: (1) the email is HTML with proper heading structure, (2) order details (items, prices, totals) are in real text, not images, (3) any attached PDF receipt is tagged and readable by screen readers. Also check the on-screen confirmation page for the same criteria.","commonFailures":{"f1":"Confirmation email is a single large image of the receipt with no alt text","f2":"PDF receipt attachment is a scanned image with no text layer","f3":"HTML email uses table-based layout with no semantic structure, screen reader reads cells in wrong order","f4":"Order details are in real text but the header logo image has alt text that reads the entire company address"}},"po2":{"text":"Account creation and login are keyboard-accessible.","guidance":"Registration forms, password fields, 'show password' toggles, and social login buttons must all be keyboard-operable.","testMethod":"Navigate to the registration and login pages. Using keyboard only, attempt to: (1) fill in all registration fields, (2) toggle 'show password', (3) submit the form, (4) use social login buttons (Google, Facebook, Apple). Verify all controls are focusable, have visible focus indicators, and can be activated with Enter or Space.","commonFailures":{"f1":"'Show password' toggle is a custom element that cannot receive keyboard focus","f2":"Social login buttons are image links with no keyboard focus indicator","f3":"Registration form submits on Enter but login form requires mouse click on the submit button","f4":"Password strength indicator updates visually but is not announced to screen readers"}},"po3":{"text":"Account creation does not require CAPTCHA without an accessible alternative.","guidance":"Image CAPTCHAs exclude blind users. Use invisible CAPTCHA, email verification, or phone verification instead.","testMethod":"Attempt to create an account and observe whether a CAPTCHA is presented. If so, check: (1) is there an audio alternative for image CAPTCHAs, (2) is an invisible CAPTCHA (reCAPTCHA v3) used instead, (3) can the CAPTCHA be completed with keyboard alone. If the only option is a visual puzzle with no alternative, it fails.","commonFailures":{"f1":"Image CAPTCHA with no audio alternative, completely blocks blind users","f2":"ReCAPTCHA v2 checkbox is keyboard-accessible but the image challenge is not","f3":"Custom CAPTCHA puzzle (drag-and-drop) that is mouse-only","f4":"Audio CAPTCHA alternative exists but the audio quality is too poor to understand"}},"po4":{"text":"Returns and refund process is accessible end-to-end.","guidance":"The return request form, shipping label download, and refund status page must all be accessible. The EAA's general accessibility obligation covers the full service lifecycle, don't make returns harder than purchasing.","testMethod":"Navigate to the returns section of the account area. Using keyboard and screen reader, attempt the full return flow: (1) select an order to return, (2) choose a return reason, (3) submit the return request, (4) download or print the return label, (5) check refund status. Every step must be keyboard-operable and announced by screen readers.","commonFailures":{"f1":"Return label is generated as an inaccessible PDF that screen readers cannot read","f2":"Return reason dropdown is a custom component that cannot be operated with keyboard","f3":"Refund status page uses colour-only indicators (green = refunded, red = pending) with no text labels","f4":"Return request form requires uploading a photo with no alternative for users who cannot take photos"}},"po5":{"text":"Customer reviews section is accessible (submission form + display).","guidance":"Review star ratings need text alternatives. The review submission form needs labels. Reviews must be navigable by heading.","testMethod":"Navigate to the customer reviews section with a screen reader. Verify: (1) star ratings are announced as text (e.g. '4 out of 5 stars'), not just as images, (2) the review submission form has labelled fields, (3) the star rating input in the form is keyboard-operable, (4) individual reviews are navigable by heading or landmark. Check that 'helpful' vote buttons have accessible names.","commonFailures":{"f1":"Star rating displayed as an image with alt text 'stars' instead of '4 out of 5 stars'","f2":"Review submission star input requires mouse click, cannot be set with keyboard","f3":"Review text area has no visible label, only placeholder text","f4":"'Was this review helpful?' buttons are icon-only with no accessible names"}},"ck1":{"text":"Cookie consent banner is keyboard-operable.","guidance":"Users must be able to Tab to the banner, activate Accept/Reject, and dismiss it entirely with keyboard. It must not trap focus.","testMethod":"Reload the page in a fresh browser session (clear cookies first). Using keyboard only, verify: (1) focus moves to the cookie banner automatically or is reachable via Tab, (2) Accept and Reject buttons are focusable and activatable with Enter or Space, (3) any 'Manage preferences' panel is fully keyboard-operable, (4) after dismissing the banner, focus returns to the main page content and is not trapped.","commonFailures":{"f1":"Cookie banner appears but cannot be reached with Tab, focus goes straight to page content behind it","f2":"Accept button works with keyboard but Reject or Manage Preferences does not","f3":"Banner traps keyboard focus, user cannot Tab past it to reach page content","f4":"Closing the banner via the X button requires mouse click"}},"ck2":{"text":"Cookie consent controls have accessible names and roles.","guidance":"Buttons must be <button> elements with clear text. Custom-styled divs acting as buttons need role='button' and aria-label.","testMethod":"Inspect the cookie banner's HTML in DevTools. Verify: (1) Accept and Reject controls use <button> elements (or have role='button'), (2) each control has visible text or an aria-label, (3) toggle switches for cookie categories have accessible names and announce their state (on/off). Test with a screen reader to confirm each control is announced with its name and role.","commonFailures":{"f1":"Accept/Reject implemented as styled <div> elements with no role='button' or keyboard handling","f2":"Cookie category toggles are custom switches with no accessible name or state announcement","f3":"Close button is an SVG X icon with no aria-label","f4":"Consent banner uses generic link text ('Click here') instead of descriptive button labels"}},"ck3":{"text":"Cookie banner does not break focus order for the rest of the page.","guidance":"After dismissing the banner, focus should return to a logical position in the page, not jump to the end or get lost.","testMethod":"Dismiss the cookie banner using keyboard. Immediately press Tab and observe where focus lands. It should be on the first focusable element of the main page content (e.g. Skip link, first navigation item). If focus jumps to the page footer, gets lost (no visible focus indicator anywhere), or returns to a non-existent banner element, it fails.","commonFailures":{"f1":"After dismissing the banner, focus disappears, no visible focus indicator on any element","f2":"Focus jumps to the page footer after banner dismissal","f3":"Banner is removed from the DOM but focus remains on the now-removed element, causing screen reader confusion","f4":"Cookie preferences modal closes but focus does not return to the trigger element"}}},"export":{"filename":"Ecommerce-checklist","title":"E-COMMERCE ACCESSIBILITY CHECKLIST","subtitle":"EAA Annex I Section IX, E-Commerce Services"},"links":{"eaaDirective":"EAA Directive 2019/882","en301549":"EN 301 549 V3.2.1"},"platformGuides":{"heading":"Platform Fix Guides","subheading":"Step-by-step instructions for fixing common issues on your platform."}},"emergency-checklist":{"meta":{"title":"Emergency Services Accessibility Checklist, EN 301 549 Chapter 13","description":"EN 301 549 Chapter 13 compliance checklist, verify that your emergency communication systems meet European Accessibility Act requirements."},"header":{"title":"Emergency Services Accessibility Checklist","subtitle":"EN 301 549 Chapter 13 Compliance Checklist"},"description":"EN 301 549 Chapter 13 compliance checklist, verify that your emergency communication systems meet European Accessibility Act requirements.","headerLinks":{"eaaDirective":"EAA Directive 2019/882","en301549":"EN 301 549 V3.2.1"},"features":["EN 301 549 Chapter 13 full coverage","12 checkpoints across emergency access, location & multi-modal communication","Pass / Partial / Fail / N/A with notes per item","How-to-test guidance and common failures for every checkpoint","Links to relevant testing tools on AccessibilityRef","Progress auto-saved in your browser","Export Word report with notes","Direct links to EAA Directive and EN 301 549"],"categories":{"access":{"label":"Emergency Access Methods","description":"EN 301 549 §13.2-§13.3, Emergency services must be reachable through multiple communication methods. Note: §13.1 covers general relay services (not emergency-specific); §13.2 covers emergency service access including RTT and location; §13.3 covers total conversation for emergency calls."},"location":{"label":"Location & Identification","description":"Caller location and identification must be transmitted accessibly."},"multi":{"label":"Multi-Modal Communication","description":"Emergency communication must not depend on a single sensory channel."}},"items":{"ea1":{"text":"Emergency calling supports voice communication to emergency services.","guidance":"The primary voice path to 112/911 must function reliably. This is the baseline requirement.","testMethod":"Place a test call to the non-emergency test number for your local PSAP (Public Safety Answering Point) or use a lab environment that simulates 112/911 routing. Verify that a voice connection is established, audio is clear in both directions, and the call is routed to the correct emergency centre. If no test facility exists, review the technical documentation and carrier certifications for voice emergency call support.","commonFailures":["VoIP application does not route 112/911 calls to the local PSAP, the call fails or reaches a generic operator","Voice quality degrades under low bandwidth to the point where emergency operators cannot understand the caller","Emergency call feature is present but disabled by default and requires user activation in settings","Application handles emergency numbers for one country but not for the jurisdictions where it is distributed"]},"ea2":{"text":"Emergency calling supports real-time text (RTT) alongside voice.","guidance":"Deaf and hard-of-hearing users must be able to contact emergency services via RTT. The RTT path must reach the same emergency centre as voice.","testMethod":"Using the application or device, initiate an emergency call and attempt to send real-time text. Verify that: (1) the RTT option is available during emergency calls, (2) text appears character-by-character at the PSAP (not as whole messages like SMS), (3) RTT and voice can be used simultaneously on the same call, (4) the RTT path reaches the same emergency centre as the voice path. Test with a PSAP test environment if available.","commonFailures":["RTT is supported for regular calls but is explicitly disabled during emergency calls","Text is sent as SMS messages rather than real-time text, characters do not appear as typed","RTT works on the device but the carrier network strips RTT data before it reaches the PSAP","RTT and voice cannot be used simultaneously, enabling RTT drops the voice channel"]},"ea3":{"text":"Emergency calling supports total conversation (voice + video + RTT simultaneously).","guidance":"Total conversation allows sign language users to communicate via video while also having voice and RTT available. This is the most inclusive emergency communication mode.","testMethod":"Initiate an emergency call and verify all three channels are available simultaneously: (1) voice audio, (2) real-time text, (3) video. Check that switching between modalities mid-call does not disconnect any channel. Verify video quality is sufficient for sign language recognition (minimum 20 fps, adequate resolution for hand and facial expression visibility). Review conformance documentation if live testing is not possible.","commonFailures":["Video is available but limited to 5 fps, too slow for sign language to be understood","Only two of the three channels (voice, RTT, video) can be active at once","Total conversation is supported on the device but the PSAP cannot receive video calls","Activating video during an emergency call causes RTT to disconnect"]},"ea4":{"text":"Emergency text communication is available via SMS where RTT is not yet supported.","guidance":"As an interim measure, SMS to emergency services should be supported in jurisdictions where RTT infrastructure is not yet deployed.","testMethod":"In jurisdictions where RTT-to-PSAP infrastructure is not deployed, verify that SMS-to-112 (or the local equivalent) is supported. Send a test SMS to the non-emergency test number and confirm it is received and displayed at the PSAP. Verify the user is informed whether their SMS was delivered. Check that the SMS path is documented in user-facing materials.","commonFailures":["SMS to emergency numbers silently fails, the user receives no delivery confirmation or error","SMS is supported but the user must pre-register for the service, and registration is not documented","SMS emergency service exists but the application blocks SMS to emergency numbers for safety reasons","Fallback SMS path is not mentioned anywhere in the product documentation or emergency instructions"]},"lo1":{"text":"Caller location information is automatically transmitted with emergency calls.","guidance":"E-112 and AML (Advanced Mobile Location) must be supported. Location data helps emergency services reach users who cannot verbally describe their location.","testMethod":"Initiate a test emergency call and verify with the PSAP test environment that location data is received. Check for: (1) network-based location (cell tower triangulation), (2) device-based location (GPS/GNSS coordinates via AML), (3) location accuracy within 50 metres in urban areas. If testing with a live PSAP is not possible, review AML compliance certificates and carrier documentation confirming location transmission.","commonFailures":["VoIP application does not transmit any location data, the PSAP receives the call with no location","Location is transmitted but uses an outdated method (cell ID only) with kilometre-level accuracy","AML is supported by the device OS but the application overrides or blocks location sharing during calls","Location data is transmitted on initial call setup but is not updated if the caller moves during the call"]},"lo2":{"text":"Caller identification is transmitted in text form to emergency services.","guidance":"The caller's number and identity must be available as text data, not just audio announcement, so emergency operators can call back via RTT or text if needed. This falls under the general emergency communication requirements of Chapter 13.","testMethod":"Initiate a test emergency call and verify with the PSAP that caller identification arrives as structured text data (calling number, subscriber name if available). Confirm the PSAP can use this data to call back the caller using a different modality (e.g. RTT callback if the original call was voice). Check that caller ID is not suppressed or anonymised during emergency calls even if the user has caller ID blocking enabled for regular calls.","commonFailures":["Caller ID is suppressed for emergency calls because the user has global caller ID blocking enabled","The calling number is transmitted but subscriber name data is not included","VoIP application transmits an internal user ID instead of a callable phone number","Caller identification is only available as an audio announcement, no text data is sent to the PSAP operator's screen"]},"mm1":{"text":"Emergency communication is not dependent on a single sensory modality.","guidance":"Users must be able to reach emergency services whether they can hear, speak, or see. Voice-only emergency services exclude deaf users; text-only excludes users with motor impairments.","testMethod":"Audit the emergency communication system by attempting to complete an emergency contact using each modality independently: (1) voice only (no text or video), (2) text only (no voice or video), (3) video only (for sign language). If the emergency service can only be reached via one modality, this fails. Document which modalities are supported and which user groups each serves.","commonFailures":["Emergency service is voice-only, deaf users, non-verbal users, and users in situations where speaking is dangerous have no way to communicate","Text option exists but requires the user to navigate a complex menu tree that is not screen-reader accessible","Multiple modalities exist on paper but only voice is reliably connected to the PSAP in practice","Emergency button in the app triggers a voice call with no option to switch to text or video"]},"mm2":{"text":"Video relay to emergency services is available for sign language users.","guidance":"Where total conversation infrastructure exists, sign language users should be able to connect to a video relay interpreter who communicates with the emergency operator.","testMethod":"Verify that a video relay service (VRS) option is available for emergency calls. Test by initiating a video relay call: (1) confirm a sign language interpreter connects, (2) verify the interpreter can relay to the PSAP, (3) check response time, the interpreter connection should happen within 60 seconds for emergency calls. If no VRS exists in the jurisdiction, check whether the product documents alternative sign language emergency access.","commonFailures":["Video relay exists for regular calls but emergency calls are excluded from the VRS routing","VRS is available but operates limited hours (e.g. 9-5), emergencies outside those hours have no sign language option","Interpreter wait times exceed 3 minutes, which is unacceptable for emergency situations","The VRS connection drops frequently due to insufficient video bandwidth requirements for the service"]},"mm3":{"text":"Emergency app or device interface is accessible (keyboard-operable, screen reader compatible).","guidance":"If you provide an emergency calling app or device, its interface must be accessible, large buttons, clear labels, screen reader support, and simple navigation under stress.","testMethod":"Test the emergency interface with: (1) keyboard only, tab to the emergency button and activate with Enter/Space, verify all controls are reachable without a mouse, (2) screen reader, enable NVDA or VoiceOver and navigate to the emergency function, verify all buttons are labelled and the emergency action is clearly announced, (3) switch access, verify the emergency action can be triggered with a single switch. Time how many steps it takes to initiate an emergency call from the app's main screen, it should be no more than 2 actions.","commonFailures":["Emergency button is only activatable via touch, keyboard and switch users cannot reach it","Screen reader announces the emergency button as 'button' with no label text","Emergency function is buried 4 screens deep in a settings menu instead of being immediately accessible","Focus is not automatically placed on the emergency dialog when it appears, screen reader users don't know it has opened"]},"mm4":{"text":"A fallback communication channel exists if RTT or total conversation is unavailable.","guidance":"Network outages or unsupported infrastructure should not leave users without any way to contact emergency services. SMS fallback must be available where RTT is not yet deployed.","testMethod":"Simulate an RTT/total conversation failure (disable the RTT feature or test on a network that does not support RTT). Verify that: (1) the application detects the failure, (2) the user is notified that RTT is unavailable, (3) an alternative is offered (SMS, voice, or location-sharing SOS), (4) the fallback connects to emergency services successfully. Document the fallback chain and verify each step works.","commonFailures":["When RTT fails, the application shows an error message but offers no alternative communication method","Fallback exists but the user is not informed that RTT failed, they believe they are sending RTT when it is not being received","SMS fallback is offered but the SMS-to-112 service is not available in the user's jurisdiction","Voice fallback is offered but this does not help deaf users who cannot use voice"]},"mm5":{"text":"Emergency UI elements meet high contrast requirements (4.5:1 minimum).","guidance":"Emergency buttons, alert text, and status messages must have maximum contrast. Users in distress may have reduced visual acuity. Err on the side of higher contrast.","testMethod":"Identify all UI elements in the emergency interface: the SOS/emergency button, status text, confirmation dialogs, and error messages. For each element, extract the foreground colour and background colour. Use a contrast ratio calculator to verify each pair meets at least 4.5:1 for normal text and 3:1 for large text. For emergency-critical buttons, aim for 7:1 or higher. Test in both light and dark modes if the app supports them.","commonFailures":["Emergency button uses white text on a medium-red background (#E53E3E), ratio of 3.2:1, below the 4.5:1 threshold","Status text ('Connecting to emergency services...') uses light grey on white, almost invisible under stress","Dark mode inverts colours but the emergency button's contrast drops below 3:1 in dark mode","Error messages during a failed emergency call use low-contrast orange text that is hard to read quickly"]},"mm6":{"text":"Emergency SOS buttons meet minimum 44x44px touch target size.","guidance":"Emergency activation buttons must be large and easy to tap under stress. WCAG AAA recommends 44x44 CSS pixels, for emergency UI, treat this as a minimum, not a target.","testMethod":"Inspect the emergency button's rendered size using browser developer tools or by measuring on the physical device. Verify: (1) the touch target is at least 44x44 CSS pixels, (2) there is at least 8px spacing between the emergency button and any adjacent interactive elements, (3) the button is large enough to be activated by users with tremors or limited fine motor control. Test on multiple screen sizes, the button must maintain minimum size on the smallest supported device.","commonFailures":["Emergency button is 32x32px on mobile, too small for users with motor impairments to reliably tap under stress","Button appears large enough but the actual tappable area (hit region) is smaller than the visual button due to padding issues","On small screens (320px width), the emergency button shrinks below 44px due to responsive scaling","Emergency button is adjacent to a 'Cancel' button with only 2px gap, users may accidentally cancel an emergency call"]}},"export":{"filename":"Emergency-checklist","title":"EMERGENCY SERVICES ACCESSIBILITY","subtitle":"EN 301 549 Chapter 13 Compliance Checklist"}},"fine-calculator-pro":{"meta":{"toolId":"Fine-calculator-pro","title":"EAA Fine Calculator Pro"},"title":"EAA Risk Comparison Pro","description":"All 27 EU member states — sort, filter, and export your full liability exposure.","proGateFeatures":["All 27 EU countries side-by-side","Sort by penalty, risk, or country","Revenue-based vs fixed-cap filter","CSV export risk report"],"howItWorks":{"heading":"How this calculator works","steps":["Enter your organisation’s <strong>annual global turnover</strong> and <strong>employee headcount</strong> below.","The calculator applies each country’s national transposition of the European Accessibility Act (Directive 2019/882/EU) to your turnover figure. Where a country uses a <strong>revenue-based formula</strong>, the penalty is a percentage of your turnover. Where a country uses a <strong>fixed cap</strong>, the national maximum is shown directly.","The figures shown are <strong>maximum penalties per violation</strong>. Regulators have discretion to set lower amounts based on the aggravating and mitigating factors listed below.","Your <strong>organisation size</strong> is automatically classified (Microenterprise / Small / Medium / Large) and a proportionality note is shown. Microenterprises providing services are exempt under EAA Article 4(4).","Use the <strong>CSV export</strong> to include this risk data in board reports or legal submissions."],"legalBasis":"EAA Article 30 requires penalties to be “effective, proportionate and dissuasive.” Each EU member state sets its own amounts via national transposition legislation. Penalty data is based on enacted national laws as of March 2026 — some member states have not yet fully published penalty schedules."},"inputs":{"turnover":"Global Annual Turnover","employees":"Employee Headcount"},"sizeCategories":{"micro":{"label":"Microenterprise","warning":"Microenterprise — You may be exempt from the EAA (services)","detail":"Under EAA Article 4(4), microenterprises providing services are exempt from the requirements of the Directive. A microenterprise is defined as fewer than 10 employees and annual turnover ≤ €2 million (EU Recommendation 2003/361/EC). This exemption does not apply to product manufacturers."},"small":{"label":"Small Enterprise","info":"Small Enterprise — EAA applies, proportionality relief available","detail":"You are not exempt, but EAA Article 14 allows you to claim disproportionate burden if compliance costs are unreasonably high relative to your financial capacity."},"medium":{"label":"Medium Enterprise","info":"Medium Enterprise — EAA fully applies","detail":"The EAA applies in full. Disproportionate burden claims (Article 14) are available but face a higher bar than for small enterprises."},"large":{"label":"Large Enterprise","warning":"Large Enterprise — Full EAA obligations, maximum penalty exposure","detail":"Large enterprises have no exemptions and are expected to have the resources to comply fully."}},"factors":{"heading":"Factors that affect your actual fine","subtitle":"Aggravating and mitigating circumstances — EAA Article 30","aggravating":{"heading":"Aggravating factors — increase the fine","items":["Severity of the violation","Duration","Number of users affected","Financial gain from non-compliance","Previous infringements","Intentional or negligent conduct"]},"mitigating":{"heading":"Mitigating factors — reduce the fine","items":["Cooperation with the authority","Swift remediation","Financial capacity / company size","Good-faith compliance efforts","Disproportionate burden","No prior infringements"]}},"stats":{"countries":"Countries","criticalRisk":"Critical Risk","revenueBased":"Revenue-Based","totalExposure":"Total Exposure (numeric)"},"table":{"country":"Country","maxPenalty":"Max Penalty","risk":"Risk","formula":"Formula","type":"Type","detail":"Detail","show":"Show","hide":"Hide","revenuePercent":"% Revenue","fixed":"Fixed"},"riskLevels":{"low":"Low","medium":"Medium","high":"High","critical":"Critical"},"filters":{"filterByCountry":"Filter by country…","revenueBasedOnly":"Revenue-based only","exportCsv":"Export CSV"},"detailPanel":{"penaltyDetail":"Penalty Detail","authority":"Authority","law":"National Law","curePeriod":"Cure Period"},"trialRestriction":"Pro only — Upgrade to export"},"fine-calculator":{"meta":{"title":"EAA Fine Calculator","description":"Estimate your maximum penalty under the European Accessibility Act for any single EU member state."},"header":{"title":"EAA Fine Calculator","subtitle":"Estimate your maximum liability under the European Accessibility Act for any EU member state."},"inputs":{"annualTurnover":"Annual Turnover","manualTurnoverLabel":"Manual turnover input","turnoverSliderLabel":"Annual turnover slider","country":"Country","countryA":"Country A","countryB":"Country B","selectCountry":"Select country,"},"controls":{"compareTwoCountries":"Compare two countries","comparingTwoCountries":"Comparing two countries","multiCountryMode":"Multi-country mode","multiCountrySelected":"Multi-country ({count} selected)","shareResult":"Share result","linkCopied":"Link copied!","resetDefaults":"Reset defaults","resetConfirm":"Reset to defaults?","yesReset":"Yes, reset","cancel":"Cancel"},"result":{"risk":"{level} Risk","estimatedMaxPenalty":"Estimated Maximum Penalty","formula":"Formula","enforcementAuthority":"Enforcement Authority","nationalLaw":"National Law","curePeriod":"Cure Period","formulaDetail":"Formula Detail","revenueBasedPenalty":"Revenue-based penalty","revenueBasedDetail":"Fine scales with your turnover, growing businesses face increasing exposure.","noStatutoryCap":"No statutory cap, unlimited exposure","noStatutoryCapDetail":"This country's penalty regime has no fixed maximum. For large enterprises the fine is a direct percentage of global annual turnover with no upper limit. Use the €100M and €250M presets above to model realistic large-enterprise exposure."},"riskLevels":{"critical":"Critical","high":"High","medium":"Medium","low":"Low","unknown":"Unknown"},"multiCountry":{"title":"Multi-Country Exposure","subtitle":"Select all EU member states where your product or service operates.","selectAll":"Select all","clear":"Clear","tableCountry":"Country","tableMaxFine":"Max Fine","tableFormula":"Formula","tableAuthority":"Authority","combinedExposure":"Combined Maximum Exposure ({count} countries)","uncapped":"+ uncapped","uncappedWarning":"One or more selected countries have uncapped revenue-based penalties. Total exposure is higher than shown.","sumDisclaimer":"Sum of maximum penalties per jurisdiction. Assumes simultaneous enforcement across all selected countries at your turnover level. Each country enforces independently, fines are not mutually offsetting.","noCountriesSelected":"Select countries above to see your multi-jurisdiction exposure."},"topThree":{"title":"Highest Penalty Countries at Your Turnover"},"exemption":{"title":"EAA Exemption Checker","introMicroenterprise":"Microenterprise","introDisproportionateBurden":"Disproportionate Burden","introFundamentalAlteration":"Fundamental Alteration","introBody":"The EAA provides three exemption routes: <micro>Microenterprise</micro> (Article 14, services only), <burden>Disproportionate Burden</burden> (Article 14, documented cost assessment), and <alter>Fundamental Alteration</alter> (Article 14, product nature would change). Fill in the fields below to estimate your position.","intro":"The EAA provides three exemption routes: Microenterprise (Article 14, services only), Disproportionate Burden (Article 14, documented cost assessment), and Fundamental Alteration (Article 14, product nature would change). Fill in the fields below to estimate your position.","employees":"Number of Employees","employeesFte":"Full-time equivalents (FTE)","complianceCost":"Estimated Compliance Cost (€)","complianceCostHint":"One-time cost to achieve compliance","orgType":"Organisation Type","servicesGroup":"Services","productsGroup":"Products","cannotClaimMicroenterprise":"This org type cannot claim the EAA microenterprise exemption.","microenterprise":"Microenterprise Exemption","likelyExempt":"Likely Exempt","doesNotApply":"Does Not Apply","microRationaleExempt":"Under 10 employees and under €2M turnover, service providers qualify for full exemption (Article 14).","microRationaleOrgIneligible":"{orgLabel} does not qualify for the microenterprise exemption.","microRationaleTooManyEmployees":"You have {count} employees, exemption requires fewer than 10 FTE.","microRationaleTooMuchTurnover":"Turnover €{turnover} exceeds the €2M threshold.","directiveLink":"EAA Article 14, Directive text","disproportionateBurden":"Disproportionate Burden","enterCost":"Enter cost →","potentiallyApplicable":"Potentially applicable","unlikely":"Unlikely","ofTurnover":"Of annual turnover","burdenEnterCostPrompt":"Enter estimated compliance cost to check disproportionate burden.","burdenUnlikely":"At {ratio}% of turnover, compliance cost is unlikely to qualify as disproportionate. Courts and regulators typically expect full compliance.","burdenBorderline":"At {ratio}% of turnover, borderline case. Document costs carefully and seek legal advice, some regulators may accept a phased compliance plan.","burdenSupportable":"At {ratio}% of turnover, a formal disproportionate burden assessment (Article 14) may be supportable. You must document costs, consult your national authority, and provide partial accessibility where possible.","fundamentalAlteration":"Fundamental Alteration","caseByCase":"Case-by-case","fundamentalAlterationDetail":"Applies when meeting accessibility requirements would fundamentally alter the nature of your product or service (Article 14(5)). This is assessed by national market surveillance authorities on a case-by-case basis, it cannot be automatically calculated.","exemptionWarningLabel":"Important:","exemptionWarning":"Exemption assessments must be formally documented and submitted to your national market surveillance authority on request. Claiming an exemption does not remove your obligation to make partial accessibility improvements where feasible. Always consult a qualified legal professional before relying on any exemption."},"orgTypes":{"service":{"label":"General service provider (website, app, SaaS)","annex":"EAA Annex I","scope":"Covers consumer-facing digital services, websites, apps, online tools."},"ecommerce":{"label":"E-commerce (webshop, marketplace)","annex":"EAA Annex I §X","scope":"Section X covers e-commerce services including product pages, checkout, customer accounts."},"banking":{"label":"Banking & financial services","annex":"EAA Annex I §IV","scope":"Section IV covers consumer banking: web/app banking, ATMs, payment terminals, customer support."},"insurance":{"label":"Insurance services","annex":"EAA Annex I §IV","scope":"Financial services including insurance, customer portals, claims forms, information documents."},"transport":{"label":"Transport operator (airline, rail, bus, ferry)","annex":"EAA Annex I §II–III","scope":"Sections II–III: ticketing, real-time travel info, self-service terminals, booking websites and apps."},"telecoms":{"label":"Electronic communications (telecoms, internet provider)","labelOption":"Electronic communications (telecoms, ISP)","annex":"EAA Annex I §I","scope":"Section I: consumer-facing telecoms services, broadband, mobile, customer portals, number-based interpersonal comms."},"media":{"label":"Media services (TV, streaming, e-books, audiovisual)","labelOption":"Media services (TV, streaming, e-books)","annex":"EAA Annex I §IX","scope":"Section IX: audiovisual media services, e-readers, e-book distribution."},"public":{"label":"Public sector / government body","annex":"Web Accessibility Directive (EU) 2016/2102","scope":"Public sector bodies are covered by the Web Accessibility Directive, not the EAA. EAA applies when public bodies provide services also offered commercially."},"product":{"label":"Product manufacturer (hardware, terminals, ATMs)","annex":"EAA Annex I §I–VIII (products)","scope":"Products in scope: computers, smartphones, ATMs, ticketing machines, e-readers, TVs with interactive features."},"both":{"label":"Both products and services","annex":"Multiple EAA Annexes","scope":"Both product requirements (Annexes I–VIII) and service requirements apply."}},"proUpsell":{"title":"Unlock All 27 Countries Simultaneously","subtitle":"Pro: side-by-side comparison across all EU states, multi-violation modelling, and PDF board report.","viewPro":"View Pro Calculator","unlockProLabel":"Unlock Pro, €999/yr"},"legal":{"title":"Legal Foundation","body":"The EAA (Directive 2019/882/EU) requires penalties to be <strong>effective, proportionate, and dissuasive</strong> (Article 30). Member states transposed this with varying structures, from fixed caps of €15,000 to uncapped percentage-of-turnover penalties. Figures shown are maximum exposure; actual penalties depend on severity, duration, and national regulator discretion.","directiveLinkLabel":"Directive 2019/882 Full Text"},"evidence":{"toolName":"EAA Fine Calculator","summaryWithResult":"{country}: {fine} max penalty at €{turnover} turnover","summaryNoResults":"No results","labels":{"primaryCountry":"Primary country","annualTurnover":"Annual turnover (€)","organisationType":"Organisation type","employees":"Employees","complianceCost":"Estimated compliance cost (€)","comparisonCountry":"Comparison country","multiCountryMode":"Multi-country mode","multiCountriesSelected":"{count} countries selected","country":"Country","maxFine":"Max fine","riskLevel":"Risk level","fineFormula":"Fine formula","enforcementAuthority":"Enforcement authority","nationalLaw":"National law","curePeriod":"Cure period","microenterpriseExemption":"Microenterprise exemption","microenterpriseExemptYes":"Yes, exempt (Article 14)","microenterpriseExemptNo":"No","burdenRatio":"Disproportionate burden ratio","burdenRatioPercent":"{ratio}% of turnover","burdenRatioNotEntered":"N/A (no compliance cost entered)","notApplicable":"N/A","method":"Method","methodBody":"Maximum penalty exposure is computed against the EAA Article 30 transposition for each EU member state at the user-supplied annual turnover. Revenue-based penalties scale with turnover; fixed-cap penalties are reproduced verbatim from national law. Microenterprise exemption (Article 14) and indicative disproportionate burden ratio (Article 14 / Annex VI) are calculated from organisation type, headcount and turnover.","inputs":"Inputs","sectorAnnex":"Sector annex","primaryJurisdiction":"Primary jurisdiction, {country}","comparisonJurisdiction":"Comparison jurisdiction, {country}","formula":"Formula","formulaDetail":"Formula detail","revenueBased":"Revenue-based","uncappedExposure":"Uncapped exposure","uncappedYes":"Yes, no statutory cap","yes":"Yes","no":"No","multiJurisdictionExposure":"Multi-jurisdiction exposure ({count} countries)","tableCountry":"Country","tableMaxFine":"Max fine","tableFormula":"Formula","tableAuthority":"Authority","tableCurePeriod":"Cure period","combinedMaxExposure":"Combined maximum exposure","combinedMaxExposureUncapped":"{value} + uncapped","includesUncapped":"Includes uncapped jurisdictions","exemptionAssessment":"Exemption assessment (Article 14)","burdenRatioRow":"Compliance cost / turnover ratio","burdenIndicator":"Disproportionate burden indicator","downloadJsonLabel":"Download JSON","downloadJsonHint":"Inputs + results + notes"},"eaaRefs":{"article30":"Article 30 (penalties)"}}},"focus-order-pro":{"meta":{"toolId":"Focus-order-pro","title":"Focus Order Visualiser Pro"},"badge":"Pro","title":"Batch Focus Order Analyser","description":"Analyse focus order across up to 10 URLs simultaneously.","proGateFeatures":["Batch-analyse keyboard focus order across up to 10 URLs at once","Full tab stop list with accessible names per element","Flags missing labels, positive tabindex abuse, and non-semantic interactive elements","Export complete focus order audit as CSV for development handoff"],"focusVisualiser":{"heading":"Focus Visualiser","intro":"Many sites strip the default focus ring with <code>outline: none</code>. On those sites a keyboard walk is impossible, you can't see where you are, and the screen reader announcement is meaningless without a visible anchor. This snippet forces a bright magenta ring on every focused element, regardless of site CSS.","howToUse":"<s>How to use:</s> Open the target page → open DevTools (F12) → go to <s>Console</s> → paste the snippet and press Enter. Run it a second time to remove. Then Tab through the page, every focus stop will be visible.","copyButton":"Copy Focus Visualiser snippet","copiedButton":"✓ Copied, paste into DevTools Console","viewSnippet":"View snippet","fallbackPrompt":"Copy this into DevTools console:"},"infoPanel":{"toggle":"What this tool checks, and why keyboard focus order is a legal requirement","whatItDoes":{"heading":"What this tool does","description":"Paste up to 10 URLs and the tool fetches each page, extracts every focusable element (links, buttons, inputs, custom elements with tabindex), and lists them in the order they receive keyboard focus.","paragraph1":"Paste up to 10 URLs and the tool fetches each page, extracts every focusable element (links, buttons, inputs, custom elements with tabindex), and lists them in the order they receive keyboard focus. For each element it shows: the element tag, its accessible name (text or aria-label), its tabindex value, and any issues detected, such as a missing accessible name, a positive tabindex that overrides the natural tab order, or a non-semantic element being made focusable without a proper role.","paragraph2":"Results are exportable as CSV for developer handoff or inclusion in a WCAG audit report."},"legalRequirement":{"heading":"Why keyboard accessibility is legally required","intro":"An estimated <s>7–10% of users</s> navigate websites using keyboard only, including people with motor disabilities, power users, and screen reader users (who navigate by keyboard exclusively). Broken focus order or inaccessible elements can make entire flows, login, checkout, forms, completely unusable.","sc211Label":"WCAG 2.2 SC 2.1.1","sc211Body":"<s>Keyboard, Level A.</s> All functionality must be operable by keyboard alone. If any action can only be performed with a mouse, it is a Level A failure. This is a hard requirement under every major legal framework.","sc243Label":"WCAG 2.2 SC 2.4.3","sc243Body":"<s>Focus Order, Level A.</s> If a page can be navigated sequentially (as with Tab), the focus order must preserve meaning and operability. A page where Tab jumps randomly between unrelated elements, or skips interactive controls, fails this criterion.","sc247Label":"WCAG 2.2 SC 2.4.7","sc247Body":"<s>Focus Visible, Level AA.</s> The keyboard focus indicator must be visible. An element in the tab order with no visible focus ring is a Level AA failure. This tool identifies elements in the tab order; use browser DevTools or the free Focus Order Visualiser tool to check focus indicator visibility.","eaaLabel":"EAA 2025","eaaBody":"<s>European Accessibility Act (Directive 2019/882)</s>, applies from <s>28 June 2025</s>. Requires WCAG 2.1 AA via EN 301 549 (clauses 9.2.1.1, 9.2.4.3, 9.2.4.7). Keyboard failures are a primary finding in enforcement investigations, they completely exclude a measurable user group.","en301549Label":"EN 301 549","en301549Body":"Clauses 9.2.1.1 and 9.2.4.3 directly map to WCAG SC 2.1.1 and SC 2.4.3. Compliance creates a legal presumption of conformity under the EAA.","psbarLabel":"UK PSBAR","psbarBody":"<s>Public Sector Bodies Accessibility Regulations 2018.</s> Keyboard accessibility is a mandatory requirement. CDDO monitoring explicitly tests keyboard-only navigation of critical user journeys.","adaLabel":"ADA / Section 508","adaBody":"Keyboard traps and inaccessible controls are among the most commonly cited failures in ADA demand letters. Section 508 requires equivalent keyboard access to all functionality for US federal agencies and contractors."},"commonIssues":{"heading":"Common focus order issues, what to look for","items":["Positive tabindex (tabindex=\"1\", \"2\" etc.), this overrides the natural DOM order.","Missing accessible name, an icon button or image link with no text or aria-label.","Non-semantic elements, a <div> or <span> with tabindex=\"0\" but no role.","Unexpected focus traps, modal dialogs should trap focus while open."],"positiveTabindexRich":"<s>Positive tabindex</s> (tabindex=\"1\", \"2\" etc.), this overrides the natural DOM order and almost always creates a broken, confusing focus sequence. Use tabindex=\"0\" or -1 only.","missingNameRich":"<s>Missing accessible name</s>, an icon button or image link with no text or aria-label is invisible to screen readers. The element appears in the tab order but the user cannot determine what it does.","nonSemanticRich":"<s>Non-semantic elements</s>, a <code>{div}</code> or <code>{span}</code> with tabindex=\"0\" but no role is operable by keyboard but not announced correctly by assistive technology.","focusTrapRich":"<s>Unexpected focus traps</s>, modal dialogs should trap focus while open. Any other element trapping focus is a keyboard blocker (SC 2.1.2 failure)."},"howToUse":{"heading":"How to use this tool","steps":["Paste the URLs you want to audit, especially pages with forms, modals, menus, and interactive widgets.","Review the summary table for pages with elements flagged as having issues.","Open the accordion for each URL to see the numbered tab stop list.","Export as CSV and share with your development team, or attach to a WCAG audit report as evidence."],"step1":"Paste the URLs you want to audit, especially pages with forms, modals, menus, and interactive widgets.","step2":"Review the summary table for pages with elements flagged as having issues.","step3":"Open the accordion for each URL to see the numbered tab stop list. Any element flagged in red needs investigation.","step4":"Export as CSV and share with your development team, or attach to a WCAG audit report as evidence."}},"ariaPatterns":{"heading":"ARIA Keyboard Interaction Patterns","subtitle":"Required keyboard behaviours per widget type. Source: ARIA Authoring Practices Guide (APG).","columns":{"widget":"Widget","keysRequired":"Keys Required","tabStops":"Tab Stops"},"rows":{"modal":{"widget":"Modal Dialog","keys":"Tab / Shift+Tab (trapped), Esc to close","stops":"1 (container)"},"menu":{"widget":"Menu / Dropdown","keys":"Enter/Space to open, Arrow keys to navigate items, Esc to close","stops":"1 (trigger)"},"tabs":{"widget":"Tabs","keys":"Tab to tab list, Arrow keys to switch tabs, Enter/Space to activate","stops":"1 (active tab)"},"accordion":{"widget":"Accordion","keys":"Tab to each header, Enter/Space to expand/collapse","stops":"1 per header"},"combobox":{"widget":"Combobox / Select","keys":"Enter/Space to open, Arrow keys to navigate, Enter to select, Esc to close","stops":"1 (input)"},"datepicker":{"widget":"Date Picker","keys":"Arrow keys to navigate days, PgUp/PgDn for month, Home/End for row","stops":"1 (input)"},"slider":{"widget":"Slider","keys":"Arrow keys to move value, Home/End for min/max","stops":"1 per thumb"},"tree":{"widget":"Tree View","keys":"Arrow keys to navigate, Right to expand, Left to collapse, Enter to select","stops":"1 (tree root)"},"carousel":{"widget":"Carousel","keys":"Previous/Next buttons keyboard operable, auto-play must pause on focus","stops":"Buttons + slides"},"datagrid":{"widget":"Data Grid","keys":"Arrow keys between cells, Tab to next widget, Enter to edit","stops":"1 (grid)"}}},"manualChecklist":{"heading":"Manual Keyboard Testing Checklist","subtitle":"This tool catches structural issues, use this checklist to complete your manual audit.","intro":"No screen reader needed. Use only Tab, Shift+Tab, Arrow keys, Enter, Space, and Escape.","categories":{"tabOrder":"Tab Order","focusVisibility":"Focus Visibility","interactiveControls":"Interactive Controls","keyboardTraps":"Keyboard Traps","tabindexIssues":"Tabindex Issues"},"items":{"tabOrder":["Tab through the entire page, does focus move in a logical left-to-right, top-to-bottom order?","Does focus skip any interactive element that should be reachable?","Does focus land on any element that is not interactive (decorative, hidden)?"],"focusVisibility":["Is there a visible focus ring on every focusable element?","Is the focus ring high enough contrast to be visible on the page background? (SC 1.4.11: 3:1 minimum)","Does focus remain visible after moving, i.e. The previous element loses its ring cleanly?"],"interactiveControls":["Can every button and link be activated with Enter or Space?","Do dropdowns, modals, and accordions follow ARIA APG keyboard patterns? (see table left)","Can you close any open overlay with Escape?"],"keyboardTraps":["Are you ever unable to Tab away from a component (except intentional modal dialogs)?","Do modal dialogs trap focus correctly, Tab loops within the dialog only?","Does focus return to the trigger element when a dialog or menu closes?"],"tabindexIssues":["Open DevTools: search for tabindex values > 0, these break natural tab order.","Confirm any tabindex=\"-1\" elements are only focused programmatically (e.g. After modal open)."]}},"input":{"label":"Enter up to 10 URLs (one per line)","placeholder":"Https://example.com\nhttps://example.com/about\nhttps://example.com/contact","urlCount":"{count} / 10 URLs"},"actions":{"analyseAll":"Analyse All","analysing":"Analysing","exportCsv":"Export CSV","expandAll":"Expand all","collapseAll":"Collapse all"},"progress":{"analysingLabel":"Analysing {current}/{total}...","buttonLabel":"{label} {current}/{total}..."},"results":{"summary":"Summary","detailedResults":"Detailed Results","urlsScanned":"URLs Scanned","totalTabStops":"Total Tab Stops","elementsWithIssues":"Elements with Issues","urlsPassing":"URLs Passing","focusableElements":"Focusable elements","withIssuesSuffix":"With issues","noIssuesSuffix":"No issues","errorPrefix":"Error","failedToAnalyse":"Failed to analyse","noFocusableOnPage":"No focusable elements found on this page.","noVisibleText":"(no visible text)","ariaLabelPrefix":"Aria-label:","textPrefix":"Text:"},"table":{"url":"URL","totalElements":"Total Elements","elementsWithIssues":"Elements with Issues","status":"Status"},"status":{"pass":"Pass","error":"Error","issuesFound":"Issues Found"},"filterIssues":{"issuesOnly":"Issues only","allUrls":"All URLs"},"trialRestriction":"Pro only, Upgrade to export","trialRestrictionTitle":"Upgrade to Pro to export documents","outlineWarning":{"title":"Focus indicator suppression detected, WCAG 2.4.7 (Level AA) risk","body":"One or more CSS rules or inline styles remove the default focus outline without providing a replacement (e.g. <code>outline: none</code> with no matching <code>box-shadow</code> or <code>border-color</code> change). Keyboard users cannot see where they are on the page. This is a Level AA failure under SC 2.4.7 Focus Visible.","note":"<s>Note:</s> this check reads inline styles and on-page <code>{styleTag}</code> blocks only. External stylesheets may contain additional suppressions this tool cannot see, a visual keyboard walk-through is still required.","copyButton":"Copy Focus Visualiser, walk the page with a visible ring","copiedButton":"✓ Copied, paste into DevTools","inlineHeading":"Inline <code>style=\"outline: none\"</code>, {count} focusable element{plural}","inlinePluralSuffix":"S","cssHeading":"CSS rules removing outline without replacement, {count}"},"export":{"docx":{"batchSummaryHeading":"Batch Summary","rowUrlsScanned":"URLs scanned","rowUrlsWithIssues":"URLs with focus/keyboard issues","rowUrlsFullyCompliant":"URLs fully compliant","rowUrlsErrored":"URLs that errored","rowTotalFocusable":"Total focusable elements","rowElementsWithIssues":"Elements with issues","rowUrlsOutlineSuppression":"URLs with outline:none suppression detected","perUrlHeading":"Per-URL Result","headerUrl":"URL","headerFocusable":"Focusable","headerIssues":"Issues","headerOutlineNone":"Outline:none","headerStatus":"Status","statusYes":"Yes","statusNo":"No","statusErrorPrefix":"Error","statusClean":"Clean","statusIssues":"Issues","findingsHeading":"Detailed Findings","findingsIntro":"Each URL with issues is listed below. Every flagged element gives the developer everything needed to find it in source: tab index, element type, identifying attributes (id / name / class / placeholder / href), the heuristic UI surface where the control physically lives, parent landmark + form action, a short DOM path, the current accessible name, the specific issue, and a truncated outerHTML snippet.","headerTab":"Tab #","headerElement":"Element","headerIdentifying":"Identifying attributes","headerLocation":"Location on page","headerName":"Accessible name","headerHtml":"HTML snippet","valueNone":"(none)","valueUnknown":"(unknown)","valueNoName":"(no accessible name)","outlineHeading":"Outline-suppression Findings","outlineIntro":"URLs below suppress the browser's default focus ring via outline:none in CSS or inline styles. This is a WCAG 2.4.7 (Focus Visible) failure unless an alternative visible focus indicator is provided. Manual verification with the Focus Visualiser snippet is recommended.","rowInlineSuppressions":"Inline outline:none suppressions","rowCssSuppressions":"CSS rule suppressions","contrastHeading":"Focus Indicator Contrast & Thickness","contrastIntro":"WCAG 2.4.13 (Focus Appearance, Level AA in WCAG 2.2) requires the focus indicator to have at least 3:1 contrast against adjacent colours and to be at least 2 CSS pixels thick (or equivalent). The static probe below extracts every:focus /:focus-visible /:focus-within rule, reads its outline-color, outline-width, box-shadow, and border-color, and computes contrast against white and black backgrounds. A rendered DOM verification (different elements may sit on different backgrounds) is recommended for any rule flagged below.","lowContrastHeading":"Low contrast, {count, plural, one {# rule} other {# rules}}","thinIndicatorHeading":"Indicator below 2px, {count, plural, one {# rule} other {# rules}}","headerSelector":"Selector","headerColor":"Color","headerVsWhite":"Vs white","headerVsBlack":"Vs black","headerWidth":"Width","headerVerdict":"Verdict","verdictPass":"Pass, meets WCAG 2.4.13","verdictLowContrast":"Fail, contrast <3:1","verdictThin":"Fail, indicator <2px","verdictNoColor":"Inconclusive, colour not parsed","urlNoRulesFound":"No:focus /:focus-visible /:focus-within rules detected in the page's stylesheets. The focus indicator relies on the browser default, which may be overridden by other CSS at runtime. Manual verification with the Focus Visualiser snippet is recommended.","rulesTruncatedNote":"Showing the first {shown} of {total} parsed focus rules. The remainder are present in the underlying JSON evidence record.","erroredHeading":"URLs That Could Not Be Scanned","methodHeading":"Method","methodBody":"Each URL was fetched server-side and parsed for focusable elements (a[href], button, input, select, textarea, [tabindex]). Each element was inspected for an accessible name and for problematic patterns (positive tabindex, non-semantic interactive containers, missing labels). Stylesheets and inline styles were scanned for outline:none suppressions of the default focus indicator. Every:focus /:focus-visible /:focus-within rule was probed for outline-color, outline-width, box-shadow, and border-color; the parsed primary colour was scored against white and black backgrounds (WCAG 2.4.13 requires ≥3:1 contrast and ≥2px thickness for the indicator). Mapped to WCAG 2.2 SC 2.4.3 (Focus Order), 2.4.7 (Focus Visible), 2.4.13 (Focus Appearance), 2.1.1 (Keyboard); EN 301 549 V3.2.1 §9.2.4.3, §9.2.4.7, §9.2.1.1."}}},"focus-order":{"meta":{"title":"Focus Order Visualiser","description":"Enter a URL to see all focusable elements in tab order. Flags missing accessible names and positive tabindex."},"header":{"title":"Focus Order Visualiser","subtitle":"Map the keyboard tab sequence, detect positive tabindex, missing names, and non-semantic interactive elements."},"howTo":{"step1Title":"Enter your page URL or paste HTML","step1Body":"Use 'Scan URL' for a live page or 'Paste HTML' for a component. The tool extracts all interactive elements (links, buttons, inputs, elements with tabindex).","step2Title":"Read the focus order list","step2Body":"Elements are listed in the order a keyboard user would Tab through them. Each entry shows the element type, its accessible name, and its tabindex value.","step3Title":"Spot the issues","step3Body":"Flags to look for: positive tabindex values (tabindex='1' or higher forces an unnatural order, use 0 or -1 only), elements with no accessible name (screen reader users won't know what they are), and <div> or <span> used as buttons.","step4Title":"Fix and verify","step4Body":"Remove positive tabindex values and rely on DOM order instead. Add aria-label or visible text to nameless elements. Replace non-semantic interactive elements with proper <button> or <a> tags."},"modes":{"scanUrl":"Scan URL","pasteHtml":"Paste HTML"},"inputs":{"urlPlaceholder":"Https://example.com/page","analyseButton":"Analyse Focus","analysingButton":"Analysing…","htmlPlaceholder":"Paste HTML source, all focusable elements will be extracted and audited…","parseButton":"Parse HTML"},"errors":{"prefix":"Error","noFocusableInHtml":"No focusable elements found in the pasted HTML."},"issues":{"noAccessibleName":"No accessible name, screen readers cannot identify this element","positiveTabindex":"Tabindex=\"{value}\", positive tabindex disrupts natural tab order (SC 2.4.3)","nonSemanticInteractive":"<{tag}> with tabindex, use a native interactive element instead"},"scores":{"focusScore":"Focus Score","tabStops":"Tab Stops","withIssues":"With Issues","overall":"Overall","pass":"Pass","review":"Review"},"scoreExplanation":{"title":"What does the Focus Score mean?","body":"The Focus Score (0–100) shows what percentage of your tab-stops are free of issues.","good":"80–100 = Good (most elements are accessible).","needsWork":"50–79 = Needs work (some issues to fix).","critical":"Below 50 = Critical (keyboard navigation is broken or confusing).","issuesDetected":"Issues detected:","positiveTabindex":"Positive tabindex (breaks natural tab order, SC 2.4.3),","missingName":"Missing accessible name (screen reader cannot identify the element, SC 4.1.2),","nonSemantic":"Non-semantic interactive element (a <div> or <span> used as a button, SC 4.1.2).","scoreRichBody":"The Focus Score (0–100) shows what percentage of your tab-stops are free of issues. <s>80–100</s> = Good (most elements are accessible). <s>50–79</s> = Needs work (some issues to fix). <s>Below 50</s> = Critical (keyboard navigation is broken or confusing).","issuesRichBody":"Issues detected: <s>Positive tabindex</s> (breaks natural tab order, SC 2.4.3), <s>missing accessible name</s> (screen reader cannot identify the element, SC 4.1.2), <s>non-semantic interactive element</s> (a <code>{div}</code> or <code>{span}</code> used as a button, SC 4.1.2)."},"issueSummary":{"positiveTabindex":"Positive tabindex","missingAccessibleName":"Missing accessible name","nonSemanticInteractive":"Non-semantic interactive"},"filters":{"all":"All ({count})","issuesOnly":"Issues only ({count})"},"controls":{"simulateTab":"Simulate Tab","stopTabSim":"Stop Tab Sim","exportCsv":"Export CSV","proOnlyExport":"Pro only, Upgrade to export","proOnlyExportTitle":"Upgrade to Pro to export documents"},"elements":{"text":"Text:","ariaLabel":"Aria-label:","noAccessibleName":"No accessible name","locationLabel":"Where on the page:","showOuterHtml":"Show outerHTML snippet","formActionLabel":"Form action:","popupLabel":"Popup:","pathLabel":"Path:"},"noIssues":"No focus order issues detected","proUpsell":{"title":"Need Batch Focus Analysis?","subtitle":"Pro: analyse up to 10 URLs simultaneously, export full findings as CSV.","buttonLabel":"Unlock Pro, Batch Mode"},"wcagReference":{"title":"Relevant WCAG Criteria","sc243":"SC 2.4.3 Focus Order (A), Focusable components must receive focus in an order that preserves meaning and operability.","sc247":"SC 2.4.7 Focus Visible (AA), Any keyboard-operable UI must have a visible focus indicator.","sc412":"SC 4.1.2 Name, Role, Value (A), All UI components must have an accessible name and role.","officialLinkLabel":"Read SC 2.4.3 Guidance"},"companionCriteria":{"title":"WCAG 2.2 companion criteria, manual verification required","intro":"This tool detects programmatic focus order issues. Two additional WCAG 2.2 Level AA criteria cannot be detected automatically and must be verified by hand:","sc2411":"SC 2.4.11 Focus Not Obscured (Minimum, AA), When a component receives keyboard focus, it must not be entirely hidden by author-created content (e.g. Sticky headers, cookie banners).","sc2413":"SC 2.4.13 Focus Appearance (AA), The focus indicator must have a minimum area (perimeter × 2 CSS px) and a contrast ratio of at least 3:1 between focused and unfocused states."},"bulkScan":{"title":"Bulk Focus Order Audit","subtitle":"Upload a sitemap to check keyboard focus order across your entire site","metaFocusable":"Focusable","metaIssues":"Issues"},"evidence":{"nextStepLabel":"Run Alt Text Checker","nextStepHint":"Check images on the same page","scannedNotePrefix":"Scanned"},"export":{"docx":{"summaryHeading":"Summary","rowScannedUrl":"Scanned URL","rowTotalFocusable":"Total focusable elements","rowElementsWithIssues":"Elements with issues","rowCleanElements":"Clean elements","issuesHeading":"Elements With Issues","issuesIntro":"{count, plural, one {# element} other {# elements}} flagged. Each row gives the developer everything needed to locate the element in source: tab order, element type, identifying attributes (id / name / class / placeholder / href), the heuristic UI surface where the control physically lives (e.g. \"Header Account dropdown, Login form\"), the parent landmark + form action, a short DOM path, the current accessible name, the specific issues detected, and a truncated outerHTML snippet.","noIssuesParagraph":"All focusable elements passed the focus-order checks.","headerTab":"Tab #","headerElement":"Element","headerIdentifying":"Identifying attributes","headerLocation":"Location on page","headerName":"Accessible name","headerIssues":"Issues","headerHtml":"HTML snippet","valueNone":"(none)","valueUnknown":"(unknown)","valueNoName":"(no accessible name)","sequenceHeading":"Full tab sequence","headerTag":"Tag","headerTabindex":"Tabindex","methodHeading":"Method","methodBody":"Focusable elements were extracted in DOM order from the supplied HTML using the standard tabbable selector (a[href], button, input, select, textarea, [tabindex]). Each element was inspected for an accessible name (text content, aria-label, or aria-labelledby) and for problematic patterns such as positive tabindex values, non-semantic interactive containers, and missing labels. Mapped to WCAG 2.2 SC 2.4.3 (Focus Order), 2.4.7 (Focus Visible), and 2.1.1 (Keyboard); EN 301 549 V3.2.1 §9.2.4.3, §9.2.4.7, §9.2.1.1."}}},"functional-criteria-checklist":{"meta":{"title":"Functional Performance Criteria Checklist, EAA Annex I Section VII","description":"EAA Annex I Section VII compliance checklist, verify that your product or service meets the functional performance fallback requirements of the European Accessibility Act across vision, hearing, speech, motor, and cognitive criteria."},"header":{"title":"Functional Performance Criteria Checklist","subtitle":"EAA Annex I Section VII, 24 Outcome-Based Accessibility Criteria"},"description":"EAA Annex I Section VII compliance checklist, verify that your product or service meets the functional performance fallback requirements of the European Accessibility Act across vision, hearing, speech, motor, and cognitive criteria.","headerLinks":{"eaaAnnex":"EAA Annex I Section VII","wcag":"WCAG 2.2","en301549":"EN 301 549 V3.2.1"},"features":["EAA Annex I Section VII full coverage","24 fallback criteria across vision, hearing, speech, motor & cognition","Outcome-based testing with Pass / Partial / Fail / N/A per item","How-to-test guidance and common failures for every checkpoint","Links to relevant testing tools on AccessibilityRef","Progress auto-saved in your browser","Export Word report with notes","Direct links to EAA Directive Annex I articles"],"categories":{"vision":{"label":"Vision-Related Criteria","description":"EAA Annex I Section VII(a)-(c), Products and services must be usable without vision, with limited vision, and without colour perception."},"hearing":{"label":"Hearing-Related Criteria","description":"EAA Annex I Section VII(d)-(e), Products and services must be usable without hearing and with limited hearing."},"speech":{"label":"Speech & Communication Criteria","description":"EAA Annex I Section VII(f), Products and services must be usable without vocal capability."},"motor":{"label":"Motor & Physical Criteria","description":"EAA Annex I Section VII(g)-(h), Products and services must be usable with limited manipulation, strength, or reach."},"cognitive":{"label":"Cognitive & Seizure Criteria","description":"EAA Annex I Section VII(i)-(k), Products and services must minimise seizure risk, support limited cognition, and protect privacy."}},"items":{"v1":{"text":"At least one mode of operation does not require vision.","guidance":"Blind users must be able to complete all essential tasks. This means providing text-to-speech output, screen reader compatibility, or audio-based interaction. If any function is vision-only with no alternative, this criterion fails.","testMethod":"Turn off the display or close your eyes and attempt to complete all core tasks using only a screen reader (NVDA on Windows, VoiceOver on macOS/iOS, TalkBack on Android). Navigate to every key feature, complete a transaction or workflow, and verify that every piece of information is announced. If any essential task cannot be completed without vision, this fails.","commonFailures":["Login flow uses a visual CAPTCHA with no audio or alternative challenge","Critical actions are conveyed through images or icons alone with no alt text or ARIA labels","Drag-and-drop interface is the only way to perform a task with no keyboard/screen reader alternative","Confirmation or error messages appear visually but are not announced by screen readers"]},"v2":{"text":"All visual information has a non-visual alternative (audio, tactile, or text-based).","guidance":"Every piece of information conveyed visually, text, images, charts, icons, status indicators, must have an equivalent non-visual representation. This includes error states, loading indicators, and confirmation messages.","testMethod":"Audit all visual elements in the product: images, icons, charts, graphs, status indicators, colour-coded labels, and video content. For each, verify that a non-visual alternative exists (alt text, ARIA label, audio description, tactile equivalent). Use a screen reader to confirm alternatives are announced correctly. If any visual information has no non-visual equivalent, this fails.","commonFailures":["Charts and graphs display data visually but have no text summary or data table alternative","Status indicators use colour dots (green/red) with no text label or screen reader announcement","Decorative and informative images both lack alt text, or decorative images have meaningless alt text","Loading spinners and progress indicators are visual-only with no screen reader announcement"]},"v3":{"text":"At least one mode of operation is usable with limited vision.","guidance":"Users with low vision must be able to use the product. This means supporting magnification, high contrast, large text, and adjustable display settings. Test with 200% zoom and inverted colours.","testMethod":"Set the browser or OS zoom to 200%. Verify that: (1) all content remains visible without horizontal scrolling, (2) no text is clipped or overlaps other elements, (3) all functionality is still accessible. Then enable the OS high contrast mode and verify all UI elements remain visible and operable. Test with the built-in screen magnifier at 400%. If content breaks at 200% zoom or high contrast mode, this fails.","commonFailures":["Text overlaps or is clipped when the browser is zoomed to 200%","Horizontal scrolling is required at 200% zoom, making content difficult to read","High contrast mode causes text and backgrounds to merge, making content unreadable","Fixed-size containers prevent text from reflowing at larger zoom levels"]},"v4":{"text":"Text can be enlarged without loss of content or functionality.","guidance":"When text is scaled to 200%, no content should be cut off, overlapped, or hidden. This applies to both digital interfaces and hardware displays.","testMethod":"Increase text size to 200% using browser text-only zoom (not page zoom) or the OS large text setting. Navigate through all screens and verify: (1) no text is truncated with ellipsis or hidden overflow, (2) buttons and labels remain readable, (3) form fields still show their labels, and (4) navigation menus remain functional. If any content is lost or functionality breaks, this fails.","commonFailures":["Button labels are truncated with '...' when text is enlarged","Form field labels disappear behind input fields at larger text sizes","Navigation menu items overflow and become inaccessible at 200% text size","Fixed-height containers cause text to overflow and overlap with adjacent elements"]},"v5":{"text":"Contrast and colour settings can be adjusted by the user.","guidance":"Users must be able to change text/background contrast ratios and colour schemes to suit their vision needs. Respect OS-level contrast settings.","testMethod":"Enable the OS high contrast mode (Windows High Contrast, macOS Increase Contrast). Verify the product respects these settings. Check if the product offers its own contrast or theme settings. Use the Contrast Checker tool to verify all text meets WCAG 2.2 AA minimum contrast (4.5:1 for normal text, 3:1 for large text). If the product ignores OS contrast settings and offers no alternative, this fails.","commonFailures":["Product uses hard-coded colours that override OS high contrast settings","Dark mode is available but text contrast ratio drops below 4.5:1 in several places","User can change the colour theme but not individual text/background contrast","Custom CSS or inline styles prevent OS-level contrast preferences from applying"]},"v6":{"text":"At least one mode of operation does not require colour perception.","guidance":"No information, instruction, or control should rely solely on colour to convey meaning. Use text labels, patterns, shapes, or icons alongside colour. Test with a colour blindness simulator.","testMethod":"View the entire product interface through a colour blindness simulator (e.g. Sim Daltonism, Chrome DevTools colour vision deficiency emulation). Select protanopia, deuteranopia, and tritanopia modes. For each mode, verify: (1) all information is still distinguishable, (2) form errors are identifiable without relying on red colour alone, (3) status indicators remain meaningful. If any information is lost, this fails.","commonFailures":["Form validation errors indicated only by a red border with no icon or text message","Required fields marked only with a red asterisk that is invisible to colour-blind users","Data charts use colour-only differentiation between data series with no patterns or labels","Links distinguished from body text only by colour with no underline or other visual cue"]},"v7":{"text":"Status indicators, error states, and data visualisations use non-colour cues.","guidance":"Red/green for pass/fail is insufficient. Add icons (checkmark/cross), text labels (Pass/Fail), or patterns. Charts must use patterns or labels, not just colour differentiation.","testMethod":"Identify all status indicators (online/offline, success/error, pass/fail), error messages, and data visualisations in the product. For each, verify: (1) a non-colour cue exists (icon, text label, pattern, shape), (2) the cue is visible when the page is viewed in greyscale (Chrome DevTools > Rendering > Emulate achromatopsia). If any status or data series relies on colour alone, this fails.","commonFailures":["Pass/fail indicators use green/red circles with no checkmark or cross icon","Online/offline status shown only as a green or grey dot with no text label","Pie chart segments are differentiated only by colour with no labels or patterns","Progress bar uses colour gradient (red to green) as the only indication of progress level"]},"h1":{"text":"At least one mode of operation does not require hearing.","guidance":"Deaf users must be able to complete all essential tasks. All audio information, alerts, instructions, feedback, must have a visual or tactile equivalent. Captions for video, visual alerts for notifications.","testMethod":"Mute all audio output and attempt to complete every core task in the product. Verify: (1) all notification sounds have a visual equivalent (toast, badge, flash), (2) video content has captions, (3) audio instructions have text alternatives, and (4) phone-based features have text-based alternatives (chat, email). If any essential task cannot be completed without hearing, this fails.","commonFailures":["Error alert is an audio beep with no visual notification on screen","Onboarding video has no captions and conveys essential information through audio only","Phone-only customer support with no text-based alternative for deaf users","Two-factor authentication uses phone calls with no SMS or app-based alternative"]},"h2":{"text":"All audio content has a visual or text alternative (captions, transcripts, visual alerts).","guidance":"Every sound, notification beeps, error tones, voice instructions, video audio, must have an equivalent visual representation. This includes system sounds and haptic feedback.","testMethod":"Catalogue all audio content in the product: notification sounds, error tones, voice prompts, video/audio media, system sounds. For each, verify a visual or text alternative exists: (1) captions for video content, (2) transcripts for audio-only content, (3) visual toast notifications for alert sounds, (4) on-screen text for voice instructions. If any audio content lacks an alternative, this fails.","commonFailures":["Notification sounds play but no visual indicator appears on screen","Podcast or audio content embedded in the product has no transcript","Voice-guided tutorials have no caption or text version","System sounds for success/failure actions have no visual feedback"]},"h3":{"text":"At least one mode provides improved audio features for users with limited hearing.","guidance":"Users with partial hearing loss need: adjustable volume beyond normal range, frequency/equalisation adjustment, hearing aid compatibility (telecoil/Bluetooth), and reduced background noise. Test with hearing aid users.","testMethod":"Test the product's audio output capabilities: (1) increase volume to maximum and verify it exceeds the default range (at least +12dB above standard), (2) check for frequency adjustment or equalisation settings, (3) verify Bluetooth audio streaming works with hearing aids in MFi or ASHA mode, (4) check whether background music or ambient sounds can be muted independently. If no improved audio features exist, this fails.","commonFailures":["Maximum volume is too low for users with moderate hearing loss","No frequency adjustment, users with high-frequency hearing loss cannot adjust audio","Bluetooth audio works with headphones but not with hearing aids","Background music cannot be muted separately from voice/dialogue audio"]},"h4":{"text":"Audio output supports hearing aid coupling (magnetic or wireless).","guidance":"Devices with audio output should support T-coil (magnetic coupling) or Bluetooth hearing aid streaming profiles. This is especially important for phones, tablets, kiosks, and terminals.","testMethod":"For hardware products: (1) check specifications for T-coil/telecoil compatibility rating (M3/T3 or higher), (2) test Bluetooth pairing with a hearing aid in streaming mode, (3) verify that audio is clean and free of electromagnetic interference when near the device. For software products: verify that audio output works through the OS hearing aid integration. If the product has audio output but does not support any hearing aid coupling, this fails.","commonFailures":["Self-service kiosk has a speaker but no induction loop or headphone jack for hearing aid users","Phone product has no T-coil rating documented in its specifications","Bluetooth audio streams to headphones but drops connection with hearing aids","Electromagnetic interference from the device causes buzzing in hearing aids"]},"s1":{"text":"At least one mode of operation does not require speech or vocal input.","guidance":"Users who cannot speak (mute users, laryngectomy, speech disabilities) must have alternatives to voice commands, voice authentication, and spoken instructions. Provide text input, touch, or gesture alternatives.","testMethod":"Identify all features that accept or require voice input: voice commands, voice search, voice authentication, phone-based interactions. For each, verify that a non-voice alternative exists: (1) text input field for voice search, (2) keyboard/touch controls for voice commands, (3) PIN/password/biometric for voice authentication, (4) chat/email for phone-based support. If any feature requires voice with no alternative, this fails.","commonFailures":["Smart home product can only be controlled by voice commands with no app or button alternative","Voice search is the primary search method with no text search field visible","Phone-based IVR system requires speaking commands with no keypad alternative","Setup wizard requires voice calibration step that cannot be skipped"]},"s2":{"text":"Voice-activated features have a non-voice alternative.","guidance":"If your product uses voice commands (Siri, Alexa, voice search), provide an equivalent button, text, or touch interface for every voice-activated function.","testMethod":"List every voice-activated feature in the product. For each feature, verify that an equivalent non-voice control exists: (1) a button or menu option for voice commands, (2) a text field for voice search, (3) touch/gesture controls for voice-triggered actions. Test each non-voice alternative to confirm it provides the same functionality. If any voice feature lacks a working non-voice equivalent, this fails.","commonFailures":["Voice command to 'play next song' exists but the app has no next button","Voice search returns richer results than the text search field","Voice-activated accessibility features (e.g. 'read this page') have no menu equivalent","Non-voice alternative exists but is hidden in a submenu and not discoverable"]},"s3":{"text":"Voice authentication has a non-voice fallback.","guidance":"Voice biometrics must not be the only authentication method. Provide PIN, password, fingerprint, or security key alternatives. See also the Biometric Matrix tool.","testMethod":"Check the product's authentication methods. If voice authentication is offered, verify: (1) at least one non-voice authentication method is also available (PIN, password, fingerprint, face recognition, security key), (2) the non-voice method provides the same level of access, and (3) the non-voice method is equally prominent and easy to find. If voice is the only authentication option, this fails.","commonFailures":["Voice is the only biometric option and the fallback is a complex 20-character password","Non-voice fallback exists but is disabled by default and hard to find in settings","Voice authentication provides access to all features but PIN only provides limited access","Fallback method requires contacting support, which itself requires a phone call"]},"mo1":{"text":"At least one mode does not require fine motor control or simultaneous actions.","guidance":"Users with motor impairments (tremors, paralysis, limited dexterity) must be able to operate the product. No pinching, twisting, or simultaneous multi-key presses should be required without an alternative.","testMethod":"Attempt to complete all core tasks using only: (1) keyboard with one finger (no key combinations), (2) a switch device or switch access mode, (3) voice control (Dragon NaturallySpeaking or OS voice control). Verify that no task requires: pinching, twisting, two-handed operation, or simultaneous key presses without an alternative. If any task requires fine motor control with no alternative, this fails.","commonFailures":["Pinch-to-zoom is the only way to zoom on a mobile interface with no button alternative","Two-finger gestures required for essential actions (e.g. Two-finger scroll on a map)","Keyboard shortcuts require simultaneous key presses (Ctrl+Shift+K) with no single-key alternative","Physical product requires twisting a knob that cannot be operated with limited grip strength"]},"mo2":{"text":"Controls can be operated with one hand and do not require tight grasping.","guidance":"All physical controls (buttons, switches, connectors) and digital controls (touch targets, sliders) must be operable with limited strength and dexterity. Support sticky keys, switch access, and single-hand operation.","testMethod":"Test all controls (physical and digital) with one hand only: (1) use only one hand to complete every task, (2) verify that no control requires tight grasping, pinching, or twisting, (3) check that digital touch targets are at least 24x24 CSS pixels (WCAG 2.2 AA), and (4) verify that sticky keys mode works for all keyboard shortcuts. If any control requires two hands or tight grasping, this fails.","commonFailures":["USB connector requires two hands to align and insert","Touch targets are 16x16 pixels, too small for users with limited dexterity","Slider control requires precise dragging that is impossible with tremors","Physical buttons require more than 5N of force to activate"]},"mo3":{"text":"All operable elements are within reach of seated and standing users.","guidance":"Physical controls and interactive elements must be reachable from a wheelchair (max 1220mm from floor) and from a standing position. Digital interfaces must not require precise pointing.","testMethod":"For physical products: (1) measure the height of all operable controls from the floor, (2) verify all controls are between 380mm and 1220mm from the floor (ADA/ISO reach range), (3) check that controls are reachable without leaning or stretching. For digital products: (1) verify all interactive elements are reachable via keyboard, (2) verify touch targets are not placed at extreme edges of large screens. If any control is out of reach range, this fails.","commonFailures":["Self-service kiosk has the card reader at 1400mm height, unreachable from a wheelchair","Touch screen mounted vertically with the top controls beyond reach of seated users","Physical buttons placed on the rear of a device, unreachable without standing and reaching behind it","Digital interface places critical actions at the far corners of a large touch display"]},"mo4":{"text":"Operable elements can be activated with limited reach and strength.","guidance":"Buttons must not require excessive force. Touch targets must be adequately sized. Physical controls must be operable with a closed fist. See the Touch Target Tester tool.","testMethod":"Test all operable elements: (1) for physical buttons, verify they can be activated with a closed fist (no finger precision needed) and require less than 5N of force, (2) for digital touch targets, verify they meet the 24x24 CSS pixel minimum (WCAG 2.2 AA), (3) for connectors and ports, verify they can be operated with limited grip. Use the Touch Target Tester tool for digital interfaces. If any element requires excessive force or precision, this fails.","commonFailures":["Power button is recessed and requires a fingernail to press","Touch targets in the mobile interface are 20x20 pixels, below the 24x24 minimum","SIM card tray requires a pin tool to open with no alternative","Toggle switches are too small and stiff for users with limited hand strength"]},"co1":{"text":"No content or interaction triggers photosensitive seizures.","guidance":"No element flashes more than 3 times per second. Avoid rapid colour transitions, strobing effects, and high-contrast flashing patterns. Test with the PEAT (Photosensitive Epilepsy Analysis Tool) or Trace Centre Flicker tool.","testMethod":"Review all animated and video content in the product. Use the PEAT tool (Photosensitive Epilepsy Analysis Tool) or the Harding test to analyse content. Manually check: (1) no element flashes more than 3 times per second, (2) the combined area of simultaneous flashes does not exceed 21,824 sq pixels, (3) no rapid red-to-dark transitions occur. If any content violates these thresholds, this fails.","commonFailures":["Hero banner with a strobing animation that flashes more than 3 times per second","Video content with rapid scene transitions and flash photography not preceded by a warning","Loading animation uses a pulsing effect with high contrast that triggers seizure risk thresholds","Game or interactive content has explosion or lightning effects without a seizure warning or option to disable"]},"co2":{"text":"Users can disable or reduce animations and motion.","guidance":"Respect the prefers-reduced-motion media query. Provide a user setting to pause, stop, or disable animations, auto-playing content, and parallax effects.","testMethod":"Enable the 'Reduce motion' setting in the OS (macOS: System Settings > Accessibility > Display; Windows: Settings > Accessibility > Visual Effects > Animation effects off). Verify: (1) the product respects prefers-reduced-motion by disabling or reducing animations, (2) a manual toggle exists in the product's settings to disable animations, (3) auto-playing content can be paused. If the product ignores reduced motion preferences, this fails.","commonFailures":["CSS animations continue running despite prefers-reduced-motion being set","Auto-playing video or carousel cannot be paused or stopped","Parallax scrolling effects persist regardless of user motion preferences","Product has no animation settings and does not respond to OS-level preferences"]},"co3":{"text":"At least one mode is simpler and easier to use for users with limited cognition.","guidance":"Provide clear, simple language. Use consistent navigation. Minimise the number of steps to complete tasks. Offer help text, tooltips, and error prevention. Avoid jargon and complex sentence structures.","testMethod":"Evaluate the product using the Readability tool to check language complexity (target: Grade 8 or below on Flesch-Kincaid). Count the number of steps to complete the 3 most common tasks. Verify: (1) language is clear and free of unnecessary jargon, (2) core tasks can be completed in 5 steps or fewer, (3) help text or tooltips are available for complex inputs, and (4) navigation is consistent across all pages. If language is complex and no simplified mode exists, this fails.","commonFailures":["Legal and technical jargon used throughout the interface with no plain-language alternative","Core task requires 12+ steps with no simplified flow or wizard","No help text or tooltips on form fields, users must guess what information is required","Navigation changes structure between sections, disorienting users with cognitive disabilities"]},"co4":{"text":"Error prevention and recovery mechanisms are provided.","guidance":"Users with cognitive disabilities make more errors. Provide clear error messages, undo functionality, confirmation steps for destructive actions, and auto-save. Do not time out without warning.","testMethod":"Deliberately trigger errors in the product: submit empty forms, enter invalid data, attempt destructive actions. Verify: (1) error messages are clear and specific (not just 'An error occurred'), (2) error messages indicate how to fix the problem, (3) destructive actions have a confirmation step, (4) undo is available for reversible actions, and (5) session timeouts give at least 20 seconds warning with an option to extend. If errors are vague or unrecoverable, this fails.","commonFailures":["Error message says 'Invalid input' without indicating which field or what is expected","Deleting an account is a single click with no confirmation dialog","Form submission clears all entered data when one field has an error","Session times out after 15 minutes with no warning, losing all unsaved work"]},"co5":{"text":"Content is predictable, consistent layout, navigation, and terminology.","guidance":"Pages should use the same navigation structure, the same terminology for the same actions, and the same layout patterns throughout. Unexpected changes in context disorient users with cognitive disabilities.","testMethod":"Navigate through at least 10 different screens in the product. Verify: (1) the main navigation is in the same position on every page, (2) the same action uses the same label everywhere (e.g. Not 'Save' on one page and 'Submit' on another for the same action), (3) page layouts follow a consistent pattern, and (4) no unexpected context changes occur (e.g. Opening a new window without warning). If navigation or terminology is inconsistent, this is partial or fail.","commonFailures":["Navigation menu is at the top on some pages and in a sidebar on others","Same action called 'Save', 'Submit', 'Confirm', and 'Done' on different pages","Clicking a link opens a new browser window without any visual indication","Form fields are in a different order on the edit page compared to the creation page"]},"co6":{"text":"Privacy is maintained when using accessibility features.","guidance":"Using accessibility features must not expose the user to privacy loss. Screen reader output should be available privately (headphones). Magnification should not expose content to bystanders. Biometric fallbacks must not require disclosing disability status.","testMethod":"Review each accessibility feature for privacy implications: (1) check if screen reader output is available through headphones (not just speakers), (2) verify that magnification does not force full-screen mode that exposes content to bystanders, (3) confirm that requesting an accessibility alternative (e.g. A text-based alternative to voice auth) does not require the user to disclose their disability, and (4) check that accessibility preference data is not shared with third parties. If using any accessibility feature exposes the user's disability or private data, this fails.","commonFailures":["Self-service kiosk announces screen reader output through a public speaker","Requesting accessible format requires selecting a disability category from a dropdown","Accessibility preferences are tracked and shared with third-party analytics","Using magnification on a shared terminal reveals the previous user's data at large size"]}},"export":{"filename":"Functional-criteria-checklist","title":"FUNCTIONAL PERFORMANCE CRITERIA CHECKLIST","subtitle":"EAA Annex I Section VII \\u2014 Outcome-Based Accessibility Criteria"}},"generic-ict-checklist":{"meta":{"title":"Generic ICT Requirements Checklist, EN 301 549 Chapter 5","description":"EN 301 549 Chapter 5 Compliance Checklist, verify that your ICT products meet generic accessibility requirements for closed functionality, biometrics, preservation of accessibility, and operable parts."},"header":{"title":"Generic ICT Requirements Checklist","subtitle":"EN 301 549 Chapter 5 Compliance Checklist"},"description":"EN 301 549 Chapter 5 Compliance Checklist, verify that your ICT products meet generic accessibility requirements for closed functionality, biometrics, preservation of accessibility, and operable parts.","headerLinks":{"eaaDirective":"EAA Directive 2019/882","en301549":"EN 301 549 V3.2.1"},"features":["EN 301 549 Chapter 5 full coverage","19 checkpoints across closed functionality, biometrics, preservation & operable parts","Pass / Partial / Fail / N/A per item with guidance","How-to-test guidance and common failures for every checkpoint","Links to relevant testing tools on AccessibilityRef","Progress auto-saved in your browser","Export Word report with notes","Direct links to EAA Directive and EN 301 549"],"categories":{"closed":{"label":"Closed Functionality","description":"EN 301 549 §5.1, Requirements for ICT with closed functionality where assistive technology cannot be connected."},"activation":{"label":"Activation of Accessibility Features","description":"EN 301 549 §5.2, Accessibility features must be discoverable and activatable without needing the feature itself."},"biometrics":{"label":"Biometrics","description":"EN 301 549 §5.3, If biometric identification or control is used, alternatives must be provided."},"preservation":{"label":"Preservation of Accessibility","description":"EN 301 549 §5.4, When ICT converts, transmits, or processes content, accessibility information must be preserved."},"operable":{"label":"Operable Parts","description":"EN 301 549 §5.5–§5.9, Physical and input requirements for ICT controls."}},"items":{"cf1":{"text":"ICT with closed functionality provides all visual content via audio output without requiring vision.","guidance":"Kiosks, ATMs, and embedded devices that cannot run screen readers must speak all on-screen text and status information aloud.","testMethod":"Approach the device and close your eyes or look away from the screen. Attempt to complete a full transaction using only audio output (plug in headphones if required). Verify that every piece of on-screen text, menu options, status messages, error alerts, and confirmation screens, is spoken aloud. If any visual-only information is not available through audio, this fails.","commonFailures":["Self-service check-in kiosk at a hotel displays a room number on screen after check-in but does not speak it, a blind user cannot learn their room number","Parking meter shows pricing tiers visually but the audio output only reads the default option, not all available choices","ATM speaks menu options but does not announce error messages like 'Insufficient funds' or 'Card declined'","Retail self-checkout kiosk reads product names but does not announce the running total or final price"]},"cf2":{"text":"Audio output of visual information is available without requiring vision to operate it.","guidance":"The mechanism to enable audio output (e.g. Headphone jack, speech button) must itself be findable and operable without sight, tactile markers, standardised positioning.","testMethod":"Without looking at the device, attempt to locate and activate the audio output mechanism. Feel for a headphone jack (should be in a standard position, e.g. Front panel lower edge), a tactile button with a raised icon, or a braille label. If you cannot find or activate the audio output without visual assistance, this fails.","commonFailures":["Headphone jack is on the back of a kiosk where users cannot reach it without staff assistance","Audio assistance button is a flat touchscreen icon with no tactile marker, indistinguishable by touch","Speech button exists but requires a visual menu selection first to enable it, creating a chicken-and-egg problem","Headphone jack is present but unlabelled and positioned identically to a USB port next to it"]},"cf3":{"text":"Auditory output is delivered privately when headphones are required.","guidance":"In public environments, audio output should default to a headphone jack. Volume controls must be tactilely operable.","testMethod":"Check whether the device has a headphone jack for private listening. Plug in headphones and verify that audio routes to them correctly. Locate the volume control, it must be findable by touch (physical dial, raised buttons, or tactile markers). Test that volume can be adjusted from minimum to a comfortable level without seeing the screen. If volume controls are on-screen only, this fails.","commonFailures":["Self-service kiosk has no headphone jack, audio plays through a public speaker, exposing private information like account balances","Headphone jack exists but audio continues to play through the speaker simultaneously, negating privacy","Volume control is a touchscreen slider with no physical alternative","Volume buttons exist but are flush with the surface and identical in shape to surrounding decorative elements"]},"cf4":{"text":"Audio output correlates with visual information in a logical order.","guidance":"When the screen shows a list or menu, the audio must read items in the same order. Random or out-of-order audio is disorienting.","testMethod":"Display a screen with multiple items (e.g. A menu with 4 options). Listen to the audio output and simultaneously observe the screen. Verify that items are read in the same top-to-bottom, left-to-right order as they appear visually. Navigate forward and backward through the list and confirm that audio matches the visual highlight position.","commonFailures":["Kiosk displays a 2-column menu but audio reads across rows instead of down columns, creating a confusing order","Navigation menu reads items alphabetically in audio but displays them in a different order on screen","When the user navigates backward in a list, the audio announces the wrong item because the audio cursor is out of sync"]},"cf5":{"text":"Speech output for user input confirmation is provided.","guidance":"When a user selects an option or enters data, the system must confirm the action via speech, e.g. 'You selected Option 2' or 'Amount entered: €50'.","testMethod":"Using the device with headphones (or audio output enabled), perform several actions: select a menu option, enter a number, confirm a choice. After each action, listen for a spoken confirmation that tells you exactly what you did. Check that the confirmation includes the specific value. If any user action produces no spoken confirmation, or the confirmation is generic and does not repeat the specific input, this fails.","commonFailures":["ATM accepts PIN entry but does not confirm how many digits have been entered, user cannot tell if they mistyped","Kiosk says 'Selection confirmed' without specifying what was selected, user cannot verify they chose correctly","Number entry on a parking meter produces a beep for each keypress but does not speak the digit or the running total","Confirmation speech is provided for the final step but not for intermediate selections in a multi-step workflow"]},"af1":{"text":"Accessibility features can be discovered and activated without requiring the accessibility feature being activated.","guidance":"A screen reader toggle must be keyboard-accessible. A high-contrast mode switch must be visible in normal contrast. Don't create chicken-and-egg problems.","testMethod":"For each accessibility feature your product offers (screen reader mode, high contrast, text resize, captions, keyboard navigation), attempt to discover and activate it without already having that feature turned on. If any accessibility feature can only be activated by using the feature itself, this fails.","commonFailures":["Screen reader mode is toggled via a button that is only visible to screen reader users but is not keyboard-focusable in normal mode","High-contrast mode toggle uses low-contrast text (grey on white) that users who need high contrast cannot read","Accessibility settings are inside a menu that requires mouse hover to open, keyboard users cannot reach them","Voice control activation requires speaking a command, but the voice control feature must first be enabled in a visual settings menu"]},"af2":{"text":"Documentation for activating accessibility features is available in an accessible format.","guidance":"Instructions for enabling screen reader mode, captions, or keyboard navigation must not be locked inside an inaccessible format.","testMethod":"Locate the documentation that explains how to activate accessibility features. Check its format: is it an accessible HTML page, a tagged PDF, or an accessible EPUB? Open it with a screen reader and verify it can be read. If the instructions are only available in an image, a video with no captions, or an untagged PDF, this fails.","commonFailures":["Accessibility setup guide is a PDF consisting of screenshots with no alt text or text layer","Instructions for enabling keyboard navigation are in a video tutorial with no captions or transcript","Help article on activating high-contrast mode is formatted with colour-coded steps that are meaningless to colour-blind users","Documentation is in an accessible format but requires login to access, and the login page itself is not keyboard-accessible"]},"af3":{"text":"Accessibility settings persist across sessions and are not reset on restart.","guidance":"If a user enables high contrast or text magnification, those settings should be preserved when they next use the product.","testMethod":"Enable an accessibility feature (e.g. High contrast, large text, screen reader mode). Close the application or browser and reopen it. Log out and log back in. Check whether the accessibility setting is still active. If the setting resets to default on restart, page navigation, or re-login, this fails.","commonFailures":["High-contrast mode resets to default every time the user navigates to a new page in a single-page application","Text size preference is stored in a session cookie that expires when the browser is closed","Accessibility settings persist on the device where they were set but do not sync to other devices via the user profile","App update resets all settings to defaults, including accessibility preferences, without warning"]},"b1":{"text":"If biometric authentication is used, at least one non-biometric alternative exists.","guidance":"Fingerprint, facial recognition, or voice authentication must have a fallback, PIN, password, or security key. Users with disabilities affecting biometric characteristics must not be locked out.","testMethod":"Identify all points in the user journey where biometric authentication is used. For each, check whether a non-biometric alternative is available on the same screen or within one step. Attempt to complete the full authentication flow using only the non-biometric method. If any biometric checkpoint has no alternative, or the alternative is hidden or requires contacting support to enable, this fails.","commonFailures":["Banking app requires fingerprint for payment confirmation with no PIN fallback, users with limb differences cannot complete transactions","Facial recognition login has a password fallback, but the 'Use password instead' link is only visible after a failed face scan","Voice authentication for phone banking has no alternative for users with speech impairments","Non-biometric alternative exists but requires a separate registration process that was never communicated to users"]},"b2":{"text":"The non-biometric alternative is equally secure and available in all contexts.","guidance":"The alternative must not be a degraded experience, e.g. If biometrics allow instant login, the PIN path should not require extra steps or verification.","testMethod":"Compare the biometric authentication flow side-by-side with the non-biometric alternative. Count the number of steps in each. Check whether the alternative provides access to the same features. If the non-biometric path requires more verification steps, imposes lower limits, or restricts access to certain features, this fails.","commonFailures":["Fingerprint login is instant but the PIN fallback requires answering two security questions plus an SMS verification code","Biometric authentication allows transactions up to 10,000 EUR but the password fallback caps at 500 EUR","Non-biometric login works in the app but not on the website","PIN fallback is available but the PIN entry screen has a 10-second timeout that is too fast for users with motor impairments"]},"pr1":{"text":"When content is converted or transmitted, accessibility metadata (alt text, captions, structure) is preserved.","guidance":"If your system transcodes documents, converts formats, or processes uploads, verify that alt text, heading structure, caption tracks, and ARIA attributes survive the pipeline.","testMethod":"Create a test document or media file with known accessibility metadata. Process it through your system (upload, convert, publish). Open the output and verify each piece of accessibility metadata is intact. Use a screen reader to confirm alt text is still present, headings are still navigable, and caption tracks still play.","commonFailures":["Document management system converts uploaded Word files to PDF but strips all heading tags and alt text in the process","CMS image upload pipeline re-encodes images and discards embedded alt text metadata without transferring it to the HTML output","Video transcoding service outputs HLS streams but drops the WebVTT caption file from the manifest","Email system converts rich HTML emails to plain text for some recipients, losing all structural markup and image descriptions"]},"pr2":{"text":"Accessibility information is not degraded during format conversion.","guidance":"Converting a tagged PDF to HTML should preserve heading levels and alt text. Converting EPUB to MOBI should preserve reading order.","testMethod":"Take a well-structured accessible document and convert it to each output format your system supports. Compare the input and output side by side: check that heading levels match, alt text content is identical, reading order is preserved, and table structure is maintained. If any accessibility feature is degraded, this fails.","commonFailures":["PDF-to-HTML converter flattens all headings to paragraphs with inline bold styling, heading structure is lost","EPUB-to-MOBI conversion drops table header cell markup, making data tables unnavigable with a screen reader","Alt text longer than 100 characters is truncated during format conversion with no warning to the content author","Reading order in a multi-column PDF is re-ordered incorrectly when converted to a single-column HTML layout"]},"op1":{"text":"Controls do not require tight grasping, pinching, or wrist twisting to operate.","guidance":"Buttons, switches, dials, and connectors must be operable with a closed fist or flat palm. This applies to hardware products and physical peripherals.","testMethod":"Attempt to operate every physical control on the device using a closed fist. If any control requires pinching, tight grasping, or wrist twisting, this fails. Also test with a flat palm, large, raised buttons should respond. Pay special attention to battery compartments, SIM card trays, and cable connectors.","commonFailures":["Payment terminal has a SIM card tray that requires a pinch grip and a pin tool to open, technicians with motor impairments cannot service it","Hardware device uses a small recessed reset button that requires a paperclip, no accessible alternative exists","Rotary dial on a smart home controller requires fine wrist rotation to select options","USB-C port is recessed so deeply that connecting a cable requires precise finger positioning and sustained pinch pressure"]},"op2":{"text":"Controls are tactilely discernible without activation.","guidance":"Users must be able to find and identify buttons and switches by touch without accidentally pressing them. Raised markers, distinct shapes, or textured surfaces help.","testMethod":"Close your eyes and run your fingers across the device controls. Can you distinguish each button from the surrounding surface? Can you tell buttons apart from each other by shape, size, or texture? Can you find a specific button without activating it? If buttons are flat, flush, and identical by touch, this fails.","commonFailures":["Kiosk has a smooth glass surface with capacitive touch buttons, completely undetectable by touch","All buttons on a remote control are the same shape, size, and texture, impossible to distinguish by touch","Power button is identical in feel to the volume buttons, leading to accidental shutdowns","Touch-sensitive controls activate on contact rather than on press, making tactile exploration impossible without triggering actions"]},"op3":{"text":"Locking or toggle key status is determinable non-visually (tactile or audio).","guidance":"Caps Lock, Num Lock, toggle buttons, their on/off state must be communicated through touch or sound, not just an on-screen light.","testMethod":"Identify all toggle or locking controls on the device. Toggle each one and check whether you can determine the current state without looking. Listen for audio feedback. Feel for a tactile change. If the only state indicator is a visual LED or on-screen icon, this fails.","commonFailures":["Keyboard Caps Lock is indicated only by a small LED that blind users cannot see","Mute button on a conference phone toggles an on-screen icon but produces no audio confirmation tone","Bluetooth toggle on a portable speaker has no tactile or audio feedback, user must check a phone app to see if Bluetooth is on","Toggle switch has the same physical position for on and off (push-push mechanism) with only a colour-changing LED as feedback"]},"op4":{"text":"Locking or toggle key status is determinable visually.","guidance":"The visual indicator for toggle state must meet contrast requirements and be clearly visible, not just a tiny LED.","testMethod":"Check each toggle or locking control for its visual state indicator. Verify that the indicator is large enough to see at normal viewing distance, has sufficient contrast, and is unambiguous. Test in both bright and dim lighting.","commonFailures":["Caps Lock LED is a 1mm blue dot that is invisible in bright office lighting","Toggle state indicated by green vs. Red LED, indistinguishable for users with red-green colour blindness","On/off indicator is a subtle change in LED brightness rather than a clear on/off distinction","Status LED is positioned on the back or bottom of the device where users cannot see it during normal use"]},"op5":{"text":"Key repeat can be adjusted or disabled by the user.","guidance":"Users with motor impairments may accidentally hold keys. The repeat rate and delay must be configurable.","testMethod":"Go to the device or application settings and look for key repeat or keyboard settings. Check whether you can adjust the repeat delay and repeat rate. Set the delay to maximum and verify that holding a key for a reasonable duration does not produce repeated characters. If no key repeat settings exist, this fails.","commonFailures":["Embedded kiosk keyboard has no configurable repeat settings, holding a key for 300ms starts rapid repeat","Application overrides the operating system's key repeat settings with its own faster defaults and provides no way to change them","Key repeat settings exist but are in an advanced menu that requires administrator access to reach"]},"op6":{"text":"Double-strike key acceptance interval can be adjusted.","guidance":"Users with tremors may press a key twice unintentionally. The system should allow adjustment of the minimum time between accepted keystrokes.","testMethod":"Check settings for a 'bounce key' or 'key debounce' option. Test it by setting a debounce interval and rapidly pressing the same key twice within that window, only one keypress should be registered. If no such setting exists, check whether the OS accessibility settings are respected. If neither is available, this fails.","commonFailures":["Custom keyboard input handler in a web application ignores the operating system's Filter Keys settings","Kiosk touch keyboard has no debounce setting, users with tremors register accidental double taps on every key","Debounce setting exists but applies globally to all keys including modifier keys, making Shift+letter combinations impossible"]},"op7":{"text":"No simultaneous user actions are required unless an alternative exists.","guidance":"If a function requires pressing two keys at once (Ctrl+S) or using two hands, provide a sequential alternative, sticky keys support or menu option.","testMethod":"Identify all functions that require simultaneous actions. For each, verify that a sequential alternative exists, sticky keys support, a menu option, or a toolbar button. If any critical function requires simultaneous actions with no alternative, this fails.","commonFailures":["Application uses Ctrl+Shift+P as the only way to access a critical function with no menu equivalent","Mobile app requires a two-finger pinch gesture to zoom with no zoom buttons or accessibility gesture alternative","Hardware device requires simultaneously pressing two buttons on opposite sides to open the battery compartment","Web application supports sticky keys for some shortcuts but not for its custom keyboard shortcuts"]}}},"hardware-checklist":{"meta":{"title":"Consumer Hardware Accessibility Checklist, EAA Annex I + EN 301 549 Chapter 8","description":"EAA Annex I Section I + EN 301 549 Chapter 8 compliance checklist, verify that your consumer hardware (smartphones, tablets, computers, TVs, e-readers) meets European Accessibility Act requirements."},"header":{"title":"Consumer Hardware Accessibility Checklist","subtitle":"EAA Annex I Section I + EN 301 549 Chapter 8 Compliance Checklist"},"description":"EAA Annex I Section I + EN 301 549 Chapter 8 compliance checklist, verify that your consumer hardware (smartphones, tablets, computers, TVs, e-readers) meets European Accessibility Act requirements.","headerLinks":{"eaaDirective":"EAA Directive 2019/882","en301549":"EN 301 549 V3.2.1"},"features":["EAA Annex I Section I + EN 301 549 Chapter 8 full coverage","27 checkpoints across physical controls, audio/visual, accessibility features, connectors, docs & hearing aids","Pass / Partial / Fail / N/A with notes per item","How-to-test guidance and common failures for every checkpoint","Links to relevant testing tools on AccessibilityRef","Progress auto-saved in your browser","Export Word report with notes","Direct links to EAA Directive and EN 301 549"],"categories":{"controls":{"label":"Physical Controls & Interaction","description":"EN 301 549 §8.4 + §5.5, Physical buttons, switches, and controls must be accessible to users with motor and visual impairments."},"audio-visual":{"label":"Audio & Visual Output","description":"EN 301 549 §5.1 + EAA Annex I §I, Hardware must provide multi-modal output."},"a11y-features":{"label":"Built-in Accessibility Features","description":"EN 301 549 §5.2, Devices must include or support accessibility features that are discoverable and persistent."},"connectors":{"label":"Connectors & Physical Ports","description":"EN 301 549 §8.4, Ports and connectors must be identifiable and usable."},"docs":{"label":"Documentation & Packaging","description":"EAA Annex I §I, Product documentation and packaging information must be accessible."},"hearing":{"label":"Hearing Aid Compatibility","description":"EAA Annex I §I, Devices with audio output must consider hearing aid users."}},"items":{"hc1":{"text":"Physical controls do not require tight grasping, pinching, or wrist twisting to operate.","guidance":"Buttons, switches, dials, and ports must be operable with a closed fist or flat palm. This includes power buttons, volume rockers, SIM trays, and port covers."},"hc2":{"text":"Physical controls are tactilely discernible without activation.","guidance":"Users must be able to find and identify buttons by touch without accidentally pressing them. Raised edges, distinct shapes, or textured surfaces help."},"hc3":{"text":"If a numeric keypad is present, it follows telephone layout (1-2-3 top row).","guidance":"Do not use calculator layout. Standard telephone layout matches tactile expectations for blind users."},"hc4":{"text":"Key 5 on numeric keypads has a tactile marker for orientation.","guidance":"A raised dot or bar on the centre key allows blind users to orient their fingers on the keypad."},"hc5":{"text":"Toggle and lock key status is determinable non-visually (tactile or audio feedback).","guidance":"Caps Lock, Mute, and similar toggles must communicate their state through touch or sound, not just a screen indicator or LED."},"hc5b":{"text":"Where the hardware requires timed responses, the user can request more time.","guidance":"If the device times out an interaction, the user must be warned and given the option to extend the time before action is taken."},"hc6":{"text":"Toggle and lock key status is determinable visually with sufficient contrast.","guidance":"Visual LED or on-screen indicators for toggle state must be clearly visible, not a tiny, low-contrast light."},"av1":{"text":"Information is provided through more than one sensory channel (visual + audio at minimum).","guidance":"Critical information (errors, alerts, status) must not be visual-only or audio-only. Provide both a visual display and an audio cue."},"av2":{"text":"Speech output is available for all displayed text (built-in or via screen reader).","guidance":"The device must either have built-in text-to-speech or support connection of assistive technology that provides it."},"av3":{"text":"Volume control is adjustable and has a visual indicator of current level.","guidance":"Users must be able to adjust audio output volume. A visual bar, number, or icon showing the current level is required."},"av4":{"text":"Private audio output is available (headphone jack or Bluetooth).","guidance":"In shared environments, users need private listening. A 3.5mm jack or Bluetooth audio output is the minimum."},"av5":{"text":"Device can display closed captions for media content.","guidance":"TVs, tablets, and computers must be capable of rendering closed captions from media sources."},"af1":{"text":"Screen magnification is supported (built-in or via OS accessibility settings).","guidance":"Users with low vision need to enlarge portions of the screen. The device must support zoom gestures, magnification window, or OS-level screen magnification."},"af2":{"text":"High contrast or colour inversion mode is available.","guidance":"Users with low vision or light sensitivity need high contrast display options. The device or OS must provide this setting."},"af3":{"text":"Switch access or alternative input methods are supported.","guidance":"Users who cannot use touchscreen or keyboard directly need switch control, head tracking, or eye tracking support."},"af4":{"text":"Accessibility features can be activated without requiring the feature itself.","guidance":"The screen reader activation path must not require a screen reader. The magnifier must be activatable without needing magnification to find the setting."},"af5":{"text":"Accessibility settings persist across power cycles and updates.","guidance":"If a user enables VoiceOver, it must remain enabled after restart and after OS updates. Settings must not be silently reset."},"cn1":{"text":"Connectors and ports are tactilely distinguishable or standardised in position.","guidance":"USB, headphone, and charging ports should be identifiable by shape, position, or tactile marking."},"cn2":{"text":"Colour coding of connectors is not the sole means of identification.","guidance":"If ports use colour coding, there must also be shape, label, or tactile differentiation."},"cn3":{"text":"Port connections do not require fine motor dexterity beyond what the connector standard requires.","guidance":"Magnetic charging, USB-C reversible connectors, and wireless alternatives reduce motor demands."},"dc1":{"text":"Product manual / instructions are available in at least one accessible digital format.","guidance":"Paper-only manuals are inaccessible to blind users. Provide an accessible HTML, EPUB, or tagged PDF version online."},"dc2":{"text":"Setup and installation instructions are available in multiple formats (visual + text + audio/video).","guidance":"Quick-start guides should not be image-only. Provide text instructions alongside diagrams."},"dc3":{"text":"Product packaging identifies accessibility features on the label.","guidance":"The box or listing should indicate key accessibility features, 'Screen reader compatible', 'Hearing aid compatible', etc."},"dc4":{"text":"Documentation describes how to activate and use each accessibility feature.","guidance":"Step-by-step instructions for enabling VoiceOver, magnification, switch control, captions, with the same detail as other feature documentation."},"ha1":{"text":"Device supports hearing aid coupling (magnetic/telecoil or Bluetooth).","guidance":"Phones and tablets must support connection to hearing aids, either via T-coil or Bluetooth hearing aid streaming profiles."},"ha2":{"text":"Audio output quality is sufficient for speech intelligibility with hearing aids.","guidance":"Electromagnetic interference from the device must not degrade audio quality when using hearing aid coupling."}}},"headings-pro":{"meta":{"toolId":"Headings-pro","title":"Heading Structure Analyser Pro"},"badge":"Pro","title":"Heading Structure Analyser Pro","description":"Batch analyse up to 50 URLs, full heading tree, issue detection, and CSV export.","wizardBanner":{"toolName":"Heading Structure Checker"},"proGateFeatures":["Batch-analyse heading structure across up to 50 URLs at once","Detects missing H1, multiple H1s, and skipped heading levels","Visual heading tree per URL, see the full document outline","Export complete audit as CSV for development teams or compliance evidence"],"infoPanel":{"toggle":"What this tool checks, and why heading structure is a legal requirement","whatItDoes":{"heading":"What this tool does","description":"Paste up to 50 URLs at once. The batch processor fetches each page, extracts every heading element (H1–H6), and checks the structure for common failures: a missing H1, more than one H1, or heading levels that skip (e.g. Jumping from H2 to H4).","paragraph1":"Paste up to 50 URLs at once. The batch processor fetches each page, extracts every heading element (H1–H6), and checks the structure for common failures: a missing H1, more than one H1, or heading levels that skip (e.g. Jumping from H2 to H4). Each URL gets a pass/fail badge, a visual heading tree, and a score. The full result set can be exported as CSV for handoff to developers or inclusion in an audit report.","paragraph2":"This is the Pro batch version, the free single-URL tool is available at <strong>Heading Analyser</strong> in the tools menu."},"legalRequirement":{"heading":"Why heading structure is required by law","items":{"wcag131":{"label":"WCAG 2.2 SC 1.3.1","title":"Info and Relationships, Level A.","body":"Information conveyed through structure must be programmatically determined. A logical heading hierarchy is the primary mechanism for conveying document structure to assistive technology users. Skipping levels or omitting an H1 breaks this."},"wcag246":{"label":"WCAG 2.2 SC 2.4.6","title":"Headings and Labels, Level AA.","body":"Headings and labels must describe the topic or purpose. This is mandatory under all major legal frameworks. A page with no H1, or headings that are vague or out of order, fails this criterion."},"eaa":{"label":"EAA 2025","titleRich":"European Accessibility Act (Directive 2019/882)","bodyRich":", applies from <strong>28 June 2025</strong>. Requires WCAG 2.1 AA via EN 301 549 (clauses 9.1.3.1 and 9.2.4.6). Heading structure failures are detectable in automated audits and will appear in enforcement investigations."},"en301549":{"label":"EN 301 549","body":"The European harmonised standard. Clauses 9.1.3.1 and 9.2.4.6 directly map to SC 1.3.1 and SC 2.4.6. Compliance with EN 301 549 creates a legal presumption of conformity under the EAA."},"ukPsbar":{"label":"UK PSBAR","title":"Public Sector Bodies Accessibility Regulations 2018.","body":"Requires WCAG 2.1 AA. The CDDO's monitoring programme specifically checks heading structure as part of automated and manual testing."},"adaSection508":{"label":"ADA / Section 508","body":"US federal and court-applied standards both reference WCAG 2.0/2.1 AA. Missing or disordered headings are a common finding in ADA demand letters and Section 508 audits of federal agency sites."}}},"screenReaders":{"heading":"How screen reader users rely on headings","body":"Screen reader users, who cannot visually scan a page, navigate primarily by jumping between headings. NVDA, JAWS, and VoiceOver all provide keyboard shortcuts to move through H1–H6 elements. A page with no H1 gives the user no sense of the page topic. Skipped levels create confusion about the document structure. Multiple H1s make it impossible to determine the primary subject. These are not theoretical issues, they directly prevent users from accessing content efficiently."},"howToUse":{"heading":"How to use this tool","steps":["Paste your URLs (one per line), home page, key landing pages, article templates, checkout flow.","Run the analysis and review the summary table for pages with issues.","Open individual accordions to see the heading tree and understand the structural problem.","Export as CSV and share with your development team, or include in a compliance report as evidence of audit scope and findings."]}},"inputModes":{"pasteUrls":"Paste URLs","sitemapScanner":"Sitemap Scanner","sitemapLocked":"Sitemap Scanner","sitemapTooltip":"Upgrade to Pro to use the Sitemap Scanner"},"input":{"urlLabel":"URLs to analyse, one per line (max 50)","urlPlaceholder":"Https://example.com\nhttps://example.com/about\nhttps://example.com/contact","sitemapLabel":"Sitemap URL","sitemapPlaceholder":"Https://example.com/sitemap.xml","loadSitemap":"Load Sitemap","loading":"Loading…"},"sitemap":{"urlsFoundOne":"{count} URL found in sitemap","urlsFoundOther":"{count} URLs found in sitemap","fullSiteWillBeAnalysed":"Full site will be analysed","willBeSampledOne":"{count} page will be sampled (20% of site)","willBeSampledOther":"{count} pages will be sampled (20% of site)","readyToAnalyse":"Ready to analyse"},"queue":{"queuedOne":"{count} URL queued","queuedOther":"{count} URLs queued","manualLimitWarning":"(only first {limit} will be scanned)","fullSite":"(full site)","sample20":"(20% sample)"},"actions":{"runAnalysis":"Run Analysis","analysing":"Analysing","exportCsv":"Export CSV","rescanFailed":"Rescan Failed","rescanFailedWithCount":"Rescan Failed ({count})","expandAll":"Expand all","collapseAll":"Collapse all"},"progress":{"processing":"Processing {current} of {total}…","doNotClose":"Do not close this window, the scanner runs at up to 80 pages per minute and may take several minutes to complete."},"results":{"summary":"Summary","detailedResults":"Detailed Results","urlsScanned":"URLs Scanned","totalHeadings":"Total Headings","issuesFound":"Issues Found","passing":"Passing","auditSummaryOne":"Audit Summary, {count} URL","auditSummaryOther":"Audit Summary, {count} URLs"},"table":{"url":"URL","h1Count":"H1 Count","totalHeadings":"Total Headings","issues":"Issues","status":"Status","score":"Score","noIssues":"None","issuesCountOne":"{count} issue","issuesCountOther":"{count} issues"},"accordion":{"issuesFound":"Issues Found ({count})","noIssues":"No heading structure issues detected.","headingTreeOne":"Heading Tree ({count} heading)","headingTreeOther":"Heading Tree ({count} headings)","noHeadings":"No headings found on this page.","emptyHeading":"(empty heading)","howToFix":"How to fix","errorPrefix":"Error: {message}","unknownError":"Unknown error"},"issues":{"noHeadings":"No heading elements found on this page.","noHeadingsRemediation":"Add a logical heading hierarchy starting with a single H1 for the page title, then H2 for major sections, H3 for sub-sections, and so on. Every content page should have at minimum an H1.","missingH1":"No H1 found on this page.","missingH1Remediation":"Add a single H1 that describes the main topic or purpose of the page. Screen reader users navigate by jumping between headings, the H1 is the primary landmark. In most cases, the H1 text and the page <title> should convey the same information.","multipleH1":"{count} H1 elements found, only one H1 is recommended per page.","multipleH1Remediation":"Demote the additional H1 elements to H2 or appropriate sub-levels. A single H1 identifies the primary subject of the page. Note: HTML5 sectioning (article/section) allows multiple H1s in theory, but WCAG guidance recommends a single H1 for maximum AT compatibility.","skippedLevel":"Heading level skipped: H{prev} → H{curr} (missing H{missing}).","skippedLevelRemediation":"Change the H{curr} to H{missing}, or add an intermediate H{missing} section. Do not choose heading levels for their visual size, use CSS for styling. Screen readers announce heading levels numerically; jumping levels signals a broken document outline.","emptyHeadingOne":"{count} empty heading element with no text content.","emptyHeadingOther":"{count} empty heading elements with no text content.","emptyHeadingRemediation":"Remove the empty heading tags or add meaningful text. Empty headings break the document outline and are announced as blank by screen readers. This commonly occurs when CMS editors insert an empty heading block for spacing, use CSS margin/padding instead.","headingOveruse":"{count} headings found, unusually high for a single page.","headingOveruseRemediation":"Review whether all heading elements serve a structural purpose. Heading proliferation, especially on listing/grid pages, can flood the screen reader heading navigation list and make it harder, not easier, to navigate. Consider whether some content sections need headings, or whether they should be structured with lists or paragraphs instead."},"severity":{"critical":"Critical","major":"Major","minor":"Minor"},"status":{"pass":"Pass","error":"Error","issuesFound":"Issues Found","done":"Done","errorBadge":"Error"},"filterIssues":{"issuesOnly":"Issues only","allUrls":"All URLs"},"trialRestriction":"Pro only, Upgrade to export","trialRestrictionTooltip":"Upgrade to Pro to export documents","networkError":"Network error, could not reach the server.","evidence":{"toolName":"Heading Analyser Pro (batch)","inputs":{"urlsScanned":"URLs scanned","urlsWithIssues":"URLs with issues","urlsFullyCompliant":"URLs fully compliant","urlsErrored":"URLs errored","totalHeadingsFound":"Total headings found","totalIssuesFound":"Total issues found"},"summary":"{scanned} URLs scanned, {compliant} fully compliant, {withIssues} with issues","sections":{"batchSummary":"Batch summary","urlsScanned":"URLs scanned","urlsFullyCompliant":"URLs fully compliant","urlsWithIssues":"URLs with issues","urlsErrored":"URLs errored","totalHeadingsExtracted":"Total headings extracted","totalIssuesFlagged":"Total issues flagged","criticalIssues":"Critical issues","majorIssues":"Major issues","minorIssues":"Minor issues","perUrlOverview":"Per-URL overview","perUrlHeaders":{"url":"URL","status":"Status","headings":"Headings","issues":"Issues","critical":"Critical","major":"Major","minor":"Minor"},"errorPrefix":"Error: {message}","unknownError":"Unknown","doneStatus":"Done","detailedFindings":"Detailed findings, URLs with issues","detailedFindingsBody":"For each URL below, every detected issue is shown with severity, WCAG mapping and remediation guidance. The full heading hierarchy as extracted is also listed for traceability.","findingsHeaders":{"severity":"Severity","type":"Type","issue":"Issue","wcag":"WCAG","remediation":"Remediation"},"hierarchyHeaders":{"index":"#","level":"Level","text":"Text"},"fullyCompliant":"Fully compliant URLs","fullyCompliantBody":"URLs below passed every heading-structure check. Heading hierarchies are listed for record.","erroredHeading":"URLs that errored during scan","erroredHeaders":{"url":"URL","error":"Error"},"unknownErrorRow":"Unknown error","method":"Method","methodBody":"Server-side fetch of each URL followed by extraction of all heading elements (H1–H6) in document order. Each page is checked for: missing H1, multiple H1s, skipped heading levels, empty headings, heading overuse, and absence of headings. Tested against WCAG 2.2 SC 1.3.1 (Info and Relationships), 2.4.6 (Headings and Labels), and 2.4.10 (Section Headings). Mapped to EN 301 549 V3.2.1 (2021-03) clauses 9.1.3.1, 9.2.4.6, 9.2.4.10. EAA Annex I §III.","emptyPlaceholder":"(empty)"},"formats":{"json":"Download as JSON","jsonHint":"All batch results"}}},"headings":{"meta":{"title":"Heading Structure Analyser","description":"Enter a URL and get a visual H1–H6 hierarchy tree. Spot skipped levels and missing H1s instantly."},"header":{"title":"Heading Structure Analyser","subtitle":"Visualise H1–H6 hierarchy, detect skipped levels, flag missing H1s, and score your document outline."},"howTo":{"step1Title":"Choose your input method","step1Body":"Select 'Scan URL' to fetch a live page (enter the full URL including https://), or 'Paste HTML' to analyse a snippet directly.","step2Title":"Run the scan","step2Body":"Click 'Analyse'. The tool fetches the page via a proxy and extracts all heading tags (H1–H6).","step3Title":"Read the tree","step3Body":"The indented hierarchy shows your heading structure. Red flags indicate problems: missing H1, skipped levels (e.g. H2 → H4), or empty headings.","step4Title":"Fix the issues","step4Body":"Each flagged heading shows the specific problem. Ensure you have exactly one H1 per page, and that levels increase by one at a time without skipping."},"modes":{"scanUrl":"Scan URL","pasteHtml":"Paste HTML"},"inputs":{"urlPlaceholder":"Https://example.com","htmlPlaceholder":"Paste HTML source here, the parser will extract all heading elements…","scanButton":"Scan URL","scanningButton":"Scanning…","parseButton":"Parse HTML"},"errors":{"prefix":"Error","noHeadingsInHtml":"No headings found in the pasted HTML."},"share":{"linkCopied":"Link copied!"},"scores":{"complianceScore":"Compliance Score","totalHeadings":"Total Headings","issuesFound":"Issues Found","pageType":"Page Type","levelsUsed":"Levels Used"},"dynamicWarning":{"title":"JavaScript-heavy page detected","body":"This page uses client-side rendering or dynamic content loading. The scan captured the HTML delivered by the server, headings injected by JavaScript after page load may not appear below. Results may be incomplete."},"issuesPanel":{"headingOne":"{count} Issue Detected","headingOther":"{count} Issues Detected"},"issues":{"title":"{count} Issue(s) Detected","whyIssue":"Why this is an issue","realWorldImpact":"Real-world impact","howToFix":"How to fix","regulationsViolated":"Regulations & criteria violated","noH1":{"message":"No H1 found on this page","fix":"Add exactly one <h1> element that clearly describes the page's main purpose. It should be the first and most prominent heading, think of it as the page's title.","why":"The H1 is the document's primary label. Screen readers announce it when a user first navigates to a page, and it is the first heading they encounter when jumping through landmarks. Without it, assistive technology has no authoritative description of what the page is about.","realWorld":"Imagine a blind user opening a tab and their screen reader reading nothing meaningful. They have to read every paragraph from the start to figure out whether they're on the right page. A missing H1 forces every screen reader user through that experience. It also harms SEO, as search engines use H1 as the strongest signal of page topic."},"multiH1":{"message":"{count} H1 headings found, only one is allowed","fix":"Demote all but the first H1 to H2 or H3. Each page should have exactly one H1 that describes the whole page. Use H2 for major sections and H3 for sub-sections within those.","why":"The H1 is the single page-level title. Multiple H1s create an ambiguous document structure that assistive technologies cannot reliably interpret. A screen reader user who asks 'what is this page?' expects one clear answer, not several competing ones.","realWorld":"Think of a book chapter that starts with three different chapter titles. The reader, and search engine, cannot know which one is correct. Screen reader users who navigate by heading ('jump to next H1') will land on unexpected content. It also signals to accessibility auditors that the page template was built without heading structure in mind."},"skip":{"message":"H{prev} → H{curr}: heading level skipped (missing H{missing})","fix":"Insert an H{missing} between the H{prev} and H{curr}, or restructure the content so that nesting increases by one level at a time. If the H{curr} visually looks like a sub-section, it should be H{missing}.","why":"Heading levels represent a document hierarchy, like chapters, sections, and sub-sections in a book. Skipping from H{prev} to H{curr} implies there is a level of content missing. Screen reader users who navigate by heading expect a predictable depth, and a jump of {jump} levels breaks that expectation.","realWorld":"A screen reader user is navigating a page by headings (a very common technique, equivalent to scanning a document's structure). They hear \"H{prev}: {prevText}\", then immediately hear \"H{curr}\". They instinctively assume they have missed a section. They go back, read more slowly, and eventually realise the structure is just broken, wasting their time and eroding trust. For a government or public service website this can mean failing an EAA audit."},"empty":{"message":"Empty H{level} at position {position}","fix":"Remove the empty heading element entirely, or add meaningful text that describes the content that follows it. Never use headings purely for visual spacing, use CSS margin/padding instead.","why":"An empty heading creates a navigation landmark with no label. Screen readers announce the heading level but read nothing. This is actively confusing, the user hears 'heading level 2' and expects content, but gets silence.","realWorld":"Developers sometimes use empty headings to create visual spacing or as layout placeholders. To a sighted user this is invisible. To a screen reader user, it sounds like a chapter that starts with a blank page. Automated accessibility scanners will flag this as a critical failure during an EAA or Section 508 compliance audit."},"trivial":{"message":"H{level} contains only punctuation or symbols: \"{text}\"","fix":"Replace the symbol-only text with a meaningful description of the section. If this is a visual divider, use an <hr> or CSS, not a heading element.","why":"Headings must describe the content that follows them. A heading containing only punctuation (e.g. '---', '***') conveys no information and will be read literally by screen readers as 'dash dash dash' or 'asterisk asterisk asterisk'.","realWorld":"A screen reader user navigating by headings hears 'Heading level 3: asterisk asterisk asterisk' and has no idea what content follows. It sounds like a bug or corrupted content. This also fails automated audits that check heading text quality."}},"duplicates":{"title":"Duplicate heading text detected","body":"The following heading texts appear more than once in the main content area. Duplicate headings can confuse screen reader users navigating by heading, each heading should uniquely identify its section."},"outline":{"title":"Document Outline","copyOutline":"Copy outline","copied":"Copied","share":"Share","emptyHeading":"Empty heading","chars":"Chars","showAll":"Show all {count} headings","showAllMain":"Show all {count} headings in main content"},"regions":{"mainContent":"Main Content","headerBanner":"Header / Banner","navigation":"Navigation","sidebar":"Sidebar","footer":"Footer"},"proUpsell":{"title":"Need Batch Analysis?","subtitle":"Pro: scan up to 50 URLs simultaneously and export a full CSV audit report."},"compliance":{"title":"Why heading structure is a legal requirement","whatItRequires":"What it requires","realWorldImpact":"Real-world impact","w3cGuidance":"W3C guidance →","screenReaderGuide":{"label":"How screen reader users navigate headings:","body":"Most screen reader users press the <hKey>H</hKey> key to jump between headings, or <numKey>1</numKey>–<numKey>6</numKey> to jump to a specific level. This is equivalent to scanning a table of contents. A page with a broken heading hierarchy forces users to either read every word linearly, or use trial-and-error navigation, both of which are significant barriers to access."},"sc131":{"criterion":"SC 1.3.1, Info and Relationships","level":"Level A, most fundamental requirement","summary":"The visual heading hierarchy must be conveyed programmatically, meaning it must exist in the HTML, not just look like a heading through CSS.","detail":"This is a Level A criterion, the most basic tier of WCAG compliance. It is required by every accessibility law globally, including the EAA, ADA, and Section 508. 'Programmatically conveyed' means using real <h1>–<h6> elements, not <div> or <span> styled to look like headings. A screen reader cannot detect visual styling, it reads the HTML structure. If your heading hierarchy exists only visually, it is invisible to assistive technology.","realWorld":"A marketing team might style a <div> in a large bold font to look like a heading. Sighted users see a heading. Screen reader users hear a paragraph. They cannot navigate to it using heading keys and do not know a new section has started. This is one of the most common accessibility failures found in EAA and WCAG audits."},"sc246":{"criterion":"SC 2.4.6, Headings and Labels","level":"Level AA, required by EAA, ADA, Section 508","summary":"Headings must describe the topic or purpose of the content that follows them, they cannot be vague, empty, or misleading.","detail":"SC 2.4.6 goes beyond just having headings in the right HTML elements, it requires them to be meaningful. A heading that says 'Section 1' or contains only punctuation fails this criterion even if the element is technically an <h2>. The heading must tell a user navigating by headings what they will find if they read further. This is the criterion that catches empty headings, symbol-only headings, and headings that do not describe their section.","realWorld":"A screen reader user navigating by headings is building a mental map of the page, like skimming a table of contents. If every heading says 'Read more' or 'Section', the map is useless. They have to read the full content of every section sequentially, which is exactly the barrier that heading navigation is designed to remove. EAA auditors will cite SC 2.4.6 when headings are present but not descriptive."},"sc2410":{"criterion":"SC 2.4.10, Section Headings","level":"Level AAA, best practice, not required by most laws","summary":"Section headings should be used to organise content, meaning content-heavy pages should use headings to break up and label sections.","detail":"This AAA criterion is not required by the EAA or ADA, but it represents the ideal. It means that even if headings are technically correct, a page that presents a wall of text without any heading structure is harder to navigate. Best practice for any content-heavy page is to use headings to divide content into labelled sections, so that users can orient themselves and jump to what they need.","realWorld":"A legal terms page with 5,000 words and no sub-headings is technically compliant at AA, but extremely difficult to navigate for screen reader users and users with cognitive disabilities. Adding H2 and H3 headings to organise sections (Delivery, Returns, Privacy) lets users jump directly to the relevant section rather than reading everything."}},"lawTags":{"eaaClause131":"EAA (EN 301 549 9.1.3.1)","eaaClause246":"EAA (EN 301 549 9.2.4.6)","adaWcag":"ADA WCAG 2.1 AA","section508":"Section 508","ukPsbar":"UK PSBAR","bestPractice":"Best practice","aaaTarget":"AAA target"},"evidence":{"toolName":"Heading Structure Analyser","toolDescription":"This assessment evaluates the heading hierarchy of a web page against WCAG 2.2 requirements. Screen reader users navigate pages using headings as signposts, a missing H1, skipped heading levels, or empty headings make pages unnavigable. Under the EAA, the programmatic heading structure must reflect the visual structure.","inputs":{"inputMode":"Input mode","source":"Source","headingsFound":"Headings found","landmarksDetected":"Landmarks detected","pageType":"Page type"},"values":{"urlScan":"URL scan","pastedHtml":"Pasted HTML","pastedHtmlSource":"(pasted HTML)","yes":"Yes","no":"No","notSet":"(not set)"},"summaryOne":"{count} heading analysed","summaryOther":"{count} headings analysed","duplicatesSuffixOne":"· {count} duplicate","duplicatesSuffixOther":"· {count} duplicates","sections":{"summary":"Summary","totalHeadings":"Total headings","h1Count":"H1 count","pageTypeDetected":"Page type detected","landmarksDetected":"Landmarks detected","issuesFlagged":"Issues flagged","duplicateHeadings":"Duplicate headings","unknown":"Unknown","issuesHeading":"Issues Requiring Attention","issuesIntroOne":"{count} structural issue detected. Each row shows the issue type, what's wrong, why it matters for screen reader users, and how to fix it.","issuesIntroOther":"{count} structural issues detected. Each row shows the issue type, what's wrong, why it matters for screen reader users, and how to fix it.","issuesTableHeaders":{"index":"#","type":"Type","issue":"Issue","fix":"Fix","why":"Why it matters"},"hierarchy":"Heading hierarchy","hierarchyHeaders":{"index":"#","level":"Level","text":"Text"},"byLandmark":"Headings by landmark","dynamicNotes":"Dynamic content notes","duplicates":"Duplicate headings flagged","duplicateItem":"\"{text}\", appears {count} times","method":"Method","methodBody":"Headings are extracted from the rendered HTML and reported in document order. Tested against WCAG 2.2 SC 1.3.1 (Info and Relationships), 2.4.6 (Headings and Labels), and 2.4.10 (Section Headings). Mapped to EN 301 549 V3.2.1 clauses 9.1.3.1, 9.2.4.6, 9.2.4.10.","emptyPlaceholder":"(empty)"},"formats":{"json":"Download as JSON","jsonHint":".json"},"scannedNote":"Scanned: {url}","nextStep":{"label":"Run Focus Order Visualiser","hint":"Test keyboard navigation on the same page"}},"proSection":{"badge":"Pro Feature","title":"Bulk Heading Audit","body":"Upload a sitemap to audit heading structure across up to {limit} URLs at once. Full CSV export with issue flags per page.","cta":"Unlock bulk audit →"}},"hospitality-checklist":{"meta":{"title":"Hospitality Accessibility Checklist, Booking, Accessible Rooms, On-Site Info","description":"Accessibility checklist for hotels, hostels and short-stay operators, covers booking flow, accessible-room availability disclosure, on-site amenities pages, menus and confirmation PDFs, and third-party booking-engine scope language. Mapped to WCAG 2.2, EN 301 549 and EAA Annex I & V."},"header":{"title":"Hospitality Accessibility Checklist","subtitle":"Booking flow · Accessible rooms · Amenities · Booking-engine scope"},"description":"Accessibility checklist for hotels, hostels and short-stay operators, covers booking flow, accessible-room availability disclosure, on-site amenities pages, menus and confirmation PDFs, and third-party booking-engine scope language. Mapped to WCAG 2.2, EN 301 549 and EAA Annex I & V.","features":{"f1":"18 checkpoints across booking, accessible-room disclosure, amenities, downloads and third-party scope","f2":"Maps each item to WCAG 2.2, EN 301 549 and the relevant EAA Annex I or Annex V provision","f3":"Pass / Partial / Fail / N/A with per-item notes","f4":"How-to-test guidance and common failures for every checkpoint","f5":"Links to relevant testing tools on AccessibilityRef","f6":"Progress auto-saved in your browser","f7":"Export Word report with notes","f8":"Print-ready view and blank Word download for offline workshops"},"categories":{"booking":{"label":"Online booking flow","description":"WCAG 1.3.1, 1.3.5, 2.4.7, 3.3.2, 3.3.7, the date picker, room selection, guest-details form and confirmation page must all be keyboard-operable with proper labelling and no redundant entry."},"rooms":{"label":"Accessible-room availability disclosure","description":"EAA Annex I §IV(g) + WCAG 1.1.1, 1.3.1, guests must be able to filter for accessible rooms, see per-room accessibility features, and read meaningful alt text on accessible-room photography."},"amenities":{"label":"On-site amenities & wayfinding pages","description":"WCAG 1.1.1, 1.3.1, 2.4.2 + Annex V scope, accessible parking, lift coverage, restaurant menus and activity booking must be accessible or accompanied by an alternative-format route."},"documents":{"label":"Document downloads","description":"EN 301 549 §10, booking confirmation PDFs and welcome packs need to be tagged or have accessible alternatives."},"thirdParty":{"label":"Third-party booking engine scope","description":"Annex V scope language, when the booking flow is hosted by a third party (Booking.com, Expedia, Hotelbeds, Cloudbeds, SiteMinder), the accessibility statement must name the vendor and describe the operator's monitoring process."}},"items":{"bk1":{"text":"Date picker is keyboard-operable.","guidance":"Check-in and check-out date pickers must be navigable with arrow keys and selectable with Enter or Space. Custom calendar widgets are a common failure point.","testMethod":"Put your mouse down. Tab to the check-in date field. Open the date picker with Enter or Space. Confirm you can move between days with arrow keys, between months with Page Up / Page Down or visible prev/next controls, and select a date with Enter. Repeat for check-out.","commonFailures":{"f1":"Date picker only opens on mouse click, Enter and Space do nothing","f2":"Days are styled divs that cannot receive keyboard focus","f3":"Calendar grid lacks ARIA grid semantics so screen reader announces a wall of numbers with no context","f4":"Selected date is shown only by background colour with no aria-selected or text indicator"}},"bk2":{"text":"Room-selection labels are not colour-only.","guidance":"Room categories must carry a text label, not only a coloured swatch or icon. WCAG 1.4.1 Use of Colour (Level A).","testMethod":"Look at the room-results listing. Confirm each room type, rate plan, and 'free cancellation' or 'non-refundable' indicator is conveyed by text, not by colour or icon alone. Test with a screen reader to verify the room category and conditions are announced.","commonFailures":{"f1":"'Free cancellation' is shown as a green dot with no text label","f2":"Rate categories are distinguished only by background colour","f3":"Discount tag is an icon-only badge with no accessible name","f4":"Soldout rooms are crossed out visually but flagged the same to AT as available rooms"}},"bk3":{"text":"Guest-details form: every input labelled, autocomplete set on standard fields.","guidance":"Name, email, address, phone and payment fields all need a visible <label>. Standard tokens (name, email, tel, address-line1, postal-code, cc-number) must be set on autocomplete. WCAG 1.3.5 Identify Input Purpose (Level AA).","testMethod":"Open the guest-details step and inspect each input in DevTools. Confirm a visible <label> is associated with each field (for-id or wrapping) and that autocomplete is set to the correct WHATWG token on every identifying field. Test with browser autofill, fields should populate from a saved profile.","commonFailures":{"f1":"Labels are only placeholders that disappear on focus","f2":"No autocomplete attribute on any field","f3":"Autocomplete='off' is set globally and defeats user autofill","f4":"Card-expiry month and year share a single label that does not identify each part"}},"bk4":{"text":"Don't ask for the same information twice, WCAG 2.2 SC 3.3.7 Redundant Entry.","guidance":"Information already collected (name, email, postcode) must not be requested again later in the same flow without pre-population or an explicit 'use same details' option.","testMethod":"Walk the whole booking flow as a fresh user. List every field on each step. Confirm that no field that was already entered is asked for again without pre-population or a clear 'reuse previous answer' control.","commonFailures":{"f1":"Billing address is re-asked on the payment step although shipping address was just entered","f2":"Email is asked twice, once for the account, once for the booking, with no pre-population","f3":"Phone is collected at registration and again for arrival confirmation, with no copy-across","f4":"Guest count is asked on step 1 and again on payment step, with re-entry forced"}},"bk5":{"text":"Confirmation page is keyboard-reachable and announces completion.","guidance":"When booking succeeds, focus should move to the confirmation heading or a status region with role='status' / aria-live='polite' so screen-reader users hear the outcome.","testMethod":"Complete a test booking with a screen reader running. Listen for an announcement after submission, booking number, dates, total. Inspect the DOM for a focused heading, role='status' wrapper, or aria-live region on the confirmation page.","commonFailures":{"f1":"Page changes but focus stays on the now-removed submit button","f2":"Confirmation message is added to the DOM with no aria-live wrapper","f3":"Confirmation is a separate page reached via redirect but focus jumps to <body> and the page title is unchanged","f4":"Success state shown only as a green checkmark with no text status"}},"rm1":{"text":"A filter or toggle for accessible rooms is visible in the search UI.","guidance":"Disabled guests must be able to search for accessible rooms directly in the room-results page, not via a hidden 'special requirements' modal or a phone call.","testMethod":"Run a search for any future date range. Look in the visible filter sidebar for a toggle, checkbox or chip that selects accessible rooms (wheelchair-accessible, step-free, etc.). Confirm it is keyboard-operable and that applying it returns appropriate results.","commonFailures":{"f1":"Only a 'call us for accessibility requirements' link is shown, no online filter","f2":"Accessible-room filter exists but is collapsed inside a 'special requirements' modal screen readers miss","f3":"Applying the filter returns 'no results' even when accessible rooms are available, the filter is wired to the wrong field","f4":"Filter is keyboard-reachable but its current state is not announced when toggled"}},"rm2":{"text":"Specific accessibility features per room are listed.","guidance":"List the actual features, roll-in shower, lowered bed height, hearing-loop in room, visual fire-alarm, fridge for medication, grab bars, accessible-route from car park. A generic 'accessible' tag is not enough.","testMethod":"Open the detail page of any accessible room. Confirm specific features are listed in text (not only in a photo). Confirm the list includes at least bathroom features, alerting features and circulation features. The room map or floor plan, if shown, has a text equivalent.","commonFailures":{"f1":"Room is marked 'accessible' with no detail on which features are present","f2":"Features are shown only as icons with no accessible names","f3":"Features are listed only in a downloadable PDF that itself is untagged","f4":"Room is labelled accessible but the actual feature mix (e.g. Roll-in vs. Lowered tub) is not stated"}},"rm3":{"text":"Photos of accessible rooms have alt text describing the accessibility feature.","guidance":"Alt text should describe what makes the room accessible, 'Bathroom with roll-in shower, grab bars and lowered sink', not just 'Hotel bathroom'.","testMethod":"Inspect each photo of an accessible room. Confirm the alt attribute describes the accessibility features visible in the image. A generic 'bathroom' or empty alt fails. Photos that exist purely for decor (lobby, restaurant) should not be the sole carrier of accessibility info.","commonFailures":{"f1":"Bathroom photo has alt='Bathroom', no mention of roll-in shower or grab bars","f2":"Photos are wrapped in <picture><img> with no alt at all","f3":"Photo gallery uses background-image CSS, so alt text cannot be applied","f4":"Photos are auto-uploaded with their filenames as alt, IMG_0421.jpg"}},"rm4":{"text":"'Contact for full accessibility details' route is published as text, not only a chat widget.","guidance":"Guests must be able to email or call a human about accessibility. A live-chat-only route excludes users who cannot use chat (deaf-blind users, users with no chat-compatible AT).","testMethod":"On the accessible-rooms page or the room detail page, look for an email address, phone number with text-relay support, or contact form for accessibility queries. Confirm the route is text-based, not gated behind a live-chat widget that itself may be inaccessible.","commonFailures":{"f1":"Only a live-chat 'pop-up' is offered for accessibility queries","f2":"Phone number is provided but no email or relay-friendly equivalent","f3":"Contact form has no fields for describing access requirements","f4":"Email address is provided as an image with no text equivalent"}},"am1":{"text":"Accessible parking spaces and distance to entrance are disclosed.","guidance":"Guests need to know in advance whether accessible parking is on-site, how far from the main entrance and step-free routes are. This is a practical accessibility detail beyond WCAG.","testMethod":"Look for a parking or 'getting here' page. Confirm it states the number of accessible spaces, their distance to the main entrance and whether the route between them is step-free. Compare with the on-site reality if possible.","commonFailures":{"f1":"Parking page mentions 'spaces available' without breakdown of accessible spaces","f2":"Distance to entrance is only shown on a non-accessible map image","f3":"Page states 'accessible parking on request' without explaining what 'on request' entails","f4":"Step-free route from car park to lobby is undocumented"}},"am2":{"text":"Lift / elevator coverage and maximum platform size are disclosed.","guidance":"Some floors may be reached only by stairs (e.g. Attic-style rooms). Lift platform dimensions matter for power-chair and large-wheelchair users.","testMethod":"Look for an on-site information page. Confirm it states which floors are lift-accessible and the maximum lift platform dimensions (W × D). If some rooms can only be reached by stairs, that is disclosed.","commonFailures":{"f1":"Page states 'lift available' but not which floors it serves","f2":"Lift platform dimensions are not disclosed anywhere","f3":"Photo of the lift is shown without dimensions","f4":"Page implies all floors are accessible when one wing is stairs-only"}},"am3":{"text":"Restaurant menu is accessible, text or accessible PDF, not menu-as-image.","guidance":"Restaurant menus published as images (PNG / JPG) or untagged PDFs cannot be read by screen readers, translated by browsers, or resized for low-vision guests.","testMethod":"Open the restaurant menu page. Try to select and copy a dish name. If it selects as text, the menu is text. If a rectangle is drawn around an image, it is an image and fails, unless the image has full text alt or an alternative format is offered.","commonFailures":{"f1":"Menu is a single image with no alt text","f2":"Menu PDF is an exported screenshot, not a tagged document","f3":"Allergen info is in a separate, untagged PDF","f4":"Menu changes daily but only one fixed photo is uploaded, current items not reflected"}},"am4":{"text":"Spa / activity booking flows are accessible OR an alternative-format contact route is published.","guidance":"If spa, gym, or activity bookings use a third-party widget, that widget must be accessible, or an alternative route (phone, email, text-relay) must be clearly published.","testMethod":"Try to book a spa or activity slot with keyboard only. If the widget fails, look for a clearly-signposted alternative route, phone, email, in-person at reception. Confirm the alternative does not rely on the same broken widget.","commonFailures":{"f1":"Spa booking is a third-party iframe that traps keyboard focus, with no alternative documented","f2":"Alternative is documented but only available during reception hours","f3":"Alternative is 'see reception on arrival', excludes pre-trip planning","f4":"Booking widget is accessible for the date picker but the time-slot grid is mouse-only"}},"dc1":{"text":"Booking confirmation PDFs are tagged (PDF/UA-1).","guidance":"The emailed confirmation PDF (or itinerary attachment) must be a tagged PDF so screen-reader users can read dates, room type, total and check-in instructions in order.","testMethod":"Buy a test booking and download the confirmation PDF. Open in Adobe Acrobat Pro and run the Accessibility Check, or upload to the Document Auditor on AccessibilityRef. Confirm the PDF is tagged, has a defined reading order, sets document language, and has alt text on any logos.","commonFailures":{"f1":"Confirmation is a flat image-only PDF with no text layer","f2":"Reading order interleaves header and footer with body content","f3":"Document language is not set, screen reader uses the wrong voice","f4":"QR / barcode is read as 'image' with no fallback text alternative"}},"dc2":{"text":"Welcome packs / room directories are accessible OR an alternative is offered.","guidance":"In-room directories explaining WiFi, breakfast hours, evacuation routes and amenities are often published as untagged PDFs. They must be tagged or an alternative format (large print, HTML page, audio file) offered.","testMethod":"Find the welcome pack on the website or in the room. If it is a PDF, run the Accessibility Check. If untagged, confirm a tagged version, HTML equivalent or audio version is also available and the alternative is publicised.","commonFailures":{"f1":"Welcome pack is an untagged InDesign-exported PDF","f2":"Evacuation map is published only as a photograph","f3":"Alternative format exists but is not signposted from the room or website","f4":"Pack is in English only with no signposting of translated or accessible versions"}},"tp1":{"text":"If the booking flow is third-party-hosted, the Annex V scope statement names the vendor.","guidance":"When booking is embedded from Booking.com, Expedia, Hotelbeds, Cloudbeds, SiteMinder or similar, the accessibility statement must name the vendor, identify scoped paths and describe the operator's monitoring process.","testMethod":"Read the published accessibility statement. Confirm it names the booking-engine vendor, identifies the scoped paths (e.g. /book/, /reserve/), and describes how the operator monitors and escalates accessibility issues with the vendor.","commonFailures":{"f1":"Statement does not mention the booking engine at all","f2":"Statement refers to 'partner systems' generically without naming the vendor","f3":"Statement disclaims responsibility for the engine without describing any monitoring or escalation process","f4":"Vendor is named in cookie notice but not in the accessibility statement scope section"}},"tp2":{"text":"Vendor liaison process for accessibility issues is documented.","guidance":"Operators must have a documented process for escalating accessibility issues to their booking-engine vendor, even if the surface is out of scope, the operator's monitoring is in scope.","testMethod":"Ask the operator for the documented escalation route to the booking-engine vendor. The process should include a named contact at the vendor, an SLA for response, and a recorded log of issues raised and resolved. Confirm at least one real example exists.","commonFailures":{"f1":"No documented process, escalation is ad hoc and undocumented","f2":"Process exists but has never been used in practice","f3":"Process names a vendor contact who no longer works there","f4":"Issues are raised by email but no log or response SLA is tracked"}},"tp3":{"text":"Hotel's own pages (room descriptions, gallery, on-site info) remain the operator's responsibility regardless of booking-engine scope.","guidance":"Annex V scope language for third-party booking engines does not cover the operator's own marketing pages. Those must meet WCAG 2.2 AA in full, regardless of whether transactional pages are scoped out.","testMethod":"Walk through the hotel's own non-transactional pages, homepage, room gallery, dining, location. Run a quick scan (Site Scanner) and a keyboard + screen-reader sample. Confirm WCAG 2.2 AA, these pages are not exempted by the third-party scope clause.","commonFailures":{"f1":"Marketing pages have widespread alt-text gaps, defended by the third-party scope clause","f2":"Operator assumes the booking-engine carve-out covers their entire site","f3":"Gallery is keyboard-inaccessible despite being the operator's own code","f4":"Contact form on the operator's pages has unlabelled inputs"}}},"export":{"filename":"Hospitality-checklist","title":"HOSPITALITY ACCESSIBILITY CHECKLIST","subtitle":"Booking flow · Accessible rooms · Amenities · Booking-engine scope"},"links":{"eaaDirective":"EAA Directive 2019/882","en301549":"EN 301 549 V3.2.1"}},"legal-pack":{"meta":{"title":"Procurement Legal Pack","description":"Fourteen EAA and WCAG 2.2 aligned contract clauses for vendor agreements, MSAs, and public procurement, each with plain-English explanations and negotiation guidance."},"header":{"title":"Procurement Legal Pack","subtitle":"Fourteen EAA and WCAG 2.2 aligned contract clauses for vendor agreements, MSAs, and public procurement, each with plain-English explanations and negotiation guidance."},"disclaimer":{"title":"Not Legal Advice.","body":"These clauses are template references only and are not tailored to your specific jurisdiction, contract structure, or circumstances. They do not constitute legal advice. Always consult a qualified solicitor or legal counsel before incorporating any clause into a contract, particularly for public procurement or regulated industry contracts."},"howTo":{"title":"How to use this pack","step1Title":"1. Select your clauses","step1Body":"Start with all Essential clauses. Add Recommended clauses based on contract value and risk. Optional clauses apply to high-value or long-term relationships.","step2Title":"2. Read the guidance","step2Body":"Each clause includes a Purpose (what it does), Why It Matters (the legal and business rationale), How to Use (where and how to insert it), and Negotiation Tips (how to handle pushback).","step3Title":"3. Adapt and copy","step3Body":"Copy the verbatim clause text and adapt the bracketed variables [like this] to fit your specific contract. Share with your legal counsel before sending to a vendor.","severityNote":"Severity ratings indicate how critical each clause is for a standard vendor contract"},"severity":{"essential":"Essential","recommended":"Recommended","optional":"Optional"},"categories":{"all":"All","coreWarranties":"Core Warranties","acceptanceDelivery":"Acceptance & Delivery","vendorResponsibilities":"Vendor Responsibilities","oversightEnforcement":"Oversight & Enforcement","complianceDocumentation":"Compliance Documentation","publicProcurement":"Public Procurement","contentDocuments":"Content & Documents"},"clauseCard":{"showing":"Showing {filtered} of {total} clauses","whyItMatters":"Why It Matters","howToUse":"How to Use","negotiationTip":"Negotiation Tip","clauseText":"Clause Text","copyClause":"Copy Clause","copied":"Copied","bracketNote":"Bracketed values [like this] are variables to be populated or agreed during contract negotiation. All clause text is indicative template language only."},"export":{"docx":{"methodHeading":"Method","methodBody":"Procurement clause library aligned to EAA Annex I (functional accessibility requirements) and Annex V (conformity assessment). Each clause includes the verbatim contract text, plain-language purpose, why it matters under the EAA, how to use it in vendor agreements, and a negotiation tip. Severity tags: Essential (must-have for EAA-grade contracts), Recommended (best practice), Optional (sector-specific).","libraryHeading":"Library overview","rowActiveCategory":"Active category filter","rowClausesIncluded":"Clauses included","rowTotalClauses":"Total clauses in library","rowCategoriesRepresented":"Categories represented","valueAllCategories":"All categories","valueAll":"All","clausesHeading":"Clauses","rowCategory":"Category","rowSeverity":"Severity","rowPurpose":"Purpose"}},"clauseBodies":{"CONFORMANCE_WARRANTY":{"title":"Accessibility Conformance Warranty","purpose":"Establishes the minimum technical accessibility standard the vendor must meet for all deliverables, web content, software, and documents, under the contract.","why_it_matters":"Without a specific technical standard named in the contract, 'accessible' becomes whatever the vendor decides it means. Referencing WCAG 2.2 Level AA and EN 301 549 v3.2.1 ties the warranty to measurable, internationally recognised criteria. WCAG 2.2 AA is the threshold required by the EAA (via EN 301 549 Chapter 9) and the Web Accessibility Directive.","how_to_use":"Insert into the Warranties section of your Master Services Agreement or Statement of Work. Define 'deliverables' broadly to include software, web interfaces, mobile apps, documents, and any digital content the vendor produces. Consider adding a schedule that lists the specific chapters of EN 301 549 that apply (e.g., Chapter 9 for web, Chapter 11 for software, Chapter 8 for hardware).","negotiation_tip":"Vendors may push back by arguing WCAG 2.2 AA is 'aspirational'. Respond that it is normatively referenced in EN 301 549 v3.2.1, which is itself the technical standard cited in the EAA and public procurement rules. If the vendor cannot warrant WCAG 2.2 AA, request a written explanation and consider it a procurement risk."},"REMEDIATION_SLA":{"title":"Remediation Service Level Agreement","purpose":"Defines the timeframes within which the vendor must respond to, plan for, and resolve accessibility defects identified by the client or by audit after delivery.","why_it_matters":"A warranty is only as useful as its enforcement mechanism. Without remediation SLAs, a vendor can acknowledge accessibility defects and take months or years to fix them. The EAA and WAD impose compliance obligations on your organisation, a slow-moving vendor directly increases your regulatory exposure. Severity-tiered SLAs reflect the real-world impact of accessibility failures: a broken checkout form affects every disabled customer who tries to purchase.","how_to_use":"Define severity levels clearly in a Schedule to the agreement. 'Critical' should capture any defect that completely blocks a user from completing a primary task (e.g., cannot complete checkout, cannot log in). 'Major' should capture significant barriers (e.g., entire pages unlabelled for screen readers). 'Minor' should capture partial conformance failures that degrade but do not prevent use. The SLA clock should start from the date of written notification from the client.","negotiation_tip":"Vendors often want longer timelines (30, 60, 90 days for critical issues). Push back by framing this in terms of regulatory risk: if a disabled user cannot access a core service and you receive a complaint to the national enforcement body, you cannot tell the regulator that you are waiting for a vendor's 90-day remediation plan. A 10-business-day resolution timeline for Critical issues is a reasonable industry standard."},"ACR_REQUIREMENT":{"title":"Accessibility Conformance Report (ACR / VPAT)","purpose":"Requires the vendor to produce and maintain a structured, evidence-based report documenting how each deliverable meets or fails to meet each WCAG and EN 301 549 requirement.","why_it_matters":"An ACR (also called a VPAT, Voluntary Product Accessibility Template) is the industry-standard mechanism for evidencing accessibility conformance. It forces the vendor to go clause-by-clause through WCAG and EN 301 549 and state explicitly whether they conform, partially conform, or do not support each criterion. An ACR provided before acceptance gives the client a documented baseline for warranty claims. Without it, you have no written record of what the vendor claimed to comply with at the time of delivery.","how_to_use":"Specify the VPAT edition to use, the VPAT 2.5 WCAG edition is appropriate for most web and software deliverables. For products sold into the EU public sector, the VPAT EU edition (based on EN 301 549) is more appropriate. Require the ACR before formal acceptance, do not accept a deliverable without one. Request updated ACRs for major releases (not only the initial delivery).","negotiation_tip":"Some vendors will provide a self-completed ACR. Require that ACRs for critical systems be verified by an independent third-party accessibility auditor. A self-certified ACR is better than nothing, but a vendor with something to hide will rate themselves as 'Supports' across all criteria regardless of actual conformance."},"ACCEPTANCE_CRITERIA":{"title":"Accessibility Acceptance Criteria","purpose":"Prevents the client from being obligated to formally accept a deliverable that contains material accessibility failures, ensuring that accessibility conformance is a condition of completion and payment.","why_it_matters":"In many contracts, acceptance is tied to functional testing only, the software works as specified, so it is accepted. Accessibility failures are then treated as post-acceptance defects, which typically have weaker remediation obligations and longer timelines. Tying acceptance to accessibility conformance puts accessibility on the same footing as functional correctness: the software is not done until it is accessible.","how_to_use":"Insert into the Acceptance Testing or Delivery section of the contract. Define 'material accessibility failure', a useful definition is any WCAG 2.2 Level A or Level AA failure that (i) affects a primary user journey, (ii) is identified in the ACR as 'Does Not Support', or (iii) would constitute a breach of the EAA or WAD. Allow for a cure period during which the vendor must remediate before acceptance is refused.","negotiation_tip":"Vendors will often argue that a zero-defect acceptance test for accessibility is unreasonable. Counter that you are not requiring zero defects, you are requiring that Critical defects on primary journeys are resolved before acceptance. You can agree to accept with a remediation plan for Minor and Major defects, provided they are listed in the ACR and have committed timelines."},"NON_REGRESSION":{"title":"Non-Regression Obligation","purpose":"Prevents the vendor from introducing new accessibility failures in subsequent releases, updates, or patches after the initial deliverable has been accepted.","why_it_matters":"Accessibility is commonly treated as a one-off compliance exercise at initial delivery. In practice, new releases regularly introduce new barriers, a redesigned navigation component, a new third-party widget, a refactored form. Without a non-regression clause, each new release resets the starting position, and the client must renegotiate remediation every time. The non-regression obligation treats accessibility as an ongoing quality standard, not a point-in-time test.","how_to_use":"Pair with the ACR Requirement clause, require that each new major release is accompanied by an updated ACR. Define 'major release' to include any change that introduces new UI components, modifies existing accessible components, or replaces third-party integrations. Minor patches (security fixes, backend changes with no UI impact) can be exempt.","negotiation_tip":"Some vendors argue that non-regression is difficult to guarantee with agile development cycles. Agree to a process-based equivalent: the vendor must include automated accessibility testing in their CI/CD pipeline (e.g., Axe-core or Playwright Accessibility) and must run a manual check on modified user journeys for each release. Evidence of this process is a reasonable substitute for a blanket non-regression warranty."},"THIRD_PARTY_COMPONENTS":{"title":"Third-Party Component Accessibility Obligation","purpose":"Ensures that the vendor takes responsibility for the accessibility of third-party libraries, frameworks, plugins, and embedded widgets included in the deliverable, not just the code they write themselves.","why_it_matters":"Under the EAA and WCAG, the client (as the operator of the digital service) is responsible for the accessibility of everything on their digital properties, including third-party content they have commissioned or embedded. Vendors often use dozens of third-party components. Without this clause, a vendor can point to a failed component and say 'that's not our code'. The client is still the one facing enforcement action.","how_to_use":"Insert into the Vendor Obligations section. Specify that the vendor must evaluate the accessibility of all third-party components before inclusion and must not include components with known accessibility failures affecting primary user journeys. Require the vendor to disclose all third-party components used and their accessibility status in the ACR.","negotiation_tip":"Vendors may argue they cannot control third-party publishers. Accept a reasonable standard: the vendor must (a) select accessible alternatives where available, (b) disclose known failures, and (c) implement accessible wrappers or workarounds where the third-party component itself has deficiencies. The obligation is to make best efforts, disclose, and mitigate, not to guarantee the third-party publisher will fix their code."},"TRAINING_OBLIGATION":{"title":"Accessibility Training Obligation","purpose":"Requires the vendor to ensure that the personnel assigned to the contract have appropriate accessibility knowledge and training, so that accessibility is built in from the outset rather than bolted on at audit.","why_it_matters":"Most accessibility failures are not deliberate, they result from developers, designers, and content authors who have never been trained on WCAG requirements. A vendor who trains their team builds accessible products by default. A vendor who does not will produce inaccessible code and rely on post-hoc audits to identify failures. Training is the upstream intervention that reduces the frequency and severity of downstream defects.","how_to_use":"Specify the minimum training requirement, for example, that at least one team member per discipline (development, design, QA, content) must hold a recognised accessibility qualification (CPACC, WAS, ADS from IAAP, or equivalent). Alternatively, require that the vendor provide evidence of their internal accessibility training curriculum. This clause is particularly important for long-term development contracts.","negotiation_tip":"Vendors may argue that training requirements are intrusive. Frame this as a quality standard, not a compliance burden: you are entitled to know that the team building your product understands the technical requirements they are warranting. Request CVs or training evidence as part of the bid response rather than post-award."},"AUDIT_RIGHTS":{"title":"Client Audit Rights","purpose":"Reserves the client's right to commission an independent accessibility audit of deliverables at any time during the contract term, at the vendor's cost if material failures are discovered.","why_it_matters":"Self-completed ACRs are inherently limited as evidence of conformance. An independent audit provides an objective verification. Under the EAA, national market surveillance authorities can require organisations to demonstrate the accessibility of their digital services at any time. The ability to commission an independent audit, and to recover its cost from the vendor where failures are found, is a meaningful incentive for vendors to maintain genuine conformance.","how_to_use":"Specify the conditions under which the client may exercise audit rights: (a) following a written complaint from a user about accessibility; (b) following a formal request from a regulatory authority; or (c) on an annual basis as part of routine oversight. Define what 'material failures' means for the purpose of cost recovery, tying it to the ACR's conformance ratings or to WCAG Level A/AA violations on primary journeys is appropriate.","negotiation_tip":"Vendors will often argue for 'reasonable notice' provisions (e.g., 30 days' notice of an audit). This is acceptable for routine audits. However, ensure that following a regulatory inquiry or user complaint, you retain the right to commission an emergency audit with shorter notice. The vendor should not be entitled to remediate defects in anticipation of an announced audit."},"STEP_IN_RIGHTS":{"title":"Step-In Rights for Accessibility Remediation","purpose":"Gives the client the right to directly engage a third party to remediate accessibility failures at the vendor's cost, where the vendor fails to meet its remediation SLA or repeatedly fails to resolve identified defects.","why_it_matters":"Where a vendor is in breach of its remediation SLA and the client faces regulatory risk (an open enforcement case, a user complaint, or an imminent EAA compliance deadline), waiting for the vendor to remediate is not always commercially viable. Step-in rights give the client a mechanism to act unilaterally and recover costs, rather than being held hostage to a non-performing vendor.","how_to_use":"Ensure that step-in rights are triggered clearly, typically after the vendor has failed to meet a remediation SLA deadline and has been given a further [5] business day cure notice. The client should give written notice of the exercise of step-in rights and should keep detailed records of costs incurred. Step-in should not automatically terminate the contract but should be paired with rights to terminate for material breach.","negotiation_tip":"Vendors frequently resist step-in rights. A reasonable compromise is to require a formal escalation process before step-in can be exercised: (1) issue a remediation notification, (2) wait for the SLA period, (3) issue a step-in warning with a further cure period, (4) exercise step-in. This ensures good faith before the nuclear option is triggered."},"INDEMNIFICATION":{"title":"Indemnification for Accessibility Non-Compliance","purpose":"Requires the vendor to indemnify the client against losses, fines, legal costs, and regulatory penalties arising from the vendor's failure to deliver accessible products, including losses arising from enforcement action under the EAA or WAD.","why_it_matters":"Under the EAA, market surveillance authorities can impose financial penalties on operators of non-compliant services. If the non-compliance arises from a vendor's deliverable, the client should not bear those costs. An indemnification clause shifts the financial risk to the party in the best position to control it, the vendor who built the inaccessible product.","how_to_use":"Ensure the indemnification covers: regulatory fines and penalties, reasonable legal costs of defending enforcement actions, costs of providing accessible alternatives to affected users in the interim, and reputational management costs where a quantifiable financial impact can be demonstrated. Cap-and-collar provisions are normal in commercial contracts, negotiate a cap at least equivalent to the contract value.","negotiation_tip":"Vendors will often argue that they cannot be held liable for regulatory fines imposed on the client, as the client is the regulated entity. The counter-argument is that the fine arises from the vendor's breach of warranty, the vendor is the proximate cause. A well-drafted clause limits the indemnity to direct financial losses attributable to the vendor's specific breach, not all regulatory exposure the client faces."},"SUBCONTRACTOR_CASCADE":{"title":"Subcontractor Accessibility Cascade","purpose":"Requires the vendor to flow down its accessibility obligations to any subcontractors, freelancers, or sub-suppliers engaged to perform any part of the services, ensuring that accessibility obligations are not diluted through the supply chain.","why_it_matters":"Vendors frequently subcontract design, development, or content work. If the subcontract does not contain equivalent accessibility obligations, the vendor may be unable to enforce them, leaving the client exposed. Cascade clauses ensure that the entire delivery chain is bound by the same standards.","how_to_use":"Insert into the Subcontracting section of the contract. Require the vendor to provide evidence of equivalent accessibility clauses in its subcontracts upon request. The vendor remains primarily liable to the client regardless of any subcontract, the cascade clause does not dilute the vendor's direct obligations.","negotiation_tip":"Some vendors will argue that requiring accessibility warranties from all subcontractors (including small freelance developers) is disproportionate. A reasonable compromise is to require the cascade for subcontractors responsible for more than [20]% of the deliverable or for any subcontractor producing user interface components."},"ACCESSIBILITY_STATEMENT_OBLIGATION":{"title":"Accessibility Statement Obligation","purpose":"Requires the vendor to produce or assist the client in producing a compliant Accessibility Statement for any web or mobile application deliverable, a mandatory requirement under the WAD and good practice under the EAA.","why_it_matters":"The Web Accessibility Directive requires public sector bodies to publish an Accessibility Statement on every website and app. Even for private sector organisations, publishing an Accessibility Statement is evidence of good faith compliance under the EAA and a requirement of best practice accessibility governance. An Accessibility Statement produced without vendor input will lack the technical detail required, known issues, estimated resolution dates, and the results of conformance testing.","how_to_use":"Specify the format: the WAD model template (Commission Decision (EU) 2018/1523) is appropriate for public sector clients. Private sector clients can adapt it. Require the vendor to provide: a list of known non-conformances with estimated resolution dates, the date of the most recent accessibility review, the testing methodology used, and a contact route for users to report issues. Update requirements should be triggered by major releases.","negotiation_tip":"Vendors often provide generic accessibility statements that say 'partially conformant' without identifying specific issues. Require that the statement must specifically identify all known Level A and Level AA failures with their WCAG success criterion reference number and an estimated resolution date. A generic statement is not compliant with the WAD model template requirements."},"INCIDENT_NOTIFICATION":{"title":"Accessibility Incident Notification Obligation","purpose":"Requires the vendor to proactively notify the client if it discovers or becomes aware of a material accessibility failure in a live deliverable, rather than waiting for the client to discover it.","why_it_matters":"Vendors who discover accessibility defects through their own monitoring or testing have a commercial incentive to quietly fix them without disclosing the original failure. For the client, this removes the opportunity to assess the impact on users, update the Accessibility Statement, and consider whether a regulatory notification obligation has been triggered. Proactive notification is also essential if a user has already been affected, the client may have an obligation to communicate with affected users.","how_to_use":"Define the notification timeline, 48-72 hours from discovery for Critical defects affecting primary journeys; 10 business days for Major defects. Require the notification to include: the nature of the failure, the WCAG success criterion(a) affected, the user journeys impacted, the estimated number of users affected (if determinable), and the proposed remediation approach. Align with your organisation's wider incident notification processes.","negotiation_tip":"Vendors will argue that voluntary self-disclosure of defects could be used against them in enforcement proceedings. Reassure them that the notification is confidential and for internal governance purposes, it does not constitute an admission of liability. The more important point is that a client who discovers a defect via a user complaint or regulatory enquiry, when the vendor already knew about it, has a much stronger breach of contract case."},"TERMINATION_FOR_BREACH":{"title":"Termination for Persistent Accessibility Non-Compliance","purpose":"Provides the client with a right to terminate the contract (or specific statements of work) for cause, where the vendor persistently fails to meet its accessibility obligations despite being given reasonable opportunity to remedy.","why_it_matters":"Without a specific termination right, a client trapped in a long-term contract with a non-compliant vendor must either accept ongoing non-compliance or rely on general breach of contract remedies, which are uncertain and expensive. A specific termination right creates a credible deterrent and an exit mechanism that does not require litigation.","how_to_use":"Trigger conditions should be specific, e.g., two or more breaches of the Remediation SLA within any 12-month period, or a failure to provide a compliant ACR for three consecutive major releases. Include a cure period (e.g., 30 days) before the termination right crystallises. Ensure that termination for accessibility breach is paired with rights to recover wasted expenditure and transition costs.","negotiation_tip":"Vendors will argue that a termination right for accessibility breach is disproportionate to the nature of the obligation. Distinguish between a single minor defect (which should not trigger termination) and persistent, systemic non-compliance that demonstrates the vendor cannot deliver accessible products. Frame the clause as a remedy of last resort, after step-in and SLA escalation mechanisms have been exhausted."},"EN301549_PROCUREMENT":{"title":"EN 301 549 as Procurement Technical Specification","purpose":"Formally incorporates EN 301 549 v3.2.1 as the technical specification for accessibility in public procurement contracts, as required by EU public procurement rules and the Web Accessibility Directive.","why_it_matters":"EU Directive 2014/24/EU on public procurement, read together with the WAD and EAA, requires contracting authorities to specify EN 301 549 as the technical standard for accessibility in ICT tenders. Failure to reference EN 301 549 explicitly in the tender specification means the contract lacks a clear accessibility baseline, making it difficult to enforce warranty claims or reject non-conformant bids.","how_to_use":"Include in the Technical Specifications section of the ITT or RFP. Specify the applicable chapters of EN 301 549, Chapter 9 (web content), Chapter 10 (non-web documents), Chapter 11 (software), Chapter 12 (documentation and support services), and Chapter 8 (hardware) as applicable to the procurement. Require bidders to confirm compliance in their tender submission and provide evidence of how they intend to meet each chapter.","negotiation_tip":"In public procurement, EN 301 549 is not negotiable, it is a legal requirement. Contracting authorities should treat an inability to confirm EN 301 549 compliance as a disqualifying criterion, not a commercial risk to be managed. Bidders who cannot warrant EN 301 549 compliance are not capable of delivering a legally compliant deliverable."},"DOCUMENT_ACCESSIBILITY":{"title":"Delivered Document Accessibility Obligation","purpose":"Extends the accessibility warranty to documents delivered under the contract, reports, specifications, training materials, user guides, and other digital documents, not just software and web interfaces.","why_it_matters":"EN 301 549 Chapter 10 (Non-Web Documents) and the WAD require that documents delivered to users be accessible. PDFs produced without accessible tagging are inaccessible to screen readers, a pervasive failure in contractor deliverables. Many procurement contracts specify software accessibility but overlook the documents that accompany the software, including user manuals, training materials, and reports.","how_to_use":"Specify that all documents delivered in digital format must conform to: PDF/UA-1 (ISO 14289-1) where the format is PDF; accessible HTML where the document is published on the web; and EN 301 549 Chapter 10 generally. Require that document production tools used by the vendor (Microsoft Word, InDesign, etc.) are configured to export accessible outputs. User manuals and help documentation are particularly important.","negotiation_tip":"Vendors often argue that PDF accessibility is difficult to achieve for complex documents (multi-column layouts, complex tables, charts). Accept that PDF/UA compliance is the standard, but allow a process-based alternative where the vendor commits to: (a) providing an accessible HTML version alongside the PDF, and (b) ensuring all non-text content has text equivalents. Avoid accepting 'we can't make this accessible' as a response."}}},"matterhorn-checklist":{"meta":{"title":"Matterhorn Protocol, PDF/UA Compliance Checklist","description":"The Matterhorn Protocol defines 136 failure conditions grouped into 31 checkpoints for PDF/UA-1 compliance. This checklist covers the most critical checkpoints relevant to EAA compliance, tagged structure, reading order, alternative text, table markup, metadata, and font embedding."},"header":{"title":"Matterhorn Protocol, PDF/UA Compliance Checklist","subtitle":"ISO 14289-1 (PDF/UA-1) + EN 301 549 §10 + Matterhorn Protocol 1.1"},"description":"The Matterhorn Protocol defines 136 failure conditions grouped into 31 checkpoints for PDF/UA-1 compliance. This checklist covers the most critical checkpoints relevant to EAA compliance, tagged structure, reading order, alternative text, table markup, metadata, and font embedding. Use alongside the Document Auditor for a full PDF accessibility assessment.","headerLinks":{"eaaDirective":"EAA Directive 2019/882","en301549":"EN 301 549 V3.2.1","pdfua":"PDF/UA-1 (ISO 14289-1)"},"features":["Covers Matterhorn Protocol checkpoints §01–§31","25 checkpoints across structure, reading order, images, tables & metadata","Pass / Partial / Fail / N/A with notes per item","How-to-test guidance and common failures for every checkpoint","Maps Matterhorn failure conditions to EN 301 549 §10","Progress auto-saved in your browser","Export Word report with notes","Direct links to PDF/UA and EAA references"],"categories":{"structure-tags":{"label":"Document Structure & Tags","description":"Matterhorn §01–§06, Tagged structure, content containment, and heading hierarchy."},"reading-order":{"label":"Reading Order & Artifacts","description":"Matterhorn §07–§09, Logical reading sequence, artifact handling, and tab order."},"images-alternatives":{"label":"Images & Alternative Text","description":"Matterhorn §13–§14, Figure tags, alt text, and images of text."},"tables-lists":{"label":"Tables & Lists","description":"Matterhorn §15–§19, Table header cells, scope, merged cells, and list structure."},"metadata-fonts":{"label":"Metadata, Language & Fonts","description":"Matterhorn §26–§31, Document title, language declarations, font embedding, and PDF/UA identifier."}},"items":{"mp1":{"text":"Document is a tagged PDF.","guidance":"The PDF must have its 'Tagged' flag set to true in the document catalog. Without tagging, assistive technologies cannot interpret the document structure at all."},"mp2":{"text":"All content is contained within the structure tree.","guidance":"Every piece of meaningful content (text, images, form fields) must be inside a structure element in the tag tree. Content outside the tag tree is invisible to assistive technologies."},"mp3":{"text":"Correct tag nesting, P tags inside Section, not inside Table.","guidance":"The structure tree must follow logical nesting rules defined by PDF/UA. Paragraph tags belong inside Section or similar grouping elements, never directly inside Table or Table Row elements."},"mp4":{"text":"No content exists outside the tag structure (orphan content).","guidance":"Content that is neither tagged nor marked as an Artifact is 'orphan content'. All content must be explicitly assigned: meaningful content gets tagged, decorative content gets marked as Artifact."},"mp5":{"text":"Heading tags (H1–H6) reflect the document's logical hierarchy.","guidance":"The heading structure in the tag tree must mirror the document's logical outline. Headings must not skip levels. Numbered heading tags (H1–H6) are preferred over the generic H tag."},"mp6":{"text":"Reading order in the tag tree matches the intended visual layout.","guidance":"The order of elements in the tag tree determines the order in which a screen reader will read the content. Multi-column layouts are particularly prone to reading-order errors."},"mp7":{"text":"Decorative elements are marked as Artifact (not tagged as content).","guidance":"Decorative borders, background images, watermarks, and purely visual elements must be marked as Artifacts so assistive technologies ignore them."},"mp8":{"text":"Page numbers, headers, and footers are marked as Artifact.","guidance":"Running headers, footers, and page numbers are repeated on every page and should be marked as Artifacts. If tagged as content, screen readers will read them between every page."},"mp9":{"text":"No empty tags exist in the structure tree.","guidance":"Empty structure elements serve no purpose and can cause unexpected pauses or blank announcements in screen readers."},"mp10":{"text":"Tab order follows the document's structure tag order.","guidance":"When a user presses Tab to navigate between interactive elements, the focus order must follow the logical structure defined by the tag tree."},"mp11":{"text":"All Figure tags have alternative text (Alt attribute).","guidance":"Every image tagged as a Figure element must have an Alt attribute containing a concise text description."},"mp12":{"text":"Decorative images are marked as Artifacts, not tagged as Figures.","guidance":"Images that serve no informational purpose must be marked as Artifacts. Tagging them as Figure elements forces screen reader users to listen to meaningless descriptions."},"mp13":{"text":"Complex images have a long description or associated accessible content.","guidance":"Charts, diagrams, infographics require more than a brief Alt attribute. Provide a long description, a linked accessible data table, or a dedicated description section."},"mp14":{"text":"Images of text are replaced with real text wherever possible.","guidance":"Text rendered as an image cannot be resized, recoloured, or read reliably by screen readers. Unless essential (e.g., a logo), text content must be real tagged text."},"mp15":{"text":"Alternative text is meaningful, not a filename or placeholder.","guidance":"Alt text must convey the purpose and content of the image in context. Filenames, generic labels like 'image' or 'photo', and auto-generated text are not meaningful alternatives."},"mp16":{"text":"Tables use TH (header) and TD (data) cells correctly.","guidance":"Data tables must distinguish header cells (TH) from data cells (TD). Without this distinction, screen readers cannot announce column or row headers when navigating the table."},"mp17":{"text":"Header cells have a Scope attribute indicating column or row.","guidance":"Each TH cell should have a Scope attribute set to 'Column', 'Row', or 'Both' to explicitly define which data cells it labels."},"mp18":{"text":"Merged cells use the Headers attribute to reference their header cells.","guidance":"When table cells span multiple rows or columns, merged data cells must use the Headers attribute to explicitly associate them with the correct headers."},"mp19":{"text":"Lists use L, LI, Lbl, and LBody tags in correct structure.","guidance":"Ordered and unordered lists must use the standard PDF list tags. Using P tags with bullet characters instead of proper list tags prevents screen readers from identifying the content as a list."},"mp20":{"text":"Nested tables are avoided, flat table structure preferred.","guidance":"Tables nested inside other table cells create extremely complex structures that are very difficult for screen readers to navigate."},"mp21":{"text":"Document title is set in metadata (not displaying filename as title).","guidance":"The PDF must have a descriptive Title field in its metadata, and the Initial View settings must display the document title, not the filename."},"mp22":{"text":"Language is declared at the document level.","guidance":"The PDF must have a Lang attribute set at the document level specifying the primary language. Without this, screen readers cannot select the correct text-to-speech voice."},"mp23":{"text":"Language changes are marked on individual content spans.","guidance":"When a document contains passages in a different language from the document-level language, those spans must be tagged with their own Lang attribute."},"mp24":{"text":"All fonts are embedded, no system font reliance.","guidance":"Every font used in the PDF must be fully embedded or subset-embedded. If a font is not embedded, the PDF viewer substitutes a different font, which can alter character mapping."},"mp25":{"text":"PDF/UA identifier is present in XMP metadata.","guidance":"A PDF/UA-compliant document must declare its conformance by including the PDF/UA identifier (pdfuaid:part = 1) in the XMP metadata stream."}},"export":{"filename":"Matterhorn-protocol","title":"MATTERHORN PROTOCOL PDF/UA","subtitle":"ISO 14289-1 Compliance Checklist"}},"media-accessibility":{"meta":{"title":"Media Accessibility, Video & Audio Compliance Tools","description":"Compliance tools for video, audio, and time-based media: comprehensive WCAG 2.2 / EAA Annex I §III checklist, plus an AI Content Warning Generator for flashing / seizure / sensitive content disclaimers (WCAG 2.3.1)."},"tabs_aria":"Media accessibility modes","tab_checklist":"Checklist","tab_warning":"Content Warning Generator","warning":{"heading":"Generate a content warning","lede":"Describe the content (a video, an audio clip, an interactive scene). The AI drafts a warning string and rates severity per WCAG 2.3.1 and EAA Annex I §III. Free for signed-in users, unlimited.","input_label":"Describe the content","input_placeholder":"e.g. 30-second clip with rapid camera flashes during a chase sequence","audience_label":"Audience","audience_general":"General","audience_children":"Children","audience_neurodivergent":"Neurodivergent","audience_epilepsy":"Epilepsy-aware","submit":"Generate warning","submitting":"Drafting…","section_warning":"Drafted warning","section_severity":"Severity","section_wcag":"WCAG criteria","section_eaa":"EAA reference","section_reasoning":"Why this severity","review_warning":"Always review before publishing. AI cannot watch your actual content; severity is heuristic from your description.","auth_required":"Sign in to use the AI generator.","quota_exhausted_pro":"Pro daily cap reached. Come back tomorrow.","error_generic":"Generation failed. Please try a clearer description."}},"metrics-dashboard":{"meta":{"toolId":"Metrics-dashboard","title":"Accessibility Metrics Dashboard","description":"Track accessibility metrics and compliance scores over time. Pro EAA self-assessment dashboard for WCAG 2.2 and EN 301 549 monitoring."},"badge":"Pro Tool","title":"Accessibility Metrics Dashboard","description":"Track accessibility health over time. Run periodic scans and see whether your score is improving or regressing.","descriptionLoggedIn":"Scan history is synced to your account.","descriptionLoggedOut":"Scan history is stored in your browser.","syncStatus":{"syncing":"Syncing…","synced":"Synced to cloud"},"proGateFeatures":["Track accessibility scores over time with historical trend charts","Run periodic scans and see whether you're improving or regressing","Compare scores across multiple URLs in one dashboard","Export metrics history as CSV for stakeholder reporting"],"howToUse":{"heading":"How to use this tool","steps":["Enter a URL and click <strong>Run scan</strong>. The tool runs 24 accessibility checks across 9 categories.","Run the same URL weekly or after each deployment to track score changes over time.","The score (0–100) is based on 24 WCAG 2.2-aligned checks: page setup, headings, landmarks, images, forms, links, keyboard, media, and structure.","A rising score indicates remediation is working. A falling score means regressions have been introduced.","Download CSV at any time for board reports or compliance documentation — all 24 checks are included as columns.","Scan history is synced to your account and accessible across devices. It is also stored locally as a fallback."]},"input":{"placeholder":"Https://yoursite.com/page","scanButton":"Run scan →","scanning":"Scanning…"},"stats":{"totalScans":"Total scans","urlsTracked":"URLs tracked","latestScore":"Latest automated scan score","avgScore":"Avg scan score"},"sections":{"trackedUrls":"Tracked URLs","scoreTrend":"Score trend","latestScan":"Latest scan","passed":"Passed","failed":"Failed"},"categories":{"pageSetup":"Page Setup","headings":"Headings","landmarks":"Landmarks","images":"Images","forms":"Forms","links":"Links","keyboard":"Keyboard","media":"Media","structure":"Structure"},"checks":{"hasTitle":"Page has a title","hasLang":"HTML lang attribute present","hasViewport":"Viewport meta tag present","isHttps":"Served over HTTPS","exactlyOneH1":"Exactly one H1 heading","noSkippedLevels":"No skipped heading levels","noDuplicateHeadings":"No duplicate heading text","hasH2s":"At least one H2 heading","hasMain":"Main landmark present","hasNav":"Nav landmark present","hasSkipLink":"Skip navigation link present","multipleNavLabelled":"Multiple navs have distinct labels","noMissingAlt":"No images with missing alt","noSuspiciousAlt":"No filename/suspicious alt text","altCoverageHigh":"Alt text coverage ≥ 90%","noTooShortAlt":"No alt text under 5 characters","allFormInputsLabelled":"All form inputs have labels","noEmptyButtons":"No empty buttons","noEmptyLinks":"No empty links","noGenericLinks":"No generic link text (click here…)","noPositiveTabindex":"No positive tabindex values","noAutoplay":"No autoplaying media","noLayoutTables":"No layout tables","noBlinking":"No blinking or marquee elements"},"actions":{"downloadCsv":"Download CSV →","clearHistory":"Clear history"},"empty":"No scans yet. Enter a URL above and click Run scan to start tracking.","bulk":{"title":"Bulk Site Metrics Audit","subtitle":"Upload a sitemap to get a full accessibility score for every page on your site","columns":{"score":"Score","passed":"Passed","failed":"Failed"}},"bulkCheckLabels":{"hasTitle":"Missing page title","hasLang":"Missing HTML lang","exactlyOneH1":"H1 issues","noSkippedLevels":"Skipped heading levels","noDuplicateHeadings":"Duplicate headings","hasH2s":"No H2 headings","hasMain":"No <main> landmark","hasNav":"No <nav> landmark","hasSkipLink":"No skip link","noMissingAlt":"Images missing alt","noSuspiciousAlt":"Suspicious alt text","allFormInputsLabelled":"Unlabelled form inputs","noEmptyButtons":"Empty buttons","noEmptyLinks":"Empty links","noGenericLinks":"Generic link text","hasViewport":"Missing viewport meta","isHttps":"Not HTTPS","noPositiveTabindex":"Positive tabindex","noAutoplay":"Autoplaying media","noLayoutTables":"Layout tables"},"export":{"docx":{"methodHeading":"Method","methodBody":"Each scan runs a 24-check static-DOM benchmark covering page setup, headings, landmarks, images, forms, links, keyboard, media and structural concerns mapped to WCAG 2.2 success criteria (SC 1.1.1, 1.3.1, 1.3.6, 1.4.2, 1.4.4, 2.2.2, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.6, 3.1.1, 3.3.2, 4.1.2). Results are persisted in the user's browser and — for Pro accounts — mirrored to Firestore for trending across audits.","latestScanHeading":"Latest scan","rowUrl":"URL","rowDate":"Date","rowOverallScore":"Overall score","rowChecksPassing":"Checks passing","rowChecksFailing":"Checks failing","rowTrendVsPrevious":"Trend vs previous scan","valuePassingFraction":"{passing} of {total}","valuePlusPoints":"+{delta} pts","valueMinusPoints":"{delta} pts","valueNoChange":"No change","valueSingleScan":"N/A (single scan)","perCheckHeading":"Latest scan — per-check result","columnCategory":"Category","columnCheck":"Check","columnWcagSc":"WCAG SC","columnResult":"Result","resultPass":"Pass","resultFail":"Fail","resultDash":"—","failuresHeading":"Latest scan — failures ({count})","failureLine":"{label} — SC {wcag} ({category})","historyHeadingOne":"Score history ({count} scan)","historyHeadingOther":"Score history ({count} scans)","columnHistoryDate":"Date","columnHistoryUrl":"URL","columnHistoryScore":"Score","columnHistoryPass":"Pass","columnHistoryFail":"Fail","valueScoreOutOf100":"{score}/100"}}},"mobile-app-checklist":{"meta":{"title":"Mobile App Accessibility Checklist, EN 301 549 + WCAG 2.2 AA","description":"EN 301 549 Chapter 11 + WCAG 2.2 AA compliance checklist, verify that your mobile application meets European Accessibility Act requirements."},"header":{"title":"Mobile App Accessibility Checklist","subtitle":"EN 301 549 Chapter 11 + WCAG 2.2 AA for Native Mobile Apps"},"description":"EN 301 549 Chapter 11 + WCAG 2.2 AA compliance checklist, verify that your mobile application meets European Accessibility Act requirements. EN 301 549 V3.2.1 references WCAG 2.1; this checklist additionally covers the new WCAG 2.2 criteria (SC 2.4.11, 2.4.12, 2.4.13, 2.5.7, 2.5.8, 3.2.6, 3.3.7, 3.3.8, 3.3.9) which apply as best practice pending the next EN 301 549 update.","headerLinks":{"eaaDirective":"EAA Directive 2019/882","en301549":"EN 301 549 V3.2.1"},"features":["EN 301 549 Chapter 11 + WCAG 2.2 AA coverage (includes new 2.2 criteria)","20 checkpoints across screen readers, input, visual, notifications & auth","Pass / Partial / Fail / N/A with notes per item","How-to-test guidance and common failures for every checkpoint","Links to relevant testing tools on AccessibilityRef","Progress auto-saved in your browser","Export Word report with notes","Direct links to EAA Directive and EN 301 549"],"categories":{"screen-reader":{"label":"Screen Reader Compatibility","description":"EN 301 549 §11.1.1–§11.4, All UI elements must be accessible to platform screen readers (TalkBack, VoiceOver)."},"input":{"label":"Input & Gestures","description":"EN 301 549 §11.1.2, Touch gestures, input methods, and keyboard/switch control must be accessible."},"visual":{"label":"Visual Accessibility","description":"WCAG 1.3–1.4 applied to native mobile UI, colour contrast, text resizing, orientation."},"notifications":{"label":"Notifications & Feedback","description":"Alerts, haptics, and system notifications must be accessible through multiple sensory channels."},"auth":{"label":"Authentication & Sessions","description":"Login, biometrics, timeouts, and session management must be accessible."}},"items":{"sr1":{"text":"All interactive elements have accessible names exposed to the platform accessibility API.","guidance":"Every button, link, input, and control must have a programmatic name, via contentDescription (Android), accessibilityLabel (iOS), or visible text."},"sr2":{"text":"All interactive elements expose their role to assistive technology.","guidance":"Buttons must be announced as buttons, checkboxes as checkboxes, links as links. Use platform-native controls or set accessibilityRole explicitly."},"sr3":{"text":"State changes (expanded, selected, checked) are programmatically exposed.","guidance":"When a toggle changes, a dropdown expands, or a tab is selected, the screen reader must announce the new state automatically."},"sr4":{"text":"Focus follows a logical reading order matching visual layout.","guidance":"Screen reader swipe navigation must move through elements in a logical order, top to bottom, left to right."},"in1":{"text":"Every swipe, pinch, or multi-finger gesture has a single-tap or button alternative.","guidance":"Pinch-to-zoom must have +/- buttons. Swipe-to-delete must have an explicit Delete button. No functionality should require complex gestures exclusively."},"in2":{"text":"Touch targets meet minimum 44×44pt (iOS) / 48×48dp (Android) size.","guidance":"Small buttons cause motor accessibility failures. Measure rendered size on actual devices. Padding counts toward tap area."},"in3":{"text":"Full keyboard and switch control navigation works for all flows.","guidance":"External keyboard users and switch control users must be able to complete every task."},"in4":{"text":"No functionality relies on device motion (tilt, shake) without an alternative.","guidance":"Shake-to-undo must have a menu alternative. Tilt-to-scroll must have button controls."},"in5":{"text":"App respects platform accessibility preferences (bold text, reduce motion, increase contrast).","guidance":"When the OS has 'Reduce Motion' enabled, the app must reduce or remove animations. 'Bold Text' should affect app typography."},"v1":{"text":"Text colour contrast meets 4.5:1 ratio (3:1 for large text).","guidance":"Measure against all backgrounds including gradients and images."},"v2":{"text":"Non-text UI components (icons, borders, focus rings) meet 3:1 contrast.","guidance":"Button borders, input outlines, icon graphics, all must have sufficient contrast against their background."},"v3":{"text":"Text resizes up to 200% via system settings without loss of content.","guidance":"Enable system font scaling and verify all text scales correctly. No truncation, overlap, or content hidden by overflow."},"v4":{"text":"App works in both portrait and landscape unless one orientation is essential.","guidance":"Content should reflow for both orientations. Only lock orientation if the content genuinely requires it."},"v5":{"text":"Colour is not the only means of conveying information.","guidance":"Error states, status indicators, and selected states must use shape, text, or icons in addition to colour."},"n1":{"text":"Notifications are available in text form, not just sound or vibration.","guidance":"Push notifications must include readable text. Haptic-only or audio-only alerts exclude deaf and deafblind users."},"n2":{"text":"Haptic feedback has a non-haptic alternative.","guidance":"Users who cannot perceive vibration need visual or audio confirmation for haptic events."},"n3":{"text":"Status messages are announced by the screen reader without focus change.","guidance":"Toast messages, loading indicators, and form submission confirmations must use platform accessibility announcements."},"au1":{"text":"Biometric login (fingerprint, face) has a PIN/password fallback.","guidance":"Not all users can use biometrics. A non-biometric path must always exist."},"au2":{"text":"Session timeouts warn the user and allow extension.","guidance":"Display a warning at least 20 seconds before timeout. Allow the user to extend. Do not silently log out."},"au3":{"text":"Authentication does not require cognitive function tests (CAPTCHAs) without an accessible alternative.","guidance":"CAPTCHAs are barriers for many users. Use alternative verification methods."}},"export":{"filename":"Mobile-app-checklist","title":"MOBILE APP ACCESSIBILITY CHECKLIST","subtitle":"EN 301 549 Chapter 11 + WCAG 2.2 AA for Native Mobile Apps"}},"mobile-checker":{"meta":{"title":"Mobile Accessibility Checker","description":"Enter any URL to run an automated mobile accessibility audit, viewport, touch targets, images, forms, landmarks, and more."},"header":{"title":"Mobile Accessibility Checker","subtitle":"Enter a URL, the page is fetched with a mobile browser user-agent and audited across 6 accessibility categories. No screenshot required.","badge":"Pro Tool","iconLabel":"Mobile phone"},"inputs":{"urlLabel":"Page URL to audit","urlPlaceholder":"Https://example.com","urlNote":"The URL is fetched server-side using a mobile Safari user-agent (iPhone iOS 17). The page must be publicly accessible."},"actions":{"check":"Check","checking":"Checking…","unlockPro":"Unlock with Pro, €999/yr","seeIncluded":"See what's included in Pro"},"loading":{"fetchingPage":"Fetching page with mobile user-agent…","parsingHtml":"Parsing HTML structure…","checkingViewport":"Checking viewport and responsiveness…","analysingInteractive":"Analysing interactive elements…","checkingImages":"Checking images and alt text…","auditingForms":"Auditing forms and labels…","compilingReport":"Compiling report…"},"error":{"title":"Error","hint":"Make sure the URL is public and does not require login. Try adding https:// if you omitted the protocol."},"status":{"pass":"Pass","fail":"Fail","warning":"Warning","info":"Info"},"scores":{"excellent":"Excellent","good":"Good","needsWork":"Needs work","poor":"Poor","mobileScore":"Mobile Score","checksRun":"Checks run","passed":"Passed","failed":"Failed"},"report":{"auditedUrl":"Audited URL","filter":"Filter:","all":"All ({count})","fail":"Fail ({count})","warn":"Warn ({count})","pass":"Pass ({count})","allPass":"All pass","fails":"{count, plural, one {# fail} other {# fails}}","warns":"{count, plural, one {# warn} other {# warns}}","howToFix":"How to fix","andMore":"…and {count} more"},"categories":{"viewport":"Viewport","pageBasics":"Page Basics","images":"Images","interactiveElements":"Interactive Elements","forms":"Forms","mobileSpecific":"Mobile-Specific"},"auditInfo":{"title":"What this audit checks","automatedChecksTitle":"Automated checks (20 total)","automatedChecks":["Viewport meta tag and zoom settings","Page title and language","H1 presence and landmark structure","Skip navigation link","Image alt text (present / filename-style)","Button and link accessible names","Generic link text detection","Non-interactive elements with onclick","Positive tabindex values","Form label associations","Placeholder-only inputs","Auto-refresh, focus styles, reduced motion"],"limitationsTitle":"Limitations","limitations":["Client-rendered content (React/Vue/Angular SPAs) may not be captured, only the initial HTML is analysed","Colour contrast requires CSS rendering, not checked here; use the Contrast Checker tool","Actual touch target pixel sizes require a browser rendering engine","External CSS files are not downloaded or analysed","Pages behind login, paywalls, or bot protection cannot be checked"]},"bulkScan":{"title":"Bulk Mobile Accessibility Audit","subtitle":"Upload a sitemap to check mobile accessibility across your entire site"},"export":{"downloadJson":"Download JSON","downloadJsonHint":"Inputs + full report + notes","noScanYet":"No scan yet","noScanRunYet":"No scan run yet","summaryLine":"Score {score}, {passed} pass / {failed} fail / {warnings} warn across {total} checks","labels":{"websiteUrl":"Website URL","notSet":"(not set)","activeFilter":"Active status filter","filterAll":"All","overallScore":"Overall score","totalChecks":"Total checks","passed":"Passed","failed":"Failed","warnings":"Warnings","failRow":"Fail {n}: {category}"},"docx":{"summaryHeading":"Summary","rowScannedUrl":"Scanned URL","rowOverallScore":"Overall score","rowTotalChecks":"Total checks","rowPassed":"Passed","rowWarnings":"Warnings","rowFailed":"Failed","failingHeading":"Failing Checks","failingIntro":"{count, plural, one {# check failed.} other {# checks failed.}} Each row shows the check, the category, what's wrong, the WCAG criterion, and how to fix it.","colNum":"#","colCategory":"Category","colCheck":"Check","colDetail":"Detail","colWcag":"WCAG","colFix":"Fix","fixDash":",","affectedHeading":"Affected items, {checkTitle}","affectedIntro":"{count, plural, one {# element} other {# elements}} listed below with full locator context, each row tells you exactly where on the site the issue lives (e.g. \"Header Account dropdown, Login form\", \"Footer newsletter form\") and the identifying attributes a developer can grep for.","affectedColElement":"Element","affectedColAttrs":"Identifying attributes","affectedColLocation":"Location on page","affectedColHtml":"HTML snippet","affectedFallbackNone":"(none)","affectedFallbackUnknown":"(unknown)","warningsHeading":"Warnings","passingHeading":"Passing Checks","methodHeading":"Method","methodBody":"The page was fetched server-side and inspected for mobile-accessibility-specific signals: viewport meta, touch-target sizing (WCAG 2.5.5 / 2.5.8), text reflow at 320 CSS pixels (WCAG 1.4.10), and form-input ergonomics. Mapped to EN 301 549 V3.2.1 §11.2.1.1, §11.2.1.4, §11.2.1.10, and §11.5.2.5."}}},"monitoring":{"page":{"title":"Monitors","description":"Schedule recurring Whole-Site Scanner runs and get notified by email when something regresses.","existing":"Your monitors","empty":"No monitors yet. Create one to start watching a site.","settings":"Settings","runHistory":"Run history","noRuns":"No runs yet. The next cron tick will pick this monitor up.","backToList":"Back to monitors"},"actions":{"create":"Create monitor","save":"Save","cancel":"Cancel","edit":"Edit","delete":"Delete","deleteConfirm":"Delete this monitor and all its run history?","viewRuns":"View runs"},"fields":{"seedUrl":"Seed URL","cadence":"Cadence","emailNotify":"Notify me by email when drift is detected","lastRun":"Last run","status":"Status","startedAt":"Started","score":"Score","pagesChecked":"Pages checked"},"cadence":{"weekly":"Weekly","monthly":"Monthly","daily":"Daily"},"thresholds":{"title":"Alert thresholds","scoreDrop":"Average score drops by 10 points or more","newFailingPages":"A page goes from passing to failing","newCheckFailures":"A new check fails across 3 or more pages","statementRegression":"Statement verdict regresses to a lower-quality bucket","statementConsistencyMismatch":"A new statement-vs-scan mismatch appears"},"status":{"loading":"Loading monitors...","saving":"Saving...","queued":"Queued","running":"Running","ok":"OK","drift":"Drift","error":"Error","never":"Never","notFound":"Monitor not found."},"cta":{"monitorThisSite":"Monitor this site automatically","monitorThisSiteBody":"Run this scan every week and get an email when something regresses. Set thresholds for score drops, new failing pages, or statement verdict changes.","setUpMonitoring":"Set up monitoring"}},"multilingual-checklist":{"meta":{"title":"Multilingual Accessibility Checklist, WCAG 3.1 + EN 301 549","description":"Assess whether accessibility features work correctly across all supported languages. Covers screen reader pronunciation, language switching, RTL support, character encoding, translated alt text, and locale-specific content accessibility."},"header":{"title":"Multilingual Accessibility Checklist","subtitle":"WCAG 3.1 + EN 301 549 §9.3.1 + EAA Annex I, Language Accessibility"},"description":"Assess whether accessibility features work correctly across all supported languages. Covers screen reader pronunciation, language switching, RTL support, character encoding, translated alt text, and locale-specific content accessibility. Critical for products serving multiple EU member states.","headerLinks":{"eaaDirective":"EAA Directive 2019/882","en301549":"EN 301 549 V3.2.1"},"features":["WCAG 3.1 + EN 301 549 §9.3.1 language requirements coverage","20 checkpoints across language declaration, pronunciation, translation & RTL","Pass / Partial / Fail / N/A with notes per item","How-to-test guidance and common failures for every checkpoint","Links to relevant testing tools on AccessibilityRef","Progress auto-saved in your browser","Export Word report with notes","Direct links to EAA Directive and EN 301 549 clauses"],"categories":{"language-declaration":{"label":"Language Declaration & Switching","description":"Correct use of lang attributes, keyboard-accessible language pickers, and state preservation across language changes."},"screen-reader-pronunciation":{"label":"Screen Reader Pronunciation","description":"Ensure text-to-speech engines correctly handle content in each supported language, including proper names, numbers, dates, and abbreviations."},"translated-content":{"label":"Translated Accessibility Content","description":"Verify that all accessibility-critical content, alt text, labels, ARIA attributes, and status messages, is properly translated in every supported language."},"rtl-locale":{"label":"RTL & Locale Support","description":"Verify correct right-to-left layout, focus order, and locale-appropriate formatting for Arabic, Hebrew, and other RTL languages."}},"items":{"ml1":{"text":"HTML lang attribute matches the primary language of the page.","guidance":"Every page must declare its language via the lang attribute on the <html> element. Screen readers use this to load the correct pronunciation engine."},"ml2":{"text":"In-page language switches are marked with the appropriate lang attribute.","guidance":"When a passage or word appears in a different language from the surrounding content, it must be wrapped in an element with the correct lang attribute."},"ml3":{"text":"Language picker is fully keyboard accessible.","guidance":"The language selector must be operable with keyboard alone, focusable, activatable with Enter/Space, and navigable with arrow keys if it is a dropdown."},"ml4":{"text":"Language change preserves page position and form state.","guidance":"When a user switches language, they should remain on the same page at the same scroll position. Any form data entered should be preserved."},"ml5":{"text":"All supported languages have a complete accessibility statement.","guidance":"Each language variant of the site must have its own accessibility statement in that language, not just an English-only statement."},"ml6":{"text":"Text-to-speech engine correctly pronounces content in each supported language.","guidance":"Screen readers use the lang attribute to select the correct TTS voice. If the attribute is wrong or missing, words are pronounced using the wrong language's phonetic rules."},"ml7":{"text":"Proper names are marked with lang attribute where pronunciation differs.","guidance":"Names of people, places, and brands that originate from a different language should be marked with the appropriate lang attribute if their pronunciation differs."},"ml8":{"text":"Numbers and dates are read in the correct locale format by screen readers.","guidance":"1.234,56 in German vs 1,234.56 in English, screen readers must interpret the correct format."},"ml9":{"text":"Currency symbols are announced correctly per locale.","guidance":"Screen readers should announce '€50' as 'fifty euros' not 'euro sign five zero'."},"ml10":{"text":"Abbreviations are expanded correctly in each language.","guidance":"Abbreviations and acronyms should be expandable or defined on first use in each language. Use <abbr> with a title attribute containing the expansion in the correct language."},"ml11":{"text":"Alt text is translated for all supported languages, not just the primary language.","guidance":"Images need meaningful alt text in every language the site supports."},"ml12":{"text":"Form labels and error messages are fully translated in all languages.","guidance":"Users completing forms in their language must see labels, placeholders, validation messages, and error text in that language."},"ml13":{"text":"ARIA labels and descriptions are translated for all languages.","guidance":"Aria-label, aria-labelledby, aria-describedby, and aria-roledescription values must be in the user's language."},"ml14":{"text":"Skip link text is translated in all supported languages.","guidance":"The 'Skip to main content' link must be in the page language."},"ml15":{"text":"Status messages and live regions are translated in all languages.","guidance":"Dynamic status messages announced via aria-live regions must be in the user's language."},"ml16":{"text":"Dir=\"rtl\" is correctly set for Arabic and Hebrew content.","guidance":"Pages in RTL languages must have dir='rtl' on the <html> element. Mixed-direction content must use dir='ltr' on the embedded element."},"ml17":{"text":"Layout mirrors correctly for RTL languages.","guidance":"In RTL mode, the entire layout should mirror, sidebar moves to the right, navigation aligns right, directional icons flip."},"ml18":{"text":"Focus order follows RTL reading direction.","guidance":"In RTL layouts, keyboard Tab order must follow the visual right-to-left, top-to-bottom order."},"ml19":{"text":"Date and number formats are locale-appropriate.","guidance":"Dates and numbers must be formatted according to the user's locale. Use Intl.DateTimeFormat and Intl.NumberFormat for automatic locale handling."},"ml20":{"text":"Content does not break when translated text is longer than the original.","guidance":"German and Finnish translations are often 30-40% longer than English. UI elements must accommodate longer text without truncation or broken layouts."}},"export":{"filename":"Multilingual-accessibility","title":"MULTILINGUAL ACCESSIBILITY","subtitle":"Cross-Language Accessibility Compliance Checklist"}},"pdf-checklist":{"meta":{"title":"PDF Accessibility Checklist, EN 301 549 Chapter 10 / PDF/UA","description":"Full PDF accessibility checklist covering EN 301 549 Chapter 10 and PDF/UA (ISO 14289). Mark each check Pass, Fail, or N/A with inline guidance and fix instructions."},"header":{"title":"PDF Accessibility Checklist","subtitle":"{count} checks covering EN 301 549 Chapter 10 / PDF/UA (ISO 14289). Mark each check Pass, Fail, or N/A, guidance and fix instructions expand inline."},"categories":{"documentIdentity":"Document Identity","structureReadingOrder":"Structure & Reading Order","imagesNonText":"Images & Non-text Content","tables":"Tables","linksNavigation":"Links & Navigation","contrastVisual":"Contrast & Visual","forms":"Forms","other":"Other"},"categoryNames":{"documentIdentity":"Document Identity","structureReadingOrder":"Structure & Reading Order","imagesNonText":"Images & Non-text Content","tables":"Tables","linksNavigation":"Links & Navigation","contrastVisual":"Contrast & Visual","forms":"Forms","other":"Other"},"filters":{"allCategories":"All categories","allSeverity":"All severity","allStatuses":"All statuses","failuresOnly":"Failures only","passesOnly":"Passes only","naOnly":"N/A only","critical":"Critical","major":"Major","minor":"Minor"},"severities":{"critical":"Critical","major":"Major","minor":"Minor"},"statuses":{"pass":"Pass","fail":"Fail","na":"N/A","pending":"Pending","notAssessed":"Not Assessed"},"stats":{"total":"Total","passed":"Passed","failed":"Failed","na":"N/A","pending":"Pending","completion":"Completion","criticalFailures":"{count} critical failure{plural}, these must be resolved for EN 301 549 conformance.","checksShown":"{filtered} of {total} checks shown"},"actions":{"exportCsv":"Export CSV","reset":"Reset","proOnly":"Pro only, Upgrade to export","proOnlyTooltip":"Upgrade to Pro to export documents"},"labels":{"pass":"Pass","fail":"Fail","na":"N/A","severity":"Severity","wcag":"WCAG","standard":"Standard","detail":"Detail","howToFix":"How to fix","tool":"Tool","notes":"Notes…"},"aria":{"expandGuidance":"Expand guidance","collapseGuidance":"Collapse guidance"},"placeholders":{"notes":"Add audit notes…"},"wcagLabels":{"WCAG_2_4_2_A":"WCAG 2.4.2 Page Titled (Level A)","WCAG_3_1_1_A":"WCAG 3.1.1 Language of Page (Level A)","BEST_PRACTICE":"Best Practice","ISO_14289_1_6_7_11":"ISO 14289-1 (PDF/UA-1) §6.7.11","WCAG_1_3_1_A":"WCAG 1.3.1 Info and Relationships (Level A)","WCAG_1_3_2_A":"WCAG 1.3.2 Meaningful Sequence (Level A)","WCAG_1_3_1_2_4_6_AA":"WCAG 1.3.1 / 2.4.6 Headings and Labels (Level AA)","WCAG_1_3_1_LEVEL_A":"WCAG 1.3.1 (Level A)","WCAG_2_4_5_AA":"WCAG 2.4.5 Multiple Ways (Level AA)","WCAG_1_1_1_A":"WCAG 1.1.1 Non-text Content (Level A)","WCAG_1_1_1_LEVEL_A":"WCAG 1.1.1 (Level A)","WCAG_2_4_4_AA":"WCAG 2.4.4 Link Purpose In Context (Level AA)","WCAG_2_4_4_LEVEL_AA":"WCAG 2.4.4 (Level AA)","WCAG_1_4_3_AA":"WCAG 1.4.3 Contrast Minimum (Level AA)","WCAG_1_4_1_A":"WCAG 1.4.1 Use of Colour (Level A)","WCAG_1_4_5_AA":"WCAG 1.4.5 Images of Text (Level AA)","WCAG_1_3_1_4_1_2_A":"WCAG 1.3.1 / 4.1.2 Name, Role, Value (Level A)","WCAG_2_4_3_A":"WCAG 2.4.3 Focus Order (Level A)","WCAG_4_1_2_A":"WCAG 4.1.2 (Level A)"},"standards":{"EN_PDFUA_TITLE":"EN 301 549 §10.2.4.2 / PDF/UA §7.1","EN_PDFUA_LANGUAGE":"EN 301 549 §10.3.1.1 / PDF/UA §7.2","PDFUA_AUTHOR":"PDF/UA §7.1","PDFUA1_XMP":"PDF/UA-1 §6.7.11 / EN 301 549 §10","PDFUA1_DISPLAY_TITLE":"PDF/UA-1 §7.1 / EN 301 549 §10.2.4.2","EN_PDFUA_TAGGED":"EN 301 549 §10.1.3.1 / PDF/UA §7.3","EN_PDFUA_READING":"EN 301 549 §10.1.3.2 / PDF/UA §7.3","EN_PDFUA_HEADINGS":"EN 301 549 §10.1.3.1 / PDF/UA §7.3","EN_HEADING_HIERARCHY":"EN 301 549 §10.1.3.1","EN_LISTS":"EN 301 549 §10.1.3.1","EN_PDFUA_BOOKMARKS":"EN 301 549 §10.2.4.5 / PDF/UA §7.7","EN_PDFUA_ALT":"EN 301 549 §10.1.1.1 / PDF/UA §7.3","PDFUA_ARTIFACTS":"PDF/UA §7.3","EN_CHARTS":"EN 301 549 §10.1.1.1","EN_SCANNED":"EN 301 549 §10.1.1.1","EN_PDFUA_TABLE_HEADERS":"EN 301 549 §10.1.3.1 / PDF/UA §7.5","PDFUA_TABLE_CAPTION":"PDF/UA §7.5","EN_TABLE_LAYOUT":"EN 301 549 §10.1.3.1","EN_LINK_TEXT":"EN 301 549 §10.2.4.4","EN_URLS":"EN 301 549 §10.2.4.4","EN_CONTRAST":"EN 301 549 §10.1.4.3","EN_COLOUR_ALONE":"EN 301 549 §10.1.4.1","EN_TEXT_IMAGES":"EN 301 549 §10.1.4.5","EN_PDFUA_FORM_FIELDS":"EN 301 549 §10.1.3.1 / PDF/UA §7.4","EN_TAB_ORDER":"EN 301 549 §10.2.4.3","PDFUA_DISPLAY_TITLE":"PDF/UA §7.1","PDFUA_NO_SECURITY":"PDF/UA §7.6"},"tools":{"wordAcrobat":"Word / Acrobat","acrobatProVeraPDFPAC":"Acrobat Pro / veraPDF / PAC","acrobatPro":"Acrobat Pro","word":"Word","wordAcrobatPro":"Word / Acrobat Pro","contrastChecker":"Contrast Checker tool","wordPowerPointDesign":"Word / PowerPoint / design tool","wordInDesign":"Word / InDesign","acrobat":"Acrobat"},"checks":{"title":{"title":"Document title set in metadata","detail":"The document title must be set in the file's metadata (not just the first heading). Screen readers announce the title when the document is opened.","howToFix":"Word: File → Info → Properties → Title. Acrobat: File → Properties → Description → Title. Then 'Save as PDF' or export with accessibility tags enabled."},"language":{"title":"Primary language declared","detail":"The document's primary language must be specified so screen readers select the correct voice and pronunciation engine.","howToFix":"Word: Review → Language → Set Proofing Language → select language and tick 'Set as Default'. Acrobat: File → Properties → Advanced → Language."},"author":{"title":"Author and subject metadata present","detail":"Author and subject fields help cataloguing systems and assistive technologies describe the document to users. Recommended for official, public-facing documents.","howToFix":"Word: File → Info → Properties → fill Author and Comments. Acrobat: File → Properties → Description."},"xmp-pdfuaid":{"title":"PDF/UA-1 XMP identification metadata present","detail":"A PDF/UA-conforming document must contain an XMP metadata stream in the document catalog that includes the PDF/UA identification schema. The namespace must be declared as xmlns:pdfuaid='http://www.aiim.org/pdfua/ns/id/' and the element <pdfuaid:part>1</pdfuaid:part> must be present. Without this marker, the document cannot be declared PDF/UA-1 conformant even if it passes all other checks. The document title must appear in the XMP stream as <dc:title><rdf:Alt><rdf:li xml:lang=\"x-default\">...</rdf:li></rdf:Alt></dc:title>, not only in the Info dictionary.","howToFix":"In Acrobat Pro: File → Properties → Description → click 'Additional Metadata'. In the Advanced pane, add the PDF/UA schema manually, or use the 'Save As → PDF/UA' option if available in your Acrobat version. Alternatively, use PAC (PDF Accessibility Checker) or veraPDF to verify the XMP stream. From Word, use the 'Acrobat' ribbon → Create PDF → Preferences → Advanced Settings → Standards → choose PDF/UA-1."},"display-doc-title":{"title":"ViewerPreferences/DisplayDocTitle set to true","detail":"The PDF viewer preferences dictionary must set /DisplayDocTitle to true so that the title from the document's metadata (XMP <dc:title> or Info dictionary /Title) is displayed in the viewer's title bar, not the filename. Screen reader users rely on the window title to know which document they are working in.","howToFix":"In Acrobat Pro: File → Properties → Initial View → Window Options → check 'Show: Document Title'. Alternatively, use iText, Apache PDFBox, or a PDF processing library to set ViewerPreferences >> /DisplayDocTitle true in the document catalog."},"tagged":{"title":"Document is tagged (PDF tags present)","detail":"Tagged PDFs carry a logical structure tree (headings, paragraphs, lists, tables). Without tags, screen readers read content in arbitrary order or announce nothing useful.","howToFix":"Export from Word using 'Save as PDF' with 'Document structure tags for accessibility' enabled. In Acrobat: Tools → Accessibility → Add Tags to Document (automatic), then review with the Tags panel."},"reading-order":{"title":"Reading order matches visual layout","detail":"The tag tree order must match the intended reading sequence. Multi-column layouts, sidebars, and text boxes frequently have wrong reading order when exported naively from Word.","howToFix":"Acrobat: View → Show/Hide → Navigation Panes → Order. Drag items to the correct sequence. For complex layouts, use the 'Reading Order' tool (Tools → Accessibility) to repaint regions."},"headings":{"title":"Heading styles used (H1, H2, H3…)","detail":"Headings must use the built-in heading paragraph styles, not manually bolded/enlarged text. This ensures tags export as <H1>, <H2> etc. And screen reader users can navigate by heading.","howToFix":"In Word, use the Styles panel: Heading 1, Heading 2, etc. Do not simulate headings with bold + font-size changes. Re-export after applying styles."},"heading-hierarchy":{"title":"Heading levels are not skipped","detail":"Heading levels must be hierarchical: H1 → H2 → H3. Jumping from H1 to H3 implies a missing H2 section and confuses screen reader users navigating by heading.","howToFix":"Check the document's heading structure in Word's Navigation pane (View → Navigation Pane → Headings). Adjust styles so levels progress logically."},"lists":{"title":"Lists use proper list styles (not manual dashes)","detail":"Bullet points and numbered lists must use Word's List styles so they export as <L>, <LI> tags. Manual en-dashes or typed '1.' characters export as plain paragraphs, losing list semantics.","howToFix":"Select all list items → apply List Bullet or List Number from the Styles panel. Avoid typing bullets manually."},"bookmarks":{"title":"Bookmarks present for documents over 20 pages","detail":"PDF bookmarks (the navigation panel) are essential for long documents. Screen reader users use them to jump to sections, equivalent to a table of contents.","howToFix":"Word: if headings are correctly styled, bookmarks appear automatically in the exported PDF. Acrobat: View → Navigation Panes → Bookmarks → manually add if missing."},"alt-text":{"title":"All informative images have alt text","detail":"Every meaningful image must have a text alternative describing its purpose. Decorative images must be explicitly marked as artifacts (ignored by screen readers).","howToFix":"Word: right-click image → Edit Alt Text → write a description. For decorative images, tick 'Mark as decorative'. Then export to PDF."},"decorative-artifacts":{"title":"Decorative images marked as artifacts","detail":"Decorative images (dividers, backgrounds, ornamental shapes) must be tagged as Artifacts so screen readers skip them. If left as tagged figures without alt text, screen readers will announce the filename.","howToFix":"Word: right-click → Edit Alt Text → tick 'Mark as decorative'. Acrobat: Tags panel → find <Figure> → right-click → Change Tag to Artifact."},"charts":{"title":"Charts and diagrams have descriptive alt text or a text equivalent","detail":"Charts must either have detailed alt text describing the data shown, or be accompanied by a data table or text summary. Alt text like 'bar chart' is insufficient.","howToFix":"Write alt text that describes the key takeaway: 'Bar chart showing sales increased 40% from Q1 to Q4 2024, with Q3 the highest at €2.1M'. Include a data table below the chart where possible."},"scanned":{"title":"Document is not a scanned image (real text present)","detail":"PDFs created by scanning paper documents are images of text, they contain no selectable or readable text. Screen readers cannot read them at all.","howToFix":"Run OCR: Acrobat Pro: Tools → Scan & OCR → Recognise Text. After OCR, review the result carefully, OCR errors create garbled text. Tag the document after OCR."},"table-headers":{"title":"Tables have header rows/columns tagged as <TH>","detail":"Table header cells must be tagged as <TH> with a Scope attribute (Row or Column) so screen readers can associate data cells with their headers. Without this, screen readers read tables as a flat list of cells.","howToFix":"Word: select first row → Table Design → check 'Header Row'. In Acrobat's Tags panel, find <TR> → change header cells from <TD> to <TH> and set Scope via cell properties."},"table-caption":{"title":"Tables have a caption or accessible name","detail":"Complex data tables should have a caption (<Caption> tag) describing their purpose. This lets screen reader users decide whether to explore the table before entering it.","howToFix":"Word: above the table, add a heading or paragraph that describes it. In Acrobat, add a <Caption> child element to the <Table> tag."},"table-not-layout":{"title":"Tables are not used for visual layout only","detail":"Tables used purely for positioning content (like two-column layouts) must be marked as presentation/artifact tables, not data tables. Otherwise, screen readers announce them as data tables with confusing headers.","howToFix":"Replace layout tables with tabbed text or multi-column sections. If unavoidable, mark the table's <Table> tag as a <Table> without header rows and add role='presentation' in Acrobat's Tags panel."},"link-text":{"title":"Hyperlinks have descriptive text (not 'click here')","detail":"Link text must describe the destination or purpose. 'Click here', 'read more', and bare URLs are inaccessible, screen reader users navigate links out of context and need each link to be self-explanatory.","howToFix":"In Word, right-click link → Edit Hyperlink → change the display text to describe the destination, e.g. 'Download the 2024 Annual Report (PDF, 2.3 MB)'."},"urls-readable":{"title":"Full URLs in text are readable when spoken","detail":"Long raw URLs like https://example.com/2024/q4/report.pdf are read character-by-character by some screen readers. Prefer linked text over pasted URLs in body copy.","howToFix":"Replace displayed URLs with descriptive hyperlink text. Where a URL must be visible (printed materials), shorten it: use a URL shortener or a memorable redirect."},"contrast":{"title":"Text meets minimum contrast ratio (4.5:1 for normal, 3:1 for large)","detail":"All body text must have at least 4.5:1 contrast against its background. Large text (18pt+ or 14pt+ bold) requires 3:1. Light grey on white or yellow on white are common failures.","howToFix":"Test colours with the Contrast Checker tool. In Word/PowerPoint, change font or background colour until ratio passes. Avoid light grey for body text."},"colour-alone":{"title":"Colour is not used as the only visual means of conveying information","detail":"If a chart uses only colour to distinguish categories, or an error state is shown only in red, users with colour blindness cannot access that information. Supplement colour with patterns, labels, or icons.","howToFix":"Add labels directly to chart series. Use fill patterns (hatch, dot) alongside colours. For status indicators, use an icon or text label alongside the colour cue."},"text-images":{"title":"Text is not presented as images (unless logo or essential)","detail":"Screenshots or images containing text cannot be resized, zoomed, or read by screen readers. This is common with scanned forms, infographic headers, and pull quotes saved as images.","howToFix":"Re-create headers and pull quotes as real styled text. For infographics, provide a text equivalent below the image."},"form-fields":{"title":"Interactive form fields have accessible labels","detail":"PDF form fields created with Acrobat must have a Tooltip set, this is what screen readers announce when the field receives focus. Without it, users hear only the field type ('text field').","howToFix":"Acrobat: open the form (Tools → Prepare a Form). Right-click each field → Properties → General → Tooltip. Write a brief but complete label."},"tab-order":{"title":"Form tab order is logical","detail":"Keyboard and screen reader users Tab through form fields. If the tab order doesn't match the visual layout, users fill fields out of sequence and make errors.","howToFix":"Acrobat Pro: Tools → Prepare a Form → click the Tab Order button in the toolbar. Drag fields to match the visual reading order."},"display-title":{"title":"PDF opens showing the document title (not filename) in the title bar","detail":"If the PDF is configured to show 'Document Title' rather than 'Filename' in the title bar, screen readers can announce the document's proper title when it opens.","howToFix":"Acrobat: File → Properties → Initial View → Show: Document Title."},"no-security":{"title":"Security settings do not block assistive technologies","detail":"Some PDF security settings (DRM/encryption) block screen readers from reading the content. The standard requires that accessibility not be restricted by content protection.","howToFix":"Acrobat: File → Properties → Security → Security Method: Password Security → tick 'Enable copying of text, images, and other content' and 'Enable text access for screen reader devices'."}},"chapter10Note":{"label":"EN 301 549 Chapter 10, Non-web documents.","body":"Under the EAA, documents provided as part of a digital service (e.g. Invoices, bank statements, booking confirmations, product manuals) must be accessible. PDF/UA (ISO 14289-1) is the recognised technical standard. Documents failing Chapter 10 are a direct EAA non-conformity for service providers in scope."},"csv":{"headers":{"category":"Category","check":"Check","severity":"Severity","status":"Status","wcag":"WCAG","standard":"Standard","notes":"Notes"},"filename":"Pdf-accessibility-audit.csv"},"evidence":{"toolName":"PDF Accessibility Checklist (PDF/UA)","results":{"totalChecksAnswered":"Total checks answered","passed":"Passed","failed":"Failed","notApplicable":"Not applicable","pending":"Pending","criticalFailures":"Critical failures","completionScore":"Completion score"},"categoryStat":"{passed} pass / {failed} fail / {na} N/A","inputs":{"itemsChecked":"Items checked","passed":"Passed","failed":"Failed","notesAdded":"Notes added"},"summary":"{count, plural, =1 {# item answered} other {# items answered}}","docx":{"summary":"Summary","totalChecks":"Total checks","itemsAnswered":"Items answered","passed":"Passed","failed":"Failed","notApplicable":"Not applicable","pending":"Pending","criticalFailures":"Critical failures","completionScore":"Completion score","perCategoryBreakdown":"Per-category breakdown","perCategoryHeaders":{"category":"Category","total":"Total","passed":"Passed","failed":"Failed","na":"N/A","pending":"Pending"},"failedHeading":"Failed checks, required remediation","failedIntro":"{count, plural, =1 {# check marked as Fail.} other {# checks marked as Fail.}} Each row shows the issue, severity, WCAG criterion, how to fix, and operator notes.","failedHeaders":{"category":"Category","check":"Check","severity":"Severity","wcag":"WCAG","howToFix":"How to fix","notes":"Notes"},"fullChecklistHeading":"Full checklist, all items","fullChecklistIntro":"Every Chapter 10 / PDF/UA criterion considered, with the operator's status, WCAG mapping, EN 301 549 / PDF/UA clause and any notes.","fullChecklistHeaders":{"category":"Category","check":"Check","severity":"Severity","status":"Status","wcag":"WCAG","standard":"Standard","notes":"Notes"},"methodHeading":"Method","methodBody":"Manual conformance review of {count} PDF accessibility checks based on EN 301 549 V3.2.1 Chapter 10 (non-web documents) and ISO 14289-1 (PDF/UA-1). Covers WCAG 2.2 SC 1.1.1, 1.3.1, 1.3.2, 1.4.1, 1.4.3, 1.4.5, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 3.1.1, and 4.1.2. Maps to EAA Annex I accessibility requirements and ISO 14289-1 PDF/UA-1 clauses §6.7.11, §7.1–§7.7."},"formats":{"json":{"label":"Download as JSON","hint":"All statuses + notes"}}}},"provisional-assessment":{"meta":{"title":"Whole-Site Scanner","description":"A pre-audit accessibility check covering 50 guided questions across Perceivable, Operable, Understandable, Robust, and EAA/Legal categories. Includes site scanning and auto-fill. Returns a provisional conformance result before you commission a formal audit."},"header":{"title":"Whole-Site Scanner","subtitle":"Answer 50 questions across 5 categories to get a provisional conformance rating. Optionally scan your site to auto-fill technical checks.","badge":"Pro Tool"},"features":["50-question guided assessment across 5 WCAG and EAA categories","Weighted scoring: critical, major, and minor questions","Site scan with auto-fill for technical checks","Export to Word, professional report with scores and recommendations"],"categories":{"perceivable":"Perceivable","operable":"Operable","understandable":"Understandable","robust":"Robust","eaa":"EAA / Legal"},"answers":{"pass":"Pass","partial":"Partial","fail":"Fail","na":"N/A"},"weights":{"critical":"Critical","major":"Major","minor":"Minor"},"inputs":{"orgName":"Organisation name","orgPlaceholder":"Your company name"},"progress":{"answered":"{count} of {total} answered","answeredShort":"Answered","categoryProgress":"{answered}/{total}"},"scan":{"title":"Site Scan","subtitle":"Scan your site to auto-fill technical checks","urlPlaceholder":"Https://example.com","modes":{"crawl":"Crawl","upload":"Upload sitemap","sitemapUrl":"Sitemap URL"},"startScan":"Start scan","scanning":"Scanning…","discovering":"Discovering pages…","discovered":"{count} pages discovered","sampled":"{count} pages sampled","progress":"{percent}% complete","autoFilled":"Auto-filled from scan","overridden":"You overrode this value"},"scanResults":{"overview":"Overview","issues":"Issues","fixes":"Fixes","pages":"Pages","avgScore":"Average score","pagesChecked":"Pages checked","pagesErrored":"Pages errored","worstPages":"Lowest-scoring pages","failRate":"Fail rate"},"results":{"showResult":"Show result","provisionalAA":"Provisional AA","provisionalA":"Provisional A","developing":"Developing","nonConformant":"Non-Conformant","provisionalAADesc":"Your responses indicate likely WCAG 2.2 Level AA conformance. A professional audit is recommended to confirm.","provisionalADesc":"Your responses suggest partial conformance. Significant issues likely remain, professional review is advised.","developingDesc":"Meaningful accessibility gaps were identified. Remediation work is needed before conformance is achievable.","nonConformantDesc":"Significant accessibility failures were identified. Immediate remediation is required to meet EAA obligations.","score":"Score: {earned} / {max} ({percentage}%)"},"actions":{"exportWord":"Export to Word","exporting":"Exporting…","proOnlyExport":"Pro only, Upgrade to export"},"disclaimer":{"headline":"Provisional only.","body":"This self-assessment does not constitute a formal audit, professional opinion, or accessibility certification. Results reflect your own responses and have not been independently verified. A professional accessibility audit by a qualified auditor is required for formal conformance claims under the European Accessibility Act or EN 301 549.","eaaNote":"Self-assessment is explicitly recognised as part of the conformity assessment process under <strong>EAA Article 14 and Annex IV</strong>, economic operators are responsible for conducting their own assessment of conformity before placing a product on the market or providing a service. This tool supports that internal process. It does not replace independent verification or the formal technical documentation required under Article 20."},"explainer":{"summaryTitle":"How this tool works","summarySubtitle":"What it checks, how scoring works, and how to interpret your results","close":"Close ▲","open":"Read ▼","part1":{"title":"Part 1, Self-Assessment Questionnaire","p1":"The questionnaire contains <strong>50 checkpoints</strong> mapped to WCAG 2.2 success criteria and EAA/EN 301 549 provisions. They are grouped into five categories: <strong>Perceivable, Operable, Understandable, Robust,</strong> and <strong>EAA/Legal</strong>.","p2":"Each checkpoint is answered Pass / Partial / Fail / N/A. <strong>Pass</strong> means you have verified this requirement is met. <strong>Partial</strong> means it is partly met. <strong>Fail</strong> means it is not met. <strong>N/A</strong> means the checkpoint does not apply to your product (e.g. No video content).","p3":"N/A answers are excluded from scoring, they do not penalise or benefit your result."},"scoring":{"title":"Weighted Scoring","intro":"Each checkpoint carries a weight: <strong>Critical (3 pts), Major (2 pts), Minor (1 pt)</strong>. Critical items map to WCAG Level A failures that make content completely inaccessible to some users. Major items are Level AA compliance failures. Minor items are best-practice issues.","ranges":{"aa":{"range":"≥ 90%","label":"Provisional AA","desc":"Likely meets WCAG 2.2 Level AA. Professional audit recommended to confirm."},"a":{"range":"70–89%","label":"Provisional A","desc":"Partial conformance. Significant gaps remain, remediation advised."},"developing":{"range":"50–69%","label":"Developing","desc":"Meaningful accessibility gaps. Substantial remediation work needed."},"nonConformant":{"range":"< 50%","label":"Non-Conformant","desc":"Major failures present. Immediate remediation required for EAA compliance."}}},"part2":{"title":"Part 2, Automated Site Scan","p1":"The automated scan discovers pages on your site via <strong>sitemap.xml</strong> (or sitemap index files referenced in robots.txt). Sites with fewer than <strong>500 pages</strong> are scanned in full. For larger sites, the scanner takes a <strong>random 20% sample</strong>, capped at 2,000 pages. If you supply a sitemap URL or upload a sitemap file directly, every URL up to the mode cap (500 for sitemap URL, 5,000 for upload) is scanned without sampling.","p2":"Each sampled page is fetched and analysed against <strong>27 automated WCAG checks</strong>. These include: page title, language attribute, heading structure, landmark regions, alt text coverage, form labelling, link quality, HTTPS, autoplay media, layout tables, accessibility overlay detection, footer accessibility link, and EAA awareness signals.","p3":"Results are aggregated to show <strong>which checks fail most often across your site</strong> and which individual pages score lowest, giving your dev team a clear remediation priority list."},"limitations":{"title":"Limitations of automated scanning","intro":"Automated checks can only test what is measurable in the HTML source. They <strong>cannot test</strong>:","items":["Keyboard navigation and focus order","Screen reader compatibility and ARIA behaviour","Colour contrast of rendered CSS (only structural checks)","Cognitive load and plain language","Touch target sizes on mobile","Video captions and audio descriptions","Pages behind authentication","Dynamically rendered content (SPAs after JS execution)"],"footer":"This is why the self-assessment questionnaire exists, to capture what automated tools cannot. Use both parts together for the most complete picture."}},"scanPanel":{"title":"Automated Site Scan","subtitle":"Crawl your site, upload a sitemap, or enter a sitemap URL · 27 automated WCAG checks per page · crawl mode samples 20% of large sites (capped at 2,000)","open":"Open ▼","close":"Close ▲","modes":{"crawl":"↗ Crawl website","upload":"↑ Upload sitemap","sitemapUrl":"🔗 Sitemap URL"},"crawl":{"placeholder":"Https://your-website.com","invalidUrl":"Enter a full web address starting with https:// or http://","discovering":"Discovering pages…","scanning":"Scanning… {percent}%","cta":"Discover & Scan"},"upload":{"dropZoneTitle":"Drop your sitemap.xml here, or click to browse","dropZoneHint":"Accepts.xml files · up to {limit} URLs","fileLoaded":"{name}, {count} URLs loaded","scanCta":"Scan {count} pages","scanCtaEmpty":"Scan uploaded sitemap","scanningProgress":"Scanning… {percent}%","errors":{"notXml":"Please upload a.xml sitemap file.","noUrls":"No URLs found in this file. Make sure it is a valid sitemap.xml with <loc> entries.","indexFile":"This is a sitemap index file, it lists {count} child sitemap files, not individual pages. Download and upload one of the child sitemaps listed inside it, or use Crawl mode to auto-discover all sitemaps.","trimmed":"Sitemap contains {count} URLs, loaded the first {limit} for scanning.","invalidXml":"Could not parse that file as XML. Make sure it is a valid sitemap.xml."}},"sitemapUrl":{"intro":"Enter the direct URL of your sitemap.xml, e.g. <code>https://example.com/sitemap.xml</code>. Sitemap index files are supported (child sitemaps are fetched automatically).","placeholder":"Https://example.com/sitemap.xml","invalidUrl":"Enter a full URL starting with https:// or http://","loaded":"{count} URLs loaded from sitemap","fetching":"Fetching sitemap…","scanning":"Scanning… {percent}%","cta":"Fetch & Scan"},"newScan":"New scan","errors":{"scanFailed":"An unexpected error occurred during the scan.","sitemapFetchFailed":"An unexpected error occurred while fetching the sitemap.","discoveryFailed":"Discovery failed.","sitemapParseFailed":"Failed to fetch sitemap.","statementFetchFailed":"Statement fetch failed"},"discoveryInfo":{"discovered":"Pages discovered","sampled":"Sampled for checking","checked":"Pages checked so far"},"progress":{"label":"Scan progress"}},"scanLive":{"avgScoreCard":"Avg score / 100","pagesCheckedCard":"Pages checked","scoring80Plus":"Scoring 80+","scoringUnder50":"Scoring under 50","topIssues":"Top issues so far","passPctLabel":"{percent}% pass","pagesAffectedShort":"{count, plural, one {# page affected} other {# pages affected}}"},"tabs":{"overview":"Categories","issues":"All Issues","fixes":"Action Plan","pages":"Pages"},"statement":{"panelTitle":"Accessibility Statement Analysis","panelSubtitle":"Fetched and classified from the footer link on your site. Checks 11 EAA Art. 13 markers.","loading":"Fetching statement…","fetchError":"Statement fetch failed: {error}","markersHit":"{count} / 12 markers hit","jurisdictionLabel":"Jurisdiction: {code}","overlayDetected":"Overlay boilerplate detected:","overlayDetectedBody":"This statement was auto-generated by an overlay vendor and does not count as a real Art. 13 declaration.","sourceLabel":"Source:","verdicts":{"fullStatement":"Full Art. 13 statement","partialStatement":"Partial statement","marketingClaimOnly":"Marketing claim only","marketingOrNone":"No real statement","overlayBoilerplate":"Overlay-generated boilerplate","unknown":"Unknown"},"markers":{"conformityClaim":"Conformity claim","wcagRef":"WCAG reference","enRef":"EN 301 549","abLevel":"A / AA level","scope":"Scope stated","date":"Review date","feedback":"Feedback mechanism","feedbackKeyword":"Feedback channel mentioned","dedicatedA11yChannel":"Dedicated accessibility channel (email or form)","contactEmail":"Contact email","inaccessibleParts":"Inaccessible parts","art29":"Enforcement / complaints","arsEnti":"Regulator reference","nationalLawRef":"National law ({label})"},"nationalLawDefault":"National law"},"checkCategories":{"identity":"Page Identity","headings":"Heading Structure","images":"Images","links":"Links & Buttons","forms":"Forms","landmarks":"Landmarks & Navigation","technical":"Technical","eaa":"EAA / Legal"},"checkLabels":{"hasTitle":"Page title","hasLang":"HTML lang","hasViewport":"Viewport meta","isHttps":"HTTPS","exactlyOneH1":"Single H1","noSkippedLevels":"Heading levels","noDuplicateHeadings":"Duplicate headings","hasH2s":"Has H2s","noMissingAlt":"Missing alt text","noSuspiciousAlt":"Bad alt text","altCoverageHigh":"Alt coverage","altQualityHigh":"Alt text quality","noTooShortAlt":"Short alt text","noEmptyLinks":"Empty links","noGenericLinks":"Generic link text","noEmptyButtons":"Empty buttons","allFormInputsLabelled":"Form labels","hasMain":"Main landmark","hasNav":"Nav landmark","hasSkipLink":"Skip link","multipleNavLabelled":"Nav labels","noAutoplay":"Autoplay media","noPositiveTabindex":"Positive tabindex","noLayoutTables":"Layout tables","noBlinking":"Blinking content","noOverlay":"No overlay widget","hasA11yFooterLink":"A11y link in footer","hasEaaAwareness":"EAA awareness signals"},"checkRemediation":{"hasTitle":{"what":"Page is missing a <title> element.","how":"Add a unique, descriptive <title> to every page's <head>. Format: Page Name | Site Name. Keep under 60 characters."},"hasLang":{"what":"The <html> element has no lang attribute.","how":"Add a lang attribute to <html> using a valid BCP 47 language tag. Missing lang breaks screen reader pronunciation."},"hasViewport":{"what":"No viewport meta tag found.","how":"Add a viewport meta tag to enable responsive scaling on mobile. Without it, pinch-to-zoom may break WCAG 1.4.4."},"isHttps":{"what":"Page is served over HTTP, not HTTPS.","how":"Configure your server to redirect all HTTP traffic to HTTPS. Free certificates are available via Let's Encrypt. Required for EAA compliance."},"exactlyOneH1":{"what":"Page has zero or multiple H1 headings.","how":"Every page needs exactly one <h1> describing its main topic. Remove duplicate H1s; add one if absent. The H1 should match or closely reflect the page <title>."},"noSkippedLevels":{"what":"Heading levels are skipped (e.g. H2 → H4).","how":"Headings must nest sequentially. After an H2, only use H3, never jump to H4 or lower. Restructure the heading hierarchy to reflect content depth."},"noDuplicateHeadings":{"what":"Duplicate heading text found across the page.","how":"Each heading should be unique and self-describing. Instead of repeating 'Read more', use the topic title: 'Read more about [specific topic]'."},"hasH2s":{"what":"No H2 headings found on the page.","how":"Use H2 headings to divide your page into sections. Screen reader users navigate by headings, a flat document is hard to scan."},"noMissingAlt":{"what":"Images are missing alt attributes entirely.","how":"Add an alt attribute to every <img>. Describe what the image shows for informative images. Use alt='' to hide purely decorative images from screen readers."},"noSuspiciousAlt":{"what":"Image alt text contains filename or generic words.","how":"Replace alt text like 'image.jpg' or 'photo' with text describing the image content. Alt should answer: what does this image convey to someone who cannot see it?"},"altCoverageHigh":{"what":"Fewer than 90% of images have alt text.","how":"Audit all <img> elements. Every image needs an alt attribute, even decorative ones (use alt=''). Missing alt is one of the most common WCAG failures."},"altQualityHigh":{"what":"Image alt text passes a basic quality check.","how":"Avoid alt text that is just a filename or a generic word like 'photo' or 'icon'. Describe what the image conveys."},"noTooShortAlt":{"what":"Some images have alt text shorter than 5 characters.","how":"Very short alt text (e.g. 'x', 'ok', '?') rarely conveys meaning. Write a phrase that describes the image's purpose in context."},"noEmptyLinks":{"what":"Links have no accessible name (empty text, no aria-label).","how":"Every <a> must have visible text or an aria-label. Icon-only links must describe the destination. Screen readers announce links by their name."},"noGenericLinks":{"what":"Links use generic text: 'click here', 'read more', 'learn more'.","how":"Replace generic link text with destination-specific text. Screen reader users often navigate by listing all links, generic text is meaningless out of context."},"noEmptyButtons":{"what":"Buttons have no accessible name.","how":"Every <button> needs visible text, an aria-label, or an aria-labelledby. Icon buttons must have accessible names for voice control and screen readers."},"allFormInputsLabelled":{"what":"Form inputs are not programmatically associated with labels.","how":"Connect every <input>, <select>, and <textarea> to a <label> using matching for/id attributes, or use aria-label. Placeholder text is not a substitute."},"hasMain":{"what":"No <main> landmark element found.","how":"Wrap the primary page content in a <main> element. Landmark regions let screen reader users jump directly to the content they need."},"hasNav":{"what":"No <nav> landmark found.","how":"Wrap navigation menus in <nav> elements. If you have multiple nav regions, give each a unique aria-label."},"hasSkipLink":{"what":"No skip navigation link found.","how":"Add a 'Skip to main content' link as the first focusable element on every page. It can be visually hidden until focused."},"multipleNavLabelled":{"what":"Multiple <nav> elements lack distinct aria-labels.","how":"When a page has more than one <nav>, give each a unique aria-label so screen reader users can tell them apart."},"noAutoplay":{"what":"Video or audio content autoplays with sound.","how":"Remove autoplay from <video> and <audio> elements, or ensure video is muted (muted autoplay is acceptable). Unexpected audio drowns out screen readers."},"noPositiveTabindex":{"what":"Elements use positive tabindex values (tabindex=1, 2…).","how":"Remove positive tabindex values, they override natural tab order and confuse keyboard users. Use tabindex='0' to make non-interactive elements focusable."},"noLayoutTables":{"what":"Tables appear to be used for layout rather than data.","how":"Use CSS (flexbox or grid) for layout. If you must use a table for layout, add role='presentation' so screen readers skip its table semantics."},"noBlinking":{"what":"Blinking or marquee content detected.","how":"Remove <blink> and <marquee> elements, they are deprecated and inaccessible. Replace CSS blink animations with transitions that respect prefers-reduced-motion."},"noOverlay":{"what":"An accessibility overlay widget (AccessiBe, UserWay, EqualWeb, etc.) was detected.","how":"Overlays are explicitly called out as inadequate by the European Commission guidance on Directive 2019/882. They do not substitute for real WCAG conformance. Remove the overlay, fix the underlying accessibility issues, and publish a self-authored Art. 13 statement.","example":"Uninstall the AccessiBe / UserWay / EqualWeb script. Remediate content to WCAG 2.2 AA. Write your own accessibility statement."},"hasA11yFooterLink":{"what":"No accessibility statement link found in the footer.","how":"EAA Article 4 + EN 301 549 Clause 12 require a published accessibility statement reachable from every page. Add a footer link labelled 'Accessibility' pointing to your statement page."},"hasEaaAwareness":{"what":"Home page contains no reference to the European Accessibility Act, Directive 2019/882, WCAG, or EN 301 549.","how":"While not a WCAG requirement, naming the legal basis of your accessibility programme (EAA, WCAG 2.2 AA, EN 301 549) signals to regulators and users that the programme is formal. Add these references to your accessibility statement or About page."}},"categoryQuestions":{"perceivable":{"label":"Perceivable","questions":{"p1":{"text":"All informative images have meaningful, descriptive alt text.","guidance":"Check images that convey information, logos, icons, photos. Each needs alt text that describes its purpose."},"p2":{"text":"Decorative images use empty alt attributes (alt='') or role='presentation'.","guidance":"Purely decorative images must be hidden from screen readers to avoid noise."},"p3":{"text":"Pre-recorded video content has accurate captions.","guidance":"Captions must be synchronised and include speaker identification where relevant."},"p4":{"text":"Pre-recorded audio-only content has a transcript.","guidance":"Podcasts or audio descriptions must have a full text transcript available."},"p5":{"text":"Heading structure (H1–H6) is logical, sequential, and non-skipping.","guidance":"Each page should have a single H1. Headings must not skip levels (e.g. H2 to H4)."},"p6":{"text":"Instructions do not rely solely on sensory characteristics (colour, shape, position).","guidance":"Avoid 'click the green button', use labels or text to identify elements."},"p7":{"text":"Colour is not the only means of conveying information or indicating status.","guidance":"Error states, chart data, required fields, all must use shape, text, or pattern alongside colour."},"p8":{"text":"Normal text (under 18pt) meets a contrast ratio of at least 4.5:1.","guidance":"Use a contrast checker against all background/foreground colour combinations."},"p9":{"text":"Large text (18pt or 14pt bold and above) meets a contrast ratio of at least 3:1.","guidance":"Large text has a relaxed ratio. Still verify headings and UI labels."},"p10":{"text":"Text can be resized up to 200% without loss of content or functionality.","guidance":"Test by zooming to 200% in the browser, no horizontal scrolling, no content overlap."},"p11":{"text":"Images of text are avoided where live text could achieve the same effect.","guidance":"Text in images cannot be resized or translated. Exceptions: logos and decorative content."},"p12":{"text":"Non-text UI components (buttons, inputs, focus indicators) meet 3:1 contrast ratio.","guidance":"Form borders, checkbox outlines, button boundaries, all must meet 3:1 against adjacent colours."}}},"operable":{"label":"Operable","questions":{"o1":{"text":"All functionality is accessible using the keyboard alone (no mouse required).","guidance":"Tab through the entire site. Every interactive element, menus, modals, carousels, must be reachable and operable."},"o2":{"text":"No keyboard traps exist, users can always move focus away from any component.","guidance":"Focus must never become stuck inside a widget. Modals need an accessible close mechanism."},"o3":{"text":"Time limits have pause, extend, or disable controls.","guidance":"Session timeouts and auto-refresh must warn users and allow extension."},"o4":{"text":"Moving, blinking, or auto-updating content can be paused or stopped.","guidance":"Carousels, tickers, and animated banners must have a pause control."},"o5":{"text":"No content flashes more than 3 times per second.","guidance":"Flashing content can trigger photosensitive seizures. Use the Trace Centre tool or PEAT to test."},"o6":{"text":"A skip navigation link allows users to bypass repeated content.","guidance":"The first interactive element on every page should be a 'Skip to main content' link."},"o7":{"text":"Every page has a meaningful, unique, descriptive title.","guidance":"Page titles appear in browser tabs and screen reader announcements. Format: Page Name | Site Name."},"o8":{"text":"Focus order follows a logical, meaningful sequence.","guidance":"Tab through the page, focus should move left to right, top to bottom, following visual flow."},"o9":{"text":"All links have descriptive accessible names (no 'click here' or 'read more').","guidance":"Link text must make sense out of context. Use aria-label if the visual text is ambiguous."},"o10":{"text":"Keyboard focus is always visible, a clear focus indicator is shown.","guidance":"The default browser outline must not be suppressed unless replaced with an equally visible indicator."},"o11":{"text":"Visible button and control labels match their accessible name.","guidance":"Siri/voice control users speak the visible label. If the accessible name differs, voice commands break."},"o12":{"text":"Touch targets are at least 24×24 CSS pixels (44×44 recommended).","guidance":"Small tap targets cause motor accessibility failures. Check on mobile with real devices."}}},"understandable":{"label":"Understandable","questions":{"u1":{"text":"The primary language of each page is declared in the HTML lang attribute.","guidance":"Every page must have <html lang='en'> (or appropriate BCP 47 code). Missing lang breaks screen reader pronunciation."},"u2":{"text":"Language changes within content are marked up with lang attributes.","guidance":"If a phrase appears in French on an English page, wrap it: <span lang='fr'>Bonjour</span>."},"u3":{"text":"No unexpected context changes occur when a component receives focus.","guidance":"Focusing a dropdown must not auto-submit or navigate. Changes only happen on deliberate activation."},"u4":{"text":"No unexpected context changes occur when input is changed.","guidance":"Selecting a radio button must not auto-advance the page. Users must control navigation."},"u5":{"text":"Navigation is consistent across all pages.","guidance":"The main nav, header, and footer must appear in the same order site-wide."},"u6":{"text":"Form errors are identified in text and describe what went wrong.","guidance":"Error messages must name the field and explain the problem: 'Email address is invalid'."},"u7":{"text":"Form inputs have clear, visible labels, not just placeholder text.","guidance":"Placeholder text disappears on input and has poor contrast. Always use a persistent <label>."},"u8":{"text":"Error correction suggestions are provided where possible.","guidance":"If the user enters the wrong format, tell them the expected format (e.g. DD/MM/YYYY)."},"u9":{"text":"Confirmation or reversal is available for important submissions.","guidance":"Legal, financial, or account-deletion actions must have a review/confirm step or undo mechanism."},"u10":{"text":"Previously entered information is auto-populated where re-entry is required.","guidance":"Multi-step forms must not force users to re-enter data from a prior step (WCAG 2.2 new)."},"u11":{"text":"Cognitive accessibility tests (e.g. CAPTCHAs) have an accessible alternative.","guidance":"Audio or text alternatives must be provided. Avoid puzzle-based CAPTCHAs entirely where possible."},"u12":{"text":"Reading level is appropriate for the intended audience (plain language).","guidance":"Use Flesch-Kincaid or similar. Aim for Grade 8–10 for general public content."}}},"robust":{"label":"Robust","questions":{"r1":{"text":"HTML is valid, no duplicate IDs, unclosed elements, or invalid nesting.","guidance":"Run pages through the W3C HTML validator. Duplicate IDs break ARIA label associations."},"r2":{"text":"All interactive controls have an accessible name, role, and state exposed to assistive technology.","guidance":"Custom buttons, toggles, and tabs must have role, aria-label (or label), and aria-expanded / aria-checked as appropriate."},"r3":{"text":"Form inputs are programmatically associated with their visible labels via for/id or aria-labelledby.","guidance":"Screen readers read the label when the input receives focus. Missing association = silent input."},"r4":{"text":"Status messages are exposed to screen readers via ARIA live regions.","guidance":"Form success/error messages, cart updates, and loading states must use aria-live='polite' or role='alert'."},"r5":{"text":"ARIA is used correctly, roles, states, and properties match the intended behaviour.","guidance":"Avoid aria-* misuse (e.g. Aria-hidden on focusable elements, aria-label on non-interactive elements)."},"r6":{"text":"Custom interactive components follow ARIA Authoring Practices Guide patterns.","guidance":"Custom tabs, accordions, menus, and dialogs must implement keyboard interactions per the ARIA APG."},"r7":{"text":"Modal dialogs trap focus correctly and restore focus on close.","guidance":"When a modal opens, focus must move inside it. Tab must cycle within. On close, focus returns to the trigger."},"r8":{"text":"The site functions correctly with JavaScript disabled for core content.","guidance":"Core page content and navigation should be accessible even if JS fails or is disabled."}}},"eaa":{"label":"EAA / Legal","questions":{"e1":{"text":"An accessibility statement is published and references WCAG 2.2 Level AA and EN 301 549.","guidance":"Required under EAA / EN 301 549. Must include conformance level, known limitations, and contact details."},"e2":{"text":"The accessibility statement is kept up to date and reviewed at least annually.","guidance":"Stale statements with old dates or outdated information can be challenged by enforcement bodies."},"e3":{"text":"A mechanism exists for users to report accessibility issues and request accessible formats.","guidance":"An email address or contact form specific to accessibility feedback must be available."},"e4":{"text":"A documented accessibility policy exists and is approved by senior management.","guidance":"Enforcement authorities may request this during an audit. Policy should cover scope, standards, and owner."},"e5":{"text":"A process is in place for responding to accessibility complaints within a reasonable timeframe.","guidance":"Complaints must be handled promptly. Document the process and response SLA."},"e6":{"text":"Periodic accessibility testing is conducted and findings are documented.","guidance":"Evidence of testing (automated tools, manual testing, user testing with disabled users) should be maintained."}}}},"questionMeta":{"scLabel":"SC {sc}","questionNumber":"#{n}","autoDetected":"Auto-detected","answerLegend":"Answer for: {text}"},"live":{"label":"Live Score","value":"{label}, {percentage}%","viewFull":"Full Result","view":"View"},"nextCategory":"Next: {label} →","resultPanel":{"heading":"Provisional Result","weightedScore":"{percentage}% weighted score","issuesHeading":"Items requiring attention ({count})","exportWord":"Export Word (.docx)","exporting":"Exporting…","proOnly":"Pro only, Upgrade to export","proOnlyTitle":"Upgrade to Pro to export documents","back":"Back to Assessment","footnote":"This provisional result is based solely on self-reported answers and does not constitute a formal accessibility audit, legal opinion, or certification. AccessibilityRef accepts no liability for decisions made on the basis of this assessment. Formal conformance claims under the European Accessibility Act or EN 301 549 require independent professional verification."},"remaining":"Answer all {total} questions to view the full result. {remaining} remaining.","scopeLimitation":{"heading":"Scope limitation, provisional result only","body":"In crawl mode, sites with fewer than 500 pages are scanned in full. Larger sites are spot-checked using a <strong>20% random sample</strong>, capped at 2,000 pages. Each sampled page is run through <strong>27 heuristic checks</strong>. This represents a partial view: automated tools typically detect 30–40% of WCAG issues. Keyboard operability, cognitive accessibility, screen reader compatibility, and time-based media conformance require manual and assistive technology testing. The overall result (\"Provisional AA\", \"Non-Conformant\", etc.) is an <strong>internal working estimate only</strong>, it is not a WCAG conformance claim and cannot be cited as such under WCAG 2.2, EN 301 549, or the European Accessibility Act. A full conformance evaluation requires a documented methodology covering all applicable success criteria across a representative sample of pages."},"fixes":{"noIssues":"No issues detected across all scanned pages.","noIssuesSub":"All 27 automated checks passed on every page sampled.","summary":"{count, plural, one {# issue found, sorted by priority then frequency. Fix critical issues first.} other {# issues found, sorted by priority then frequency. Fix critical issues first.}}","groupHeading":"{count, plural, one {# issue to fix} other {# issues to fix}}","failPctLabel":"{percent}% fail","pagesAffected":"{count, plural, one {# page} other {# pages}}","howToFix":"How to fix"},"issuesTab":{"intro":"All {count} checks, sorted by how many pages are affected. Only checks with failures are highlighted.","allPass":"All pass ✓","pagesShort":"{count, plural, one {# page} other {# pages}}","failPctLabel":"{percent}% fail"},"pagesTab":{"searchPlaceholder":"Search by URL…","filters":{"all":"All pages","fail":"Failing (<80)","pass":"Passing (80+)"},"sortLabel":"Score","showing":"{shown} of {total} pages shown","showingWithErrors":"{shown} of {total} pages shown · {errored} blocked/errored","tableHeaders":{"url":"URL","score":"Score","issues":"Issues found"},"allChecksPassed":"All checks passed","truncated":"Showing 150 of {total}, use search or filters to narrow results."},"summaryFootnote":{"autoFilled":"{count, plural, one {# checklist question auto-filled from scan results, look for the Auto-detected badge below. You can override any answer manually.} other {# checklist questions auto-filled from scan results, look for the Auto-detected badge below. You can override any answer manually.}}","footer":"Automated checks cover structural HTML only. Keyboard navigation, screen reader behaviour, colour contrast, and cognitive accessibility require manual testing, use the checklist below for full coverage."},"exportPanel":{"labels":{"orgName":"Organisation name","orgNotSet":"(not set)","questionsAnswered":"Questions answered","assessmentMode":"Assessment mode","scannedUrl":"Scanned URL","pagesScanned":"Pages scanned","autoFilledAnswers":"Auto-filled answers","modeCrawl":"Automated crawl","modeUpload":"URL upload","modeSitemap":"Sitemap URL","conformance":"Conformance determination","weightedScore":"Weighted score","categoryRow":"{label}, answered / score","categoryRowValue":"{answered}/{total} questions · {percent}%"},"wcagLevel":"Level AA (50-point assessment)","summary":{"withOrg":"Provisional assessment for {orgName}, {answered}/50 answered","noOrg":"Add your organisation name above to enable export"},"downloadJsonLabel":"Download as JSON","downloadJsonHint":"Complete answer set + scan results"},"wordExport":{"title":"PROVISIONAL ACCESSIBILITY ASSESSMENT","organisation":"Organisation: {name}","assessmentDate":"Assessment Date: {date}","disclaimerHeading":"IMPORTANT DISCLAIMER","disclaimerBody":"This is a self-reported provisional assessment only. It does not constitute a formal accessibility audit, professional opinion, or certification of conformance. Results are based solely on answers provided by the respondent and have not been independently verified. This assessment does not replace a professional accessibility audit conducted by a qualified auditor.","overallHeading":"Overall Result","tableHeaders":{"score":"Score","percentage":"Percentage","result":"Provisional Result","answered":"Questions Answered","sourceUrl":"Source URL","verdict":"Verdict","markersHit":"Markers Hit (/ 12)","overlayVendor":"Overlay Vendor","sc":"SC","checkpoint":"Checkpoint","result2":"Result"},"statementHeading":"Accessibility Statement Analysis","footer":"Generated by accessibilityref.eu | {date}"},"fileNames":{"exportPrefix":"Provisional-assessment","draftFallback":"Draft","reportFallback":"Report"},"statementCard":{"heading":"Accessibility Statement","sourceUrlLabel":"Statement URL","verdicts":{"FULL_STATEMENT":"Full Annex V statement detected, verify completeness with the Statement Validator.","PARTIAL_STATEMENT":"Partial statement, some Annex V elements missing.","NO_STATEMENT":"No accessibility statement detected at the discovered URL.","OVERLAY_BOILERPLATE":"Generic overlay-vendor boilerplate, does not satisfy Annex V.","UNKNOWN":"Statement classification inconclusive."},"markers":{"wcagRef":"References WCAG","enRef":"References EN 301 549","feedback":"Feedback mechanism present","contactEmail":"Contact email present","date":"Last-reviewed date present","conformityClaim":"Conformity claim present"}},"pdfCard":{"heading":"{count, plural, one {# PDF discovered} other {# PDFs discovered}}","lede":"PDF documents linked from the scanned pages. Article 4 of the EAA applies to all service content, audit each PDF separately with the Document Auditor.","cta":"Open Document Auditor →"},"botWall":{"cardTitle":"This site blocks automated scans ({vendor})","cardBody":"The Whole-Site Scanner runs from our servers, and your target site is configured to block server traffic. That's a security choice on their side, not a fault in your site. To audit it, run the Live Page Bookmarklet from your own browser instead.","perPageBlocked":"We couldn't reach this page ({vendor} block)","perPageBody":"Open the page in your browser and run the bookmarklet to audit it.","vendor":{"cloudflare":"Cloudflare","akamai":"Akamai","datadome":"DataDome","unknown":"an enterprise bot-wall"},"useBookmarkletCta":"Run the Live Page Bookmarklet","retryCta":"Try a different URL","ownerAllowlistCta":"If you own this site, allowlist our scanner →","exportSectionTitle":"Pages we could not scan","exportSectionBody":"These pages were behind an automated-traffic block. They are excluded from the score. To audit them, run the Live Page Bookmarklet from your own browser."},"consistency":{"sectionTitle":"Statement vs scan consistency","mismatchTitle":"Claims that the scan did not confirm","matchTitle":"Claims the scan supports","unverifiableTitle":"Claims this scanner cannot check","statementSays":"Statement says","scanFound":"Scan found","claim":{"wcagConformance":"WCAG conformance","skipLink":"Skip link","altText":"Alt text on images","keyboardNav":"Keyboard navigability","feedbackChannel":"Feedback channel"}},"jurisdictional":{"sectionTitle":"Jurisdictional Framing","supervisorLabel":"Supervisor","finesLabel":"Fines","inForceLabel":"in force"},"templates":{"sectionTitle":"Template scores","column":"Template","home":"Home","cart":"Cart","checkout":"Checkout","category":"Category","product":"Product","other":"Other","inputLabel":"Template URLs (optional)","inputHelp":"Paste up to five URLs to override the automatic template detection.","exportSectionTitle":"Findings by template","exportSubsectionHeading":"{label} (score {score}%) — {pages} pages scanned","exportNoFindings":"No failing checks recorded for this template.","exportFindingRow":"[{severity}] {label} ({count} of {pages} pages)","severity":{"critical":"Critical","major":"Major","minor":"Minor"}}},"readability-dashboard":{"meta":{"title":"Readability Score Dashboard","description":"Batch-score multiple URLs for Flesch-Kincaid readability. See which pages are too complex for your audience."},"header":{"title":"Readability Score Dashboard","subtitle":"Batch score multiple URLs using the Flesch-Kincaid readability formula. Identify pages that are too complex for your target audience.","badge":"Pro Tool"},"howTo":{"title":"How to use this tool","step1":"Paste URLs into the input box below, one per line, or comma-separated.","step2":"Click Add URLs, then Analyse all to run scoring.","step3":"The Flesch Reading Ease score ranges 0–100. Higher = easier to read. WCAG 3.1.5 recommends content readable at lower secondary level (Flesch ≥60).","step4":"Pages scoring below 50 are considered difficult. Below 30 is very difficult, review and simplify these pages.","step5":"Download a CSV report to share with your content team or include in a compliance audit."},"wcagRef":{"label":"WCAG 3.1.5 Reading Level (Level AAA)","description":"Supplemental content is available for text that requires a reading ability more advanced than lower secondary education level."},"languageWarning":{"title":"Language Limitation:","body":"Flesch-Kincaid readability formulas are specifically calibrated for English. Batch-scoring non-English content will produce mathematically invalid results that cannot be used as supporting evidence for EAA compliance in those languages."},"inputs":{"placeholder":"Https://example.com/page1\nhttps://example.com/about\nhttps://example.com/services"},"actions":{"addUrls":"Add URLs","analyseAll":"Analyse all","analysing":"Analysing…","exportCsv":"Export CSV","clearAll":"Clear all","proOnlyExport":"Pro only, Upgrade to export","proOnlyExportTitle":"Upgrade to Pro to export documents","unlockPro":"Unlock with Pro, €999/yr","seeIncluded":"See what's included in Pro"},"results":{"avgScore":"Avg Score","overallEasy":"Overall: Easy to read","overallStandard":"Overall: Standard complexity","overallComplex":"Overall: Too complex, review flagged pages","words":"{count} words","sentences":"{count} sentences","pending":"Pending","error":"Error","belowThreshold":"Score {score} is below recommended threshold (60). Simplify sentences, use shorter words, and break up long paragraphs.","wcagLink":"WCAG 3.1.5 →","removeRow":"Remove"},"levels":{"veryEasy":"Very Easy","easy":"Easy","fairlyEasy":"Fairly Easy","standard":"Standard","fairlyDifficult":"Fairly Difficult","difficult":"Difficult","veryDifficult":"Very Difficult","insufficient":"Insufficient text"},"grades":{"fifth":"5th grade","sixth":"6th grade","seventh":"7th grade","eighthNinth":"8–9th grade","tenthTwelfth":"10–12th grade","college":"College","collegePlus":"College+"},"scoring":{"noText":"No readable text content found","insufficientText":"Insufficient text for analysis","longAvgSentence":"Average sentence length >25 words","veryLongSentences":"{count} very long sentence(s) (>30 words)","readingLevelIssue":"Reading level: {level} (score {score})","metaScore":"Score","metaGrade":"Grade","metaWords":"Words"},"bulkScan":{"title":"Bulk Readability Audit","subtitle":"Upload a sitemap to check reading level across your entire site, identify pages that are too complex for general audiences"},"csv":{"url":"URL","fleschScore":"Flesch Score","gradeLevel":"Grade Level","readingLevel":"Reading Level","wordCount":"Word Count","sentences":"Sentences","status":"Status"},"exportEvidence":{"toolName":"Readability Score Dashboard","inputPagesScanned":"Pages scanned","inputBelowThreshold":"Pages below readable threshold (score < 60)","inputAboveThreshold":"Pages at good readability (score ≥ 60)","inputAvgScore":"Average Flesch score","inputHardestPage":"Hardest page","summaryTemplate":"{done} pages scored, avg Flesch {avg}, {below} below readable threshold","resultPagesScanned":"Pages scanned","resultAvgScore":"Average Flesch score","resultAvgGrade":"Average grade level","resultPagesAbove":"Pages at good readability (≥60)","resultPagesBelow":"Pages below threshold (<60)","resultWorstPage":"Worst-performing page","resultBestPage":"Best-performing page","resultScoreOf":"{score}/100","naValue":"N/A","formatJsonLabel":"Download as JSON","formatJsonHint":"All readability scores","docxSummary":"Summary","docxTotalSubmitted":"Total pages submitted","docxSuccessfullyScored":"Pages successfully scored","docxWithErrors":"Pages with errors","docxAvgScore":"Average Flesch reading-ease score","docxAtOrAbove":"Pages at or above readable threshold (>= 60)","docxBelow":"Pages below readable threshold (< 60)","docxBestPage":"Best-performing page","docxWorstPage":"Worst-performing page","docxPerPage":"Per-Page Results","docxPerPageIntro":"For each submitted URL, the table below shows the Flesch reading-ease score, the equivalent US grade level, the reading-level band, and the word/sentence counts the score was based on.","docxColHash":"#","docxColUrl":"URL","docxColStatus":"Status","docxColScore":"Score","docxColGrade":"Grade","docxColLevel":"Reading level","docxColWords":"Words","docxColSentences":"Sentences","docxColRecommendation":"Recommendation","docxStatusDone":"DONE","docxStatusError":"ERROR","docxStatusRunning":"Running","docxStatusPending":"Pending","docxBelowThresholdHeading":"Pages Below Readable Threshold ({count})","docxBelowThresholdIntroSingle":"{count} page scored below Flesch 60 (Plain English / WCAG SC 3.1.5 target). The table below lists each one in order of severity, with a recommendation.","docxBelowThresholdIntroPlural":"{count} pages scored below Flesch 60 (Plain English / WCAG SC 3.1.5 target). The table below lists each one in order of severity, with a recommendation.","docxAboveThresholdHeading":"Pages Meeting Readable Threshold ({count})","docxAboveItem":"{url}, Flesch {score} ({level})","docxErroredHeading":"Errored Pages","docxColError":"Error","docxUnknownError":"Unknown error","docxRecommendationHigh":"Simplify significantly, very difficult to read","docxRecommendationMid":"Simplify, difficult for general audience","docxRecommendationLow":"Moderate, consider simplification","docxMethodHeading":"Method","docxMethodBody":"For each URL, the page text is fetched server-side and scored with the Flesch Reading Ease formula. Syllables are counted via a heuristic vowel-group method. The score is mapped to a US grade band and a reading-level label. The threshold for 'plain English' is Flesch >= 60 (approximately Grade 8-9). Tested against WCAG 2.2 SC 3.1.5 (Reading Level, Level AAA). Mapped to EN 301 549 V3.2.1 clause 9.3.1.5. Note: Flesch is calibrated for English; scores for other languages are mathematically invalid.","auditThresholdLabel":"Flesch Reading Ease ≥ 60 (Plain English / WCAG 3.1.5)"}},"readability":{"meta":{"title":"Readability Checker","description":"Analyse text complexity using Flesch-Kincaid scoring. Paste any content, get instant results."},"tabs_aria":"Readability modes","tab_single":"Single text","tab_bulk":"Bulk dashboard","tabs":{"proBadge":"Pro"},"header":{"title":"Readability Checker","subtitle":"Grade your original content, then paste your simplified version to see if it meets the WCAG SC 3.1.5 target of Grade 9 or below."},"actions":{"trySample":"Try sample text","clearAll":"Clear all"},"wcagInfo":{"title":"WCAG 2.2 SC 3.1.5, Reading Level (AAA)","description":"When content requires a reading ability beyond lower secondary education (approx. Grade 8–9), you must provide a simplified version or summary. This tool grades both your original and simplified text so you can confirm the simplified version actually hits the target.","whereToApply":"Where to apply it:","whereToApplyDetail":"Error messages, cookie/legal notices, checkout flows, support articles, product descriptions, and form instructions. Aim for Flesch-Kincaid Grade ≤ 9 with sentences averaging under 15 words."},"languageWarning":{"title":"Language Limitation:","body":"Flesch-Kincaid and similar readability formulas are calibrated specifically for English. While this tool will process other EU languages, the resulting scores are mathematically invalid for non-English content and cannot be used as supporting evidence for EAA understandable information compliance in those languages."},"editor":{"step1":"Step 1","step2":"Step 2","originalLabel":"Original Text","simplifiedLabel":"Simplified Version","editTab":"Edit","sentencesTab":"Sentences","originalPlaceholder":"Paste your content here to check the reading grade…","simplifiedPlaceholder":"Write or paste your simplified version here, scores update live as you type…","pasteToSee":"Paste text above to see readability scores","noSimplifiedYet":"No simplified version yet","noSimplifiedHint":"Type or paste here, the grade updates as you write so you can see when you hit Grade 9."},"stats":{"readingEase":"Reading Ease","gunningFog":"Gunning Fog","smogIndex":"SMOG Index","colemanLiau":"Coleman-Liau","words":"Words","sentences":"Sentences","avgSent":"Avg sent.","complexWords":"Complex words","passiveVoice":"Passive voice","readTime":"Read time","wordsUnit":"Words","syllables3plus":"3+ syllables","instances":"Instances","topKeywords":"Top Keywords","recommended":"≤ 12 recommended","gradeEquivalent":"Grade equivalent","secondsSuffix":"S","minutesSuffix":"M"},"longSentences":{"label":"{count} long sentence(s) (>25 words)"},"grade":{"fkGrade":"Flesch-Kincaid Grade","elementary":"Elementary","middleSchool":"Middle School","highSchool":"High School","university":"University","postGraduate":"Post-graduate","compliant":"SC 3.1.5 Compliant","simplifiedNeeded":"Simplified version needed","targetMet":"Target met, SC 3.1.5 ready","stillAbove":"Still above Grade 9, keep simplifying"},"ease":{"veryEasy":"Very easy","easy":"Easy","standard":"Standard","fairlyDifficult":"Fairly difficult","difficult":"Difficult","veryConfusing":"Very confusing"},"improvement":{"title":"Improvement Summary","targetAchieved":"Target achieved","progressMade":"Progress made","gradeIncreased":"Grade increased, check your edits","noChange":"No change yet","fkGradeChange":"FK Grade Change","ease":"Ease","fogIndex":"Fog Index","avgSentence":"Avg Sentence","higherBetter":"Higher = better","lowerBetter":"Lower = better","wordsShorter":"Words shorter","toReachGrade9":"To reach Grade 9:","sentencesStillLong":"{count} sentence(s) still over 25 words, split them up.","complexWordsRemain":"{count} complex words (3+ syllables) remain, replace with shorter alternatives where possible.","passiveVoiceInstances":"{count} passive voice instance(s), rewrite in active voice.","avgSentenceStillHigh":"Average sentence is still {avg} words, aim for under 15.","targetMetMessage":"Your simplified version scores Grade {grade}, it meets the WCAG SC 3.1.5 target of Grade 9 or below. Link to this version as the \"simplified alternative\" from your original content."},"sentenceView":{"noText":"No text to analyse.","legend12":"≤12 words","legend1320":"13–20 words","legend2125":"21–25 words","legend25plus":">25 words","passiveVoice":"Passive voice","short":"Short","ok":"OK","long":"Long","veryLong":"Very long","tooLong":"Too long","complex":"Complex","passive":"Passive","splitSentence":"Split this into two shorter sentences.","sentencesAnalysed":"{count} sentence(s) analysed","wordsBadgeSuffix":"W","complexBadge":"{count} complex"},"highReadingLevel":{"title":"When high reading levels are expected","intro":"Some websites are intentionally written for professional audiences, and a Grade 12–16 score may be entirely appropriate for the primary content. WCAG SC 3.1.5 does not require you to simplify specialist writing; it requires you to provide an alternative for users who need one.","commonlyHighTitle":"Sites that commonly score Grade 12–18","cannotSimplifyTitle":"What to do when you cannot simplify","cannotSimplifyIntro":"If simplifying the primary content would remove required precision, use one or more of these strategies to comply with SC 3.1.5:","legalPosition":"The legal position","legalPositionBody1":"SC 3.1.5 is Level AAA, the highest WCAG conformance level, and is not required by the EAA or most national accessibility regulations for general conformance (which target Level AA). However, it is referenced in EN 301 549 (the technical standard underpinning the EAA and the Web Accessibility Directive), and regulators may consider failure to provide plain-language alternatives as evidence of poor cognitive accessibility practice, particularly in consumer-facing financial and healthcare contexts. The CJEU and national enforcement bodies have latitude to consider overall usability, not only checklist conformance.","legalPositionBody2":"Best practice guidance: Even where SC 3.1.5 is not legally mandated, providing plain-language summaries for complex legal, financial, and medical content is low-cost, high-impact, and reduces the risk of a disproportionate burden challenge.","diagnosticTitle":"Diagnostic: what score is causing the high grade?","diagnosticIntro":"Use this tool's sentence view and metrics to identify the specific driver of a high grade, then apply targeted fixes:"},"commonlyHigh":{"legalTitle":"Legal & compliance","legalBody":"Contract terms, privacy policies, regulatory filings, dense subordinate clauses push grades above 16","medicalTitle":"Medical & clinical","medicalBody":"Patient information leaflets written by clinicians, clinical trial protocols, prescribing information","financialTitle":"Financial services","financialBody":"Prospectuses, KIDs (Key Information Documents), loan agreements, regulatory language is inherently complex","academicTitle":"Academic & research","academicBody":"Journal abstracts, grant applications, technical whitepapers, specialised vocabulary inflates syllable counts","technicalTitle":"Technical documentation","technicalBody":"API references, engineering specs, safety data sheets, precision requires terminology that resists simplification","governmentTitle":"Government & policy","governmentBody":"Legislation, impact assessments, planning documents, statutory language is formulaic and verbose"},"cannotSimplify":{"summaryTitle":"Plain-language summary","summaryBody":"Write a short (Grade ≤ 9) executive summary at the top of the page. Link to it from the detailed content.","glossaryTitle":"Inline glossary / tooltips","glossaryBody":"Define specialist terms on first use, either inline or via a tooltip/expandable definition. This reduces cognitive load without removing precision.","layeredTitle":"Layered content","layeredBody":"Structure pages with a brief overview section followed by the full technical version. Users self-select the depth they need.","separateTitle":"Separate accessible version","separateBody":"Publish a dedicated 'plain language version' page and link to it prominently. This is the WCAG-compliant alternative.","examplesTitle":"Worked examples","examplesBody":"For procedures or calculations, a worked example in plain language can convey the same information more accessibly than the formal definition alone.","audioVideoTitle":"Audio / video supplement","audioVideoBody":"A short explainer video or audio summary provides an alternative for users with reading or cognitive disabilities, link it clearly."},"diagnostic":{"longSentences":"Long sentences","longSentencesCause":"Average sentence length > 20 words","longSentencesFix":"Split compound sentences at conjunctions (and, but, which). Aim for one idea per sentence.","complexVocab":"Complex vocabulary","complexVocabCause":"Many 3-syllable words (polysyllabic)","complexVocabFix":"Replace with shorter synonyms where meaning is preserved. Add a glossary for unavoidable technical terms.","passiveVoice":"Passive voice","passiveVoiceCause":"'was issued by', 'is required to be'","passiveVoiceFix":"Rewrite in active voice: 'The regulator issued', 'You must'. Passive voice adds syntactic distance and length.","fixLabel":"Fix:"},"wcagRefSection":{"title":"WCAG 2.2 SC 3.1.5, Reading Level","body":"SC 3.1.5 (Level AAA) requires a supplemental version when content needs reading ability beyond lower secondary education (approx. Grade 8–9). Targeting Grade 8 ensures the widest audience accessibility, including users with cognitive disabilities.","officialLink":"Read SC 3.1.5 Understanding Document"},"exportEvidence":{"toolName":"Readability Checker","toolDescription":"This assessment evaluates the reading level of textual content against WCAG 2.2 SC 3.1.5. Content written above CEFR B2 / Flesch-Kincaid Grade 9 creates barriers for people with cognitive disabilities, dyslexia, and those reading in a second language. Where content exceeds this threshold, a simplified version or summary must be provided.","inputOriginalChars":"Original text (chars)","inputSimplifiedChars":"Simplified text (chars)","inputFkGrade":"Flesch-Kincaid grade","inputReadingEase":"Reading ease score","summaryWithOrig":"Original grade {origGrade}","summaryWithBoth":"Original grade {origGrade} → simplified {simpGrade}","summaryNone":"No analysis yet","resultOriginalFk":"Original, Flesch-Kincaid Grade","resultOriginalEase":"Original, Reading Ease","resultOriginalFog":"Original, Gunning Fog","resultOriginalAvgSent":"Original, Avg sentence length","resultOriginalComplex":"Original, Complex words","resultOriginalPassive":"Original, Passive voice","resultSimplifiedFk":"Simplified, Flesch-Kincaid Grade","resultSimplifiedEase":"Simplified, Reading Ease","resultSimplifiedFog":"Simplified, Gunning Fog","resultSimplifiedAvgSent":"Simplified, Avg sentence length","wordsUnit":"Words","formatJsonLabel":"Raw data (.json)","formatJsonHint":"For developers","nextStepLabel":"Generate Accessibility Statement","nextStepHint":"Create your EAA Article 14 accessibility statement","docxSummary":"Summary","docxOriginalFkGrade":"Original FK Grade","docxOriginalStatus":"Original SC 3.1.5 status","docxSimplifiedFkGrade":"Simplified FK Grade","docxSimplifiedStatus":"Simplified SC 3.1.5 status","docxStatusPass":"PASS, Grade 9 or below","docxStatusFailNeeded":"FAIL, simplified version needed","docxStatusFailContinue":"FAIL, keep simplifying","docxOriginalMetrics":"Original Text, Full Metrics","docxSimplifiedMetrics":"Simplified Text, Full Metrics","docxMetricHeader":"Metric","docxValueHeader":"Value","docxTargetHeader":"Target / Note","docxFkGradeRow":"Flesch-Kincaid Grade","docxFkGradeTarget":"<= 9 for SC 3.1.5","docxEaseRow":"Flesch Reading Ease","docxEaseTarget":"Higher = easier ({label})","docxFogRow":"Gunning Fog Index","docxFogTarget":"<= 12 recommended","docxSmogRow":"SMOG Index","docxSmogTarget":"Grade equivalent","docxCliRow":"Coleman-Liau Index","docxCliTarget":"Grade equivalent","docxWordCount":"Word count","docxSentenceCount":"Sentence count","docxAvgSent":"Average sentence length","docxAvgSentTarget":"Aim for < 15","docxComplexWords":"Complex words (3+ syllables)","docxComplexTarget":"Lower = easier","docxPassive":"Passive voice instances","docxPassiveTarget":"Lower = easier","docxReadTime":"Estimated reading time","docxReadTimeTarget":"@ 200 wpm","docxNoTarget":",","docxLongSentencesHeading":"Long sentences in original ({count})","docxLongSentencesIntro":"These sentences exceed 25 words and should be split for accessibility.","docxLongSentencesSimpHeading":"Long sentences still in simplified version ({count})","docxTopKeywords":"Top keywords in original (excluding stop words)","docxTopKwHash":"#","docxTopKwWord":"Word","docxTopKwOcc":"Occurrences","docxOriginalText":"Original Text","docxSimplifiedText":"Simplified Text","docxImprovement":"Improvement Summary","docxFkChange":"FK Grade change","docxEaseChange":"Reading Ease change","docxFogChange":"Gunning Fog change","docxAvgSentChange":"Avg sentence length change","docxAvgSentChangeUnit":"Words","docxComplexRemoved":"Complex words removed","docxFinalOutcome":"Final SC 3.1.5 outcome","docxFinalMet":"Target met","docxFinalNotMet":"Below target, keep simplifying","docxEaseHigherEasier":"Higher = easier","docxFogLowerEasier":"Lower = easier","docxMethod":"Method","docxMethodBody":"The text is analysed locally in the browser using the Flesch-Kincaid Grade Level, Flesch Reading Ease, Gunning Fog, SMOG, and Coleman-Liau formulas. Syllables are counted via a heuristic vowel-group method. Complex words are defined as those with three or more syllables. Passive voice is detected with a be-verb-plus-past-participle regex. Long sentences are flagged at >25 words. Tested against WCAG 2.2 SC 3.1.5 (Reading Level, Level AAA). Mapped to EN 301 549 V3.2.1 clause 9.3.1.5. Note: these formulas are calibrated for English; scores for other languages are mathematically invalid."},"whatNext":{"toolName":"Readability Checker","proToolName":"Readability Score Dashboard"}},"rfp-generator":{"meta":{"title":"Vendor Accessibility Checklist, Accessibility RFP Questionnaire","description":"Pre-built accessibility questionnaire to send to vendors and suppliers. 28 evidence-based questions across 5 categories, with evaluator guidance. Doubles as an accessibility RFP template. Exports to Word."},"header":{"title":"Vendor Accessibility Checklist","subtitle":"Send a structured accessibility questionnaire to vendors and suppliers before you sign. 28 evidence-based questions across 5 categories, with evaluator guidance for what a passing answer looks like. Exports to Word with blank answer spaces, ready to drop into an RFP, tender, or due diligence pack.","badge":"Pro Tool"},"features":["28 evidence-based accessibility questions across 5 procurement categories","Covers Legal Compliance, Development & Testing, Governance, Product Capabilities, and Support","Export to Word with blank answer spaces, ready to send to suppliers","Each question includes why it matters and what a passing answer looks like"],"about":{"title":"What this tool does","body1":"When procuring a digital product or service on behalf of your organisation, you have a legal obligation to ensure that what you buy meets accessibility requirements under the European Accessibility Act. This questionnaire helps you assess vendors systematically, covering their legal compliance, testing practices, internal governance, product capabilities, and long-term support commitments.","body2":"Export the questionnaire to Word to create a professional, branded document with blank answer spaces that you can send directly to vendors as part of your RFP, tender, or due diligence process."},"form":{"title":"Document Details","orgName":"Your Organisation Name","orgPlaceholder":"E.g. City Council of Dublin","projectName":"Project / Contract Name","projectPlaceholder":"E.g. New HR Portal Procurement 2026","vendorName":"Vendor / Supplier Name","vendorPlaceholder":"E.g. SoftwareCo Ltd, or leave blank for generic","deadline":"Response Deadline","deadlinePlaceholder":"E.g. 15 April 2026"},"questions":{"title":"Questions, {selected} of {total} selected","selectAll":"Select all","deselectAll":"Deselect all","selected":"{count}/{total} selected","categorySelected":"{count}/{total} selected","questionPrefix":"Q{number}.","showGuidance":"Show evaluator guidance ▼","hideGuidance":"Hide guidance ▲","whyWeAsk":"Why we ask this","whatToLookFor":"What to look for","minimumPass":"Minimum pass","redFlags":"Red flags"},"categories":{"legalCompliance":"Legal Compliance & Standards","developmentTesting":"Development & Testing","peopleGovernance":"People & Governance","productCapabilities":"Product Capabilities","supportRoadmap":"Support & Roadmap"},"actions":{"exportWord":"Export to Word","exporting":"Exporting…","exportBlank":"Blank version","exportBlankTitle":"Download a generic blank questionnaire with every question included and no project/vendor details, for sending off-the-shelf to any vendor.","proOnlyExport":"Pro only, Upgrade to export","proOnlyTitle":"Upgrade to Pro to export documents"},"exportPanel":{"heading":"Export Questionnaire","summary":"{count, plural, one {# question selected} other {# questions selected}} · Exports as a formatted Word document with vendor answer spaces and signature block.","toolName":"RFP Accessibility Template","downloadJsonLabel":"Download as JSON","downloadJsonHint":"Questions + selections","summaryWithProject":"{project}, {count, plural, one {# question} other {# questions}} for {vendor}","summaryFallbackVendor":"Vendor","summaryEmpty":"Add organisation and project name above to enable export","labels":{"organisation":"Organisation","project":"Project","vendor":"Vendor","deadline":"Submission deadline","deadlineNotSet":"Not set","totalSelected":"Total questions selected","empty":","},"filenameDraft":"Draft"},"word":{"title":"Accessibility Vendor Questionnaire","subtitle":"European Accessibility Act · WCAG 2.2 · EN 301 549 V3.2.1","issuedBy":"Issued by","projectContract":"Project / Contract","addressedTo":"Addressed to","responseDeadline":"Response deadline","dateIssued":"Date issued","vendorResponse":"Vendor response:","vendorDeclaration":"Vendor Declaration","vendorDeclarationBody":"By signing below, the vendor confirms that the responses provided are accurate, complete, and truthful to the best of their knowledge, and that supporting documentation is available upon request.","instructionsHeading":"Instructions for Vendors","instructions":["This questionnaire forms part of the procurement process for {project}. It assesses your organisation's accessibility programme and your product's conformance with WCAG 2.2 Level AA, as required under the European Accessibility Act (Directive 2019/882/EU).","Please provide full, honest, and evidenced responses to each question. Vague commitments without supporting evidence will be scored lower than specific, documented answers.","Where a question reveals a known gap or limitation, please describe it honestly along with your planned remediation timeline. Undisclosed barriers that are later discovered may be treated as material non-disclosure.","Supporting documents (VPAT/ACR, audit reports, training records, roadmaps) may be attached to your response."],"questionsHeading":"Questions","whyLabel":"Why we ask this:","lookForLabel":"What to look for:","minimumPassLabel":"Minimum pass:","redFlagsLabel":"Red flags:","fallback":{"organisation":"[Organisation Name]","project":"[Project Name]","vendor":"[Vendor / Supplier Name]","deadline":"[Date]","projectInline":"[project]"},"signature":{"vendorOrg":"Vendor organisation name:","signedBy":"Signed by (name):","title":"Title / Role:","date":"Date:","signature":"Signature:"},"filenameVendorFallback":"Vendor"},"rfpQuestions":{"q1":{"question":"Do your digital products and services currently conform to WCAG 2.2 Level AA in full? If partial conformance is claimed, please specify which success criteria are not met and the reason.","why":"WCAG 2.2 Level AA is the technical standard referenced by the European Accessibility Act (EN 301 549) and by most national public-sector accessibility regulations. Partial conformance carries legal risk for your organisation if you rely on the vendor's products.","lookFor":"A clear yes/no with evidence, or an honest list of known gaps with a remediation timeline. Be cautious of vague answers like 'we are committed to accessibility' without specifics.","minimumPass":"A clear yes/no with a specific list of any known gaps plus a dated remediation timeline.","redFlags":"Vague statements like 'we are committed to accessibility' with no evidence. Claims of 'full WCAG 2.2 conformance' with no ACR to verify."},"q2":{"question":"Can you provide a current Accessibility Conformance Report (ACR) based on the VPAT® 2.5 (WCAG Edition) or EN 301 549 edition? Please include the date of the most recent audit.","why":"An ACR (filled VPAT) is the standard procurement document for accessibility. It lets buyers compare vendors on a structured, criteria-by-criteria basis. An up-to-date ACR signals maturity.","lookFor":"A VPAT completed within the past 12 months, covering all WCAG 2.2 Level A and AA success criteria. Older documents or documents covering only WCAG 2.1 are less reliable.","minimumPass":"A VPAT/ACR completed or updated within the past 12 months, covering WCAG 2.1 or 2.2 Level A and AA, with a named auditor and date.","redFlags":"ACR dated more than 24 months ago. Self-assessment only with no third-party verification. ACR covering WCAG 2.0 only."},"q3":{"question":"How does your organisation ensure ongoing compliance with the European Accessibility Act (Directive 2019/882) for all products and services placed on the EU market after 28 June 2025?","why":"The EAA is now enforceable across all 27 EU member states. Products and services placed on the market after June 2025 must comply. Vendors without a clear EAA compliance programme pose regulatory risk.","lookFor":"Evidence of: a legal gap analysis against EAA requirements, a compliance roadmap, and accountability at management level.","minimumPass":"Evidence of a completed EAA legal gap analysis, a roadmap with owner, and management-level accountability.","redFlags":"No knowledge of EAA or Directive 2019/882. No compliance programme. 'We're looking into it' without specifics."},"q4":{"question":"Have you produced an EU Declaration of Conformity in accordance with Annex IV of Directive 2019/882 for the product(s)/service(s) being offered? Can you provide a copy?","why":"The Annex IV declaration is a mandatory legal document that must be drawn up before a product is placed on the EU market and retained for five years (Article 20). Its absence is a direct non-conformity.","lookFor":"A signed document covering the seven mandatory Annex IV elements: identification, manufacturer, sole responsibility, object, conformity statement, harmonised standards, and signatory.","minimumPass":"A signed DoC covering all 7 Annex IV mandatory elements, dated and in force, available on request.","redFlags":"No DoC at all. A DoC that covers only part of the product. A DoC signed by someone without authority to legally bind the organisation."},"q5":{"question":"Do you publish an Accessibility Statement in accordance with Annex V of Directive 2019/882? Please provide the URL.","why":"An Accessibility Statement is a public-facing legal requirement for digital services. It must include the conformance status, known barriers, complaint mechanism, and escalation route to an enforcement body.","lookFor":"A live, dated Accessibility Statement that matches the Annex V template, not simply a corporate commitment page.","minimumPass":"A live, dated URL to a published Accessibility Statement reviewed within the past 12 months, containing conformance status, known barriers, feedback mechanism, and enforcement body escalation route.","redFlags":"A generic 'accessibility commitment' page with no structured statement. No URL available. Statement not updated in over 12 months."},"q6":{"question":"Please describe your end-to-end accessibility testing methodology, including the specific tools, screen readers, browsers, and operating systems used.","why":"Strong accessibility testing requires a combination of automated tools (for coverage) and manual testing with assistive technologies (for validity). Neither alone is sufficient.","lookFor":"Mention of specific tools (axe, WAVE, Lighthouse, Deque WorldSpace), specific screen readers (NVDA + Chrome, JAWS + Chrome/Edge, VoiceOver + Safari), and explicit manual test procedures.","minimumPass":"Named tools (axe, WAVE, Lighthouse or equivalent), named screen readers (NVDA+Chrome, JAWS+Edge, VoiceOver+Safari as a minimum), and a described manual testing process.","redFlags":"Automated tools only, no screen reader testing. Testing only on one browser/OS combination. Vague references to 'industry standard tools'."},"q7":{"question":"Is automated accessibility testing integrated into your CI/CD pipeline? At what stage does a failing accessibility check block a release?","why":"Automated testing integrated into CI/CD prevents regressions reaching production. The answer reveals whether accessibility is treated as a quality gate or an afterthought.","lookFor":"Specific pipeline integration (GitHub Actions, Jenkins, Azure DevOps) with axe-core or pa11y. Ideally, critical accessibility failures should block merges.","minimumPass":"Accessibility checks integrated into CI/CD (GitHub Actions, Jenkins, Azure DevOps) with named tools (axe-core, pa11y) and critical failures blocking merges or deployments.","redFlags":"Accessibility testing only triggered manually before releases. No pipeline integration. No quality gate."},"q8":{"question":"Do you conduct structured manual testing with disabled users or paid testers who use assistive technology? If so, how frequently, and what does the process involve?","why":"Automated tools detect around 30–40% of WCAG issues. The remainder require human judgment, especially for cognitive accessibility, task completion, and screen reader flow.","lookFor":"Evidence of regular user testing sessions with screen reader users, cognitive disability testers, or mobility-impaired users, not just internal team members.","minimumPass":"Regular sessions (at least annually) with real disabled users or paid assistive technology testers, with a described process and documented outcomes.","redFlags":"No user testing with disabled users. Internal team only. Screen reader testing done only by sighted developers."},"q9":{"question":"How frequently is formal accessibility testing conducted? Is it triggered only by major releases or embedded in every sprint?","why":"Accessibility regresses silently. Point-in-time audits are insufficient for products with continuous deployment. Testing cadence reveals the maturity of the programme.","lookFor":"Sprint-level automated testing plus quarterly manual reviews as a minimum. Annual audits only, or audits conducted only before procurement, are a warning sign.","minimumPass":"Sprint-level automated testing plus at minimum quarterly manual reviews. Testing embedded in SDLC, not only pre-release.","redFlags":"Annual-only audits. Testing only conducted when a procurement requires it. No ongoing monitoring."},"q10":{"question":"How are accessibility defects classified, tracked, and prioritised? What is your defined SLA for remediating critical accessibility barriers that prevent a user from completing a core task?","why":"Without a defect classification system, accessibility bugs are deprioritised in favour of feature work. An SLA commitment signals that accessibility is treated like functional quality.","lookFor":"A defined severity taxonomy (critical/major/minor mapped to user impact), a ticketing process, and specific SLAs, e.g. Critical barriers fixed within 5 business days.","minimumPass":"A defined severity taxonomy (critical/major/minor based on user impact) plus specific SLAs, e.g. Critical barriers fixed within 5 business days.","redFlags":"No formal defect classification. Accessibility bugs in the same queue as feature requests with no priority weighting. No SLA commitment."},"q11":{"question":"Is there a named Accessibility Lead, Subject Matter Expert (SME), or dedicated accessibility function within your product team? What are their responsibilities?","why":"Accessibility requires sustained specialist knowledge. Organisations without a designated lead typically have inconsistent implementation and slow defect response.","lookFor":"A named role with product-level authority, not just an HR diversity statement. The SME should be involved in design reviews, code reviews, and audit responses.","minimumPass":"A named Accessibility Lead or SME with product-level authority, involved in design reviews, code reviews, and audit responses.","redFlags":"Accessibility owned only by HR or a diversity team. No technical SME. No product team representation."},"q12":{"question":"What accessibility training do your engineers, designers, and product managers receive? Is this training mandatory and how recently was it updated to cover WCAG 2.2?","why":"WCAG 2.1 and 2.2 introduced significant new requirements (success criteria 2.5.3–2.5.8, 3.2.6, 3.3.7–3.3.9). Training that pre-dates 2023 may not cover these criteria.","lookFor":"Role-specific training (not a single company-wide session), updated for WCAG 2.2, and with evidence of completion (completion certificates, training records).","minimumPass":"Mandatory training for engineers, designers, and PMs, updated to cover WCAG 2.2 within the past 18 months, with evidence (e.g. Training records, certification).","redFlags":"Training is optional or informal. Last update covered WCAG 2.0 or 2.1 only. No training records available."},"q13":{"question":"Who within your organisation holds ultimate accountability for accessibility compliance, and at what seniority level?","why":"When accountability sits below Director level, accessibility typically lacks the authority to block releases or secure remediation budget. Executive sponsorship is a strong predictor of programme success.","lookFor":"A C-suite sponsor or Board-level commitment, not just a mid-level team lead. Look for evidence in annual reports, public statements, or governance documents.","minimumPass":"Executive sponsor named, accessibility in OKRs or KPIs, board-level reporting.","redFlags":"No executive ownership. Accessibility not in any performance objective or business metric."},"q14":{"question":"Have you engaged external accessibility auditors within the past 18 months? Can you share the scope, findings summary, and evidence of remediation?","why":"Self-assessment alone is insufficient for a defensible compliance position. External audits provide independent validation and are increasingly expected by regulators.","lookFor":"An audit report from a recognised accessibility consultancy, with a remediation log showing which issues have been fixed. Redacted finding summaries are acceptable.","minimumPass":"External audit conducted within past 18 months by an independent firm, with a named auditor and methodology.","redFlags":"Self-assessment only. No external validation. External audit more than 3 years ago."},"q15":{"question":"Please describe how your product supports screen reader users. Which screen readers have been explicitly tested, and are there any known compatibility limitations?","why":"Screen reader support is the single most tested dimension in accessibility audits. Known limitations must be disclosed, undisclosed barriers become your organisation's liability.","lookFor":"Explicit testing against NVDA + Chrome, JAWS + Chrome/Edge (Windows), and VoiceOver + Safari (macOS/iOS). Known limitations should be documented.","minimumPass":"Explicit confirmation of screen reader support for NVDA+Chrome and VoiceOver+Safari at minimum, with test evidence.","redFlags":"Untested. Vague 'should work with screen readers' without evidence."},"q16":{"question":"Can all primary workflows in your product be completed using keyboard navigation alone, without the use of a mouse or touch screen? Please describe how this has been verified.","why":"Keyboard accessibility is fundamental to motor disability support and is a requirement under WCAG 2.1 (SC 2.1.1). Many products fail on complex components (date pickers, drag-and-drop, rich text editors).","lookFor":"Confirmation that all interactive components, including dropdowns, modal dialogs, date pickers, and data tables, are keyboard operable and follow ARIA Authoring Practices.","minimumPass":"All interactive elements keyboard-operable, no keyboard traps, visible focus indicator on all elements.","redFlags":"Mouse-only interactions. Custom UI components not keyboard accessible. No focus visibility."},"q17":{"question":"How does your product support users who require high contrast mode, text zoom to 200%, or browser-based font overrides?","why":"WCAG 1.4.4 requires text to remain readable at 200% zoom without loss of content or functionality. Windows High Contrast Mode support is essential for many visually impaired users.","lookFor":"Explicit confirmation of 200% zoom testing (not just system zoom), Windows High Contrast Mode support, and confirmation that custom font settings do not break layouts.","minimumPass":"Content readable and functional at 200% zoom and 400% magnification, with reflow at 320px width.","redFlags":"Horizontal scrolling required at 200% zoom. Content or functionality lost at high zoom."},"q18":{"question":"Are there any documented accessibility limitations or known non-conformances in the current version of the product? Please list them.","why":"Vendors who claim zero accessibility issues are rarely being honest. A list of known limitations, with planned fix dates, is a sign of maturity and transparency.","lookFor":"An honest list, however short. Refusal to answer or a claim of full conformance without supporting evidence should be treated as a risk flag.","minimumPass":"Known limitations listed honestly, each with WCAG criterion and remediation target date.","redFlags":"Claims of zero known limitations with no verification. Limitations listed without any remediation plan."},"q19":{"question":"Do users with disabilities who use your core customer-facing workflows (registration, checkout, account management, support) complete those tasks without encountering barriers? What evidence supports this?","why":"Task completion for disabled users is the operational measure of accessibility, it goes beyond criterion-level conformance to actual usability impact.","lookFor":"Evidence from user testing (session recordings, task completion rates) or structured usability studies with disabled participants.","minimumPass":"Evidence from user testing or equivalent that users with disabilities can complete core tasks independently.","redFlags":"No user task completion evidence. Theoretical compliance without real-world verification."},"q20":{"question":"What mechanism do users have to report accessibility barriers in your product? How are reports triaged, and what response time commitment can you make?","why":"EAA Annex V requires the Accessibility Statement to include a feedback mechanism and an escalation route to an enforcement body. Vendors without this are in direct non-conformance.","lookFor":"A dedicated accessibility feedback channel (not just a generic contact form), a defined response SLA (e.g. Acknowledge within 2 business days), and evidence it is actively monitored.","minimumPass":"A dedicated accessibility feedback channel, response SLA, and a named person responsible for accessibility complaints.","redFlags":"Accessibility feedback routed through generic support with no specialist handling. No SLA. No named responsible person."},"q21":{"question":"What contractual commitment can you make regarding accessibility maintenance across the contract term? Will you include accessibility as a measurable service level in the contract?","why":"Accessibility that is not in the contract will not be maintained. Service levels for accessibility issues should be defined alongside functional SLAs.","lookFor":"A willingness to include accessibility SLAs in the contract, e.g. No critical WCAG failures unresolved beyond X days; annual audit requirement; regression testing on major updates.","minimumPass":"Accessibility included as a measurable SLA in the contract, with defined remediation obligations and remedies for breach.","redFlags":"No accessibility in the contract. Vendor refuses to include accessibility warranties."},"q22":{"question":"What is your documented accessibility roadmap for the next 12–24 months? How does it address the new criteria introduced in WCAG 2.2?","why":"WCAG 2.2 added 9 new success criteria (SC 2.4.11–2.4.13, 2.5.3–2.5.8, 3.2.6, 3.3.7–3.3.9). Products that have not been updated for 2.2 have known gaps.","lookFor":"A product-specific roadmap with WCAG 2.2 new criteria addressed, not a generic 'we prioritise accessibility' statement.","minimumPass":"A specific roadmap with named WCAG 2.2 criteria, owners, and target dates.","redFlags":"No WCAG 2.2 roadmap. Vendor unaware of the 9 new WCAG 2.2 success criteria."},"q23":{"question":"How will you ensure continued accessibility conformance when the product is updated or new features are launched? What governance exists to prevent accessibility regression?","why":"New feature releases frequently introduce accessibility regressions. The absence of a release gate or accessibility sign-off process will eventually result in non-conformance.","lookFor":"An explicit accessibility gate in the release process, design review, code review checklist, automated CI check, and a manual sign-off step before major feature launches.","minimumPass":"Critical accessibility failures block releases. Defined quality gate with named criteria for what constitutes a blocker.","redFlags":"Accessibility issues never block releases. No quality gate defined."},"q24":{"question":"Do your sub-contractors and third-party component suppliers have accessibility obligations that flow down from your contract with us? How do you enforce accessibility requirements through your supply chain?","why":"EAA Article 10 requires economic operators to ensure their supply chain meets accessibility requirements. A vendor who relies on third-party components (maps, payment widgets, analytics, chat tools) but has no supply-chain obligation clause creates a gap that regulators will hold the prime vendor accountable for, not the sub-contractor.","lookFor":"Evidence of: contractual accessibility clauses cascaded to all third-party suppliers; a process to collect and verify sub-contractor VPATs/ACRs; a named owner responsible for supply-chain accessibility compliance; and a clear plan for what happens when a sub-contractor is non-conformant.","minimumPass":"Accessibility obligations flow to sub-contractors by contract, with VPAT collection from component vendors.","redFlags":"No supply chain accessibility requirements. Third-party components not assessed."},"q25":{"question":"Do you publish an Accessibility Statement for the products/services being offered that meets all mandatory elements of EAA Annex V? Please provide the URL and confirm when it was last updated.","why":"An Accessibility Statement is a mandatory public-facing document under EAA Article 16 and Annex V. It must contain: the conformance status, a description of known barriers, the assessment approach, a feedback mechanism, and the national enforcement body to which users can escalate complaints. A missing, outdated, or incomplete statement is a direct regulatory non-conformance that can attract enforcement action independently of the product's technical accessibility.","lookFor":"A live, dated URL to the published statement. The statement must have been reviewed within the past 12 months, must declare a specific conformance status (fully/partially/not compliant), must list known barriers with planned fix dates, and must name the applicable national enforcement body. A generic 'we care about accessibility' corporate page is not an Accessibility Statement.","minimumPass":"A live, dated URL to a statement reviewed within 12 months with all 7 Annex V mandatory elements.","redFlags":"No live URL. A statement that is a generic commitment page. Statement last updated more than 12 months ago."},"q26":{"question":"Is your product or service in scope of the European Accessibility Act (Directive 2019/882)? If yes, have you drawn up an EU Declaration of Conformity (DoC) under Annex IV, and can you provide a copy? Under which Annex I section do you classify your product/service?","why":"The EAA covers a defined set of products and services (Annex I, Sections I–XI) placed on the EU market from 28 June 2025. Economic operators must draw up a Declaration of Conformity before placing an in-scope product on the market (Article 20) and retain it for five years. If a vendor cannot confirm their EAA scope classification or provide a DoC, you cannot rely on their EAA compliance, and your own regulatory position as the service deployer may be affected.","lookFor":"Clear identification of the Annex I section (e.g. Section IX for e-commerce/web services, Section X for banking). A signed DoC covering all seven mandatory Annex IV elements: product identification, manufacturer details, sole responsibility declaration, object of declaration, conformity statement, harmonised standards referenced, and authorised signatory. The DoC should be current (reviewed within the past 12 months or when the product significantly changed).","minimumPass":"Clear identification of the applicable Annex I section, a signed DoC covering all 7 Annex IV elements, current and reviewed within 12 months.","redFlags":"Vendor cannot identify their EAA scope. No DoC. DoC does not cover the specific product being offered."},"q27":{"question":"What contractual warranty do you provide regarding accessibility? If a release introduces a critical accessibility regression that blocks a user from completing a core task, what are the contractual remedies and timelines for resolution?","why":"Without an accessibility warranty in the contract, the deploying organisation bears full regulatory risk if an integrated component causes non-conformance. A vendor warranty creates enforceable accountability and aligns incentives.","lookFor":"Explicit accessibility warranty language in the MSA/SLA. Defined remedy for critical accessibility regressions (e.g. Patch within 48h, credit, right to terminate). Not just a best-efforts commitment.","minimumPass":"Accessibility included as a warranty in the contract with a defined remedy for critical regressions and a named resolution SLA (e.g. Critical barriers resolved within 5 business days).","redFlags":"No warranty. Vendor refuses accessibility warranty language. Remedy is 'we'll look into it' with no defined timeline. Right to terminate not included for persistent non-conformance."},"q28":{"question":"How do you monitor for accessibility regressions post-deployment? Do you have automated regression testing that would detect an accessibility issue introduced in a routine update?","why":"Accessibility conformance can regress silently between audits, a routine UI update, dependency upgrade, or content change can break keyboard navigation or screen reader support without any visual indication. Monitoring is essential for maintaining sustained conformance.","lookFor":"Automated regression testing with axe-core or equivalent running against every deployment. Alerting for new accessibility violations. A process for reviewing new component or dependency versions for accessibility impact before shipping.","minimumPass":"Automated accessibility regression testing running on every deployment (not just manual releases), with alerting for new violations and a process to resolve before user exposure.","redFlags":"No automated regression testing. Accessibility only re-checked at the next formal audit cycle. No mechanism to detect regressions introduced between audits."}}},"roi-calculator":{"meta":{"title":"Accessibility ROI Calculator","description":"Estimate the financial return on EAA compliance, revenue uplift from reaching disabled users, legal risk mitigation, and payback period."},"header":{"title":"Accessibility ROI Calculator","subtitle":"Estimate the financial return on EAA compliance, revenue uplift from reaching disabled users, legal risk mitigation (Article 30), and payback period."},"inputs":{"section1Title":"1. Commercial Metrics","monthly":"Monthly","annual":"Annual","activeUsers":"Active users","conversionRate":"Conversion rate (%)","avgOrderValue":"Avg Order Value (€)","addressableAudience":"Addressable Audience (%)","section2Title":"2. Legal Risk & Investment","operatingCountry":"Operating Country","annualRevenue":"Annual Revenue (€)","complianceCost":"Estimated Compliance Cost (€)","benchmarks":{"smallSite":"Small site","mediumSite":"Medium site","largeSite":"Large site","enterprise":"Enterprise"}},"results":{"revenueUplift":"Revenue Uplift ({period})","reachedFrom":"Reached from {count} additional users","legalRiskTitle":"Legal Risk Mitigation (Art. 30)","potentialFineAvoided":"Potential fine avoided","legalRiskNote":"EAA Article 30 requires penalties to be effective, proportionate, and dissuasive. Fines for non-compliance in {country} are capped at {cap}.","netRoi":"Net ROI ({period})","annualRoi":"Annual ROI","totalValueAtRisk":"Total Value at Risk","paybackPeriod":"Payback Period","paybackMonths":"{months} mo","copySummary":"Copy Summary Text"},"methodology":{"title":"Methodology & Assumptions","audiencePrevalence":"Audience Prevalence:","audiencePrevalenceBody":"WHO estimates that 15-20% of the global population lives with a disability. In the EU, Eurostat (Disability statistics, prevalence and demography, 2022) reports that approximately 24% of adults aged 16+ have some form of activity limitation. This calculator defaults to 15% but is adjustable based on your target market demographics.","conversionParity":"Conversion Parity:","conversionParityBody":"The model assumes that removing accessibility barriers brings the conversion rate of disabled users to parity with your non-disabled user base. In practice, disabled users exhibit 70%+ brand loyalty to accessible platforms, potentially yielding higher LTV.","legalRisk":"Legal Risk:","legalRiskBody":"Avoided fine estimates are pulled from the EAA Fine Engine, based on national transpositions of Directive 2019/882. Fines are administrative and separate from potential private litigation or reputational damage costs.","disclaimer":"Disclaimer:","disclaimerBody":"This tool provides directional estimates for business case development. It does not constitute a financial guarantee or legal advice."},"disabilityGroups":{"visual":"Visual impairments","motor":"Motor impairments","cognitive":"Cognitive & learning","hearing":"Hearing impairments","speech":"Speech impairments","temporary":"Temporary impairments"},"export":{"toolName":"Accessibility ROI Calculator","downloadJson":"Download JSON","downloadHint":"Inputs + results + notes"}},"scoping-wizard":{"meta":{"title":"Am I Affected by the EAA?, Free EAA Scope Quiz","description":"Answer 5 simple questions to find out whether the European Accessibility Act applies to your business. Free, no login required, takes 60 seconds."},"header":{"title":"Am I Affected by the EAA?","subtitle":"Answer 5 quick questions to find out if the European Accessibility Act applies to your business.","badge":"Free, No Login Required","time":"Takes about 60 seconds"},"progress":{"step":"Question {current} of {total}"},"questions":{"employees":{"title":"How many people work at your company?","hint":"Include full-time and part-time staff.","options":{"under10":"Under 10","10to49":"10 – 49","50to249":"50 – 249","250plus":"250 or more"}},"turnover":{"title":"What is your annual turnover (revenue)?","hint":"An approximate figure is fine.","options":{"under2m":"Under €2 million","2to10m":"€2 – €10 million","10to50m":"€10 – €50 million","over50m":"Over €50 million"}},"offerings":{"title":"What do you offer to customers in the EU?","hint":"Select all that apply.","options":{"website":"Website or web application","mobile":"Mobile app","ecommerce":"E-commerce (online shop)","banking":"Banking or financial services","transport":"Transport or ticketing","ebooks":"E-books or digital publishing","telephony":"Telephony or messaging services","hardware":"Physical products (ATMs, kiosks, terminals)","none":"None of the above"}},"market":{"title":"Do you sell to customers in the EU?","hint":"This includes selling through third-party platforms.","options":{"yes_direct":"Yes, we sell directly to EU customers","yes_partners":"Yes, through partners or resellers","no":"No, we do not sell in the EU"}},"country":{"title":"Which EU country is your primary market?","hint":"Choose the country where most of your EU customers are located.","placeholder":"Select a country..."}},"results":{"in_scope":{"heading":"The EAA likely applies to you","body":"Based on your answers, your business appears to fall within the scope of the European Accessibility Act. You offer in-scope products or services to EU customers and do not qualify for the microenterprise exemption.","country_note":"View the specific requirements and penalties for {country}.","cta":"Start your compliance assessment","cta_country":"View {country} requirements"},"exempt":{"heading":"You may be exempt","body":"Your business appears to qualify as a microenterprise (under 10 employees and under €2M turnover) providing services only. Under Article 14 of the EAA, microenterprises providing services are exempt from the accessibility requirements. Note: this exemption does not apply to manufacturers of physical products.","cta":"Learn more about the EAA"},"out_of_scope":{"heading":"The EAA probably does not apply","body":"Based on your answers, your business does not appear to offer products or services that fall within the scope of the European Accessibility Act, or you do not sell to EU customers.","cta":"Review what the EAA covers"},"unclear":{"heading":"We need more information","body":"Based on your answers, we cannot give a definitive answer. Your situation may involve edge cases, such as partial EU market presence or offerings that straddle scope boundaries. We recommend taking the full EAA Ready Quiz for a more detailed assessment.","cta":"Take the full EAA Ready Quiz"},"disclaimer":"This is a simplified screening tool and does not constitute legal advice. The actual scope of the EAA depends on multiple factors including your specific products and services, national transposition laws, and contractual arrangements. Consult a qualified legal professional for a definitive assessment.","start_over":"Start over","copy_result":"Copy result to clipboard","copied":"Copied!","your_answers":"Your answers","answer_labels":{"employees":"Employees","turnover":"Turnover","offerings":"Offerings","market":"EU market","country":"Primary country"}},"export":{"docx":{"verdictHeading":"Scoping Verdict","rowVerdict":"Verdict","rowAnnexIvSection":"Annex IV section","valueAnnexIvExempt":"5, Disproportionate burden / microenterprise exemption","valueAnnexIvProduct":"1, Product description","rowPrimaryCountry":"Primary country of establishment","responsesHeading":"Operator Responses","columnQuestion":"Question","columnOperatorAnswer":"Operator answer","fallbackEmployees":"Employees","fallbackTurnover":"Annual turnover","fallbackOfferings":"Products / services placed on the EU market","fallbackMarket":"EU market activity","fallbackCountry":"Country","valueDash":",","reasoningHeading":"Reasoning","reasoningNoOffering":"No in-scope offering was selected, Article 2 does not apply when the operator does not place any of the listed products or services on the EU market.","reasoningNoMarket":"Operator does not sell to EU customers, directly or via partners, territorial scope under Article 2 is not engaged.","reasoningMicroenterprise":"Operator qualifies as a microenterprise providing services only, Article 4(5) exempts microenterprises (fewer than 10 staff and turnover ≤ €2M) from the obligations applicable to services. Note: this exemption does not apply to products, including hardware.","reasoningInScope":"Operator places at least one Annex I in-scope product or service on the EU market and does not qualify for the microenterprise exemption, accessibility obligations under EAA Article 4 apply.","reasoningCountry":"Country of establishment: {country}. National enforcement and any country-specific fine ranges follow the local transposition of Directive 2019/882.","methodHeading":"Method","methodBody":"This scoping decision is computed from the five operator-supplied answers above. The decision logic implements Directive (EU) 2019/882 (European Accessibility Act) Article 2 (territorial and material scope), Article 3 (definitions), Article 4 (general accessibility obligations) and Article 4(5) (microenterprise exemption, fewer than 10 staff and annual turnover ≤ €2 million, services only). Operators in scope must comply by 28 June 2025 unless they qualify for Article 14 disproportionate-burden or fundamental-alteration exemptions, which require their own assessment."}}},"screen-reader-simulator":{"meta":{"title":"Screen Reader Simulator","description":"Paste HTML and hear what a screen reader announces. Flags missing names, empty headings, and broken ARIA. Includes text-to-speech playback."},"header":{"title":"Screen Reader Simulator","subtitle":"Paste HTML and hear what a screen reader would announce. Instantly flags missing names, empty headings, and broken ARIA.","badge":"Pro Tool"},"howTo":{"title":"How to use this tool","step1":"Paste your HTML snippet into the editor below (or use the example pre-loaded).","step2":"Click Simulate to parse the markup and generate screen reader announcements.","step3":"Use Speak All to hear the announcements using your browser's text-to-speech engine.","step4":"Click the speaker icon next to any element to hear just that announcement.","step5":"Review flagged issues, each links to the relevant WCAG criterion and fix guidance."},"inputMode":{"pasteHtml":"Paste HTML","fetchUrl":"Fetch URL"},"inputs":{"htmlLabel":"HTML Input","urlLabel":"Page URL","urlPlaceholder":"Https://example.com/page","urlNote":"The page HTML is fetched server-side. JavaScript-rendered content will not be visible, use Paste HTML mode for SPAs."},"actions":{"simulate":"Simulate","stop":"Stop","stopReading":"Stop reading","speakAll":"Speak All","fetching":"Fetching…","unlockPro":"Unlock with Pro, €999/yr","seeIncluded":"See what's included in Pro"},"stats":{"totalElements":"Total elements","landmarks":"Landmarks","passed":"Passed","issues":"Issues"},"tabs":{"issues":"Issues ({count})","landmarks":"Landmarks ({count})","all":"All ({count})"},"errors":{"fetchFailed":"Failed to fetch URL.","networkError":"Network error, could not reach the server."},"results":{"noIssues":"No issues found, all elements have accessible names and roles.","issuesFoundOne":"{count} issue found","issuesFoundOther":"{count} issues found","allPass":"All detected elements have accessible names and roles.","manualTestNote":"This tool checks programmatic accessibility, manual testing with a real screen reader is also required.","simulatorDisclaimer":"This simulator approximates screen reader announcements based on semantic HTML structure. It cannot replicate the actual behaviour of JAWS, NVDA, VoiceOver, or TalkBack, which have different virtual cursor modes, announcement patterns, and platform-specific quirks. Before publishing, test with at least two real assistive technologies. EN 301 549 §11.5.2 requires compatibility with actual assistive technology, not simulation.","fix":"Fix:","speakAnnouncement":"Speak this announcement","speakIssueTitle":"Hear how a screen reader announces this issue","speakLandmark":"Speak: {role} {text}","speakItem":"Speak: {label}","noLandmarks":"No landmarks detected","landmarksFoundOne":"{count} landmark, navigable by screen reader users","landmarksFoundOther":"{count} landmarks, navigable by screen reader users","noLandmarkElements":"No landmark elements found.","noLandmarkAdvice":"Screen reader users rely on landmark regions to navigate pages efficiently. Add <main>, <nav>, <header>, and <footer> to your page structure.","landmarkNavigation":"Screen reader landmark navigation","landmarkKeys":"NVDA: D cycles through landmarks. JAWS: R. VoiceOver: W. The Rotor (VoiceOver) / Elements list (JAWS) lists all landmarks.","allAnnouncementsOne":"All announcements ({count} element)","allAnnouncementsOther":"All announcements ({count} elements)","empty":"(empty)","issueShort":"Issue","speakIssuePrefix":"{role}. Issue: {issue}","speakElement":"{text}. {role}.","nonDescriptiveFix":"Replace \"{text}\" with text that describes the destination or purpose out of context."},"fixMap":{"linkNoName":"Add text content inside the <a> tag or use aria-label=\"destination description\".","buttonNoName":"Add visible text content or aria-label describing the button action.","imageNoAlt":"Add alt=\"description\" for informative images, or alt=\"\" for decorative images.","inputNoLabel":"Add <label for=\"inputId\">Label text</label> or use aria-label directly on the input.","emptyHeading":"Add meaningful text, or remove the element if it serves no structural purpose.","selectNoLabel":"Add <label for=\"selectId\"> or use aria-label on the select element.","dialogNoName":"Add aria-label=\"Dialog title\" or aria-labelledby pointing to a heading inside the dialog.","tableNoCaption":"Add <caption>Table description</caption> inside the table, or aria-label on the <table> element.","default":"Review this element and add appropriate accessible name or role."},"roles":{"link":"Link","button":"Button","image":"Image","checkbox":"Checkbox","radio":"Radio","textbox":"Textbox","headingLevel":"Heading level {level}","navigation":"Navigation","main":"Main","complementary":"Complementary","article":"Article","region":"Region","dialog":"Dialog","list":"List","listOrdered":"List (ordered)","listItem":"List item","disclosure":"Disclosure widget","table":"Table","columnHeader":"Column header","group":"Group","contentinfo":"Contentinfo","banner":"Banner","form":"Form","listbox":"Listbox"},"names":{"decorativeSkipped":"(decorative, skipped)","unnamedNavigation":"Unnamed navigation","mainContent":"Main content area","unnamedRegion":"Unnamed {regionRole}","labelledDialog":"Labelled dialog","unnamedDialog":"Unnamed dialog","itemsOne":"{count} item","itemsOther":"{count} items","unnamedDisclosure":"Unnamed disclosure","tableSize":"Table {rows} rows × {cols} columns","unnamedGroup":"Unnamed group","pageFooter":"Page footer","pageHeader":"Page header","unnamedForm":"Unnamed form"},"issuesText":{"linkNoName":"Link has no accessible name","linkNonDescriptive":"Non-descriptive link text: \"{text}\"","buttonNoName":"Button has no accessible name","imageNoAlt":"Image missing alt attribute","inputNoLabel":"Input has no accessible label","emptyHeading":"Empty heading","navNoName":"Navigation landmark has no accessible name, with multiple nav elements, users can't distinguish them","sectionNoLabel":"<section> without aria-label or title, announced as generic region, not useful for navigation","dialogNoName":"Dialog has no accessible name, screen reader users can't determine its purpose","tableNoCaption":"Table has no caption or aria-label, screen reader users can't identify its purpose before navigating it","emptyTableHeader":"Empty table header, column content has no announced header","fieldsetNoLegend":"Fieldset has no <legend>, form group purpose is not announced","selectNoLabel":"Select has no accessible label"},"wcag":{"linkPurpose":"WCAG 2.4.4 Link Purpose (In Context), Level AA","nameRoleValue":"WCAG 4.1.2 Name, Role, Value, Level A","nameRoleValueShort":"WCAG 4.1.2, Level A","nonTextContent":"WCAG 1.1.1 Non-text Content, Level A","infoAndRelationships":"WCAG 1.3.1 Info and Relationships, Level A","infoAndRelationshipsShort":"WCAG 1.3.1, Level A","headingsAndLabels":"WCAG 2.4.6 Headings and Labels, Level AA","identifyPurpose":"WCAG 1.3.6 Identify Purpose, Level AAA"},"export":{"docx":{"summaryHeading":"Summary","rowInputMethod":"Input method","valueInputPasted":"Pasted HTML","valueInputUrl":"URL fetch","rowScannedUrl":"Scanned URL","rowTotalElements":"Total elements analysed","rowIssuesFound":"Issues found","rowPassingElements":"Passing elements","rowLandmarksDetected":"Landmarks detected","issuesHeading":"Issues Found","issuesIntroOne":"{count} element has screen-reader accessibility issues. Each row shows the element role, the issue, the WCAG criterion, the offending HTML snippet, and the recommended fix.","issuesIntroOther":"{count} elements have screen-reader accessibility issues. Each row shows the element role, the issue, the WCAG criterion, the offending HTML snippet, and the recommended fix.","columnNumber":"#","columnRole":"Role","columnIssue":"Issue","columnWcag":"WCAG","columnHtmlSnippet":"HTML snippet","columnFix":"Fix","valueDash":",","noIssuesBody":"No issues detected, all parsed elements have accessible names and roles. This tool checks programmatic accessibility only; manual testing with a real screen reader (JAWS, NVDA, VoiceOver, TalkBack) is also required.","landmarksHeading":"Landmarks","landmarksIntroOne":"{count} landmark region detected. Screen reader users navigate pages by landmark, D in NVDA, R in JAWS, W in VoiceOver.","landmarksIntroOther":"{count} landmark regions detected. Screen reader users navigate pages by landmark, D in NVDA, R in JAWS, W in VoiceOver.","columnAccessibleName":"Accessible name","valueUnnamed":"(unnamed)","fullSequenceHeading":"Full Announcement Sequence","fullSequenceIntro":"All parsed elements in source order, showing how a screen reader would announce each one.","columnAnnouncement":"Announcement","columnStatus":"Status","valueEmpty":"(empty)","statusIssue":"Issue","statusOk":"OK","methodHeading":"Method","methodBody":"The HTML was parsed via DOMParser and walked recursively to extract semantic role, accessible name (aria-label, alt, title, label[for], legend, caption, or text content), and issues such as missing labels, empty headings, and non-descriptive link text. This is a programmatic approximation, actual screen-reader behaviour (JAWS, NVDA, VoiceOver, TalkBack) varies by virtual cursor mode and platform. Mapped to WCAG 2.2 SC 1.1.1, 1.3.1, 2.4.4, 2.4.6, 4.1.2; EN 301 549 V3.2.1 §9.1.1.1, §9.1.3.1, §9.2.4.4, §9.2.4.6, §9.4.1.2; and §11.5.2 (compatibility with assistive technology)."}},"example":{"mainNavLabel":"Main navigation","linkHome":"Home","linkAbout":"About us","linkClickHere":"Click here","h1":"Welcome to our website","imgAlt":"Happy customers using our product","inputNamePlaceholder":"Your name","labelEmail":"Email address","buttonSubmit":"Submit","linkProducts":"View products","linkReadMore":"Read more"}},"self-assessment":{"meta":{"title":"EAA Self-Assessment Tool (Directive 2019/882), Compliance Evidence","description":"Under Directive (EU) 2019/882 Article 4 and Annex I, generate legal-grade evidence through a guided scoping questionnaire, personalised tool list, RAG dashboard, and compliance report export."},"legalBasis":{"heading":"Legal basis for this assessment","intro":"This wizard generates evidence aligned to Directive (EU) 2019/882 Article 4 and Annex I, plus the accessibility-statement requirement in Directive (EU) 2016/2102 Article 9."},"header":{"title":"EAA Compliance Wizard","subtitle":"Guided compliance assessments · European Accessibility Act 2019/882","allAssessments":"← All assessments"},"home":{"title":"Your assessments","subtitle":"Each assessment is a named compliance review. Build it up over time, open tools, send results back, track your progress.","startNew":"+ Start a new assessment","nameYourAssessment":"Name your assessment","nameHint":"Give it a name that describes what you're assessing, e.g. \"ACME Website, Q2 2025\" or \"Mobile App v3 Assessment\".","namePlaceholder":"E.g. \"ACME Website, Q2 2025\"","createAssessment":"Create assessment →","cancel":"Cancel","continueAssessment":"Continue an assessment","toolsDone":"{completed} of {total} tools done · last updated {date}","open":"Open →","deleteConfirm":"Delete this assessment? This cannot be undone.","proFeature":"Pro feature","proFeatureBody":"The full wizard (dashboard, tool guidance, and report export) requires a Pro subscription. Click any assessment to continue or sign in.","howItWorks":{"step1Title":"Name & describe","step1Body":"Give your assessment a name and fill in your product, organisation, and auditor details.","step2Title":"Answer the questionnaire","step2Body":"A short guided questionnaire builds a personalised tool list, based on your product type, sector, and operator role under the EAA.","step3Title":"Work through your tool list","step3Body":"Your assessment page shows every tool you need as a tick-box checklist. Open each tool, run it, your result saves automatically.","step4Title":"Build your compliance report","step4Body":"Hit 'Build Compliance Report' to compile all results into a Word document and CSV for your Article 15 technical documentation."},"proFeatureNotice":{"label":"Pro feature","body":"The full wizard (dashboard, tool guidance, and report export) requires a Pro subscription. Click any assessment to continue or sign in."}},"howItWorks":{"step1Title":"Name & describe","step1Body":"Give your assessment a name and fill in your product, organisation, and auditor details.","step2Title":"Answer the questionnaire","step2Body":"A short guided questionnaire builds a personalised tool list, based on your product type, sector, and operator role under the EAA.","step3Title":"Work through your tool list","step3Body":"Your assessment page shows every tool you need as a tick-box checklist. Open each tool, run it, your result saves automatically.","step4Title":"Build your compliance report","step4Body":"Hit 'Build Compliance Report' to compile all results into a Word document and CSV for your Article 15 technical documentation."},"context":{"title":"About this assessment","assessmentLabel":"Assessment:","productName":"Product or service name *","productNamePlaceholder":"E.g. ACME Online Banking","orgName":"Organisation name *","orgNamePlaceholder":"E.g. ACME Financial Ltd","productUrl":"Product URL","productUrlPlaceholder":"Https://example.com","auditorName":"Auditor name","auditorNamePlaceholder":"Your name or team","assessmentDate":"Assessment date","testingMethodologyTitle":"Testing methodology (optional, for Article 15 technical file)","testingMethodologyHint":"These fields are included in your exported compliance report and strengthen your Article 15 technical documentation.","testingMethodology":"Testing methodology","testingMethodologyPlaceholder":"E.g. Manual expert review + automated scan (axe-core)","atUsed":"Assistive technologies used","atUsedPlaceholder":"E.g. NVDA 2024.1, VoiceOver iOS 17, JAWS 2024","evaluatorQualifications":"Evaluator qualifications","evaluatorQualificationsPlaceholder":"E.g. CPACC certified, 5 years EN 301 549 experience","priorComplaints":"Prior accessibility complaints received?","priorComplaintsPlaceholder":"E.g. None / 2 complaints in 2025 re: screen reader access","back":"← Back","continueToScoping":"Continue to scoping →"},"scoping":{"questionOf":"Question {current} of {total}","back":"← Back","next":"Next →","finishScoping":"Finish scoping →","buildPath":"Build my tool path →","microNotice":{"title":"ℹ Micro enterprise, Article 4(5) applies","body":"You are exempt from most <strong>product</strong> accessibility requirements under EAA Article 4(5). However, if you provide any digital services (website, app, streaming), full <strong>service</strong> requirements still apply. Sector-specific requirements (banking, e-commerce, transport) remain in full force regardless of size. Your tool list will be tailored accordingly."},"questions":{"productTypes":{"question":"What types of product or service are you assessing?","explanation":"Select all that apply, this determines which tools are included."},"operatorRoles":{"question":"What is your organisation's role in the supply chain?","explanation":"The EAA assigns different legal obligations per role."},"sectors":{"question":"Which sectors apply to your product?","explanation":"Specific EAA requirements exist for certain sectors beyond WCAG.","options":{"banking":{"label":"Banking and financial services","explains":"EAA Annex I Section IV(e), payment, authentication, and account services. Adds: Banking & Finance Checklist, CEFR B2 Readability Compliance Checklist (legal requirement), Banking Regulatory Cross-Reference (PSD2/CCD/MiFID II/GDPR), and forces Readability Analyser as mandatory."},"ecommerce":{"label":"E-commerce","explains":"EAA Annex I Section IV(g), full purchase journey including payment must be accessible. Adds E-Commerce Accessibility Checklist."},"transport":{"label":"Passenger transport services (air, rail, bus, waterborne)","explains":"EAA Annex I Section IV(c), ticketing, real-time info, and staffing accessibility. Adds Transport Accessibility Checklist. Article 5 cross-references existing transport regulations."},"ebook":{"label":"E-books or digital publications","explains":"EAA Annex I Section IV(f), EPUB Accessibility 1.1 required; DRM must not block accessibility features"},"emergency":{"label":"Emergency communications (112 services, emergency coordination, public alerting)","explains":"EAA Article 2(2)(c) + Annex I Section IV(a) paragraph 2, emergency communications have additional requirements beyond standard electronic communications: synchronised voice, RTT, and video to 112. Cannot claim disproportionate burden exemption for emergency comms requirements."},"sports":{"label":"Sports club, federation or league (digital surface, site, shop, ticketing, live media)","explains":"Falls under e-commerce (Annex I Section IV(g)) for the online shop and ticketing flow, and AVMS (Annex I Section IV(b)) if you publish live match commentary, goal videos, or audio description streams. Adds the E-Commerce Accessibility Checklist and the Sport Services Accessibility Checklist. For match programmes and ticket-confirmation PDFs, also tick 'We publish downloadable documents'. For captioned highlights and audio commentary streams, also tick 'We publish or distribute audio-visual media'."},"hotels":{"label":"Hotel, hostel or short-stay accommodation (online booking, room information, on-site services)","explains":"Falls under e-commerce (Annex I Section IV(g)) for the room-booking flow (search → date pick → room select → guest details → payment). Adds the E-Commerce Accessibility Checklist and the Hospitality Accessibility Checklist scoped to the booking journey, accessible-room disclosure and Annex V scope language for third-party booking engines. For menus, room-service documents and booking confirmation PDFs, also tick 'We publish downloadable documents'."},"none":{"label":"None of the above","explains":"General WCAG + EAA requirements apply"}},"subQuestions":{"sectionTitleSports":"A few quick follow-ups about your sport surfaces","sectionTitleHotels":"A few quick follow-ups about your hospitality surfaces","sports":{"ticketing":{"question":"Do you use a third-party ticketing widget?","explanation":"E.g. Eventbrite, Universe, Stripe Tap, Bilheteira Online. Affects the Annex V scope language and triggers the Vendor Accessibility Checklist deep link.","vendorLabel":"Vendor name","vendorPlaceholder":"E.g. Eventbrite","yes":"Yes, third-party widget","no":"No, built in-house"},"liveMedia":{"question":"Do you publish live match content (commentary, goal videos, match-day highlights)?","explanation":"Affects the Annex I Section IV(b) (AVMS) applicability and forces caption / transcript checks.","yes":"Yes","no":"No"},"documents":{"question":"Do you publish match programmes or ticket confirmations as downloadable PDFs?","explanation":"If yes, the PDF Accessibility Checklist will be surfaced as a conditional tool.","yes":"Yes","no":"No"}},"hotels":{"bookingType":{"question":"Is your booking flow on-domain or hosted by a third-party booking engine?","explanation":"Third-party engines (Booking.com, Expedia, Hotelbeds, Cloudbeds, SiteMinder) trigger Annex V scope language and the Vendor Accessibility Checklist deep link.","vendorLabel":"Booking-engine vendor name (if applicable)","vendorPlaceholder":"E.g. Booking.com","onDomain":"On-domain, we host the booking flow","thirdParty":"Third-party booking engine"},"documents":{"question":"Do you publish menus, room directories, or welcome packs as PDFs?","explanation":"If yes, the PDF Accessibility Checklist will be surfaced as a conditional tool.","yes":"Yes","no":"No"},"accessibleRoomFilter":{"question":"Does your room-search UI include a filter for accessible-room availability?","explanation":"Affects the Annex I §IV(g) accessible-room availability disclosure check.","yes":"Yes","no":"No","notApplicable":"We don't have any accessible rooms"}},"vendorPrefillHint":"We'll pre-fill the Vendor Accessibility Checklist with this vendor name, saves time when you send it out.","thirdPartyScopeHint":"We'll add a third-party scope sentence to your accessibility statement export naming this vendor."}},"orgSize":{"question":"How large is your organisation?","explanation":"Size affects burden exemption eligibility."},"claimBurden":{"question":"Are you considering a disproportionate burden exemption?","explanation":"Exemptions require a formal four-criteria Annex VI assessment, you cannot skip it."},"preJune2025":{"question":"Was this product or service already on the market before 28 June 2025?","explanation":"EAA Article 32 contains transition provisions that may affect your compliance timeline."},"usesBiometric":{"question":"Does your product or service use biometric data processing or AI-based automated decision-making that affects users?","explanation":"Biometric systems (face recognition, fingerprint, voice ID) and AI decision-making create specific accessibility barriers."},"isMultilingual":{"question":"Does your product or service support multiple languages?","explanation":"Accessibility features must work correctly in every supported language, screen reader pronunciation, translated alt text, ARIA labels, and error messages."},"priorCert":{"question":"Does your organisation already hold EN 301 549 conformance test results or a third-party accessibility audit?","explanation":"Existing test evidence can be referenced in your Article 15 technical documentation, it does not eliminate the need to address failures, but may reduce the scope of new testing required."}}},"dashboard":{"ragLabels":{"green":"Likely Compliant","amber":"Partial, Action Required","red":"Non-Compliant, Critical Gaps","grey":"In Progress"},"buildReport":"Build Compliance Report","editScoping":"Edit scoping","toolTiers":{"mandatory":"Mandatory","recommended":"Recommended","conditional":"Conditional"},"tierLabels":{"mandatory":"Required by law","recommended":"Recommended","conditional":"Applicable"},"progressTitle":"Tool checklist progress","progressComplete":"{percent}% complete","progressReady":"{percent}% complete, ready to build report","ragSummary":"{passes} pass · {partials} partial · {fails} fail · {pending} pending","checklistTitle":"Your tool checklist","checklistHint":"Click any tool name for guidance · Open tool to run it","buildReportArrow":"Build Compliance Report →","notices":{"microTitle":"Micro enterprise, Article 4(5) partial exemption applies","microBody":"Under EAA Article 4(5), micro enterprises (<10 employees, <€2m turnover) are exempt from the product accessibility requirements in Annex I. This means hardware product obligations are significantly reduced. <strong>However:</strong> if you provide any digital services (website, app, streaming), full service requirements still apply, Article 4(5) only covers products, not services. If you provide services in regulated sectors (banking, e-commerce, transport), all sector-specific requirements remain in full force.","microFooter":"Member states may also exempt micro service providers from the disproportionate burden assessment procedure under Article 22, check your national transposition law.","transitionTitle":"Article 32 transition provisions, grace period may apply","transitionProducts":"<strong>Products (Article 32(1)):</strong> Products already placed on the EU market before 28 June 2025 may continue to circulate until <strong>28 June 2030</strong> without modification. However, any version updated or replaced after June 2025 must comply immediately. Document the original market placement date in your Article 15 technical file.","transitionServices":"<strong>Services (Article 32(2)):</strong> Service contracts concluded before 28 June 2025 may continue under existing terms until <strong>28 June 2030</strong>. New contracts, new services, and significantly updated services must comply now. Track which service components are new vs. Pre-existing.","transitionFooter":"The grace period does not apply to new versions, significant updates, or new contracts signed after 28 June 2025.","priorCertFullTitle":"Full prior audit recorded, reference in Article 15 technical file","priorCertPartialTitle":"Partial prior test results recorded, complete remaining coverage below","priorCertFullBody":"Your existing EN 301 549 audit report should be referenced in your Article 15 technical documentation as the primary conformance evidence. Use this assessment to verify no regressions since the audit and to track remediation of failures found. Any failures identified in the prior audit must still be addressed and re-tested.","priorCertPartialBody":"Your partial test results can be referenced in your Article 15 technical file for the components already tested. This assessment covers the remaining scope. Ensure prior results and this assessment are compiled together in your technical documentation.","publicSectorTitle":"Public sector, two parallel accessibility regimes apply","publicSectorBodyA":"<strong>Web Accessibility Directive (2016/2102):</strong> Already applies to your websites and mobile apps. Requires WCAG 2.1 AA compliance, an accessibility statement, and annual monitoring. This obligation runs in parallel with EAA and does not disappear when EAA comes into force.","publicSectorBodyB":"<strong>EAA Article 26, Procurement:</strong> When procuring ICT products and services, you must include EN 301 549 accessibility requirements in technical specifications. Use the VPAT Editor and Generic ICT Requirements tools to structure your procurement specifications correctly. Failure to include accessibility requirements in public tenders may constitute a breach of EU procurement law.","b2bTitle":"B2B services, verify EAA scope with your legal adviser","b2bBody":"The EAA's service requirements primarily target consumer-facing services in the listed sectors (Article 2(2)). If your service operates exclusively in business-to-business (B2B) contexts with no direct consumer users, some EAA obligations may not apply. However, the boundary is not always clear, services that touch consumer processes through a B2B chain may still be in scope. If you are unsure whether the EAA applies to your service, seek legal advice before assuming you are out of scope. <strong>When in doubt, comply.</strong>","selfAssessmentTitle":"Self-assessment only, does not replace third-party verification","selfAssessmentBody":"Under EAA Annex IV, self-assessment is permitted. However, market surveillance authorities may challenge results at any time. Tools marked <strong>⚠ Consider 3rd-party</strong> below require independent verification for physical products and electronic communications services before EU market placement."},"confidence":{"heading":"Assessment Confidence Level","gradeOf":"Confidence Grade {grade} of A","gradeAInitialLabel":"Initial Self-Assessment","gradeAInitialDesc":"Your assessment is based on self-review using structured tooling. This satisfies Annex IV requirements as a starting point. Strengthen your position by adding user testing or commissioning a third-party audit.","gradeAFullLabel":"Audit-Grade, Full Independent Verification","gradeAFullDesc":"Your assessment combines independent third-party audit, user testing with disabled participants, and multi-AT interoperability testing. This represents the highest standard of evidence for market surveillance authorities.","gradeBLabel":"Professionally Verified","gradeBDesc":"Your assessment includes a third-party audit plus additional evidence from user testing or AT interoperability testing. This is a strong evidence base under EAA market surveillance.","gradeCLabel":"Improved Self-Assessment","gradeCDesc":"Your assessment goes beyond basic self-review with either independent audit or a combination of user testing and AT interoperability evidence. Adding the remaining verification steps will further strengthen your position.","gradeDLabel":"Documented Self-Assessment","gradeDDesc":"Your assessment includes structured evidence from user testing or AT interoperability testing, going beyond tool-only review. Consider commissioning a third-party audit to achieve a higher grade.","checkThirdParty":"Independent third-party EN 301 549 audit","checkUserTesting":"User testing with disabled participants","checkATInterop":"Multi-AT interoperability testing","thirdPartyToolsProgress":"{done}/{total} tools with recommended third-party verification completed","thirdPartyConfirm":"I have commissioned or completed an independent third-party EN 301 549 audit"},"remediation":{"heading":"Remediation Re-Assessment Schedule","intro":"Schedule re-testing dates for failed tools. Re-run each tool after fixes are applied and update the result.","retestScheduled":"Retest scheduled: {date}","noRetestScheduled":"No retest scheduled","retestCta":"Re-test ↗","footer":"After remediation, re-run each tool and update the result to Pass or Partial. The assessment confidence level will update accordingly."},"criticalFailures":{"heading":"⛔ Critical failures, must fix before 28 June 2025","reopenCta":"Re-open ↗"},"annexIv":{"heading":"📁 Annex IV Technical File, what manufacturers must retain","body":"Under EAA Article 7(3) and Annex IV, manufacturers must draw up and retain a technical file before placing a product on the market. The file must include: (1) a description of the product and its intended use; (2) a list of EN 301 549 chapters applied; (3) a description of solutions adopted to meet accessibility requirements; (4) copies of test reports or risk assessments; (5) a copy of the EU Declaration of Conformity; (6) where applicable, documentation of any Article 14 burden exemptions. Retain the technical file for <strong>5 years</strong> after the product is last placed on the market.","footer":"The compliance report exported from this wizard forms part of item (4), test reports and risk assessments."},"additionalResults":{"heading":"Additional results","intro":"Results from tools outside your scoped list, included in the compiled report.","removeTitle":"Remove"},"buildReportCta":{"title":"Ready to compile your compliance report?","noneDone":"Complete some tools first, then build your report.","someRemaining":"{remaining} tool still pending, you can build now or finish them first.","someRemainingPlural":"{remaining} tools still pending, you can build now or finish them first.","allDone":"All tools complete. Build your full compliance report.","cta":"Build Compliance Report →"}},"toolStatus":{"pass":"Pass","partial":"Partial","fail":"Fail","na":"N/A","pending":"Not started"},"toolCard":{"thirdPartyBadge":"⚠ 3rd-party recommended","art32GraceBadge":"⏱ Art.32 grace may apply","ragMin":"~{mins} min","notes":"Notes","notesWithCount":"Notes ({count})","openTool":"Open tool ↗","noNotesYet":"No notes yet, add your first note below.","addNotePlaceholder":"Add a note, progress update, issue found, fix applied...","markStatusFirst":"Mark a status first, then add notes","addNote":"Add"},"toolDetail":{"regulatoryBasis":"Regulatory Basis","whatYouNeed":"What You Need","howToUse":"How to Use","estimatedTime":"Estimated Time","minutes":"{mins} minutes","openTool":"Open Tool →","thirdPartyRecommended":"Independent third-party verification recommended","backToDashboard":"← Back to dashboard","lastResultRecorded":"Last result recorded {date}","whyRequired":"Why this is required","steps":"Steps","thirdPartyTitle":"Third-party verification recommended","howResultsTitle":"How results get back","howResultsBody":"When you open this tool, the <strong>blue \"Add to assessment\" widget</strong> appears at the top of the page. Select this assessment from the dropdown, set your result, and save, it will appear here automatically.","openToolNamed":"Open {name} ↗"},"manualEntry":{"addCta":"+ Add result from any other tool, site tools, third-party tests, manual evaluations","title":"Add a result","subtitle":"Pick from the tool suite below, or enter any custom tool or third-party test.","closeLabel":"Close add-result panel","savedMessage":"Saved, result added to your assessment.","pickLabel":"Pick from tool suite","searchPlaceholder":"Search tools...","noMatch":"No tools match \"{filter}\"","customLabel":"Or enter custom / third-party tool","customPlaceholder":"E.g. Axe DevTools scan, WAVE report, Manual keyboard test...","changeTool":"Change ×","resultLabel":"Result","notesLabel":"Notes (optional)","notesPlaceholder":"Issues found, page URLs, remediation steps...","save":"Save to assessment →","cancel":"Cancel","status":{"pass":"Pass","partial":"Partial","fail":"Fail","na":"N/A"}},"export":{"title":"Build Compliance Report","subtitle":"Compile all assessment results into a structured compliance report for your Article 15 technical documentation.","downloadWord":"Download Word (.docx)","downloadCsv":"Download CSV","downloadJson":"Download JSON","backToDashboard":"← Back to dashboard","complianceReportTitle":"Compliance Report, {name}","summary":{"labelPass":"Pass","labelPartial":"Partial","labelFail":"Fail","labelPending":"Pending"},"csvSection":{"title":"Results spreadsheet (CSV)","description":"All tool results, notes, and regulatory references.","proOnly":"Pro only, Upgrade to export","proOnlyTitle":"Upgrade to Pro to export documents","cta":"Download CSV"},"wordSection":{"title":"Full compliance report (Word)","proBadge":"Pro","description":"Formatted Word document with summary, results table, critical gaps, and Article 15 notice.","cta":"Download Word"},"perToolLinks":"Open individual tools","samplePreview":{"name":"Self-Assessment","description":"The Self-Assessment produces a compliance report with a 30-point score, detailed findings, and remediation priorities. Exported as Word or PDF with legal-grade metadata."},"word":{"documentTitle":"EAA Compliance Assessment Report","assessmentLabel":"Assessment: {name}","organisationLabel":"Organisation: {name}","productLabel":"Product: {name}","urlLabel":"URL: {url}","auditorLabel":"Auditor: {name}","assessmentDateLabel":"Assessment Date: {date}","testingMethodologyLabel":"Testing Methodology: {value}","atUsedLabel":"Assistive Technologies Used: {value}","evaluatorQualificationsLabel":"Evaluator Qualifications: {value}","priorAuditLabel":"Prior EN 301 549 Audit: {value}","priorAuditFull":"Full audit held, referenced in technical file","priorAuditPartial":"Partial results held, referenced in technical file","priorAuditNone":"None","notSpecified":"Not specified","overallStatusHeading":"Overall Compliance Status","overallStatusSummary":"Pass: {passes} · Partial: {partials} · Fail: {fails} · Pending: {pending}","resultsHeading":"Results by Tool","tableHeaderTool":"Tool","tableHeaderBasis":"Regulatory Basis","tableHeaderStatus":"Status","tableHeaderNotes":"Notes","criticalGapsHeading":"Critical Gaps, Immediate Action Required","basisLine":"Basis: {basis}","noNotesRecorded":"No notes recorded.","additionalResultsHeading":"Additional Results","additionalResultsIntro":"Results from supplementary tools and manual evaluations:","additionalHeaderTool":"Tool / Test","additionalHeaderStatus":"Status","additionalHeaderNotes":"Notes","additionalHeaderDate":"Date","legalScopeHeading":"Important, Legal Scope and Third-Party Verification","selfAssessmentNoticeLabel":"SELF-ASSESSMENT NOTICE:","selfAssessmentNoticeBody":"This document is a self-assessment produced using an online guidance tool. It does not constitute a formal conformance evaluation by a qualified third party. Under Annex IV of Directive 2019/882, manufacturers may use internal production control for EAA conformity. However, market surveillance authorities may challenge self-assessments at any time.","thirdPartyLabel":"THIRD-PARTY VERIFICATION:","thirdPartyBody":"For products placed on the EU market, a formal test report from a qualified EN 301 549 accessibility evaluator is strongly recommended to support Article 15 technical documentation. For physical hardware (ATMs, kiosks, terminals) and electronic communications services (real-time text, total conversation), independent technical verification may be required by national market surveillance authorities before market placement.","article15Label":"ARTICLE 15 DOCUMENTATION:","article15Body":"Under Article 15 of Directive 2019/882, economic operators must maintain technical documentation and make it available to market surveillance authorities on request. This document should be supplemented with formal test reports, evidence of applied harmonised standards (EN 301 549 (2021-03)), and where applicable, a completed EU Declaration of Conformity (Annex IV).","footer":"Generated by AccessibilityRef EAA Compliance Wizard · {date}"},"docx":{"contextHeading":"Assessment context","scopingHeading":"Scoping responses","overallResultHeading":"Overall result","perTierHeading":"Per-tier breakdown","failedToolsHeading":"Failed tools, required remediation","failedToolsIntro":"{count, plural, one {# tool result} other {# tool results}} marked as Fail. Each row shows the tool, regulatory basis, plain-language explanation, and operator notes.","partialToolsHeading":"Partially conforming tools","passingToolsHeading":"Passing tools","fullRegisterHeading":"Full tool register, every tool considered","fullRegisterIntro":"Every tool selected for this assessment, with tier, status, regulatory basis and the operator's latest note.","additionalResultsHeading":"Additional tool results (added outside the wizard)","noteHistoryHeading":"Note history (audit trail)","noteHistoryIntro":"Every operator note recorded against each tool, with timestamp. Provides a chronological audit trail required for Annex IV traceability.","methodHeading":"Method","methodBody":"Self-assessment of EAA conformance built from {count} tier-classified tools (mandatory, recommended, conditional) selected from a library of WCAG 2.2 / EN 301 549 / EAA Annex I checks. Each tool's status (Pass / Partial / Fail / N/A) and operator notes are aggregated into a RAG (red/amber/green) overall outcome. Mapped to EAA Article 13 (Technical Documentation), Article 15 (Conformity Assessment) and Annex IV. Standards covered: WCAG 2.2 Level AA, EN 301 549 V3.2.1 (2021-03), Directive (EU) 2019/882 Annex I.","rowAssessmentName":"Assessment name","rowRunId":"Run ID","rowOrganisation":"Organisation","rowProductService":"Product / Service","rowProductUrl":"Product URL","rowAuditor":"Auditor","rowAuditDate":"Audit date","rowCreated":"Created","rowLastUpdated":"Last updated","rowProductTypes":"Product types","rowOperatorRoles":"Operator roles","rowSectors":"Sectors","rowOrgSize":"Organisation size","rowExistingComplaints":"Existing complaints?","rowClaimBurden":"Claim disproportionate burden?","rowPreJune2025":"On market before 28 June 2025? (Article 32 transition)","rowUsesBiometric":"Uses biometric/AI automated decisions?","rowMultilingual":"Multilingual product?","rowPriorCert":"Prior EN 301 549 conformance test results?","rowThirdPartyConfirmed":"Third-party audit confirmed?","rowTestingMethodology":"Testing methodology","rowAtUsed":"Assistive technologies used","rowEvaluatorQualifications":"Evaluator qualifications","rowRagStatus":"RAG status","rowToolsSelected":"Tools selected","rowAdditionalResults":"Additional tool results (outside wizard scope)","headerQuestion":"Question","headerResponse":"Response","headerTier":"Tier","headerTotal":"Total","headerTool":"Tool","headerRegulatoryBasis":"Regulatory basis","headerWhyItMatters":"Why it matters","headerOperatorNotes":"Operator notes","headerStatus":"Status","headerNotes":"Notes","headerCompletedAt":"Completed at","headerDate":"Date","headerNote":"Note","statusPass":"Pass","statusPartial":"Partial","statusFail":"Fail","statusNa":"N/A","statusPending":"Pending","tierMandatory":"Mandatory","tierRecommended":"Recommended","tierConditional":"Conditional","ragGreen":"GREEN, Likely conformant","ragAmber":"AMBER, Partial conformance","ragRed":"RED, Critical gaps","valueUnnamed":"(unnamed)","valueNotSet":"(not set)","valueNoneSelected":"(none selected)","valueYes":"Yes","valueNo":"No"}}},"site-scanner":{"meta":{"title":"EAA Site Scanner, Free Instant Accessibility Audit","description":"Enter any URL and get an instant accessibility score. 27 automated checks mapped to WCAG 2.2 and EN 301 549, plus a Lighthouse real-browser second opinion. Free, no login required."},"header":{"title":"EAA Site Scanner","lede":"Enter any URL and get an instant accessibility score with specific findings mapped to WCAG 2.2 and EN 301 549.","howItWorks":"How it works:","howItWorksBody":"We fetch your page server-side and run 27 automated accessibility checks across headings, images, landmarks, forms, links, ARIA, contrast (static + Lighthouse), HTML conformance, language tagging, accessibility-statement discovery, and stack-specific known issues. Results in 10–25 seconds. For single-page apps (React, Angular, Vue) we run a Lighthouse second opinion against the rendered DOM, so the score isn't penalised by client-side rendering. Pro users can also run a Pa11y deep scan with the axe-core ruleset for an independent fourth verdict."},"input":{"placeholder":"Https://example.com","scan":"Scan","scanning":"Scanning..."},"cached":{"label":"Showing cached result (up to 24h old). Pushed an accessibility fix recently?","forceFresh":"Force fresh scan","freshHint":"Cached result, scan again for fresh data"},"errorPrefix":"Error:","botWall":{"cardTitle":"This site blocks automated scans ({vendor})","cardBody":"The Site Scanner runs from our servers, and your target site is configured to block server traffic. That is a security choice on their side, not a fault in your site. To audit this page, run the Live Page Bookmarklet from your own browser instead.","vendor":{"cloudflare":"Cloudflare","akamai":"Akamai","datadome":"DataDome","unknown":"an enterprise bot-wall"},"useBookmarkletCta":"Run the Live Page Bookmarklet","retryCta":"Try a different URL","ownerAllowlistCta":"If you own this site, allowlist our scanner →"},"loading":"Scanning page and running accessibility checks...","csr":{"detected":"Client-side rendering detected"},"score":{"outOf":"Out of 100"},"summary":{"passed":"Passed","warnings":"Warnings","failed":"Failed"},"results":{"headingChecks":"Detailed Results, {count} Checks","noIssues":"No issues found, this check passed.","elementsAffected":"{count, plural, one {# element affected} other {# elements affected}}","ruleId":"Rule ID:","axeHeading":"Axe-core audit, {count} violations","axePassed":"Rules passed","axeIncomplete":"Incomplete","axeNotApplicable":"N/A","axeBlurb":"Rules powered by <axe>axe-core</axe>, Deque's open-source accessibility engine, the same rules library used by Google Lighthouse and Microsoft Accessibility Insights. Colour-contrast and target-size rules require rendered layout and are run by the Pro rendered-DOM scan instead.","axeNoViolations":"✓ No axe-core violations detected in the fetched HTML.","firstAffected":"First affected element","dequeDocs":"Deque docs: how to fix →","impactUnknown":"Unknown"},"scoreLegend":{"heading":"What This Score Means","gradeA":"A (90+)","gradeB":"B (80–89)","gradeC":"C (70–79)","gradeD":"D (60–69)","gradeF":"F (<60)","explanation":"This score reflects automated checks only. It covers HTML structure, semantics, and basic WCAG conformance, but cannot detect all accessibility issues. Keyboard navigation, colour contrast on rendered elements, screen reader compatibility, and cognitive accessibility require manual testing. A high score does not guarantee EAA compliance. A low score almost certainly indicates non-compliance."},"checkNames":{"lang":"Language Declaration","title":"Page Title","headings":"Heading Structure","images":"Image Alt Text","skip-link":"Skip Navigation Link","landmarks":"ARIA Landmarks","form-labels":"Form Labels","links":"Link Text Quality","tabindex":"Tab Order","viewport":"Zoom & Scaling","accessibility-statement":"Accessibility Statement","language-of-parts":"Language of Parts","autocomplete":"Identify Input Purpose","social-image-alt":"Social Card Image Alt Text","http-headers":"HTTP Header Signals","semantic-richness":"Semantic HTML Richness","inclusive-language":"Inclusive Language","well-known-accessibility":"Well-known Accessibility Endpoint","aria-usage":"ARIA Role & Attribute Validity","i18n-bcp47":"BCP-47 Language Tag","i18n-rtl":"Right-to-Left Direction","i18n-charset":"Document Charset","i18n-langswitch":"Language Switcher Presence","vnu-validation":"W3C HTML Conformance (Nu Validator)","css-contrast-static":"CSS Colour Contrast (Static)","known-issues":"Known stack-specific accessibility issues","psi-lighthouse":"PageSpeed Insights Lighthouse (real-DOM second opinion)"},"export":{"downloadJson":"Download JSON","downloadJsonHint":"Full scan results with all check details","filenamePrefix":"Site-scan-","summaryLine":"Score {score}/100 (Grade {grade}), {passed} passed, {warnings} warnings, {failed} failed","defaultNotes":"EAA Site Scanner: {url} scored {score}/100 (Grade {grade})","labels":{"scannedUrl":"Scanned URL","checksRun":"Checks run","overallScore":"Overall score","passed":"Passed","warnings":"Warnings","failed":"Failed"},"docx":{"summaryHeading":"Summary","rowGrade":"Grade","rowTotalChecks":"Total checks","rowPageTitle":"Page title","rowLanguage":"Page language","checksHeading":"Per-Check Results","colCheck":"Check","colScore":"Score","colStatus":"Status","colWcag":"WCAG","colIssues":"Issues","statusPass":"Pass","statusWarn":"Warn","statusFail":"Fail","noIssues":"No issues found","issuesHeading":"Detailed Findings","issuesIntro":"Each failing or warning check is listed below with every individual issue detected.","checkIssuesFor":"Issues, {checkName}","affectedElementsIntro":"Affected elements, {count} of {total} listed with full locator context (identifying attributes, parent landmark, form action, DOM path, and an outerHTML snippet) so the developer can locate each one in source.","affectedColElement":"Element","affectedColAttrs":"Identifying attributes","affectedColLocation":"Location on page","affectedColHtml":"HTML snippet","affectedFallbackNone":"(none)","affectedFallbackUnknown":"(unknown)","axeHeading":"Axe-core Violations","axeIntro":"Violations detected by Deque's axe-core rules engine. Counts indicate how many DOM nodes triggered each rule.","axeColImpact":"Impact","axeColRule":"Rule","axeColNodes":"Affected nodes","axeColWcag":"WCAG","axeColSample":"First sample","axeNoViolations":"No axe-core violations detected in the fetched HTML.","methodHeading":"Method","methodBody":"The page was fetched server-side and parsed against 27 automated structural and semantic checks. Each check is mapped to one or more WCAG 2.2 Success Criteria and EN 301 549 V3.2.1 clauses. The scan also runs an independent W3C Nu HTML conformance pass, a CSS contrast pass via PostCSS, and a Google Lighthouse second opinion against the rendered DOM (so client-side-rendered pages still receive an accurate score). Axe-core is run against the fetched HTML for a rules-engine verification. Pro users can additionally trigger a Pa11y deep scan (real Chromium + axe-core) for an independent fourth verdict."}},"nextSteps":{"buildTechnicalFile":"Build Technical File from this scan"},"pa11yPanel":{"heading":"Pa11y deep scan","proBadge":"Pro","subHeading":"Real-browser audit using industry-standard rules","idleIntro":"Pa11y is a free, open-source accessibility tester used by many auditors. It loads your page in a real Chromium browser, including any JavaScript-rendered content the static checks above can't see, and runs the axe-core ruleset, the same ruleset behind most browser-extension auditors and Google's Lighthouse.","expanderTitle":"When should I use this? What will I see?","useItWhenHeading":"Use it when…","useItWhenItem1":"Your site is a single-page app (React, Vue, Angular, Svelte, etc.), the static scan above marks many checks as \"Unable to verify, page uses client-side rendering.\" This bypasses that.","useItWhenItem2":"The page only renders content after a fetch / cookie banner / authentication step.","useItWhenItem3":"You want an independent second opinion against an industry-recognised ruleset before saving the evidence for your Technical File.","whatYoullSeeHeading":"What you'll see","whatYoullSeeIntro":"Each finding is classified as one of:","errorLabel":"Error","errorDescription":"A clear WCAG violation (e.g. An image with no alt text on a meaningful image). Fix before publication.","warningLabel":"Warning","warningDescription":"A probable violation that needs human judgement (e.g. An alt text that looks suspicious). Review and decide.","noticeLabel":"Notice","noticeDescription":"A manual-check reminder. Pa11y can't determine pass/fail automatically; you need to verify yourself.","howLongHeading":"How long does it take?","howLongBody":"Typically 20–45 seconds. The first scan of the day on this service can take an extra ~30 s while the browser warms up. Repeat scans of the same URL within 24 h return instantly from cache.","whyOptInHeading":"Why isn't this on by default?","whyOptInBody":"Pa11y is much more expensive to run than the static checks (it boots a full Chromium per scan), so it's opt-in. It also does not work behind login walls, for those, use the bookmarklet instead.","runButton":"Run Pa11y deep scan","queuedHeadlineWithEta":"Waiting in queue, position {position}, ~{etaSeconds} s estimated wait","queuedHeadlineNoEta":"Waiting in queue, position {position}","queuedBody":"Pa11y runs one scan at a time so each request gets the full resources of a real browser. Your scan will start automatically when it reaches the front of the line. Elapsed: {elapsed} s.","runningHeadline":"Scanning your page… {elapsed} s elapsed","runningBody":"A real Chromium browser is loading your URL, waiting for any JavaScript to finish, and applying the axe-core ruleset against the fully rendered page. Typical duration: 20–45 seconds for a standard page.","doneHeadlinePrefix":"Pa11y completed.","doneNoIssues":"No issues found against the WCAG 2.1 AA ruleset.","doneSummary":"Found {count, plural, one {# item} other {# items}}: {errors} error, {warnings} warning, {notices} notice.","doneLegendErrorBold":"Errors","doneLegendErrorBody":"Are clear violations to fix before publication.","doneLegendWarningBold":"Warnings","doneLegendWarningBody":"Need human judgement.","doneLegendNoticeBold":"Notices","doneLegendNoticeBody":"Are manual-check reminders, Pa11y can't determine pass/fail for these. All findings are included in your downloaded evidence below.","groupErrorsTitle":"Errors, must be fixed ({count})","groupErrorsIntro":"Clear violations of WCAG. These should be fixed before publishing the page or before signing off the Statement of Accessibility.","groupWarningsTitle":"Warnings, need human review ({count})","groupWarningsIntro":"Probable violations whose verdict depends on context. Review each one, sometimes the page is fine, sometimes it isn't.","groupNoticesTitle":"Notices, manual checks ({count})","groupNoticesIntro":"Items Pa11y can't decide automatically. You need to perform the check yourself (often a visual or behavioural test).","chipError":"Error","chipWarning":"Warning","chipNotice":"Notice","elementSelectorLabel":"Element selector","showHtmlContext":"Show HTML context","ruleCodeExpander":"Rule code (for developers)","ruleCodeUnderstandingLink":"Understanding WCAG {sc} ↗","ruleCodeTechniqueLink":"Technique {id} ↗","failedHeadline":"Pa11y scan unavailable","failedNotConfigured":"Pa11y service not configured on this deployment.","failedSignIn":"Sign in (Pro) to run a deep accessibility scan.","failedProRequired":"Pa11y deep scan requires a Pro subscription.","failedQueueFull":"Queue is full ({max} waiting). Try again in ~90 seconds.","failedUnexpected":"Unexpected error (HTTP {status})","failedBadShape":"Unexpected response shape from server.","failedRetry":"Retry","failedUpgrade":"Upgrade to Pro","externalLanguageNote":"Pa11y issue text is provided by the open-source Pa11y / axe-core engines in English."},"psiDetail":{"auditsBelowTarget":"{count, plural, one {# Lighthouse audit} other {# Lighthouse audits}} below target.","lighthouseVersion":"Lighthouse {version}","strategyLabel":"Strategy: {strategy}","cachedBadge":"Cached (24h)","failChip":"Fail","affectedElementsShown":"Affected elements ({shown})","affectedElementsOfTotal":"Affected elements ({shown} of {total})","externalLanguageNote":"Lighthouse audit text is provided by Google's PageSpeed Insights in English."}},"software-checklist":{"meta":{"title":"Non-Web Software Accessibility Checklist, EN 301 549 Chapter 11","description":"EN 301 549 Chapter 11 compliance checklist, verify that your non-web software (desktop, native, and installed applications) meets European Accessibility Act requirements."},"header":{"title":"Non-Web Software Accessibility Checklist","subtitle":"EN 301 549 Chapter 11, Desktop, Native & Installed Applications"},"description":"EN 301 549 Chapter 11 compliance checklist, verify that your non-web software (desktop, native, and installed applications) meets European Accessibility Act requirements.","features":{"f1":"EN 301 549 Chapter 11 full coverage","f2":"25 checkpoints across platform API, keyboard, visual, screen reader, errors & installation","f3":"Pass / Partial / Fail / N/A with notes per item","f4":"How-to-test guidance and common failures for every checkpoint","f5":"Links to relevant testing tools on AccessibilityRef","f6":"Progress auto-saved in your browser","f7":"Export Word report with notes","f8":"Direct links to EAA Directive and EN 301 549"},"categories":{"api":{"label":"Platform Accessibility API","description":"EN 301 549 §11.5, Software must use the platform accessibility API to expose UI information to assistive technology."},"keyboard":{"label":"Keyboard Navigation","description":"EN 301 549 §11.1.2.1 (maps to WCAG 2.1.1), All functionality must be keyboard-operable."},"visual":{"label":"Visual Accessibility","description":"WCAG 1.3-1.4 applied to software UI, contrast, resizing, colour use."},"screen-reader":{"label":"Screen Reader Compatibility","description":"Verification with platform screen readers, NVDA, JAWS, Narrator, VoiceOver."},"error":{"label":"Error Handling & Recovery","description":"WCAG 3.3 applied to software, error identification, suggestions, and recovery."},"install":{"label":"Installation & Updates","description":"The installation and update process must itself be accessible."}},"items":{"pa1":{"text":"All UI elements expose an accessible name via the platform accessibility API.","guidance":"On Windows, use UI Automation (UIA) or MSAA. On macOS, use NSAccessibility. On Linux, use ATK/AT-SPI. Every control must have a programmatic name.","testMethod":"Run the Accessibility Insights for Windows inspect tool (or Xcode Accessibility Inspector on macOS). Hover over each UI element and verify that the 'Name' property is populated with a meaningful, descriptive string. Check buttons, inputs, icons, and custom controls. If any interactive element has an empty or generic name (e.g. 'button1'), this fails.","commonFailures":{"f1":"Icon-only toolbar buttons have no accessible name, screen reader says 'button'","f2":"Custom-drawn controls expose no name to the accessibility API at all","f3":"Auto-generated names like 'textBox47' are used instead of meaningful labels","f4":"Accessible name is set to the internal variable name rather than user-facing text"}},"pa2":{"text":"All UI elements expose their role (button, checkbox, text field, etc.).","guidance":"Custom-drawn controls must map to standard accessibility roles. A painted rectangle acting as a button must expose role='button' to the accessibility API.","testMethod":"Using Accessibility Insights or the platform inspection tool, check the 'Role' or 'ControlType' property of each UI element. Verify that buttons report as 'button', checkboxes as 'checkbox', text fields as 'edit', etc. Pay special attention to custom-drawn controls, if a clickable area reports role='pane' or 'group' instead of 'button', this fails.","commonFailures":{"f1":"Clickable labels are exposed as static text instead of role='button'","f2":"Custom dropdown reports as a generic 'pane' instead of 'combobox'","f3":"Toggle switches have no role, screen reader cannot identify them as interactive","f4":"Entire canvas-rendered UI has a single role='image' with no child elements"}},"pa3":{"text":"State changes (checked, expanded, selected, disabled) are programmatically exposed.","guidance":"When a checkbox is toggled or a tree node expanded, the state change must be announced by the screen reader via the accessibility API.","testMethod":"Enable a screen reader (NVDA on Windows, VoiceOver on macOS). Interact with checkboxes, toggles, expandable tree nodes, and accordion panels. Listen for state announcements, 'checked', 'unchecked', 'expanded', 'collapsed', 'selected', 'disabled'. If the screen reader does not announce state changes when you interact with controls, this fails.","commonFailures":{"f1":"Checkbox toggles visually but screen reader still says 'unchecked'","f2":"Tree node expands but screen reader does not announce 'expanded'","f3":"Disabled buttons appear greyed out but still report as enabled to assistive technology","f4":"Tab selection changes visually but the selected tab is not announced"}},"pa4":{"text":"Parent-child relationships between UI elements are exposed.","guidance":"A list must expose its items as children. A tab panel must be associated with its tab. This enables screen reader navigation of complex structures.","testMethod":"Using the accessibility tree viewer (Accessibility Insights tree view, or Xcode Accessibility Inspector hierarchy), examine complex UI structures: lists, tables, tab panels, tree views, menus. Verify that parent-child relationships are correctly represented, list items are children of the list, table cells are children of rows, menu items are children of the menu. If items appear as flat siblings with no hierarchy, this fails.","commonFailures":{"f1":"List items are exposed as independent elements with no parent list container","f2":"Tab panels are not associated with their corresponding tab, screen reader cannot link them","f3":"Table structure is flat, cells are not grouped into rows and columns","f4":"Menu items are siblings of the menu bar rather than children of their submenu"}},"pa5":{"text":"Text content is programmatically determinable (caret position, selection, attributes).","guidance":"Screen readers need to read, navigate, and select text within text areas and documents. The accessibility API must expose text content and attributes.","testMethod":"Open a text editing area in the application with a screen reader active. Type some text, then use screen reader commands to read by character, word, and line. Select a range of text and verify the screen reader announces the selection. Check that bold, italic, and other formatting attributes are announced. If the screen reader cannot read or navigate text content, this fails.","commonFailures":{"f1":"Custom text editor renders text as pixels, screen reader reads nothing","f2":"Caret position is not tracked by the accessibility API, breaking character-by-character navigation","f3":"Text selection is visual only, screen reader does not announce what is selected","f4":"Formatting attributes (bold, italic, heading level) are not exposed to assistive technology"}},"kb1":{"text":"All functionality is accessible using the keyboard alone.","guidance":"Every action, opening menus, activating buttons, navigating trees, editing content, must work without a mouse. Test with keyboard only, mouse unplugged.","testMethod":"Disconnect the mouse. Starting from application launch, attempt every workflow using only the keyboard: open menus (Alt or F10), activate buttons (Enter/Space), navigate lists and trees (arrow keys), switch tabs (Ctrl+Tab), access toolbars, and complete any form or dialog. Document any action that cannot be performed without a mouse.","commonFailures":{"f1":"Drag-and-drop is the only way to reorder items, no keyboard alternative exists","f2":"Right-click context menu has no keyboard equivalent (Shift+F10 or Menu key does nothing)","f3":"Ribbon or toolbar cannot be reached via keyboard, requires mouse click","f4":"Canvas-based drawing tools have no keyboard-accessible alternative workflow"}},"kb2":{"text":"No keyboard traps exist, focus can always be moved away.","guidance":"Dialogs, panels, and embedded controls must not trap keyboard focus. The user must always be able to Tab or Escape away.","testMethod":"Tab through the entire application interface. At each stop, verify you can move focus away using Tab, Shift+Tab, Escape, or arrow keys. Pay special attention to modal dialogs, embedded media players, code editors, rich text editors, and third-party plugin areas. If focus enters a region and cannot be moved out by any keyboard method, this is a keyboard trap.","commonFailures":{"f1":"Embedded PDF viewer traps focus, Tab cycles within the viewer with no escape","f2":"Modal dialog has no close mechanism via keyboard, Escape does nothing","f3":"Rich text editor captures all keyboard input including Tab, preventing exit","f4":"Third-party charting component traps focus with no documented keyboard exit"}},"kb3":{"text":"Keyboard focus indicator is clearly visible on all focused elements.","guidance":"A visible ring, outline, or highlight must indicate which element has focus. Never suppress the focus indicator without a visible replacement.","testMethod":"Tab through the application and observe the focus indicator on each element. Verify that: (1) a visible outline, ring, or highlight appears on every focusable element, (2) the indicator has sufficient contrast against the background (at least 3:1), (3) the indicator is at least 2px thick or uses a colour change that covers the entire element. If focus disappears or becomes invisible on any element, this fails.","commonFailures":{"f1":"CSS or styling removes the default focus ring with outline:none and provides no replacement","f2":"Focus indicator is a 1px light grey dotted line that is invisible against white backgrounds","f3":"Focus is visible on buttons but invisible on links and list items","f4":"Dark mode uses a dark focus ring against a dark background, effectively invisible"}},"kb4":{"text":"Tab order follows a logical, meaningful sequence.","guidance":"Focus should move through controls in the order a user would expect, typically top-to-bottom, left-to-right, matching the visual layout.","testMethod":"Tab through the entire interface and note the order in which elements receive focus. Compare this order to the visual layout. Focus should move top-to-bottom, left-to-right (or the equivalent in RTL layouts), following the logical grouping of controls. If focus jumps unpredictably, e.g. From the header to the footer, then back to the sidebar, this fails.","commonFailures":{"f1":"Focus jumps from the first form field to the submit button, skipping intermediate fields","f2":"Tab order goes through the sidebar before the main content area","f3":"Dynamically added elements receive focus at the end of the DOM rather than their visual position","f4":"Tab order differs from reading order, confusing screen reader users"}},"kb5":{"text":"Standard keyboard shortcuts follow platform conventions.","guidance":"Ctrl+C, Ctrl+V, Ctrl+Z must work as expected. Custom shortcuts must not conflict with OS or screen reader shortcuts.","testMethod":"Test standard keyboard shortcuts: Ctrl+C (copy), Ctrl+V (paste), Ctrl+Z (undo), Ctrl+A (select all), Ctrl+S (save), Ctrl+P (print), F1 (help). Verify each works as expected. Test with a screen reader active to ensure custom shortcuts do not conflict with screen reader commands (e.g. Insert+key for JAWS/NVDA). Document any conflicts or non-standard behaviour.","commonFailures":{"f1":"Ctrl+Z does not undo, the application uses a custom undo shortcut","f2":"Application overrides F1 for a custom function instead of help","f3":"Custom shortcut Ctrl+D conflicts with JAWS screen reader command","f4":"Alt+key shortcuts conflict with menu bar accelerators in some locales"}},"vi1":{"text":"Text colour contrast meets 4.5:1 ratio (3:1 for large text).","guidance":"Measure against the actual background in the application. Custom themes and dark mode must also meet contrast requirements.","testMethod":"Use a colour contrast analyser tool (e.g. Colour Contrast Analyser by TPGi) to sample text and background colours throughout the application. Measure the contrast ratio for normal text (must be at least 4.5:1) and large text 18pt+ or 14pt bold (must be at least 3:1). Test all themes including dark mode, high contrast, and any custom colour schemes.","commonFailures":{"f1":"Light grey placeholder text on white input fields, ratio below 2:1","f2":"Dark mode uses medium grey text on dark grey background, ratio around 3:1 for body text","f3":"Disabled button text has insufficient contrast and no other visual indicator of disabled state","f4":"Status bar text is white on a light blue background, fails 4.5:1"}},"vi2":{"text":"Non-text UI components (icons, borders, focus rings) meet 3:1 contrast.","guidance":"Button outlines, input field borders, and icon graphics must have sufficient contrast against their background.","testMethod":"Using a colour contrast analyser, measure the contrast ratio of: (1) button borders against their background, (2) input field outlines against the page background, (3) icon graphics against their background, (4) focus indicators against the surrounding area. Each must meet at least 3:1. Pay attention to inactive/default states, not just hover states.","commonFailures":{"f1":"Input field borders are light grey (#E0E0E0) on white, ratio 1.4:1","f2":"Icon buttons use light grey icons on white background, below 3:1","f3":"Chart legends use colours that are indistinguishable at 3:1 contrast","f4":"Toggle switch track colour is too similar to the background in both on and off states"}},"vi3":{"text":"Application respects OS text scaling / DPI settings up to 200%.","guidance":"When the user sets system font size to 200% or changes DPI, the application must scale text without truncation, overlap, or loss of functionality.","testMethod":"Set the OS display scaling to 200% (Windows: Settings > Display > Scale; macOS: System Preferences > Displays > Scaled). Launch the application and verify: (1) all text is enlarged, (2) no text is truncated or clipped by containers, (3) no UI elements overlap, (4) all functionality remains accessible. Test critical workflows at 200% scaling.","commonFailures":{"f1":"Button labels are truncated with ellipsis at 150% scaling, cutting off critical text","f2":"Dialog boxes extend beyond the screen edge at 200% and cannot be scrolled","f3":"Application ignores OS DPI settings entirely, text stays the same size","f4":"Navigation menu overlaps content at 175% scaling, making both unusable"}},"vi4":{"text":"Application supports OS high contrast mode.","guidance":"On Windows, High Contrast Mode must be respected. On macOS, Increase Contrast must be honored. Don't override system accessibility display settings.","testMethod":"Enable OS high contrast mode (Windows: Settings > Accessibility > Contrast themes, select 'High Contrast Black' or 'High Contrast White'; macOS: System Preferences > Accessibility > Display > Increase Contrast). Launch the application and verify: (1) text and backgrounds adopt high contrast colours, (2) all UI elements remain visible, (3) no information is lost, (4) the application does not override the system setting.","commonFailures":{"f1":"Application uses hardcoded colours that ignore Windows High Contrast mode entirely","f2":"Custom-drawn UI elements become invisible in high contrast mode (same colour as background)","f3":"Images with transparent backgrounds disappear when high contrast is enabled","f4":"Status indicators that rely on specific colours (red/green) become indistinguishable"}},"vi5":{"text":"Colour is not the only means of conveying information.","guidance":"Error indicators, status lights, and selected states must use text, icons, or patterns in addition to colour.","testMethod":"Review every instance where colour is used to convey information: form validation errors, status indicators, selected/unselected states, required fields, chart data series, diff views. For each, verify there is a secondary indicator (text label, icon, pattern, underline, or shape). View the UI in greyscale (use a colour blindness simulator) and check that all information is still distinguishable.","commonFailures":{"f1":"Form errors indicated only by a red border, no icon, text, or other visual cue","f2":"Online/offline status shown only as a green/red dot with no text label","f3":"Required fields marked only with a red asterisk, no text saying 'required'","f4":"Chart data series distinguished only by colour with no patterns or labels"}},"scr1":{"text":"Screen reader compatibility verified with NVDA or JAWS (Windows).","guidance":"Test all major workflows with NVDA (free) and/or JAWS. Verify that all controls are announced, state changes are reported, and navigation is logical.","testMethod":"Install NVDA (free from nvaccess.org) or JAWS. Launch the application and complete every major workflow using only the screen reader and keyboard. Verify: (1) all controls are announced with name and role, (2) state changes are reported (checked, expanded, selected), (3) content is read in logical order, (4) dynamic updates are announced via live regions or focus management. Record any silent or misannounced elements.","commonFailures":{"f1":"Custom ribbon controls are completely silent, NVDA reads nothing","f2":"Dialog content is not read when dialog opens, user does not know a dialog appeared","f3":"Data grid cells are announced as 'blank' despite containing text","f4":"JAWS reads content in DOM order which differs from visual order, causing confusion"}},"scr2":{"text":"Screen reader compatibility verified with VoiceOver (macOS).","guidance":"If your software runs on macOS, test with VoiceOver enabled. Verify Rotor navigation, element descriptions, and action announcements.","testMethod":"Enable VoiceOver (Cmd+F5 on macOS). Navigate the application using VoiceOver commands: VO+Right/Left to move between elements, VO+Space to activate, VO+U for the Rotor. Verify: (1) every element is reachable and announced, (2) Rotor lists headings, links, and form controls correctly, (3) custom actions are described, (4) notifications and alerts are announced. Test all major workflows.","commonFailures":{"f1":"VoiceOver Rotor shows no headings because the app uses visual styling instead of semantic headings","f2":"Custom NSView elements are ignored by VoiceOver entirely","f3":"VoiceOver reads outdated or cached content after a dynamic update","f4":"Electron-based app has accessibility support disabled by default on macOS"}},"scr3":{"text":"Screen reader compatibility verified with Narrator (Windows) or Orca (Linux).","guidance":"Test with additional screen readers to ensure broad compatibility. Narrator is built into Windows; Orca is the primary Linux screen reader.","testMethod":"Enable Narrator (Win+Ctrl+Enter on Windows) or Orca (on Linux). Navigate the application and verify: (1) all interactive elements are announced, (2) reading mode (Narrator Scan Mode) works for content areas, (3) landmarks and headings are navigable. Compare the experience to NVDA/JAWS, significant differences indicate inconsistent accessibility API usage. Document any elements that work with one screen reader but not another.","commonFailures":{"f1":"Application works with JAWS but Narrator cannot read custom controls due to different API usage","f2":"Narrator Scan Mode does not work in the application, content is not browseable","f3":"Orca cannot access the application because it uses a UI toolkit with poor ATK/AT-SPI support","f4":"Narrator reads elements in a different order than NVDA, indicating inconsistent DOM structure"}},"er1":{"text":"Error messages are identified in text and describe the problem.","guidance":"'File not found: config.xml', not just a beep or red highlight. Error messages must be text that screen readers can announce.","testMethod":"Trigger every error condition you can: invalid input, file not found, network failure, permission denied, validation errors. For each error, verify: (1) a text message appears describing the problem, (2) the message is announced by the screen reader, (3) the message is associated with the relevant field or action, (4) the error is not conveyed solely through colour, sound, or icon.","commonFailures":{"f1":"Validation error shown only as a red border around the field with no text explanation","f2":"Error dialog says 'Error' with no description of what went wrong","f3":"Error beep plays with no visual or text indication of the problem","f4":"Error message appears but is not announced by the screen reader, focus does not move to it"}},"er2":{"text":"Error correction suggestions are provided where the expected input is known.","guidance":"If a filename is invalid, explain the naming rules. If a number is out of range, state the acceptable range.","testMethod":"Trigger validation errors for fields with known constraints: enter an invalid email address, a number outside the acceptable range, a filename with forbidden characters, a date in the wrong format. Verify that the error message includes a suggestion for correction, e.g. 'Enter a number between 1 and 100' rather than just 'Invalid input'. If the application knows the correct format but does not communicate it, this fails.","commonFailures":{"f1":"Error says 'Invalid input' with no indication of what valid input looks like","f2":"Date field rejects input but does not state the expected format (DD/MM/YYYY vs MM/DD/YYYY)","f3":"Password validation fails with 'Password too weak' but does not list the requirements","f4":"File path error says 'Invalid path' but does not explain which characters are forbidden"}},"er3":{"text":"Undo/redo is available for destructive actions.","guidance":"Delete, overwrite, and format actions should be reversible via Ctrl+Z or an explicit Undo option. For irreversible actions, require confirmation.","testMethod":"Perform destructive actions: delete a file, clear a form, overwrite content, format a disk section, remove a user. Verify that: (1) Ctrl+Z undoes the action, or (2) a confirmation dialog appears before the action executes, or (3) an 'Undo' option is available after the action. If a destructive action is immediate and irreversible with no confirmation or undo, this fails.","commonFailures":{"f1":"Delete permanently removes items with no confirmation dialog and no recycle/trash mechanism","f2":"Ctrl+Z does not work after a bulk operation (e.g. Find-and-replace across files)","f3":"Format/clear action is immediate with no undo, data is permanently lost","f4":"Confirmation dialog exists but is not keyboard-accessible or screen reader-announced"}},"er4":{"text":"Application has auto-save or data recovery on crash.","guidance":"Users with disabilities may take longer to complete tasks. Losing work due to a crash is disproportionately harmful. Auto-save at regular intervals.","testMethod":"Create a document or enter data, then force-close the application (Task Manager kill or Cmd+Option+Escape force quit). Relaunch the application and check whether: (1) unsaved work is recoverable, (2) an auto-save file or recovery prompt appears, (3) the recovery mechanism itself is keyboard-accessible and screen reader-compatible. If all work is lost with no recovery option, this fails.","commonFailures":{"f1":"Application has no auto-save, a crash loses all unsaved work","f2":"Auto-save exists but the recovery prompt on restart is not keyboard-accessible","f3":"Recovery file is saved but in a hidden location that users cannot easily find","f4":"Auto-save interval is 30 minutes, far too long for meaningful data recovery"}},"in1":{"text":"Installation wizard is keyboard-accessible and screen reader compatible.","guidance":"The entire install flow, EULA, options, progress, completion, must work with keyboard and screen reader. No mouse-only steps.","testMethod":"Run the installer with a screen reader active (NVDA or Narrator) and without using a mouse. Navigate through every step: EULA acceptance, installation path selection, component selection, progress bar, completion. Verify that: (1) every control is reachable via keyboard, (2) the screen reader announces each step and its controls, (3) progress is communicated, (4) the Next/Install/Finish buttons are keyboard-activatable.","commonFailures":{"f1":"Custom installer UI is completely inaccessible to screen readers, reads nothing","f2":"EULA text area traps keyboard focus, user cannot Tab to the Accept button","f3":"Installation path browse button is mouse-only, no keyboard activation","f4":"Progress percentage is visual only, screen reader does not announce installation progress"}},"in2":{"text":"Update notifications are accessible (text-based, screen reader announced).","guidance":"Update prompts must be announced by screen readers. 'Update available' must be navigable and dismissible with keyboard.","testMethod":"Trigger or wait for an update notification. Verify that: (1) the screen reader announces the notification when it appears, (2) the notification contains text describing the update, (3) the user can navigate to the Update and Dismiss buttons via keyboard, (4) the notification does not steal focus from the current task without warning. If the update notification is a silent popup that the screen reader ignores, this fails.","commonFailures":{"f1":"Update notification appears as a toast that disappears before screen reader can read it","f2":"Notification is announced but the Update button is not keyboard-focusable","f3":"Update dialog opens behind the main window and is not announced","f4":"Notification uses only a badge icon with no text, screen reader says nothing"}},"in3":{"text":"Installation does not reset previously configured accessibility settings.","guidance":"An application update must not disable screen reader support, high contrast mode, or custom accessibility configurations the user has set.","testMethod":"Configure accessibility settings in the application (font size, high contrast, screen reader optimisations, keyboard shortcut customisations). Run an update or reinstall. After the update completes, verify that all accessibility settings are preserved. If any setting reverts to default, this fails. Pay special attention to settings stored in config files that the installer might overwrite.","commonFailures":{"f1":"Update overwrites the user config file, resetting font size and contrast preferences","f2":"Reinstall disables the 'optimise for screen reader' setting that was manually enabled","f3":"Custom keyboard shortcuts are lost after an update because the keymap file is replaced","f4":"Accessibility plugin or extension is disabled by the update process"}}},"export":{"filename":"Software-checklist","title":"NON-WEB SOFTWARE ACCESSIBILITY","subtitle":"EN 301 549 Chapter 11, Desktop, Native & Installed Applications"},"links":{"eaaDirective":"EAA Directive 2019/882","en301549":"EN 301 549 V3.2.1"}},"sport-services-checklist":{"meta":{"title":"Sport Services Accessibility Checklist, Ticketing, Live Media, Stadium Info","description":"Accessibility checklist for sport clubs, federations and leagues, covers online ticketing, accessible-seat disclosure, live media captions, audio description, stadium information pages, and season-ticket renewal flows. Mapped to WCAG 2.2, EN 301 549 and EAA Annex I & V."},"header":{"title":"Sport Services Accessibility Checklist","subtitle":"Ticketing · Live media · Stadium info · Season-ticket renewal"},"description":"Accessibility checklist for sport clubs, federations and leagues, covers online ticketing, accessible-seat disclosure, live media captions, audio description, stadium information pages, and season-ticket renewal flows. Mapped to WCAG 2.2, EN 301 549 and EAA Annex I & V.","features":{"f1":"18 checkpoints across ticketing, programmes, live media, stadium info and membership","f2":"Maps each item to WCAG 2.2, EN 301 549, and the relevant EAA Annex I or Annex V provision","f3":"Pass / Partial / Fail / N/A with per-item notes","f4":"How-to-test guidance and common failures for every checkpoint","f5":"Links to relevant testing tools on AccessibilityRef","f6":"Progress auto-saved in your browser","f7":"Export Word report with notes","f8":"Print-ready view and blank Word download for offline workshops"},"categories":{"ticketing":{"label":"Online ticketing & accessible seating","description":"WCAG 1.3.1, 2.4.7, 3.3.2, 4.1.2 + EAA Annex V, the full ticket-purchase flow must be keyboard-operable, with accessible-seat options surfaced in the seat-chart UI rather than only via phone enquiry."},"programmes":{"label":"Match programmes & ticket-confirmation PDFs","description":"EN 301 549 §10 + PDF/UA-1, match-day programmes and ticket-confirmation PDFs must be tagged so screen readers can read them in correct order."},"live":{"label":"Live media, broadcasts, clips, commentary","description":"WCAG 1.2.2 (AA), 1.2.5 (AAA, record as recommendation), 4.1.3 (AA), captions on goal clips, transcripts for highlight reels, audio commentary for visually-impaired fans, and live-region announcements for score widgets."},"stadium":{"label":"Stadium & visitor information","description":"WCAG 1.1.1, 1.3.1, 2.4.2, a discoverable stadium-accessibility page with accessible-entrance instructions in text and clear service-animal and personal-assistant policies."},"membership":{"label":"Membership & season-ticket renewal","description":"WCAG 1.3.1, 1.3.5, 3.3.2, 3.3.7, every renewal-form input labelled, autocomplete on identification fields, and no redundant entry on later steps."}},"items":{"tix1":{"text":"The ticket-purchase flow is fully completable by keyboard alone.","guidance":"A keyboard-only user must be able to search dates, select fixture, pick seat, enter guest details, accept terms, and submit payment without ever needing a mouse.","testMethod":"Put your mouse down. Using only Tab, Shift+Tab, Enter, Space and arrow keys, complete a real ticket purchase from fixture search to confirmation. Note any control that cannot be reached or activated, and any focus that disappears or jumps unexpectedly.","commonFailures":{"f1":"Date picker only opens on mouse click, Enter and Space do not trigger it","f2":"Seat selection grid is mouse-only with no keyboard equivalent","f3":"Terms-and-conditions checkbox is a styled div with no keyboard handler","f4":"Final 'Pay' button is inside a third-party iframe that traps keyboard focus"}},"tix2":{"text":"Wheelchair and companion seats are filterable in the seat-chart UI, not only via phone enquiry.","guidance":"Disabled supporters must have parity of access. A 'call us for accessible seats' link without a self-service equivalent forces disabled users through a slower, less private channel.","testMethod":"Open the seat-chart for any upcoming fixture. Look for a visible filter, toggle, or category for wheelchair-user seats and companion seats. Confirm the filter is keyboard-operable and that the resulting seats can be selected through the same flow as a standard seat.","commonFailures":{"f1":"Only a 'please call our accessibility line' link is shown, no online accessible-seat purchase route","f2":"Accessible-seat filter exists but is hidden under a 'special requirements' tab that screen readers miss","f3":"Wheelchair seats are visible on the map but cannot be selected, clicking shows a 'phone only' modal","f4":"Companion-seat option does not appear after selecting a wheelchair seat, buyer cannot bring a personal assistant"}},"tix3":{"text":"The seat-chart image has a text equivalent, a table of available seats with prices.","guidance":"A screen-reader user cannot navigate a graphical seat map. Provide an accessible table listing block, row, available seats, and price as a programmatic equivalent.","testMethod":"Inspect the seat-chart with a screen reader. Listen for whether seat availability and pricing are announced. If the map is the only representation, look for a 'view as list' or 'accessible seat list' toggle. Confirm the table has proper headers and that all visible chart information is also available textually.","commonFailures":{"f1":"Seat map is rendered as a single SVG with no alt text and no text equivalent","f2":"Accessible 'list view' exists but pricing is omitted","f3":"Table is provided but uses <div> grids with no <th> headers","f4":"Text equivalent loads only on a separate page, breaking the buying flow"}},"tix4":{"text":"Pricing-tier labels are announced by screen readers, not colour-only.","guidance":"Distinguishing 'gold tier' from 'silver tier' by colour alone fails WCAG 1.4.1 Use of Colour. Each tier needs a text label adjacent to or within the price element.","testMethod":"Inspect each pricing tier in the seat-chart or ticket-tier table. Confirm a text label (e.g. 'Gold', 'Silver', 'Family Stand') is present on every tier, not only a coloured swatch. Test with a screen reader to verify the tier name is announced alongside the price.","commonFailures":{"f1":"Tiers shown only as coloured rectangles in the seat-chart legend","f2":"Tier name is in an image of text with no alt attribute","f3":"Tier price has aria-label='29 euros' but omits the tier name","f4":"Discount tier (e.g. Concession) indicated only by a different shade of the same colour"}},"tix5":{"text":"Third-party ticketing widget: an Annex V scope statement names the vendor.","guidance":"Where ticketing is embedded from a vendor (Eventbrite, Universe, Stripe Tap, Bilheteira Online), the accessibility statement must name the vendor and explain the operator's reasonable monitoring process for that scoped content.","testMethod":"Read the published accessibility statement. Confirm it names the third-party ticketing vendor, identifies the scoped paths (e.g. /tickets/, /bilheteira/), and describes the operator's process for raising and tracking accessibility issues with the vendor.","commonFailures":{"f1":"Statement does not mention the third-party widget at all","f2":"Statement mentions 'embedded content' generically but does not name the vendor","f3":"Statement disclaims responsibility for the widget without describing any monitoring or escalation path","f4":"Vendor name appears only in cookie notice, not in the accessibility statement scope section"}},"prg1":{"text":"Match programmes are published as tagged PDFs (PDF/UA-1).","guidance":"Match-day programmes must be tagged, reading order, headings, language, alt text on photos. Untagged PDFs are unreadable by screen readers.","testMethod":"Download the most recent match programme PDF. Open in Adobe Acrobat Pro and run the Accessibility Check tool, or upload to the Document Auditor on AccessibilityRef. Confirm the PDF is tagged, has a defined reading order, includes alt text on photos, and has a document title and language set in metadata.","commonFailures":{"f1":"Programme is an exported InDesign PDF with no tag tree","f2":"Reading order follows visual layout instead of logical flow","f3":"Player photos lack alt text, screen reader announces 'image'","f4":"Document language is not set, so screen reader uses the wrong voice"}},"prg2":{"text":"Ticket-confirmation PDFs have a tagged reading order.","guidance":"The emailed ticket attachment must be a tagged PDF so screen-reader users can read seat number, gate, and entry time in logical order.","testMethod":"Buy a test ticket and download the confirmation PDF. Open with a screen reader (e.g. NVDA + Adobe Reader) and listen to the order in which fields are announced. Confirm seat, gate, fixture, kick-off and barcode/QR description are read in a sensible sequence.","commonFailures":{"f1":"Confirmation is a flat image-only PDF with no text layer","f2":"Barcode and QR code are read as 'image' with no fallback text alternative","f3":"Reading order interleaves footer and body fields","f4":"Kick-off time is in an image of text with no programmatic equivalent"}},"prg3":{"text":"Player rosters are HTML text, not images of text.","guidance":"Squad listings, line-ups and stat tables must be real text in HTML, so screen readers, translation tools and large-text users can interact with them.","testMethod":"Open the team-roster page and try to select and copy a player's name. If the text selects cleanly it is real text. If the cursor draws a rectangle around an image, the roster is an image-of-text and fails.","commonFailures":{"f1":"Squad list is a single PNG exported from a design template","f2":"Stats table is published as an Instagram-style image","f3":"Player profile photos have alt text but the player name underneath is part of the photo","f4":"Names are HTML but jersey numbers are sprite images with no text"}},"lv1":{"text":"Goal-video clips are published with synchronised captions.","guidance":"Pre-recorded goal clips and post-match interviews need captions, commentary, crowd reactions, manager quotes. WCAG SC 1.2.2 Captions (Prerecorded) is Level AA.","testMethod":"Open the latest three goal-clip or interview videos on the club site. Turn on captions in each player. Confirm captions exist, are synchronised, identify speakers in interviews, and include relevant non-speech information (e.g. '[crowd cheers]'). Auto-generated captions without human review usually fail accuracy.","commonFailures":{"f1":"Goal clips have no captions whatsoever","f2":"Auto-captions are used with uncorrected errors in player and place names","f3":"Manager interviews caption the manager but not the journalist's questions","f4":"Captions are burned into video at low contrast and cannot be turned off or resized"}},"lv2":{"text":"Match-highlight reels have a text transcript.","guidance":"Highlight reels with commentary should have a transcript or descriptive summary, so users who cannot use captions (e.g. Those with cognitive disabilities or in low-bandwidth contexts) can still follow the content.","testMethod":"Look at the highlights page for a recent fixture. Beside or below the video, look for a transcript link, an 'expand transcript' control, or a descriptive recap paragraph. Confirm the transcript covers the main commentary, goal events and substitutions.","commonFailures":{"f1":"Only the video is provided, no transcript or recap","f2":"A recap article exists but is not linked from the video page","f3":"Transcript link opens a PDF that is itself untagged","f4":"Transcript is auto-generated from captions with no proofreading and contains many errors"}},"lv3":{"text":"Audio commentary for visually-impaired fans is available on at least one matchday channel.","guidance":"Live audio description for visually-impaired supporters, typically a dedicated commentary feed on the club app or website, is a strong indicator of inclusive matchday coverage. Note this is a Level AAA / recommendation under WCAG 1.2.5.","testMethod":"Check the matchday page or club app for an audio-only or 'audio description' commentary option. Confirm it is discoverable (not buried in a sub-menu), free of paywall for accessibility users, and works alongside in-stadium use.","commonFailures":{"f1":"No audio-only commentary feed at all","f2":"Audio feed exists only behind a paid streaming subscription with no accessibility carve-out","f3":"App audio feed crashes when used with VoiceOver or TalkBack","f4":"Audio commentary is offered only post-match as a podcast, not live in stadium"}},"lv4":{"text":"Livescore widget announces score changes via aria-live or role=\"status\".","guidance":"Live score, possession and shot counters update silently for screen-reader users unless wrapped in an aria-live region. Goals and reds must be announced.","testMethod":"Open the live-match page during a fixture (or on an archived live feed). Activate a screen reader and wait for a score event or notable update. Confirm the change is announced. Inspect the DOM for aria-live='polite' or role='status' on the score and event-log container.","commonFailures":{"f1":"Score updates visually but no aria-live region wraps the value","f2":"Whole live-feed container uses aria-live='assertive' and interrupts the screen reader on every minor update","f3":"Score is rendered inside a canvas element with no text equivalent","f4":"Event log updates via DOM mutation but the new event is not the announced node"}},"st1":{"text":"A dedicated stadium-accessibility page exists, linked from the main navigation or footer.","guidance":"Operators must publish, in one discoverable place, the practical information a disabled supporter needs to plan a visit: entrances, parking, seat blocks, sensory rooms, audio description availability.","testMethod":"From the homepage, look for a top-level navigation link or footer link labelled 'Accessibility', 'Visitor accessibility' or similar. Confirm it leads to a stadium-specific page (not just the legal accessibility statement). Confirm the page covers entrances, accessible parking, lift coverage, sensory facilities and contact route.","commonFailures":{"f1":"Only the legal accessibility statement is published, no operational stadium information","f2":"Stadium-accessibility information is split across three different sub-pages with no index","f3":"Page is linked only from the season-ticket holder area, hidden from public users","f4":"Page is reachable but uses 'disability' rather than 'accessibility' language and is hard to discover via search"}},"st2":{"text":"Accessible-entrance instructions are text, not photos of signs.","guidance":"Photo-of-sign assets cannot be read by screen readers, translated by browsers, or resized for low-vision users. Entrance instructions must be in HTML text.","testMethod":"On the stadium-accessibility page, look for entrance and route information. Try to select and copy the entrance address and directions. If text selects, it is real text. If it is an image (photo of a sign, map overlay), it fails, unless full alt text or a text equivalent is provided.","commonFailures":{"f1":"Entrance address is shown only as a photo of the wayfinding sign","f2":"Directions are in a tour-style PDF that itself is untagged","f3":"Stadium map is an interactive image with hotspots but no text alternative","f4":"Step-free route is described in a video that has no captions and no transcript"}},"st3":{"text":"Service-animal and personal-assistant policies are linked from the stadium page.","guidance":"Disabled supporters need to know in advance whether service animals are permitted and whether a personal assistant accompanies free of charge. This policy must be published, not held only by the ticket office.","testMethod":"On the stadium-accessibility page, look for sections on service animals (guide / assistance dogs) and personal-assistant tickets. Confirm both policies are written down and linked from this page, not only available by phoning the ticket office.","commonFailures":{"f1":"Personal-assistant ticket policy is mentioned in a FAQ but not surfaced on the accessibility page","f2":"Service-animal policy is undocumented online, answered only by phone","f3":"Policy is published but does not specify whether assistance dogs are permitted in all areas","f4":"Personal-assistant policy applies only to season-ticket holders, with no equivalent for matchday buyers"}},"mb1":{"text":"Season-ticket renewal forms have a <label> on every input.","guidance":"Every text field, radio group and select must have a visible, programmatically associated <label>. Placeholder text is not a substitute.","testMethod":"Open the season-ticket renewal form and inspect each field in DevTools. Confirm every input is associated with a <label for='id'> or wrapped in a <label>. Try the form with a screen reader and confirm each field announces its label.","commonFailures":{"f1":"Placeholder text is the only label and disappears when typing begins","f2":"Labels are visually hidden with display:none and unreachable","f3":"Radio group labels exist for each radio but there is no <legend> for the group","f4":"Multi-part fields (e.g. Card expiry month / year) share a single label that does not identify each part"}},"mb2":{"text":"Identification fields carry the appropriate autocomplete value.","guidance":"Name, email, address-line1, postal-code and tel fields should declare their purpose with the standard HTML autocomplete tokens so password managers and AT can prefill them. WCAG 1.3.5 Identify Input Purpose (Level AA).","testMethod":"Inspect each identifying input in the renewal form. Confirm autocomplete='name', 'email', 'address-line1', 'postal-code', 'tel' (and similar) are present and use the correct WHATWG tokens. Test with browser autofill, fields should populate from a saved profile.","commonFailures":{"f1":"No autocomplete attributes on any input","f2":"Autocomplete='off' is set globally, defeating user autofill","f3":"Token is misspelled (autocomplete='adress-line1')","f4":"Address fields use a non-standard custom token"}},"mb3":{"text":"Don't ask for the same information on later steps, WCAG 2.2 SC 3.3.7 Redundant Entry.","guidance":"If the user has already entered name, email and address on step 1, do not ask for them again on step 3. WCAG 2.2 SC 3.3.7 (Level A) requires either pre-population or a select-from-prior option.","testMethod":"Walk the full renewal flow. Note every field on each step. Confirm no field that was already entered (name, email, postcode, payment-card number where allowed by PCI) is re-requested without pre-population or an explicit 'use same details' option.","commonFailures":{"f1":"Billing address is re-asked on the payment step even though shipping address was just entered","f2":"Email field is requested again on the confirmation step","f3":"Phone number is asked once for verification and again for stadium contact, with no copy-across","f4":"Renewal form does not pre-populate from last year's record"}}},"export":{"filename":"Sport-services-checklist","title":"SPORT SERVICES ACCESSIBILITY CHECKLIST","subtitle":"Ticketing · Live media · Stadium info · Season-ticket renewal"},"links":{"eaaDirective":"EAA Directive 2019/882","en301549":"EN 301 549 V3.2.1"}},"statement-validator":{"meta":{"title":"Annex V Statement Validator, EAA Accessibility Statement Checker","description":"Paste a published accessibility-statement URL and validate it against the 14 mandatory elements of EAA Annex V, EN 301 549 §12.1.1 and Directive 2016/2102 Article 7."},"title":"Annex V Statement Validator","subtitle":"Validate any published accessibility statement against the 14 mandatory elements of EAA Annex V, EN 301 549 §12.1.1 and Directive 2016/2102 Article 7.","howItWorksTitle":"How it works:","howItWorksBody":"We fetch the URL server-side and search the page text for each Annex V mandatory element using language-agnostic patterns (PT, EN, FR, ES, DE, IT). Each element carries a weight; the score is the percentage of weighted elements present. Use this to verify your own statement before publication, or to assess a third party's statement before procurement.","urlInputLabel":"URL of the published accessibility statement","validate":"Validate","scanning":"Validating...","errorPrefix":"Error","outOf100":"Out of 100","elementsCounted":"{present} of {total} mandatory elements detected","annexVElements":"Annex V Mandatory Elements","present":"Present","missing":"Missing","interpretingTitle":"How to interpret the score","interpretingBody":"A score below 80 indicates the statement is at material risk of being deemed insufficient by a market-surveillance authority. Critical-weight elements, EN 301 549 reference, conformance status, feedback channel and enforcement procedure, together account for 44 of the 100 points. Missing any one of these will materially reduce the score and should be remediated before relying on the statement as Annex V evidence.","downloadJson":"Download JSON","downloadJsonHint":"Full validation result with detected evidence per element","urlPlaceholder":"Https://example.com/accessibility","weightUnit":"{count} pts","export":{"labels":{"validatedUrl":"Validated URL","score":"Score","elementsPresent":"Elements present","present":"Present","missing":"Missing"},"summaryLine":"Annex V validation: {score}/100, {present}/{total} elements present","defaultNotes":"Annex V Statement Validator: {url} → {score}/100 ({present}/{total} elements)","docx":{"summaryHeading":"Summary","rowValidatedUrl":"Validated URL","rowPageTitle":"Page title","rowScore":"Score","rowScoreValue":"{score} / 100 (Grade {grade})","rowElementsPresent":"Elements present","rowElementsPresentValue":"{present} / {total}","rowElementsMissing":"Elements missing","rowDetectedLanguage":"Detected language","rowContentLength":"Content length","rowContentLengthValue":"{count} characters","rowFetchedBytes":"Fetched bytes","fallbackNone":"(none)","checklistHeading":"Annex V Element Checklist","checklistIntro":"Each row shows one Annex V required element, whether it was detected on the page, the weight applied to the score, and the legal basis. Evidence text is the matching snippet pulled from the page.","colNum":"#","colElement":"Element","colStatus":"Status","colWeight":"Weight","colLegal":"Legal basis","colEvidence":"Evidence","weightCell":"{count} pts","evidenceCell":"\"…{snippet}…\"","evidenceDash":",","missingHeading":"Missing Elements","missingIntro":"{count, plural, one {# required element was} other {# required elements were}} not detected on the page. Each missing element reduces the validation score by its weight.","missingItem":"{label} ({weight} pts), {legal}","detectedHeading":"Detected Elements","detectedItemWithEvidence":"{label}, \"…{snippet}…\"","detectedItemNoEvidence":"{label}, (no excerpt captured)","methodHeading":"Method","methodBody":"The accessibility statement page was fetched server-side and parsed for the elements required by Annex V of Directive (EU) 2019/882 and Article 7 of Directive (EU) 2016/2102 (Web Accessibility Directive). Each element is detected via heuristic regex/keyword matching and weighted by legal importance. Mapped to EN 301 549 V3.2.1 §12.1.1 (accessibility statement) and Annex V of the European Accessibility Act."}},"nextSteps":{"fixInWizard":"Draft a fix in Statement Wizard"}},"statement-wizard":{"meta":{"toolId":"Statement-wizard","title":"Directive 2016/2102 Accessibility Statement Generator","description":"Under Directive (EU) 2016/2102 Article 9, generate a compliant accessibility statement. Covers all 7 EAA Annex V mandatory elements, 7 EU languages."},"legalBasis":{"heading":"Legal basis for this statement","intro":"This generator builds the accessibility statement mandated by Directive (EU) 2016/2102 Article 9 with the disproportionate-burden structure from Article 5, and the service-provider information obligations of Directive (EU) 2019/882 Article 13."},"title":"Accessibility Statement Generator","header":{"lede":"Generate an EAA Annex V compliant accessibility statement. Complete all steps, then download or copy.","officialLinkLabel":"EAA Directive 2019/882, Annex V"},"proGate":{"features":["EAA Annex V compliant Accessibility Statement, all mandatory elements included","7 EU language outputs: EN, DE, FR, ES, IT, PT, NL","Auto-fills the correct national enforcement body and URL for your EU country","Download as a publish-ready HTML file, copy as plain text, or embed directly"]},"proGateFeatures":["Generate a legally compliant accessibility statement in minutes","Covers WCAG 2.1/2.2, EAA, EN 301 549, and national transposition laws","Auto-fills enforcement body and national law based on your EU country","Multi-language output: English, French, German, Spanish, Italian, Portuguese, Dutch","Issue tracker with WCAG criterion, reason, remediation plan, and target date"],"legalContext":{"heading":"When an Accessibility Statement is legally required, and what it must contain","whoMustPublishLabel":"Who must publish one:","whoMustPublishBody":"Under the EAA (Directive 2019/882), all organisations placing in-scope products and services on the EU market from 28 June 2025 must be able to demonstrate accessibility compliance. For digital services covered by the Web Accessibility Directive (EU 2016/2102), public sector bodies have been required to publish an Accessibility Statement since 2018.","ukNote":"Under UK PSBAR, all UK public sector bodies must publish a statement meeting GOV.UK guidance, including a list of known accessibility issues and their planned fix dates.","annexVHeading":"What EAA Annex V requires, the 7 mandatory elements:","annexVList":["Name and contact details of the organisation","The applicable standard (WCAG 2.1 Level AA / EN 301 549)","Conformance status: fully / partially / not compliant","Description of non-accessible content and the reason (where partially/non-compliant)","Disproportionate burden claims, if any","A feedback mechanism for users to report barriers","The national enforcement body to escalate complaints to"],"footer":"This wizard generates all 7 elements plus recommended W3C best-practice sections (organisational measures, assessment approach, formal approval). Once published, review and update your statement at least annually."},"howTo":{"step1":{"title":"Organisation Details","body":"Enter your organisation name, website URL, EU country and review dates. The tool auto-fills the correct national enforcement body."},"step2":{"title":"Compliance Status","body":"Select your WCAG conformance level. If partially or non-compliant, describe the gaps, this is required by EAA Annex V."},"step3":{"title":"Efforts & Technical","body":"Document organisational measures you have taken, the technologies your site uses, and how you assessed conformance. These strengthen the credibility of your statement."},"step4":{"title":"Contact & Formal","body":"Add a feedback email, phone, postal address, the national enforcement body, formal complaints procedure, and the name of whoever approved the statement."},"step5":{"title":"Generate & Download","body":"Choose your output language (7 EU languages). Preview, then download as HTML, copy as plain text, or grab the JSON-LD and embeddable feedback form."}},"progress":{"stepLabels":["Organisation","Compliance","Efforts","Contact","Preview"],"stepOf":"Step {current} of {total}","percentComplete":"{percent}% complete","stepOfStatus":"Step {current} of {total}: {label}","completeness":"Statement completeness: {percent}%"},"clearDraft":{"label":"Clear draft","confirmPrompt":"Clear all draft data?","cancel":"Cancel","confirm":"Clear"},"industryTemplates":{"heading":"Quick-start industry template","subheading":"Select your sector to pre-fill relevant content. You can edit all fields afterwards.","labels":{"ecommerce":"E-commerce","banking":"Banking / Fintech","saas":"SaaS / Software","publicSector":"Public Sector","media":"Media / Publishing"}},"steps":{"step1":{"label":"Organisation","title":"Organisation Details","heading":"Step 1: Organisation Details","intro":"Enter the legal entity details that will appear in the published accessibility statement.","continueButton":"Continue to Compliance Status →","fields":{"entityName":"Organisation / Entity Name","websiteName":"Website / Service Name","websiteUrl":"Website URL","postalAddress":"Postal Address","preparationDate":"Statement Preparation Date","lastReviewedDate":"Last Reviewed Date","nextReviewDate":"Next Review Date","language":"Statement Language","country":"EU Member State","nationalLaw":"National Transposition Law","scope":"Scope of Service","annexISection":"Annex I Section"},"labels":{"entityName":"Legal Entity Name","entityNamePlaceholder":"E.g. Acme Corp EU GmbH","websiteName":"Website / App Name (optional)","websiteNamePlaceholder":"E.g. Acme Customer Portal","websiteNameHelp":"If the website has a distinct name from the organisation, enter it here. It appears alongside the URL in the statement.","websiteUrl":"Website URL","websiteUrlPlaceholder":"Https://www.example.com","statementPublicationUrl":"Statement Publication URL","statementPublicationUrlNote":"(where this statement will be published on your website)","statementPublicationUrlPlaceholder":"Https://www.example.com/accessibility-statement","statementPublicationUrlHelp":"Annex V requires the statement to be published on your digital service. Market surveillance authorities verify this URL. It should be linked from your main navigation or footer.","scope":"Scope / Platform Coverage","scopeBadge":"Included in statement","scopeHelp":"Specify which platforms and channels this statement covers. If you have a mobile app, it must be separately assessed against EN 301 549 Clause 11 (non-web software), not Clause 9 (web).","scopeMobileWarning":"Mobile app scope note:","scopeMobileWarningBody":"Mobile apps are assessed against EN 301 549 Clause 11 (non-web software), not Clause 9 (web content). If your mobile app has not been separately assessed under Clause 11, declare partial conformance for the app scope. A separate VPAT/ACR for the app is strongly recommended.","annexISection":"EAA Annex I Section","annexISectionBadge":"Identifies legal scope","annexISectionHelp":"Identifies which section of EAA Annex I your product/service falls under. Enforcement bodies use this to determine applicable requirements.","preparationDate":"Preparation Date","lastReviewedDate":"Last Reviewed Date","nextReviewDate":"Next Review Date"}},"step2":{"label":"Compliance","title":"Compliance Status","heading":"Step 2: Compliance Status","intro":"Select the current WCAG conformance level and describe any gaps.","continueButton":"Continue to Efforts & Technical →","fields":{"complianceStatus":"Conformance Status","wcagLevel":"WCAG Conformance Level","enStandard":"EN 301 549 Version","nonAccessibleContent":"Non-Accessible Content","disproportionateBurdenClaims":"Disproportionate Burden Claims","interimAlternative":"Interim Alternative Access"},"complianceOptions":{"fully":"Fully conformant","partially":"Partially conformant","not":"Not conformant"},"labels":{"complianceStatusLegend":"Compliance Status","fully":"Fully Compliant","fullyDesc":"All content meets the selected WCAG level with no known failures.","partially":"Partially Compliant","partiallyDesc":"Some content does not yet meet the requirements.","not":"Not Compliant","notDesc":"The website does not currently meet the WCAG requirements.","wcagLevelLegend":"WCAG Level","enStandardLegend":"Harmonised Standard, EN 301 549 Version","enV321Label":"V3.2.1 (2021), Recommended for EAA","enV321Note":"References WCAG 2.1, current OJEU harmonised standard","enV411Label":"V4.1.1 (2024)","enV411Note":"References WCAG 2.2, best practice, not yet in OJEU list","wcagNoteV321":"EN 301 549 V3.2.1 (2021) references WCAG 2.1 Level AA as its web accessibility standard. If you intend to claim WCAG 2.2 conformance, select EN 301 549 V4.1.1 below, noting V4.1.1 is not yet listed in the OJEU harmonised standards list.","wcagNoteV411":"EN 301 549 V4.1.1 (2024) references WCAG 2.2. This version is not yet designated as a harmonised standard in the OJEU. Citing it demonstrates best practice but does not provide presumption of conformity under the EAA.","nonAccessibleContent":"Non-Accessible Content Description","nonAccessibleContentPlaceholder":"Describe which content or features are not yet accessible and why…","nonAccessibleContentHelp":"Optional: use the free-text field above for a general description, or use the structured issue builder below (recommended) to document each barrier individually with remediation steps. Enforcement bodies prefer per-issue documentation.","insertExample":"Insert example","burdenClaims":"Disproportionate Burden Claims (optional)","burdenClaimsPlaceholder":"If any content is exempt under disproportionate burden, describe it here…","burdenClaimsHelp":"Disproportionate burden is a legal exemption, not a general excuse. You must be able to demonstrate the assessment if challenged by an enforcement body.","interimAlternative":"Interim Accessible Alternative","interimAlternativeBadge":"Required, Article 13(2)","interimAlternativePlaceholder":"Describe how users can still access the content or service while the burden exemption applies, e.g. 'Contact us at accessibility@example.com to request an accessible version within 5 working days'…","interimAlternativeNote":"Article 13(2) requires that when a disproportionate burden exemption is invoked, an interim accessible means of access must be provided. This is not optional, failure to provide an alternative route of access may render the burden claim invalid.","interimAlternativeMissing":"⚠ You have claimed a disproportionate burden but have not described an interim accessible alternative. This is required for a valid EAA statement.","insertTemplate":"Insert template"},"examples":{"nonAccessibleContent":"The following content does not yet fully conform to {wcagVersion} Level {wcagLevel}:\n\n1. Some images on product listing pages are missing descriptive alt text. Affected criterion: SC 1.1.1 (Non-text Content). We are working with our CMS provider to update these by [target date].\n\n2. Colour contrast on certain promotional banners does not meet the 4.5:1 minimum ratio. Affected criterion: SC 1.4.3 (Contrast Minimum). A design update is scheduled for [target date].\n\n3. Keyboard focus order on the checkout page does not follow a logical sequence on mobile breakpoints. Affected criterion: SC 2.4.3 (Focus Order). Development fix is in progress.","burdenClaims":"We have assessed the following areas and determined that full compliance would impose a disproportionate burden, as defined under Article 14 of Directive 2019/882:\n\nOur archive of documents published before [date] has not been made fully accessible. Remediation would require significant resource that is disproportionate to the benefit, given the low usage of this content. We are committed to providing accessible alternatives on request, contact accessibility@[yourdomain.com] to request an accessible version of any archived document.","interimAlternative":"Where content is exempt under a disproportionate burden assessment, we provide the following interim accessible means of access:\n\nUsers who require access to any content covered by the disproportionate burden claim should contact us at accessibility@[yourdomain.com] or call [phone number]. We will provide the requested information in an accessible format (email, accessible PDF, large print, or verbal briefing) within 5 working days at no cost to the user."}},"step3":{"label":"Efforts & Technical","title":"Organisational Measures & Technical Details","heading":"Step 3: Efforts & Technical","intro":"Document the organisational measures you have taken, the technologies your site uses, and how you assessed conformance. These sections are recommended by the W3C and strengthen the credibility of your statement.","continueButton":"Continue to Contact & Formal →","fields":{"orgMeasures":"Organisational Measures Taken","technologiesUsed":"Technologies Used","assessmentApproach":"Assessment Approach","evaluationReportUrl":"Evaluation Report URL","evaluationStatementUrl":"WCAG-EM Evaluation Statement URL","assessmentMethodType":"Assessment Method","assessmentMethodAuditorName":"Auditor Name","assessmentMethodAuditorOrg":"Auditor Organisation"},"labels":{"orgMeasuresLegend":"Organisational Measures","orgMeasuresNote":"(optional, select all that apply)","orgMeasuresHelp":"Tick the measures your organisation has in place to support accessibility.","addMeasure":"+ Add another measure","removeMeasure":"Remove measure","customMeasurePlaceholder":"Describe an additional measure…","technologiesLegend":"Technologies Used","technologiesNote":"(optional)","technologiesHelp":"Select the web technologies your site or app relies on for accessibility conformance.","addTechnology":"+ Add another technology","removeTechnology":"Remove technology","customTechnologyPlaceholder":"E.g. PDF/UA, EPUB","assessmentLegend":"Assessment Approach","assessmentNote":"(optional, select all that apply)","assessmentHelp":"How did you assess the accessibility of this website?","addAssessment":"+ Add another approach","removeAssessment":"Remove assessment approach","customAssessmentPlaceholder":"E.g. Automated testing with axe DevTools","methodTypeLegend":"Assessment Method Type (Annex V element 6, mandatory)","methodSelf":"Self-assessment","methodSelfDesc":"Internal team assessed against WCAG/EN 301 549","methodThirdParty":"Third-party audit","methodThirdPartyDesc":"Independent accessibility specialist conducted the audit","methodCombination":"Combination","methodCombinationDesc":"Mix of internal self-assessment and external specialist testing","methodMissingNote":"Assessment method type is a mandatory Annex V element. Market surveillance authorities verify this, self-assessments receive more scrutiny than third-party audits.","auditorName":"Auditor Name","auditorNamePlaceholder":"E.g. Jane Smith","auditorOrg":"Auditor Organisation","auditorOrgPlaceholder":"E.g. Accessible Digital Ltd","evidenceHeading":"Related Evidence (optional)","evalReportUrl":"Evaluation Report URL","evalReportUrlPlaceholder":"Https://example.com/accessibility-audit-report","evalReportUrlHelp":"Link to a formal WCAG audit or evaluation report, if available.","evalStatementUrl":"Evaluation Statement URL","evalStatementUrlPlaceholder":"Https://example.com/wcag-evaluation-statement","evalStatementUrlHelp":"Link to a formal WCAG evaluation statement (e.g. WCAG-EM report), if available."},"orgMeasuresOptions":["Include accessibility as part of our mission statement","Include accessibility throughout our internal policies","Integrate accessibility into our procurement practices","Appoint an accessibility officer and/or ombudsperson","Provide continual accessibility training for our staff","Assign clear accessibility goals and responsibilities","Include accessibility as part of our quality assurance process"],"assessmentOptions":{"selfV321Label":"Self-evaluation, against WCAG 2.1 AA / EN 301 549 V3.2.1 (the harmonised standard)","selfV22Label":"Self-evaluation, against WCAG 2.2 AA (current W3C Recommendation, October 2023)","externalLabel":"External evaluation, carried out by an independent accessibility specialist"}},"step4":{"label":"Contact & Formal","title":"Contact Information & Enforcement","heading":"Step 4: Contact & Formal","intro":"Provide feedback contact details, the national enforcement body, a formal complaints procedure, and the name of whoever approved this statement.","continueButton":"Preview Statement →","fields":{"feedbackEmail":"Feedback Email","feedbackPhone":"Feedback Phone","enforcementBody":"National Enforcement Body","enforcementUrl":"Enforcement Body URL","complaintsProcess":"Complaints Process","approverName":"Approver Name","approverTitle":"Approver Title","additionalInfo":"Additional Information"},"labels":{"guidanceHeading":"What to include in Step 4","guidanceFeedbackEmail":"Feedback email:","guidanceFeedbackEmailBody":"Use a monitored inbox, e.g. Accessibility@yourdomain.com. EAA requires that you respond to feedback within a reasonable time. The 5-working-day response time included in the generated statement is recommended best practice guidance, not a statutory obligation under EAA Annex V, adjust as appropriate for your organisation.","guidanceCountry":"Country:","guidanceCountryBody":"Selecting your country auto-fills the correct national enforcement body. Users have a legal right to escalate to this body if unsatisfied with your response.","guidanceComplaints":"Complaints procedure:","guidanceComplaintsBody":"Describe the steps a user should follow to make a formal complaint, this is required by many national enforcement bodies.","guidanceApproval":"Formal approval:","guidanceApprovalBody":"Include the name and title of the person who approved this statement. This demonstrates accountability and is recommended by the W3C.","feedbackEmail":"Feedback Email","feedbackEmailPlaceholder":"Accessibility@example.com","feedbackPhone":"Feedback Phone (optional)","feedbackPhonePlaceholder":"+49 30 12345678","postalAddress":"Postal / Visitor Address (optional)","postalAddressPlaceholder":"E.g. 10 Main Street, Berlin, 10115, Germany","country":"Country (auto-fills enforcement body & national law)","countryPlaceholder":"Select your EU country,","countryHelp":"The EAA is a Directive and each Member State has its own transposition law, enforcement body and contact requirements, which can change after release. Verify the auto-filled values against your national authority's current guidance before publishing.","nationalLawAutoFilled":"National Transposition Law (auto-filled)","nationalLawAutoFilledHelp":"This will be included in your accessibility statement alongside the EU Directive reference. Enforcement bodies review national law, not the Directive directly.","nationalLawOverride":"National Law Citation (editable)","nationalLawOverridePlaceholder":"E.g. National transposition act","nationalLawOverrideHelp":"Your accessibility statement must cite the national law that transposes the EAA, not just the EU Directive. Edit if the auto-filled text needs updating.","enforcementBody":"National Enforcement Body Name","enforcementBodyPlaceholder":"E.g. National enforcement authority","enforcementUrl":"Enforcement Body URL","enforcementUrlPlaceholder":"Https://www.enforcement-body.example","enforcementUrlNote":"⚠ The enforcement body must match the EAA sector (Annex I section) of your product. For example: audio-visual media (Section VII) uses a different authority than e-commerce (Section IX) or banking (Section X). Check your national transposition law for the correct authority per sector.","complaintsProcess":"Formal Complaints Procedure","complaintsProcessBadge":"Required by most enforcement bodies","complaintsProcessPlaceholder":"Describe the steps a user should take to submit a formal complaint, including contact method, acknowledgement timeframe, resolution timeframe, and how to escalate to the enforcement body if unsatisfied.","complaintsProcessTimelinesNote":"⚠ Response timelines for accessibility complaints vary by member state, they are set by national transposition law, not the EAA itself. Check your national law for the legally required response times before committing to specific timeframes in this statement.","complaintsProcessRequiredNote":"⚠ Most EU enforcement bodies require this section. Simply naming the enforcement body is not sufficient, the statement must explain the steps a user takes to make a formal complaint and escalate. Use the template above as a starting point.","complaintsProcessProvided":"✓ Complaints procedure provided.","insertGuidedTemplate":"Insert guided template","insertExample":"Insert example","approvalHeading":"Formal Approval (optional)","approvalIntro":"The name and title of the person who reviewed and approved this accessibility statement. Demonstrates accountability.","approverName":"Approver Name","approverNamePlaceholder":"E.g. Jane Smith","approverTitle":"Approver Title / Function","approverTitlePlaceholder":"E.g. Head of Digital, Accessibility Officer","additionalInfo":"Additional Information (optional)","additionalInfoPlaceholder":"Any additional notes, roadmap information, or context you wish to include…","languageRequirementHeading":"Language requirement, {countryName}"},"examples":{"complaintsProcess":"If you are not satisfied with our response to your accessibility feedback, you may raise a formal complaint:\n\n1. Contact our Accessibility Officer at accessibility@[yourdomain.com] with the subject \"Formal Accessibility Complaint\".\n2. We will acknowledge your complaint within 5 working days and provide a full response within 20 working days.\n3. If you remain dissatisfied after our response, you have the right to escalate to the national enforcement body:\n {enforcementBody}\n {enforcementUrl}\n\nThe enforcement body can investigate your complaint and, where appropriate, require us to take corrective action.","additionalInfo":"We are committed to improving the accessibility of our digital services. We are working towards full {wcagVersion} Level {wcagLevel} compliance and regularly review our website to identify and fix issues.\n\nIf you are experiencing difficulty accessing any content on this website, please contact us using the details above and we will endeavour to provide an accessible alternative within 5 working days."}},"step5":{"label":"Preview","heading":"Step 5: Preview & Download","intro":"Review your accessibility statement below, select the output language, then download or copy.","selfAccessibilityHeading":"Statement accessibility requirement","selfAccessibilityBody":"The published accessibility statement page must itself conform to WCAG 2.1 Level AA. Before publishing, verify the HTML file passes automated testing (axe, WAVE) and is navigable by keyboard and screen reader. An inaccessible accessibility statement is a direct contradiction in terms, and the first thing enforcement bodies check.","outputLanguage":"Output Language","downloadHtml":"Download HTML","copyPlainText":"Copy Plain Text","copied":"Copied!","copyEmbedHtml":"Copy Embed HTML","copyJsonLd":"Copy JSON-LD","copyFeedbackForm":"Copy Embeddable Feedback Form HTML","outputFormats":{"htmlHeading":"HTML Download","htmlBody":"Publish-ready branded HTML file. Upload to your website at /accessibility-statement.","jsonLdHeading":"JSON-LD","jsonLdBody":"Machine-readable metadata. Add inside a <script type=\"application/ld+json\"> tag in your HTML head.","feedbackFormHeading":"Feedback Form","feedbackFormBody":"Drop-in HTML form for collecting accessibility reports from users. No backend required."},"previewLabel":"Accessibility statement preview","backEdit":"← Back & Edit","annexV":{"title":"EAA Annex V, Mandatory disclosures","satisfiedCount":"{satisfied} / {total} present","missingNotice":"Your statement is missing {failed, plural, one {# item} other {# items}} required by EAA Annex V. Add them before export so the published statement is structurally complete.","ariaLabel":"EAA Annex V Compliance Card","items":{"compliance-status":{"label":"Compliance status","citation":"Annex V §a, declaration of conformity status","hint":"Pick one of: fully / partially / not compliant in Step 2."},"non-accessible-content":{"label":"Non-accessible content listed","citation":"Annex V §b, list of non-conformities","hint":"If not fully compliant, list known barriers in Step 2 (free-text or per-issue entries)."},"alternatives":{"label":"Accessible alternatives offered","citation":"Annex V §c, alternatives where conformity not achieved","hint":"Describe interim alternatives in Step 2 (e.g. Phone hotline, manual fulfilment)."},"feedback-mechanism":{"label":"Feedback mechanism (email / phone / address)","citation":"Annex V §d, feedback channel for users","hint":"Add at least one contact channel in Step 4."},"enforcement-contact":{"label":"National enforcement body identified","citation":"Annex V §e, escalation route","hint":"Select the project's jurisdiction in Step 1, the wizard will fill the enforcement body for you."},"last-revision-date":{"label":"Last revision date","citation":"Annex V §f, date of last update","hint":"Set the last-reviewed date in Step 1."},"preparation-method":{"label":"Preparation method (self / third-party / combination)","citation":"Annex V §g, assessment method","hint":"Pick assessment method in Step 3, self-assessment, third-party audit, or a combination."},"preparation-date":{"label":"Date statement was prepared","citation":"Annex V §h, date of preparation","hint":"Set the preparation date in Step 1."},"methodology":{"label":"Methodology (standard + tools)","citation":"Annex V §i, methodology used","hint":"Pick the EN 301 549 version in Step 2 and at least one assessment approach in Step 3."}}},"permalink":{"snapshotSaved":"Snapshot saved","publicPermalinkLabel":"Public permalink:","immutabilityNote":"Link to this from your live statement page. The snapshot is immutable, if you edit the statement and re-export, the new snapshot will reference this one in its chain, so a regulator can verify exactly when each disclosure changed.","signInPrompt":"Sign in to publish a public, tamper-evident permalink for this snapshot. Your locally-generated hash is","fullHashLabel":"Full SHA-256:","snapshotErrorNotice":"Statement was downloaded, but the permalink snapshot service did not respond: {error}. You can re-trigger by downloading again."},"backingEvidence":{"heading":"Backing evidence, Statement ↔ Technical File","linkedBadge":"{count} linked","intro":"Tie each Annex V claim to the <code>auditId</code>s in your Evidence Vault that back it. Linked records appear as <code>[Evidence: …]</code> footnotes on the exported statement and as a Statement Backing Evidence Index in your Technical File ZIP.","loading":"Loading your Evidence Vault…","empty":"No evidence records in your Vault yet. Export a scan or audit from any tool (e.g. Site Scanner, Whole-Site Scanner, Contrast Suite), Pro exports are stored in the Vault and become linkable here.","recommendedHeading":"Recommended for this claim","noneRecommended":"No records currently tagged to the Annex IV sections that typically back this claim.","showOthersToggle":"Show all other vault records ({count})","untitledTool":"Untitled tool"},"enforcementPreview":{"heading":"Enforcement body","missingForCountry":"No EU-27 enforcement body on file for country code <code>{country}</code>. Verify the country selection in Step 1, the exported statement will not cite an authority.","citedHeading":"Enforcement body cited, {country}","complaintFormLabel":"Complaint form","responseWindow":"Statutory response window: {days} days."}}},"issues":{"heading":"Known Accessibility Issues","addIssue":"Add Issue","removeIssue":"Remove","fields":{"what":"What is the barrier?","wcagCriterion":"WCAG Success Criterion","reason":"Reason","howAddressed":"How is it being addressed?","targetDate":"Target Fix Date"},"reasons":{"technical":"Technical limitation","thirdParty":"Third-party content","burden":"Disproportionate burden","inProgress":"Remediation in progress"},"builder":{"heading":"Structured Issue Builder","subheading":"Recommended, creates a per-issue breakdown with problem description, WCAG criterion, and remediation plan","addButton":"+ Add issue","newIssue":"New accessibility issue","editIssue":"Edit issue","issueLabel":"Issue {number}: {description}","wcagPrefix":"WCAG: {criterion}","howAddressedPrefix":"How addressed: {plan}","targetPrefix":"Target: {date}","edit":"Edit","delete":"Delete","barrierLabel":"What is the barrier?","barrierPlaceholder":"Describe the specific accessibility barrier, e.g. 'Product listing images are missing descriptive alt text on the product catalogue pages'","wcagCriterionLabel":"WCAG Success Criterion","wcagCriterionPlaceholder":"E.g. 1.1.1 Non-text Content","reasonLabel":"Reason for non-compliance","reasonSelectPlaceholder":"Select reason,","reasonInProgress":"Under active remediation (with planned fix date)","reasonTechnical":"Technical constraint (describe in remediation field)","reasonThirdParty":"Third-party content outside our control","reasonBurden":"Disproportionate burden claimed (Article 14)","howAddressedLabel":"How will this be addressed?","howAddressedPlaceholder":"Describe the remediation plan, e.g. 'CMS workflow will be updated to require alt text on all product images. Training scheduled for content team in Q3 2026.'","targetDateLabel":"Target resolution date","saveAdd":"Add issue","saveUpdate":"Update issue","cancel":"Cancel","emptyHint":"No structured issues added yet. Click \"+ Add issue\" to begin, or use the free-text field above."}},"journey":{"heading":"Journey-Level Conformance Summary","headingNote":"(helps users understand which tasks are accessible)","addJourney":"+ Add journey","emptyHint":"Optional but strongly recommended: instead of just saying \"partially conformant\", tell users which specific journeys are accessible and which are not.","journeyPlaceholder":"E.g. Product search and browsing","statusConformant":"✓ Conformant","statusPartial":"⚠ Partially conformant","statusNonConformant":"✗ Non-conformant","removeJourney":"Remove journey"},"scopeLabels":{"web":"Website / web application only","webAndIos":"Website and iOS mobile app","webAndAndroid":"Website and Android mobile app","webAndMobile":"Website and mobile apps (iOS and Android)","allPlatforms":"Website, mobile apps, and desktop software","desktop":"Desktop software only"},"actions":{"previous":"Previous","back":"← Back","next":"Next","generateStatement":"Generate Statement","downloadHtml":"Download HTML","downloadWord":"Download Word","copyToClipboard":"Copy to Clipboard"},"validation":{"entityNameRequired":"Legal Entity Name is required.","feedbackEmailRequired":"Feedback Email is required.","feedbackEmailInvalid":"Invalid email format.","requiredMarker":"*"},"article16":{"heading":"Article 16 / Annex V Compliance Check","allPassed":"All checks passed","needAttention":"{count, plural, one {# item needs attention} other {# items need attention}}","intro":"The following checklist confirms your statement contains all mandatory elements required by EAA Article 16 and Annex V. Resolve any red items before publishing.","goBackButton":"← Go back and complete missing fields","checks":{"entityName":"Legal entity name","entityNameNote":"Required, Annex V element 1","feedbackEmail":"Feedback email (contact mechanism)","feedbackEmailNote":"Required, Annex V element 6: feedback mechanism","enStandard":"Applicable standard cited (EN 301 549 version)","enStandardNote":"Required, Annex V element 2","complianceStatus":"Conformance status declared","complianceStatusNote":"Required, Annex V element 3: fully / partially / not compliant","nonAccessibleContent":"Non-accessible content described (if partial/non-compliant)","nonAccessibleContentNote":"Required when not fully compliant, Annex V element 4: use structured issue builder or free-text","burdenClaims":"Disproportionate burden claims documented (if any)","burdenClaimsNote":"Required if invoking Article 14 exemption, Annex V element 5","interimAlternative":"Interim accessible alternative described (when burden claimed)","interimAlternativeNote":"Required under Article 13(2) when burden is invoked, provides users with an alternative means of access","enforcementBody":"National enforcement body named","enforcementBodyNote":"Required, Annex V element 7: escalation route for users","nationalLaw":"National transposition law cited","nationalLawNote":"Required by enforcement bodies, cite national law, not just EU Directive","complaintsProcess":"Formal complaints procedure included","complaintsProcessNote":"Required by most EU enforcement bodies, explains how users escalate unresolved issues","dates":"Preparation date and review dates set","datesNote":"Required, statement must be dated and reviewed at least annually","annexISection":"EAA Annex I section identified","annexISectionNote":"Best practice, identifies which EAA product/service category applies","publicationUrl":"Statement publication URL provided","publicationUrlNote":"The statement must be published at a stable URL on the digital service, linked from main navigation or footer.","methodType":"Assessment method type declared (Annex V element 6)","methodTypeNote":"Annex V requires the method used to prepare the statement to be disclosed: self-assessment, third-party audit, or combination."}},"bilingual":{"noteSuffix":"The statement wizard currently generates one language at a time. Use the Output Language selector in Step 5 to export in each required language and publish both versions.","requirements":{"BE":"Belgium has three official languages (French, Dutch, German). Consider publishing your accessibility statement in all three, or at minimum in the language(s) used by your service. The enforcement body (UNIA) accepts French and Dutch.","LU":"Luxembourg has three official languages (French, German, Luxembourgish). Consider publishing your statement in French and German as a minimum.","FI":"Finland has two national languages (Finnish and Swedish). If your service targets Swedish-speaking users, consider publishing your statement in both languages.","IE":"Ireland has two official languages (English and Irish/Gaeilge). Public bodies may need to publish in both; private-sector digital services typically publish in English.","MT":"Malta has two official languages (Maltese and English). Most digital services publish in English; Maltese may be required for government-facing services."}},"countries":{"AT":"Austria","BE":"Belgium","BG":"Bulgaria","CY":"Cyprus","CZ":"Czechia","DE":"Germany","DK":"Denmark","EE":"Estonia","ES":"Spain","FI":"Finland","FR":"France","GR":"Greece","HR":"Croatia","HU":"Hungary","IE":"Ireland","IT":"Italy","LT":"Lithuania","LU":"Luxembourg","LV":"Latvia","MT":"Malta","NL":"Netherlands","PL":"Poland","PT":"Portugal","RO":"Romania","SE":"Sweden","SI":"Slovenia","SK":"Slovakia"},"annexI":{"categories":{"Website / Web Application":"Website / Web Application","Mobile Application":"Mobile Application","Desktop Software":"Desktop Software","Banking / Financial Service":"Banking / Financial Service","E-book Service":"E-book Service","Passenger Transport Service":"Passenger Transport Service","Audio-visual Media Service":"Audio-visual Media Service","E-commerce Service":"E-commerce Service","Electronic Communications Service":"Electronic Communications Service","Self-service Terminal":"Self-service Terminal","Other":"Other"},"sections":{"Website / Web Application":"Annex I, Section IX, E-commerce services and electronic communications services","Mobile Application":"Annex I, Section IX, E-commerce services and electronic communications services","Desktop Software":"Annex I, Section III, General-purpose computer hardware and operating systems","Banking / Financial Service":"Annex I, Section X, Banking services for consumers","E-book Service":"Annex I, Section VIII, E-books and dedicated reading software","Passenger Transport Service":"Annex I, Section XI, Passenger transport services","Audio-visual Media Service":"Annex I, Section VII, Audio-visual media services","E-commerce Service":"Annex I, Section IX, E-commerce services","Electronic Communications Service":"Annex I, Section VI, Electronic communications services","Self-service Terminal":"Annex I, Section V, Self-service terminals","Other":"Please identify the applicable Annex I section manually"}},"industryTemplateBodies":{"ecommerce":{"nonAccessible":"Some third-party payment widgets have limited keyboard support. Legacy product images may lack adequate alt text. Remediation is planned for Q3.","additionalInfo":"Scope: home page, product listing, product detail, shopping cart, checkout, order confirmation, user account. Testing tools: axe DevTools, NVDA + Firefox, keyboard-only navigation, colour contrast analyser, iOS VoiceOver."},"banking":{"nonAccessible":"Some complex data tables in the transaction history have limited screen reader support. PDF statements do not currently meet the PDF/UA (ISO 14289) standard. A remediation plan is underway with a target date of [insert date].","additionalInfo":"Scope: login, account dashboard, transaction history, funds transfer, statements, help and support, mobile application. Testing tools: axe DevTools, JAWS + Chrome, NVDA + Firefox, keyboard-only navigation, iOS VoiceOver, Android TalkBack."},"saas":{"nonAccessible":"Some dynamically rendered UI components may not fully expose ARIA states to all assistive technologies. The web application relies on complex interactive patterns (drag-and-drop, custom date pickers) that present challenges for keyboard-only users. This is under active development.","additionalInfo":"Scope: marketing site, sign-up and login, main application dashboard, settings, help documentation, onboarding flow. Testing tools: axe DevTools, keyboard-only navigation, NVDA + Firefox, colour contrast analyser."},"publicSector":{"nonAccessible":"Certain legacy PDF documents published before 2020 may not meet current PDF/UA (ISO 14289) standards. A review and remediation programme is in progress, prioritising high-traffic documents.","additionalInfo":"Scope: home page, service index, key service pages and forms, search, news and publications, contact pages, document downloads. Testing tools: axe DevTools, NVDA + Firefox, JAWS, keyboard-only navigation, colour contrast analyser, PDF accessibility checker."},"media":{"nonAccessible":"Archived video content published before 2023 may lack closed captions or audio descriptions. User-generated content in comment sections is not systematically reviewed for accessibility. A phased remediation plan is in place.","additionalInfo":"Scope: home page, article pages, video player, podcast player, search results, newsletter sign-up, archive pages. Testing tools: axe DevTools, keyboard-only navigation, NVDA + Firefox, colour contrast analyser, caption quality review."}},"versionHistory":{"heading":"Version History ({count} saved)","show":"▼ Show","hide":"▲ Hide","draftFallback":"Draft","savedAt":"Saved {datetime}","restore":"Restore"},"export":{"toolName":"Accessibility Statement Wizard","summaryReady":"Accessibility statement for {entityName} ({language})","summaryEmpty":"Complete the wizard above to enable export","documentTitle":"Accessibility Statement, {entityName}","wcagLevelValue":"{wcagVersion} Level {wcagLevel}","labels":{"entityName":"Entity name","website":"Website","country":"Country","complianceStatus":"Compliance status","wcagLevel":"WCAG level","enStandard":"EN standard","identifiedIssues":"Identified issues","burdenClaims":"Disproportionate burden claims","interimAlternative":"Interim alternative","preparationDate":"Preparation date","lastReviewed":"Last reviewed"},"values":{"fully":"Fully compliant","partially":"Partially compliant","not":"Not compliant","burdenDocumented":"Yes, documented","burdenNone":"None","interimProvided":"Provided","interimNotSpecified":"Not specified","dash":","},"formats":{"htmlEvidence":"Evidence-stamped HTML","htmlEvidenceHint":"Self-contained, brandable","htmlPublish":"Publish-ready HTML","htmlPublishHint":"For /accessibility URL","txt":"Plain text","txtHint":".txt","json":"JSON","jsonHint":"For re-processing"}},"templateDefaults":{"enforcementBodyFallback":"[National enforcement body]","enforcementUrlFallback":"[Enforcement body website]"},"samplePreview":{"name":"Statement Wizard","description":"The Statement Wizard creates an EAA Annex V compliant accessibility statement in 7 EU languages, with your organisation's branding. Publish directly to your website as HTML."},"microenterpriseShortCircuit":{"kicker":"EAA Article 4(5), Microenterprise","headlinePartial":"Your services qualify for the EAA microenterprise exemption","headlineFull":"Your organisation appears exempt under EAA Article 4(5)","subBodyPartial":"We can generate a 1-page Microenterprise Notice that covers your exempt services. Your products remain in scope and still require an Article 15 Declaration of Conformity.","subBodyFull":"Instead of the full Annex V statement, generate a 1-page Microenterprise Notice, a defensible record that you ran the eligibility check and documented the result.","legalBasisLabel":"Legal basis: {article}","ariaLabel":"Microenterprise exemption short-circuit","dismissAria":"Dismiss banner and continue with full wizard","dismissButton":"Dismiss","generateButton":"Generate Microenterprise Notice (DOCX)","generatingButton":"Generating…","continueButton":"Continue with full statement"}},"supply-chain-checklist":{"meta":{"title":"Supply Chain Compliance Checklist, EAA Articles 7–12","description":"EAA Articles 7–12 compliance checklist, verify that every economic operator in your supply chain meets European Accessibility Act requirements for manufacturers, importers, and distributors."},"header":{"title":"Supply Chain Compliance Checklist","subtitle":"EAA Articles 7–12, Manufacturer, Importer & Distributor Obligations","description":"EAA Articles 7–12 compliance checklist, verify that every economic operator in your supply chain meets European Accessibility Act requirements for manufacturers, importers, and distributors."},"features":{"f1":"EAA Articles 7–12 full coverage","f2":"Manufacturer, importer & distributor obligations","f3":"33 checkpoints across 5 categories","f4":"Pass / Partial / Fail / N/A with notes per item","f5":"How-to-test guidance and common failures for every checkpoint","f6":"Links to relevant testing tools on AccessibilityRef","f7":"Progress auto-saved in your browser","f8":"Export Word report with notes","f9":"Direct links to EAA Directive articles"},"categories":{"manufacturer":{"label":"Manufacturer Obligations (Article 7)","description":"EAA Article 7, Manufacturers must design compliant products, prepare documentation, maintain conformity, and cooperate with authorities."},"importer":{"label":"Importer Obligations (Article 9)","description":"EAA Article 9, Importers must verify compliance before placing products on the EU market and maintain documentation."},"distributor":{"label":"Distributor Obligations (Article 10)","description":"EAA Article 10, Distributors must exercise due care and verify compliance before making products available."},"traceability":{"label":"Supply Chain Traceability (Article 12)","description":"EAA Article 12, Economic operators must be able to identify their suppliers and customers for 5 years."},"rebranding":{"label":"Rebranding & Modification (Article 11)","description":"EAA Article 11, When an importer or distributor places a product under their own brand or modifies it, they take on full manufacturer obligations."}},"items":{"m1":{"text":"Products are designed and manufactured in accordance with applicable Annex I accessibility requirements.","guidance":"All products placed on the EU market must meet the accessibility requirements in Annex I that apply to their category. This is the core manufacturer obligation.","testMethod":"Obtain the product's Annex I applicability matrix. For each applicable requirement, verify that the product design and implementation addresses it. Cross-reference with EN 301 549 harmonised standard clauses where available. If any applicable requirement has no design evidence, this fails.","commonFailures":["Product launched without any Annex I mapping, accessibility requirements never identified","Design team addressed web accessibility but ignored hardware/physical accessibility requirements","Requirements were identified but not implemented due to cost-cutting during development","Product meets some Annex I requirements but critical ones (e.g. Screen reader support) are missing"]},"m2":{"text":"Technical documentation has been prepared in accordance with Annex IV.","guidance":"The technical documentation must demonstrate how the product meets accessibility requirements. It must include a general product description, list of applied harmonised standards, and explanations of how requirements are met.","testMethod":"Request the technical documentation file. Verify it contains: (1) a general product description, (2) a list of all applicable Annex I requirements, (3) references to harmonised standards applied (e.g. EN 301 549), (4) a description of how each requirement is met, and (5) test results or evidence. If the file does not exist or is incomplete, this fails.","commonFailures":["No technical documentation file exists, compliance was assumed rather than documented","Documentation lists standards but does not explain how each requirement is specifically met","Technical file was prepared for initial launch but never updated after product changes","Documentation references outdated versions of harmonised standards"]},"m3":{"text":"Conformity assessment procedure (Annex IV) has been carried out.","guidance":"The manufacturer must perform the internal production control procedure described in Annex IV. This includes verifying the manufacturing process produces compliant products.","testMethod":"Review the conformity assessment records. Verify that internal production control was carried out including: (1) examination of the technical documentation, (2) verification that the manufacturing process produces products matching the documentation, and (3) sign-off by a responsible person. If no assessment was performed, this fails.","commonFailures":["No formal conformity assessment was ever conducted, the CE mark was applied without evidence","Assessment performed by an unqualified person with no accessibility expertise","Assessment only covered one variant of the product, not the full range","Assessment was done once at launch but the product has since been significantly updated"]},"m4":{"text":"EU Declaration of Conformity has been drawn up.","guidance":"A formal written declaration following the Annex IV model must be prepared. Use the EU Declaration of Conformity Generator to create this document.","testMethod":"Locate the EU Declaration of Conformity document. Verify it includes: (1) manufacturer name and address, (2) product identification (model, type, batch), (3) statement that the declaration is issued under sole responsibility of the manufacturer, (4) references to relevant harmonised standards, and (5) date and signature. If no declaration exists, this fails.","commonFailures":["No formal EU Declaration of Conformity exists for the product","Declaration exists but references the wrong Directive (e.g. EMC instead of EAA)","Declaration is unsigned or undated","Declaration references harmonised standards that were not actually applied"]},"m5":{"text":"CE marking has been affixed to the product.","guidance":"The CE marking must be affixed visibly, legibly, and indelibly to the product, its data plate, or packaging before market placement.","testMethod":"Physically inspect the product, its data plate, and packaging. Verify the CE marking is: (1) visible without removing packaging, (2) legible (minimum 5mm height), (3) indelible (cannot be rubbed off), and (4) proportioned correctly per Regulation 765/2008 Annex II. If the CE mark is missing, too small, or easily removable, this fails.","commonFailures":["CE marking is completely absent from the product and packaging","CE mark is printed on a sticker that peels off easily","CE mark is smaller than the required 5mm minimum height","CE mark resembles but does not match the official proportions (China Export confusion)"]},"m6":{"text":"Technical documentation and EU Declaration are retained for at least 5 years after the last product is placed on market.","guidance":"Both the technical file and the declaration must be kept available for authorities for a minimum of 5 years. Set a document retention policy.","testMethod":"Check the document management system or filing records. Verify: (1) a retention policy exists specifying 5-year minimum, (2) documents are stored in a retrievable location (digital or physical), (3) the retention clock starts from the date the last unit was placed on market, not the date of document creation. If no retention policy exists, this is partial at best.","commonFailures":["No document retention policy exists, files are stored ad hoc on individual laptops","Documents were retained but accidentally deleted during a server migration","Retention period is calculated from product launch rather than last unit placed on market","Paper-only copies stored in an unlabelled box with no retrieval system"]},"m7":{"text":"Procedures are in place to ensure series production remains in conformity.","guidance":"It is not enough to test one unit. The manufacturing process must be monitored to ensure every unit produced meets accessibility requirements. Changes to production or standards must trigger reassessment.","testMethod":"Review the quality management documentation. Verify that: (1) production monitoring includes accessibility checkpoints, (2) there is a change control process that flags accessibility-impacting changes, (3) periodic audits or spot-checks of production units are conducted for accessibility, and (4) standard updates trigger a review. If production monitoring does not mention accessibility, this fails.","commonFailures":["Quality control checks physical defects but has no accessibility checkpoints","Software updates are deployed without checking impact on screen reader compatibility","Component supplier changed but no reassessment of accessibility impact was done","Production monitoring exists but only for the initial product variant, not subsequent models"]},"m8":{"text":"Product bears a type, batch, or serial number for identification.","guidance":"Every product must be individually identifiable. Affix a model number, batch code, or serial number on the product or packaging.","testMethod":"Inspect the product and its packaging. Look for a type number, batch number, or serial number. Verify it is: (1) present on the product itself (not just the box), (2) legible, and (3) unique enough to trace back to production records. If no identification number exists, this fails.","commonFailures":["Digital-only product with no version number or build identifier visible to users","Serial number printed on packaging but not on the product itself","Batch number exists but is not linked to any production records","Identification number is printed so small it cannot be read without magnification"]},"m9":{"text":"Manufacturer name, registered trade name, and contact address are on the product or packaging.","guidance":"Consumers and authorities must be able to identify and contact the manufacturer. Include legal name and postal address (a URL alone is not sufficient).","testMethod":"Check the product, its data plate, and packaging for the manufacturer's: (1) legal company name, (2) registered trade name or trademark, and (3) postal contact address. A URL or email alone is insufficient, a physical address is required. If any of these are missing, this is partial or fail.","commonFailures":["Only a website URL is provided with no physical postal address","Trade name is shown but the legal entity name is missing","Contact information is on the outer shipping box but not on the product or retail packaging","Address provided is a PO Box rather than a registered business address"]},"m10":{"text":"Instructions and safety information are provided in an accessible and understandable language.","guidance":"Product instructions must be in the official language(s) of the Member State where the product is sold, and must be accessible (e.g. Available in HTML or accessible PDF, not just a printed leaflet).","testMethod":"Obtain the product instructions and safety information. Verify: (1) they are in the official language(s) of the target market, (2) they are available in at least one accessible digital format (HTML, accessible PDF, or EPUB), (3) they can be read by a screen reader, and (4) technical jargon is explained. If instructions are only available as a printed leaflet with no digital accessible version, this fails.","commonFailures":["Instructions only available as a printed paper leaflet with no digital version","Digital instructions exist but are scanned image PDFs that screen readers cannot read","Instructions available in English only but the product is sold in non-English-speaking markets","Safety warnings use colour-coding alone (red = danger) with no text labels"]},"m11":{"text":"When non-conformity is identified, corrective measures are taken immediately (correction, withdrawal, or recall).","guidance":"If you discover that a product on the market does not meet accessibility requirements, you must act immediately, correct the product, withdraw it from sale, or recall it from consumers.","testMethod":"Review incident logs and corrective action records. Verify: (1) a process exists for identifying non-conformity, (2) past incidents (if any) were acted upon immediately, (3) corrective actions were documented including timeline and outcome, and (4) the process includes withdrawal/recall escalation criteria. If no process exists, this fails even if no incident has occurred.","commonFailures":["No corrective action process exists, accessibility issues are treated as feature requests","Non-conformity was identified but corrective action took months rather than days","Product was corrected via software update but affected hardware units were not recalled","Corrective actions are taken but not documented anywhere"]},"m12":{"text":"Market surveillance authorities are informed immediately when non-conformity is identified.","guidance":"You cannot quietly fix the issue. National authorities must be notified of the non-conformity, the details of any corrective action taken, and the markets affected.","testMethod":"Check whether a notification procedure to market surveillance authorities exists. Verify: (1) contact details for relevant national authorities are on file, (2) a notification template or procedure is documented, (3) past non-conformities (if any) were reported to authorities. If there is no authority notification procedure, this fails.","commonFailures":["No contact details for market surveillance authorities are on file","Non-conformity was fixed internally but never reported to authorities","Notification was sent but only to authorities in one Member State, not all affected markets","Team assumed that fixing the issue removes the obligation to notify"]},"m13":{"text":"A complaints register is maintained and monitored.","guidance":"Keep a log of all accessibility-related complaints received from consumers, distributors, or authorities. Review complaints regularly and use them to improve compliance.","testMethod":"Request access to the complaints register. Verify: (1) a dedicated log exists (spreadsheet, CRM, or database), (2) it tracks complaint date, source, description, and resolution, (3) accessibility-related complaints are tagged or categorised separately, and (4) the register is reviewed periodically (e.g. Monthly). If no register exists, this fails.","commonFailures":["No complaints register exists, complaints go into a general customer service inbox and are lost","Register exists but does not categorise complaints by type (accessibility vs. Other)","Complaints are logged but never reviewed or analysed for patterns","Register is maintained by one person and is inaccessible when they are absent"]},"m13b":{"text":"If the manufacturer is established outside the EU, a written mandate has been issued to an EU-based authorised representative.","guidance":"Non-EU manufacturers must designate an authorised representative established in the EU. The mandate must specify the representative's powers and be signed by both parties. The representative takes on the manufacturer's obligations under Article 7(2)–(9).","testMethod":"If the manufacturer's registered address is outside the EU/EEA: (1) verify a written mandate exists naming a specific EU-based legal entity as authorised representative, (2) confirm the mandate is signed and specifies Article 8(2) obligations (keeping technical file, cooperating with authorities, providing documentation), (3) confirm the representative's name and contact details appear on the product and/or in the EU declaration of conformity. If no mandate exists, this is a critical gap, the product cannot lawfully be placed on the EU market.","commonFailures":["Manufacturer is headquartered outside the EU but no authorised representative has been appointed","A representative is named in documentation but no formal written mandate exists","The mandate exists but does not cover the full scope of Article 8(2) obligations","EU declaration of conformity does not include the authorised representative's details"]},"m14":{"text":"The manufacturer cooperates with authorities on request, providing documentation and information.","guidance":"When a market surveillance authority requests information or documentation, you must respond promptly. This includes providing the technical file, EU declaration, and test results in an accessible format.","testMethod":"Verify that: (1) a contact person or department is designated to handle authority requests, (2) all required documents (technical file, declaration, test results) are accessible and retrievable within a reasonable timeframe (48 hours), and (3) documents can be provided in accessible formats if requested. If no designated contact exists, this is partial.","commonFailures":["No one in the organisation is designated to handle authority requests","Documents exist but are scattered across departments and would take weeks to compile","Technical file is only available in the original language and cannot be translated quickly","Team is unaware that authorities can request accessibility documentation at any time"]},"i1":{"text":"Only compliant products are placed on the EU market.","guidance":"Before importing, verify that the manufacturer has met all Article 7 obligations. Do not import products that you know or should know are non-compliant.","testMethod":"Review the due diligence checklist used before importing. Verify: (1) there is a formal pre-import review process, (2) the manufacturer's Article 7 compliance is checked, (3) evidence of conformity is obtained before purchase orders are placed, and (4) non-compliant products are rejected. If no pre-import review process exists, this fails.","commonFailures":["Products imported based solely on price and availability with no compliance check","Importer relied on the manufacturer's verbal assurance of compliance without documentation","Due diligence was performed for the first shipment but not for subsequent orders","Compliance review exists but does not include accessibility, only safety and EMC"]},"i2":{"text":"Before placing on market: manufacturer has completed Annex IV conformity assessment.","guidance":"Request and review evidence that the manufacturer performed the conformity assessment procedure. Do not rely on verbal assurances.","testMethod":"Request the manufacturer's conformity assessment records. Verify: (1) a written record of the Annex IV internal production control procedure exists, (2) it is signed and dated, (3) it references the specific product being imported, and (4) it was completed before the product was placed on market. If the manufacturer cannot provide this, this fails.","commonFailures":["Manufacturer says 'we did it' but cannot produce any written evidence","Conformity assessment exists but for a different product model","Assessment was completed after the product was already placed on market","Assessment document exists but is undated and unsigned"]},"i3":{"text":"Before placing on market: technical documentation exists.","guidance":"Obtain confirmation that the full technical file exists and can be produced on request. You do not need to hold a copy, but you must be satisfied it exists.","testMethod":"Request written confirmation from the manufacturer that the technical file exists. Ideally obtain a table of contents or summary of the technical file. Verify: (1) the manufacturer confirms the file exists, (2) the confirmation is in writing, and (3) the manufacturer can produce it within a reasonable timeframe if authorities request it. If the manufacturer cannot confirm, this fails.","commonFailures":["Importer has never asked the manufacturer whether a technical file exists","Manufacturer confirms the file exists but it is actually incomplete or outdated","Technical file exists but is stored in a format or language the importer cannot verify","Manufacturer went out of business and the technical file is inaccessible"]},"i4":{"text":"Before placing on market: CE marking is affixed and required documents accompany the product.","guidance":"Physically verify CE marking on the product or packaging. Check that required documentation (instructions, safety information, declaration reference) is present.","testMethod":"Inspect a sample unit from each shipment. Verify: (1) CE marking is present, visible, and correctly proportioned, (2) instructions are included in the correct language(s), (3) safety information is present, and (4) a reference to the EU Declaration of Conformity is included. If any element is missing from the sample, this fails for the shipment.","commonFailures":["CE marking is on the manufacturer's website but not physically on the product or packaging","Instructions included but only in the manufacturer's language, not the target market language","First shipment was checked but subsequent shipments were accepted without inspection","CE marking is present but required safety information leaflet is missing from the box"]},"i5":{"text":"Importer's name, registered trade name, and contact address are on the product or packaging.","guidance":"In addition to the manufacturer's details, the importer must display their own identification and contact information on the product or packaging.","testMethod":"Inspect the product and packaging. Verify the importer's: (1) legal company name, (2) registered trade name or trademark, and (3) postal contact address are displayed. A URL alone is insufficient. If the importer's details are missing entirely, this fails.","commonFailures":["Only the manufacturer's details are on the packaging, the importer is not identified","Importer's name is on the shipping carton but not on the retail packaging or product","A website URL is provided instead of a postal address","Importer details were added via a sticker that falls off during handling"]},"i6":{"text":"Instructions and information are provided in an accessible language required by the Member State.","guidance":"The importer must ensure instructions are available in the official language(s) of the target market, in an accessible format.","testMethod":"Check the product instructions against the target market requirements. Verify: (1) instructions are in the official language(s) of the Member State, (2) they are in an accessible format (not just a printed leaflet), and (3) technical terms are explained or translated. If instructions are only in the manufacturer's language, this fails.","commonFailures":["Instructions shipped in Chinese or English only for a product sold in Germany or France","Instructions translated but the translation is poor quality with key safety terms mistranslated","Translated instructions provided as a scanned PDF that screen readers cannot read","Instructions available online but no indication of the URL is included with the product"]},"i7":{"text":"A copy of the EU Declaration of Conformity is kept for at least 5 years.","guidance":"The importer must retain a copy of the EU declaration and be able to provide the technical documentation to authorities on request for 5 years.","testMethod":"Check the importer's document management system. Verify: (1) a copy of the EU Declaration of Conformity is on file, (2) a retention policy of at least 5 years exists, (3) the 5-year period runs from the last product placed on market, and (4) the document is retrievable within 48 hours. If no copy is retained, this fails.","commonFailures":["Importer never requested or retained a copy of the EU Declaration","Copy was received but stored on an employee's laptop that was later wiped","Retention policy is 3 years instead of the required 5 years","Declaration is retained but the importer cannot locate it quickly when asked"]},"i8":{"text":"A complaints register is maintained by the importer.","guidance":"Like manufacturers, importers must keep a log of accessibility complaints and non-conforming products, and inform distributors of issues.","testMethod":"Request access to the importer's complaints register. Verify: (1) a dedicated log exists, (2) it tracks complaint date, source, product identification, description, and resolution, (3) accessibility-related complaints are identifiable, and (4) distributors are notified of non-conformity issues. If no register exists, this fails.","commonFailures":["No complaints register, returns are processed without logging the reason","Register exists but does not link complaints to specific product batches","Accessibility complaints are mixed in with general quality complaints and not flagged","Distributors are not notified when the importer discovers a non-conformity"]},"i9":{"text":"Corrective measures are taken immediately when non-conformity is identified.","guidance":"If you discover that an imported product does not comply, you must correct, withdraw, or recall it, and notify the manufacturer and authorities.","testMethod":"Review the importer's corrective action procedure. Verify: (1) a written process exists for handling non-conformity, (2) it includes escalation to the manufacturer, (3) it includes notification to market surveillance authorities, (4) it includes withdrawal/recall decision criteria, and (5) past incidents (if any) were handled according to the process. If no procedure exists, this fails.","commonFailures":["No corrective action process, non-compliant products remain on sale until stock runs out","Importer notified the manufacturer but did not notify market surveillance authorities","Withdrawal was ordered but distributors were not informed, so products continued to sell","Corrective action taken for one Member State but not others where the product is also sold"]},"d1":{"text":"Due care is exercised before making a product available on the market.","guidance":"Distributors must verify that the product bears CE marking, is accompanied by required documents, has manufacturer and importer identification, and has accessible instructions in the correct language.","testMethod":"Review the distributor's incoming goods inspection process. Verify that the checklist includes: (1) CE marking present, (2) manufacturer/importer identification on product or packaging, (3) instructions present in the correct language, (4) instructions in an accessible format. Spot-check 3 products on shelf against these criteria. If the inspection process does not exist or products on shelf fail checks, this fails.","commonFailures":["No incoming goods inspection, products are shelved directly from the shipping container","Inspection checklist exists for safety but does not include accessibility or CE marking checks","Products are checked at warehouse level but not at individual store level","Due care was exercised initially but became lax after the first few shipments"]},"d2":{"text":"Non-compliant products are not made available until brought into conformity.","guidance":"If a distributor identifies or suspects non-compliance, they must not sell the product. Inform the manufacturer or importer and, where there is a risk, inform authorities.","testMethod":"Review the distributor's non-conformity handling procedure. Verify: (1) a hold/quarantine process exists for suspected non-compliant products, (2) products are not sold while under investigation, (3) the manufacturer/importer is notified, and (4) authorities are informed where there is a risk. If no hold process exists, this fails.","commonFailures":["Non-compliant products are sold at a discount rather than quarantined","Suspect products are pulled from shelves but the manufacturer is never informed","Hold process exists on paper but staff are not trained to recognise non-compliance indicators","Products are held temporarily but released back to sale without resolution"]},"d3":{"text":"Storage and transport conditions do not jeopardise compliance.","guidance":"Products must be stored and transported in conditions that preserve their accessibility features. Environmental damage or packaging degradation that affects accessibility is the distributor's responsibility.","testMethod":"Inspect storage and transport conditions. Verify: (1) products with screens or displays are stored within temperature/humidity specifications, (2) packaging containing accessible instructions is not damaged or wet, (3) Braille labels or tactile features are not worn down by storage conditions, and (4) battery-powered accessibility features are not degraded by shelf life. If conditions could compromise accessibility features, this is partial.","commonFailures":["Products with Braille labels stored in conditions that cause label peeling or wear","Accessible instruction leaflets damaged by water or crushing during warehouse storage","Electronic products stored beyond battery shelf life, disabling accessibility features on first use","Display products handled in a way that damages screen readers or audio output hardware"]},"d4":{"text":"Corrective measures are taken when non-conformity is identified.","guidance":"If a product on sale is found non-compliant, the distributor must ensure correction, withdrawal, or recall, and notify the manufacturer/importer and authorities.","testMethod":"Review the corrective action procedure. Verify: (1) a process exists for withdrawal or recall at distributor level, (2) it includes notification to the manufacturer/importer, (3) it includes notification to market surveillance authorities, and (4) timelines are defined. Check past incidents (if any) against this process. If no procedure exists, this fails.","commonFailures":["No withdrawal process, non-compliant products are simply not reordered but remain on shelves","Distributor informs the importer but does not notify market surveillance authorities","Withdrawal from one location but the product remains available in other branches","No documented process, responses to non-conformity are ad hoc and inconsistent"]},"d5":{"text":"The distributor cooperates with authorities on request.","guidance":"Provide all requested information and documentation to market surveillance authorities. Cooperate with corrective actions.","testMethod":"Verify: (1) a contact person or department is designated to respond to authority requests, (2) relevant records (purchase orders, supply chain documentation, inspection records) are accessible, and (3) the designated person understands their obligations under the EAA. If no contact person is designated, this is partial.","commonFailures":["No designated contact for authority requests, inquiries go to general customer service","Records exist but are fragmented across multiple systems and cannot be compiled quickly","Staff are unaware of their obligation to cooperate with market surveillance authorities","Distributor cooperates but cannot provide product traceability information"]},"t1":{"text":"Each economic operator can identify every operator that supplied them a product.","guidance":"You must be able to tell authorities who you bought each product from, by name, with documentation. This applies to manufacturers, importers, and distributors alike.","testMethod":"Select 5 products at random. For each product, attempt to trace it back to the supplier. Verify: (1) the supplier's name and contact details are on record, (2) purchase documentation (invoices, purchase orders) is retrievable, and (3) the trail is complete (no gaps). If any product cannot be traced to its supplier, this fails.","commonFailures":["Products purchased through brokers or marketplaces with no record of the original supplier","Supplier records exist for recent purchases but older records have been deleted or lost","Supplier is identified by company name but no contact address or registration number is on file","Traceability exists for own-brand products but not for third-party products resold"]},"t2":{"text":"Each economic operator can identify every operator they supplied a product to.","guidance":"You must be able to tell authorities who you sold or distributed each product to. Maintain sales records that link to product identification numbers.","testMethod":"Select 5 products at random. For each, attempt to identify all downstream operators (distributors, retailers) the product was supplied to. Verify: (1) sales records link product identification to buyer details, (2) buyer names and contact details are on record, and (3) records are retrievable within 48 hours. If any product's downstream chain cannot be identified, this fails.","commonFailures":["Sales records show revenue per product but do not identify the buyer by name","Products sold through online marketplaces with no record of the end retailer","Sales records exist but do not link to specific product batches or serial numbers","Records are maintained per customer account but not per product identification number"]},"t3":{"text":"Traceability information is retained for at least 5 years.","guidance":"Keep supply chain records for a minimum of 5 years after the last transaction. The Commission may extend this period for products with longer economic life via delegated acts.","testMethod":"Check the data retention policy. Verify: (1) a written retention policy exists covering supply chain records, (2) it specifies a minimum of 5 years, (3) the 5-year clock starts from the last transaction (not the first), and (4) records from 4+ years ago are still retrievable. Request a record from at least 3 years ago as a spot-check. If the policy is missing or records are not retained, this fails.","commonFailures":["No written data retention policy, records are kept 'as long as we need them'","Retention policy specifies 3 years for commercial reasons, violating the 5-year minimum","Records purged during a system migration or ERP upgrade","Policy exists but IT systems auto-delete records after 2 years"]},"rb1":{"text":"If a product is placed on market under the importer/distributor's own name or trademark, all manufacturer obligations (Article 7) apply.","guidance":"White-labelling, rebranding, or own-brand products trigger the full set of manufacturer obligations, conformity assessment, technical documentation, CE marking, 5-year retention, complaints register, and authority cooperation.","testMethod":"Identify all products sold under the company's own brand or trademark. For each, verify: (1) the full Article 7 manufacturer obligation checklist has been completed (items m1–m14 above), (2) the company is identified as the manufacturer on the product, and (3) a complete technical file and EU Declaration exist under the company's name. If any own-brand product has not been treated with full manufacturer obligations, this fails.","commonFailures":["Company rebrands products from a supplier but treats itself as a distributor rather than a manufacturer","Own-brand product has CE marking from the original manufacturer rather than the rebrander","Technical file exists under the original manufacturer's name, not the company placing it on market","White-label agreement with the supplier does not address accessibility compliance responsibilities"]},"rb2":{"text":"If a product is modified in a way that may affect compliance, all manufacturer obligations apply.","guidance":"Any modification that could change the product's accessibility characteristics (hardware redesign, firmware update, UI changes) makes the modifier a deemed manufacturer. A full Annex IV conformity assessment must be repeated.","testMethod":"Review the product change log. Identify all modifications made after the original conformity assessment. For each modification, verify: (1) an impact assessment was performed to determine whether accessibility is affected, (2) if affected, a new conformity assessment was carried out, (3) the technical file was updated, and (4) the EU Declaration was reissued. If any accessibility-impacting modification was made without reassessment, this fails.","commonFailures":["Firmware update changed the UI navigation but no accessibility impact assessment was done","Hardware component was swapped for a cheaper alternative without checking accessibility impact","Product modification log does not exist, changes are made without formal tracking","Impact assessment was done but concluded 'no impact' without actually testing with assistive technologies"]}},"export":{"filename":"Supply-chain-checklist","title":"SUPPLY CHAIN COMPLIANCE CHECKLIST","subtitle":"EAA Articles 7\\u201312 \\u2014 Manufacturer, Importer & Distributor Obligations"},"links":{"eaaDirective":"EAA Directive 2019/882","eaaAnnexIV":"EAA Annex IV"}},"support-docs-checklist":{"meta":{"title":"Support & Documentation Checklist, EN 301 549 Chapter 12","description":"EN 301 549 Chapter 12 compliance checklist, verify that your product documentation and support services meet European Accessibility Act requirements."},"header":{"title":"Support & Documentation Checklist","subtitle":"EN 301 549 Chapter 12 Compliance Checklist","description":"EN 301 549 Chapter 12 compliance checklist, verify that your product documentation and support services meet European Accessibility Act requirements."},"features":{"f1":"EN 301 549 Chapter 12 full coverage","f2":"14 checkpoints across documentation, support & relay services","f3":"Pass / Partial / Fail / N/A with notes per item","f4":"How-to-test guidance and common failures for every checkpoint","f5":"Links to relevant testing tools on AccessibilityRef","f6":"Progress auto-saved in your browser","f7":"Export Word report with notes","f8":"Direct links to EAA Directive and EN 301 549"},"categories":{"docs":{"label":"Product Documentation Accessibility","description":"EN 301 549 §12.1 requires product documentation to be provided in accessible formats and to describe the accessibility features of the product."},"support":{"label":"Support Services Accessibility","description":"EN 301 549 §12.2 requires that support services (help desks, call centres, technical support) communicate accessibility information and are themselves accessible."},"relay":{"label":"Relay & Intermediary Services","description":"EN 301 549 §12.2.4 and EAA Annex I require that where relay or intermediary services are used, they meet accessibility needs."}},"items":{"d1":{"text":"Product documentation is available in at least one accessible format (HTML, accessible PDF, or EPUB).","guidance":"Documentation must not be locked inside image-only PDFs or proprietary formats that screen readers cannot parse. Provide at least one format that meets WCAG 2.1 AA.","testMethod":"Download or open the product documentation. Try navigating it with a screen reader (NVDA or VoiceOver). If it reads content correctly with headings and structure, it passes. If the screen reader reads nothing or reads garbled text, it fails. For PDFs, check the 'Tags' panel in Adobe Acrobat, if no tags exist, the PDF is not accessible.","commonFailures":["Documentation only available as a scanned/image-only PDF with no text layer","Help pages rendered as images or embedded in iframes that block screen readers","Documentation locked inside a proprietary format that requires specific software to read","HTML documentation that has no heading structure or semantic markup"]},"d2":{"text":"Documentation describes all accessibility features of the product or service.","guidance":"Users need to know what accessibility features exist, screen reader support, keyboard shortcuts, high contrast mode, text resizing, and how to activate them. This must be documented alongside other product features, not hidden in a separate section.","testMethod":"Search the product documentation for terms like 'accessibility', 'screen reader', 'keyboard', 'high contrast', 'magnification'. If no results appear, accessibility features are undocumented. Cross-reference with the product's actual accessibility features to verify completeness.","commonFailures":["Product has a dark mode but documentation doesn't mention it as an accessibility feature","Keyboard shortcuts exist but are not listed anywhere in the documentation","Accessibility section is a single paragraph saying 'we are committed to accessibility' with no specifics","Features are documented but buried in a location no user would find (e.g. Deep in API docs)"]},"d3":{"text":"Documentation describes how to activate and use each accessibility feature.","guidance":"Step-by-step instructions for enabling features like screen reader mode, captioning, font resizing, or keyboard navigation must be included. Don't just list features, explain how to use them.","testMethod":"For each accessibility feature identified in the product, check whether the documentation includes: (1) how to find the setting, (2) how to enable it, (3) how to use it, and (4) any limitations. If any feature lacks activation instructions, this item is partial or fail.","commonFailures":["Documentation says 'supports screen readers' but doesn't explain how to navigate with one","Keyboard shortcuts listed but no explanation of when they apply (e.g. Only in editing mode)","Accessibility settings exist in the product but the path to find them is not documented"]},"d4":{"text":"Accessibility features are documented with the same level of detail as other features.","guidance":"Accessibility must not be an afterthought. If your product manual explains how to change language in 3 paragraphs, the screen reader section should be equally detailed.","testMethod":"Compare the word count and depth of accessibility documentation against a similar non-accessibility feature in the same manual. If accessibility documentation is significantly shorter or less detailed, this fails.","commonFailures":["Three-page guide for customising the dashboard, one sentence for accessibility","Accessibility section uses vague language ('may work with some screen readers') while other features are specific","Screenshots included for every feature except accessibility settings"]},"d5":{"text":"Documentation is available in the same languages as the product or service.","guidance":"If the product supports French, German, and English, the accessibility documentation must also be available in those languages.","testMethod":"List all languages the product UI is available in. Check whether the accessibility documentation (not just the main docs) is translated into each of those languages. Machine-translated content with obvious errors counts as partial.","commonFailures":["Product available in 12 languages but accessibility docs only in English","Main documentation translated but the accessibility section left in English","Accessibility page exists in other languages but contains only the English text with a Google Translate banner"]},"d6":{"text":"If video tutorials exist, they have captions and audio descriptions.","guidance":"Onboarding videos, how-to guides, and product walkthroughs must have synchronised captions and, where the visual content is essential, an audio description track.","testMethod":"Play each tutorial video. Enable captions (CC button). Verify: (1) captions exist, (2) they are synchronised with speech, (3) they include speaker identification when multiple speakers, (4) they include relevant non-speech sounds. For videos with visual-only content (e.g. Showing where to click), check if audio description is available.","commonFailures":["YouTube auto-captions used without human review, containing errors in technical terms","Tutorial shows on-screen actions ('click here, then here') with no audio description of what's being clicked","Captions exist for English videos but not for translated versions","Captions miss non-speech information like '[error sound plays]' or '[loading animation]'"]},"s1":{"text":"Help desk / support staff can provide information about the accessibility features of the product.","guidance":"Support staff must be able to answer questions like 'Does this product work with a screen reader?' or 'How do I enable keyboard navigation?' This requires training.","testMethod":"Contact your own help desk and ask: 'What accessibility features does this product have?' and 'Does it work with a screen reader?' Evaluate the response. If the agent cannot answer or redirects to a generic FAQ, this fails. If they can describe specific features and how to use them, it passes.","commonFailures":["Support agent says 'I don't know' or 'We don't support accessibility'","Agent redirects to a generic accessibility page that doesn't answer the specific question","Support scripts don't include any accessibility-related responses","Agent confuses accessibility features with general display settings"]},"s2":{"text":"Help desk provides information in accessible formats on request.","guidance":"If a user asks for help documentation in an accessible format (plain text, HTML, large print), the support team must be able to provide it.","testMethod":"Contact support and request: 'Can you send me the setup instructions in plain text or HTML format? I use a screen reader and cannot read the PDF.' If support can provide an alternative format within a reasonable time, it passes. If they say they can only provide the standard PDF, it fails.","commonFailures":["Support says 'We only have the PDF version, sorry'","Agent offers to read the document aloud over the phone but cannot provide a text version","Large print version requested but only standard font available"]},"s3":{"text":"Support is available through at least two communication channels (e.g. Phone + email, chat + email).","guidance":"Users who cannot use the phone (deaf users) or cannot use chat (users with motor impairments) need alternatives. Provide at least two different modalities.","testMethod":"Visit the contact/support page. Count the distinct communication channels offered (phone, email, live chat, contact form, social media DM, video call). If only one channel exists, this fails. Two or more distinct modalities = pass.","commonFailures":["Only a phone number is provided, excludes deaf and hard-of-hearing users","Only a live chat widget, excludes users with motor impairments who cannot type quickly","Contact form exists but never receives a response (effectively one channel)","Email support listed but auto-reply says 'Please call us for faster service'"]},"s4":{"text":"A mechanism exists for users to report accessibility issues specifically.","guidance":"A dedicated email, contact form, or feedback channel for accessibility complaints is required under the EAA. This must be easy to find, not buried 5 clicks deep.","testMethod":"Navigate to the website footer, accessibility statement, or contact page. Look for a dedicated accessibility feedback mechanism (email, form, or link). It should be reachable within 2 clicks from the homepage. If it exists and is easy to find, it passes. If there's only a generic contact form with no accessibility option, it's partial.","commonFailures":["No accessibility-specific contact channel exists anywhere on the site","Accessibility email address exists but is not published on the website","Contact form has no category option for 'accessibility' or 'disability'","Accessibility feedback link is only in the accessibility statement, which itself is hard to find"]},"s5":{"text":"A documented process exists for responding to accessibility complaints within a reasonable timeframe.","guidance":"Define an SLA for accessibility complaints, e.g. Acknowledgement within 2 business days, resolution within 30 days. Document this process internally.","testMethod":"Ask to see the internal process document for handling accessibility complaints. Verify it includes: (1) who receives complaints, (2) acknowledgement timeframe, (3) investigation steps, (4) resolution timeline, (5) escalation path. If no documented process exists, this fails.","commonFailures":["No written process exists, complaints are handled ad hoc","Process document exists but has no defined response timeframes","Complaints go to a generic inbox with no triage for accessibility issues","Process exists on paper but staff are unaware of it"]},"s6":{"text":"Support staff have basic disability awareness training.","guidance":"Staff should understand common assistive technologies, disability etiquette, and how to communicate with users who have different needs. Annual training is recommended.","testMethod":"Check training records for support staff. Verify that training covers: (1) what assistive technologies are (screen readers, switch access, magnifiers), (2) common accessibility barriers, (3) how to communicate with users who have disabilities, (4) how to escalate accessibility issues. If no training has been provided, this fails.","commonFailures":["No accessibility training has ever been provided to support staff","Training was provided once 3 years ago with no refresh","Training covered 'diversity' generally but not disability-specific topics like assistive technology","Only senior staff received training, front-line agents were excluded"]},"r1":{"text":"If relay services are available, they are referenced in product documentation.","guidance":"If your country or service provides text relay or video relay for deaf users, this should be documented so users know it is available.","testMethod":"Search product documentation and accessibility statement for references to relay services (text relay, video relay, NGT, Relay UK, or equivalent national service). If the product involves phone communication and no relay information is provided, this is a gap.","commonFailures":["Product requires phone calls for critical actions but doesn't mention relay services","Relay service exists in the country but the product doesn't reference it"]},"r2":{"text":"Support channels are compatible with third-party relay services.","guidance":"If a deaf user contacts your help desk via a text relay service, your phone system and agents must be able to handle relay calls without hanging up or refusing them.","testMethod":"If possible, test a relay call to your support line. Alternatively, ask support management: 'If a customer calls via a text relay service, can our system handle it? Have agents been trained to recognise relay calls?' If the answer is no or unknown, this fails.","commonFailures":["IVR system hangs up on relay calls due to silence detection","Agents hang up on relay calls thinking they are spam or robocalls","Phone system requires DTMF input that relay services cannot provide","Support staff have never heard of relay services and don't know how they work"]}}},"terminal-checklist":{"meta":{"title":"Self-Service Terminal Checklist, EN 301 549 Chapter 8","description":"EN 301 549 Chapter 8 + EAA Annex I Section II compliance checklist, verify that your self-service terminals (ATMs, kiosks, ticketing machines) meet European Accessibility Act requirements."},"header":{"title":"Self-Service Terminal Checklist","subtitle":"EN 301 549 Chapter 8 + EAA Annex I Section II","description":"EN 301 549 Chapter 8 + EAA Annex I Section II compliance checklist, verify that your self-service terminals (ATMs, kiosks, ticketing machines) meet European Accessibility Act requirements."},"features":{"f1":"EN 301 549 Chapter 8 + EAA Annex I Section II full coverage","f2":"19 checkpoints across reach, keypad, display & physical interaction","f3":"Pass / Partial / Fail / N/A with notes per item","f4":"How-to-test guidance and common failures for every checkpoint","f5":"Links to relevant testing tools on AccessibilityRef","f6":"Progress auto-saved in your browser","f7":"Export Word report with notes","f8":"Direct links to EAA Directive and EN 301 549"},"categories":{"reach":{"label":"Physical Reach & Clearance","description":"EN 301 549 §8.3, Physical dimensions for wheelchair users and users with limited reach."},"keypad":{"label":"Keypad & Controls","description":"EN 301 549 §8.4, Numeric keypads and physical controls must be tactilely discernible."},"display":{"label":"Display & Audio Output","description":"Screen content, audio output, and privacy requirements for terminal displays."},"physical":{"label":"Physical Interaction","description":"Card slots, receipt mechanisms, and physical touchpoints."}},"items":{"re1":{"text":"Unobstructed forward reach: operable parts within 1220mm from floor, at least 380mm clear space.","guidance":"A wheelchair user approaching from the front must be able to reach all controls. Measure from floor to highest operable control.","testMethod":"Position yourself or a test subject in a wheelchair directly in front of the terminal. Using a tape measure, verify that the highest operable control is no more than 1220mm from the floor and that there is at least 380mm of clear floor space in front. Attempt to reach and operate every control from the seated position.","commonFailures":["Card reader or receipt slot mounted above 1220mm, out of wheelchair reach","Touchscreen positioned at standing height with no tilt adjustment","Floor mat or raised platform reduces effective clear space below 380mm","Promotional signage or attached peripherals block forward approach"]},"re2":{"text":"Unobstructed side reach: operable parts within 1220mm from floor.","guidance":"For side approach, the same 1220mm maximum height applies. Ensure controls are not recessed beyond reach.","testMethod":"Approach the terminal from the side in a wheelchair. Measure the height of the highest operable control, it must be within 1220mm. Attempt to reach all controls from a side approach without leaning forward more than a natural extension allows.","commonFailures":["Controls mounted on a recessed panel that extends beyond comfortable side reach","Terminal installed in an alcove that prevents side approach entirely","Side-mounted card slot placed higher than 1220mm from floor"]},"re3":{"text":"Obstructed forward reach (≤510mm deep): top of controls within 1220mm.","guidance":"If there is an obstruction (counter, shelf) up to 510mm deep, the maximum height of operable parts is 1220mm. For obstructions 510–635mm deep (§8.3.2.4), the maximum height drops to 1120mm. Verify with the EN 301 549 reach diagrams.","testMethod":"Measure the depth of any obstruction (counter, shelf, ledge) between the user and the controls. If the obstruction is 510mm or less, verify controls are at or below 1220mm height. If the obstruction is between 510mm and 635mm deep, the limit drops to 1120mm (§8.3.2.4). Test by reaching over the obstruction from a wheelchair for each scenario.","commonFailures":["Counter ledge is 520mm deep (>510mm) but controls are mounted at 1220mm, must be ≤1120mm for this obstruction depth (§8.3.2.4)","Shelf above the terminal blocks reach even though controls are within height limits","Obstruction depth not measured during installation, leading to non-compliant placement","Obstruction is 600mm deep and controls at 1150mm, exceeds the 1120mm limit for 510–635mm obstructions"]},"re4":{"text":"Width for wheelchair approach: at least 760mm clear width.","guidance":"The approach path to the terminal must be wide enough for a standard wheelchair. Measure the narrowest point.","testMethod":"Measure the width of the approach path at the narrowest point between any walls, barriers, or adjacent terminals. The minimum is 760mm. Physically navigate the path with a standard wheelchair to confirm clearance. Check for temporary obstructions like queue barriers or signage stands.","commonFailures":["Adjacent terminals installed too close together, leaving less than 760mm between them","Queue management barriers narrow the approach path below 760mm","Bollards or anti-ram posts reduce effective approach width","Temporary signage or displays placed in the approach path"]},"re5":{"text":"Knee and toe clearance: at least 230mm depth, 635mm height under the terminal.","guidance":"For forward approach, space must exist under the terminal for wheelchair footrests and knees.","testMethod":"Measure the space under the terminal: there must be at least 230mm of depth and 635mm of height for knee and toe clearance. Position a wheelchair directly in front and verify footrests and knees fit comfortably under the terminal without contact.","commonFailures":["Terminal mounted on a solid pedestal with no clearance underneath","Base plate or cable housing blocks toe space under the terminal","Knee clearance exists but is only 200mm deep, 30mm short of the requirement"]},"re6":{"text":"Installation instructions document accessible placement requirements.","guidance":"The installation guide must specify accessible mounting heights, approach clearances, and floor space requirements.","testMethod":"Review the terminal's installation manual or deployment guide. Search for references to accessible mounting heights, wheelchair approach clearances, knee clearance, and floor space requirements. If the manual contains a dedicated accessibility installation section with specific measurements, it passes.","commonFailures":["Installation manual specifies only standing-user ergonomics with no wheelchair guidance","Accessible placement requirements mentioned but without specific measurements","Installation guide is only available to installers and not to the procuring organisation"]},"kp1":{"text":"Numeric keypad follows standard telephone/ATM layout (1-2-3 top row).","guidance":"The layout must match the standard ITU-T E.161 telephone keypad. Do not use calculator layout (7-8-9 top) for public terminals.","testMethod":"Visually inspect the numeric keypad layout. The top row must be 1-2-3, middle row 4-5-6, bottom row 7-8-9 with 0 below. Compare against the ITU-T E.161 telephone layout diagram. If the terminal uses a calculator-style layout (7-8-9 on top), it fails.","commonFailures":["Terminal uses calculator-style layout (7-8-9 top row) instead of telephone layout","Touchscreen numeric keypad renders in a non-standard arrangement","Keys are positioned correctly but labelled incorrectly"]},"kp2":{"text":"Key 5 has a tactile marker (raised dot or bar) for orientation.","guidance":"The centre key on a numeric keypad must have a tactile identifier so blind users can orient themselves on the keypad.","testMethod":"Run your finger over the number 5 key on the keypad. There must be a tactile nib, raised dot, or bar that is distinguishable by touch alone. Close your eyes and attempt to locate the 5 key and then orient to adjacent keys. If the marker is worn smooth or absent, it fails.","commonFailures":["Key 5 has no tactile marker at all, all keys feel identical","Tactile marker was present at manufacture but has worn smooth from use","Touchscreen keypad has no physical tactile feedback mechanism","Tactile marker exists but is too subtle to detect reliably by touch"]},"kp3":{"text":"Status of toggle keys is determinable both tactilely and visually.","guidance":"If the terminal has toggle keys (Caps Lock, function modes), their state must be perceivable by touch and by sight.","testMethod":"Identify any toggle keys on the terminal (Caps Lock, function mode switches, language toggles). Activate each toggle and check: (1) is there a visual indicator of the current state (LED, on-screen indicator), and (2) is there a tactile or auditory indicator (raised position, click, beep)? Both modalities must be present.","commonFailures":["Toggle key has a visual LED but no tactile or auditory state indicator","Language toggle changes on screen but the physical key gives no feedback","Toggle state is only shown on screen, blind users cannot determine it"]},"kp4":{"text":"If biometric authentication is used, a non-biometric fallback exists.","guidance":"Fingerprint readers on terminals must have PIN or card-based alternatives. Not all users can provide biometric input.","testMethod":"Check whether the terminal uses any biometric authentication (fingerprint, facial recognition, iris scan). If it does, verify that an alternative non-biometric method is available (PIN entry, card swipe, NFC). Attempt to complete the full transaction using only the non-biometric method to confirm it works end-to-end.","commonFailures":["Fingerprint scanner is the only authentication method with no PIN fallback","Facial recognition required for age verification with no manual alternative","Non-biometric fallback exists but requires staff assistance, making it not independent","PIN fallback is available but hidden behind a menu that is not announced by audio output"]},"di1":{"text":"Display screen is positioned for both seated (wheelchair) and standing users.","guidance":"The screen must be readable from wheelchair height (~1100mm eye level) and standing height. Consider tilt-adjustable screens.","testMethod":"View the screen from a seated wheelchair position (approximately 1100mm eye level) and from a standing position. Check for glare, viewing angle degradation, and readability from both positions. If the screen is tilt-adjustable, verify the adjustment mechanism is operable from a wheelchair.","commonFailures":["Screen tilted upward for standing users, causing glare and poor readability from wheelchair height","Screen mounted too high for seated users to read comfortably","Tilt adjustment mechanism requires tools or staff assistance","Privacy screen filter reduces viewing angles so severely that wheelchair users cannot read the display"]},"di2":{"text":"Screen text meets 4.5:1 contrast ratio against the background.","guidance":"In-terminal displays must meet the same contrast requirements as web content. Ambient lighting can reduce effective contrast, test in situ.","testMethod":"Use a contrast analyser or colour picker tool to measure the contrast ratio between foreground text and background colours on the terminal display. Test in the actual installation environment, as ambient lighting (direct sunlight, overhead fluorescents) can reduce effective contrast. All body text must achieve at least 4.5:1; large text (18pt+) must achieve at least 3:1.","commonFailures":["Light grey text on white background falls below 4.5:1 in indoor lighting","Outdoor terminal screen washes out in direct sunlight, dropping effective contrast below the threshold","Brand colours used for buttons have insufficient contrast against the button background","Error messages displayed in low-contrast orange or yellow text"]},"di3":{"text":"Audio output is available via headphone jack or wireless connection.","guidance":"Blind users need audio output to operate the terminal. A standard 3.5mm headphone jack in a tactilely locatable position is the minimum.","testMethod":"Locate the headphone jack on the terminal by touch alone (eyes closed). Plug in standard headphones and verify that audio output is produced for all on-screen content. Check volume controls are present and adjustable. If wireless audio is offered (Bluetooth), verify pairing is straightforward and does not require visual interaction.","commonFailures":["No headphone jack present on the terminal","Headphone jack exists but is recessed so deeply that standard plugs do not fully insert","Audio output does not cover all screens, some menus or error messages are silent","Headphone jack is not tactilely locatable, no raised surround or Braille label"]},"di4":{"text":"All on-screen text and status information is available as speech output.","guidance":"Every menu, instruction, error, and confirmation must be spoken aloud through the audio channel. No visual-only information.","testMethod":"Plug in headphones and navigate through the entire terminal workflow (start to finish). At each step, compare what is displayed on screen with what is spoken through the audio. Every piece of text, status update, error message, and confirmation must be spoken. If any screen has visual content that is not announced, it fails.","commonFailures":["Error messages appear on screen but are not spoken through the audio channel","Transaction confirmation amount is displayed but not announced audibly","Loading/processing status shown visually but no audio equivalent provided","Language selection screen has no audio output, trapping non-sighted users at the first step"]},"di5":{"text":"All instructions are available in both visual and audio form.","guidance":"Usage instructions, how to insert a card, select options, confirm transactions, must be available visually on screen and as audio.","testMethod":"Walk through the terminal's full workflow with headphones plugged in. At each step, verify the instruction is presented both on screen (visual) and through audio. Pay particular attention to the first interaction (e.g. 'Insert your card') and any error recovery steps. If any instruction is visual-only or audio-only, this is partial or fail.","commonFailures":["'Insert card' instruction only shown on screen with an arrow graphic, no audio equivalent","Audio instructions exist but are incomplete, covering only the first three steps","'Please wait' screen has no audio notification, leaving blind users uncertain","Instructions are in audio but only in one language while the visual supports multiple languages"]},"ph1":{"text":"Card insertion slot is tactilely locatable.","guidance":"Blind users must be able to find the card slot by touch. A raised border, tactile arrow, or standardised position is required.","testMethod":"Close your eyes and attempt to locate the card insertion slot by touch alone. Check for raised edges, a tactile arrow indicating insertion direction, or Braille labelling near the slot. Time how long it takes, if it takes more than 10 seconds of searching, the tactile indicators are insufficient.","commonFailures":["Card slot is flush with the terminal surface and has no tactile border","Contactless tap area has no tactile indicator showing where to hold the card","Multiple slots exist (card, receipt, cash) with no tactile differentiation between them","Tactile arrow showing insertion direction is missing or worn away"]},"ph2":{"text":"Receipt or printout has an accessible alternative (e.g. Email, SMS).","guidance":"Paper receipts are inaccessible to blind users. Offer digital alternatives, email confirmation, SMS, or mobile app notification.","testMethod":"Complete a transaction and check whether the terminal offers a digital receipt option (email, SMS, app notification) in addition to or instead of a paper receipt. Verify the digital alternative is offered before or at the point of transaction completion and is itself accessible (e.g. HTML email, not an image-only PDF).","commonFailures":["Only a paper receipt is offered with no digital alternative","Email receipt option exists but requires typing an email address on an inaccessible touchscreen keyboard","Digital receipt is sent as an image-only PDF that screen readers cannot parse","SMS receipt option is available but not announced through the audio channel"]},"ph3":{"text":"Physical controls do not require tight grasping, pinching, or wrist twisting.","guidance":"Buttons must be operable with a closed fist. Coin slots and card readers must not require fine motor dexterity.","testMethod":"Attempt to operate every physical control on the terminal using a closed fist or a single finger without pinching or twisting. Card insertion, button presses, coin/note insertion, and receipt retrieval must all be possible without fine motor dexterity. If any control requires a pinch grip or wrist twist, it fails.","commonFailures":["Coin slot requires precise pinch-and-insert motion that users with tremors cannot perform","Receipt must be pulled from a narrow slit requiring a pinch grip","Card slot is too tight, requiring precise alignment and force to insert","Rotating knob or twist mechanism used for menu navigation"]},"ph4":{"text":"The terminal provides clear feedback on each user action (visual + audio).","guidance":"Every button press, selection, and transaction step must be confirmed through both visual and audio feedback.","testMethod":"Perform each possible user action on the terminal (button press, menu selection, card insertion, transaction confirmation) and verify that both visual feedback (screen update, LED, animation) and audio feedback (beep, spoken confirmation, click sound) are produced. If any action produces only visual or only audio feedback, it is partial.","commonFailures":["Button presses produce a visual highlight but no audio click or confirmation","Card insertion triggers an on-screen animation but no audio acknowledgement","Transaction completion beeps but the audio does not confirm the amount or status","Error state shown with a red screen but no audio alert or spoken error message"]}}},"touch-target-tester":{"meta":{"title":"Touch Target Size Tester, WCAG 2.2 SC 2.5.8","description":"Verify interactive elements against WCAG 2.2 SC 2.5.8 (24px minimum) and best-practice 44px targets. Visual demo, component reference, and CSS fix generator."},"header":{"title":"Touch Target Size Tester","description":"Verify interactive elements against WCAG 2.2 SC 2.5.8 (24px minimum) and best-practice 44px targets."},"context":{"heading":"WCAG 2.2 SC 2.5.8, Target Size (Minimum)","wcag22AA":{"title":"24 × 24px, WCAG 2.2 Level AA","body":"The legal minimum under the EAA, EN 301 549 clause 9.2.5.8, and WCAG 2.2 AA. Every interactive element must meet this unless the spacing exception applies."},"appleHIG":{"title":"44 × 44px, Apple HIG & WCAG 2.5.5 AAA","body":"Apple and Google both recommend 44–48px for comfortable one-handed mobile use. This was the WCAG 2.1 AAA requirement and remains best practice for all touch surfaces."},"spacingException":{"title":"Spacing Exception (SC 2.5.8)","body":"If a target is smaller than 24px, it still passes if there is sufficient space between it and adjacent targets, specifically, the offset must make the total target + offset ≥ 24px on each side."}},"tabs":{"demo":"Visual Demo","reference":"Component Reference","css":"CSS Fix Generator"},"demo":{"targetSizeLabel":"Target Size:","wcagAA":"WCAG AA","recommended":"Rec.","livePreviewHeading":"Live Component Preview, {size}px target","excellent":"Excellent","aaPass":"AA Pass","fail":"Fail","dashedOutlineNote":"Dashed outline shows required 24px minimum. Red elements are failing SC 2.5.8.","spacingHeading":"SC 2.5.8 Spacing Exception Calculator","spacingDescription":"If targets are smaller than 24px, adequate spacing between them may satisfy SC 2.5.8.","targetVisualSize":"Target visual size: {size}px","usingSize":"Using the size set above.","gapLabel":"Gap between adjacent targets","gapAriaLabel":"Gap between targets in pixels","alreadyMeets":"Target already meets 24px, spacing exception not needed.","spacingApplies":"Spacing exception applies","spacingAppliesDetail":"With {spacing}px gap, the target offset ({size}px + {spacing}px = {total}px) meets the 24px threshold. Document this decision in your accessibility statement.","spacingDoesNotApply":"Spacing exception does NOT apply","spacingDoesNotApplyDetail":"Need at least {needed}px gap between targets (you have {spacing}px). Increase spacing or increase target size to 24px."},"compliance":{"excellent":"Excellent (48px+)","recommended":"Recommended (44px+)","wcag22Pass":"WCAG 2.2 AA Pass (24px+)","fail":"Fail, below 24px","shortOf24":"{diff}px short of the 24px WCAG 2.2 AA minimum.","passes24":"Passes WCAG 2.2 AA. Add {diff}px to reach the 44px recommendation.","meetsApple":"Meets Apple HIG. Add {diff}px for Material Design 48px target.","meetsAll":"Meets all major platform guidelines and WCAG requirements.","spacingMayApply":"Spacing exception may apply, see Spacing Calculator below."},"reference":{"howToRead":"How to read this table","howToReadBody":"WCAG 2.2 column = legal minimum under EAA, EN 301 549, ADA. Recommended column = best practice for touch devices (Apple HIG / Material Design). The \"Note\" column explains common failure patterns for each component type.","componentHeader":"Component","wcag22Header":"WCAG 2.2 AA Minimum","recommendedHeader":"Recommended","notesHeader":"Notes"},"components":{"iconButton":{"name":"Icon button (close, share, menu)","note":"Most commonly undersized. Padding to 44px is the standard fix."},"checkbox":{"name":"Checkbox","note":"The clickable area must be 24×24px minimum, the visual mark can be smaller."},"radioButton":{"name":"Radio button","note":"As with checkboxes, padding the label area extends the hit zone."},"textLink":{"name":"Text link (inline)","note":"SC 2.5.8 applies minimum height: 24px. Inline links in body text may be exempt if spacing requirement is met."},"navTab":{"name":"Navigation tab / pill","note":"Tabs in bottom navigation bars should be 44–48px for comfortable mobile use."},"toggle":{"name":"Toggle / switch","note":"The full track width counts toward target size, not just the thumb."},"select":{"name":"Select / dropdown trigger","note":"The trigger must be at least 24px tall. Full-width selects usually pass automatically."},"submitButton":{"name":"Form submit button","note":"Submit and CTA buttons are rarely undersized, but confirm minimum 24px height on mobile."},"pagination":{"name":"Pagination control","note":"Prev/Next and numbered page buttons are frequently too small on mobile breakpoints."},"carousel":{"name":"Carousel prev/next","note":"Carousel arrows are a common failure on mobile, they are often 20px or smaller."},"accordion":{"name":"Accordion trigger","note":"The full header row (with padding) counts as the target. Headers are usually sufficient."},"tooltip":{"name":"Tooltip trigger","note":"\"i\" info icons are frequently 16px. Must be padded to 24px minimum."}},"demoElements":{"iconBtn":{"label":"Icon Button","desc":"Close/dismiss/toolbar button"},"checkbox":{"label":"Checkbox","desc":"Form checkbox"},"radio":{"label":"Radio","desc":"Form radio input"},"navItem":{"label":"Nav Item","desc":"Navigation link/tab"},"caret":{"label":"Expand Arrow","desc":"Accordion / dropdown trigger"},"infoIcon":{"label":"Info Icon","desc":"Tooltip / help trigger"}},"cssFix":{"configureHeading":"Configure the fix","visualSizeLabel":"Visual element size (actual rendered size)","targetGoalLabel":"Target goal","aa":"AA","rec":"Rec.","matrl":"Matrl.","paddingFor24":"Padding for WCAG 2.2 AA (24px)","paddingForGoal":"Padding for {goal}px target","addPadding":"Add this padding to all four sides of the element.","extendsHitZone":"Extends hit zone to {goal}px without changing visual size.","generatedCSS":"Generated CSS","copy":"Copy","tipsHeading":"Implementation tips","tips":{"padding":{"title":"Padding trick (preferred)","body":"Add equal padding to all four sides. The clickable area grows with the padding. Use negative margin to prevent layout shift. This works on inline elements, buttons, and links."},"minSize":{"title":"Min-width / min-height approach","body":"Set min-width and min-height on the element. Use flexbox or grid to centre the visual content. Cleaner for elements that should stretch horizontally."},"pseudo":{"title":"::before pseudo-element","body":"Position a::before (or::after) pseudo-element with position: absolute and a larger hit zone. Useful when you cannot modify the element's own box model."},"noFake":{"title":"Do not fake it with pointer-events","body":"Never set pointer-events: none on a surrounding element to make it non-interactive, this removes accessibility. Always make the actual interactive element larger."},"realDevices":{"title":"Test on real devices","body":"The 24px/44px rules are about CSS pixels, but user-set font scaling on iOS and Android affects effective touch size. Test with large text modes enabled."},"documentSpacing":{"title":"Document spacing exceptions","body":"If you rely on the SC 2.5.8 spacing exception, document it in your accessibility statement, include which components use it and why increasing size is not feasible."}}},"export":{"docx":{"configurationHeading":"Configuration","standardsVerdictHeading":"Standards Verdict","remediationHeading":"Remediation Guidance","componentCatalogueHeading":"Component Reference Catalogue","componentCatalogueIntro":"Standard component-by-component target size guidance. WCAG 2.2 minimum is the legal AA floor; the recommended column reflects iOS/Android UX conventions for comfortable touch use.","methodHeading":"Method","methodBody":"This tool simulates target size at chosen pixel dimensions and applies the WCAG 2.2 SC 2.5.8 (24 px minimum), WCAG 2.5.5 (44 px AAA / Apple HIG), and Android Material Design (48 px) thresholds. The SC 2.5.8 spacing exception is calculated as ceil((24 - size) / 2) px minimum gap to adjacent targets. Mapped to WCAG 2.2 SC 2.5.5 (Target Size) and 2.5.8 (Target Size Minimum), and EN 301 549 V3.2.1 §11.5.2.5.","rowMeasuredSize":"Measured target size","rowVisualSize":"Visual target size","rowTargetGoal":"Target goal","rowAdjacentDistance":"Adjacent target distance","rowSpacing":"Spacing between targets","rowActiveTab":"Active tab","rowPaddingTo24":"Padding needed to reach 24 px","rowPaddingToGoal":"Padding needed to reach {goal} px goal","rowSpacingExceptionMet":"Spacing exception met","rowSpacingExceptionThreshold":"Spacing exception threshold","paddingEachSide":"{padding} px each side","thresholdAdjacent":"Adjacent targets must be >= {gap} px apart","thresholdNotApplicable":"Not applicable (target meets 24 px minimum)","headerNumber":"#","headerStandard":"Standard","headerThreshold":"Threshold","headerVerdict":"Verdict","headerNotes":"Notes","headerComponent":"Component","headerWcag22Min":"WCAG 2.2 minimum","headerRecommended":"Recommended","standardWcag258":"WCAG 2.2 SC 2.5.8 Target Size (Minimum)","standardWcag255Apple":"WCAG 2.5.5 / Apple HIG (AAA / iOS recommendation)","standardAndroid":"Android Material Design","verdictPass":"PASS","verdictPassSpacing":"PASS (spacing exception)","verdictFail":"FAIL","noteSpacingExceptionApplies":"Spacing exception applies, {spacing} px gap is sufficient at {size} px target size","noteMeetsApple":"Meets Apple HIG and WCAG 2.5.5 AAA","noteShortOf44":"{diff} px short of 44 px","noteMeetsAndroid":"Meets Material Design recommendation","noteShortOf48":"{diff} px short of 48 px","valueYes":"Yes","valueNo":"No"}}},"transport-checklist":{"meta":{"title":"Transport & Booking Accessibility Checklist, EAA Annex I","description":"EAA Annex I Sections II–III compliance checklist, verify that your passenger transport booking services meet European Accessibility Act requirements."},"header":{"title":"Transport & Booking Accessibility Checklist","subtitle":"EAA Annex I Sections II–III Compliance Checklist","description":"EAA Annex I Sections II–III compliance checklist, verify that your passenger transport booking services meet European Accessibility Act requirements."},"features":{"f1":"EAA Annex I Sections II–III full coverage","f2":"19 checkpoints across journey search, booking, assistance & travel information","f3":"Pass / Partial / Fail / N/A with notes per item","f4":"How-to-test guidance and common failures for every checkpoint","f5":"Links to relevant testing tools on AccessibilityRef","f6":"Progress auto-saved in your browser","f7":"Export Word report with notes","f8":"Direct links to EAA Directive articles"},"categories":{"search":{"label":"Journey Search & Planning","description":"EAA Annex I §II–III, Journey planners and timetable information must be accessible."},"booking":{"label":"Booking & Seat Selection","description":"The booking flow including seat maps and passenger details."},"assistance":{"label":"Accessibility Assistance","description":"EAA requires transport operators to provide accessible assistance booking."},"post-booking":{"label":"Post-Booking & Travel","description":"Confirmations, boarding documents, and disruption information."}},"items":{"js1":{"text":"Journey planner / route search is fully keyboard-operable.","guidance":"Origin/destination fields, date pickers, time selectors, and search buttons must all work with keyboard alone.","testMethod":"Navigate to the journey planner using only the keyboard. Tab through the origin field, destination field, date picker, time selector, and search button. Verify that each element receives visible focus, can be activated, and that the date picker allows selecting a date with arrow keys and Enter. Confirm the autocomplete dropdown for station names is navigable with arrow keys and selectable with Enter.","commonFailures":["Date picker opens on click only, keyboard users cannot open or navigate the calendar","Station autocomplete dropdown appears but arrow keys do not move through suggestions","Search button is a styled <div> that does not receive keyboard focus","Time selector is a custom scroll wheel that only responds to mouse drag"]},"js2":{"text":"Timetable data is available in text, not image-only.","guidance":"Schedule tables must use proper HTML tables with headers. PDF timetables must be tagged. No image-based schedules.","testMethod":"Open the timetable page and inspect the HTML. Verify that schedule data uses <table>, <th>, and <td> elements with proper scope attributes. If PDF timetables are offered, open them in Adobe Acrobat and check the Tags panel for table structure. Test with a screen reader to confirm departure times, destinations, and platform numbers are correctly announced with their column headers.","commonFailures":["Timetable rendered as a screenshot image or embedded JPEG with no text alternative","HTML table used but lacks <th> elements, screen readers cannot identify column headers","PDF timetable is a scanned image with no OCR text layer","Timetable data is inside an <iframe> pointing to a third-party widget that lacks accessibility"]},"js3":{"text":"Real-time departure/arrival updates use aria-live regions.","guidance":"Live departure boards that auto-update must announce changes to screen readers, 'Flight BA123 now delayed to 14:30'.","testMethod":"Open the live departures/arrivals page with a screen reader active. Wait for an update to occur (or trigger one by refreshing data). Listen for an automatic announcement of the change. Inspect the DOM for aria-live='polite' or role='status' on the container that updates. Verify that only the changed information is announced, not the entire board.","commonFailures":["Departure board updates visually every 30 seconds but screen readers are never notified","Aria-live set on the entire table, causing the full board to be re-read on every minor update","Status change from 'On time' to 'Delayed' shown only by changing text colour from green to red","Live updates work via WebSocket but the DOM mutation does not trigger aria-live announcements"]},"js4":{"text":"Multi-leg journey information has clear heading structure.","guidance":"Each leg of a journey (flight 1, connection, flight 2) must be clearly separated with headings and presented in sequential order.","testMethod":"Search for a multi-leg journey (e.g. With a connection). In the results, verify that each leg is introduced with a heading element (h2, h3, or h4) or equivalent ARIA landmark. Check that connection information (transfer time, terminal change) is clearly labelled between legs. Navigate with a screen reader using heading shortcuts (H key in NVDA) to confirm each leg can be reached directly.","commonFailures":["All journey legs presented as a continuous block of text with no heading separation","Connection time and terminal change information is only shown as a small visual divider line","Heading hierarchy is broken, legs use <h4> inside a section with no <h2> or <h3>","Return journey legs are mixed in with outbound legs, creating a confusing reading order"]},"js5":{"text":"Price comparison is presented in accessible table format.","guidance":"Fare class comparisons with features (baggage, flexibility) must use properly structured tables, not image-based grids.","testMethod":"Navigate to the fare comparison view. Inspect the HTML for proper <table> markup with <th> headers for fare classes and <td> cells for features. With a screen reader, navigate the table and verify that each cell announces its row and column headers (e.g. 'Economy, Baggage, 1 bag included'). Check that the 'Select' button for each fare class has a unique accessible name.","commonFailures":["Fare comparison built with CSS grid of <div> elements, no table semantics for screen readers","Feature icons (checkmark, cross) used without text alternatives to indicate inclusion/exclusion","All 'Select' buttons have the same accessible name 'Select' with no fare class distinction","Price displayed in a large font as a visual highlight but not programmatically associated with the fare class"]},"bk1":{"text":"Seat selection interface is keyboard-accessible.","guidance":"Interactive seat maps must support keyboard navigation, arrow keys to move, Enter to select. Provide a list-based alternative if the map is complex.","testMethod":"Open the seat selection page and attempt to choose a seat using only the keyboard. Verify that arrow keys move between seats, Enter or Space selects a seat, and the selected seat is announced. Check whether a list-based alternative view is available (e.g. 'Select by row and seat number' dropdown). Confirm that focus is visible on the currently highlighted seat.","commonFailures":["Seat map is an interactive SVG that does not receive keyboard focus at all","Arrow keys scroll the page instead of moving between seats in the map","No list-based alternative, keyboard users have no way to select a specific seat","Selected seat is highlighted visually but no announcement is made to screen readers"]},"bk2":{"text":"Seat map has text alternatives for seat status (available, occupied, premium).","guidance":"Each seat cell must have aria-label describing its status, 'Seat 12A, window, available, €45', not just colour coding.","testMethod":"Inspect the seat map HTML. Verify that each seat element has an aria-label or title attribute that includes the seat number, position (window/middle/aisle), status (available/occupied/premium), and price if applicable. Test with a screen reader, navigate to several seats and confirm the full description is announced. Check that occupied seats are not just greyed out but also marked with aria-disabled='true'.","commonFailures":["Seats distinguished only by colour, green for available, grey for occupied, gold for premium","Aria-label on seats says only 'Seat' or '12A' without status or position information","Occupied seats have no aria-disabled attribute, screen reader users can attempt to select them and receive no feedback","Emergency exit row seats have visual warnings (icon) but no text alternative explaining restrictions"]},"bk3":{"text":"Passenger detail forms have clear labels for all fields.","guidance":"Title, name, date of birth, passport number, all must have <label> elements. Group related fields with fieldset/legend.","testMethod":"Open the passenger details form and inspect each field. Verify every input has a visible <label> with a matching 'for' attribute. Check that related fields are grouped, e.g. Passenger 1's details within a <fieldset> with <legend> 'Passenger 1'. Test with a screen reader to confirm each field announces its label and group context. Verify date of birth fields specify the expected format.","commonFailures":["First name and last name fields share a single label 'Name', ambiguous for screen readers","Passenger 2 fields have identical labels to Passenger 1 with no fieldset grouping to distinguish them","Date of birth field does not indicate expected format (DD/MM/YYYY vs MM/DD/YYYY)","Passport number field uses an input mask that fights with screen reader text entry"]},"bk4":{"text":"Booking summary with review step before payment.","guidance":"Show all journey details, passenger info, and total cost for review before processing payment.","testMethod":"Proceed through the booking flow to the review step before payment. Verify the summary includes: journey details (route, dates, times), passenger names, seat selections, baggage, total price with taxes and fees broken down. Confirm an 'Edit' or 'Back' button exists for each section. Test that the 'Pay' button is only available after the review step, not before.","commonFailures":["Payment is processed immediately after entering card details with no review step","Review page shows journey details but omits fee breakdown, total is higher than expected","Edit links exist but return to the beginning of the flow instead of the relevant step","Review page is not keyboard-navigable, users cannot Tab to the edit or confirm buttons"]},"as1":{"text":"Accessibility assistance booking is available online, not phone-only.","guidance":"Wheelchair assistance, meet-and-greet, and special needs requests must be bookable through the website, not just a phone number.","testMethod":"Search the booking flow and account settings for an option to request accessibility assistance (wheelchair, meet-and-greet, hearing loop). Verify the request can be completed entirely online without needing to call a phone number. Test the assistance booking form with a screen reader and keyboard to confirm it is itself accessible. Check that confirmation of the assistance request is provided.","commonFailures":["Assistance page says 'Please call our accessibility helpline on...' with no online booking option","Online form exists but requires selecting from a dropdown of disability types with no 'Other' option","Assistance request is part of the booking flow but appears only on a step that is skipped by default","Confirmation email for the booking does not mention the assistance request, leaving users uncertain"]},"as2":{"text":"Station/stop accessibility information is published online.","guidance":"Which stations have step-free access, lifts, accessible toilets, and assistance points must be published and searchable.","testMethod":"Navigate to the station information pages. For a sample of stations, check whether accessibility details are published: step-free access, lift availability, accessible toilets, tactile paving, hearing loops, staff assistance points. Verify this information is available as text (not just icons) and that a filter or search exists to find accessible stations specifically.","commonFailures":["No accessibility information published for any station, users must call to ask","Accessibility shown only as a wheelchair icon with no detail about what is actually accessible","Information exists but is buried in a PDF station guide rather than on the station web page","Step-free access information is outdated, lists lifts that have been out of service for months"]},"as3":{"text":"Vehicle accessibility information is available (wheelchair spaces, audio announcements).","guidance":"Users should know before booking whether the vehicle has wheelchair spaces, hearing loops, and audio/visual announcements.","testMethod":"During the booking process or on the service information page, check whether vehicle accessibility features are listed for each service (wheelchair spaces and their location, priority seating, hearing loops, audio announcements, visual displays). Verify this information is available before the user commits to a booking, not only after purchase.","commonFailures":["No vehicle accessibility information published anywhere on the website","Information says 'accessible vehicles available' without specifying which services or features","Wheelchair space availability shown only on the physical vehicle, not bookable online","Audio announcement availability varies by vehicle type but the website does not indicate which type serves which route"]},"pb1":{"text":"Booking confirmation is in accessible format (HTML email, not image receipt).","guidance":"Confirmation emails must be HTML with proper structure. Attached PDFs must be tagged. No image-only receipts.","testMethod":"Complete a test booking and examine the confirmation email. Open it with a screen reader and verify all booking details (route, date, time, passenger, seat, price) are readable as text. If a PDF is attached, check it for tags in Adobe Acrobat. Verify the email uses semantic HTML (headings, tables with headers) rather than a single image of the itinerary.","commonFailures":["Confirmation email is a single large image of the itinerary with alt='Booking confirmation'","Email uses HTML tables for layout but no semantic headings, screen readers read a jumbled sequence","Attached PDF ticket is an image-only file with no text layer","Important details (gate, terminal) are in a coloured banner that is actually an image"]},"pb2":{"text":"Mobile boarding pass / e-ticket is screen-reader compatible.","guidance":"QR codes need text alternatives. Boarding details (gate, time, seat) must be available as real text, not embedded in an image.","testMethod":"Open the mobile boarding pass or e-ticket on a phone with VoiceOver (iOS) or TalkBack (Android) active. Swipe through each element and verify that the QR code has an alt text (e.g. 'Boarding pass QR code for flight BA123'). Confirm that gate, boarding time, seat, and passenger name are all real text elements, not part of a background image. Check that the pass is usable in both portrait and landscape orientation.","commonFailures":["Boarding pass is rendered as a single image, screen reader announces only 'image' with no details","QR code has no text alternative, screen reader users cannot confirm they are showing the right pass","Gate and seat information is overlaid on a decorative background image and not in the DOM as text","Pass only works in portrait mode but the screen reader user has their phone in landscape for easier reading"]},"pb3":{"text":"Disruption alerts (delays, cancellations, gate changes) are available in text.","guidance":"Push notifications and in-app alerts must include full text, not just 'Alert' with details in an inaccessible overlay.","testMethod":"Trigger or wait for a disruption notification (delay, cancellation, gate change). Verify the push notification includes the full detail in text (e.g. 'Flight BA123 to Paris delayed to 16:45, new gate B12'). Open the in-app alert and confirm it is announced by the screen reader with all relevant information. Check that the notification is not just a sound or vibration without accompanying text.","commonFailures":["Push notification says only 'Travel update' with no detail, user must open the app to learn more","In-app alert overlay is not announced by screen readers and has no focus management","Gate change shown only on the interactive map with no text notification","Disruption SMS sent but contains a shortened URL instead of the actual information"]},"pb4":{"text":"Rebooking and cancellation processes are accessible.","guidance":"If a journey is disrupted, the rebooking flow must be as accessible as the original booking, not a degraded experience.","testMethod":"Navigate to the manage booking or rebooking page. Using a screen reader and keyboard, attempt to change a journey date or cancel the booking. Verify all form fields are labelled, alternative journey options are presented accessibly, and confirmation is provided. Compare the rebooking experience with the original booking flow, it should be equally accessible.","commonFailures":["Rebooking page is a simplified mobile view that strips out accessibility features present in the main flow","Alternative journey options presented in a modal that traps focus and cannot be closed with Escape","Cancellation requires calling a phone number, no online self-service option","Refund confirmation is sent as an image-only PDF with no text content"]},"pb5":{"text":"Real-time travel information displays provide both visual and audio output.","guidance":"Departure boards, platform indicators, and gate displays must provide information visually on screen and via audio announcements. Information must not be conveyed through a single sensory channel.","testMethod":"At a station or airport (or via the live information web page), observe the real-time information displays. Verify that visual displays are accompanied by audio announcements for departures, arrivals, platform changes, and delays. Check that the web-based live information page provides equivalent text updates accessible to screen readers via aria-live regions.","commonFailures":["Platform change shown only on the visual departure board with no audio announcement","Audio announcements made but too quiet or distorted to be understood in a noisy station","Web-based live board is a video stream of the physical display, no text data for screen readers","Audio announcements cover departures but not delays or cancellations"]},"pb6":{"text":"Audio announcements include destination, stops, delays, and safety information.","guidance":"On-board and at-station audio must announce upcoming stops, final destination, delays, and safety instructions. This serves blind passengers and those who cannot read displays.","testMethod":"Board a vehicle or listen to station announcements. Verify that audio includes: (1) final destination of the service, (2) upcoming stops, (3) delay information with revised times, (4) safety information (emergency exits, procedures). Check that announcements are in the primary language and at least one additional language where applicable. On the website, verify that equivalent information is available as text.","commonFailures":["On-board announcements include only the next stop, no final destination or delay information","Safety announcements made only at the start of the journey and not repeated or available in text","Announcements in one language only on an international route","Automated announcement system frequently malfunctions with no manual backup procedure"]},"pb7":{"text":"Disruption notifications are available in multiple formats (app, SMS, email, display).","guidance":"When services are disrupted, notify passengers through multiple channels, not just a screen at the station. Mobile push notifications, SMS, and email ensure users receive the information regardless of their location or abilities.","testMethod":"Check the notification settings in the booking account. Verify that users can opt in to receive disruption alerts via at least three channels: push notification, SMS, and email. Trigger or wait for a disruption and confirm notifications are sent through all selected channels. Verify that each channel provides the same level of detail (not just 'check the app' in the SMS).","commonFailures":["Disruptions communicated only via the physical departure board at the station","Push notifications available but SMS and email options are not offered","SMS notification says 'Your journey is affected. Open the app for details' instead of including the information","Email notifications sent but delayed by 30+ minutes, arriving after the disruption has passed"]}},"export":{"filename":"Transport-checklist","title":"TRANSPORT & BOOKING ACCESSIBILITY","subtitle":"EAA Annex I Sections II\\u2013III Compliance Checklist"},"links":{"eaaDirective":"EAA Directive 2019/882","eaaAnnex":"EAA Annex I §II–III"}},"transposition-tracker":{"meta":{"title":"EAA Transposition Tracker, National Laws Per Member State","description":"Reference table of how each EU member state transposed the European Accessibility Act (Directive 2019/882), statute number, regulator, complaint URL, and maximum fine."},"header":{"eyebrow":"EAA Reference Data","title":"EU Member-State Transposition Tracker","subtitle":"How each EU member state transposed Directive 2019/882. Statute, regulator, fine, and citation per country."},"table":{"caption":"EAA transposition status across EU member states with national statute, regulator, and maximum fine","country":"Country","status":"Status","statute":"National statute","transpositionDate":"Transposition date","applicationDate":"Application date","regulator":"Regulator","maxFine":"Max fine","complaint":"Complaint","sources":"Sources"},"status":{"transposed":"Transposed","delayed":"Delayed","partial":"Partial","in-progress":"In progress"},"filter":{"label":"Filter by status","all":"All","search":"Search by country or statute","resultCount":"Showing {count} of {total} member states"},"fines":{"turnoverPct":"% of turnover","tiers":{"severe":"Severe violations (product, CE marking, service provision)","less-severe":"Less severe cases (information, documentation, missing statement)","accessibility-obligation":"Breach of accessibility obligation","complementary-obligation":"Breach of complementary obligation (statement, multi-year scheme)","very-serious-legal":"Very serious, legal person","very-serious-natural":"Very serious, natural person","serious-legal":"Serious, legal person","serious-natural":"Serious, natural person","very-serious":"Very serious infringement","serious":"Serious infringement","minor":"Minor infringement","indictable":"Conviction on indictment","summary":"Summary conviction"}},"footer":{"disclaimerTitle":"Reference only","disclaimer":"This tracker reflects publicly available transposition status. It is not legal advice. National statutes change; verify against the linked source before relying on any value here for compliance decisions."}},"user-testing-log":{"meta":{"title":"User Testing with Disabled Participants, Checklist","description":"Document and verify user testing conducted with participants who have disabilities. Enforcement bodies increasingly expect evidence of real-user testing beyond automated and expert assessment."},"header":{"title":"User Testing with Disabled Participants, Checklist","subtitle":"EAA Article 15 Technical Documentation + EN 301 549 Annex C","description":"Document and verify user testing conducted with participants who have disabilities. Enforcement bodies increasingly expect evidence of real-user testing beyond automated and expert assessment. This checklist ensures your testing methodology, participant recruitment, and findings documentation meet regulatory expectations."},"features":{"f1":"EAA Article 15 & EN 301 549 Annex C aligned","f2":"20 checkpoints across recruitment, methodology, documentation & follow-up","f3":"Pass / Partial / Fail / N/A with notes per item","f4":"How-to-test guidance and common failures for every checkpoint","f5":"Links to relevant testing tools on AccessibilityRef","f6":"Progress auto-saved in your browser","f7":"Export Word report with notes","f8":"Direct links to EAA Directive articles and EN 301 549 clauses"},"categories":{"participant-recruitment":{"label":"Participant Recruitment & Representation","description":"Ensure participant panels are representative of disabled end-users and that recruitment practices are ethical and documented."},"testing-methodology":{"label":"Testing Methodology","description":"Verify that the testing approach is structured, reproducible, and appropriate for accessibility evaluation with disabled participants."},"findings-documentation":{"label":"Findings Documentation","description":"Ensure barriers discovered during user testing are documented with sufficient detail for remediation and regulatory evidence."},"follow-up":{"label":"Follow-Up & Remediation Verification","description":"Confirm that user testing findings drive remediation and that fixes are validated through re-testing."}},"items":{"ut1":{"text":"A minimum of 2 participants per disability profile are recruited for each testing round.","guidance":"Single-participant testing per profile does not produce reliable findings. Two participants per profile is the minimum to identify patterns versus individual preferences. Larger panels are preferred for critical services.","testMethod":"Review the participant roster for the most recent testing round. Count the number of participants per disability profile (vision, hearing, motor, cognitive). Verify that each profile has at least two participants listed. Cross-reference with consent forms to confirm actual attendance.","commonFailures":["Only one blind user recruited, providing a single data point that may reflect personal preference rather than a genuine barrier","Cognitive disability profile omitted entirely from the participant panel","Participants listed on roster but did not attend, actual testing conducted with fewer than minimum"]},"ut2":{"text":"Disability profiles include vision, hearing, motor, and cognitive impairments.","guidance":"Testing must cover the four major disability categories. Within each category, consider sub-profiles (e.g. Low vision vs blind, d/Deaf vs hard-of-hearing). The specific profiles selected should reflect likely end-users of the product.","testMethod":"Review the testing plan and participant roster. Confirm that all four major disability categories are represented. Check whether sub-profiles within each category were considered and documented. Verify that the rationale for included profiles is linked to the product's user base.","commonFailures":["Only blind screen reader users recruited, low vision, motor, hearing, and cognitive profiles excluded","Hearing disability profile listed as 'included' but participant uses hearing aids and faces no barriers with the product, does not represent d/Deaf users","Motor impairment profile limited to wheelchair users, ignoring users with limited dexterity who interact with interfaces differently","Cognitive impairment category omitted with no documented justification"]},"ut3":{"text":"Participants use their own assistive technology during testing sessions.","guidance":"Asking participants to use unfamiliar AT introduces confounding variables. Users should bring their own devices and AT (screen readers, switches, magnifiers) configured to their preferences. If remote testing, confirm participants are using their everyday setup.","testMethod":"Review session setup notes or pre-session questionnaires. Confirm that each participant documented the AT they use daily and that the same AT was used during testing. Check session recordings or facilitator notes for evidence that participants were not asked to switch to lab-provided AT.","commonFailures":["Lab-provided laptop with default NVDA settings used instead of participant's own JAWS configuration","Participant asked to test on a device they do not normally use, producing unrepresentative results","Remote session conducted via a platform that conflicts with the participant's screen reader, but no alternative offered"]},"ut4":{"text":"Participants receive fair compensation for their time.","guidance":"Unpaid testing exploits disabled participants and may bias recruitment toward those with fewer options. Compensation should be at least equivalent to market rates for usability testing. Payment must be accessible (e.g. Bank transfer, not only gift cards to inaccessible platforms).","testMethod":"Review the testing budget and participant agreements. Confirm that compensation amounts are documented and consistent with market rates (typically €50–€150 per hour). Verify that payment was made within the stated timeframe and in an accessible format. Check that compensation is not contingent on completing all tasks.","commonFailures":["Participants offered only 'exposure' or a thank-you email instead of monetary compensation","Compensation provided as gift cards to an e-commerce platform that is itself inaccessible","Payment delayed by months, discouraging future participation","Compensation contingent on completing all tasks, penalising participants who encounter barriers"]},"ut5":{"text":"Informed consent is documented for each participant, covering data use, recording, and anonymisation.","guidance":"Consent forms must be accessible (not image-only PDFs). They must explain what data is collected, how sessions are recorded, how findings are anonymised, and how participants can withdraw. Provide consent forms in advance so participants can review with their AT.","testMethod":"Request copies of the consent forms used. Verify they are in an accessible format (tagged PDF, HTML, or plain text). Check that the form covers: purpose of testing, data collected, recording consent, anonymisation approach, right to withdraw, and data retention period. Confirm signed/agreed forms exist for every participant in the roster.","commonFailures":["Consent form is a scanned image PDF that screen reader users cannot read","Form does not mention video recording, but sessions were recorded","No consent form exists, verbal agreement only, with no documentation"]},"ut6":{"text":"Defined task scenarios cover all critical user journeys.","guidance":"Task scenarios should cover the end-to-end journeys that matter most: registration, login, core functionality, payments, support. Tasks must be written in plain language and be achievable within session time. Avoid leading participants toward specific UI elements.","testMethod":"Review the task scenario document. Map each task to a critical user journey in the product. Verify that all journeys identified in the product's accessibility scope are covered by at least one task. Check that tasks are written as realistic goals (e.g. 'Find and purchase a blue shirt in size M') rather than step-by-step instructions.","commonFailures":["Tasks cover only the homepage and 'About' page, checkout, account management, and support journeys omitted","Task scenarios written as step-by-step instructions ('Click the menu, then click Products'), removing the opportunity to observe natural navigation","Critical journeys like password reset or error recovery not included in the task set","Tasks written with jargon or internal terminology that participants do not understand"]},"ut7":{"text":"Tasks match the scope of the accessibility assessment (same pages, components, and flows).","guidance":"User testing should validate the same scope as the conformance assessment. If the WCAG audit covers 20 pages, user testing tasks should exercise those same pages. Misaligned scope means testing results cannot be correlated with audit findings.","testMethod":"Compare the list of pages and components in the accessibility assessment scope with the user testing task scenarios. Confirm that each assessed page or component is exercised by at least one task. Document any scope gaps and verify whether they were intentionally excluded with justification.","commonFailures":["WCAG audit covers the checkout flow, but no user testing task involves completing a purchase","Assessment scope includes mobile responsive views, but testing conducted only on desktop","New features added after the audit scope was defined are not included in user testing tasks"]},"ut8":{"text":"Think-aloud protocol or structured observation method is documented and followed.","guidance":"The facilitation method must be defined before testing begins. Think-aloud protocol asks participants to verbalise their thoughts while performing tasks. Alternatively, retrospective interviews or structured observation with a predefined rubric are acceptable. The method must be consistent across all sessions.","testMethod":"Review the test plan for the stated facilitation method. Check session recordings or facilitator notes to confirm the method was consistently applied. Verify that the facilitator prompted think-aloud verbalisation (or applied the chosen method) without leading the participant. Check that the same method was used for all participants to enable comparison.","commonFailures":["No facilitation method documented, each session conducted differently depending on the facilitator's preference","Think-aloud protocol stated but facilitator intervened and guided the participant through barriers instead of observing","Method changed mid-study from think-aloud to retrospective interview without documenting the rationale"]},"ut9":{"text":"Sessions are recorded (with participant consent) for evidence and later analysis.","guidance":"Recordings provide evidence for enforcement bodies and allow the team to review findings in detail. Both screen and audio should be captured. If participants decline recording, detailed contemporaneous notes must substitute. Recordings must be stored securely with restricted access.","testMethod":"Verify that session recordings exist for each participant (or that detailed notes exist where recording was declined). Check that recordings capture both the screen interaction and participant audio. Confirm that recordings are stored securely with access limited to the testing team. Verify recording consent is documented in participant consent forms.","commonFailures":["No recordings made, findings rely entirely on facilitator memory","Screen recorded but audio not captured, losing all think-aloud commentary","Recordings stored on an unsecured shared drive accessible to the entire organisation","Participant declined recording but no contemporaneous notes were taken as substitute"]},"ut10":{"text":"Testing is helped by an independent person, not the product developer or designer.","guidance":"Developers and designers have inherent bias and knowledge of the product that can lead them to unconsciously guide participants. The facilitator should be someone who did not build the feature being tested. External accessibility consultants or trained UX researchers are preferred.","testMethod":"Review the test plan and session records to identify the facilitator. Confirm that the facilitator is not listed as a developer, designer, or product owner for the features being tested. Check facilitator credentials or training in accessibility testing facilitation. If an internal team member helped, verify they were not involved in building the tested features.","commonFailures":["Lead developer helped sessions and unconsciously guided participants past known issues","Designer helped and became defensive when participants struggled, biasing the session","No facilitator documented, unclear who conducted the sessions"]},"ut11":{"text":"Each barrier documented with: disability profile, AT used, task attempted, barrier description, and severity.","guidance":"A finding without context is not actionable. Each documented barrier must state which participant profile encountered it, what AT was in use, which task was being attempted, a clear description of the barrier, and a severity rating (critical / major / minor). This structure enables prioritised remediation.","testMethod":"Review the findings report. For each documented barrier, check that all five required fields are populated: (1) disability profile, (2) assistive technology, (3) task scenario, (4) barrier description, (5) severity rating. Verify severity ratings use a consistent scale that is defined in the report methodology section.","commonFailures":["Barriers listed as one-line notes ('button didn't work') without disability profile, AT, or task context","Severity ratings inconsistent, some findings rated 'high/medium/low', others 'critical/major/minor' with no defined scale","AT used not recorded, making it impossible to reproduce the barrier","Task context omitted, so developers cannot trace the barrier to a specific user journey"]},"ut12":{"text":"Each finding is linked to the relevant WCAG success criterion.","guidance":"Linking user testing findings to WCAG success criteria connects real-user evidence to normative requirements. This strengthens conformance claims and helps developers understand which requirement is affected. If a barrier does not map to a specific SC, document it as a usability issue outside WCAG scope.","testMethod":"Review each finding in the report. Verify that a WCAG success criterion reference (e.g. '1.3.1 Info and Relationships') is included. Check that the mapping is accurate, the cited SC should genuinely relate to the barrier described. Identify any findings without WCAG mapping and confirm they are explicitly flagged as usability issues.","commonFailures":["No WCAG references included in any findings, report reads as a usability study with no normative grounding","Incorrect WCAG mapping, a colour contrast issue linked to SC 2.4.7 (Focus Visible) instead of SC 1.4.3 (Contrast Minimum)","All findings mapped to SC 4.1.2 (Name, Role, Value) as a catch-all, even when more specific criteria apply"]},"ut13":{"text":"Participant quotes are included in findings (anonymised).","guidance":"Direct quotes from participants provide powerful qualitative evidence. They illustrate the human impact of barriers and are compelling in regulatory submissions and stakeholder presentations. All quotes must be anonymised (e.g. 'Participant B3, blind, JAWS user').","testMethod":"Review the findings report for participant quotes. Verify that quotes are attributed to anonymised identifiers (not real names). Check that quotes are drawn from session recordings or contemporaneous notes. Confirm that at least the critical and major findings include supporting participant commentary.","commonFailures":["No quotes included, findings are purely technical descriptions with no human perspective","Quotes attributed to participants by real name, violating anonymisation commitments","Quotes fabricated or paraphrased without indication, not actual participant words"]},"ut14":{"text":"Success rate per task per disability profile is recorded.","guidance":"Quantitative success rates complement qualitative findings. For each task, record how many participants in each disability profile completed it successfully, partially, or not at all. This data reveals which journeys are most problematic and for which user groups.","testMethod":"Review the findings report for a task completion matrix or equivalent data. Verify it shows success/partial/fail rates broken down by disability profile for each task. Check that the denominator matches the actual number of participants who attempted each task. Confirm that 'partial success' is defined (e.g. Completed with workaround or excessive time).","commonFailures":["No quantitative data recorded, report contains only narrative descriptions","Success rates reported as aggregate across all profiles, masking that blind users failed 80% of tasks while other profiles succeeded","Partial success not defined, unclear whether a participant who took 10 minutes for a 2-minute task 'succeeded'","'N/A' used extensively without explanation, reducing the effective sample size"]},"ut15":{"text":"Re-testing is planned after remediation of identified barriers.","guidance":"User testing without follow-up re-testing is incomplete. A re-testing round should be scheduled after developers address the critical and major findings. The re-test plan should specify timelines, scope (which fixes to validate), and participant requirements.","testMethod":"Review the testing report or project plan for a documented re-testing schedule. Verify it specifies: target date, scope of re-testing (which barriers will be re-validated), and participant requirements. Check that the re-test timeline allows sufficient development time for remediation but is not indefinitely deferred.","commonFailures":["No re-testing planned, findings documented but never validated after fixes","Re-test scheduled but repeatedly postponed with no firm deadline","Re-test scope limited to 'spot checks' rather than systematically validating each reported barrier"]},"ut16":{"text":"The same participants (or same disability profiles) are invited for re-testing.","guidance":"Re-testing should involve participants with the same disability profiles as the original round to ensure fixes are validated by the affected user groups. Ideally, the same individuals participate to provide continuity. If original participants are unavailable, recruit replacements with matching profiles.","testMethod":"Compare the re-test participant roster with the original roster. Verify that all disability profiles from the original round are represented. Check whether original participants were invited first and, if unavailable, that replacements with matching profiles and AT configurations were recruited.","commonFailures":["Re-test conducted with sighted users only, no disabled participants involved","Original blind participants unavailable and no replacement blind users recruited","Re-test participant panel significantly smaller than original, reducing coverage"]},"ut17":{"text":"Findings are shared with the development team within 5 working days of testing completion.","guidance":"Delayed reporting reduces the likelihood of remediation. Critical barriers should be communicated immediately; the full report should follow within 5 working days. Use accessible formats and include enough technical detail for developers to reproduce and fix each barrier.","testMethod":"Check the date of the last testing session and the date the findings report was delivered to the development team. Verify the gap is 5 working days or fewer. Confirm that critical barriers were flagged immediately (e.g. Via email or ticket) rather than held for the full report. Check that the report was delivered in an accessible format.","commonFailures":["Report delivered 6 weeks after testing, developers had already moved to other features","Findings shared verbally in a meeting but no written report provided for reference","Report delivered as an inaccessible PDF that the development team's blind QA engineer could not read","Critical barriers not flagged separately, buried in a 40-page report with no priority ordering"]},"ut18":{"text":"User testing findings are integrated into the self-assessment or conformance evaluation results.","guidance":"User testing should feed into the formal accessibility assessment. WCAG conformance claims should be informed by real-user evidence, not just automated and expert testing alone. Where user testing reveals barriers that expert testing missed, the assessment must be updated.","testMethod":"Review the accessibility conformance report or self-assessment. Check whether it references user testing findings. Verify that any WCAG SC marked as 'Supports' or 'Partially Supports' has been cross-checked against user testing results. Confirm that barriers found in user testing that affect conformance claims have been reflected in the assessment.","commonFailures":["Conformance report states 'Supports' for SC 2.1.1 Keyboard, but user testing showed keyboard traps, assessment not updated","User testing report and conformance report maintained as separate documents with no cross-referencing","Self-assessment completed before user testing, and never revised afterward"]},"ut19":{"text":"User testing is repeated annually or after any major product release.","guidance":"A single round of user testing does not provide ongoing assurance. Testing should be conducted at least annually and triggered by major releases that affect accessibility-relevant functionality. Document the testing cadence in the accessibility policy.","testMethod":"Review the organisation's accessibility policy or testing schedule for a stated testing cadence. Check the dates of past user testing rounds to verify the cadence is being followed. Confirm that major releases since the last testing round were evaluated for accessibility impact and triggered re-testing where appropriate.","commonFailures":["User testing conducted once in 2024 and never repeated despite three major releases since","Annual testing scheduled but skipped due to budget constraints with no compensating measures","Major redesign launched without user testing because it was 'only visual changes'","Testing cadence not documented, conducted ad hoc when stakeholders remember to request it"]},"ut20":{"text":"Testing report is available for market surveillance authorities upon request.","guidance":"Enforcement bodies may request evidence of user testing as part of market surveillance. The report must be stored securely, be retrievable within a reasonable timeframe, and contain sufficient detail to demonstrate compliance with EAA Article 15 technical documentation requirements.","testMethod":"Confirm that the user testing report is stored in a known, secure location. Verify that the document owner or compliance officer can locate and produce it within 48 hours. Check that the report is in an accessible format and contains all required sections (methodology, participants, findings, remediation status).","commonFailures":["Report stored on a former employee's personal drive, no one can locate it","Report exists but is marked 'draft' and was never finalised","Multiple versions of the report exist with no clear indication of which is current"]}},"links":{"eaaDirective":"EAA Directive 2019/882","en301549":"EN 301 549 V3.2.1"}},"video-media-checklist":{"meta":{"title":"Video & Media Accessibility Checklist, EN 301 549 Chapter 7","description":"EN 301 549 Chapter 7 + WCAG 1.2 series, verify captions, audio description, player controls, and media content accessibility."},"header":{"title":"Video & Media Accessibility Checklist","subtitle":"EN 301 549 Chapter 7 + WCAG 1.2 Compliance","description":"EN 301 549 Chapter 7 + WCAG 1.2 series, verify captions, audio description, player controls, and media content accessibility."},"features":{"f1":"EN 301 549 Chapter 7 full coverage","f2":"24 checkpoints, captions, audio description, player controls, content","f3":"Pass / Partial / Fail / N/A with detailed guidance","f4":"How-to-test guidance and common failures for every checkpoint","f5":"Links to relevant testing tools on AccessibilityRef","f6":"Progress auto-saved in your browser","f7":"Export Word report with notes","f8":"Direct links to EAA Directive and EN 301 549"},"categories":{"captions":{"label":"Captioning","description":"EN 301 549 §7.1, ICT with video capabilities must support caption display, synchronization, and preservation."},"audio-desc":{"label":"Audio Description","description":"EN 301 549 §7.2, Audio description provides narration of key visual content for blind and low-vision users."},"controls":{"label":"Player Controls","description":"EN 301 549 §7.3, User controls for captions and audio description must be keyboard-operable, labelled, and prominent."},"content":{"label":"Media Content Requirements","description":"WCAG 1.2 series and EAA Annex I requirements for the actual media content provided."}},"items":{"c1":{"text":"The media player can display captions when available.","guidance":"If your product plays video, the player UI must be able to render closed captions. This applies to embedded players, native apps, and streaming services.","testMethod":"Load a video that has a caption track (SRT, VTT, or embedded CEA-608/708). Look for a CC button in the player controls and activate it. Verify that caption text appears overlaid on the video. Test in at least two browsers (Chrome and Firefox) and on mobile. If captions do not render or there is no toggle, this fails.","commonFailures":["Custom-built video player has no caption rendering engine, captions silently ignored even when the video file contains a subtitle track","Player renders captions on desktop but the mobile version strips the CC toggle to save space","Embedded third-party player (e.g. Vimeo basic) does not support sidecar caption files uploaded by the content team","Player only supports SRT format but content team provides WebVTT, captions fail to load with no error message"]},"c2":{"text":"Captions are synchronised with the audio, within 100ms tolerance.","guidance":"Captions that appear too early or too late undermine comprehension. Test synchronisation across the full duration of the video, not just the start.","testMethod":"Play the video with captions enabled and watch at least three segments: the beginning, middle, and end. Note whether caption text appears at the same moment the corresponding words are spoken. A delay of more than approximately 100 milliseconds is noticeable. Use a media analysis tool like Subtitle Edit or Aegisub to inspect timestamp alignment if precision is needed.","commonFailures":["Captions were authored against a rough cut and the final video was re-edited, shifting all audio by several seconds","Live-to-VOD recording has captions that drift progressively later because the caption file uses a different frame rate than the video","Auto-generated captions on a platform like YouTube are re-synced after processing, causing a 1-2 second lag on longer videos"]},"c3":{"text":"Captions are not stripped or lost during video processing, conversion, or distribution.","guidance":"If your pipeline transcodes video (e.g. Uploading, CDN processing), verify that caption tracks survive the process intact.","testMethod":"Upload a video with an embedded caption track or sidecar caption file through your full publishing pipeline. After processing completes, download or play the published version and confirm captions are still present and intact. Check that no characters are corrupted (especially accented characters and special symbols). Repeat for each output format your pipeline produces (HLS, DASH, MP4).","commonFailures":["CDN transcoding pipeline strips subtitle tracks from MP4 containers during HLS segmentation","CMS upload workflow accepts caption files but the build step does not copy them to the output directory","Video encoding service converts embedded captions to a format the player does not support, effectively losing them","Non-Latin characters (e.g. German umlauts, Polish diacritics) are corrupted during transcoding due to encoding mismatch"]},"c4":{"text":"Users can customise caption appearance, font, size, colour, background.","guidance":"The player should allow users to override default caption styling. This is essential for users with low vision who need high-contrast or large text captions.","testMethod":"Open the player settings or caption settings menu. Look for options to change caption font size, font family, text colour, and background colour/opacity. Change each setting and verify the changes are reflected on-screen. If no customisation options exist, this fails. If the player defers to OS-level caption settings (e.g. IOS or Windows caption preferences), verify those system settings are respected.","commonFailures":["Player uses hardcoded white text on a semi-transparent black background with no way to change it","Caption settings menu exists but changes do not persist after the video is reloaded or paused","Font size can be changed but the background does not resize to match, causing text to overflow and become unreadable","Player claims to respect system caption settings but ignores Windows High Contrast mode"]},"c5":{"text":"Spoken subtitles (text-to-speech of caption text) are available or can be enabled.","guidance":"For users who cannot read the captions visually, the system should be able to speak them aloud. This is especially relevant for deafblind users using refreshable braille.","testMethod":"Check if the player or platform offers a spoken subtitle or text-to-speech option for caption text. This may appear as a separate audio track or a TTS toggle in the settings menu. If no such feature exists, check whether the caption text is programmatically exposed so that a screen reader running on the device can access it. Test with NVDA or VoiceOver to see if the live caption text is announced.","commonFailures":["Caption text is rendered as a canvas overlay or bitmap, making it invisible to screen readers and TTS engines","Player exposes caption text to the DOM but uses aria-hidden on the caption container, blocking screen reader access","Spoken subtitle feature exists in the native app but not in the web version of the same platform"]},"c6":{"text":"All pre-recorded video with audio has accurate, synchronised captions.","guidance":"Captions must include all spoken dialogue, speaker identification, and relevant non-speech sounds like [applause] or [phone rings]. Auto-generated captions must be reviewed and corrected.","testMethod":"Select a sample of pre-recorded videos (at least 3, or 10% of the library, whichever is greater). Play each with captions enabled and compare caption text to what is actually spoken. Check for: missing dialogue, incorrect words, missing speaker identification, and missing non-speech sounds. If any video has no captions at all, this is an immediate fail. If captions exist but contain frequent errors, mark as partial.","commonFailures":["Marketing team publishes product demo videos without captions because 'they are short and simple'","Auto-generated captions on YouTube left unreviewed, technical terms like 'WCAG' captioned as 'W-CAG' or 'double-u cag'","Captions exist but do not include speaker identification in panel discussions or interviews with multiple participants","Background music and sound effects relevant to the narrative (e.g. An alarm beeping in a safety video) are not captioned"]},"c7":{"text":"Live video/audio has real-time captioning provision.","guidance":"Webinars, live streams, and live events must have real-time captioning, either through a human captioner (CART) or high-quality automated captioning with correction.","testMethod":"Attend or review a recording of a recent live event (webinar, live stream, town hall). Check whether real-time captions were provided. Ask the events team what captioning method is used (CART provider, AI auto-captions, or none). If AI auto-captions are used, review a segment for accuracy, if error rate is above approximately 5%, mark as partial. If no live captioning is provided at all, this fails.","commonFailures":["Company runs weekly webinars with no live captioning, assumes attendees can listen","AI auto-captioning enabled but accuracy is poor for speakers with accents or when technical jargon is used","CART captioning booked for external events but internal all-hands meetings have no captions","Live captions provided in English only despite a multilingual audience"]},"a1":{"text":"The media player can play an audio description track when available.","guidance":"If an audio description track exists, the player must be able to select and play it. This is a player capability requirement.","testMethod":"Load a video that has an audio description track (either as a secondary audio track or a separate file). Look for an audio description toggle or audio track selector in the player controls. Activate it and verify that the description audio plays alongside the main audio. If the player has no mechanism to select alternative audio tracks, this fails.","commonFailures":["Player supports multiple audio tracks for language selection but does not expose audio description tracks in the same menu","Audio description track is available in the source file but the player only renders the primary audio track","Player uses a proprietary format that does not support multiple audio tracks, making audio description technically impossible"]},"a2":{"text":"Audio description is synchronised with the video content.","guidance":"The description must align with the visual action it describes. Descriptions should fit into natural pauses in dialogue.","testMethod":"Play the video with audio description enabled. Verify that descriptions are spoken during pauses in dialogue and that they describe the visual action that is currently on screen, not what happened 5 seconds ago. If descriptions overlap with dialogue or describe scenes that have already passed, this fails.","commonFailures":["Audio description was authored against an earlier edit of the video and timing no longer matches the final cut","Descriptions overlap with dialogue because the script was not timed to fit natural pauses","Description track describes a scene that appears 3 seconds later due to a frame-rate mismatch between the video and the description file"]},"a3":{"text":"Audio description tracks are not stripped or lost during processing.","guidance":"Like captions, audio description tracks must survive transcoding and distribution. Verify the full pipeline.","testMethod":"Upload a video with an audio description track through your complete publishing pipeline. After processing, download or stream the published version and check that the audio description track is still selectable and plays correctly. Test across all delivery formats (HLS, DASH, progressive MP4).","commonFailures":["Transcoding pipeline configured to output only the primary audio track, silently dropping the audio description track","Audio description track survives processing but is not listed in the player manifest file, making it invisible to the player","CDN caching serves an older version of the video without the audio description track that was added later"]},"a4":{"text":"Pre-recorded video has an audio description or full text alternative.","guidance":"For videos where the visual content conveys information not available in the audio (e.g. On-screen text, demonstrations), provide audio description or a detailed transcript.","testMethod":"Watch the video without looking at the screen (audio only). Note any points where visual-only information is conveyed, on-screen text, charts, demonstrations of physical actions, scene changes. Check whether audio description narrates these moments or whether a full text alternative (descriptive transcript) is linked adjacent to the video. If neither exists and the video contains visual-only information, this fails.","commonFailures":["Product tutorial shows on-screen clicks and menu navigation but the narration only says 'click here and here' without naming the elements","Training video displays a data chart on screen for 10 seconds with no verbal description of the data","Video has a text transcript but it only includes the spoken dialogue, not descriptions of the visual content","Animated explainer video uses visual metaphors (arrows, colour changes) that are never described in the audio"]},"a5":{"text":"Audio description is provided for all pre-recorded video content (Level AA).","guidance":"At Level AA, audio description is required, not just a text alternative. This is the EAA baseline requirement via EN 301 549.","testMethod":"Audit your video content library. For each video that contains meaningful visual-only information, check that a dedicated audio description track exists (not just a transcript). Sample at least 3 videos or 10% of the library. If any video with significant visual content lacks audio description, this fails. Videos where the audio track already describes all on-screen content fully may be marked N/A.","commonFailures":["Organisation provides text transcripts for all videos but has not produced any audio description tracks, relying on the WCAG 1.2.3 fallback instead of meeting the AA requirement","Audio description exists for flagship product videos but not for support tutorials or onboarding content","Audio description was produced for the English version of videos but not for localised versions","Marketing team considers audio description unnecessary for 'simple' videos, but those videos contain visual product demonstrations"]},"p1":{"text":"Controls to activate captions and audio description are prominently available in the player UI.","guidance":"Caption and audio description toggle buttons must not be hidden in sub-menus. They should be visible in the main player controls.","testMethod":"Look at the video player control bar. Without clicking any menus or settings icons, check whether a CC/captions button and an audio description button are visible. If either control requires opening a settings menu, sub-menu, or overflow menu to find, this is partial. If the controls are not available at all, this fails.","commonFailures":["CC button is hidden inside a 'Settings' gear icon that requires two clicks to reach","Audio description toggle exists but is only accessible via a right-click context menu that touch/keyboard users cannot reach","Player shows the CC button only when a caption track is detected, but detection fails silently so the button never appears","Controls are visible on desktop but hidden on mobile to save space in the smaller control bar"]},"p2":{"text":"Caption and audio description controls are keyboard-operable.","guidance":"Users must be able to toggle captions and audio description using keyboard alone, Tab to reach, Enter/Space to activate.","testMethod":"Click somewhere on the page above the video player, then use Tab to move focus into the player controls. Continue tabbing until you reach the CC button and the audio description button. Press Enter or Space to toggle each. If you cannot reach the controls via Tab, or they do not respond to Enter/Space, this fails. Test in both Chrome and Firefox.","commonFailures":["Player controls are built with div elements and click handlers but no tabindex or keyboard event listeners","Tab key moves focus into the player but skips the CC button, jumping from play/pause directly to the volume slider","CC button receives focus and responds to Enter but the audio description button is not in the tab order","Keyboard focus enters the player but gets trapped, pressing Tab cycles between controls indefinitely with no way to exit"]},"p3":{"text":"Controls have accessible labels (e.g. 'Toggle captions', 'Enable audio description').","guidance":"Button text or aria-label must clearly describe the action. Icon-only buttons without labels are inaccessible to screen reader users.","testMethod":"Inspect each player control button using browser DevTools or a screen reader. For icon-only buttons, check for aria-label, aria-labelledby, or visually hidden text that describes the action. The label should be specific (e.g. 'Toggle captions on' not just 'CC'). Run NVDA or VoiceOver and tab through the controls, each button should be announced with a meaningful name.","commonFailures":["CC button has no aria-label, screen reader announces it as 'button' with no description","Buttons use title attributes instead of aria-label, which many screen readers do not announce by default","Label says 'Button 3' or uses an internal identifier instead of a human-readable description","Toggle button does not communicate state, screen reader cannot tell if captions are currently on or off"]},"p4":{"text":"All player controls (play, pause, seek, volume) are keyboard-accessible.","guidance":"Every interactive control in the video player must be operable with keyboard alone. No mouse-only interactions.","testMethod":"Using only the keyboard (no mouse), attempt to: play the video, pause it, seek forward and backward, adjust volume, enter and exit fullscreen, and toggle captions. Tab through all controls and operate each with Enter, Space, or arrow keys as appropriate. If any control cannot be reached or operated via keyboard, this fails.","commonFailures":["Seek bar is a custom range slider that only responds to mouse drag, arrow keys have no effect","Volume control appears on hover and cannot be triggered via keyboard","Fullscreen button works with keyboard but there is no keyboard shortcut or button to exit fullscreen, user is trapped","Play/pause works with Space but only when the player has focus, if focus is lost, Space scrolls the page instead"]},"p5":{"text":"All player controls have a visible focus indicator.","guidance":"When tabbing through player controls, each focused element must show a clear visual indicator (outline, ring, or equivalent).","testMethod":"Tab through the video player controls and observe each one as it receives focus. Each control should display a visible focus ring, outline, or highlight that has at least 3:1 contrast against the surrounding background. If any control receives focus without a visible change in appearance, this fails. Check both light and dark player themes if applicable.","commonFailures":["Player CSS includes 'outline: none' on buttons with no replacement focus style","Focus indicator is a thin 1px grey line on a dark player background, insufficient contrast","Focus ring appears on buttons but not on the seek bar or volume slider","Custom player theme overrides browser default focus styles without adding new ones"]},"m1":{"text":"Pre-recorded audio-only content (podcasts, audio clips) has a full text transcript.","guidance":"A verbatim transcript must be available adjacent to or linked from the audio player. Include speaker identification and relevant non-speech audio.","testMethod":"Identify all audio-only content on your site or product (podcasts, audio messages, voice recordings). For each, check whether a text transcript is provided on the same page or linked directly from the player. The transcript should include speaker names, all spoken words, and descriptions of relevant non-speech sounds. If any audio-only content lacks a transcript, this fails.","commonFailures":["Company podcast published weekly with no transcripts, team considers them optional because 'everyone listens'","Transcript exists but is a separate PDF download that is itself inaccessible (scanned image)","Transcript includes spoken words but omits speaker identification, making multi-person podcasts impossible to follow","Audio customer testimonials on the marketing site have no text alternative"]},"m2":{"text":"Pre-recorded video-only content (silent demos, animations) has a text transcript or audio track.","guidance":"Silent product demos, animated infographics, and similar video-only content must have a descriptive text alternative or narration audio track.","testMethod":"Find all video content that has no audio track (silent screen recordings, animated GIFs converted to video, motion graphics without narration). Check whether each has either: (1) a descriptive text transcript linked from the page, or (2) a narration audio track. If neither exists, this fails. Animated GIFs that convey information also fall under this requirement.","commonFailures":["Product changelog page uses silent screen recordings to show new features with no text description","Animated infographic auto-plays on the homepage showing statistics with no text alternative","Silent demo video has a caption track, but captions only work for audio content, a descriptive transcript of the visual content is what is needed here"]},"m3":{"text":"Captions include speaker identification where multiple speakers are present.","guidance":"When more than one person speaks, captions must identify who is speaking, e.g. [Sarah]: or >> SARAH:, so viewers can follow the conversation.","testMethod":"Select videos that feature two or more speakers (interviews, panel discussions, meetings). Enable captions and watch a segment where speakers change. Check that each new speaker is identified by name or role before their dialogue. If captions show dialogue without any speaker labels, this fails.","commonFailures":["Interview video captions show all text in the same style with no indication of which person is speaking","Speaker labels used for the first exchange but dropped after the first minute","Auto-generated captions do not include speaker identification and no one has added them manually","Speaker identified as 'Speaker 1' and 'Speaker 2' instead of actual names or roles"]},"m4":{"text":"Captions include relevant non-speech sounds (e.g. [applause], [alarm beeping]).","guidance":"Non-speech information conveyed through audio, sound effects, music cues, environmental sounds, must be captioned when relevant to understanding.","testMethod":"Watch several videos with captions enabled and listen for non-speech sounds that convey meaning: alert tones, background music that sets mood, applause, laughter, environmental sounds. Check whether these are represented in the captions with descriptions like [applause], [upbeat music], [door slams]. If meaningful non-speech sounds are consistently absent from captions, this fails.","commonFailures":["Training video uses a 'ding' sound to indicate correct answers and a 'buzz' for incorrect ones, neither is captioned","Product demo video has an error alert sound that is critical to understanding the workflow but is not captioned","Background music changes to indicate a shift in tone (e.g. Tense music during a security warning) but captions do not note this","Captions include [music] once at the start but do not note when music stops or changes"]},"m5":{"text":"Sign language interpretation is available for key content (best practice).","guidance":"While not strictly required at WCAG AA, sign language interpretation for important content (legal, safety, onboarding) is a strong EAA best practice and may be required in some national transpositions.","testMethod":"Review key content categories: legal terms, safety information, onboarding videos, and major announcements. Check whether any of these have sign language interpretation available (either as a picture-in-picture interpreter or a separate sign language version). If none exists, note this as a gap. Check whether your national EAA transposition specifically requires sign language for any content categories.","commonFailures":["No sign language interpretation exists for any video content despite serving a large deaf community","Sign language video exists but uses a different sign language than the target audience (e.g. ASL provided for a European audience that uses their national sign language)","Sign language interpreter window is too small to read clearly or is cropped by the player controls"]}}},"voice-comms-checklist":{"meta":{"title":"Voice & Video Calling Checklist, EN 301 549 Chapter 6","description":"EN 301 549 Chapter 6 compliance checklist, verify that your voice and video calling services meet European Accessibility Act requirements."},"header":{"title":"Voice & Video Calling Checklist","subtitle":"EN 301 549 Chapter 6 Compliance Checklist","description":"EN 301 549 Chapter 6 compliance checklist, verify that your voice communication services meet European Accessibility Act requirements."},"features":{"f1":"EN 301 549 Chapter 6 full coverage","f2":"17 checkpoints across audio, RTT, caller ID, alternatives & video","f3":"Pass / Partial / Fail / N/A with notes per item","f4":"How-to-test guidance and common failures for every checkpoint","f5":"Links to relevant testing tools on AccessibilityRef","f6":"Progress auto-saved in your browser","f7":"Export Word report with notes","f8":"Direct links to EAA Directive and EN 301 549"},"categories":{"audio":{"label":"Audio Quality & Bandwidth","description":"EN 301 549 §6.1, Voice communication services must support sufficient audio bandwidth for speech intelligibility."},"rtt":{"label":"Real-Time Text (RTT)","description":"EN 301 549 §6.2, If voice communication is provided, real-time text must be supported alongside it."},"caller":{"label":"Caller Identification","description":"EN 301 549 §6.3, Caller identity must be available in text form."},"alternatives":{"label":"Alternatives to Voice","description":"EN 301 549 §6.4, At least one non-voice communication alternative must be available."},"video":{"label":"Video Communication","description":"EN 301 549 §6.5, If video calling is provided, quality must support sign language communication."}},"items":{"aq1":{"text":"Voice communication supports a frequency range of at least 300–3400 Hz (narrowband minimum).","guidance":"This is the minimum for speech intelligibility. Standard telephony meets this. VoIP services must ensure codec selection supports at least this range.","testMethod":"Review the audio codec specifications used by the service (e.g. G.711, Opus, AMR). Check the codec datasheet for the supported frequency range. G.711 supports 300–3400 Hz by default. If using a custom VoIP solution, use an audio spectrum analyser during a test call to verify frequencies below 300 Hz and above 3400 Hz are not being cut. If the codec or system documentation confirms narrowband support, it passes.","commonFailures":["VoIP service using a highly compressed codec that cuts off frequencies above 2500 Hz, reducing speech clarity","Custom implementation that applies aggressive noise filtering which removes speech frequencies","System configured with a codec that only supports 500–2500 Hz, failing to cover the full narrowband range"]},"aq2":{"text":"Wideband audio (150–7000 Hz) is supported where the network allows.","guidance":"Wideband audio significantly improves speech clarity for hearing aid users and users with hearing loss. HD Voice / VoLTE support is strongly recommended.","testMethod":"Check the service's codec negotiation, does it offer wideband codecs (G.722, Opus wideband, AMR-WB) when bandwidth is available? Make a test call on a high-bandwidth connection and use a spectrum analyser to verify frequencies up to 7000 Hz are transmitted. Check the call quality indicator or codec display if available. If the service only ever uses narrowband codecs even on good connections, it fails.","commonFailures":["Service hardcodes G.711 narrowband and never negotiates up to a wideband codec","Wideband codec is available but the system defaults to narrowband and provides no way to prefer wideband","Mobile app supports HD Voice but the backend infrastructure downgrades all calls to narrowband","Wideband works for calls within the platform but is lost when bridging to PSTN without fallback notification"]},"rt1":{"text":"If voice communication is provided, real-time text (RTT) is also supported.","guidance":"RTT transmits text character-by-character as it is typed, unlike SMS or chat where text is sent as a block. This is essential for deaf and hard-of-hearing users.","testMethod":"Initiate a call using the service. Look for an RTT or text option during the call. If an RTT button or text input field is available, type a message and verify it transmits character-by-character to the other party (not waiting for Enter to send). If the service offers voice calls but has no RTT capability at all, it fails. Note: standard chat/messaging is not the same as RTT.","commonFailures":["Service offers voice calls and a separate chat feature, but no real-time text within the call itself","RTT option exists in settings but is permanently greyed out or non-functional","Text messaging is available but only sends complete messages (not character-by-character), this is chat, not RTT","RTT was implemented but removed in a later update without replacement"]},"rt2":{"text":"RTT can be used simultaneously with voice (concurrent voice and text).","guidance":"Users must be able to speak AND type in the same call, not be forced to choose between voice mode and text mode.","testMethod":"Start a call with RTT enabled. While the voice channel is active, type text and verify it transmits. Then speak and verify voice audio is also transmitted simultaneously. If the system forces the user to switch between voice mode and text mode (e.g. A toggle that disables voice when text is active), it fails. Both channels must operate concurrently.","commonFailures":["System has a 'voice mode' and 'text mode' toggle, user must pick one, cannot use both at once","Typing RTT mutes the microphone automatically","Voice call drops or pauses when the RTT input field is activated","RTT is available only before the call connects but not during an active voice call"]},"rt3":{"text":"Sent and received RTT are visually distinguishable in the display.","guidance":"Like a chat interface, the user's own text and the remote party's text must be visually distinct (different colours, sides, or labels).","testMethod":"During an RTT call, send text from both sides. Examine the display: (1) Is sent text visually different from received text? Check for colour differences, alignment (left vs right), labels ('You' vs 'Caller'), or speech bubble styling. (2) Can you immediately tell who typed what without reading the content? If sent and received text look identical with no visual distinction, it fails.","commonFailures":["All RTT text displayed in a single stream with no indication of who typed each character","Sent and received text use the same colour and alignment, only distinguishable by tiny labels easily missed","Text direction is shown but only via a small arrow icon that is not visible to users with low vision","In group calls, RTT from multiple participants is displayed with no per-person identification"]},"rt4":{"text":"Direction of RTT (sent vs received) is programmatically determinable.","guidance":"Screen readers must be able to distinguish sent from received text, not just visual styling but semantic markup.","testMethod":"Enable VoiceOver (iOS) or TalkBack (Android) during an RTT call. Navigate to the RTT display area. When the screen reader reads sent text, it should announce something like 'You: hello' or 'Sent: hello'. When reading received text, it should announce 'Caller: hi' or 'Received: hi'. If the screen reader reads all text identically with no directional context, it fails. On web-based RTT, inspect the HTML for aria-labels or semantic roles that indicate direction.","commonFailures":["Screen reader reads all RTT text as a flat list with no 'sent' or 'received' context","Visual distinction exists (colours/sides) but no programmatic labels for assistive technology","Accessibility labels say 'message' for both sent and received text, no directional information","RTT display uses a canvas or image rendering that is completely opaque to screen readers"]},"rt5":{"text":"RTT interoperates with other RTT-capable services and networks.","guidance":"RTT from your service must be able to reach users on other RTT-capable platforms. Interoperability with standards like RFC 4103 is expected.","testMethod":"Attempt to send RTT from your service to a different RTT-capable service or device (e.g. An RTT-capable phone, a different VoIP platform that supports RFC 4103). Verify that text arrives character-by-character on the remote end. If your service can only send RTT to other users of the same service but not to external RTT endpoints, it is partial. If no interoperability has been tested or implemented, it fails.","commonFailures":["RTT works between users of the same app but cannot interoperate with PSTN RTT or other platforms","Service claims RFC 4103 support but has never been tested against another implementation","RTT is converted to SMS when crossing network boundaries, losing the real-time character-by-character property","Interoperability exists for domestic calls but fails for international RTT calls"]},"rt6":{"text":"RTT characters appear within 500ms of being typed.","guidance":"The defining feature of RTT is real-time display. Characters must appear on the remote screen within half a second of being typed, not buffered until Enter is pressed.","testMethod":"Set up two devices on a call with RTT enabled. On device A, type a single character and start a stopwatch. On device B, measure how long until the character appears. Repeat 10 times and average the results. The average must be under 500ms. Alternatively, screen-record both devices simultaneously and measure frame-by-frame delay. If characters are buffered until Enter is pressed or appear with more than 500ms delay, it fails.","commonFailures":["System buffers text and sends it as a complete message when Enter is pressed, this is chat, not RTT","Characters transmit in real-time on fast networks but buffer for 2+ seconds on slower connections","Implementation sends text word-by-word (on space key) instead of character-by-character","RTT delay exceeds 1 second due to server-side processing or transcoding in the signalling path"]},"ci1":{"text":"Caller identification is available in text form, not just audio announcement.","guidance":"Deaf users cannot hear the caller's name announced by the system. Caller ID must be displayed visually and exposed to assistive technology.","testMethod":"Receive an incoming call on the service. Verify that the caller's identity (name, number, or both) is displayed as text on screen, not just spoken by an audio announcement. Then enable VoiceOver or TalkBack and receive another call. Verify the screen reader announces the caller's identity from the visual text. If caller ID is only available as an audio ring tone or spoken announcement with no visual text, it fails.","commonFailures":["Incoming call screen shows 'Incoming Call' with no caller name or number displayed","Caller name is spoken by the system but the screen only shows a generic phone icon","Caller ID text is displayed but not exposed to the accessibility API, screen reader announces 'incoming call' only","Group call or conference bridge shows no participant names, just 'Conference Call' text"]},"av1":{"text":"At least one non-voice alternative is available (text, email, chat, video relay).","guidance":"Users who cannot speak (mute users, speech disabilities) must have an alternative communication channel. Text chat, email, or video relay must be offered.","testMethod":"Review all communication channels offered by the service. Identify whether at least one non-voice option exists: text chat, email, contact form, SMS, video relay, or RTT. Try to complete the same tasks available via voice through the non-voice channel. If the only way to communicate is by speaking on a voice call, it fails. If a text alternative exists but only covers limited functionality, it is partial.","commonFailures":["Customer support is available only via phone call, no email, chat, or text option","Text chat exists but can only handle basic enquiries, anything complex requires a phone call","Non-voice alternative is listed on the website but is perpetually 'offline' or unresponsive","Email support is available but has a 5-day response time while phone support is instant, not equivalent service"]},"av2":{"text":"The non-voice alternative provides equivalent functionality to the voice channel.","guidance":"If voice support can resolve all issues, the text/chat alternative must also have full resolution capability, not just a 'please call us' redirect.","testMethod":"List all actions or resolutions available via the voice channel (e.g. Account changes, technical support, complaints, purchases). Attempt each one through the non-voice alternative. If any action requires escalation to a phone call or is refused via the non-voice channel, it is partial or fail. The non-voice channel must provide the same resolution authority and access to the same services.","commonFailures":["Chat agent says 'For security reasons, this change can only be made over the phone'","Email support can answer questions but cannot make account changes or process refunds","Text channel has restricted hours (9-5) while phone support is 24/7","Non-voice channel requires identity verification methods that are only possible by voice (e.g. 'tell me your passphrase')"]},"vc1":{"text":"Video calling supports at least QVGA resolution (320×240 pixels).","guidance":"This is the minimum resolution for sign language to be intelligible. Higher resolution is preferred for clear hand and facial expression visibility.","testMethod":"Start a video call and check the transmitted video resolution. Most platforms display this in call statistics or debug info (e.g. Settings, WebRTC getStats()). Verify the resolution is at least 320x240 pixels. If the platform auto-adjusts quality, test on a constrained connection to see the minimum resolution floor. If the video drops below QVGA on a reasonable connection, it fails.","commonFailures":["Video quality drops to 160×120 on moderate bandwidth, making sign language unintelligible","Platform prioritises audio quality and aggressively reduces video to thumbnail resolution","Video resolution meets QVGA but heavy compression artefacts make hand shapes unreadable","Screen sharing mode reduces participant video to a tiny low-resolution thumbnail"]},"vc2":{"text":"Video frame rate is at least 20fps, adaptable to network conditions.","guidance":"Below 20fps, sign language becomes difficult to understand. The system should prioritise frame rate over resolution when bandwidth is limited.","testMethod":"During a video call, check the frame rate in the platform's call statistics or use a frame rate counter tool on a screen recording. The frame rate should be at least 20fps under normal conditions. Then simulate reduced bandwidth (using network throttling tools or a mobile connection) and verify the system prioritises maintaining frame rate over resolution. If frame rate drops below 20fps on a reasonable connection, it fails.","commonFailures":["Frame rate drops to 10-15fps during normal calls, making rapid sign language movements jerky and unclear","System prioritises high resolution over frame rate, sends 720p at 10fps instead of 480p at 25fps","Frame rate is adequate for the active speaker but drops for other participants in gallery view","Screen sharing mode locks video to 5fps to save bandwidth, even for sign language interpreters"]},"vc3":{"text":"Audio and video are synchronised, lip sync within 100ms.","guidance":"Lip-reading users depend on precise audio-visual sync. Test under typical network conditions, not just ideal.","testMethod":"During a video call, have the remote participant count aloud ('one, two, three') while you observe their lip movements. If the audio and lip movements are noticeably out of sync, it may fail. For precise measurement, record the call and analyse the audio-video offset frame-by-frame, the offset must be within 100ms. Test on both Wi-Fi and mobile data connections. If lip sync is consistently off by more than 100ms, it fails.","commonFailures":["Audio arrives 200-300ms before video, making lip reading impossible","Sync is fine at call start but drifts over time, after 10 minutes, audio leads video by 500ms+","Audio and video are synced on desktop but consistently out of sync on mobile clients","When network jitter occurs, the system resynchronises audio but not video, causing persistent offset"]},"vc4":{"text":"A visual indicator is shown when audio is active (speaking indicator).","guidance":"Deaf users on video calls need a visual cue that someone is speaking, a pulsing icon, border highlight, or waveform.","testMethod":"Join a video call with at least one other participant. When the other participant speaks, look for a visual indicator: a glowing border around their video, a microphone icon animation, a waveform display, or a speaking badge. Mute your speakers to confirm you can still tell who is speaking from visual cues alone. If no visual speaking indicator exists, it fails. Also verify the indicator works when the speaker's camera is off.","commonFailures":["No speaking indicator at all, deaf users cannot tell who is talking in a group call","Speaking indicator exists but is too subtle (a thin 1px border change) to be noticed","Indicator only works when the speaker's camera is on, disappears when camera is off","Speaking indicator has a significant delay (2+ seconds) making it unreliable for following conversation flow"]},"vc5":{"text":"The active speaker is visually identified when multiple participants are present.","guidance":"In group calls, the current speaker must be visually highlighted so sign language interpreters and lip readers know who to watch.","testMethod":"Join a group video call with 3+ participants. Have different participants speak one at a time. Verify that the active speaker is clearly highlighted, e.g. Their video tile enlarges, moves to a prominent position, or has a distinctive border. The identification must be immediate and unambiguous. If all participants look the same regardless of who is speaking, it fails. Test in both gallery view and speaker view modes if available.","commonFailures":["Gallery view shows all participants equally with no active speaker highlighting","Active speaker highlight exists but there is a 3-second delay before it switches","In large meetings (10+ participants), the active speaker is not visible without scrolling","Speaker view works but defaults to gallery view where active speaker is not highlighted"]},"vc6":{"text":"A non-video alternative exists for all video-based communication.","guidance":"Users who cannot use video (bandwidth constraints, privacy, blindness) must have an alternative, voice + RTT, or text-only communication.","testMethod":"Check whether the service allows participation in video-based communication without enabling the camera. Verify: (1) users can join with camera off and still participate fully, (2) voice-only participation is supported, (3) text/RTT participation is available for users who cannot use voice or video. If the service requires video to participate (e.g. Video verification, mandatory camera policy enforced by the platform), it fails.","commonFailures":["Platform requires camera to be on to join the meeting, no camera-off option","Users can turn camera off but then lose access to features like screen sharing or reactions","Audio-only dial-in number exists but provides no access to chat, shared content, or RTT","Service is video-only with no voice or text fallback for users on low-bandwidth connections"]}}},"vpat-editor":{"meta":{"title":"VPAT® / ACR Editor","description":"Create a professional Accessibility Conformance Report (ACR) documenting your product's WCAG 2.2 conformance, criterion by criterion. Export to Word for procurement submissions."},"header":{"title":"VPAT® / ACR Editor","subtitle":"Create a professional Accessibility Conformance Report (ACR) documenting your product's WCAG 2.2 conformance, criterion by criterion. Export to Word for procurement submissions.","badge":"Pro Tool","badges":{"vpat":"VPAT® 2.5","wcag":"WCAG 2.2 Edition","criteria":"56 Criteria"}},"features":["Full VPAT® 2.5 editor covering all 56 WCAG 2.2 success criteria","Structured conformance levels: Supports / Partially Supports / Does Not Support","Export to Word, ready for procurement and tender submissions","EAA and EN 301 549 cross-references included"],"explain":{"toggle":"What is a VPAT and why do you need one?","toggleSub":"Understand the purpose, who needs it, and how to complete it correctly","whatIsVpat":"What is a VPAT®?","whatIsVpatBody":"A VPAT® (Voluntary Product Accessibility Template) is a standardised document format created by the Information Technology Industry Council (ITI) that software vendors use to declare how their product conforms to accessibility standards. When filled out, it becomes an Accessibility Conformance Report (ACR). The VPAT format is widely recognised by procurement teams, government bodies, and enterprise buyers worldwide.","whyUsed":"Why is it used, and who asks for it?","whyUsedBody":"Buyers, particularly government agencies, higher education institutions, and large enterprises, request ACRs during procurement to compare vendors on accessibility. Under the European Accessibility Act, Section 508 (USA), and similar laws, buyers have a duty to procure accessible products. An ACR is the standard evidence format they require. Without one, vendors are often excluded from procurement processes entirely.","whichEdition":"What edition should I use?","whichEditionBody":"This tool generates the WCAG 2.2 Edition, which covers all 56 WCAG 2.2 success criteria across 4 principles (Perceivable, Operable, Understandable, Strong). For US federal procurement, you may also need the Revised Section 508 Edition or the International Edition, both reference WCAG 2.1, which is a subset of 2.2. The WCAG 2.2 Edition is the most current and full.","howToComplete":"How to complete this accurately","howToCompleteBody":"For each criterion, select the conformance level that honestly reflects your product. 'Supports' means the criterion is met without known defects. 'Partially Supports' means some functionality fails. 'Does Not Support' means most functionality fails. 'Not Applicable' means the criterion genuinely cannot apply (e.g. A product with no audio content cannot fail 1.2.2 Captions). Use the Remarks column to explain any partial or non-support, name the affected component, and, where possible, provide a remediation date.","legalStatus":"Legal status of an ACR","legalStatusBody":"An ACR is not a legally binding document in itself, it is a voluntary declaration. However, misrepresenting conformance in an ACR used in a procurement process may constitute misrepresentation or fraud under contract law in many jurisdictions. The document should be accurate, dated, and reviewed by your accessibility team before submission. It is best practice to attach it to your EU Declaration of Conformity as supporting evidence."},"productInfo":{"title":"Product Information","subtitle":"Appears in the ACR header","productName":"Product Name","productNamePlaceholder":"E.g. CloudPortal","version":"Version / URL","versionPlaceholder":"E.g. V2.4.1","vendor":"Vendor / Company","vendorPlaceholder":"E.g. Acme Software Ltd","reportDate":"Report Date"},"eaaContext":{"title":"EAA Regulatory Context","subtitle":"Appears in the ACR header and Word export","annexISection":"EAA Annex I Section","annexISectionPlaceholder":"E.g. Annex I, Section IX, E-commerce services","annexIHint":"Identifies which EAA product/service category this ACR covers. Include in all regulatory submissions.","evaluationStandard":"Evaluation Standard","platformScope":"Platform Scope","webOnly":"Web only, Clause 9","mobileOnly":"Mobile app only, Clause 11","desktop":"Desktop software, Clause 11","webAndMobile":"Web + Mobile, Clauses 9 & 11","standardV321Label":"EN 301 549 V3.2.1","standardV321Note":"OJEU harmonised","standardV411Label":"EN 301 549 V4.1.1","standardV411Note":"Best practice","standardV411Warning":"V4.1.1 is not yet in the OJEU harmonised list. This ACR does not provide a presumption of conformity under Article 15 EAA. Consider noting V3.2.1 compliance is also satisfied.","clause11Warning":"Clause 11 (non-web software) applies to mobile apps and desktop software. This VPAT editor covers Clause 9 (web) criteria only. For mobile or desktop software, a separate EN 301 549 Clause 11 assessment is required. Criteria in Clauses 11.5–11.8 address native app accessibility and are not represented here.","clause11WarningStrong":"Clause 11 (non-web software) applies to mobile apps and desktop software.","clause11WarningRest":"This VPAT editor covers Clause 9 (web) criteria only. For mobile or desktop software, a separate EN 301 549 Clause 11 assessment is required. Criteria in Clauses 11.5–11.8 address native app accessibility and are not represented here.","webAndMobileNote":"If this ACR covers both web and mobile, clearly label the scope of each section. Procurement teams expect distinct Clause 9 and Clause 11 coverage tables."},"contactEval":{"title":"Contact & Evaluation","contactName":"Contact Name","contactNamePlaceholder":"Accessibility contact","contactEmail":"Contact Email","contactEmailPlaceholder":"Accessibility@example.com","evaluatedBy":"Evaluated By","evaluatedByPlaceholder":"Internal team / Agency name","notes":"Notes / Evaluation scope","notesPlaceholder":"Describe the scope, testing environment, and any important context for the reader."},"conformance":{"supports":"Supports","partiallySupports":"Partially Supports","doesNotSupport":"Does Not Support","notApplicable":"Not Applicable","notEvaluated":"Not Evaluated","remarks":"Remarks and Explanations","remarksPlaceholder":"Explain any partial support, affected component, or planned fix…","level":"Conformance Level","selectPlaceholder":"Select,","notAssessedOption":"Not assessed"},"principles":{"perceivable":"Perceivable","operable":"Operable","understandable":"Understandable","robust":"Robust"},"progress":{"filled":"{count} of {total} criteria assessed","supports":"Supports","partial":"Partial","fail":"Fail","applyToAll":"Apply to all","completion":"Completion"},"exclusions":{"title":"Third-Party Component Exclusions","addExclusion":"+ Add exclusion","hint":"Third-party components outside your control should be excluded from this ACR with a clear explanation. Regulators and procurement teams expect exclusions to be disclosed, not hidden.","componentName":"Component name","componentNamePlaceholder":"E.g. FlightUI seat-selection widget","thirdPartyVendor":"Third-party vendor","thirdPartyVendorPlaceholder":"E.g. FlightUI Ltd.","reason":"Reason for exclusion","reasonPlaceholder":"E.g. Not under our control; vendor responsible for conformance","vendorAcr":"Vendor ACR/VPAT expected by","vendorAcrPlaceholder":"E.g. Q3 2026 / already requested","add":"Add","cancel":"Cancel","remove":"Remove","newExclusion":"New Exclusion","vendorLabel":"Vendor","reasonLabel":"Reason","vendorAcrExpectedLabel":"Vendor ACR expected"},"supplyChain":{"title":"Supply Chain VPAT Tracker","subtitle":"EAA Article 10, track third-party ACR collection","addComponent":"+ Add component","hint":"EAA Article 10 requires that accessibility obligations flow through the supply chain. Track which third-party components need VPATs/ACRs and whether they have been collected.","noComponents":"No components tracked yet. Add any third-party maps, payment widgets, chat tools, analytics, or media players that are embedded in your product.","requested":"Requested","received":"Received","acrReceived":"ACR received","pending":"Pending","notRequested":"Not requested","remove":"Remove","contractRefPlaceholder":"Contract clause / PO ref / SLA section","addThirdPartyTitle":"Add Third-Party Component","componentNamePlaceholder":"Component name (e.g. Google Maps embed, Stripe payment widget)","vendorPlaceholder":"Vendor / supplier name (e.g. Google LLC)","add":"Add","cancel":"Cancel","collectedSummary":"{received}/{total} third-party ACRs collected.","followUpVendors":"Follow up with outstanding vendors before finalising this ACR.","allCollected":"All supply chain ACRs collected."},"disabilityProfiles":{"title":"Test User Disability Profiles","hint":"Select the disability groups represented in your testing","blind":"Blind (screen reader)","lowVision":"Low vision (magnification)","colourBlind":"Colour blind","deaf":"Deaf / hard of hearing","motor":"Motor / mobility impaired","cognitive":"Cognitive / learning disability","speech":"Speech impaired","multiple":"Multiple disabilities","notesPlaceholder":"Additional notes e.g. 'NVDA 2024.4 + Chrome 121; VoiceOver 17.3 + Safari; TalkBack Android 14; keyboard-only (no mouse)'"},"criterion":{"scLabel":"SC","levelBadge":"Level {level}"},"en301549":{"sectionTitle":"EN 301 549 Non-WCAG Clauses","sectionSubtitle":"Clauses 5–7, 12–13, required for a complete EN 301 549 conformance report","expand":"▼ Expand","collapse":"▲ Collapse","intro":"A complete EN 301 549 ACR must address all applicable clauses, not only the WCAG-mapped Clause 9 (web) or Clause 11 (software) criteria. Many of these will be Not Applicable, but they must be explicitly declared.","remarksPlaceholder":"Remarks / justification for Not Applicable / explanation of any partial support...","clauses":{"5_2":{"title":"Activation of accessibility features","description":"ICT must not require the user to activate accessibility features to use them; accessibility must be available by default or on a single-step toggle."},"5_3":{"title":"Biometrics","description":"Where biometrics are used, at least one accessible non-biometric alternative must be available."},"5_4":{"title":"Preservation of accessibility information during conversion","description":"When converting document formats, accessibility information must be preserved in the output."},"5_5":{"title":"Operable parts, means of activation","description":"Physical controls must be operable with limited dexterity/strength; applies to hardware products."},"6_1":{"title":"Audio bandwidth for speech (two-way voice)","description":"Applies to ICT with real-time voice communication (e.g. Customer service calls). Minimum audio quality for intelligibility with hearing aids."},"6_2":{"title":"Real-time text (RTT) support","description":"ICT with voice communication must support real-time text interoperability for deaf users."},"6_3":{"title":"Caller ID","description":"Caller identification information must be available in text to deaf/hard-of-hearing users."},"7_1":{"title":"Captions, media player support","description":"Media players must support captioning. Applies to any ICT that plays video with audio."},"7_2":{"title":"Audio description, media player support","description":"Media players must support audio descriptions. Applies to ICT that plays video content."},"7_3":{"title":"User controls for captions and audio descriptions","description":"User must be able to activate and deactivate captions and audio descriptions while content is playing."},"12_1_1":{"title":"Accessibility features in product documentation","description":"Product documentation must describe all accessibility features of the product."},"12_1_2":{"title":"Accessible documentation","description":"Documentation and support materials must themselves be accessible (e.g. In accessible PDF or HTML)."},"12_2_2":{"title":"Information on accessibility features in support","description":"Support staff must be able to provide information on accessibility features."},"12_2_3":{"title":"Effective communication (support)","description":"Support services must be accessible to users of relay services and hearing/speech assistive technologies."},"13_1":{"title":"Relay services requirements","description":"Applies to ICT providing relay or emergency services access."}}},"itiNotice":{"title":"VPAT® version, verify with ITI before submission","body":"This tool generates reports based on <strong>VPAT® 2.5 (WCAG 2.2 Edition)</strong>. The Information Technology Industry Council (ITI) periodically releases updated VPAT® templates. Before submitting an ACR for procurement purposes, verify that VPAT® 2.5 is still the current version by checking the ITI website. Using an outdated template version may cause procurement officers to request resubmission against the current template."},"actions":{"exportWord":"Export to Word","exporting":"Exporting…","proOnlyExport":"Pro only, Upgrade to export","proOnlyTooltip":"Upgrade to Pro to export documents"},"samplePreview":{"toolName":"VPAT Editor","description":"The VPAT/ACR Editor helps you create Voluntary Product Accessibility Templates that enterprise customers and government procurement teams require. Export as Word with full EN 301 549 clause mapping."},"exportPanel":{"toolName":"VPAT® / ACR Editor","summary":{"withProduct":"VPAT for {productName}{version}, {count} criteria evaluated","noProduct":"Add product name above to enable export"},"labels":{"criteriaEvaluated":"Criteria evaluated","supports":"Supports","partiallySupports":"Partially Supports","doesNotSupport":"Does Not Support","notApplicable":"Not Applicable","notEvaluated":"Not Evaluated","perceivableBreakdown":"Perceivable, Supports / Partial / Fails","operableBreakdown":"Operable, Supports / Partial / Fails","understandableBreakdown":"Understandable, Supports / Partial / Fails","robustBreakdown":"Robust, Supports / Partial / Fails","topNonConformant":"Top non-conformant criteria","topNonConformantNone":"None"},"exports":{"jsonLabel":"Download as JSON","jsonHint":"Full ACR data"},"docx":{"productInfoHeading":"Product information","productNameRow":"Product name","versionRow":"Version","vendorRow":"Vendor","reportDateRow":"Report date","productScopeRow":"Product scope","contactNameRow":"Contact name","contactEmailRow":"Contact email","evaluatedByRow":"Evaluated by","annexISectionRow":"EAA Annex I section","enVersionRow":"EN 301 549 version","notSet":"(not set)","vpatNotesHeading":"VPAT notes","conformanceSummaryHeading":"Conformance summary","totalWcagRow":"Total WCAG 2.2 criteria","perPrincipleHeading":"Per-principle breakdown (POUR)","perPrincipleHeaders":{"principle":"Principle","total":"Total","supports":"Supports","partial":"Partial","doesNot":"Does Not","na":"N/A","notEval":"Not Eval."},"doesNotSupportHeading":"Does Not Support, required remediation","doesNotSupportIntroSingular":"{count} criterion marked as Does Not Support. Each row shows the SC, level, principle and operator remarks.","doesNotSupportIntroPlural":"{count} criteria marked as Does Not Support. Each row shows the SC, level, principle and operator remarks.","partiallySupportsHeading":"Partially Supports","criteriaTableHeaders":{"sc":"SC","criterion":"Criterion","level":"Level","principle":"Principle","conformance":"Conformance","remarks":"Remarks"},"fullRegisterHeading":"WCAG 2.2 success criteria, full register ({count} criteria)","fullRegisterIntro":"Every WCAG 2.2 criterion in the VPAT 2.5 edition, with conformance level and remarks. Supports / Partially Supports / Does Not Support / Not Applicable / Not Evaluated are the standard VPAT conformance terms.","en301549Heading":"EN 301 549 non-WCAG clauses (5–7, 12–13)","en301549Intro":"EN 301 549 clauses beyond the WCAG-mapped Clause 9/11 that have been assessed.","en301549Headers":{"clause":"Clause","conformance":"Conformance","remarks":"Remarks"},"disabilityHeading":"Test user disability profiles","supplyChainHeading":"Third-party / supply-chain components","supplyChainHeaders":{"component":"Component","vendor":"Vendor","vpatRequested":"VPAT requested","vpatReceived":"VPAT received","contractualRef":"Contractual ref"},"yes":"Yes","no":"No","exclusionsHeading":"Third-party exclusions","exclusionsHeaders":{"component":"Component","vendor":"Vendor","reason":"Reason for exclusion","vendorAcrExpected":"Vendor ACR expected"},"methodHeading":"Method","methodBody":"Voluntary Product Accessibility Template (VPAT®) 2.5, WCAG 2.2 Edition. Each of the {count} WCAG 2.2 success criteria is assigned a standard conformance term (Supports / Partially Supports / Does Not Support / Not Applicable / Not Evaluated) with operator remarks. Evaluation conducted against EN 301 549 {standard}. VPAT® is a registered service mark of the Information Technology Industry Council (ITI). This Accessibility Conformance Report (ACR) supports EAA Article 13 Technical Documentation, EAA Annex IV §6, and US Section 508 / EN 301 549 procurement requirements."}}},"components":{"evidence-attach-uploader":{"findingIdPlaceholder":"Finding id (from your report)","dropZoneAria":"Drag a file or click to pick. Accepts image, video, or audio up to 50 MB.","uploading":"Uploading,","dropTitle":"Drop a screenshot, video, or AT recording","dropHint":"or click to pick (max 50 MB)","success":"✓ Attached. Evidence quality for <code>{findingId}</code> is now <strong>{quality}/3</strong>.","errors":{"needFindingId":"Enter the finding id (visible in your report) before attaching.","invalidFindingId":"Finding id can only contain letters, digits, '.', ':', '_', '-'.","fileTooLarge":"File too large (50 MB cap).","wrongType":"Only image, video, or audio files are accepted.","needSignIn":"Please sign in (Pro) to attach evidence.","uploadFailedStatus":"Upload failed (HTTP {status}).","uploadFailedFallback":"Upload failed."}},"gaad-2026-promo":{"logo_alt":"GAAD logo","locked_prefix":"Coming Thursday 21 May:","locked_title":"State of Portuguese Digital Accessibility 2026","locked_countdown_label":"In","live_prefix":"Just published:","live_title":"State of Portuguese Digital Accessibility 2026","cta":"Read the report","cta_locked":"Preview","dismiss_aria":"Dismiss GAAD 2026 promo"},"sample-preview":{"heading":"Sample output","buttonLabel":"Download sample {toolName} output","trialCta":"Start free trial"},"technical-file-completeness":{"heading":"Annex IV Technical File Completeness","allPresent":"All required documents present","missingCount":"{count, plural, one {# required document missing} other {# required documents missing}}","requiredHeading":"Required for EAA Annex IV","recommendedHeading":"Recommended","openTool":"Open tool →","documents":{"contrast":{"label":"Colour Contrast Test","why":"WCAG SC 1.4.3 / 1.4.11, required for all visual content"},"headings":{"label":"Heading Structure Audit","why":"WCAG SC 1.3.1 / 2.4.6, document structure for screen readers"},"focus":{"label":"Keyboard / Focus Order Test","why":"WCAG SC 2.1.1 / 2.4.3, all functionality must be keyboard-operable"},"alt-text":{"label":"Image Alternative Text Audit","why":"WCAG SC 1.1.1, all non-text content needs text alternatives"},"readability":{"label":"Readability / Reading Level Check","why":"WCAG SC 3.1.5, content must not exceed lower secondary reading level"},"sector-checklist":{"label":"Sector-Specific Checklist","why":"EAA Annex I, sector requirements (banking, e-commerce, transport, etc.)"},"statement":{"label":"Accessibility Statement","why":"EAA Article 14, public accessibility statement is a legal requirement"},"conformity":{"label":"EU Declaration of Conformity","why":"EAA Article 16 / Annex IV, formal declaration document"},"screen-reader":{"label":"Assistive Technology / Screen Reader Test","why":"EN 301 549 §11.5, interoperability with assistive technology"},"compliance-report":{"label":"Bundled Compliance Report","why":"Annex IV, all evidence bundled into a single Technical File"},"vpat":{"label":"VPAT / Accessibility Conformance Report","why":"Procurement standard, expected by EU public sector buyers"}}},"trial-banner":{"lead":"🔓 Try all Pro tools free for 7 days","sub":"No credit card required","cta":"Start trial →","dismiss_aria":"Dismiss trial banner","region_label":"Free trial offer"}},"exports":{"docx":{"common":{"footerMethodology":"Findings produced by the AccessibilityRef Whole-Site Scanner.","noFindings":"No findings recorded for this section.","endOfDocument":"End of document.","page":"Page","of":"of","severity":{"critical":"Critical","serious":"Serious","major":"Major","moderate":"Moderate","minor":"Minor"},"table":{"url":"Page URL","issue":"Issue","wcag":"WCAG","fix":"Suggested fix","criterion":"Criterion","conformance":"Conformance","remarks":"Remarks and Explanations","result":"Result","tool":"Tool","status":"Status","notes":"Notes","date":"Date"},"section":{"assessmentDetails":"Assessment Details","summary":"Summary","findings":"Findings","methodology":"Methodology","appendix":"Appendix","operatorNotes":"Operator Notes","assessmentScope":"Assessment Scope","testResultData":"Test Result Data","testUserDisabilityProfiles":"Test User Disability Profiles"},"fields":{"tool":"Tool","auditId":"Audit ID","generated":"Generated","expires":"Expires","annexIvSection":"Annex IV section","conformanceOutcome":"Conformance outcome","assessedBy":"Assessed by","testingPeriod":"Testing period","pagesSampled":"Pages sampled","included":"Included","excluded":"Excluded","technologyScope":"Technology scope","notAssessed":"Not Assessed"},"severityAdj":{"was":"was"}},"wholeSiteScanner":{"title":"Whole-Site Accessibility Report","sectionFindings":"Findings","sectionByPage":"Findings by page","sectionByTemplate":"Findings by template","sectionConsistency":"Statement vs scan consistency","sectionBotWalled":"Pages we could not scan"},"headingsPro":{"title":"Heading Structure Report"},"focusOrderPro":{"title":"Focus Order Report"},"statementValidator":{"title":"Accessibility Statement Validation Report"},"complianceReport":{"title":"Compliance Report"},"vpat":{"title":"Voluntary Product Accessibility Template (VPAT)","subtitle":"Accessibility Conformance Report","edition":"VPAT 2.5, WCAG 2.2 Edition","unnamedProduct":"Unnamed Product","productInformation":"Product Information","fields":{"productName":"Product Name","version":"Version","vendor":"Vendor","reportDate":"Report Date","contactName":"Contact Name","contactEmail":"Contact Email","evaluatedBy":"Evaluated By"},"notes":"Notes","conformanceLevelsUsed":"Conformance Levels Used","conformanceLevels":{"supports":"Supports","supportsDef":"The functionality of the product has at least one method that meets the criterion without known defects.","partiallySupports":"Partially Supports","partiallySupportsDef":"Some functionality of the product does not meet the criterion.","doesNotSupport":"Does Not Support","doesNotSupportDef":"The majority of product functionality does not meet the criterion.","notApplicable":"Not Applicable","notApplicableDef":"The criterion is not relevant to the product."},"successCriteriaHeading":"WCAG 2.2 Success Criteria","tableHeaders":{"criterion":"Criterion","level":"Level","conformance":"Conformance","remarks":"Remarks and Explanations"},"testUserDisabilityProfiles":"Test User Disability Profiles","disabilityProfilesIntro":"Disability groups represented in testing: {profiles}","en301549Heading":"EN 301 549 Non-WCAG Clauses (5-7, 12-13)","en301549Intro":"The following EN 301 549 clauses beyond the WCAG-mapped Clause 9/11 have been assessed:","en301549Headers":{"clause":"Clause","conformance":"Conformance","remarks":"Remarks"},"trademark":"VPAT® is a registered service mark of the Information Technology Industry Council (ITI). This report was generated using AccessibilityRef.com."},"conformityGenerator":{"title":"EU Declaration of Conformity"},"contrastChecker":{"sectionResults":"Colour Contrast Results","foreground":"Foreground colour","background":"Background colour","contrastRatio":"Contrast ratio","textContext":"Text context","criterion":"Criterion","result":"Result","wcagAaNormal":"WCAG AA, Normal text (4.5:1)","wcagAaLarge":"WCAG AA, Large text (3:1)","wcagAaUi":"WCAG AA, UI components (3:1)","wcagAaaNormal":"WCAG AAA, Normal text (7:1)","wcagAaaLarge":"WCAG AAA, Large text (4.5:1)","pass":"PASS","fail":"FAIL"},"readability":{"sectionOriginalAnalysis":"Original Text Analysis","sectionOriginalText":"Original Text","sectionSimplifiedAnalysis":"Simplified Text Analysis","sectionSimplifiedText":"Simplified Text","fleschKincaidGrade":"Flesch-Kincaid Grade","fleschReadingEase":"Reading Ease","gunningFog":"Gunning Fog Index","wordCount":"Word count","sentenceCount":"Sentence count","avgSentenceLength":"Avg sentence length","complexWords":"Complex words","words":"words"},"checklistChecklist":{"disclaimer":"This checklist is a reference tool and does not constitute legal advice. Consult a qualified auditor for formal compliance assessment."},"wcagChecklist":{"title":"WCAG 2.2 Audit Checklist","fallbackAuditName":"WCAG 2.2 Audit","exportedLine":"Exported: {date} · Tool: accessibilityref.eu","summary":"Summary","totalCriteria":"Total criteria","pass":"Pass","fail":"Fail","na":"N/A","pending":"Pending","progress":"Progress","criteriaShown":"Criteria ({count} shown)","headers":{"scId":"SC ID","criterionName":"Criterion Name","level":"Level","status":"Status","auditNotes":"Audit Notes"},"levelLabel":"Level {level}","generatedBy":"Generated by AccessibilityRef · accessibilityref.eu","disclaimer":"This checklist is a reference tool and does not constitute legal advice. Consult a qualified auditor for formal compliance assessment."},"branding":{"name":"AccessibilityRef","domain":"accessibilityref.eu","tagline":"Independent European platform for digital accessibility compliance self-assessment"},"footer":{"tagline":"Independent European platform for digital accessibility compliance self-assessment","legalGrade":"EAA · WCAG 2.2 · EN 301 549 V3.2.1, Legal-grade evidence, not legal advice"},"vaultPack":{"manifestTitle":"ANNEX IV TECHNICAL DOCUMENTATION","manifestSubtitle":"Directive (EU) 2019/882, European Accessibility Act","productSectionHeading":"Product / Service","buildNotesLabel":"Build notes: ","emptySection":"No evidence recorded for this section yet.","backingIndexTitle":"STATEMENT BACKING EVIDENCE INDEX","backingIndexSubtitle":"EAA Annex V claims → Technical-File evidence records (cross-deliverable linker).","missingAuditNote":" (audit id not found in current vault, record may have been deleted or belongs to a different account)","endOfBackingIndex":"End of backing index,","backingIndexHeading":"Statement Backing Evidence Index","endOfManifest":"End of manifest,"}}}},"now":"$undefined","timeZone":"UTC","children":["$L1e","$L1f","$L20"]}] </article></body></html>

3:["$","$L1d",null,{"formats":"$undefined","locale":"en","messages":{"nav":{"home":"Home","tools":"Tools","pricing":"Pricing","contact":"Contact","login":"Log In","sign_up":"Sign Up","account":"Account","all_tools":"All {toolCount} Tools","search_tools_label":"Search tools","search_tools_placeholder":"Search tools...","help_center":"Help Center","about":"About","team":"Team","my_team":"My Team","reference_library":"Reference Library","ref_wcag":"WCAG 2.2 Standards","ref_eaa_tracker":"EAA Law Tracker","ref_en301549":"EN 301 549","ref_roles":"Accessibility Roles","ref_verticals":"Industry Verticals","ref_glossary":"A–Z Glossary","ref_partners":"Partner Directory","tool_statement_wizard":"Statement Wizard","tool_burden_calculator":"Burden Calculator","tool_conformity_generator":"EU Declaration of Conformity Generator","tool_compliance_program":"Compliance Programme","tool_roi_calculator":"ROI Calculator","tool_compliance_report":"Compliance Report","tool_self_assessment":"Guided EAA Self-Assessment","dashboard":"Dashboard","all_tools_short":"All Tools","navigation":"Navigation","pro_tools":"Pro Tools","pro_bundle_price":"Starter €499, Pro €999","compliance_tools":"Compliance Tools","open_menu":"Open menu","close_menu":"Close menu","for_businesses":"For Businesses","for_developers":"For Developers","for_compliance":"For Compliance","for_education":"For Education","for_procurement":"For Procurement","blog":"Blog"},"header":{"tagline":"European Accessibility Compliance"},"chrome":{"skip_to_main":"Skip to main content","high_contrast":"High Contrast","standard_contrast":"Standard","site_utilities_label":"Site utilities and account","main_navigation_label":"Main Navigation","breadcrumb_label":"Breadcrumb","submit_search_label":"Submit search","pro_bundle_aria_label":"See AccessibilityRef pricing: Starter €499/yr and Pro €999/yr","pro_feature_locked":"{label}, Pro feature, upgrade to access","official_sync":"Official Sync:","official_sync_aria":"Data last synchronized with official sources on {date}","footer_navigation":"Footer navigation"},"breadcrumb_segments":{"tools":"Tools","eaa":"EAA","wcag":"WCAG 2.2","en-301-549":"EN 301 549","glossary":"Glossary","roles":"Accessibility Roles","verticals":"Industry Verticals","global":"Global","for-businesses":"For Businesses","for-developers":"For Developers","for-compliance":"For Compliance","for-education":"For Education","for-procurement":"For Procurement","audit":"Audit","trust-badge":"Trust Badge","pricing":"Pricing","contact":"Contact","login":"Log In","blog":"Blog","privacy":"Privacy","terms":"Terms","cookies":"Cookies","accessibility-statement":"Accessibility Statement","impressum":"Impressum","authorities":"Authorities","horizontal":"Horizontal","pro":"Pro","sc":"Success Criterion","account":"Account","dashboard":"Dashboard","partners":"Partner Directory","help":"Help Center","about":"About"},"tool_how_to":{"title":"How to use this tool","what_is_this":"What is this?","when_do_i_need_this":"When do I need this?","applies_to":"Applies to:"},"platform_guide":{"how_to_fix_on":"How to fix this on {platforms}"},"export_panel_formats":{"raw_data_json":"Raw data (.json)","spreadsheet_csv":"Spreadsheet (.csv)"},"footer":{"brand_description":"The independent European platform for digital accessibility compliance, tools, legislation, and standards.","pro_cta":"Pricing: Starter €499, Pro €999","who_its_for":"Who It's For","businesses":"Businesses","developers":"Developers","compliance_teams":"Compliance Teams","education":"Education","procurement":"Procurement","tools":"Tools","all_tools":"All Tools","contrast_checker":"Contrast Checker","fine_calculator":"Fine Calculator","statement_wizard":"Statement Wizard","compliance_report":"Compliance Report","pro_bundle":"Pricing","reference":"Reference","wcag":"WCAG 2.2","eaa":"EAA by Country","en301549":"EN 301 549","glossary":"A–Z Glossary","accessibility_statement":"Accessibility Statement","gaad_report":"State of Portuguese Digital Accessibility 2026","legal":"Legal","privacy":"Privacy Policy","terms":"Terms of Service","cookies":"Cookie Policy","cookie_settings":"Cookie Settings","copyright":"© {year} accessibilityref. All rights reserved.","impressum":"Impressum"},"disclaimer":{"ai_translation":""},"language_switcher":{"en":"English","fr":"Français","pt":"Português"},"account":{"language_preference":"Language Preference","language_en":"English","language_fr":"Français","language_pt":"Português"},"tools-index":{"meta":{"title":"{toolCount} Free & Pro EAA Self-Assessment Tools, WCAG 2.2 Compliance Checklist","description":"{toolCount} accessibility self-assessment tools for EAA and WCAG 2.2 compliance. Free contrast checker, heading analyser, audit checklist, fine calculator, transposition tracker, and compliance programme template. Pro tools for batch auditing, statement generation, and sector-specific checklists."},"header":{"eyebrow":"EAA Self-Assessment & Compliance Tools","title":"EAA Self-Assessment Tools & WCAG 2.2 Compliance Checklist","description":"{toolCount} free and professional self-assessment tools for European Accessibility Act compliance. Complete EAA Directive coverage, every article, every annex, every sector. WCAG 2.2 audit checklists, EN 301 549 conformance testing, accessibility statement generation, transposition tracking, and compliance programme templates.","forDevelopers":"For Developers","forCompliance":"For Compliance","forBusinesses":"For Businesses"},"badgeCta":{"eyebrow":"Self-Declaration","title":"Display your compliance level badge","description":"Display a WCAG AA or EAA Conformant badge on your website. Copy-paste HTML or Markdown.","button":"Get badge"},"sections":{"freeTools":"Free Tools","noLoginRequired":"No login required","proTools":"Pro Tools","proPrice":"€499/yr","proUnlockText":"Unlock all pro tools for €499/year. Cancel any time.","complianceTools":"Compliance & Business Tools","free":"Free","specialistTools":"Specialist Tools","sectorTools":"EAA Sector & Hardware Checklists","pro":"Pro","sectorDescription":"15 sector-specific checklists covering every article and annex of the EAA, hardware, terminals, mobile apps, telecoms, e-commerce, banking, transport, publishing, emergency services, supply chain obligations, and functional performance criteria. Complete EN 301 549 and EAA Directive coverage."},"actions":{"openTool":"Open tool","open":"Open","openChecklist":"Open checklist"},"unlockCta":{"title":"Unlock All Pro Tools","description":"Annual subscription, access all pro tools for €499/year. Cancel any time.","button":"Get Pro Access, €499/yr","pricingLink":"See full pricing","pricingPage":"Pricing page"},"bundleCta":{"title":"All Pro Tools, €499/year","description":"Batch auditing, palette generator, statement wizard, compliance report builder, screen reader simulator, component library, and more, annual subscription, cancel any time.","button":"See pro tools"},"filter":{"label":"Filter by standard or purpose","ariaLabel":"Filter tools by compliance standard","clear":"Clear","toolCount":"{count} tool","toolCountPlural":"{count} tools","noMatch":"No tools match this filter.","searchPlaceholder":"Search tools by name, tag, or description…","tags":{"New":"Just Launched","WCAG-2-2":"WCAG 2.2","EAA Directive":"EAA Directive","EN 301 549":"EN 301 549","Annex IV":"Annex IV / Technical File","Sector":"Sector Checklists","Free":"Free Tools","Procurement":"Procurement","Documents":"Documents & PDFs"},"tagDescriptions":{"New":"Tools released or significantly updated in the last 60 days.","WCAG-2-2":"Web Content Accessibility Guidelines, the technical standard for web and app accessibility","EAA Directive":"European Accessibility Act (Directive 2019/882), legal obligations for EU market products and services","EN 301 549":"The harmonised European standard, technical requirements referenced by the EAA","Annex IV":"Tools that generate or support documents required for your EAA Article 15 Technical File","Sector":"Product and service-type specific checklists, e-commerce, banking, transport, hardware, and more","Free":"No login or payment required","Procurement":"RFP templates, contract clauses, and VPAT tools for supplier and vendor management","Documents":"PDF/UA, Word document, and digital publishing accessibility tools"}},"workflowTracks":{"title":"Pick your workflow","lede":"Three common journeys through the toolkit. Use one as a starting recipe, every tool is independently usable.","cards":{"scan":{"eyebrow":"Scan a site","title":"Audit an existing website end-to-end"},"statement":{"eyebrow":"Write a statement","title":"Draft, validate, and publish an Annex V accessibility statement"},"posture":{"eyebrow":"Assess EAA posture","title":"Decide where you stand under the European Accessibility Act"}}},"sectorFilter":{"ariaLabel":"Filter sector checklists","allSectors":"All sectors","labels":{"Banking":"Banking & Finance","E-Commerce":"E-Commerce","Transport":"Transport & Travel","Publishing":"Publishing & E-Books","Media":"Video & Media","Telecoms":"Telecoms","Hardware":"Consumer Hardware","Software":"Software","Mobile":"Mobile Apps","ICT":"Generic ICT","Documents":"Documents","All Sectors":"Cross-Sector"}},"search":{"title":"Search Results","noResults":"No tools found for \"{query}\"","resultCount":"{count} tool matching \"{query}\"","resultCountPlural":"{count} tools matching \"{query}\"","tryDifferent":"Try a different search term, or browse all tools below.","clearSearch":"Clear search","clearSearchShowAll":"Clear search, show all tools"},"tools":{"site-scanner":{"title":"EAA Site Scanner","description":"Enter any URL and get an instant accessibility score. 27 automated checks plus Lighthouse second-opinion rendering, covering headings, images, landmarks, forms, links, ARIA, contrast, language tagging and input purpose, mapped to WCAG 2.2 and EN 301 549."},"statement-validator":{"title":"Annex V Statement Validator","description":"Paste any published accessibility-statement URL and verify it against the 14 mandatory elements of EAA Annex V, EN 301 549 §12.1.1 and Directive 2016/2102 Article 7."},"bookmarklet":{"title":"Live Page Bookmarklet","description":"Drag a single bookmarklet to your bookmarks bar and scan any rendered page, including authenticated and JavaScript-heavy sites the server-side scanner cannot see. Eight rendered-DOM checks, run inside your own browser."},"contrast-checker":{"title":"Colour Contrast Checker","description":"Verify AA/AAA compliance with real-time luminance calculation. Enter any two hex colours."},"aria-reference":{"title":"ARIA Role Reference","description":"Browse all 50+ ARIA roles, states, properties, keyboard interactions, and HTML equivalents."},"readability":{"title":"Readability Checker","description":"Analyse text complexity using Flesch-Kincaid scoring. Paste any content, get instant results."},"fine-calculator":{"title":"EAA Fine Calculator","description":"Estimate your maximum penalty under the European Accessibility Act for any single EU member state."},"headings":{"title":"Heading Structure Analyser","description":"Enter a URL and get a visual H1–H6 hierarchy tree. Spot skipped levels and missing H1s instantly."},"alt-text":{"title":"Alt Text Quality Checker","description":"Scan a single URL for missing, empty, or suspicious image alt attributes."},"focus-order":{"title":"Focus Order Visualiser","description":"Enter a URL to see all focusable elements in tab order. Flags missing accessible names and positive tabindex."},"checklist":{"title":"WCAG 2.2 Audit Checklist","description":"Browse all WCAG 2.2 Level A and AA success criteria with normative text. View-only reference, no login."},"colour-blindness":{"title":"Colour Blindness Simulator","description":"Upload any image and see how it appears to users with protanopia, deuteranopia, tritanopia, and achromatopsia. WCAG 1.4.1."},"metrics-dashboard":{"title":"Accessibility Metrics Dashboard","description":"Track accessibility scores across all your URLs over time. Run periodic scans, visualise trends, and catch regressions before they become compliance issues. Scan history syncs to the cloud for Pro and Teams users."},"contrast-palette":{"title":"Colour Contrast Palette Generator","description":"Enter your brand colour and get a full 9-step WCAG-compliant palette. Export as CSS variables, JSON, or Figma tokens."},"statement-wizard":{"title":"Accessibility Statement Generator","description":"Multi-step wizard generating EAA Annex V compliant statements. Multi-language output, branded HTML download."},"checklist-generator":{"title":"WCAG Audit Checklist Generator","description":"Interactive checklist with pass/fail/N/A per criterion, notes, regulation filter (EAA + ADA + 508), CSV export and print-to-PDF."},"fine-calculator-pro":{"title":"EAA Fine Calculator Pro","description":"Side-by-side penalty comparison across all 27 EU countries simultaneously. Multi-violation modeling."},"headings-pro":{"title":"Heading Structure Analyser Pro","description":"Batch analyse up to 50 URLs at once. Export full heading audit as CSV with issue flags per page."},"alt-text-pro":{"title":"Alt Text Quality Checker Pro","description":"Batch scan up to 20 URLs. Full CSV export with image src, alt text, status, and issue descriptions."},"focus-order-pro":{"title":"Focus Order Visualiser Pro","description":"Batch analyse up to 10 URLs. Export full tab order audit as CSV with accessible name and issue flags."},"compliance-report":{"title":"Compliance Report Builder","description":"Full audit report with cover page, findings table, remediation timeline. Print-to-PDF. Save and resume projects."},"aria-assistant":{"title":"ARIA Role Assistant","description":"Paste HTML and get AI-powered ARIA analysis. Issues linked to WCAG 2.2. Receive a corrected version of your code. Powered by Claude."},"document-auditor":{"title":"Document Accessibility Auditor","description":"Upload Word (.docx) or PDF files for an instant audit. Heading structure, alt text, language, table headers. Processed locally, files never leave your browser."},"competitor-benchmark":{"title":"Competitor Accessibility Benchmark","description":"Compare two websites side-by-side on heading structure and alt text coverage. Overall score with per-metric breakdown."},"readability-dashboard":{"title":"Readability Score Dashboard","description":"Batch score multiple URLs for Flesch-Kincaid readability. Identify pages too complex for your audience. CSV export. WCAG 3.1.5."},"screen-reader-simulator":{"title":"Screen Reader Simulator","description":"Paste HTML and hear what a screen reader announces. Flags missing names, empty headings, and broken ARIA. Includes text-to-speech playback."},"mobile-checker":{"title":"Mobile Accessibility Checker","description":"Upload a mobile screenshot to check touch target sizing (WCAG 2.5.8) and surface contrast. Processed locally, never uploaded."},"debt-calculator":{"title":"Accessibility Debt Calculator","description":"Turn audit findings into hours, cost, and timeline. Input issue counts by severity, hourly rate, and team capacity. Export CSV."},"component-library":{"title":"Accessible Component Library","description":"Copy-paste accessible code patterns for forms, navigation, modals, buttons, and more. Live previews with WCAG references."},"alt-text-prompter":{"title":"Alt Text Prompter","description":"AI-assisted alt text prompts for any image type. Get the right prompts to generate EAA-compliant image descriptions."},"vpat-editor":{"title":"VPAT® / ACR Editor","description":"Create and edit a Voluntary Product Accessibility Template (VPAT) for procurement submissions."},"rfp-generator":{"title":"Vendor Accessibility Checklist","description":"Pre-built accessibility questionnaire to send to vendors and suppliers, 28 evidence-based questions across 5 categories with evaluator guidance. Doubles as an accessibility RFP template."},"legal-pack":{"title":"Procurement Legal Pack","description":"Standard accessibility contract clauses for vendor agreements and MSAs. WCAG 2.2 and EAA-aligned. Copy-ready for legal review."},"provisional-assessment":{"title":"Whole-Site Scanner","description":"50-point self-assessment across WCAG 2.2 and EAA provisions. Weighted scoring. Provisional conformance result with issues list. Export as Word."},"self-assessment":{"title":"Guided EAA Self-Assessment","description":"Guided 30-point WCAG 2.2 / EAA self-assessment. Complete each section and export a compliance report. Teams: shared across your whole team."},"scoping-wizard":{"title":"Am I Affected? (EAA Scope Quiz)","description":"Answer 5 quick questions to find out if the European Accessibility Act applies to your business. Instant result, no login."},"eaa-ready-quiz":{"title":"EAA Ready Quiz","description":"20 questions to assess your organisation's current EAA compliance posture. Immediate scored results."},"conformity-generator":{"title":"EU Declaration of Conformity Generator","description":"Generate an EU Declaration of Conformity (EAA Annex IV) with the correct legal form and references."},"burden-calculator":{"title":"Disproportionate Burden Calculator","description":"Model an exemption claim under EAA Article 14. Calculate proportionality and generate supporting documentation."},"compliance-program":{"title":"Compliance Programme Template","description":"Generate a full organisational Accessibility Compliance Programme, governance, scope, document management, audit cycle, remediation SLAs, training plan, and supply chain policy. Export as Word."},"roi-calculator":{"title":"ROI Calculator","description":"Model the business case for accessibility: market expansion, legal risk mitigation, and reputational value."},"hardware-checklist":{"title":"Consumer Hardware Checklist","description":"EAA Annex I §I + EN 301 549 Chapter 8, physical controls, audio/visual output, accessibility features, connectors, hearing aid compatibility for smartphones, tablets, TVs, and e-readers."},"terminal-checklist":{"title":"Self-Service Terminal Checklist","description":"EN 301 549 Chapter 8 + EAA Annex I §II, ATMs, ticketing machines, kiosks. Physical reach, keypad, display, audio output, and interaction requirements."},"software-checklist":{"title":"Non-Web Software Checklist","description":"EN 301 549 Chapter 11, desktop and native applications. Platform accessibility API, keyboard navigation, screen reader compatibility, and installation accessibility."},"mobile-app-checklist":{"title":"Mobile App Checklist","description":"EN 301 549 Chapter 11 + WCAG 2.1 AA for native iOS/Android. Screen reader, gestures, touch targets, notifications, and authentication."},"generic-ict-checklist":{"title":"Generic ICT Requirements Checklist","description":"EN 301 549 Chapter 5, closed functionality, activation of accessibility features, biometrics, preservation of accessibility, operable parts."},"video-media-checklist":{"title":"Video & Media Checklist","description":"EN 301 549 Chapter 7 + WCAG 1.2, captioning, audio description, player controls, and media content requirements."},"voice-comms-checklist":{"title":"Voice & Video Calling Checklist","description":"EN 301 549 Chapter 6, real-time text (RTT), caller ID, audio bandwidth, video calling quality for sign language, and voice alternatives."},"support-docs-checklist":{"title":"Support & Documentation Checklist","description":"EN 301 549 Chapter 12, accessible product documentation, help desk accessibility, relay service compatibility, and complaint handling."},"ecommerce-checklist":{"title":"E-Commerce Accessibility Checklist","description":"EAA Annex I §IX, product browsing, cart & checkout, post-purchase, cookie consent. Full e-commerce journey coverage."},"banking-checklist":{"title":"Banking & Financial Services Checklist","description":"EAA Annex I §IV, core banking, authentication, financial calculators, secure messaging, branch/ATM accessibility."},"transport-checklist":{"title":"Transport & Booking Checklist","description":"EAA Annex I §II–III, journey search, seat selection, accessibility assistance, disruption alerts, boarding passes."},"ebook-checklist":{"title":"E-Book & Digital Publishing Checklist","description":"EAA Annex I §VIII, EPUB metadata, content structure, MathML, reflowable text, reading system compatibility, DRM and TTS."},"emergency-checklist":{"title":"Emergency Services Checklist","description":"EN 301 549 Chapter 13, emergency calling via voice, RTT, and total conversation. Location transmission and multi-modal access."},"supply-chain-checklist":{"title":"Supply Chain Compliance Checklist","description":"EAA Articles 7–12, manufacturer, importer, and distributor obligations. Documentation, CE marking, traceability, complaints register, and corrective action."},"functional-criteria-checklist":{"title":"Functional Performance Criteria Checklist","description":"EAA Annex I Section VII, 11 outcome-based fallback criteria. Usage without vision, hearing, speech, colour, fine motor control. Seizure prevention, cognition, and privacy."},"cognitive-checklist":{"title":"Cognitive Accessibility Checklist","description":"Assess cognitive accessibility beyond readability, interaction complexity, error recovery, predictable behaviour, cognitive load, and memory support. WCAG 2.2 + EAA Annex I Section VII."},"cefr-checker":{"title":"CEFR B2 Readability Compliance Checklist","description":"EAA Annex I Section IV(e), deep CEFR B2 validation for banking content. Vocabulary complexity, sentence structure, document organisation, and financial terminology beyond Flesch-Kincaid proxy."},"matterhorn-checklist":{"title":"Matterhorn Protocol, PDF/UA Checklist","description":"ISO 14289-1 PDF/UA-1 compliance via Matterhorn Protocol 1.1, tagged structure, reading order, alt text, table markup, metadata, and font embedding. Supplements the Document Auditor."},"banking-regulatory-crossref":{"title":"Banking Regulatory Cross-Reference","description":"EAA + PSD2 + Consumer Credit Directive + MiFID II + GDPR, accessibility obligations that overlap with the EAA for banking and financial services."},"multilingual-checklist":{"title":"Multilingual Accessibility Checklist","description":"Verify accessibility features work across all supported languages, screen reader pronunciation, language switching, translated alt/ARIA, RTL support, and locale-specific content."},"at-interop-checklist":{"title":"AT Interoperability Testing Checklist","description":"EN 301 549 §5.1 + §11.5, test beyond screen readers. Covers magnifiers, switch access, voice control, braille displays, hearing aids, and eye tracking."},"user-testing-log":{"title":"User Testing with Disabled Participants","description":"Plan, conduct, and document accessibility user testing. Participant recruitment, methodology, findings documentation, and remediation verification. Strengthens Article 15 technical file."},"badges":{"title":"Accessibility Badge Generator","description":"Self-Declaration. Get copy-paste HTML and Markdown badges, WCAG AA, EAA Conformant, In Progress, and more, to display on your website or README."},"touch-target-tester":{"title":"Touch Target Tester","description":"Validate that interactive elements meet the 44×44px minimum size required by WCAG 2.5.5."},"pdf-checklist":{"title":"PDF Accessibility Checklist","description":"Requirements specific to accessible PDF documents, separate from WCAG web requirements."},"biometric-matrix":{"title":"Biometric Matrix","description":"Compliance requirements for biometric data handling by jurisdiction, EU AI Act, GDPR, and EAA."},"transposition-tracker":{"title":"EAA Transposition Tracker","description":"Reference table of how each EU member state transposed Directive 2019/882, statute number, regulator, complaint URL, and maximum fine. Sources cited verbatim from official journals."},"contrast-suite":{"title":"Contrast Suite","description":"Three contrast tools in one: Contrast Checker (WCAG + APCA), Palette Generator, and Colour-Blindness Simulator. WCAG 2.2 SC 1.4.3 / 1.4.11."},"business-case":{"title":"Business Case Bundle","description":"Three Pro calculators in one workspace: 27-country fine comparison, audit-debt sizing (hours/cost/timeline), and accessibility ROI modelling. Replaces the standalone Fine Calculator Pro, Debt Calculator, and ROI Calculator."}},"selfAssessmentCta":{"eyebrow":"★ Most popular, start here","title":"Run your EAA Self-Assessment","description":"30-point guided assessment across WCAG 2.2 and EAA provisions. Auto-saves as you go, exports to a Word report. Pro account required.","button":"Start the assessment"}},"about":{"meta":{"title":"About AccessibilityRef, European Accessibility Compliance Platform","description":"Independent EAA compliance platform built for European businesses. Our methodology, data sources, and commitment to accessibility."},"hero":{"title":"About AccessibilityRef","subtitle":"The independent European platform for digital accessibility compliance"},"mission":{"heading":"Our Mission","body":"AccessibilityRef exists to make EAA compliance achievable for every European business, from sole traders to multinationals. We provide self-assessment tools, legal reference data, and compliance documentation so organisations can understand and meet their obligations without hiring expensive consultants."},"methodology":{"heading":"Data Sources & Methodology","intro":"All legal content is sourced from official publications and verified regularly.","sources":[{"name":"EUR-Lex, Directive (EU) 2019/882","desc":"The official text of the European Accessibility Act, including all 32 articles and 6 annexes."},{"name":"ETSI EN 301 549 V3.2.1 (2021)","desc":"The harmonised European standard for ICT accessibility, referenced by the EAA for technical requirements."},{"name":"W3C WCAG 2.2","desc":"Web Content Accessibility Guidelines, the global standard for digital accessibility, referenced by EN 301 549 Chapter 9."}],"process":"National transposition data is verified against each member state's official gazette. Country pages show the last verification date. WCAG criteria reference the W3C Recommendation directly."},"platform":{"heading":"What We Provide","items":[{"title":"{toolCount} Self-Assessment Tools","desc":"From WCAG checklists to sector-specific compliance tools, covering the full EAA scope."},{"title":"27 EU Country Profiles","desc":"National law, enforcement authority, penalty structure, and cure period for every EU member state."},{"title":"Legal-Grade Evidence","desc":"Every tool output includes audit ID, tool version, and generation timestamp for regulatory defensibility."},{"title":"Full Directive Text","desc":"All 32 articles and 6 annexes of Directive 2019/882, with plain-language summaries alongside verbatim legal text."}]},"disclaimer":{"heading":"Legal Disclaimer","body":"AccessibilityRef is a self-assessment aid. Content on this platform does not constitute legal advice. All assessment risk lies with the user. For binding legal guidance, consult a qualified accessibility lawyer in your jurisdiction."}},"accessibility-statement":{"meta":{"title":"Accessibility Statement, AccessibilityRef","description":"AccessibilityRef accessibility statement. Our commitment to WCAG 2.2 AA conformance, known limitations, and how to report accessibility issues on accessibilityref.eu."},"heading":"Accessibility Statement","subtitle":"Compliance commitment for accessibilityref.eu","commitment":{"heading":"Our Commitment","body":"Accessibilityref is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards."},"conformance":{"heading":"Conformance Status","p1":"The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.","p2":"accessibilityref.eu is conformant with WCAG 2.2 level AA. Conformant means that the content fully conforms to the accessibility standard with no exceptions."},"legal_framework":{"heading":"Legal Framework","intro":"Accessibilityref.eu is operated for users throughout the European Union. This statement declares conformance with the European directives that set the technical baseline, the harmonised standard they reference, and the national transpositions in every member state where we have mapped the operative law to the site's verbatim legal corpus. Each reference links to the official publisher.","eu_heading":"European Union, baseline","eu_directive_2019_882":"Directive (EU) 2019/882, European Accessibility Act","eu_directive_2016_2102":"Directive (EU) 2016/2102, Public Sector Accessibility Directive","eu_en_301_549":"EN 301 549 v3.2.1, Accessibility requirements for ICT products and services","ie_heading":"Ireland","ie_si_636_2023":"S.I. No. 636/2023, European Union (Accessibility Requirements of Products and Services) Regulations 2023","fr_heading":"France","fr_ordonnance_2023_859":"Ordonnance n° 2023-859 du 6 septembre 2023, dispositions d'enforcement (ARCOM, article 47-1 de la loi 2005-102)","fr_decret_2023_931":"Décret n° 2023-931 du 9 octobre 2023, transposition substantive (Code de la consommation, articles D. 412-49 à D. 412-62)","pt_heading":"Portugal","pt_decreto_lei_82_2022":"Decreto-Lei n.º 82/2022 de 6 de dezembro, transposição da Diretiva (UE) 2019/882","more_coming":"Additional member states (Germany, Spain, Italy, Netherlands, Belgium, Poland and the remainder of the 27) will be added as their operative transpositions are ingested. Until then, accessibilityref.eu relies on the EU-level directives above as the applicable legal baseline for visitors in those jurisdictions.","authorities_link_pre":"The full directory of national enforcement authorities (competent body, contact, and penalty framework) is maintained at","authorities_link_label":"/eaa/authorities","authorities_link_post":"."},"feedback":{"heading":"Feedback","intro":"We welcome your feedback on the accessibility of accessibilityref.eu. Please let us know if you encounter accessibility barriers:","contact_label":"Contact Form:","contact_link":"Submit a report","response":"We try to respond to feedback within 2 business days."},"compatibility":{"heading":"Compatibility with Browsers and Assistive Technology","intro":"Accessibilityref.eu is designed to be compatible with the following assistive technologies:","browsers":"Chrome, Firefox, and Safari on latest OS versions.","screen_readers":"NVDA, JAWS, and VoiceOver screen readers."},"specs":{"heading":"Technical Specifications","intro":"Accessibility of accessibilityref.eu relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:","list":["HTML","WAI-ARIA","CSS","JavaScript"]},"features":{"heading":"Accessibility Features","intro":"This website includes several features to help people with disabilities navigate and use our resources:","skip_nav":"Skip Navigation: A \"Skip to content\" link is available to keyboard users to bypass navigation menus.","high_contrast":"High Contrast Mode: A toggle is available in the top utility bar to switch to a high-contrast (black/white/yellow) interface.","landmarks":"Semantic Landmarks: Proper use of HTML5 landmarks (header, nav, main, footer) to assist screen reader users.","aria_live":"Aria-Live Updates: Real-time \"Official Sync\" updates are announced to assistive technology.","focus_order":"Logical Focus Order: Tab order follows the visual and semantic structure of the page."},"roadmap":{"heading":"Recent Remediation","intro":"A full WCAG 2.2 AA remediation was completed in April 2026, addressing the following across 87+ files:","phase1":{"title":"Visual & Contrast Fixes","desc":"Colour contrast ratios (1.4.3), non-text contrast (1.4.11), and text resize (1.4.4) resolved across all core pages."},"phase2":{"title":"Interaction & Structure Fixes","desc":"Focus visibility (2.4.7), form labels (1.3.1), heading hierarchy, and ARIA improvements applied site-wide."}},"limitations":{"heading":"Remaining Limitations","intro":"The following limitations are outside our direct control and are being monitored:","contrast":"Third-party Embedded Content: Widgets or embeds served by external providers may not fully conform; we limit their use and provide alternatives where possible.","interactivity":"Tool Interactivity: Some advanced diagnostic tools have complex keyboard interaction patterns that are under ongoing refinement.","pdf":"PDF Documents: Older downloadable templates may not be fully optimised for screen readers. We are progressively remediating these."},"enforcement":{"heading":"Enforcement Procedure","body":"If you encounter accessibility barriers on this platform, please contact us at support@accessibilityref.eu. We aim to respond within 5 business days. If you are not satisfied with our response, you may file a complaint with the national enforcement authority designated under your jurisdiction's transposition of Directive (EU) 2019/882, for Ireland this is the Competition and Consumer Protection Commission (CCPC); for France the Autorité de régulation de la communication audiovisuelle et numérique (ARCOM) for public-sector services and the Direction générale de la concurrence, de la consommation et de la répression des fraudes (DGCCRF) for products; for Portugal the Instituto Nacional para a Reabilitação, I.P. (INR, I.P.). A directory of all 27 member-state authorities is at /eaa/authorities."},"last_reviewed":"This statement was last reviewed on 17 April 2026."},"account-agency-profile":{"title":"Agency profile","intro":"Set your firm name, logo, and brand colour. Branding is applied automatically to every DOCX export and on the public partners directory when you opt in.","backToDashboard":"Back to dashboard","loading":"Loading","saving":"Saving...","save":"Save changes","cancel":"Cancel","saved":"Branding saved.","fields":{"firmName":"Firm name","logo":"Logo (PNG, JPG, or SVG, max 1 MB)","logoHint":"Public read access. Used in DOCX exports and on the partners page.","logoPreviewAlt":"Current agency logo","removeLogo":"Remove logo","uploading":"Uploading logo...","primaryColor":"Primary colour","primaryColorHint":"Applied to heading text in branded DOCX exports.","footerText":"Custom footer text","footerTextHint":"Replaces the default tagline on the last page of branded DOCX exports.","jurisdiction":"Primary jurisdiction","jurisdictionPlaceholder":"Select country","contactLegend":"Contact","contactEmail":"Contact email","contactPhone":"Contact phone","websiteUrl":"Website URL","publicListed":"List publicly on the partners page","publicListedHint":"Your firm name, logo, jurisdiction, and website appear on /partners.","showAttribution":"Include \"Powered by accessibilityref.eu\" on exports","showAttributionHint":"Recommended. Keeps a small attribution line at the bottom of branded deliverables."},"errors":{"firmNameRequired":"Firm name is required.","notAuthed":"You need to sign in again to save changes.","uploadFailed":"Logo upload failed.","saveFailed":"Could not save branding."}},"account-counsel":{"meta":{"title":"Counsel dashboard"},"headings":{"page":"My counsel dashboard","sharedProjects":"Projects shared with me","deliverables":"Deliverables"},"intro":{"lead":"Every legal project a Pro client has invited you to review appears here. Open any deliverable to inspect the latest snapshot and add a sign-off block.","noEdit":"Counsel access is read-only. You can attach sign-offs, but cannot edit project details or any deliverable's content."},"columns":{"deliverable":"Deliverable","status":"Status"},"status":{"awaiting":"Awaiting sign-off","signed":"Signed","superseded":"Superseded (project edited after sign-off)"},"deliverables":{"statement":"Accessibility statement","technical-file":"Annex IV technical file","conformity-declaration":"EU declaration of conformity","compliance-report":"Compliance report"},"labels":{"jurisdiction":"Jurisdiction","open":"Open","noProjects":"No projects have been shared with you yet. Ask the project owner to send you an invite link.","noDeliverables":"This project has no deliverables yet."},"states":{"loading":"Loading shared projects","needSignIn":"Sign in to view projects shared with you.","loadFailed":"Could not load shared projects. Refresh and try again."},"back":{"toDashboard":"Back to dashboard"},"dashboardLink":{"label":"Counsel dashboard"}},"account-invites":{"meta":{"title":"Accept counsel invite"},"headings":{"page":"Counsel invitation","signedOut":"Sign in to accept this invite","mismatch":"This invite is for a different account","ready":"You are about to accept this invite","accepted":"Invite accepted"},"intro":{"lead":"You have been invited to join a legal project as counsel. Once you accept, the project will appear in your Counsel Dashboard and you will be able to review every deliverable and add sign-off blocks.","noEdit":"Counsel access is read-only on project details. You cannot edit the project itself, only attach sign-offs to its deliverables."},"labels":{"accept":"Accept invite","accepting":"Accepting","signIn":"Sign in","signOut":"Sign out","goToCounsel":"Open the Counsel Dashboard","invitedAddress":"Invite is addressed to","signedInAs":"You are signed in as"},"errors":{"tokenMissing":"This invite link is missing its token. Ask the project owner to send a fresh link.","notFound":"This invite was not found. It may have already been used, or the link may be incorrect.","expired":"This invite has expired. Ask the project owner to send a new one.","alreadyAccepted":"This invite has already been accepted.","emailMismatch":"This invite is not addressed to the email on your account. Sign in with the matching address, or ask the owner to reissue the invite.","emailRequired":"Your account does not expose an email address, which is required to accept a counsel invite. Sign in with an email-based account.","acceptFailed":"Could not accept the invite. Try again, and if it keeps failing, contact support."},"states":{"loading":"Loading invite"}},"account-projects-share":{"meta":{"title":"Share project with counsel"},"headings":{"page":"Invite counsel","currentCollaborators":"Current collaborators","inviteForm":"Send a new invite"},"intro":{"lead":"Generate a single-use link that lets a lawyer or compliance reviewer attach themselves to this project as counsel. Counsel can view every deliverable and add sign-off blocks, but cannot edit project details.","expiry":"Invite links expire after 14 days and can only be used by the email address you enter below."},"labels":{"email":"Lawyer's email","emailPlaceholder":"lawyer@firm.example","submit":"Generate invite link","submitting":"Generating","copyLink":"Copy invite link","copied":"Copied","linkLabel":"Send this link to the invitee","role":"Role","roleCounsel":"Counsel","invitedAt":"Invited","acceptedAt":"Accepted"},"states":{"noCollaborators":"No counsel has been invited yet.","needSignIn":"Sign in to manage this project.","needPro":"Counsel sharing is a Pro feature.","notFound":"Project not found. It may have been deleted, or you may not be the owner.","loading":"Loading project"},"errors":{"invalidEmail":"Enter a valid email address.","saveFailed":"Could not generate the invite. Try again, and if it keeps failing, contact support.","copyFailed":"Could not copy automatically. Select and copy the link manually."},"back":{"toDashboard":"Back to dashboard"}},"auth":{"meta":{"title":"Log In, AccessibilityRef","description":"Sign in or create an AccessibilityRef account. Access Pro self-assessment tools, saved compliance reports, and EAA audit features."},"header":{"loginTitle":"Member Login","registerTitle":"Create Account","loginSubtitle":"Access your professional accessibility tools.","registerSubtitle":"Sign up with your email to access accessibility tools."},"form":{"fullNameLabel":"Full Name *","fullNamePlaceholder":"Jane Smith","companyLabel":"Company / Organisation *","companyPlaceholder":"Acme Ltd","phoneLabel":"Phone Number","phonePlaceholder":"+44 7700 900000","emailLabel":"Email Address *","emailPlaceholder":"Name@company.com","passwordLabel":"Password *","passwordPlaceholder":"••••••••","forgotPassword":"Forgot password?","resetSent":"Reset email sent, check your inbox.","submitLogin":"Sign In","submitRegister":"Create Free Account","consentDataProcessing":"I agree to the processing of my personal data in accordance with the Privacy Policy and Terms of Service. I understand my data will be stored securely and I can request its deletion at any time under GDPR. *","consentMarketing":"I agree to receive occasional product updates and accessibility news from AccessibilityRef. You can unsubscribe at any time."},"switch":{"haveAccount":"Already have an account?","noAccount":"New to accessibilityref?","switchToLogin":"Sign In","switchToRegister":"Register for Free"},"termsFooter":"By continuing, you agree to our Terms of Service and Privacy Policy.","loggedIn":{"welcomeBack":"Welcome Back!","accountLabel":"Account: {email}","proMember":"Pro Member","freeTier":"Free Tier","upgradeToPro":"Upgrade to Pro","signOut":"Sign Out"},"verify":{"title":"Verify your email","description":"We sent a verification link to {email}. Click the link to activate your account.","spamHint":"The email can take a minute to arrive. Check your spam folder if you don't see it.","verificationSent":"Verification email sent. Check your inbox.","tooManyRequests":"Too many requests. Wait a few minutes before resending.","couldNotSend":"Could not send the verification email. Please try again.","stillNotVerified":"Still not verified. Click the link in your email, then try again.","couldNotCheck":"Could not check status. Please try again.","checking":"Checking...","iVerified":"I've verified, continue","sending":"Sending...","resendVerification":"Resend verification email","signOut":"Sign out"},"errors":{"invalidCredentials":"Invalid email or password.","emailAlreadyInUse":"An account with this email already exists. Try signing in instead.","invalidEmail":"Please enter a valid email address.","weakPassword":"Password is too weak. Use at least 8 characters with a mix of letters and numbers.","missingPassword":"Please enter your password.","tooManyRequests":"Too many attempts. Please wait a few minutes and try again, or reset your password.","networkError":"Network error. Please check your connection and try again.","operationNotAllowed":"This sign-in method is currently disabled. Please contact support.","registerFailed":"Could not create account. Please try again.","throttled":"Too many attempts. Please wait a moment.","consentRequired":"You must agree to the data processing terms to create an account.","forgotNeedsEmail":"Enter your email address above, then click Forgot password.","forgotFailed":"Could not send reset email. Check the address and try again."}},"blog":{"meta":{"siteTitle":"Blog · AccessibilityRef"},"index":{"title":"Blog","subtitle":"News, insights, and guides on European accessibility law.","tabs":{"all":"All","news":"News","insight":"Insights","guide":"Guides"},"empty":"No posts yet.","readingTime":"{minutes} min read"},"post":{"by":"By","publishedOn":"Published {date}","updatedOn":"Updated {date}","relatedTitle":"Related reading","tocTitle":"In this guide","copyLink":"Copy link","copied":"Copied"},"preview":{"banner":"Draft preview, not indexed, do not share publicly."}},"case-studies":{"meta":{"title":"Case Studies","description":"Real-world examples of how businesses use the full AccessibilityRef ecosystem ({toolCount}+ tools) to achieve EAA compliance."},"hero":{"title_line1":"The Full Lifecycle:","title_line2":"{toolCount}+ Tools in Action","description":"EAA compliance isn't a single checkbox. It runs from strategy through to deployment, and the documentation lives for five years afterwards. See how the {toolCount}+ tools fit together across that lifecycle."},"workflow":{"0":{"phase":"1. Strategy & Risk","description":"Establishing the business case, identifying legal exposure across EU states, and setting the compliance budget."},"1":{"phase":"2. Design & Content","description":"Ensuring brand colours meet 4.5:1 ratios and all copy is written at or below a Grade 9 reading level."},"2":{"phase":"3. Technical Development","description":"Building semantic HTML, ensuring 24px/44px touch targets, and managing complex ARIA states."},"3":{"phase":"4. Sector-Specific Auditing","description":"Running deep-dives into industry-specific EAA requirements (e.g., Annex I Section X for Ecommerce)."},"4":{"phase":"5. Final Compliance","description":"Generating the legal 'Declaration of Conformity' and public accessibility statement required by the EAA."},"heading":"The Compliance Workflow"},"caseStudies":{"0":{"company":"EcoVibe","sector":"E-commerce (Home & Garden)","location":"Berlin, Germany","challenge":"Expanding to the EU-wide market while ensuring compliance with the German BFSG (Accessibility Reinforcement Act).","narrative":"EcoVibe started with the Fine Calculator to size their EAA exposure, then used the Heading Analyser to fix 142 structural issues and the Touch Target Tester to resize 24 navigation icons that were failing the 24px AA minimum. The Ecommerce Checklist paired with the ROI Calculator turned a legal requirement into a quantified growth case.","quote":"AccessibilityRef gave our developers exact pixel values and HTML fixes. We shipped a compliant checkout in weeks, not months."},"1":{"company":"GlobalFin Insurance","sector":"Financial Services","location":"Dublin, Ireland","challenge":"Simplifying complex insurance disclosure documents to meet WCAG 2.2 SC 3.1.5 (Reading Level) for EAA 'Understandable' requirements.","narrative":"GlobalFin used the Banking Checklist to test their portal against the financial sector EAA clauses. The ARIA Assistant fixed 14 custom data-grid widgets that were invisible to screen readers, and the PDF Checklist verified all policy downloads were correctly tagged.","quote":"The Banking Checklist mapped sector-specific obligations to concrete remediation tickets. Our developers stopped guessing at compliance scope."},"2":{"company":"TravelEase Airways","sector":"Transport (Aviation)","location":"Paris, France","challenge":"Managing multi-jurisdictional risk across 12 EU member states with varying penalty structures.","narrative":"TravelEase covered three surfaces: the web booking engine, the mobile app, and physical airport kiosks. The Transport Checklist handled sector-specific rules; the Terminal Checklist audited the check-in kiosks; the Mobile App Checklist took the boarding-pass flow to a 92/100 score with confirmed 44px touch targets.","quote":"Three different surfaces, one audit trail. The Multi-jurisdiction Fine Calculator made the budget case to the board on its own."},"coreToolsLabel":"Core Compliance Tools","technicalToolsLabel":"Technical Audit Tools","metricsLabel":"Tool-Verified Metrics","challengeLabel":"The Challenge","narrativeLabel":"Tool Integration Story","cta_tools":"Explore the full {toolCount}-tool toolkit →","cta_pricing":"View Pro Features"},"cta":{"title_line1":"Stop guessing.","title_line2":"Start complying.","description":"ROI modelling, ARIA debugging, technical-file generation, statement publishing. The toolkit covers every requirement of the European Accessibility Act.","primary":"Explore All {toolCount} Tools","secondary":"See pricing"}},"contact":{"meta":{"title":"Contact Us, AccessibilityRef","description":"Report an error, enquire about team subscriptions, explore sponsorship, or get in touch with the AccessibilityRef team."},"heading":"Contact Us","description":"Report an error, enquire about team subscriptions, explore sponsorship, or get in touch for any other reason.","reasons":{"compliance":{"label":"Compliance guidance","desc":"I need help understanding my EAA obligations","placeholder":"Tell us about your business, what you sell, where you operate, and what you need help with."},"enterprise":{"label":"Enterprise enquiry","desc":"Invoicing, DPA, multi-seat, or custom requirements","placeholder":"Describe your organisation, team size, and any procurement requirements (PO invoicing, DPA, SSO, etc.)."},"error":{"label":"Error on page","desc":"Found a bug, broken tool, outdated guidance, or incorrect WCAG information? Let us know so we can fix it.","placeholder":"Describe the error, include the page URL, what's incorrect, and what the correct information should be..."},"team":{"label":"Team subscription enquiry","desc":"Interested in the Teams plan for your organisation? Ask about pricing, onboarding, volume licensing, or custom requirements.","placeholder":"Tell us about your team, how many users, your organisation, and any questions about the Teams plan..."},"sponsorship":{"label":"Sponsorship / Partnership","desc":"Want to sponsor accessibilityref.eu or explore partnership opportunities to reach accessibility professionals across Europe?","placeholder":"Tell us about your organisation and what kind of sponsorship or partnership you're interested in..."},"other":{"label":"Other","desc":"Anything else, feedback, feature requests, accessibility issues with our own site, or general questions.","placeholder":"How can we help?"}},"form":{"name_label":"Full Name","email_label":"Email","reason_label":"Reason for Contact","message_label":"Message","submit":"Send Message","sending":"Sending...","error_fallback":"Something went wrong. Please try again."},"success":{"heading":"Message Sent","description":"We'll get back to you within 1–2 business days.","send_another":"Send another message"}},"cookies":{"meta":{"title":"Cookie Policy","description":"Information about the cookies used by AccessibilityRef and how to manage them."},"heading":"Cookie Policy","last_updated":"Last updated: 9 April 2026","intro":"This policy explains what cookies we use on accessibilityref, why we use them, and how you can control them. We comply with the EU ePrivacy Directive and GDPR.","s1":{"heading":"What Are Cookies?","body":"Cookies are small text files placed on your device when you visit a website. They help websites remember your preferences and understand how you use the site. Some cookies are strictly necessary for the site to function; others are optional and only set with your consent."},"s2":{"heading":"Cookies We Use","col_cookie":"Cookie","col_provider":"Provider","col_purpose":"Purpose","col_type":"Type","col_expiry":"Expiry","cookie1":{"name":"Cookie_consent","provider":"Accessibilityref","purpose":"Stores your cookie consent preference (accepted/rejected). Essential for remembering your choice.","type":"Essential","expiry":"12 months (auto-expires)"},"cookie2":{"name":"Firebase Auth cookies","provider":"Google LLC (Firebase)","purpose":"Maintains your logged-in session. Required for account access and Pro tool authentication.","type":"Essential","expiry":"Session / 1 year"},"cookie3":{"name":"_ga, _gid","provider":"Google Analytics (Firebase)","purpose":"Tracks page views and usage patterns to help us improve the site. Only set with your consent.","type":"Analytics","expiry":"Up to 2 years"},"cookie4":{"name":"Stripe cookies","provider":"Stripe Inc.","purpose":"Fraud prevention and secure payment processing. Only active during checkout.","type":"Essential","expiry":"Session"},"cookie5":{"name":"Zoho SalesIQ chat cookies (_zcsr_tmp, _zldp, _zldt, zsiq*)","provider":"Zoho Corporation B.V. (EU)","purpose":"Powers the in-page support chat widget on salesiq.zoho.eu. Maintains chat session state, identifies returning visitors, and routes conversations to the support agent. Only loaded with your consent.","type":"Marketing","expiry":"Session to 2 years"}},"s3":{"heading":"Your Consent Choices","intro":"When you first visit the site, a cookie banner gives you the following options:","accept_all":"Accept All","accept_all_desc":"Essential and analytics cookies are enabled.","essential_only":"Essential Only","essential_only_desc":"Only strictly necessary cookies are set. Analytics cookies are blocked.","change_preference":"You can change your preference at any time using the button below. Your consent is valid for 12 months, after which you will be asked again."},"s4":{"heading":"Google Consent Mode v2","body":"We use Google Consent Mode v2 to signal your consent choice directly to Google Analytics. When you choose \"Essential Only\", Google receives a signal that consent has been denied and will not use your data for measurement."},"s5":{"heading":"Managing Cookies in Your Browser","body":"You can control cookies through your browser settings. Note that blocking essential cookies will prevent some features (such as staying logged in) from working correctly.","chrome":"Google Chrome","firefox":"Mozilla Firefox","safari":"Apple Safari","edge":"Microsoft Edge"},"s6":{"heading":"Legal Basis","body":"Essential cookies are set under the \"strictly necessary\" exemption in Article 5(3) of the ePrivacy Directive (2002/58/EC) and do not require consent. Analytics cookies are set only with your explicit consent under GDPR Article 6(1)(a)."},"s7":{"heading":"Local Storage","body":"In addition to cookies, we use browser localStorage to store your authentication session token (Firebase) and tool preferences (such as saved wizard progress and checklist answers). This data remains on your device and is not transmitted to our servers unless required for authentication. You can clear localStorage via your browser's developer tools or site settings."},"s8":{"heading":"Contact","body":"For questions about cookies or data storage on this site, please use our contact form or refer to the Privacy Policy."},"related":{"heading":"Related Policies","privacy":"Privacy Policy","terms":"Terms of Service","contact":"Contact Us"}},"eaa":{"meta":{"title":"EAA Law Tracker, European Accessibility Act by Country","description":"Track EAA national transpositions, enforcement authorities, and penalty frameworks for all 27 EU member states. Updated reference for European Accessibility Act compliance self-assessment."},"hub":{"title":"European Accessibility Act 2025 Compliance Hub","description":"Monitoring the enforcement of Directive (EU) 2019/882 across all 27 Member States before the June 28, 2025 deadline."},"scoping":{"label":"Free Tool, 60 Seconds","heading":"Not sure if the EAA applies to your business?","body":"Answer 5 quick questions to find out whether you are in scope, exempt, or unaffected.","cta":"Check now"},"overview":{"heading":"EAA Compliance Overview","paragraph1":"The European Accessibility Act (EAA), formally EU Directive 2019/882, mandates that key digital products and services must meet accessibility requirements by the June 28, 2025 deadline. This law applies to private companies operating within the EU, focusing on e-commerce, banking, transport, and telecommunications.","paragraph2":"To achieve compliance, websites and apps must align with the EN 301 549 accessibility standards, which directly reference WCAG 2.1 Level AA. Failure to comply can result in significant EAA penalties and fines, which vary by Member State. While micro-enterprise exemptions exist for certain services, most digital providers must publish a formal Accessibility Statement to document their conformance."},"penalties":{"heading":"EAA Penalties and Fines by Country","highest_cap":"Highest Cap","revenue_based":"Revenue Based","standard_cap":"Standard Cap"},"table":{"caption":"EAA Transposition status across EU Member States","country":"Country","national_law":"National Law","enforcement_authority":"Enforcement Authority","status":"Status","action":"Action","status_transposed":"Transposed","tbc":"TBC","view_details":"View Details"},"country":{"title":"{name}: Accessibility Law","compliance_summary":"Compliance Summary","enforcement_body":"Enforcement Body","penalty_structure":"Penalty Structure","authority_discretion":"Authority Discretion","up_to":"Up to","compliance_deadline":"Compliance Deadline","cure_period":"Cure Period","verbatim_law":"Verbatim Law Details","key_articles":"Key Articles","sectors_in_scope":"Sectors in Scope","exemptions":"Exemptions","compliance_notes":"Compliance Notes","official_directive_label":"EU EAA Directive 2019/882","national_authority_label":"National Enforcement Authority","last_verified":"Last Verified: March 2026"},"authorities":{"meta_title":"EAA Enforcement Authorities, National Market Surveillance Directory","meta_title_full":"EAA Enforcement Authorities (Article 13 Directive 2019/882), National Directory","meta_description":"Directory of all 27 EU national enforcement authorities for the European Accessibility Act. Contact details, penalty frameworks, and compliance self-assessment guidance.","meta_description_full":"Under Article 13 of Directive (EU) 2019/882, each member state designates authorities for market surveillance, compliance checks, and complaint handling. Directory of all 27.","title":"National Authority Directory","description":"Official market surveillance and enforcement bodies for the EAA.","designated_authority":"Designated Authority","designation_in_progress":"Authority Designation in Progress"},"countries":{"AT":"Austria","BE":"Belgium","BG":"Bulgaria","CY":"Cyprus","CZ":"Czech Republic","DE":"Germany","DK":"Denmark","EE":"Estonia","ES":"Spain","FI":"Finland","FR":"France","GR":"Greece","HR":"Croatia","HU":"Hungary","IE":"Ireland","IT":"Italy","LT":"Lithuania","LU":"Luxembourg","LV":"Latvia","MT":"Malta","NL":"Netherlands","PL":"Poland","PT":"Portugal","RO":"Romania","SE":"Sweden","SI":"Slovenia","SK":"Slovakia"},"horizontal":{"key_requirements":"Key Requirements","assessment_criteria":"Assessment Criteria","exemption_thresholds":"Exemption Thresholds","enforcement_actions":"Actual Enforcement Actions","view_verbatim":"View Verbatim Text on EUR-Lex"}},"en301549":{"meta":{"title":"EN 301 549 Reference, Harmonised European Standard for EAA Compliance","description":"EN 301 549 V3.2.1 chapter-by-chapter reference with WCAG 2.1 mappings. Understand the requirements beyond WCAG for EAA compliance, non-web software, hardware, documents, and ICT accessibility self-assessment."},"hub":{"badge":"European Standard","title":"EN 301 549","description":"The harmonised European standard for ICT accessibility, V3.2.1. Mandated by the European Accessibility Act and the Web Accessibility Directive."},"what_is":{"heading":"What is EN 301 549?","body":"EN 301 549 is the European standard that defines technical accessibility requirements for ICT products and services, websites, mobile apps, software, hardware, and documents. It incorporates WCAG 2.1 Level AA by reference (Chapter 9 for web, Chapter 10 for documents, Chapter 11 for software) and adds requirements beyond WCAG for hardware and communication services.","current_version_label":"Current version","current_version_value":"V3.2.1 (2021)","next_version_label":"Next version","next_version_value":"V4.1.1 (in progress)","eaa_mandate_label":"EAA mandate","eaa_mandate_value":"Article 4 + Annex I"},"chapters":{"heading":"Chapters & Annexes","read_chapter":"Read chapter","chapter_4":{"title":"Chapter 4, Functional Performance Statements","desc":"9 statements covering vision, hearing, speech, cognition, and physical operation. Establishes the accessibility floor for all ICT."},"chapter_5":{"title":"Chapter 5, Generic Requirements","desc":"Closed functionality, biometric requirements, privacy, and cognitive requirements that apply across all ICT product types."},"chapter_8":{"title":"Chapter 8, Hardware","desc":"Physical ICT requirements including operable parts, display size, keypad layouts, and tactile indicators."},"chapter_10":{"title":"Chapter 10, Non-web Documents","desc":"Accessibility requirements for documents (PDF, Office) that are not web pages but are distributed electronically."},"chapter_11":{"title":"Chapter 11, Software","desc":"Requirements for software with a user interface, includes user preferences, assistive technology interoperability, and authoring tools."},"chapter_12":{"title":"Chapter 12, ICT with Communication","desc":"Real-time text, voice telephony relay services, video communication, and captioning requirements."},"annex_c":{"title":"Annex C, Determination of Conformity","desc":"Normative test methodology. Maps each requirement to a specific test procedure. Required for formal conformity assessment."},"v4_tracker":{"title":"V3.2.1 → V4.1.1 Evolution Tracker","desc":"Key changes between the current standard and the upcoming V4.1.1 revision. Understand what's changing and when."},"en_17161":{"title":"EN 17161, Design for All","desc":"The companion standard for accessible procurement and design-for-all methodology. Relevant for public sector buyers."}},"wcag_rel":{"heading":"Relationship to WCAG","chapter_9":"Chapter 9","chapter_9_title":"Web content","chapter_9_wcag":"WCAG 2.1 AA (by reference)","chapter_10":"Chapter 10","chapter_10_title":"Non-web documents","chapter_10_wcag":"WCAG 2.1 AA adapted","chapter_11":"Chapter 11","chapter_11_title":"Software UI","chapter_11_wcag":"WCAG 2.1 AA adapted","body":"Meeting WCAG 2.1 Level AA satisfies Chapter 9 of EN 301 549. However, the full standard also covers hardware, communication services, and documents, areas WCAG does not address.","view_wcag":"View full WCAG 2.2 reference"},"download_label":"Download EN 301 549 V3.2.1 PDF (ETSI)","detail":{"clause_prefix":"Clause","section_prefix":"Section","normative_test_mapping":"Normative Test Mapping","mapping_wcag_sc":"WCAG SC","mapping_test_id":"Annex C Test ID","mapping_requirement":"Requirement","evolution_heading":"V3.2.1 → V4.1.1 Evolution","current_label":"Current (V3.2.1)","next_label":"Next (V4.1.1)","impact_label":"Impact","download_label":"Download EN 301 549 V3.2.1 PDF"}},"evidence-vault":{"proGate":{"features":{"archive":"Full evidence archive","filtering":"Date range filtering","wordExport":"Word export for Annex IV Technical File"}},"header":{"backToDashboard":"← Dashboard","title":"Evidence Vault","intro":"5-year archive of all accessibility audit evidence generated under your account. Filter by date range and export to Word for your Annex IV Technical File.","refresh":"Refresh ↻"},"stats":{"records":"Records","toolsUsed":"Tools used","downloadableFiles":"Downloadable files"},"filters":{"heading":"Filter Records","fromDate":"From date","toDate":"To date","search":"Search","searchPlaceholder":"Tool name, Annex IV section, notes, audit ID,","clear":"✕ Clear filters"},"chain":{"heading":"Tamper-Evident Chain","description":"Each evidence record is hash-linked to the one before it. Verify walks every record and re-derives the chain. If any record has been silently edited since it was written, the chain breaks at that record and you will see the audit ID.","verifyButton":"Verify chain","verifyingButton":"Verifying,","verified":"{count, plural, one {Chain verified across # record.} other {Chain verified across # records.}}","legacySkipped":"{count, plural, one {# pre-chain record skipped (written before chain rollout).} other {# pre-chain records skipped (written before chain rollout).}}","headHash":"Head: {hash}","broken":"Chain broken.","firstBroken":"First broken record: {auditId}","verifiedBeforeBreak":"Verified {verified} of {total} records before the break. Contact support, this should never happen in normal operation.","verifyFailedFallback":"Verify failed"},"actionBar":{"recordsInView":"{count, plural, one {# record in view} other {# records in view}}","rangeSuffix":"({from} → {to})","rangeStart":"start","rangePresent":"present","selectedForReport":"{count, plural, one {# selected for compliance report} other {# selected for compliance report}}","addToReport":"Add {count} to Compliance Report →","exportAll":"⬇ Export all to Word (.docx)","exportSelected":"⬇ Export {count} selected (.docx)","exportBuilding":"Building,","exportFailedFallback":"Export failed"},"errors":{"signInToView":"Sign in to view your Evidence Vault.","loadFailed":"Failed to load Evidence Vault.","vaultApiResponded":"Vault API responded {status}","notAuthenticated":"Not authenticated","downloadFailedFallback":"Download failed","downloadFailedStatus":"Download failed ({status})","exportFailedFallback":"Export failed","diffFailedFallback":"Diff failed","diffFailedStatus":"Diff failed ({status})","benchmarkFailedFallback":"Benchmark failed","benchmarkFailedStatus":"Benchmark failed ({status})","benchmarkNoUrl":"Could not auto-extract the audit URL. The benchmark endpoint needs a scanned URL, re-run this audit with a fresh site-scanner pass to capture it.","benchmarkNoFailingChecks":"No failing checks in this audit match the Portugal EAA Index check enum, so there is nothing to benchmark.","benchmarkSignInExpired":"Sign in expired. Refresh and try again.","benchmarkAllFailed":"All benchmark requests failed. The Portugal EAA Index may not have peer data for this sector + check slice yet.","benchmarkEmptyParagraph":"Empty paragraph returned","benchmarkNoProject":"No active Legal Project. Create one in Tools, Project Picker before saving."},"loading":{"records":"Loading evidence records,"},"emptyVault":{"title":"No evidence yet","body":"Run any tool and use its Export as evidence panel while signed in. Your exports will appear here with a 5-year audit trail.","browseTools":"Browse Tools →"},"emptyFilters":{"title":"No records match your filters","clear":"Clear filters"},"table":{"selectAll":"Select all","columns":{"date":"Date","tool":"Tool","annexIv":"Annex IV §","standards":"Standards covered","outcome":"Outcome","testedBy":"Tested by","auditId":"Audit ID","expires":"Expires","download":"Download"},"moreCount":"+{count} more","assessmentTooltip":"Assessment: {tag}","outcome":{"notAssessed":"Not assessed","passes":"Passes","partiallySupports":"Partially Supports","doesNotSupport":"Does Not Support","notApplicable":"Not Applicable","notTested":"Not Tested"},"actions":{"compare":"↺ Compare","compareTitle":"AI-classify changes against the prior scan of the same URL","benchmark":"▲ Benchmark","benchmarkTitle":"Benchmark this audit's top failing checks against the Portugal EAA Index sector cohort","word":"⬇ Word","wordTitle":"Download evidence as Word (.docx)","attach":"+ Attach","attachClose":"✕ Close","attachTitle":"Attach a screenshot, video, or AT recording to a specific finding (lifts evidence quality score)","json":"JSON","jsonTitle":"Download raw output (JSON)","oversized":"Oversized","busy":"…"},"attachPanel":{"intro":"Attach supporting evidence to a specific finding in {auditPrefix}…. Paste the finding id from your downloaded report (or open the Word/JSON export to see ids), then drop one file. Allowed: image, video, audio up to 50 MB. This lifts the per-finding evidence quality score (0 to 3)."},"narrowFilter":"Showing {count} records. Use the date filter to narrow results."},"regression":{"title":"Regression Diff","titleWithTool":"Regression Diff, {tool}","subtitle":"AI-graded change report comparing this scan to the prior scan of the same URL.","close":"Close","closeAria":"Close diff","comparing":"Comparing audits with Claude Haiku,","currentAudit":"Current audit:","priorAudit":"Prior audit:","noFindings":"No findings to classify.","tableColumns":{"status":"Status","finding":"Finding","priorCurrent":"Prior → Current","reasoning":"Reasoning"},"classifications":{"fixed":"Fixed","new":"New","persisting":"Persisting","regressed":"Regressed","unclear":"Unclear"}},"benchmark":{"title":"Sector Peer Benchmark, {tool}","subtitle":"AI-graded comparison of this audit's top failing checks against the Portugal EAA Index sector cohort.","closeAria":"Close benchmark","sector":"Sector","url":"URL","loading":"Querying Portugal EAA Index cohort and asking Claude to write benchmark paragraphs,","peers":"{count} peers","source":"Source: Portugal EAA Index ({editionId})","sourceCurrent":"current","someFailed":"Some benchmark requests did not return:","failureLine":"{label}: {reason}","saved":"✓ Saved to active project, next DOCX export will include them.","activeProject":"Active project: {name}","noActiveProject":"No active Legal Project, create one before saving.","saveButton":"Save to next report","savedButton":"Saved","close":"Close"}},"export-evidence-panel":{"heading":"Export as evidence","lede":"Save this result as a legal-evidence record. Add operator notes if useful, they're stamped on the document footer.","proBadge":"★ Pro · Saved to Evidence Vault","freeBadge":"Free · Download only","anonBadge":"Anonymous · Download only","proStatus":{"pro":"Pro, saved automatically to your Evidence Vault.","freeSignedIn":"Free account, exports work, but the Evidence Vault history is Pro-only.","anonymous":"Not signed in, exports work but won't be stored. Sign in to keep a history."},"auditTagLabel":"Assessment name","auditTagHint":"(optional, groups records in the vault)","auditTagPlaceholder":"E.g. Globalbay Q2 2026 audit, NordBank v3.2.1 assessment","notesLabel":"Operator notes","notesHint":"(optional, max 2000 chars)","notesPlaceholder":"Add context: page tested, environment, scope, known exclusions, who performed the test, anything you'd want to remember in 5 years.","notesProAutoSave":"Sign in as Pro to auto-save notes","saveStatus":{"saving":"Saving…","saved":"✓ Saved to cloud","error":"⚠ Save failed, will retry on export"},"errorPrefix":"Export failed:","legalDetails":{"heading":"Legal Details","filledBadge":"Filled","expand":"Expand","hide":"Hide","intro":"Required for EAA Annex IV Technical Files. The conformance outcome, methodology, scope, and signatory are printed on every exported document and stored in the Evidence Vault.","conformanceLabel":"Overall conformance outcome","conformanceClause":"(EN 301 549 A.1.1)","outcomeNotAssessed":"Not Assessed, assessment not yet complete","outcomePasses":"Passes, fully conforms to all applicable criteria","outcomePartial":"Partially Supports, some criteria met, some not","outcomeDoesNot":"Does Not Support, does not meet applicable criteria","outcomeNA":"Not Applicable, criteria do not apply to this product/service","outcomeNotTested":"Not Tested, not yet evaluated","scopeHeading":"Assessment scope","scopeClause":"(EAA Article 13)","scopeVersionPlaceholder":"Product/service version: e.g. V2.4.1, commit a3f9b2d, release 2026-04-13","scopeIncludedPlaceholder":"Included: e.g. Www.example.com public pages","scopeExcludedPlaceholder":"Excluded: e.g. Admin panel, third-party widgets, PDF downloads","scopeTechPlaceholder":"Technology scope: e.g. Desktop web, mobile web (native apps not assessed)","methodologyHeading":"Testing methodology","methodologyClause":"(EN 301 549 §0.1)","methodologyToolsPlaceholder":"Automated tools: e.g. Axe DevTools v4.9, WAVE v5.1","methodologyBrowsersPlaceholder":"Browsers tested: e.g. Chrome 121, Firefox 122, Safari 17","methodologyATPlaceholder":"Assistive technologies: e.g. NVDA, VoiceOver, JAWS","methodologyDatesPlaceholder":"Testing period: e.g. 2026-04-01 to 2026-04-13","methodologySamplePlaceholder":"Pages / components sampled: e.g. 24","methodologyManualLabel":"Manual inspection","methodologyDisabledUsersLabel":"Tested with disabled users","methodologyLimitationsPlaceholder":"Known limitations: e.g. PDFs not assessed, third-party iframes excluded","signatoryHeading":"Signatory","signatoryClause":"(EAA Article 14)","signatoryNamePlaceholder":"Full name","signatoryRolePlaceholder":"Title / role","signatoryEmailPlaceholder":"Email"},"formats":{"downloadWord":"⬇ Download Word (.docx)","wordHint":"Legal-grade evidence document","saveToVault":"★ Save to Evidence Vault","saveToVaultSaving":"Saving to vault…"},"footer":{"legalBasis":"Legal basis:","everyExport":"Every export includes a legal-evidence metadata footer with the audit ID, generation date, tool version, EN 301 549 clauses, and the standard disclaimer. Legal-grade evidence, not legal advice."}},"for-agencies":{"meta":{"title":"EAA Compliance Tools for Digital Agencies, AccessibilityRef","description":"AccessibilityRef provides EAA compliance tools for digital agencies. Redirects to pricing for full Pro tool details."},"redirect":{"message":"This page redirects to the pricing page."}},"for-businesses":{"meta":{"title":"EAA Compliance Self-Assessment for Businesses, Free Tools & Audit Reports","description":"Is your website legally compliant with the European Accessibility Act? Free EAA self-assessment tools to calculate fine risk, test WCAG 2.2 compliance, and generate audit-ready documentation. Covering all 27 EU member states."},"hero":{"badge":"EAA Enforcement Live · For European Businesses","title_line1":"Is Your Website","title_line2":"Legally Compliant?","description":"The European Accessibility Act requires most commercial websites and apps to meet WCAG 2.1 AA standards. Non-compliance can result in fines of up to €22.5 million or 3% of global turnover.","cta_primary":"Calculate your fine risk, free","cta_secondary":"See pricing"},"law":{"heading":"What the EAA requires","description":"Directive (EU) 2019/882, the European Accessibility Act, applies to most private sector websites, mobile apps, e-commerce, banking, transport, and digital services sold to EU consumers. This includes SaaS companies, fintech startups, and software providers whose products are used in the EU.","items":{"0":"Websites and mobile apps must meet WCAG 2.1 AA","1":"A public accessibility statement must be published","2":"Users must be able to request accessible alternatives","3":"Complaints must be handled within a defined timeframe","4":"Non-compliance is enforced by national authorities"},"cta":"Read full EAA requirements by country →","penalty_label":"Penalty range","penalty_range":"€80k – €22.5M","penalty_description":"Fines vary by member state, company size, and number of violations. Austria caps at €80,000. Italy allows up to 5% of turnover. Use the calculator below to estimate your exposure.","penalty_cta":"Calculate your risk →"},"steps":{"0":{"number":"01","title":"Check your risk","body":"Use the free Fine Calculator to see your potential liability. Then take the EAA Ready Quiz to understand your current compliance level."},"1":{"number":"02","title":"Audit your website","body":"Use our free technical tools, contrast checker, heading analyser, alt text checker, to identify the most common issues on your site."},"2":{"number":"03","title":"Generate your Annex IV pack","body":"Produce a complete EAA Annex IV Technical File: Accessibility Statement, Declaration of Conformity, and compliance report, all using our pro tools."},"3":{"number":"04","title":"Retain for 5 years","body":"EAA Article 13 requires every covered business to keep technical documentation on file for at least 5 years. Pro accounts retain your full audit history automatically."},"heading":"How to comply in 4 steps"},"tools":{"0":{"title":"EAA Fine Calculator","desc":"Enter your country and revenue. Get your maximum potential fine under the European Accessibility Act."},"1":{"title":"EAA Ready Quiz","desc":"20 questions. Find out how prepared your organisation is for the June 28 deadline."},"2":{"title":"ROI Calculator","desc":"Model the business case: market expansion, legal risk reduction, and reputational value of compliance."},"3":{"title":"Statement Wizard","desc":"Generate a legally compliant EAA Annex V accessibility statement for your website. 7 languages supported."},"4":{"title":"Burden Calculator","desc":"Model the disproportionate burden exemption under EAA Article 14. Generate supporting documentation."},"5":{"title":"Compliance Report Builder","desc":"Generate the conformity assessment results section of your EAA Annex IV Technical File. Findings table, remediation timeline, responsible parties."},"heading":"Tools for your business","description":"Start with the free tools. Upgrade to Pro for documentation and reports.","open":"Open tool →","free":"Free","pro":"Pro"},"pro":{"heading":"Pro tools for compliance work","description":"Generate a Declaration of Conformity, accessibility statement, and compliance report. Run batch audits across your site. The documentation and evidence the EAA requires, in one place.","cta_primary":"See pricing","cta_secondary":"Take the readiness quiz, free"},"reference":{"0":{"title":"EAA by Country","desc":"Penalties, authorities, and deadlines for all 27 EU member states."},"1":{"title":"WCAG 2.2","desc":"The 87 technical success criteria your site must meet."},"2":{"title":"EN 301 549","desc":"The harmonised standard referenced in the EAA."},"heading":"Reference and legislation"}},"for-compliance":{"meta":{"title":"EAA Self-Assessment & Compliance Documentation Tools for Compliance Officers","description":"{toolCount} self-assessment tools covering every article and annex of the European Accessibility Act. Model fine risk across 27 EU states, generate accessibility statements, Declarations of Conformity, compliance programmes, and sector-specific audit checklists."},"hero":{"badge":"EAA Enforcement Live · For Compliance Officers","title_line1":"Prove Compliance.","title_line2":"Document","title_line3":"Everything.","description":"Generate the EAA Annex IV Technical File your organisation must keep on record for 5 years. Model fine risk across all 27 EU member states, produce Annex V Accessibility Statements, and export legal-grade audit reports for procurement and regulators.","cta_primary":"Build compliance report, Pro","cta_secondary":"Model fine risk, Pro"},"process":{"0":{"number":"01","title":"Assess current state","body":"Use the EAA Readiness Quiz and the WCAG 2.2 Audit Checklist to understand where your organisation stands against the harmonised standard EN 301 549."},"1":{"number":"02","title":"Calculate fine exposure","body":"Use the Fine Calculator Pro to model liability across all 27 EU member states with multi-violation scenarios. Useful for board-level risk reporting."},"2":{"number":"03","title":"Generate Annex V & Annex IV documentation","body":"Produce the Accessibility Statement (EAA Annex V), the Declaration of Conformity (EAA Annex IV), and a disproportionate burden assessment under Article 14 if applicable."},"3":{"number":"04","title":"Build the conformity assessment report","body":"Use the Compliance Report Builder to produce the conformity assessment results section of your Annex IV Technical File, findings, remediation timelines, EN 301 549 clause references, ready for regulators."},"4":{"number":"05","title":"Retain evidence for 5 years","body":"EAA Article 13 requires every covered business to keep technical documentation on file for at least 5 years. Pro accounts retain your full audit history automatically, no separate document management system needed."},"5":{"number":"06","title":"Maintain compliance","body":"Track ongoing conformance with the WCAG 2.2 checklist. Our data syncs daily with EUR-Lex so any national transposition changes show up immediately."},"heading":"Compliance process"},"tools":{"0":{"title":"EAA Fine Calculator Pro","desc":"Model liability across all 27 EU member states simultaneously. Multi-violation scenarios, PDF export."},"1":{"title":"Accessibility Statement Wizard","desc":"Generate a legally compliant EAA Annex V accessibility statement. 7 languages. Branded HTML download."},"2":{"title":"Declaration of Conformity","desc":"Generate a EU Declaration of Conformity (EAA Annex IV) with the correct legal form and references."},"3":{"title":"Disproportionate Burden Calculator","desc":"Model an exemption claim under EAA Article 14. Calculate proportionality and generate documentation."},"4":{"title":"WCAG Audit Checklist Generator","desc":"Interactive 87-criterion checklist with pass/fail/N/A tracking. Filter by EAA, ADA, or Section 508. CSV export."},"5":{"title":"Compliance Report Builder","desc":"Full audit report with cover, findings table, remediation timeline, and legislation references. Print to PDF."},"6":{"title":"Fine Calculator","desc":"Quick estimate of maximum EAA penalty for any single EU member state. Free, no login required."},"7":{"title":"EAA Readiness Quiz","desc":"20 questions to assess your organisation's current compliance posture. Immediate scored feedback."},"heading":"Compliance tools","open":"Open tool →","free":"Free","pro":"Pro"},"docs":{"0":{"item":"Accessibility Statement (Annex V)","tool":"Statement Wizard"},"1":{"item":"Declaration of Conformity (Annex IV)","tool":"EU Declaration of Conformity Generator"},"2":{"item":"Disproportionate Burden Assessment","tool":"Burden Calculator"},"3":{"item":"Audit Report with remediation plan","tool":"Compliance Report"},"heading":"Required documentation under the EAA","reportBuilder":{"badge":"Pro Tools","title":"Compliance Report Builder","description":"Build a compliance report with cover page, findings table, remediation timeline, and legislation references. Export as PDF, Word, or Google Sheets, ready for procurement responses and regulatory submissions.","cta":"Open report builder →"}},"legislation":{"0":{"title":"EAA by Country","desc":"Directive (EU) 2019/882 national transpositions, enforcement authorities, and penalty caps for all 27 EU member states."},"1":{"title":"WCAG 2.2 Success Criteria","desc":"All 87 success criteria with verbatim W3C text and manual test scripts. The technical standard referenced by the EAA."},"2":{"title":"EN 301 549 Standard","desc":"The harmonised European technical standard that defines the specific requirements for ICT accessibility under the EAA."},"heading":"Legislation and standards"}},"for-developers":{"meta":{"title":"Free WCAG 2.2 Testing & Self-Assessment Tools for Developers","description":"Free developer tools for WCAG 2.2 and EAA compliance: contrast checker, heading analyser, alt text checker, focus order visualiser, ARIA reference, accessible component library, and self-assessment checklists. Built for catching accessibility issues while the code is still open in your editor."},"hero":{"badge":"Developer Tools","title_line1":"Catch accessibility issues","title_line2":"while the code is still","title_line3":"open in your editor.","description":"Free tools for contrast, headings, alt text, focus order, ARIA roles, and more. All built against WCAG 2.2 and the European Accessibility Act.","cta_primary":"Explore all tools","cta_secondary":"WCAG 2.2 reference"},"freeTools":{"0":{"title":"Colour Contrast Checker","desc":"Real-time WCAG AA and AAA luminance calculation. Enter any two hex colours. Instant pass/fail."},"1":{"title":"Heading Structure Analyser","desc":"Enter a URL. Get a visual H1–H6 hierarchy tree with flags for skipped levels and missing H1s."},"2":{"title":"Alt Text Quality Checker","desc":"Scan a page for missing, empty, or suspicious alt attributes on images."},"3":{"title":"Focus Order Visualiser","desc":"See all focusable elements in tab order. Flags missing accessible names and positive tabindex."},"4":{"title":"ARIA Role Reference","desc":"Browse all 50+ ARIA roles with states, properties, keyboard interactions, and HTML equivalents."},"5":{"title":"Touch Target Tester","desc":"Validate that interactive elements meet the 44x44px minimum (WCAG 2.5.5)."},"6":{"title":"Readability Checker","desc":"Flesch-Kincaid scoring for content complexity. Paste any text, get instant grade-level results."},"7":{"title":"Alt Text Prompter","desc":"AI-assisted alt text suggestions. Upload an image and get a WCAG-quality description draft."},"heading":"Free tools","badge":"No login required","open":"Open tool →"},"resources":{"sr_heading":"Developer resources","componentLibrary":{"label":"Reference","title":"Accessible Component Library","description":"Copy-paste accessible patterns for forms, navigation, modals, and more, all keyboard and screen reader tested.","cta":"Browse components →"},"checklist":{"label":"Checklist","title":"WCAG 2.2 Audit Checklist","description":"All WCAG 2.2 Level A and AA success criteria with normative text, all EAA-mandatory criteria. Use as a developer reference during implementation or code review. Every check maps to its EN 301 549 clause so the output can drop straight into your team's Annex IV Technical File.","cta":"Open checklist →"}},"proTools":{"0":{"title":"Colour Contrast Palette Generator","desc":"Enter your brand colour. Get a full 9-step WCAG-compliant palette. Export as CSS, JSON, or Figma tokens."},"1":{"title":"Heading Analyser Pro","desc":"Batch analyse up to 50 URLs at once. Full CSV report with issue flags per page."},"2":{"title":"Alt Text Checker Pro","desc":"Batch scan up to 20 URLs. CSV export with image src, alt text, status, and issue descriptions."},"3":{"title":"Focus Order Visualiser Pro","desc":"Batch analyse up to 10 URLs. Export full tab order audit with accessible name and issue flags."},"heading":"Pro tools for teams","badge":"Starter €499, Pro €999","description":"Batch audit multiple URLs at once, export CSVs, and generate WCAG-compliant colour palettes for design handoff.","label":"Pro","open":"Open tool →","pricing":{"heading":"All Pro tools","description":"Annual subscription. Cancel any time.","cta":"See full pricing →"}},"wcag":{"heading":"Most referenced WCAG criteria","viewAll":"View all 87 WCAG 2.2 success criteria →"}},"for-education":{"meta":{"title":"Accessible Digital Learning, WCAG 2.2 & EAA Tools for Education","description":"WCAG 2.2 and EAA compliance tools for universities, schools, and educational platforms. Audit student portals, LMS, PDFs, lecture recordings, and more."},"hero":{"badge":"For Education · Universities, Schools & EdTech","title_line1":"Accessible Digital","title_line2":"Learning for Every Student","description":"The European Accessibility Act and WCAG 2.2 apply to student portals, learning management systems, and digital course materials. Start with a free audit, no account required.","cta_primary":"Start with the free WCAG Checklist","cta_secondary":"See pricing"},"challenges":{"heading":"Common challenges in education","description":"Educational institutions have their own accessibility requirements: screen-reader-compatible LMS interfaces, captioned lecture recordings, accessible PDF handouts.","items":{"0":"Student portal and VLE accessibility (keyboard navigation, screen reader support)","1":"LMS compliance, Moodle, Canvas, Blackboard, and custom platforms","2":"PDF and document accessibility, course handouts, syllabi, reading lists","3":"Lecture recording and video accessibility, captions, transcripts, audio descriptions","4":"Neurodiverse learner support, readability, cognitive load, plain language"},"cta":"Read the EAA requirements →"},"tools":{"0":{"title":"WCAG 2.2 Audit Checklist","desc":"Work through all 87 WCAG 2.2 success criteria. Ideal for auditing student portals, VLEs, and institutional websites."},"1":{"title":"PDF Accessibility Checklist","desc":"Verify course handouts, syllabi, and reading materials meet WCAG PDF/UA requirements."},"2":{"title":"Document Auditor","desc":"Check Word and PDF documents for accessibility issues before publishing to your LMS."},"3":{"title":"Readability Checker","desc":"Measure reading level and plain-language compliance. Essential for neurodiverse learner support."},"4":{"title":"Cognitive Accessibility Checklist","desc":"Evaluate cognitive load, plain language, error handling, and memory demands across learning interfaces."},"5":{"title":"Focus Order Checker","desc":"Verify keyboard navigation order through forms, menus, and interactive learning content."},"6":{"title":"Video & Media Checklist","desc":"Check lecture recordings, embedded videos, and podcasts for captions, transcripts, and audio descriptions."},"7":{"title":"Heading Structure Analyser","desc":"Inspect H1–H6 hierarchy on any institutional web page. Flags skipped levels and missing headings."},"heading":"Recommended tools for education","description":"Eight tools covering the full education accessibility audit workflow: WCAG testing, document review, cognitive load checks.","open":"Open tool →","free":"Free","pro":"Pro"},"pro":{"heading":"Pro tools for institutional compliance","description":"Generate audit-ready documentation, compliance reports, and accessibility statements for your institution. Pro accounts support batch auditing across multiple pages and portals.","cta_primary":"See pricing","cta_secondary":"Take the readiness quiz, free"},"reference":{"0":{"title":"WCAG 2.2 Standards","desc":"The 87 technical success criteria your student portals and digital content must meet."},"1":{"title":"EAA Law Tracker","desc":"Penalties, authorities, and deadlines for all 27 EU member states, including higher education obligations."},"2":{"title":"EN 301 549","desc":"The harmonised EU standard covering web, software, documents, and hardware used in education."},"heading":"Reference and legislation"}},"for-procurement":{"meta":{"title":"Accessible Procurement Requirements, EN 301 549, WCAG & EAA Tools","description":"Write enforceable accessibility requirements for RFPs and tenders. EN 301 549, WCAG 2.2, and EAA compliance tools for public and private sector procurement."},"hero":{"badge":"For Procurement · Public & Private Sector","title_line1":"Write Accessible","title_line2":"Procurement Requirements","description":"EN 301 549 and the European Accessibility Act set mandatory accessibility requirements for ICT products and services procured by public bodies. Generate compliant RFP language, vendor scorecards, and supply chain checklists.","cta_primary":"Start with the RFP Generator","cta_secondary":"See pricing"},"challenges":{"heading":"Common procurement challenges","description":"Procurement teams must translate legal obligations into enforceable contract language, and verify that vendors actually deliver what they claim.","items":{"0":"Writing accessibility requirements for RFPs, ITTs, and framework agreements","1":"Assessing vendor accessibility claims and VPAT / ACR documentation","2":"Referencing the correct EN 301 549 clauses for web, software, hardware, and documents","3":"Managing supply chain compliance across multiple vendors and platforms","4":"Documenting procurement decisions and accessibility evidence for audit trails"},"cta":"Read EN 301 549 requirements →"},"tools":{"0":{"title":"RFP Accessibility Requirements Generator","desc":"Generate ready-to-paste EN 301 549 and WCAG 2.2 accessibility clauses for RFPs, ITTs, and framework agreements."},"1":{"title":"VPAT / ACR Editor","desc":"Build and review Voluntary Product Accessibility Templates. Assess vendor ACR submissions against EN 301 549."},"2":{"title":"Supply Chain Accessibility Checklist","desc":"Audit third-party products and services against EAA and EN 301 549 supply chain obligations."},"3":{"title":"Checklist Generator","desc":"Create a bespoke EN 301 549 checklist for any product or service type in your procurement scope."},"4":{"title":"EN 301 549 Reference","desc":"Browse all EN 301 549 (2021-03) clauses with plain-language explanations and test guidance."},"5":{"title":"Legal Pack","desc":"Download a full accessibility legal pack: statement, declaration of conformity, and supporting documentation."},"heading":"Recommended tools for procurement","description":"Six tools covering the full procurement accessibility workflow: RFP drafting, vendor assessment, supply chain compliance.","open":"Open tool →","free":"Free","pro":"Pro"},"pro":{"heading":"Pro tools for procurement teams","description":"Generate full Annex IV Technical Files, batch-audit vendor platforms, and export documentation packages suitable for public procurement audit trails.","cta_primary":"See pricing","cta_secondary":"Take the readiness quiz, free"},"reference":{"0":{"title":"EN 301 549","desc":"The harmonised EU standard for ICT accessibility, the primary reference for all public procurement."},"1":{"title":"EAA Law Tracker","desc":"Penalties, authorities, and deadlines for all 27 EU member states."},"2":{"title":"WCAG 2.2 Standards","desc":"The W3C technical standard referenced by EN 301 549 for web content and software."},"heading":"Reference and legislation"}},"gaad-2026-callout":{"logo_alt":"GAAD 2026","eyebrow_locked":"GAAD 2026 · Coming 21 May","eyebrow_live":"Now published","title":"State of Portuguese Digital Accessibility 2026","subtitle_locked":"Inaugural national audit of 160 Portuguese consumer-facing digital services against the European Accessibility Act. Publishing 08:00 WEST on Global Accessibility Awareness Day.","subtitle_live":"Inaugural national audit of 160 Portuguese consumer-facing digital services against the European Accessibility Act. 58% of sites have no accessibility statement ten months after enforcement began.","cta_locked":"Preview the cover","cta_live":"Read the report","countdown_label":"Publishing in"},"global":{"meta":{"title":"Global Accessibility Standards, EAA Cross-Border Compliance Map","description":"Compare global accessibility standards and regulations. Map EAA, ADA, AODA, and other frameworks side-by-side for cross-border compliance self-assessment."},"hero":{"title":"Global Standards","description":"Mapping international accessibility laws and standards to the EAA and EN 301 549."},"card":{"cta":"View Mapping →"},"cards":{"us-section-508":{"title":"US Section 508 vs EN 301 549","description":"Mapping federal US accessibility requirements to the European ICT standard."},"uk-equality-act":{"title":"UK Equality Act 2010","description":"Accessibility requirements in the UK post-Brexit."},"ada-title-iii":{"title":"ADA Title III (USA)","description":"Impact of US disability law on European firms."},"aca-canada":{"title":"Accessible Canada Act (ACA)","description":"Federal accessibility law in Canada."},"australia-dda":{"title":"Australia DDA","description":"The Disability Discrimination Act and digital accessibility."},"ontario-aoda":{"title":"Ontario AODA (Canada)","description":"Province-specific accessibility standards."},"global-fine-tracker":{"title":"Global Accessibility Fine Tracker","description":"Comparing the financial risks of non-compliance across borders."}}},"glossary":{"meta":{"title":"A-Z Accessibility Glossary, EAA & WCAG Terminology","description":"Complete A-Z glossary of digital accessibility terms. Definitions for EAA, WCAG, EN 301 549, ARIA, and compliance terminology used in self-assessment and accessibility auditing."},"title":"A-Z Accessibility Glossary","description":"Definitions and context for digital accessibility and regulatory terminology."},"home":{"meta":{"title":"AccessibilityRef, EAA Compliance for European SMBs. Starter €499/yr, Pro €999/yr","description":"Generate legal-grade evidence, not legal advice, for the European Accessibility Act. Annex IV Technical File, Accessibility Statement (7 EU languages), EN 301 549 mapping, 5-year audit retention. {toolCount} tools, all 27 EU member states. Starter €499/yr or Pro €999/yr, no sales call."},"announcement":{"label_prefix":"🇪🇺 EAA Enforcement","label_status":"LIVE","label_suffix":"· Built for European SMBs","stat_states_value":"27/27","stat_states_label":"EU states","stat_languages_value":"7","stat_languages_label":"Languages","stat_tools_value":"{toolCount}","stat_tools_label":"Tools"},"hero":{"badge":"EAA Enforcement Live · Built for European SMBs","title_html":"Document your EAA compliance before a regulator asks.","description_html":"Legal-grade evidence, not legal advice. Produce your full Annex IV technical file and accessibility statement in under 48 hours, with the audit trail attached.","cta_trial":"Start your compliance audit. 7 days free.","cta_scoping":"Not sure if the EAA applies to you? Take the 5-question check →","cta_trial_caption":"No credit card required · Cancel any time","trust_1":"5-year audit retention included","trust_2":"Maps to EN 301 549","trust_3":"Built for EAA Directive (EU) 2019/882","trust_4":"Annual subscription. Cancel any time. No sales call."},"trust_panel":{"aria":"Platform at a glance","kicker":"Platform / at a glance","synced":"Synced today","stat_states_value":"27/27","stat_states_label":"EU Member States mapped","stat_criteria_value":"87","stat_criteria_label":"WCAG 2.2 criteria covered","stat_tools_value":"{toolCount}","stat_tools_label":"Tools, free & Pro","enforcement_kicker":"EAA ENFORCEMENT STATUS","enforcement_value":"Jun 28, 2025 · Now Active"},"ttv":{"eyebrow":"How fast you can ship","headline":"From scoping to a signed accessibility statement in under 48 hours.","body":"Most teams move from the scoping wizard to a downloadable accessibility statement inside a single working day of focused effort. The 48-hour window leaves room to gather an asset list, run the whole-site scanner, and circulate a draft for stakeholder review before publishing.","step1_label":"Step 1 · 10 minutes","step1_title":"Confirm scope","step1_body":"Five questions to confirm the EAA applies to your business and which Annex applies to your product.","step2_label":"Step 2 · 60 to 90 minutes","step2_title":"Collect evidence","step2_body":"Run the whole-site scanner across your domains. Tag remediation items into the Evidence Vault as you go.","step3_label":"Step 3 · 2 to 4 hours","step3_title":"Generate the documents","step3_body":"The statement wizard and conformity generator produce a publishable accessibility statement plus the supporting Annex IV technical file.","cta":"Start the scoping wizard →","cta_href":"/tools/scoping-wizard"},"urgency":{"eyebrow":"What enforcement looks like","headline":"In some EU jurisdictions, EAA fines reach 5% of national turnover.","body":"The directive has been enforceable in all 27 EU member states since 28 June 2025. Enforcement authorities can impose revenue-scaled fines and force non-conforming products off the EU market. Microenterprises (under 10 staff and €2M turnover) are exempt from service requirements only.","cta":"Estimate your country's maximum fine →","cta_href":"/tools/fine-calculator"},"quick_answer":{"label":"Quick answer","question":"What is the European Accessibility Act, and what do I need to do?","answer":"The European Accessibility Act (Directive (EU) 2019/882) requires consumer-facing digital products and services placed on the EU market on or after 28 June 2025 to meet the harmonised accessibility standard EN 301 549 (2021-03), which incorporates WCAG 2.1 Level AA for web content. AccessibilityRef tooling tests against WCAG 2.2 Level AA, the strict superset of WCAG 2.1, so passing here means you also clear the EAA's legal baseline. Producers must publish an Accessibility Statement and retain a five-year Annex IV technical file; non-compliance is enforced by national market-surveillance authorities.","source":"Directive (EU) 2019/882, art. 4, 9 & 13","source_href":"Https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32019L0882"},"last_updated":{"iso":"2026-04-28"},"author_byline":{"name":"AccessibilityRef Editorial","role":"Compliance editorial team"},"legal_framework_heading":"Legal framework","scoping":{"label":"Free Tool, 60 Seconds","heading":"Not sure if the EAA applies to you?","body":"Answer 5 questions to find out whether the European Accessibility Act covers your business. No login, no email.","cta":"Check now →"},"segments":{"eyebrow":"Self-Assessment Tools","heading":"Who are you?","sub":"Start where you stand.","business":{"label":"I run a business","role":"⬢ Business Owner","tagline":"Is my website legally compliant?","body":"See your EAA fine exposure in any EU member state, work out your deadline, and generate the compliance documentation you actually need.","cta":"See what applies to you →"},"developer":{"label":"I build websites","role":" Developer","tagline":"Test accessibility while you code, not after the audit.","body":"Contrast checker, heading analyser, alt-text checker, focus-order visualiser, component library. Six tools, no login.","cta":"Explore developer tools →"},"compliance":{"label":"I handle compliance","role":"§ Compliance Officer","tagline":"Prove compliance. Document everything.","body":"Generate statements and model fine risk across all 27 EU states. Export audit-ready documentation when you need to show your work.","cta":"Access compliance tools →"},"education":{"label":"I work in education","role":"✎ Education","tagline":"Accessible learning for every student.","body":"Audit student portals, LMS, PDFs, and lecture recordings. Tools built for neurodiverse learner support and WCAG 2.2 compliance.","cta":"See education tools →"},"procurement":{"label":"I handle procurement","role":"◈ Procurement","tagline":"Write accessible procurement requirements.","body":"Generate EN 301 549 RFP clauses. Assess vendor VPATs. Manage supply-chain accessibility compliance end to end.","cta":"See procurement tools →"}},"deadline":{"eyebrow":"EAA Enforcement Deadline","date":"June 28, 2025","status_chip":"Regulation Now Active","body":"All 27 EU member states have transposed the EAA into national law. Enforcement authorities are actively reviewing compliance.","cta":"View by country →","states_aria":"EU member states"},"pro":{"label":"Pro Tools","heading":"All Pro tools","description":"All pro tools including batch auditing, palette generator, statement wizard, 15 EAA sector checklists, screen reader simulator, component library, one annual subscription.","cta":"See all pro tools →","terminal_more":"+ 55 more"},"tools":{"eyebrow":"Featured Free Self-Assessment Tools","heading":"Start free. No login required.","view_all":"View all {toolCount} tools →","open":"Open tool →","free":"Free","contrast":{"title":"Colour Contrast Checker","description":"Verify WCAG AA/AAA compliance. Enter any hex colour pair, get instant results."},"fine":{"title":"EAA Fine Calculator","description":"Estimate your maximum EAA penalty for any EU member state based on company revenue."},"headings":{"title":"Heading Structure Analyser","description":"Enter a URL. Get a visual H1–H6 hierarchy tree with skipped-level and missing-H1 flags."},"quiz":{"title":"EAA Ready Quiz","description":"20 questions. Score your organisational readiness for the EAA deadline in under 5 minutes."}},"stats":{"eyebrow":"Platform statistics","heading":"Independent and daily-synced with the source.","countries":"27/27","countries_label":"EU Member States mapped","countries_desc":"All EAA national transpositions verified and daily-synced with EUR-Lex.","criteria":"87","criteria_label":"WCAG 2.2 criteria covered","criteria_desc":"Every success criterion with verbatim W3C text and manual test scripts.","grade":"AA","grade_label":"Built to the same bar","grade_desc":"AccessibilityRef itself is a B2B SaaS, technically out of EAA scope, but we hold ourselves to WCAG 2.2 Level AA, the same bar we hold your sites to. Independently re-tested each quarter."},"reference":{"eyebrow":"Reference library","heading":"The standards, verbatim.","wcag":{"code":"W3C · WCAG 2.2","title":"WCAG 2.2 Standards","desc":"All 87 success criteria with verbatim text, manual test scripts, and remediation guidance.","cta":"Browse WCAG →"},"eaa":{"code":"EU · Directive 2019/882","title":"EAA Law Tracker","desc":"National transpositions, enforcement authorities, and penalty caps for all 27 EU member states.","cta":"View by country →"},"en301549":{"code":"ETSI · EN 301 549 v3.2.1","title":"EN 301 549","desc":"The harmonised European standard that defines the technical requirements under the EAA.","cta":"Read the standard →"}},"what_is":{"heading":"What is AccessibilityRef?","body":"AccessibilityRef is the independent European platform for digital accessibility compliance self-assessment. {toolCount} free and professional tools test against the European Accessibility Act, WCAG 2.2, and EN 301 549, with 22 sector-specific checklists across hardware, software, mobile, telecoms, e-commerce, banking, transport, and publishing. Country-specific fine calculators and enforcement-authority data cover all 27 EU member states."},"faq":{"eyebrow":"FAQ","heading":"Frequently asked questions about EAA self-assessment","q1":"What is the European Accessibility Act (EAA)?","a1":"The EAA (Directive 2019/882) is the EU law requiring consumer-facing digital products and services to be accessible to people with disabilities. It became fully enforceable on 28 June 2025. Each member state sets its own penalty framework; fines can reach up to 5% of national turnover in some jurisdictions.","q2":"How do I run an EAA self-assessment?","a2":"Start with the free EAA Ready Quiz for a quick compliance score. From there, the WCAG 2.2 Audit Checklist covers all 87 success criteria. For a full evaluation, use the Whole-Site Scanner: a 50-point self-assessment that produces a weighted conformance score and exports as a Word report.","q3":"What is the difference between WCAG, EAA, and EN 301 549?","a3":"WCAG 2.2 is the W3C technical standard for web content accessibility. EN 301 549, the harmonised European standard, references WCAG 2.1 AA and adds requirements for non-web software, hardware, and documents. The EAA is the EU law that mandates compliance with EN 301 549 for products and services sold in the EU.","q4":"Which standard should I use for EAA compliance?","a4":"The harmonised standard for EAA is EN 301 549 (2021-03). For web content, this standard directly references WCAG 2.1 Level AA. Meeting WCAG 2.2 AA satisfies the web requirements and exceeds the minimum.","q5":"Are microenterprises exempt from the EAA?","a5":"Microenterprises (fewer than 10 employees and ≤ €2M turnover) are exempt from the EAA's service requirements, but not necessarily from national laws or product requirements.","q6":"What happens if you don't comply with the European Accessibility Act?","a6":"Non-compliance can result in fines set by each EU member state, orders to withdraw products from the market, public warnings, and mandatory corrective action. Use the EAA Fine Calculator to estimate the maximum penalty for any member state.","q7":"What accessibility self-assessment tools are available for free?","a7":"The free tier includes the Colour Contrast Checker, Heading Structure Analyser, Alt Text Quality Checker, Focus Order Visualiser, WCAG 2.2 Audit Checklist, EAA Ready Quiz, EAA Fine Calculator, Readability Checker, and ARIA Role Reference. None of them require a login.","q8":"How do I use this site to build a compliance programme?","a8":"Three tools form the documentation backbone: the Compliance Programme Template for the governance framework, the Guided EAA Self-Assessment for the 30-point audit, and the Statement Wizard for the accessibility statement itself. Pro tools add batch auditing, the compliance report builder, and the VPAT editor on top."}},"impressum":{"meta":{"title":"Impressum","description":"Legal disclosure / Impressum for AccessibilityRef as required by §5 TMG."},"heading":"Impressum","subtitle":"Legal disclosure pursuant to §5 TMG (Germany)","s1":{"heading":"Information pursuant to §5 TMG","name":"David Keogh","address_line1":"Travessa Dom Sancho I 25","address_line2":"3030-461 Coimbra","country":"Portugal"},"s2":{"heading":"Contact","email_label":"Email:"},"s3":{"heading":"VAT","body":"VAT registration is not required at the current trading level. A VAT ID will be added once registration is completed."},"s4":{"heading":"Responsible for Content","name":"David Keogh","address_line1":"Travessa Dom Sancho I 25","address_line2":"3030-461 Coimbra","country":"Portugal"},"related":{"heading":"Related Policies","privacy":"Privacy Policy","terms":"Terms of Service","cookies":"Cookie Policy","contact":"Contact Us"}},"late":{"meta":{"title":"Already Late for EAA Compliance? Here's What to Do Now, AccessibilityRef","description":"The EAA deadline was June 28, 2025. If you're not yet compliant, here are the 10 highest-priority actions in order of legal risk reduction. Free and Pro tools to help."},"hero":{"badge":"EAA Enforcement Active · June 28, 2025","title_line1":"The EAA Deadline","title_line2":"Has Passed.","title_line3":"Here's What to Do Now.","subtitle":"You're not alone, most businesses are still working on compliance. Here are the 10 highest-priority actions, in order of legal risk reduction."},"intro":{"heading":"Don't panic. Start here.","body":"Regulators across the EU are beginning enforcement, but they are also looking for evidence of good faith effort. Taking action now, even partial action, significantly reduces your legal exposure. Follow these steps in order."},"steps":{"0":{"title":"Publish an Accessibility Statement","time":"15 min","desc":"Shows regulators you are aware of the requirement and actively working on it. This is your single most important quick win, it demonstrates good faith before anything else.","href":"/tools/statement-wizard"},"1":{"title":"Take the EAA Ready Quiz","time":"5 min","desc":"Understand exactly where you stand before fixing anything. The quiz gives you a clear picture of your gaps and prioritises the issues that matter most under the EAA.","href":"/tools/eaa-ready-quiz"},"2":{"title":"Check Your Country's Requirements","time":"10 min","desc":"Penalties, cure periods, and enforcement bodies vary significantly by member state. Knowing your national rules tells you how much time you have and what the consequences are.","href":"/eaa"},"3":{"title":"Fix Colour Contrast","time":"30 min","desc":"The most common accessibility failure on EU websites. Low contrast text fails WCAG 1.4.3, which is explicitly required by the EAA. Fix this first for the fastest visible improvement.","href":"/tools/contrast-checker"},"4":{"title":"Add Alt Text to Images","time":"1–2 hours","desc":"Missing alt text is the second most common issue found in EAA audits. Every meaningful image needs a text alternative so screen reader users can access your content.","href":"/tools/alt-text"},"5":{"title":"Fix Heading Structure","time":"30 min","desc":"Screen readers rely on headings to navigate your content. A broken heading hierarchy (skipped levels, missing H1) is a common WCAG 1.3.1 failure that regulators specifically check.","href":"/tools/headings"},"6":{"title":"Ensure Keyboard Navigation","time":"1 hour","desc":"Every function on your site must be operable without a mouse. This is WCAG 2.1 (Keyboard Accessible), a core EAA requirement. Test by tabbing through your site right now.","href":"/tools/focus-order"},"7":{"title":"Run the Full Self-Assessment","time":"45 min","desc":"A systematic 30-point assessment covering all EAA requirements. This gives you a documented baseline of your current state, essential for any enforcement inquiry.","href":"/tools/self-assessment"},"8":{"title":"Generate Your Compliance Report","time":"30 min","desc":"Document your current state and your remediation plan. A written record showing the steps you are taking is the strongest evidence of good faith you can present to an enforcement body.","href":"/tools/compliance-report"},"9":{"title":"Create a Conformity Declaration","time":"15 min","desc":"The formal EU document required under Annex IV of the EAA. This is the legal declaration that your product or service meets the accessibility requirements of the directive.","href":"/tools/conformity-generator"},"heading":"10 Priority Actions","subheading":"Work through these in order. Each one reduces your legal risk.","free":"Free","pro":"Pro","open":"Open tool →"},"cta":{"heading":"Need a structured remediation plan?","body":"The EAA Compliance Wizard walks you through a full scoping assessment and generates a prioritised action plan tailored to your business type, size, and sector.","primary":"Start the compliance wizard","secondary":"View all Pro tools"},"reassurance":{"heading":"What enforcement looks like in practice","items":{"0":"Most enforcement actions begin with a warning and a cure period, not an immediate fine.","1":"A published accessibility statement demonstrating awareness is weighted positively by regulators.","2":"Documented remediation plans show good faith effort, which reduces penalty severity.","3":"Acting now, even partially, is significantly better than doing nothing."}}},"legal-context":{"legalBasisHeading":"Legal basis","legalBasisLabel":"Legal basis:","toolHeadings":{"burden-calculator":"Legal basis, disproportionate burden exception","conformity-generator":"Legal basis, EU Declaration of Conformity","compliance-program":"Legal basis for the compliance programme","compliance-report":"Legal basis for compliance reporting","vpat-editor":"Legal basis, accessibility conformance reporting","scoping-wizard":"Legal basis, EAA scope and definitions","eaa-ready-quiz":"Legal basis, EAA readiness","fine-calculator":"Legal basis, penalty framework","self-assessment":"Legal basis, self-assessment pipeline","statement-wizard":"Legal basis, accessibility statement","statement-validator":"Legal basis, accessibility statement validation","site-scanner":"Legal basis, automated scanning","alt-text":"Legal basis, image accessibility","headings":"Legal basis, heading structure","focus-order":"Legal basis, focus management","contrast-suite":"Legal basis, colour contrast","readability":"Legal basis, readability","mobile-checker":"Legal basis, mobile accessibility","touch-target-tester":"Legal basis, touch target sizing","screen-reader-simulator":"Legal basis, screen-reader compatibility","biometric-matrix":"Legal basis, biometric authentication","aria-assistant":"Legal basis, ARIA usage","document-auditor":"Legal basis, document accessibility","pdf-checklist":"Legal basis, PDF accessibility","competitor-benchmark":"Legal basis, competitor benchmarking","metrics-dashboard":"Legal basis, accessibility metrics","rfp-generator":"Legal basis, RFP accessibility requirements","legal-pack":"Legal basis, procurement legal pack","checklist-generator":"Legal basis, checklist export","component-library":"Legal basis, accessible components","checklist":"Legal basis, WCAG checklist","transposition-tracker":"Legal basis, EAA transposition","banking-checklist":"Legal basis, banking services","ecommerce-checklist":"Legal basis, e-commerce","transport-checklist":"Legal basis, transport services","voice-comms-checklist":"Legal basis, voice communications","support-docs-checklist":"Legal basis, support documentation","ebook-checklist":"Legal basis, e-books","emergency-checklist":"Legal basis, emergency communications","supply-chain-checklist":"Legal basis, supply chain"},"jurisdictionalExtrasHeading":"What {jurisdictionName} requires beyond the EAA baseline","jurisdictionalExtras":{"intro":"These are the requirements the national transposition adds on top of the directive, meet them in addition to the EAA baseline.","obligationsCount":"{count, plural, one {# obligation} other {# obligations}}","categoryLabels":{"scope":"Scope","labelling":"Labelling & language","documentation":"Documentation","enforcement":"Enforcement","penalties":"Penalties","reporting":"Reporting"},"jurisdictionNames":{"eu":"EU baseline","ie":"Ireland","fr":"France","pt":"Portugal"}},"disclosureShow":"Show full text ▾","disclosureHide":"Hide full text ▴","disclosureSummary":"Cited articles, in full","viewOnEurLex":"View on EUR-Lex","viewOnIrishStatuteBook":"View on Irish Statute Book","viewOnEtsi":"View on ETSI","viewSource":"View source","retrievedOn":"Retrieved {date}","transposes":"Transposes {instrument}, {citation},","officialEnglishPending":"(official English text pending verbatim ingestion).","howItAppliesLocally":"How it applies locally","readVerbatimText":"Read the verbatim text ({chars}+ characters) ▾","hideVerbatimText":"Hide verbatim text ▴","articleLabel":"Article {number}","annexLabel":"Annex {number}","regulationLabel":"Regulation {number}","sectionLabel":"Section {number}","paragraphLabel":"Paragraph {number}","scheduleLabel":"Schedule {number}","popoverAriaLabel":"Legal citation, {instrument}"},"legal-disclaimer":{"title":"Important Legal Disclaimer","body":"This tool is a self-assessment aid only and does not constitute legal advice or a formally certified compliance assessment. Outputs, including reports, scores, checklists, and accessibility statements, are for internal use and should be reviewed by a qualified legal representative or independent accessibility auditor before being relied upon for regulatory, procurement, or public-disclosure purposes. All assessment risk lies with the internal assessor. accessibilityref, its developers, and staff accept zero liability for losses arising from use of or reliance on these outputs. Always verify against official sources: the W3C WCAG 2.2 Recommendation, the European Accessibility Act (Directive 2019/882), and your national enforcement authority."},"notifications":{"heading":"Notifications","lede":"Updates on background jobs you've kicked off, like batch translations and bulk alt-text generation.","auth_required":"Sign in to see your notifications.","load_error":"Could not load notifications.","empty":"No notifications yet. You'll see one here once a batch job finishes.","batch_complete_heading":"Batch finished","batch_complete_body":"Your {routeName} batch of {itemCount} items is ready.","batch_id_label":"Batch ID","view_tool":"Open tool","generic_label":"Update"},"partners":{"metaTitle":"Partner Directory | AccessibilityRef","metaDescription":"Accessibility consultants, agencies, and developers across the EU who can help implement your EAA compliance plan.","heading":"Partner Directory","intro":"Accessibility consultants, agencies, and developers across the EU. Filter by jurisdiction to find a partner near you.","filterLabel":"Jurisdiction","filterAll":"All EU-27","emptyHeading":"No partners listed yet","emptyBody":"We are onboarding the first agencies right now. Check back soon, or get in touch if you would like to be listed.","joinHeading":"Are you an accessibility professional?","joinBody":"Consultants, agencies, and developers specialising in accessibility can apply for a free Pro account in exchange for being listed here.","joinCta":"Get in touch","visitWebsite":"Visit website","noWebsite":"No website","logoAlt":"{firmName} logo"},"portugal-eaa-2026":{"meta":{"title":"State of Portuguese Digital Accessibility 2026, Inaugural Edition · AccessibilityRef","description":"An inaugural audit of 160 Portuguese consumer-facing digital services against the European Accessibility Act. 58% of sites have no accessibility statement ten months after enforcement began.","ogImageAlt":"State of Portuguese Digital Accessibility 2026 cover image"},"locked":{"eyebrow":"Global Accessibility Awareness Day · 21 May 2026","title":"State of Portuguese Digital Accessibility","year":"2026","subtitle":"An inaugural audit of 160 Portuguese consumer-facing digital services against the European Accessibility Act.","publishingStrap":"Publishing 21 May 2026 at 08:00 WEST","countdownLabel":"Time until publication","wordmark":"Accessibilityref.eu"},"embargoBanner":{"label":"EMBARGOED","body":"EMBARGOED until 21 May 2026 08:00 WEST. Do not publish or share publicly."},"hero":{"badge":"GAAD 2026","title":"State of Portuguese Digital Accessibility","year":"2026, Inaugural Edition","subtitle":"Automated audit of 160 Portuguese consumer-facing digital services across eight sectors, run between 22 and 24 April 2026 against the European Accessibility Act.","downloadCta":"Download report (Word.docx)","downloadHref":"/reports/state-of-portuguese-digital-accessibility-2026-en.docx","datasetCta":"Download dataset (Excel.xlsx)","datasetHref":"/reports/state-of-portuguese-digital-accessibility-2026-dataset.xlsx","metaStrip":"Published 21 May 2026 · accessibilityref.eu · Scan window 22–24 April 2026"},"stats":{"heading":"Headline numbers","cards":{"sitesInScope":{"label":"Sites in scope","value":"160","caption":"8 sectors × 20 sites"},"sectors":{"label":"Sectors covered","value":"8","caption":""},"passing":{"label":"Passing grade","value":"64","caption":"40% of audited sites"},"gradeA":{"label":"Grade A sites","value":"8","caption":"Score 16+/20"},"fullStatement":{"label":"Fully compliant statement","value":"20","caption":"Article 13 substantive markers"},"noStatement":{"label":"No statement at all","value":"92","caption":"58% of audited sites"},"unreachable":{"label":"Unreachable","value":"30","caption":"Bot-blocked or failed fetch"},"overlays":{"label":"Overlay widgets","value":"10","caption":"Third-party accessibility scripts"}},"meanCaption":"Mean composite score across reachable sites: 9.74/20."},"executiveSummary":{"heading":"Executive summary","paragraphs":["In April 2026, ten months after the European Accessibility Act became enforceable across the EU, accessibilityref.eu audited 160 Portuguese consumer-facing digital services using automated structural and rendered-DOM testing. The sample covered eight sectors with twenty sites each: banking, public sector, healthcare and insurance, telecoms and media, travel and transport, e-commerce, sport and culture, and utilities. Sites were selected as the largest and most-used Portuguese services within each category.","Only twenty-four of the 160 sites in scope met or exceeded the threshold for an A or B grade. Ninety-two had no detectable accessibility statement, which is a baseline requirement under Article 13 of the EAA transposition. A further thirty could not be reached by a standard audit request.","The findings are aggregate. No company is named, and individual results are not published; the data does not establish legal non-compliance for any specific entity. The report characterises the state of one sector as it adapts to a new legal obligation, and flags where consumer complaints and regulator attention are most likely in the months ahead."],"caveatCallout":"A passing grade in this report is the structural and statement-level baseline of EAA conformance, nothing more. Even sites in the A band carry residual issues that a manual conformance audit would catch. Passing here is the floor."},"methodology":{"heading":"Methodology","intro":"The audit used three layers of automated testing, scoped to what can be observed without authentication or private-account interaction. It therefore captures the public-facing experience of each service: what a first-time visitor encounters, including a visitor relying on assistive technology.","whatTestedHeading":"What was tested","whatTestedItems":["Structural HTML inspection via cheerio: page language declaration, viewport meta tag, skip-to-content link,

landmark presence, heading hierarchy, image alt attribute coverage, form field labelling, and cookie banner accessibility signals.","Rendered DOM accessibility audit via axe-core 4.10 running inside a real browser (Chrome). Axe-core runs the full WCAG 2.1 A and AA ruleset plus best-practice checks against the post-render DOM.","Accessibility statement detection and classification: each site was probed at six common conventional URLs for an Article 13-style accessibility statement, and the recovered statement was scored against eleven required markers (conformity claim, WCAG reference, EN 301 549 reference, A/AA level declaration, scope, date, feedback channel, contact email, declaration of inaccessible parts, Article 29 reference, and the named regulator).","Overlay widget detection: third-party 'accessibility overlay' vendor scripts were detected via known DOM signatures and recorded as a separate signal. They do not count toward conformance."],"scoringHeading":"Composite scoring","scoringIntro":"Each site was assessed against a 20-point binary scoring system spread across four dimensions:","scoringDimensions":["Structural accessibility (8 points): one point per structural check passed.","Accessibility statement (4 points): four points for a full Article 13 statement, two for a partial statement, one for a marketing claim only, zero for none or for overlay-vendor boilerplate.","Axe-core findings (5 points): one point each for: zero critical violations, fewer than five critical-plus-serious violations, zero colour-contrast issues, zero image-alt issues, zero link-name issues.","EAA compliance signals (3 points): one point each for: no overlay widget present, EAA signals detected in markup, accessibility links present in navigation."],"grades":{"A":"Grade A: 16–20 (strong baseline conformance)","B":"Grade B: 13–15 (substantial conformance with material gaps)","C":"Grade C: 10–12 (passing baseline but multiple weak areas)","D":"Grade D: 7–9 (substantial non-conformance)","F":"Grade F: 0–6 (negligible accessibility provision)","NA":"Not reachable: site could not be retrieved by automated audit (bot wall, geoblock, fetch error)."},"notTestedHeading":"What this audit does not test","notTestedBody":"This audit is not a manual accessibility conformance evaluation. It does not test authenticated user flows, screen reader narration quality, the full transactional path (checkout, booking, account management), keyboard-only journey completion, video caption quality, or PDF document accessibility. A site scoring well here may still fail a full manual audit, and a site scoring poorly here will almost certainly fail one. The findings should be read as a sector-level signal, not as a definitive statement on any individual site.","selfDeclarationCallout":"This is a self-assessment tooling exercise. Under the European Accessibility Act, businesses self-assess and publish accessibility statements; regulators investigate reactively. This report describes the public evidence of that self-assessment work across one national market."},"findings":{"heading":"Findings","f1":{"title":"1. Composite score distribution","body":"Of the 160 sites audited, 64 (40%) reached a passing composite grade of C or higher. Only 8 reached Grade A. The largest grade band was D, substantial non-conformance. A further 30 sites could not be reached by the automated audit at all, which is itself an accessibility concern: infrastructure that blocks accessibility tooling typically also impairs assistive technology."},"f2":{"title":"2. Mean score by sector","body":"Sector-level performance is uneven. Banking and Public Sector clear the passing threshold of 10/20; the remaining six sectors do not. Travel & Transport, E-commerce, and Telecoms & Media cluster within 0.1 points of one another at 9.5/20, which suggests a similar baseline of partial structural compliance without statement-level effort.","tableCaption":"Sector-by-sector composite results","tableHeaders":{"sector":"Sector","mean":"Mean score","scored":"Sites scored","unreachable":"Sites unreachable"},"rows":[{"sector":"Banking","mean":"12.06/20","scored":"17","unreachable":"3"},{"sector":"Public Sector","mean":"11.63/20","scored":"19","unreachable":"1"},{"sector":"Healthcare & Insurance","mean":"9.65/20","scored":"17","unreachable":"3"},{"sector":"Telecoms & Media","mean":"9.47/20","scored":"19","unreachable":"1"},{"sector":"Travel & Transport","mean":"9.47/20","scored":"17","unreachable":"3"},{"sector":"E-commerce","mean":"9.46/20","scored":"13","unreachable":"7"},{"sector":"Sport & Culture","mean":"7.77/20","scored":"13","unreachable":"7"},{"sector":"Utilities","mean":"7.4/20","scored":"15","unreachable":"5"}]},"f3":{"title":"3. Grade distribution within each sector","body":"No sector is uniform. Even the lowest-mean sectors include individual high performers; even Banking, the strongest-mean sector, contains sites scoring in the F band. The dispersion suggests EAA compliance is currently driven by individual organisational priorities rather than sector-wide standards or peer pressure."},"f4":{"title":"4. Accessibility statements: the single largest gap","paragraphs":["The largest gap in the dataset is the near-absence of compliant Article 13 accessibility statements. Of 160 sites, only 20 (13%) published a statement that met the substantive markers required by the EAA transposition. 92 sites (58%) published no statement at all, neither at conventional URLs (/acessibilidade, /accessibility, /declaracao-de-acessibilidade) nor in their footer navigation.","A further nine sites published only the boilerplate statement injected by a third-party accessibility overlay vendor. These do not satisfy Article 13: they describe the overlay's claimed remediation rather than the site's actual conformance position, and they do not name the responsible regulator or the feedback mechanism that the law requires.","Producing an accessibility statement is mechanically the easiest part of EAA compliance: a written declaration following a published template. That 58% of sites have not produced one indicates EAA awareness has not yet reached the operational level inside most organisations."]},"f5":{"title":"5. Structural pass rates","paragraphs":["Eight structural HTML accessibility checks were applied to every site. Pass rates varied widely. Mobile viewport and language declaration both reach high pass rates because modern web frameworks set them by default. The lower-scoring checks (heading order, skip links, and accessible cookie banners) fail because they require deliberate accessibility intent rather than framework defaults.","The cookie banner result is worth pulling out. Only 11% of sites passed the cookie banner accessibility check. No consumer can use a Portuguese commercial site without first interacting with a cookie banner, so an inaccessible banner is a complete blocker for users relying on assistive technology, regardless of how accessible the rest of the site is."]},"f6":{"title":"6. Top automated (axe-core) violations","intro":"Across the 118 sites where the rendered DOM was successfully captured, axe-core flagged thousands of individual violations. Three violation types account for most of them:","items":["Colour contrast (832 instances across 49 sites): text fails the WCAG AA contrast ratio of 4.5:1, or 3:1 for large text. This is the most prevalent issue in the dataset, and the easiest to remediate via a stylesheet audit.","Link name (324 instances across 45 sites): links lack discernible text. The most common causes are icon-only links without aria-labels and social media icons in footers. Screen readers cannot describe these links to users.","Image alt (275 instances across 27 sites): informative images missing alt text. Concentrated in a small number of image-heavy sites where remediation is large in scope but mechanical."],"outro":"Together, these three issue classes account for over 80% of detected automated violations. They are also the issues a regulator is most likely to detect when running an automated scan in response to a complaint."},"f7":{"title":"7. Accessibility overlays","paragraphs":["Ten of the 160 sites in the audit had a third-party accessibility overlay widget installed. These products are widely marketed to non-technical site owners as a low-effort EAA compliance solution. The European disability community has consistently rejected this framing: overlays cannot fix underlying code-level issues like missing alt text, broken heading hierarchy, or inaccessible custom components. They can only modify visual presentation for users who interact with the overlay itself.","Overlay-equipped sites in this audit scored no better on average than non-overlay sites in the same sector. Three of the ten overlay-equipped sites had detectable underlying issues that the overlay was actively masking. In one example, the overlay claimed conformance in its boilerplate statement while axe-core detected critical violations on the same page."]}},"whatThisMeans":{"heading":"What this means for Portuguese organisations","ab":{"title":"For organisations that scored well (A or B band)","intro":"A composite score in the A or B band indicates deliberate accessibility work and a published statement. It does not indicate full conformance. Organisations in this band should:","items":["Commission a full manual conformance audit before the EAA enforcement window matures further. Automated tooling typically catches 30–40% of WCAG issues; the rest require human evaluation.","Verify that the published accessibility statement reflects the current state of the site, not the state at the time of writing. Statements should be reviewed at least annually.","Establish a complaints handling procedure that meets the Article 13 timelines, and publish the responsible feedback channel where users can find it."]},"cd":{"title":"For organisations that scored in the C or D band","intro":"A score in this band typically means some accessibility work has been done, but without a coherent compliance posture. The common pattern is a site that passes mobile viewport and language checks (often by framework default) but lacks structural landmarks, has heading-order issues, and has no published statement. For these organisations:","items":["The fastest single intervention is publishing an Article 13 accessibility statement. It is required by law, it is mechanically straightforward, and it moves an organisation from 'no engagement' to 'documented engagement' in a regulator's eyes.","Cookie banner accessibility is the second-fastest material improvement. The banner is a discrete component, often supplied by a third-party CMP that has accessible variants available.","Colour contrast remediation typically delivers the largest reduction in automated violation counts for the lowest engineering effort."]},"f":{"title":"For organisations that scored in the F band or were not reachable","intro":"These sites are at the highest risk of regulatory attention. An unreachable site is, in practice, also unreachable to assistive technology in many configurations. A site scoring in the F band would not survive any reasonable manual audit, and is likely to receive complaints if anyone chooses to file one with the relevant regulator.","items":["A formal accessibility audit by a qualified consultant is the appropriate first step for organisations in this position. Self-remediation is unlikely to succeed at the scale required.","Site infrastructure that blocks bots will frequently also block legitimate accessibility tooling, including the tools regulators use during investigations. Whitelisting known accessibility scanners is a low-risk infrastructure change."]}},"sectorObservations":{"heading":"Sector-level observations","intro":"Beyond individual organisations, several patterns emerge at the sector level:","items":[{"title":"Banking outperforms but does not excel","body":"Banking achieved the highest mean score, in line with the sector's long history of investment in regulated digital infrastructure. The gap between Banking's 12.1/20 and a genuinely strong sector-wide score (anything approaching 16/20) remains substantial. Three banking sites in the audit could not be reached at all."},{"title":"Public Sector shows the legacy of WAD compliance work","body":"Portuguese public sector sites have been subject to the Web Accessibility Directive transposition (Decreto-Lei 83/2018) for almost eight years, longer than the EAA. The 11.6/20 mean reflects accumulated compliance investment, particularly visible in the higher prevalence of accessibility statements among public sector sites. The remaining gap is concentrated in older municipal and ministerial portals that have not been refreshed since the original WAD work."},{"title":"Utilities and Sport & Culture lag substantially","body":"These two sectors share a profile: lower digital sophistication overall, customer interactions that historically did not require sustained website use, and limited competitive pressure on user experience. As a result, accessibility provision in these sectors is meaningfully behind. The customer base also skews older and includes a higher proportion of users who would benefit most from accessibility provision."},{"title":"E-commerce shows the highest unreachable rate","body":"Seven of the twenty E-commerce sites in scope could not be reached by the automated audit. The unreachable rate is significantly higher than any other sector, and reflects aggressive bot-blocking infrastructure deployed by larger Portuguese retail platforms. The infrastructure protects against scraping but also blocks accessibility tooling, third-party audit work, and in some configurations certain assistive technologies that simulate browser behaviour."}]},"lookingAhead":{"heading":"Looking ahead","paragraphs":["The European Accessibility Act has been enforceable for ten months at the time of this audit. The dataset shows that compliance work has begun in pockets but has not yet reached the operational level in most Portuguese organisations. The accessibility statement gap (58% of sites with no detectable statement) is the most actionable finding: it is the easiest individual element to remediate, and the element regulators will look for first.","Enforcement patterns to date in other EU member states (notably Germany, France, and Italy) show first-wave regulatory action focused on the most visible categories (large e-commerce platforms, banks, and telecoms) and on the easiest-to-prove failures, including missing accessibility statements and obvious axe-detectable issues like colour contrast and missing alt text. Portuguese enforcement will likely follow a similar pattern.","Accessibilityref.eu will repeat this audit in September 2026 (mid-year update) and January 2027 (year-end review), with comparable methodology and scope. A second comparable dataset will allow trend reporting: which sectors are improving, which are not, and where regulator attention may be most warranted."],"callout":"The State of Portuguese Digital Accessibility report is published as a recurring series. Aggregate findings are public; individual results are not. The objective is to inform the conversation, not to identify defendants."},"about":{"heading":"About this report","paragraphs":["This report was produced by accessibilityref.eu, an independent European accessibility tooling and reference platform. The audit ran between 22 and 24 April 2026 on a custom Node.js audit harness combining HTTP fetching, headless browser rendering, axe-core 4.10, and a purpose-built Article 13 accessibility statement classifier.","Site identities are masked using sector-prefixed sequence identifiers (e.g. BANK-01, ECOM-12) ordered by composite score within each sector. No mapping between anonymous identifiers and named entities is published."],"dataAvailability":{"title":"Data availability","body":"The anonymised dataset is published as an Excel workbook alongside this report. It contains a summary by sector, all 160 anonymised site rows with composite scores and per-check binary results, and a methodology key explaining each of the twenty checks. Additional cuts or extracts can be requested at press@accessibilityref.eu."},"pressContact":{"title":"Press contact","name":"Dave Keogh, Founder","availability":"Available for written comment in English and Portuguese. Spoken interviews in English only.","email":"Press@accessibilityref.eu","location":"Coimbra, Portugal"},"copyright":"© 2026 accessibilityref.eu. This report may be cited and quoted with attribution. The underlying dataset is provided under a transparent research framing and may not be used to identify individual organisations."},"ptDisclaimer":{"heading":"Note on translation","body":"This Portuguese version of the report was produced with AI-assisted translation. Reasonable steps have been taken to verify accuracy; please report any errors to press@accessibilityref.eu. The English version is authoritative."},"frRedirectNotice":"The full Portuguese Digital Accessibility report is published in English and Portuguese only."},"portugal-eaa-index":{"meta":{"title":"Portugal EAA Compliance Index · AccessibilityRef","description":"Public dataset of EAA compliance signal across 160 Portuguese websites in 8 sectors."},"header":{"badge":"Public Dataset","title":"Portugal EAA Compliance Index","lede":"A recurring audit of 160 Portuguese websites across eight sectors against the European Accessibility Act. Open methodology, open data, reproducible scoring.","stats":{"sites":"160 sites","sectors":"8 sectors","checks":"Axe-core + 10 interaction checks","export":"CSV & JSON export"}},"editions":{"heading":"Editions","empty":"The first edition has not been published yet. Check back soon.","sitesProgress":"{complete}/{total} sites","avgScore":"Avg {score}/100"},"methodology":{"heading":"Methodology","body":"Scores combine axe-core automated audits (55% weight) with ten interaction checks (45% weight) including keyboard navigation, cookie banner reachability, form error handling, mobile tap-targets, and skip-link behaviour. Scans are run against the homepage in a Portugal-locale headless browser. Automated tools catch an estimated 30–40% of WCAG issues; this index is a comparative signal, not a conformance claim."}},"pricing":{"meta":{"title":"Pricing, Starter €499 and Pro €999 for the EAA Compliance Pack","description":"Two-tier annual subscription: Starter €499/year (single site, document generators, statement wizard, 24 sector checklists, basic Evidence Vault), Pro €999/year (3 domains, Whole-Site Scanner, batch tools, AI cross-page dedup, full immutable Evidence Vault with sealed export). 7-day Pro trial, no credit card required. Cancel any time."},"hero":{"label":"Pricing · No sales call","title":"Everything regulators need to see. For less than the cost of a single consultant day.","description":"Starter (€499/yr) gives a single-site business the documentation a market-surveillance authority would actually ask for. Pro (€999/yr) adds whole-site scanning across three domains and a regulator-ready Evidence Vault. Seven-day Pro trial, no credit card, cancel any time."},"card":{"free":{"chip":"Free forever","title":"Free","price":"€0","unit":"/forever","risk_line":"No login required for most tools · Forever","description":"Anonymous single-URL diagnostics. No login required.","features":["Colour Contrast Checker (WCAG AA/AAA)","EAA Fine Calculator, all 27 EU states","Heading Structure Analyser","EAA Ready Quiz (20 questions)","Alt Text Quality Checker","Focus Order Visualiser","ARIA Role Reference","Readability Checker","WCAG 2.2 reference library (87 criteria)","EAA Transposition Tracker"],"cta":"Browse free tools"},"starter":{"chip":"Starter","title":"Starter","price":"€499","unit":"/year","risk_line":"30-day refund · Annual subscription · Cancel any time","description":"If you have one website to protect, this tier produces the documentation a regulator would actually ask for: accessibility statement, EU Declaration of Conformity, audit checklist, and the burden calculator if you need to justify a partial exemption.","cta":"Subscribe to Starter","features":["1 verified domain","All free tools","Accessibility Statement Generator (7 languages)","EU Declaration of Conformity Generator","WCAG Audit Checklist Generator","Compliance Programme Template","Disproportionate Burden Calculator","Business Case Bundle","EAA Ready Quiz + Badge Generator","All 24 sector checklists","PDF Accessibility Checklist","Evidence Vault, basic (store your own records)"]},"pro":{"chip":"Pro","bundle_label":"Best for multi-site","title":"Pro","price":"€999","unit":"/year","risk_line":"7-day free trial · 30-day refund · No credit card required","description":"For brands running multiple domains who need to produce regulator-ready evidence on demand. Automate whole-site scanning across three domains, batch-audit pages in parallel, and lock your audit trail in an Evidence Vault that's tamper-evident by design.","cta":"Subscribe to Pro","trial_cta":"Start your compliance audit. 7 days free.","features":["3 verified domains","Everything in Starter","Whole-Site Scanner with sampling","Heading Structure Analyser Pro (batch 50)","Focus Order Visualiser Pro (batch 10)","Competitor Accessibility Benchmark","Document Accessibility Auditor","Mobile Accessibility Checker","Screen Reader Simulator","Metrics Dashboard","AI Cross-Page Dedup, 50 batches/day","Compliance Report Builder","Guided EAA Self-Assessment","VPAT / ACR Editor","Vendor Accessibility Checklist (RFP)","Procurement Legal Pack","Evidence Vault, full immutable hash chain with sealed export"]},"trial_note":"7-day free trial on Pro, no credit card required. VAT added at checkout for EU customers.","agency":{"line":"Running accessibility programmes for multiple clients? Agency plans launch later this year. Get on the early-access list and we will lock in your seat pricing now, before the public rate is set.","cta":"Reserve agency pricing"},"alternatives":{"heading":"Why this and not the alternatives","intro":"Three approaches European businesses currently use to address the EAA. Here is what each one actually produces.","columns":[{"tag":"Cheapest","title":"Overlay widget","price":"€40 to €490 / month","summary":"A JavaScript widget that adds a floating accessibility toolbar on top of your site.","pros":["Lowest sticker price","Two-minute install"],"cons":["Does not produce the Annex IV technical file the EAA requires","Does not generate the accessibility statement or the EU Declaration of Conformity","Leaves the underlying HTML unchanged, so accessibility audits still flag the same issues"],"verdict":"Useful as a complement. Not a compliance strategy on its own."},{"tag":"Deepest","title":"Boutique consultant","price":"€1,200 to €2,500 / day","summary":"An accessibility specialist runs a manual audit and produces a written report.","pros":["Bespoke recommendations from a human expert","Defensible methodology for high-stakes procurement"],"cons":["Engagements typically run 8 to 20 days","The report is a snapshot in time. Re-engaging every 6 to 12 months is standard","Often beyond SMB budget"],"verdict":"The right choice for enterprises with regulator-facing exposure."},{"tag":"Recommended for SMBs","title":"AccessibilityRef","price":"€499 to €999 / year","summary":"Self-serve tooling and documentation generators with continuous monitoring built in.","pros":["Produces the Annex IV technical file and the EU Declaration of Conformity","Accessibility statement generator in seven EU languages","5-year audit retention with tamper-evident Evidence Vault"],"cons":["Self-serve, so you need to follow the guided flow yourself","Not a substitute for legal counsel on disputed enforcement actions"],"verdict":"Right for the 95% of SMBs that need defensible documentation without a consulting engagement."}],"footnote":"Pricing reflects typical EU market rates as of 2026-05. AccessibilityRef pricing is the listed annual subscription. Alternative pricing varies by vendor and engagement scope.","pros_label":"What it gives you","cons_label":"What it doesn't","verdict_label":"Verdict"},"compare":{"heading":"Compare plans","col_feature":"Feature","col_free":"Free","col_starter":"Starter","col_pro":"Pro","rows":[{"label":"Anonymous single-URL diagnostics","free":true,"starter":true,"pro":true},{"label":"Verified domains","free":false,"starter":true,"pro":true},{"label":"Accessibility Statement Generator (7 languages)","free":false,"starter":true,"pro":true},{"label":"EU Declaration of Conformity, Annex IV","free":false,"starter":true,"pro":true},{"label":"All 24 sector checklists","free":false,"starter":true,"pro":true},{"label":"Evidence Vault, basic record storage","free":false,"starter":true,"pro":true},{"label":"Whole-Site Scanner with sampling","free":false,"starter":false,"pro":true},{"label":"Batch analysers (Heading, Alt-Text, Focus Order Pro)","free":false,"starter":false,"pro":true},{"label":"AI Cross-Page Dedup","free":false,"starter":false,"pro":true},{"label":"Compliance Report Builder + VPAT Editor + RFP Pack","free":false,"starter":false,"pro":true},{"label":"Evidence Vault, sealed export + immutable hash chain","free":false,"starter":false,"pro":true}]},"default_faq":[{"q":"What is the difference between Starter and Pro?","a":"Starter (€499/yr) covers a single-site business: document generators, the Statement Wizard, all 24 sector checklists, and basic Evidence Vault storage. Pro (€999/yr) adds the Whole-Site Scanner, batch analysers, AI cross-page dedup, the full immutable Evidence Vault with sealed export, and three verified domains. Pro is the right choice if you own several properties or need defensible evidence for procurement, regulators, or large tenders."},{"q":"Is there a monthly plan?","a":"No. Both tiers are annual subscriptions billed via Stripe. You can cancel any time from your Stripe customer portal and you will not be re-billed."},{"q":"Why an annual subscription instead of a one-time audit?","a":"Because a website that was compliant in January is not necessarily compliant in June. Pages get rebuilt, partners ship new embeds, marketing adds new PDFs. If a market-surveillance authority asks for your evidence, they want to see ongoing monitoring, not a frozen snapshot from a year ago. The annual subscription covers continuous tracking and the rolling five-year audit retention that the EAA requires."},{"q":"Do you offer refunds?","a":"Yes. 30-day refund on either tier, no questions asked. After that, the 7-day Pro trial is the way to try before buying."},{"q":"Can I upgrade from Starter to Pro later?","a":"Yes. The upgrade is one click in your Stripe customer portal; the price difference is prorated for the remainder of the year. All your existing Evidence Vault entries stay intact."},{"q":"Is this legal advice?","a":"No. AccessibilityRef generates legal-grade evidence and documentation. It is not legal advice. For binding legal opinions, consult a qualified accessibility attorney in your jurisdiction."}]}},"privacy":{"meta":{"title":"Privacy Policy","description":"How AccessibilityRef and Keogh Ltd collect, use, and protect your personal data under GDPR."},"heading":"Privacy Policy","last_updated":"Last updated: 9 April 2026","intro_p1":"This policy explains how Keogh Ltd, trading as AccessibilityRef (\"we\", \"us\", \"our\"), collects, uses, and protects personal data in accordance with the EU General Data Protection Regulation (GDPR), Regulation (EU) 2016/679.","intro_p2":"This policy applies to the AccessibilityRef website (accessibilityref.eu).","s1":{"heading":"1. Data Controller","legal_entity_label":"Legal entity:","legal_entity":"Keogh Ltd","trading_as_label":"Trading as:","trading_as":"AccessibilityRef","address_label":"Registered address:","address":"Travessa Dom Sancho I 25, 3030-461 Coimbra, Portugal","website_label":"Website:","website":"Accessibilityref.eu","enquiries_label":"Data protection enquiries:","enquiries_link":"Contact form","dpo":"We have not appointed a Data Protection Officer as we do not meet the thresholds under GDPR Article 37. For all data protection enquiries, please use our contact page.","authority":"Lead supervisory authority: Comissão Nacional de Proteção de Dados (CNPD), Portugal. You also have the right to lodge a complaint with the supervisory authority in your country of residence."},"s2":{"heading":"2. Data We Collect","account":"Account data: Email address and password (hashed) when you register. Stored securely via Firebase Authentication (Google LLC).","payment":"Payment data: When purchasing Pro tools, payment is processed by Stripe Inc. We receive only a transaction confirmation and your email. We do not store card details.","usage":"Usage data: Page views and tool interactions via Google Analytics 4. This data is anonymised and aggregated, and only collected with your consent.","ai":"AI tool input data: When using AI-powered tools (ARIA Assistant, Alt Text Prompter), the content you submit is sent to Anthropic's Claude API for processing. We do not store this input data after the response is returned. Under Anthropic's API terms, inputs and outputs are not used to train their models. Anthropic may retain data for up to 30 days for trust and safety purposes per their data retention policy."},"s3":{"heading":"3. Legal Basis for Processing","contract":"Contract (Art. 6(1)(b)): Processing your account and payment data to provide the service you purchased.","legitimate":"Legitimate interests (Art. 6(1)(f)): Security, fraud prevention, crash reporting, and improving the platform and app.","consent":"Consent (Art. 6(1)(a)): Advertising and analytics cookies, only after you click \"Accept All\" in the cookie banner."},"s4":{"heading":"4. Third-Party Processors","col_processor":"Processor","col_purpose":"Purpose","col_location":"Location","firebase":"Firebase (Google LLC)","firebase_purpose":"Authentication and database","firebase_location":"USA (SCCs)","ga4":"Google Analytics 4","ga4_purpose":"Usage analytics (consent required)","ga4_location":"USA (SCCs)","stripe":"Stripe Inc.","stripe_purpose":"Payment processing","stripe_location":"USA (SCCs)","resend":"Resend Inc.","resend_purpose":"Transactional email (account and payment notifications)","resend_location":"USA (SCCs)","anthropic":"Anthropic PBC","anthropic_purpose":"AI processing for ARIA Assistant and Alt Text Prompter tools","anthropic_location":"USA (SCCs)","vercel":"Vercel Inc.","vercel_purpose":"Website hosting","vercel_location":"USA/EU (SCCs)","zoho":"Zoho Corporation B.V.","zoho_purpose":"In-page support chat (Zoho SalesIQ), loaded only with marketing-cookie consent","zoho_location":"EU (Netherlands / Ireland data centres)","sccs_note":"SCCs = Standard Contractual Clauses, ensuring GDPR-compliant international transfers."},"s5":{"heading":"5. Cookies & Analytics","body":"We use Google Analytics 4 to understand how the site is used. Analytics cookies are only set after you click \"Accept All\" in the cookie banner. We implement Google Consent Mode v2, which signals your consent choice to Google. We do not display advertisements. See our Cookie Policy for full details."},"s6":{"heading":"6. Your Rights Under GDPR","rights":[{"right":"Right of Access","desc":"Request a copy of your personal data."},{"right":"Right to Rectification","desc":"Correct inaccurate data we hold."},{"right":"Right to Erasure","desc":"Request deletion of your account and data."},{"right":"Right to Restriction","desc":"Limit how we process your data."},{"right":"Right to Portability","desc":"Receive your data in a machine-readable format."},{"right":"Right to Object","desc":"Object to processing based on legitimate interests."},{"right":"Right to Withdraw Consent","desc":"Withdraw advertising consent at any time via the cookie banner."},{"right":"Right to Lodge a Complaint","desc":"Contact your national data protection authority."}],"exercise":"To exercise any right, use our contact form. We will respond within 30 days as required by GDPR Article 12(3).","erasure_heading":"Right to erasure (Article 17), how to exercise it","erasure_body":"You can submit a deletion request at any time from the Privacy & Your Data section of your account page. Every request is reviewed manually by our admin team and actioned within 7 days under normal circumstances, and within 30 days at the latest as required by GDPR Article 12(3). You will receive an email confirmation once the deletion has been completed. The manual review step exists to verify identity, check for active billing disputes or legal holds, and prevent malicious deletions of compromised accounts.","erasure_deleted":"What is deleted: your profile, saved checklists and assessments, team membership, and Firebase Authentication record.","erasure_retained":"What is retained (and why): anonymised Stripe billing records (with your name and email removed) are retained for the period required by EU tax law, typically 7 years, under the legal obligation exemption in GDPR Article 17(3)(b). These records cannot be linked back to you.","erasure_export":"You can also use the Export your data button on the same page to download a JSON copy of all personal data we hold (Article 20)."},"s7":{"heading":"7. Data Retention","account":"Account data: Retained while your account is active. Deleted within 7 days of an approved deletion request, and within 30 days at the latest (GDPR Article 12(3)).","payment":"Payment records: Anonymised Stripe billing records (with personally identifying fields removed) are retained for 7 years to comply with EU tax and accounting obligations under GDPR Article 17(3)(b).","analytics":"Analytics data: Retained for 14 months (Firebase Analytics default), then automatically purged.","audit":"Audit logs: Server-side audit logs of administrative actions and security events are retained for 12 months for security and compliance purposes."},"s8":{"heading":"8. Security","body":"We implement appropriate technical and organisational measures to protect your personal data against unauthorised access, alteration, disclosure, or destruction. All data in transit is encrypted via TLS. Authentication credentials are hashed and never stored in plain text. Access to production systems is restricted to authorised personnel only."},"s9":{"heading":"9. Children","body":"AccessibilityRef is a professional B2B service not directed at children. We do not knowingly collect personal data from anyone under 16 years of age. If we become aware that we have collected data from a child, we will delete it promptly. If you believe a child has provided us with personal data, please contact us."},"s10":{"heading":"10. Automated Decision-Making","body":"We do not use automated decision-making or profiling that produces legal effects or similarly significant effects on you, as described in GDPR Article 22. AI-powered tools (ARIA Assistant, Alt Text Prompter) process content you voluntarily submit and return suggestions, they do not make decisions about you or your legal status."},"s_analytics":{"heading":"10a. Usage Analytics and Refund Counter","intro":"Beyond the records described in section 2, we keep a first-party log of how the site is used. This section is fully transparent: we record more than you might expect, but we keep it ourselves, we do not share it with third-party trackers, and you can opt out of the analytics portion through the cookie banner.","what_h":"What we record","what_view":"view: each page render — path, locale, your account tier if signed in, a rotating session id.","what_action":"action: primary button clicks — signup, sign in, checkout, running a tool. Each event has a short name and the page it fired on.","what_api":"api_call: every server-side API call our app makes on your behalf — route, HTTP method, response status, duration.","what_export":"export: each deliverable document you generate (statements, conformity declarations, technical files, VPATs, compliance reports). Recorded server-side, attributable to your account.","what_aicall":"ai_call: each successful invocation of an AI feature (alt-text generator, ARIA generator, document analysers).","what_ack":"signup_acknowledgement: a record at account creation showing you saw the refund-cap terms — version, caps, a hashed and truncated IP address.","why_h":"Why we record it","why_body":"Product improvement (which tools are used, which workflows succeed) and dispute resolution. Our 30-day refund promise ends once you have generated 3 full deliverables or made 2 AI-assisted generations — the export and AI-call records back that policy if a refund is ever disputed.","basis_h":"Legal basis","basis_body":"Essential events (api_call recorded server-side, export, ai_call, signup_acknowledgement, refund_counter, refund_request) run on our legitimate interest in service delivery, fraud prevention, and dispute resolution (GDPR Article 6(1)(f)). Analytics events (view and action beacons) run on your consent through the cookie banner (Article 6(1)(a)); rejecting the analytics bucket disables them. Marketing cookies (Google Ads partnership) are independently consented.","retention_h":"Retention","retention_body":"Raw events expire automatically after 90 days. Daily aggregate rollups (counts of events per tool per day with cardinality counts of unique users) are kept indefinitely but contain no personal identifiers. Refund-counter records and signup acknowledgements are kept for the duration of your account plus any dispute window.","rights_h":"Your rights","rights_body":"Section 5 of this policy lists the GDPR rights that apply to all data we hold. Specifically for analytics: you can opt out of analytics beacons through the cookie banner. You can request export or deletion of every record above through your account settings — deletion removes raw events, refund counters, signup acknowledgements, and refund requests within the SLA in section 5."},"s11":{"heading":"11. Changes to This Policy","body":"We may update this policy periodically. Material changes will be communicated by email and/or prominent notice on the site at least 14 days before taking effect. Where changes affect our legal basis for processing or introduce new processing activities, we will seek your consent where required by law."},"related":{"heading":"Related Policies","terms":"Terms of Service","cookies":"Cookie Policy","accessibility":"Accessibility Statement"}},"project-picker":{"label":"Project","noProjects":"No projects yet","createFirst":"+ Create your first project","create":"+ New project","manage":"Manage projects…","active":"Active","untitled":"Untitled project","modal":{"title":"Manage projects","close":"Close","createPlaceholder":"Project name (e.g. Globalbay Q2 2026 audit)","createButton":"Create","switchTo":"Switch to","rename":"Rename","delete":"Delete","confirmDelete":"Delete \"{name}\"? Its metadata is gone for good, exports already in your Vault are unaffected.","saved":"Saved","saving":"Saving…"}},"roles":{"meta":{"title":"Accessibility Role Guides, EAA Compliance by Stakeholder","description":"Role-based accessibility compliance guides for developers, designers, product managers, legal teams, and more. EAA self-assessment guidance tailored to your responsibilities."},"hero":{"title":"Stakeholder Pathways","description":"Targeted implementation guidance for every role in your organization to ensure EAA compliance."},"card":{"cta":"View Guide →"},"cards":{"developer":{"title":"Developer Compliance Pathway","description":"What engineers building EAA-compliant software actually need to know, with the clauses, the patterns, and the tools to verify the work."},"designer":{"title":"Designer Compliance Pathway","description":"Visual and interaction design decisions that determine whether your product is usable, and whether it meets the EAA. Half of accessibility is decided before a single line of code is written."},"qa":{"title":"QA & Tester Compliance Pathway","description":"How to plan, run, and document accessibility testing in a way that survives a regulator audit. Automated tools are part of it. They are not most of it."},"product":{"title":"Product Manager Compliance Pathway","description":"Treating accessibility as a regulatory requirement and a product quality requirement at the same time. Both are now real, both have deadlines, and both land on the PM's desk."},"legal":{"title":"Legal & Compliance Pathway","description":"What in-house counsel and external advisors need to know about the EAA: the obligations, the documentation, the liability allocation, and the things that will land on your desk when something goes wrong."},"content":{"title":"Content Creator Pathway","description":"Writing, editing, and publishing in a way that works for everyone. Most accessibility wins for content people are decided in the draft, not in the CMS."},"procurement":{"title":"Procurement & RFP Pathway","description":"How to buy accessible technology, evaluate vendor claims, and protect your organisation from inheriting someone else's compliance debt."},"support":{"title":"Customer Support Pathway","description":"Help desks, contact channels, and self-service documentation are part of the EAA scope. The user who can't get into the product is the one who calls support, and support has to be reachable too."},"hardware":{"title":"Hardware Engineer Pathway","description":"Physical product accessibility under the EAA: ATMs, ticket machines, payment terminals, e-readers, smart TVs, and the consumer hardware that connects to all of them."},"executive":{"title":"Executive Briefing (C-Suite)","description":"What boards, CEOs, CFOs, and General Counsel need to know about the EAA in less than ten minutes. The numbers, the obligations, the decisions only you can make."},"accessibility-lead":{"title":"Accessibility Lead Pathway","description":"The person inside the organisation who owns accessibility end-to-end. Sits between product, engineering, design, legal, and the executive layer. Translates between all five."},"compliance-officer":{"title":"Compliance Officer Pathway","description":"The day-to-day owner of the conformity assessment, the audit register, and the regulator-facing paper trail. Different from Legal: less interpretation, more operational discipline."}}},"sector-checklist":{"header":{"descriptionSuffix":"{count} checkpoints across {categories} categories.","legalBasis":"Legal basis:","externalLinkSuffix":"↗"},"form":{"orgNameLabel":"Organisation Name","orgNamePlaceholder":"Your company name","trialBadge":"Trial, Upgrade to export","trialBadgeTitle":"Upgrade to Pro to export documents","markRemainingNa":"Mark {count} remaining as N/A","markRemainingConfirm":"Mark {count} unanswered items as N/A? You can change individual items afterwards.","reset":"Reset","resetConfirm":"Clear all answers, notes, and progress? This cannot be undone."},"autosave":"Progress auto-saved in your browser","progress":{"label":"Progress: {answered} / {total} items","pass":"Pass: {count}","partial":"Partial: {count}","fail":"Fail: {count}","na":"N/A: {count}"},"vault":{"saved":"✓ Saved to Evidence Vault","error":"⚠ Save failed, sign in as Pro","saving":"Saving…","save":"Save to Vault"},"tabs":{"results":"Results","failsSuffix":"{count}F"},"item":{"weightCritical":"Critical","weightMajor":"Major","weightMinor":"Minor","testWith":"Test with {tool} →","viewSource":"View source ↗","hideDetails":"Hide details ▲","showDetails":"How to test & common failures ▼","howToTest":"How to Test","commonFailures":"Common Failures","notesLabel":"Notes / Evidence","notesPlaceholder":"Document your observations, evidence, URLs, screenshots taken, or remediation plan..."},"answers":{"pass":"Pass","partial":"Partial","fail":"Fail","na":"N/A"},"results":{"heading":"Assessment Results","passLabel":"Pass","partialLabel":"Partial","failLabel":"Fail","naLabel":"N/A","complianceScore":"Compliance Score","issuesHeading":"{category}, Issues","failPrefix":"FAIL:","partialPrefix":"PARTIAL:","notesPrefix":"Notes:"},"exportPanel":{"summary":"{answered}/{total} items assessed · {pct}% score · {fail} {failNoun}","failNounSingular":"Fail","failNounPlural":"Fails","labels":{"organisation":"Organisation","checklist":"Checklist","itemsAssessed":"Items assessed","itemsAssessedValue":"{answered} of {total}","score":"Score","complianceScore":"Compliance score","passing":"Passing","partial":"Partial","failing":"Failing","notApplicable":"Not applicable","notAssessed":"Not assessed","categories":"Categories","fail":"Fail","na":"N/A","notSet":"(not set)","categorySummary":"{pct}% ({pass}P / {fail}F / {na}NA)"},"json":{"label":"Download JSON","hint":"Answers + notes + stats"}},"docx":{"overallResult":"Overall Result","rows":{"organisation":"Organisation","checklist":"Checklist","score":"Score","itemsAssessed":"Items assessed","itemsAssessedValue":"{answered} / {total}","pass":"Pass","partial":"Partial","fail":"Fail","na":"N/A"},"coverParagraph":"This checklist covers {count} checkpoints across {categories} categories, evaluating compliance with the European Accessibility Act (Directive (EU) 2019/882) and EN 301 549 V3.2.1.","failedHeading":"Failed checkpoints, required remediation","failedIntroSingular":"{count} checkpoint marked as Fail. Each row shows the reference, severity, requirement, guidance and operator notes.","failedIntroPlural":"{count} checkpoints marked as Fail. Each row shows the reference, severity, requirement, guidance and operator notes.","tableHeaders":{"ref":"Ref","severity":"Severity","requirement":"Requirement","status":"Status","guidance":"Guidance","notes":"Notes"},"categoryHeading":"{label} ({pct}%)","statusLabels":{"pass":"Pass","partial":"Partial","fail":"FAIL","na":"N/A","notAssessed":"Not Assessed"},"weightLabels":{"critical":"Critical","major":"Major","minor":"Minor"},"method":"Method","methodParagraph":"Manual sector-specific compliance review of {count} checkpoints across {categories} categories. Each checkpoint was assessed as Pass, Partial, Fail, N/A, or left as Not Assessed, with operator notes. Mapped to the European Accessibility Act (Directive (EU) 2019/882, Annex I) and EN 301 549 V3.2.1 (2021-03) where applicable. This record forms part of the Annex IV Technical File required under EAA Article 13."},"blank":{"sectionHeading":"Send this checklist to a vendor","sectionDescription":"Download a blank Word document or open a printable view to send this checklist to a third party (vendor, agency, external auditor) for completion. The blank version contains every checkpoint with empty Pass / Partial / Fail / N/A boxes and a Notes column.","downloadButton":"Download blank Word version","downloadingButton":"Preparing…","printButton":"Open print view","titleSuffix":"Blank checklist","bannerLine1":"Blank checklist for offline completion.","bannerLine2":"Tick one box per row. Add comments and evidence references in the Notes column as needed.","printHeaderKicker":"Blank checklist, printable form","printFooter":"Generated from accessibilityref.eu/tools/{toolId}","notesColumn":"Notes / Evidence"}},"technical-file":{"meta":{"title":"Annex IV Technical File Builder","description":"Bundle every Evidence Vault record into one EAA Annex IV Technical Documentation pack, manifest, machine-readable index, and the original files."},"auth":{"loading":"Loading…","signInRequired":"Sign in required","signInHelp":"Please sign in to build a Technical File.","signInButton":"Sign in","proRequired":"Pro required","proHelp":"Building an Annex IV Technical File requires a Pro subscription. Your Evidence Vault starts filling up automatically the moment you upgrade.","proPricingButton":"See pricing →"},"header":{"back":"← Back to dashboard","title":"Annex IV Technical File Builder","lede":"Bundle every evidence record from your Evidence Vault into a single EAA Annex IV Technical Documentation pack. The builder groups your records by Annex IV section, attaches the original files, and produces a reviewable ZIP you can hand to a market surveillance authority or your legal team."},"fields":{"productName":"Product name *","productNamePlaceholder":"Acme Checkout v4","manufacturer":"Manufacturer *","manufacturerPlaceholder":"Acme Digital Services GmbH","model":"Model","modelPlaceholder":"Web, Premium tier","productVersion":"Product version","productVersionPlaceholder":"4.2.0","ceDate":"CE / declaration date","contactEmail":"Contact email","contactEmailPlaceholder":"Accessibility@…","notes":"Build notes (optional)","notesPlaceholder":"Scope of this technical file, exclusions, reviewers, anything you want preserved in the pack."},"build":{"button":"Build Technical File ZIP →","building":"Building pack…","footnoteHtml":"The pack contains manifest.docx (human-readable Annex IV manifest), manifest.json (machine-readable), and evidence/<section>/… folders holding every inline-stored file from your Evidence Vault. Records whose file was too large to store inline are listed by audit ID in the manifest with a note."},"review":{"heading":"Before you hand this to a regulator","body":"This is legal-grade evidence assembled from your own test runs, not a formally certified conformity assessment. Have a qualified accessibility professional review the pack before submitting it to a market surveillance authority."},"errors":{"buildFailed":"Pack build failed","signInToBuild":"Sign in to build a Technical File."}},"terms":{"meta":{"title":"Terms of Service","description":"Terms and conditions for using AccessibilityRef's tools and services."},"heading":"Terms of Service","last_updated":"Last updated: 25 March 2026","intro":"By accessing or using accessibilityref (\"the Service\"), you agree to be bound by these Terms of Service. Please read them carefully before using the Service or any of its tools.","s1":{"heading":"1. Service Description","p1":"Accessibilityref provides an online platform of self-assessment tools, reference guides, and compliance resources to assist organisations with digital accessibility under WCAG 2.2, the European Accessibility Act (EAA, Directive 2019/882), and related regulatory frameworks.","p2":"The tools offered, including but not limited to the Guided EAA Self-Assessment, Accessibility Statement Wizard, Compliance Report Builder, WCAG Audit Checklist, and associated pro tools, are designed to support internal self-assessment and awareness. They are aids to help teams understand accessibility requirements, identify potential gaps, and document their efforts. They are not a substitute for a formal legal audit or professional legal advice.","p3":"Free tools are available without registration. Pro tools and Teams features require a paid subscription."},"s2":{"heading":"2. Subscription, Pro & Teams Plans","p1":"Pro tool access is provided on a recurring annual subscription basis, processed by Stripe Inc. Your subscription renews automatically each year unless cancelled before the renewal date.","cancellation_label":"Cancellation:","cancellation":"You may cancel your subscription at any time from your account settings. Cancellation takes effect at the end of the current billing period. No partial refunds are issued for unused time within a billing period.","refunds_label":"Refunds:","refunds":"Due to the immediate digital delivery of access, all sales are final and non-refundable unless required by applicable consumer protection law.","eu_rights_label":"EU Consumer Rights:","eu_rights":"EU consumers have a 14-day withdrawal right. However, by confirming access to a digital product immediately upon purchase, you expressly consent to waive this right per Article 16(m) of Directive 2011/83/EU.","price_label":"Price changes:","price":"We will give at least 30 days' notice of any change to subscription pricing before it takes effect on renewal.","teams_label":"Teams plans:","teams":"Seats are allocated per subscription. The account holder (team admin) is responsible for ensuring invited members comply with these terms. Seat counts include the team admin."},"s3":{"heading":"3. Accounts","p1":"You must provide accurate information when creating an account. You are responsible for maintaining the security of your credentials and for all activity under your account.","p2":"We reserve the right to suspend or terminate accounts that violate these terms or applicable law."},"s4":{"heading":"4. Nature of Self-Assessment Tools, Important Limitations","p1":"The tools provided by accessibilityref are intended to assist with internal self-assessment only. They help teams learn about accessibility requirements, conduct preliminary checks, and generate supporting documentation for internal use.","p2":"Reports and outputs are not legally certified documents. Any report, statement, checklist, score, or assessment output generated by the Service, including but not limited to the Guided EAA Self-Assessment, Compliance Report Builder, Accessibility Statement Wizard, WCAG Checklist, and Whole-Site Scanner, should be treated as a working document for internal review.","p3":"Legal review is strongly recommended. Before relying on any output for regulatory compliance, public disclosure, procurement, or legal purposes, you should have the output reviewed and confirmed as acceptable by a qualified legal representative or independent accessibility auditor with appropriate professional qualifications.","p4":"Self-checks are your responsibility. If you are not engaging formal legal or specialist advisory services, you are responsible for conducting your own verification of the accuracy, completeness, and applicability of any output to your specific circumstances. Automated tool outputs cannot account for every edge case, organisational context, or jurisdiction-specific nuance.","p5":"While every effort is made to keep reference content, WCAG criteria mappings, country-specific enforcement body information, and legal summaries accurate and up to date, accessibility law is evolving. You should always verify against official sources and current legislation."},"s5":{"heading":"5. Disclaimer of Liability, Self-Assessment Risk","p1":"All risks associated with the use of self-assessment tools, reports, and outputs from this Service lie solely with the internal assessor and the organisation conducting the assessment.","p2":"Accessibilityref, its developers, directors, employees, contractors, and contributors accept zero liability for any loss, damage, penalty, fine, regulatory action, legal claim, reputational harm, or any other consequence, direct, indirect, incidental, or consequential, arising from:","list":["Reliance on any assessment output, report, score, or recommendation produced by the Service;","Inaccuracy, incompleteness, or out-of-date information in tool outputs or reference content;","A failure to achieve, demonstrate, or maintain regulatory compliance with the EAA, WCAG, or any other accessibility standard;","Enforcement action, fines, or legal proceedings brought against you by a national enforcement body or third party;","Decisions made on the basis of any generated accessibility statement, compliance report, or audit checklist;","Any other use of or reliance on the Service or its outputs."],"p3":"This disclaimer applies regardless of whether accessibilityref was advised of the possibility of such losses. Nothing in these terms excludes liability that cannot be excluded by law (such as for fraud or death/personal injury caused by negligence), but accessibilityref's liability is otherwise limited to the maximum extent permitted under applicable law.","p4":"Our total aggregate liability for any single claim shall not exceed the total subscription fees paid by you to accessibilityref in the 12 months preceding the event giving rise to the claim."},"s6":{"heading":"6. Acceptable Use","intro":"You may not:","list":["Reproduce, resell, or redistribute paid tool outputs commercially without written permission.","Attempt to circumvent access controls or reverse-engineer Pro features.","Use the Service for unlawful purposes or in violation of any applicable regulation.","Scrape or systematically download reference data at scale.","Present any output from the Service as a formally certified or legally verified compliance assessment without independent professional verification."]},"s7":{"heading":"7. Intellectual Property","body":"All content on this site, including reference data compilations, tool interfaces, and written analysis, is the property of accessibilityref or its licensors. Normative legal text (WCAG, EAA directives) remains in the public domain under their respective licences. You may reference and cite our content for non-commercial purposes with attribution."},"s8":{"heading":"8. Governing Law","body":"These terms are governed by the laws of the European Union and the Republic of Ireland. Any disputes shall be subject to the exclusive jurisdiction of the Irish courts, without prejudice to your rights as an EU consumer under the laws of your country of residence."},"s9":{"heading":"9. Warranty Disclaimer","body":"The Service is provided \"as is\" and \"as available\" without warranties of any kind, whether express, implied, or statutory, including but not limited to implied warranties of merchantability, fitness for a particular purpose, accuracy, or non-infringement. We do not warrant that the Service will be uninterrupted, error-free, or free of harmful components. Nothing in this section excludes warranties that cannot be excluded under applicable EU consumer law."},"s10":{"heading":"10. Indemnification","body":"You agree to indemnify and hold harmless Keogh Ltd, its directors, employees, and contractors from and against any claims, damages, losses, liabilities, costs, and expenses (including reasonable legal fees) arising from: (a) your use of the Service; (b) your violation of these Terms; or (c) your reliance on any output from the Service in a manner inconsistent with the limitations described in Section 4."},"s11":{"heading":"11. Termination","body":"We may suspend or terminate your account for material breach of these Terms, with 14 days' written notice where practicable. Upon termination: (a) your access to Pro tools will cease immediately; (b) you may export your data within 30 days of notice via your account dashboard; (c) no refund is due for termination caused by your breach; (d) provisions that by their nature should survive (Sections 4, 5, 9, 10, 13, 14) shall survive termination."},"s12":{"heading":"12. Force Majeure","body":"We shall not be liable for any failure or delay in performing our obligations where such failure or delay results from circumstances beyond our reasonable control, including but not limited to natural disasters, pandemics, war, terrorism, government actions, power failures, internet disruptions, or third-party service outages (Firebase, Stripe, Vercel, Anthropic)."},"s13":{"heading":"13. Severability","body":"If any provision of these Terms is held to be invalid or unenforceable by a court of competent jurisdiction, the remaining provisions shall continue in full force and effect. The invalid provision shall be modified to the minimum extent necessary to make it valid and enforceable."},"s14":{"heading":"14. Entire Agreement","body":"These Terms, together with the Privacy Policy and Cookie Policy, constitute the entire agreement between you and Keogh Ltd regarding the Service, and supersede all prior agreements, representations, and understandings."},"s15":{"heading":"15. Changes to These Terms","body":"We may update these terms periodically. Material changes will be communicated by email and/or prominent notice on the site at least 14 days before taking effect. Where changes affect your subscription terms or payment obligations, we will seek your affirmative acceptance on your next login. Continued use of the Service after the notice period for non-material changes constitutes acceptance."},"summary":{"heading":"Summary, Not Legal Advice","body":"Accessibilityref tools are self-assessment aids. Outputs are not legally certified. Always have compliance-critical documents reviewed by a qualified legal or accessibility professional. All assessment risk sits with the assessor."},"related":{"heading":"Related Policies","privacy":"Privacy Policy","cookies":"Cookie Policy","contact":"Contact Us"}},"tool-guides":{"touch-target-tester":{"intro":"This tool checks whether the buttons, links, and form controls on your website or app are large enough to tap with a finger. Targets that are too small are a barrier for people with motor disabilities.","whenToUse":"Use this when you have a mobile website or app, or any website that can be viewed on a touchscreen. If your product is only used on desktop with a mouse and keyboard, this check is lower priority.","applicability":"Mobile apps, touch-enabled websites, responsive web. Less applicable to keyboard-only desktop interfaces.","steps":[{"title":"Enter your element size","body":"Type the width and height (in pixels) of the button, link, or control you're checking. If you're not sure, right-click it in your browser, choose Inspect, and look for the width/height values in the Styles panel."},{"title":"Read the verdict","body":"The tool immediately tells you whether the element passes the minimum legal requirement (24px, WCAG 2.2 AA) or the recommended comfortable size (44px for iOS, 48px for Android)."},{"title":"Use the spacing exception if needed","body":"If your buttons are small but spread apart, WCAG allows an exception. Enter the gap between adjacent targets; the tool will tell you whether the exception applies."},{"title":"Get the CSS fix","body":"Switch to the CSS Fix tab to get the exact code that will fix the issue. Copy and send it to your developer, no expertise needed."},{"title":"Export your evidence","body":"Scroll to the Export section and download a record of your test. This becomes part of your EAA Technical File."}]},"readability":{"intro":"This tool analyses text from your website and tells you how difficult it is to read. EU accessibility law requires that content doesn't exceed the reading level of a typical lower-secondary school student.","whenToUse":"Use this on any public-facing text: product descriptions, terms and conditions, help pages, error messages. Especially important for banking, insurance, and e-commerce.","applicability":"All websites and apps with text content. Particularly important for financial services, legal documents, and consumer-facing copy.","steps":[{"title":"Paste your text or enter a URL","body":"Either paste the text you want to check into the box, or enter your page URL so the tool can fetch the content automatically."},{"title":"Read the score","body":"The tool shows a Flesch Reading Ease score and a grade level. Aim for Grade 8 or below (reading ease above 60) for most public-facing content."},{"title":"Check the highlighted problem areas","body":"Long sentences and difficult words are highlighted. These are the first things to simplify."},{"title":"Rewrite and re-test","body":"Edit your content, shorter sentences, simpler words, then paste it back in to confirm the score has improved."},{"title":"Export your evidence","body":"Download the results to include in your Technical File."}]},"contrast-palette":{"intro":"This tool tests your entire brand colour palette for contrast in one go, rather than checking pairs one at a time. It tells you which colour combinations are safe to use for text and which will fail accessibility requirements.","whenToUse":"Use this early in a design project when defining your brand palette, or when auditing an existing design system. It's faster than the Contrast Checker for testing many combinations.","applicability":"All websites and apps with visual content. Essential for designers and anyone producing branded materials.","steps":[{"title":"Enter your brand colours","body":"Type in your hex colour codes (e.g. #005A9C). Add as many colours as are in your palette. You can find hex codes in your brand guidelines or by using a browser colour picker on your existing site."},{"title":"Read the matrix","body":"The tool shows a grid of every colour combination. Green cells pass; red cells fail. The ratio shown must be at least 4.5:1 for normal text and 3:1 for large text."},{"title":"Identify safe pairs","body":"Note which foreground/background combinations are always safe. These are the ones your designers should use for text."},{"title":"Flag problem combinations","body":"Any red cells should be removed from your approved colour usage guidelines for text. They can still be used for decorative elements."},{"title":"Export your evidence","body":"Download the matrix as part of your accessibility evidence."}]},"compliance-report":{"intro":"This tool bundles all your accessibility evidence, test results from other tools, checklist completions, and notes, into a single formatted document. This is your EAA Technical File.","whenToUse":"Use this after you have completed testing with the other tools and want to compile everything into one document for your records, for a client, or for a regulator.","applicability":"All product types covered by the EAA.","steps":[{"title":"Complete your other tool assessments first","body":"Run the relevant checklist(s), scanners, and calculators. The compliance report pulls together evidence you've generated elsewhere."},{"title":"Open this tool and review the evidence summary","body":"The tool shows which evidence has been saved to your Evidence Vault. Check that all required sections are present."},{"title":"Add any manual notes or context","body":"Use the notes fields to explain any partial assessments, known issues, or remediation timelines."},{"title":"Generate the report","body":"Click Generate Report. The tool produces a formatted Word or PDF document ready to send to stakeholders or store in your compliance records."}]},"screen-reader-simulator":{"intro":"This tool shows you what a screen reader, the software used by blind people to navigate the web, would read out on any given page. It's a quick way to spot missing descriptions and confusing navigation without needing to install a real screen reader.","whenToUse":"Use this when you want to check whether your content makes sense to blind users, or when you're reviewing a page after development to catch common screen reader issues.","applicability":"All websites and web apps. Especially important for pages with images, forms, tables, and interactive components.","steps":[{"title":"Enter the URL of the page to test","body":"Type the full web address of the page you want to check. The page must be publicly accessible (not behind a login for first-time use)."},{"title":"Read the simulated output","body":"The tool shows the order and content that a screen reader would announce. Look for '[image]' with no description, '[button]' with no label, or confusing link text like 'click here'."},{"title":"Check the heading structure","body":"Screen reader users navigate by headings. Check that headings are present and in a logical order (H1 → H2 → H3)."},{"title":"Note any issues","body":"Make a list of elements with missing or unclear labels. These are your development tasks."},{"title":"Export your evidence","body":"Download the simulation results as part of your accessibility testing record."}]},"mobile-checker":{"intro":"This tool runs a set of automated accessibility checks on a mobile page view of your website, checking for issues that are specific to small screens and touch interfaces.","whenToUse":"Use this when your website or app is used on mobile devices. Run it alongside the desktop scanning tools for full coverage.","applicability":"Mobile websites, responsive web apps, progressive web apps.","steps":[{"title":"Enter your page URL","body":"Type the web address of the page you want to check. The tool will load it at a mobile screen size."},{"title":"Review the issues list","body":"The tool lists accessibility problems found. Each issue includes what failed and where on the page it was found."},{"title":"Prioritise by severity","body":"Critical and serious issues should be fixed first. These are likely to block disabled users entirely."},{"title":"Share with your developer","body":"Export the results or copy the issue list and send to the person responsible for development."},{"title":"Re-test after fixes","body":"Run the tool again after development changes to confirm the issues are resolved."}]},"colour-blindness":{"intro":"This tool shows you what your website looks like to people with different types of colour blindness. Around 1 in 12 men and 1 in 200 women have some form of colour blindness.","whenToUse":"Use this when reviewing your design or when checking whether you rely on colour alone to convey information (e.g. Red = error, green = success). If the meaning is lost in the simulation, you need to add an icon or text label.","applicability":"All websites and apps with colour-coded information, charts, maps, status indicators, or form validation.","steps":[{"title":"Enter your page URL or upload a screenshot","body":"Type the address of the page or upload a screenshot."},{"title":"Select a colour blindness type","body":"Try Deuteranopia (the most common type) first, then Protanopia and Tritanopia."},{"title":"Check colour-only information","body":"Look at error messages, success states, charts, and maps. If the meaning disappears or is ambiguous, you have an issue."},{"title":"Identify fixes needed","body":"For anything that relies on colour alone, add a text label, icon, or pattern. For example, add an ✗ icon to error messages alongside the red colour."},{"title":"Export your evidence","body":"Download the simulation screenshots for your Technical File."}]},"aria-assistant":{"intro":"This tool generates the ARIA (Accessible Rich Internet Applications) code that developers need to make interactive components accessible to screen readers. You describe what you want; it produces the code.","whenToUse":"Use this when a developer is building a custom component, a dropdown menu, modal dialog, tab panel, carousel, that doesn't use a standard HTML element. Standard HTML elements like buttons and inputs don't need ARIA.","applicability":"Web applications with custom interactive components. Not needed for simple content pages.","steps":[{"title":"Describe the component","body":"Select the component type from the list (e.g. Modal dialog, tab panel, combobox)."},{"title":"Configure the options","body":"Answer the questions about how the component behaves, does it open/close, does it have a label, is it required?"},{"title":"Copy the generated code","body":"The tool outputs the ARIA attributes to add to your HTML. Copy and paste directly to your developer."},{"title":"Test after implementation","body":"After the developer adds the code, use the Screen Reader Simulator to verify it's working correctly."}]},"banking-checklist":{"intro":"This is an EAA compliance checklist for online banking services, internet banking platforms, and financial apps. It maps requirements from EAA Annex I Section IV (banking services) and WCAG 2.1 AA.","whenToUse":"Use this if your product is a consumer banking service, payment service, or financial app covered by the EAA. Work through it methodically, you don't need to complete it in one session.","applicability":"Online banking, payment apps, investment platforms, insurance portals, any consumer-facing financial service.","steps":[{"title":"Work through each section","body":"The checklist is grouped by topic. Tick each item Pass, Fail, or N/A. Add notes where needed, especially for Fails."},{"title":"Use N/A for items that don't apply","body":"Not every item will apply to your product. Mark those N/A to keep track of what you've considered."},{"title":"Record evidence for each item","body":"Where you mark an item Pass, note how you tested it (e.g. 'tested with NVDA screen reader on Chrome')."},{"title":"Address Fails before your deadline","body":"Failed items are your remediation backlog. Prioritise them by user impact and legal risk."},{"title":"Export your completed checklist","body":"Download the checklist as a Word document. This is a core document in your EAA Technical File."}]},"transport-checklist":{"intro":"This is an EAA compliance checklist for transport and passenger services, ticketing websites, journey planners, real-time information services, and booking platforms.","whenToUse":"Use this if your product provides passenger transport services, ticket sales, or travel information to consumers in the EU.","applicability":"Rail, bus, ferry, and air ticketing; journey planners; real-time departure boards; transport apps.","steps":[{"title":"Work through each section","body":"The checklist is grouped by topic. Tick each item Pass, Fail, or N/A."},{"title":"Use N/A for items that don't apply","body":"Mark items N/A where your product doesn't have that feature, for example, if you don't sell tickets, skip the payment accessibility items."},{"title":"Record how you tested each Pass","body":"Note the test method, automated scan, manual keyboard test, screen reader test, etc."},{"title":"Prioritise Fails","body":"Focus first on items that directly prevent disabled users from completing a journey booking."},{"title":"Export for your Technical File","body":"Download the completed checklist as a Word document."}]},"ecommerce-checklist":{"intro":"This is an EAA compliance checklist for online retail and e-commerce, product listings, basket and checkout flows, account pages, and customer communications.","whenToUse":"Use this if your product includes any e-commerce functionality: browsing products, adding to a basket, making a payment, or managing an order.","applicability":"Online shops, marketplaces, subscription services, booking engines with payment.","steps":[{"title":"Work through each section","body":"Sections cover: product pages, search, basket, checkout, payment, order confirmation, and account management."},{"title":"Pay extra attention to the checkout flow","body":"The checkout is the highest-risk area for accessibility failures and the most likely area regulators will scrutinise."},{"title":"Mark N/A where applicable","body":"For example, if you don't offer guest checkout, mark those items N/A."},{"title":"Document your test evidence","body":"For each Pass, note what you tested and how. Screenshots or screen recordings are ideal."},{"title":"Export for your Technical File","body":"Download the completed checklist."}]},"ebook-checklist":{"intro":"This is an EAA compliance checklist for e-books and digital publications, EPUB files, PDF books, and digital magazines. It covers how content must be structured and tagged so assistive technology can read it.","whenToUse":"Use this if you publish e-books, digital textbooks, or digital magazines distributed through e-readers or reading apps.","applicability":"EPUB publications, digital textbooks, online magazines, accessible PDFs sold or distributed to consumers.","steps":[{"title":"Work through each section","body":"Sections cover: document structure, images and captions, tables, navigation, metadata, and reading order."},{"title":"Pay attention to image alt text","body":"Every image that conveys information needs a text description. Decorative images should be marked as such."},{"title":"Check your table of contents","body":"The publication must have a navigable table of contents that works with screen readers."},{"title":"Test with an e-reader","body":"Open the publication in a real e-reader app (such as Apple Books or Thorium Reader) and navigate using assistive technology."},{"title":"Export for your Technical File","body":"Download the completed checklist."}]},"software-checklist":{"intro":"This is an EAA compliance checklist for desktop and web software, applications that users install or access via a browser to perform tasks. It covers keyboard navigation, screen reader support, and visual design.","whenToUse":"Use this if your product is a desktop application, a web application used for work tasks, or any software that consumers purchase or subscribe to.","applicability":"Desktop applications (Windows, macOS), web applications, SaaS products sold to consumers or businesses.","steps":[{"title":"Work through each section","body":"Sections cover: keyboard access, screen reader compatibility, visual design, error handling, and documentation."},{"title":"Test keyboard navigation first","body":"Try using your application with only the keyboard (no mouse). Can you reach every function? Is focus visible at all times?"},{"title":"Test with a screen reader","body":"Use NVDA (free, Windows) or VoiceOver (built into Mac) to navigate your application. Does everything make sense?"},{"title":"Record your test results","body":"Note what you tested and what you found. Screenshots and videos are useful evidence."},{"title":"Export for your Technical File","body":"Download the completed checklist."}]},"hardware-checklist":{"intro":"This is an EAA compliance checklist for physical hardware products, devices with screens, controls, or interfaces that users interact with. It covers physical accessibility, screen readability, and audio/visual cues.","whenToUse":"Use this if your product is a physical device: a terminal, kiosk, ATM, set-top box, phone, computer, or any hardware sold to consumers.","applicability":"Consumer electronics, kiosks, ATMs, self-service terminals, set-top boxes, computers, tablets.","steps":[{"title":"Work through each section","body":"Sections cover: physical controls, displays, audio output, connectivity for assistive devices, and documentation."},{"title":"Check physical accessibility","body":"Can users in wheelchairs reach all controls? Is the screen at an accessible height? Are controls distinguishable by touch?"},{"title":"Check audio and visual alternatives","body":"Does the device provide both audio and visual feedback for critical events? Can the volume be adjusted?"},{"title":"Test with assistive technology","body":"If your device has a screen, can it be operated with an external keyboard or switch device?"},{"title":"Export for your Technical File","body":"Download the completed checklist."}]},"terminal-checklist":{"intro":"This is an EAA compliance checklist for self-service terminals, kiosks, ATMs, ticket machines, check-in desks, and interactive information points used in public spaces.","whenToUse":"Use this if your product is any kind of self-service machine that members of the public interact with directly.","applicability":"ATMs, ticket vending machines, airport check-in kiosks, supermarket self-checkouts, information kiosks, parking meters.","steps":[{"title":"Work through each section","body":"Sections cover: reachability, screen visibility, audio output, tactile features, and alternative service provision."},{"title":"Check reach and clearance","body":"Controls and screen must be reachable from a seated position (wheelchair user). Minimum knee clearance: 700mm height, 600mm depth."},{"title":"Check audio output","body":"Does the terminal have a headphone socket for private audio? Is speech output available for screen content?"},{"title":"Check tactile cues","body":"Does the keypad have a tactile marker on the 5 key? Are control labels in Braille where applicable?"},{"title":"Export for your Technical File","body":"Download the completed checklist."}]},"generic-ict-checklist":{"intro":"This is a general EAA compliance checklist for ICT products and services that don't fit neatly into the other specific categories. It covers the core EN 301 549 requirements applicable to all digital products.","whenToUse":"Use this if your product is a digital product or service covered by the EAA but not covered by one of the more specific checklists (banking, e-commerce, transport, etc.).","applicability":"General ICT products: software, cloud services, digital tools, and services without a more specific checklist.","steps":[{"title":"Confirm this is the right checklist","body":"First check whether a more specific sector checklist applies to your product. If not, this one covers the baseline requirements."},{"title":"Work through each section","body":"Sections follow the EN 301 549 standard structure: general, user interface, visual design, and documentation."},{"title":"Mark N/A for non-applicable items","body":"Many items will not apply to every product type. Mark these N/A with a brief note."},{"title":"Document your test method for each Pass","body":"Note whether each item was tested automatically, manually, or through user testing."},{"title":"Export for your Technical File","body":"Download the completed checklist."}]},"mobile-app-checklist":{"intro":"This is an EAA compliance checklist for native mobile apps, iOS and Android applications. It covers screen reader support, touch target sizes, system font scaling, and platform-specific accessibility APIs.","whenToUse":"Use this if your product includes a native iOS or Android app (as opposed to a mobile website, which is covered by other checklists).","applicability":"Native iOS apps, native Android apps, cross-platform apps built with React Native or Flutter.","steps":[{"title":"Work through each section","body":"Sections cover: VoiceOver (iOS) and TalkBack (Android) support, touch targets, text scaling, colour contrast, and focus management."},{"title":"Test with VoiceOver or TalkBack","body":"Enable the screen reader on a real device and navigate your app using swipe gestures. Every interactive element must be announced correctly."},{"title":"Test large text","body":"Go to Settings → Accessibility → Larger Text and set text size to maximum. Does your app layout break? Does text get cut off?"},{"title":"Test with one finger only","body":"Try completing key journeys using only one finger. Are there any two-finger gestures with no alternative?"},{"title":"Export for your Technical File","body":"Download the completed checklist."}]},"video-media-checklist":{"intro":"This is an EAA compliance checklist for video and audio content, media players, video libraries, podcasts, and on-demand streaming services.","whenToUse":"Use this if your product includes video or audio content that users can play, or if you operate a media player.","applicability":"Video streaming, on-demand audio, podcast platforms, video players embedded on websites.","steps":[{"title":"Work through each section","body":"Sections cover: captions, audio description, transcripts, media player controls, and sign language."},{"title":"Check for captions on all videos","body":"Every video that contains speech must have accurate captions. Auto-generated captions (e.g. YouTube auto-captions) do not meet the standard unless reviewed and corrected."},{"title":"Check your media player controls","body":"Can the play, pause, volume, and caption toggle controls be used with a keyboard alone? Are they large enough to tap on mobile?"},{"title":"Check for audio description","body":"Videos with important visual information that is not explained in the audio need an audio description track."},{"title":"Export for your Technical File","body":"Download the completed checklist."}]},"voice-comms-checklist":{"intro":"This is an EAA compliance checklist for voice communication services, VoIP apps, video calling, and real-time messaging platforms.","whenToUse":"Use this if your product enables users to make voice or video calls, or send real-time text messages.","applicability":"VoIP apps, video conferencing, messaging apps with voice/video features.","steps":[{"title":"Work through each section","body":"Sections cover: real-time text (RTT) support, screen reader compatibility in the calling interface, caption support, and emergency calling."},{"title":"Check emergency call access","body":"If your service allows calls, can users reach emergency services (112 in the EU)? This is a specific EAA requirement."},{"title":"Check your calling interface","body":"Can a screen reader user answer, mute, end a call, and switch between audio and speaker using keyboard commands?"},{"title":"Check real-time text support","body":"EAA requires that voice communication services support RTT for users who cannot use voice."},{"title":"Export for your Technical File","body":"Download the completed checklist."}]},"support-docs-checklist":{"intro":"This is an EAA compliance checklist for support documentation, help articles, user manuals, FAQs, and instructional content provided alongside a product.","whenToUse":"Use this when auditing the documentation and help content for your product. EAA requires that support materials are as accessible as the product itself.","applicability":"Help centres, user guides, knowledge bases, in-product tutorials, FAQs.","steps":[{"title":"Work through each section","body":"Sections cover: document structure, image alt text, table accessibility, reading level, and PDF accessibility."},{"title":"Check your help articles","body":"Open several help articles and test: Do they have clear headings? Do images have descriptions? Are tables readable by screen reader?"},{"title":"Check PDFs","body":"If you provide PDF manuals, run them through the Document Auditor or PDF Checklist tools to check their accessibility."},{"title":"Check reading level","body":"Run representative help articles through the Readability tool. Aim for Grade 8 or below."},{"title":"Export for your Technical File","body":"Download the completed checklist."}]},"emergency-checklist":{"intro":"This is a checklist for emergency and safety information provided digitally, emergency alerts, safety warnings, evacuation instructions, and crisis communications.","whenToUse":"Use this if your product distributes emergency information, safety notices, or real-time alerts to the public.","applicability":"Emergency alert systems, safety communication platforms, building management systems with digital notices.","steps":[{"title":"Work through each section","body":"Sections cover: multi-channel alerts, text alternatives for audio alerts, screen reader compatibility, and language clarity."},{"title":"Check that alerts are not audio-only","body":"Emergency alerts must have a visible text component. Users who are deaf or have hearing loss must be able to receive the alert."},{"title":"Check that alerts are not visual-only","body":"Equally, users who are blind or have low vision must be able to receive alerts through audio or vibration."},{"title":"Check reading level of alert text","body":"In an emergency, clear simple language is critical. Aim for the simplest possible phrasing."},{"title":"Export for your Technical File","body":"Download the completed checklist."}]},"supply-chain-checklist":{"intro":"This checklist helps you assess the accessibility compliance of digital products in your supply chain, third-party tools, embedded services, and components built by other suppliers.","whenToUse":"Use this when evaluating a supplier's accessibility commitment, procuring new software, or auditing components you embed in your product (e.g. A payment gateway, a chat widget, a map embed).","applicability":"Procurement teams, product managers evaluating third-party components, compliance teams reviewing supply chain risk.","steps":[{"title":"Identify the third-party components in your product","body":"List every external tool, embed, widget, or API that end users interact with directly."},{"title":"Request ACR/VPAT from each supplier","body":"Ask each supplier for their Accessibility Conformance Report (ACR) or VPAT. This is their formal accessibility statement."},{"title":"Work through this checklist for each supplier","body":"Evaluate each supplier's documentation and test any areas of concern yourself."},{"title":"Document gaps","body":"If a supplier cannot provide an ACR or has known accessibility gaps, document this and your plan to address it."},{"title":"Export for your Technical File","body":"Download the completed checklist."}]},"functional-criteria-checklist":{"intro":"This checklist covers the functional performance criteria from EN 301 549 and the EAA, the accessibility requirements expressed in terms of what a disabled user must be able to DO, rather than specific technical requirements.","whenToUse":"Use this as a cross-check alongside your sector checklist, or when a technical requirement is unclear and you want to reason about it from the user's perspective.","applicability":"All EAA-covered products. Useful for bridging the gap between technical specs and real-world user outcomes.","steps":[{"title":"Work through each functional criterion","body":"Each item describes a user task a disabled person must be able to complete: see, hear, operate, understand, navigate."},{"title":"Test with real users if possible","body":"Functional criteria are best validated with disabled users. Even one or two informal tests with a screen reader user or someone with low vision provides valuable insight."},{"title":"Cross-reference with your sector checklist","body":"Any Fails here should also be recorded in your sector checklist as Fails."},{"title":"Document your evidence","body":"Note how you tested each criterion and what you found."},{"title":"Export for your Technical File","body":"Download the completed checklist."}]},"cognitive-checklist":{"intro":"This checklist covers cognitive accessibility, how easy your product is to understand, learn, and use for people with cognitive disabilities such as dyslexia, ADHD, memory difficulties, or learning disabilities.","whenToUse":"Use this for any consumer-facing product, especially those used by the general public or vulnerable groups. Cognitive accessibility improvements benefit all users, not just those with disabilities.","applicability":"All consumer-facing websites and apps. Especially important for financial services, healthcare, and public services.","steps":[{"title":"Work through each section","body":"Sections cover: plain language, consistent navigation, error prevention, memory demands, and distraction."},{"title":"Read your content aloud","body":"A quick way to spot overly complex language. If you stumble while reading it, users will too."},{"title":"Check your forms","body":"Do forms explain what's expected before the user makes a mistake? Are error messages in plain language? Does the form retain data after an error?"},{"title":"Check navigation consistency","body":"Navigation menus and common actions should appear in the same place on every page."},{"title":"Export for your Technical File","body":"Download the completed checklist."}]},"matterhorn-checklist":{"intro":"This checklist tests PDF documents against the Matterhorn Protocol, the industry standard for accessible PDFs (PDF/UA). It covers the tagging, reading order, and structure that screen readers need to read PDF content correctly.","whenToUse":"Use this when you produce PDF documents that users download or receive, reports, contracts, invoices, user guides, forms. Regular web pages don't need this; it's for PDF files specifically.","applicability":"PDFs distributed to consumers: reports, contracts, guides, forms, statements.","steps":[{"title":"Open the PDF you want to test","body":"Have the PDF file ready. The tool will guide you through each Matterhorn checkpoint."},{"title":"Work through each checkpoint","body":"For each checkpoint, you'll need to check the PDF in Adobe Acrobat Pro or another PDF accessibility checker, then record your result here."},{"title":"Pay special attention to tagging","body":"PDFs must be 'tagged', a hidden layer of structure that screen readers use. An untagged PDF is completely inaccessible. Check Tags in Acrobat's Accessibility panel."},{"title":"Check reading order","body":"Use Acrobat's Read Out Loud feature to confirm text is read in the correct order."},{"title":"Export for your Technical File","body":"Download the completed checklist."}]},"multilingual-checklist":{"intro":"This checklist covers accessibility requirements for websites and apps that serve content in multiple languages, checking that language changes are marked correctly, right-to-left scripts are handled, and language-specific formatting is accessible.","whenToUse":"Use this if your product is available in more than one language, or if it displays content in a language other than the page's primary language.","applicability":"Multilingual websites and apps, products serving RTL languages (Arabic, Hebrew), products with user-generated content in multiple languages.","steps":[{"title":"Work through each section","body":"Sections cover: language declaration, inline language changes, RTL support, locale-specific formatting, and translation quality."},{"title":"Check your HTML lang attribute","body":"Every page must declare its primary language in the attribute. Screen readers use this to select the correct voice."},{"title":"Check inline language switches","body":"If a page contains text in a different language (e.g. A French phrase on an English page), that text must be wrapped in a span with lang='fr'."},{"title":"Check RTL pages if applicable","body":"Right-to-left pages must set dir='rtl' on the html or body element and use logical CSS properties."},{"title":"Export for your Technical File","body":"Download the completed checklist."}]},"pdf-checklist":{"intro":"This checklist helps you assess the accessibility of PDF files you produce or distribute, checking for tags, reading order, colour contrast, form fields, and other requirements.","whenToUse":"Use this when you create or commission PDF documents that customers, users, or the public will receive. Applies to contracts, guides, statements, invoices, and any other distributed PDF.","applicability":"All PDFs distributed to consumers as part of a product or service covered by the EAA.","steps":[{"title":"Open the PDF in Adobe Acrobat Pro","body":"The Accessibility Checker in Acrobat Pro is the standard tool for PDF accessibility testing. The free Reader does not include this feature."},{"title":"Run the Accessibility Checker","body":"Go to Tools → Accessibility → Full Check. Fix the issues flagged by the checker first."},{"title":"Work through this checklist","body":"This checklist covers additional items the automated checker may miss, including reading order and colour contrast."},{"title":"Test with a screen reader","body":"Use Acrobat's Read Out Loud feature or NVDA to verify the PDF reads correctly from start to finish."},{"title":"Export for your Technical File","body":"Download the completed checklist."}]},"at-interop-checklist":{"intro":"This checklist tests whether your product works correctly with common assistive technologies, screen readers, switch devices, voice control software, and magnification tools.","whenToUse":"Use this when you want to verify real-world compatibility with assistive technology, or when your sector checklist has items about AT interoperability.","applicability":"All digital products: websites, web apps, desktop software, mobile apps.","steps":[{"title":"Work through each AT combination","body":"The checklist is organised by AT type: screen readers (NVDA+Chrome, JAWS+Chrome, VoiceOver+Safari), voice control (Dragon, Windows Speech Recognition), and switch access."},{"title":"Test each combination methodically","body":"For each AT and browser combination, attempt the key user journeys: navigate to a page, fill in a form, complete a transaction."},{"title":"Record what you find","body":"Note any AT and browser combination where a task fails or produces confusing output."},{"title":"Prioritise NVDA+Chrome and VoiceOver+Safari","body":"These are the most widely used combinations. Fix issues here first."},{"title":"Export for your Technical File","body":"Download the completed checklist."}]},"burden-calculator":{"intro":"This tool helps you assess whether achieving full accessibility compliance would be a 'disproportionate burden' on your organisation. The EAA allows limited exemptions where the cost of compliance genuinely outweighs the benefit, but the bar is high and the exemption must be formally documented.","whenToUse":"Use this only when you believe a specific accessibility requirement would be genuinely unachievable due to financial or technical constraints. Do not use it to avoid compliance generally.","applicability":"Any EAA-covered product or service where a specific requirement may create disproportionate burden.","steps":[{"title":"Enter your organisation's financial details","body":"The calculation requires your annual turnover, net profit, and number of employees. These determine your financial capacity."},{"title":"Describe the specific requirement","body":"Name the specific accessibility requirement you believe may be disproportionate. Be precise, 'full WCAG compliance' is not a valid burden claim; a specific technical feature may be."},{"title":"Enter the estimated cost of compliance","body":"Get a realistic quote for implementing the requirement. Use the tool's cost breakdown fields."},{"title":"Review the assessment","body":"The tool calculates whether your claimed burden is likely to be accepted by a regulator. If the score is low, reconsider whether a full exemption is justified."},{"title":"Export your assessment","body":"Download the full assessment document. You must file this formally and review it annually."}]},"fine-calculator":{"intro":"This tool estimates the potential financial penalties your organisation could face for EAA non-compliance, based on your revenue and the likely severity of violations. It is a planning tool, not a legal prediction.","whenToUse":"Use this when building a business case for accessibility investment, or when assessing the financial risk of delayed compliance.","applicability":"Any organisation selling products or services in EU markets covered by the EAA.","steps":[{"title":"Enter your annual EU revenue","body":"Use the revenue from EU sales/services that fall within EAA scope."},{"title":"Select your violation type","body":"The tool has pre-set scenarios ranging from minor technical violations to systematic exclusion of disabled users."},{"title":"Review the estimated range","body":"The tool shows a low/high range based on known penalty structures from EU member state transpositions."},{"title":"Use the output for business cases","body":"Export the estimate to support a business case for accessibility budget, or to brief senior leadership on compliance risk."}]},"debt-calculator":{"intro":"This tool quantifies your 'accessibility debt', the estimated cost of fixing all known accessibility issues in your product. It helps you understand the scale of remediation work needed and communicate it to stakeholders.","whenToUse":"Use this after completing an accessibility audit and you have a list of issues. It converts that list into an estimated remediation cost and effort.","applicability":"Organisations that have completed an audit and want to build a remediation roadmap or business case.","steps":[{"title":"Import or enter your audit findings","body":"Upload a CSV from an audit tool, or manually enter issues with their severity and estimated fix complexity."},{"title":"Set your hourly developer rate","body":"Enter the blended hourly cost of your development team (or agency rate if you're outsourcing fixes)."},{"title":"Review the debt estimate","body":"The tool calculates total hours and total cost, broken down by issue severity."},{"title":"Use the output for prioritisation","body":"Focus first on critical issues that have the most users impacted and the lowest fix cost (quick wins)."},{"title":"Export the remediation plan","body":"Download the prioritised issue list and cost estimate for your compliance programme."}]},"roi-calculator":{"intro":"This tool calculates the return on investment from accessibility improvements, showing the financial upside from reaching more customers, reducing support costs, and avoiding fines.","whenToUse":"Use this when making the business case for accessibility investment to leadership or a finance team.","applicability":"All organisations, especially those that need to justify accessibility spend to non-technical stakeholders.","steps":[{"title":"Enter your product's user base size","body":"Total monthly active users or annual customers."},{"title":"Enter your average revenue per user","body":"Annual revenue divided by user count is a good approximation."},{"title":"Review the estimated addressable market","body":"Around 1 in 6 people have a disability. The tool shows the additional revenue from making your product accessible to that group."},{"title":"Add your compliance investment cost","body":"Enter the estimated cost of accessibility improvements (use the Debt Calculator output for this)."},{"title":"Review the ROI summary","body":"The tool shows payback period and 3-year return. Export this for your business case presentation."}]},"eaa-ready-quiz":{"intro":"This is a short readiness quiz that helps you understand where your organisation stands on EAA compliance. It asks about your product type, current accessibility practices, and known gaps.","whenToUse":"Use this at the start of your compliance journey to get a quick sense of where you are and what you need to focus on. It's a starting point, not a substitute for a full audit.","applicability":"Any organisation beginning their EAA compliance journey.","steps":[{"title":"Answer each question honestly","body":"The quiz only takes a few minutes. There are no wrong answers, it's designed to help you, not judge you."},{"title":"Review your readiness score","body":"The tool produces a score and a traffic-light summary by category (legal, technical, process)."},{"title":"Read the recommended next steps","body":"Based on your answers, the tool suggests which tools and checklists to start with."},{"title":"Share with your team","body":"Export the summary to share with colleagues who need to understand the compliance gap."}]},"conformity-generator":{"intro":"This tool generates your EU Declaration of Conformity, the formal legal document that declares your product meets EAA requirements. It is a required document for all EAA-covered products.","whenToUse":"Use this once you have completed your compliance assessments and are confident your product meets the applicable requirements. Do not sign a Declaration of Conformity for a product that has known critical accessibility failures.","applicability":"All organisations with EAA-covered products that are ready to declare conformity.","steps":[{"title":"Enter your organisation details","body":"Legal name, address, and registration number of the manufacturer or service provider."},{"title":"Describe the product or service","body":"Product name, version, and the specific EAA Annex that applies to it."},{"title":"Select the standards applied","body":"Check off the standards you've assessed against: EAA, WCAG 2.1 AA, EN 301 549. Only tick standards you've actually verified."},{"title":"Enter signatory details","body":"Name and role of the person signing on behalf of the organisation. This is a legally binding declaration."},{"title":"Download and sign","body":"Download the generated document, have it reviewed by legal counsel, and sign. Store the original and include a copy in your Technical File."}]},"vpat-editor":{"intro":"This tool helps you create a VPAT (Voluntary Product Accessibility Template), also called an ACR (Accessibility Conformance Report). This is the standard document procurement teams and enterprise buyers use to assess the accessibility of software before purchasing.","whenToUse":"Use this when a customer, procurement team, or public sector buyer has asked for an ACR/VPAT, or when you want to proactively publish your accessibility conformance.","applicability":"Software products, SaaS applications, and any digital product sold through a procurement process.","steps":[{"title":"Select the correct VPAT template","body":"Choose WCAG 2.1 AA for most digital products. If you're selling to the US Federal Government, also complete the Section 508 columns."},{"title":"Work through each criterion","body":"For each WCAG success criterion, select: Supports, Partially Supports, Does Not Support, or Not Applicable. Add remarks explaining your assessment."},{"title":"Be accurate, not optimistic","body":"A VPAT that overclaims conformance is a legal liability. If a criterion partially fails, mark it Partially Supports."},{"title":"Add your testing methodology","body":"Describe how you tested (automated tools, manual testing, AT testing). This increases the report's credibility."},{"title":"Export and publish","body":"Download the completed VPAT. Publish it on your website and include it in procurement responses."}]},"legal-pack":{"intro":"This tool generates the legal documents you need to demonstrate EAA compliance to customers and regulators: your Accessibility Statement, Privacy Notice (accessibility data section), and Terms of Service addendum.","whenToUse":"Use this when preparing the legal documentation for EAA compliance, or when updating existing documents to reflect your accessibility commitments.","applicability":"All organisations with EAA-covered products that need legal documentation.","steps":[{"title":"Enter your organisation and product details","body":"Legal name, product name, and contact details for accessibility queries."},{"title":"Select which documents you need","body":"Choose from: Accessibility Statement (required by EAA Article 14), VPAT/ACR addendum, or full legal pack."},{"title":"Complete the compliance status fields","body":"Be accurate about your current conformance level. State any known issues and your remediation timeline."},{"title":"Review the generated documents","body":"Read through the output carefully. Have your legal team review the documents before publication."},{"title":"Publish and link from your footer","body":"The Accessibility Statement must be easily findable, link it from your website footer on every page."}]},"rfp-generator":{"intro":"This tool generates accessibility requirements you can paste into procurement documents, RFPs, ITTs, and supplier contracts. It ensures that any new software or digital service you buy must meet EAA requirements.","whenToUse":"Use this before issuing a procurement for any digital product or service, to ensure accessibility is a scored requirement, not an afterthought.","applicability":"Procurement teams, IT managers, and anyone commissioning digital work from external suppliers.","steps":[{"title":"Select your product category","body":"Choose the type of product or service you're procuring. Different categories have different specific requirements."},{"title":"Select your conformance level","body":"WCAG 2.1 AA is the standard minimum. Choose WCAG 2.2 AA for newer procurements."},{"title":"Customise the requirements","body":"Add any sector-specific requirements relevant to your organisation."},{"title":"Copy and paste into your procurement document","body":"The generated text is formatted for direct insertion into an RFP or ITT."},{"title":"Add to your supplier evaluation criteria","body":"Ensure accessibility is a scored category in your evaluation, not just a pass/fail gate."}]},"compliance-program":{"intro":"This tool helps you build a structured accessibility compliance programme, a roadmap with owners, timelines, and milestones for reaching and maintaining EAA compliance.","whenToUse":"Use this when setting up or formalising your accessibility compliance effort, particularly if you need to present a compliance programme to senior leadership or regulators.","applicability":"Organisations beginning or formalising their EAA compliance journey.","steps":[{"title":"Enter your EAA deadline and product scope","body":"Select your applicable EAA compliance date (most products: June 2025 for new; June 2030 for legacy) and list your in-scope products."},{"title":"Complete the maturity assessment","body":"Answer questions about your current practices to establish a baseline."},{"title":"Review the generated programme","body":"The tool produces a phased roadmap with recommended activities, milestones, and roles."},{"title":"Assign owners and dates","body":"Edit the programme to assign each activity to a real person with a real deadline."},{"title":"Export and track","body":"Download the programme as a spreadsheet or document. Review it quarterly and update as you make progress."}]},"provisional-assessment":{"intro":"This tool lets you quickly record your current accessibility status across the main EAA requirements, a snapshot assessment that takes 20–30 minutes and gives you a clear picture of your compliance gap.","whenToUse":"Use this at the start of your EAA compliance journey, or when you need a quick status update without running a full audit.","applicability":"All EAA-covered products and services.","steps":[{"title":"Work through each section quickly","body":"For each item, mark your best estimate: Compliant, Partially Compliant, Non-Compliant, or Not Assessed. This is a provisional assessment, precision comes later."},{"title":"Add brief notes where helpful","body":"A short note on each Partially Compliant or Non-Compliant item will help when you do the detailed work later."},{"title":"Review your overall picture","body":"The tool summarises your compliance status by category. This is your gap analysis."},{"title":"Use the results to prioritise","body":"Focus detailed work first on the highest-risk Non-Compliant items, those most likely to affect the largest number of disabled users."},{"title":"Export your assessment","body":"Download the provisional assessment. This is a useful baseline document for your compliance file."}]},"self-assessment":{"intro":"This is a full, guided self-assessment that takes you through all EAA requirements in detail. It is more thorough than the Whole-Site Scanner and produces a complete assessment record.","whenToUse":"Use this when you are ready to do a thorough compliance assessment, or when preparing your Technical File for submission. Allow 2–4 hours for a full product assessment.","applicability":"All EAA-covered products. Especially important for the full Technical File required before the EAA deadline.","steps":[{"title":"Work through each phase","body":"The assessment is divided into phases: scope confirmation, product classification, technical testing, and documentation review."},{"title":"Gather your evidence as you go","body":"For each item you mark Compliant, attach or note the evidence: test results, screenshots, audit reports."},{"title":"Do not rush","body":"A thorough self-assessment is more valuable than a fast incomplete one. It can be paused and resumed."},{"title":"Review the gap summary","body":"At the end, the tool generates a prioritised gap list. These are your actions before the EAA deadline."},{"title":"Export your full assessment","body":"Download the complete assessment as a Word document for your Technical File."}]},"biometric-matrix":{"intro":"This tool maps which biometric authentication methods (fingerprint, face ID, voice, iris) meet EAA requirements, and what alternative authentication must be provided for users who cannot use a given biometric.","whenToUse":"Use this if your product uses biometric authentication as a primary or secondary login method.","applicability":"Apps and services using fingerprint, face recognition, voice authentication, or iris scanning.","steps":[{"title":"Select the biometric methods your product uses","body":"Choose from the list: fingerprint, face ID, voice recognition, iris scan, vein pattern."},{"title":"Review the accessibility requirements for each","body":"The matrix shows which disabilities are excluded by each method and what alternatives are legally required."},{"title":"Check your alternative provision","body":"For each biometric method, confirm you offer a fully accessible alternative that doesn't require that biometric."},{"title":"Note any gaps","body":"Record any biometric methods where your alternative provision is missing or inadequate."},{"title":"Export your assessment","body":"Download the matrix for your Technical File."}]},"competitor-benchmark":{"intro":"This tool lets you compare your accessibility performance against named competitors or industry averages, using publicly available data and your own test results.","whenToUse":"Use this when you need to position your accessibility performance in a competitive context, for a business case, for marketing, or for a procurement response.","applicability":"Any organisation that wants to benchmark their accessibility investment relative to competitors or industry standards.","steps":[{"title":"Enter your product's accessibility score","body":"Use results from your completed checklists and scan tools to establish your score."},{"title":"Enter competitor URLs or scores","body":"Either enter competitor URLs for the tool to scan, or enter scores from publicly available accessibility reports."},{"title":"Review the comparison","body":"The tool produces a side-by-side comparison chart."},{"title":"Identify your competitive position","body":"Are you ahead, behind, or at parity? Use this to set your investment level."},{"title":"Export the benchmark report","body":"Download the comparison for use in presentations or procurement responses."}]},"metrics-dashboard":{"intro":"This tool tracks your accessibility metrics over time, compliance scores, issue counts, and remediation progress, so you can demonstrate continuous improvement.","whenToUse":"Use this once you have initial scan results and want to track progress as you fix issues. Useful for quarterly compliance reviews and reporting to leadership.","applicability":"Organisations with an ongoing accessibility improvement programme.","steps":[{"title":"Import your latest scan results","body":"Upload results from your scanning tools or enter issue counts manually."},{"title":"Set your baseline","body":"Your first import becomes the baseline. All subsequent imports are compared against it."},{"title":"Review the trend charts","body":"The dashboard shows issue counts over time by severity, and your overall compliance score trend."},{"title":"Add milestone markers","body":"Mark key dates: compliance deadline, major releases, remediation sprints."},{"title":"Export for reporting","body":"Download the dashboard as a PDF or slide-ready chart for leadership reports."}]},"readability-dashboard":{"intro":"This tool gives you a readability overview across multiple pages of your website at once, rather than checking one page at a time in the Readability tool. It shows your average reading level and highlights the most complex pages.","whenToUse":"Use this after running the Readability tool on individual pages and you want a portfolio view, or when you want to scan a whole section of your website quickly.","applicability":"Websites with substantial text content: financial services, healthcare, public services, legal services.","steps":[{"title":"Enter the URLs you want to analyse","body":"Paste in a list of page URLs, the tool fetches and analyses each one."},{"title":"Review the summary scores","body":"The dashboard shows average reading ease and grade level across all pages, plus a list sorted by most complex to least complex."},{"title":"Identify the worst pages","body":"Focus rewriting effort on the pages with the lowest reading ease scores and the highest traffic."},{"title":"Track improvement over time","body":"Re-run the analysis after rewriting content to confirm scores have improved."},{"title":"Export the overview","body":"Download the dashboard for your accessibility programme report."}]},"alt-text-prompter":{"intro":"This tool helps you write good alternative text (alt text) for images, the text description that screen readers read aloud to blind users in place of an image. It gives you prompts and examples for different types of images.","whenToUse":"Use this when you're adding or reviewing images on your website or app and aren't sure what to write for the alt text. Useful for content editors, marketers, and developers.","applicability":"Any website or app with images: product photos, charts, infographics, icons, diagrams.","steps":[{"title":"Select the type of image","body":"Choose from: informative image, decorative image, chart/graph, photo with people, logo, icon, complex infographic."},{"title":"Answer the prompts","body":"The tool asks questions about your specific image: What does it show? What does it communicate? Is it purely decorative?"},{"title":"Review the suggested alt text","body":"The tool generates suggested alt text based on your answers. Edit it to match your specific image."},{"title":"Apply the alt text","body":"Add the alt text to the img alt='' attribute in your HTML, or in your CMS's alt text field."},{"title":"For decorative images","body":"If an image is purely decorative (adds no information), use an empty alt attribute: alt=''. Never leave alt text missing entirely."}]},"badges":{"intro":"This tool generates accessibility compliance badges you can display on your website, showing customers and procurement teams your current conformance level (e.g. WCAG 2.1 AA Compliant).","whenToUse":"Use this once you have completed a formal accessibility assessment and are confident in your conformance claim. Do not display a badge for a level you have not verified.","applicability":"Any EAA-covered website or app that wants to publicly signal its accessibility commitment.","steps":[{"title":"Select your conformance level","body":"Choose the level you have verified: WCAG 2.1 A, WCAG 2.1 AA, WCAG 2.2 AA, or EAA Compliant."},{"title":"Enter your assessment date","body":"The badge should show when the assessment was last conducted. Badges expire, reassess at least annually."},{"title":"Choose badge style","body":"Select a badge style that suits your site's design."},{"title":"Copy the embed code","body":"Copy the generated HTML snippet and paste it into your website footer or accessibility statement page."},{"title":"Link the badge to your Accessibility Statement","body":"The badge should link to your published Accessibility Statement so users can see the details."}]},"banking-regulatory-crossref":{"intro":"This tool is a reference guide that maps EAA requirements to their counterparts in EU banking regulations, EBA guidelines, PSD2, GDPR, and AML requirements, helping banking compliance teams see the full regulatory picture.","whenToUse":"Use this when you need to understand how EAA accessibility requirements interact with other banking regulations your product must comply with.","applicability":"Banks, payment service providers, fintech companies, and their compliance teams.","steps":[{"title":"Select the EAA requirement you're researching","body":"Browse by EAA Annex section or search by keyword."},{"title":"Review the cross-reference table","body":"The tool shows related requirements from EBA, PSD2, and other applicable frameworks."},{"title":"Identify overlapping obligations","body":"Where requirements overlap, a single control or document can satisfy multiple regulatory obligations."},{"title":"Export the cross-reference","body":"Download the relevant sections for use in your compliance documentation."}]},"aria-reference":{"intro":"This is a reference guide for ARIA (Accessible Rich Internet Applications) attributes, the HTML attributes developers use to make interactive components accessible to screen readers. It's a lookup tool, not an automated checker.","whenToUse":"Use this when a developer or designer needs to know what ARIA attributes are available for a given component, what values they accept, and when to use them.","applicability":"Web developers and designers building interactive web components.","steps":[{"title":"Search for the component or attribute you need","body":"Search by component name (e.g. 'dialog', 'combobox') or attribute name (e.g. 'aria-expanded')."},{"title":"Read the usage guidance","body":"Each entry explains what the attribute does, when to use it, what values it accepts, and common mistakes."},{"title":"Check the code example","body":"Copy the example code as a starting point for your implementation."},{"title":"Test your implementation","body":"After implementing, test with a screen reader to confirm the attribute is being read correctly."}]},"checklist":{"intro":"This is a full WCAG 2.1 AA checklist covering all 50 success criteria. It's the most complete checklist on the platform and the foundation of a full accessibility audit.","whenToUse":"Use this when conducting a thorough accessibility audit of your product, or when you need to demonstrate compliance with WCAG 2.1 AA specifically. For EAA compliance, use the sector-specific checklists which include additional EAA requirements.","applicability":"All digital products: websites, web apps, mobile apps, desktop software.","steps":[{"title":"Work through each criterion","body":"The checklist is grouped by WCAG principle: Perceivable, Operable, Understandable, Strong. Work through each section systematically."},{"title":"Test each item before marking it","body":"Don't mark items as Pass based on assumption. Use the testing guidance provided for each criterion."},{"title":"Use N/A where criteria genuinely don't apply","body":"For example, if your product has no video content, mark the captions criteria N/A."},{"title":"Record evidence for Passes","body":"Note how you tested each Pass: automated tool, keyboard test, screen reader test, or visual inspection."},{"title":"Export your completed checklist","body":"Download the checklist as a Word document for your Technical File."}]},"component-library":{"intro":"This is a library of accessible UI component code examples, buttons, forms, modals, navigation menus, built to meet WCAG 2.1 AA. Developers can copy and use these as starting points.","whenToUse":"Use this when building new UI components and you want to start from an accessible baseline rather than retrofitting accessibility later.","applicability":"Web developers building new interfaces or component libraries.","steps":[{"title":"Browse or search for the component you need","body":"Find the component type: button, form input, modal, tabs, accordion, dropdown, etc."},{"title":"Review the accessibility notes","body":"Each component includes notes on which WCAG criteria it satisfies and why specific ARIA attributes are used."},{"title":"Copy the HTML and CSS","body":"Use the provided code as a starting point. Adapt visual styling to match your design system."},{"title":"Do not remove accessibility attributes","body":"The aria-* and role attributes are not optional. Removing them will break screen reader compatibility."},{"title":"Test after adapting","body":"After customising the component, re-test with a keyboard and screen reader to ensure nothing was broken."}]},"user-testing-log":{"intro":"This tool provides a structured template for recording accessibility user testing sessions, testing with real disabled users. User testing is the most valuable form of accessibility evidence.","whenToUse":"Use this when conducting user research sessions with disabled participants, or when reviewing usability testing that included accessibility tasks.","applicability":"Any product undergoing user testing that includes accessibility tasks or disabled participants.","steps":[{"title":"Set up the session record","body":"Enter the date, participant's disability and assistive technology used, browser, and OS."},{"title":"Record tasks and outcomes","body":"For each task you tested, record whether the participant completed it, any issues they encountered, and direct quotes."},{"title":"Note severity","body":"For each issue found, record severity: critical (task failure), serious (significant difficulty), moderate (workaround needed), or minor."},{"title":"Capture participant quotes","body":"Direct quotes from participants are powerful evidence in a Technical File and for development teams."},{"title":"Export your session log","body":"Download the completed log for your compliance file. Multiple logs build a strong evidence base."}]},"document-auditor":{"intro":"This tool audits Word documents (.docx) and PDFs for accessibility, checking structure, headings, alt text, colour contrast, and other requirements. It's for documents you produce and distribute, not web pages.","whenToUse":"Use this when checking documents you create in Word or export as PDFs: reports, guides, contracts, templates, forms.","applicability":"Word documents (.docx), PDFs, and other downloadable documents distributed to users.","steps":[{"title":"Upload your document","body":"Upload a.docx or PDF file. The tool analyses its structure and content."},{"title":"Review the issues list","body":"Issues are listed by type: missing alt text, poor heading structure, low contrast, untagged content."},{"title":"Fix issues in the source document","body":"Return to Word (or your PDF authoring tool) to fix the issues. Do not edit the PDF directly, fix the source and re-export."},{"title":"Re-upload to confirm fixes","body":"Upload the fixed document to confirm all issues are resolved."},{"title":"Export the audit report","body":"Download the audit results for your compliance file."}]},"cefr-checker":{"intro":"This tool checks whether text meets a specified CEFR (Common European Framework of Reference) language level, B1, B2, C1, etc. It's useful for plain-language compliance and for multilingual content quality assurance.","whenToUse":"Use this when you need to verify that text intended for a general audience meets a specific reading level, or when checking translations for language difficulty.","applicability":"Public-facing content, translated documents, consumer communications, legal notices, and accessibility statements.","steps":[{"title":"Paste your text","body":"Paste the text you want to assess into the input field."},{"title":"Select your target CEFR level","body":"Choose the level you're aiming for. B1 is appropriate for general public content; B2 for professional documents."},{"title":"Review the assessment","body":"The tool highlights words and phrases that are above the target level."},{"title":"Simplify highlighted content","body":"Replace complex words with simpler alternatives. The tool will update the score in real time."},{"title":"Export the assessment","body":"Download the results for your content quality record."}]}},"transitional-register":{"loading":"Loading,","unauthTitle":"Transitional register","unauthBody":"Sign in to maintain your EAA Article 32 transitional-period register.","signInLink":"Sign in","heading":{"title":"EAA Article 32 register","descriptionBody":"EAA Article 32(1) lets service contracts signed before 28 June 2025 keep running under the pre-EAA regime until they expire, and no later than {absoluteEnd}. This register documents the contracts you are treating as in scope. You will receive email reminders 90, 30, and 7 days before each expiry, and once on the day of expiry. Entries are auto-attached to your Technical File under 6, supporting evidence."},"entries":{"heading":"Register entries","addButton":"+ Add entry","empty":"No transitional contracts on file."},"entry":{"signedExpires":"Signed {signed}, expires {expiry}","ownerLabel":"Owner: {owner}","editButton":"Edit","deleteButton":"Delete"},"status":{"expired":"Expired","daysLeft":"{days, plural, one {# day left} other {# days left}}"},"form":{"editHeading":"Edit entry","newHeading":"New entry","cancel":"Cancel","submitBusy":"Saving,","submitEdit":"Save changes","submitNew":"Add to register","fields":{"contractRef":{"label":"Contract reference *","placeholder":"e.g. MSA-2024-08 with Acme GmbH"},"signedDate":{"label":"Signed date *","help":"Must be before 28 June 2025 to be Article 32 eligible."},"computedExpiry":{"label":"Computed expiry","help":"min(signedDate + 5 years, {absoluteEnd})."},"scope":{"label":"Scope / service description *"},"remediationOwner":{"label":"Remediation owner (optional)"},"notificationEmail":{"label":"Notification email (optional)","placeholder":"defaults to your account email"},"evidenceUrls":{"label":"Evidence URLs (one per line)"}}},"messages":{"entrySaved":"Entry saved."},"errors":{"loadFailed":"Fetch failed","saveFailed":"Save failed","deleteFailed":"Delete failed"},"confirmDelete":"Delete this transitional-register entry? The audit trail will retain a deletion record."},"trust-badge":{"meta":{"title":"Trust Badge, AccessibilityRef EAA Compliance Verification","description":"AccessibilityRef Trust Badge for EAA compliance verification. Demonstrate your accessibility self-assessment status to customers and regulators."}},"verticals":{"meta":{"title":"Industry Accessibility Hubs, EAA Compliance by Sector","description":"Industry-specific EAA compliance guides for e-commerce, banking, transport, healthcare, and more. Self-assessment tools and requirements tailored to your sector."},"hero":{"title":"Industry Hubs","description":"Sector-specific accessibility requirements mandated by the European Accessibility Act."},"card":{"cta":"Explore Requirements →"},"cards":{"banking":{"title":"Banking & Financial Services Hub","description":"Consumer banking, payment services, and financial products fall squarely within the European Accessibility Act's core scope. From online banking portals to ATM terminals, organisations must ensure every touchpoint is usable by people with visual, motor, cognitive, and hearing impairments."},"ecommerce":{"title":"E-Commerce & Retail Hub","description":"Online shops, marketplaces, and digital retail services must ensure every step of the purchase journey, from product discovery through to post-sale support, is accessible under the EAA. The Act covers both the retailer's own interface and any third-party payment gateways embedded within it."},"transport":{"title":"Transport Services Hub","description":"Rail, air, bus, and ferry operators providing passenger services with digital touchpoints must comply with the EAA. This covers ticketing websites and apps, real-time information systems, self-service kiosks, and any digital service used to book, manage, or access a journey."},"audiovisual":{"title":"Audiovisual Media Hub","description":"Video-on-demand platforms, streaming services, and broadcast catch-up services are explicitly named in the EAA. The Act requires not just accessible media players but end-to-end platform accessibility, from content discovery and search through playback controls, programme guides, and account management."},"telecom":{"title":"Telecommunications Hub","description":"Telecommunications services, voice telephony, messaging, video calling, and internet access services, are core EAA targets. The Act requires that disabled users can access the same communications services as non-disabled users, with equivalent quality, and that emergency services (112) remain fully accessible."},"ebooks":{"title":"E-Books & Publishing Hub","description":"E-books and dedicated e-reading software are explicitly listed in Annex I of the EAA. Publishers, distributors, and reading platform providers must ensure digital publications are born accessible, not retrofitted, and that the software used to read them never blocks accessibility features."},"public-sector":{"title":"Public Sector (WAD / EAA Overlap) Hub","description":"Public sector bodies are subject to both the Web Accessibility Directive (WAD, 2016/2102) and, where they offer EAA-scope services commercially or in competition with the private sector, the EAA. Understanding which regime applies, where they overlap, and how monitoring and enforcement interact is critical for compliance officers."},"education":{"title":"Higher Education & VLE Hub","description":"Universities, colleges, and higher education institutions operate in a complex landscape where the Web Accessibility Directive already applies to public institutions, and the EAA now extends obligations to private providers and third-party EdTech platforms. Virtual Learning Environments, student portals, assessment tools, and campus ICT must all be accessible."},"healthcare":{"title":"Healthcare Technology Hub","description":"Patient-facing digital health services, from GP booking portals to hospital patient apps, prescription management, and telehealth platforms, must be accessible under the EAA. Healthcare accessibility carries additional urgency: an inaccessible appointment booking system is not merely inconvenient, it creates a clinical risk for patients who cannot access timely care."},"gaming":{"title":"Gaming Industry Hub","description":"The gaming industry's EAA obligations focus on in-game communications services and digital storefronts rather than gameplay itself. Where voice chat, messaging, and community features function as electronic communications services, they fall within EAA scope. Platform stores selling games also have obligations as e-commerce services."}}},"wcag":{"meta":{"title":"WCAG 2.2 Standards Reference, All 87 Success Criteria","description":"Complete WCAG 2.2 reference with all 87 success criteria (Level A, AA, AAA). Verbatim W3C text, manual test scripts, and remediation guidance for EAA and EN 301 549 compliance self-assessment."},"page":{"meta_title":"WCAG 2.2 Reference, AccessibilityRef","meta_description":"All 87 WCAG 2.2 success criteria with verbatim W3C text, manual test scripts, and remediation guidance. Organised by the four POUR principles.","hero_eyebrow":"W3C · WCAG 2.2 (October 2023)","hero_title":"WCAG 2.2 Standards","hero_lede":"All 87 success criteria with verbatim W3C text, manual test scripts, and remediation guidance. Organised by the four POUR principles.","breadcrumb_home":"Home","breadcrumb_current":"WCAG 2.2","sidebar_principle":"Principle","sidebar_level":"Level","sidebar_level_label":"Level {level}","principles":{"p1_title":"Perceivable","p1_desc":"Information and user interface components must be presentable to users in ways they can perceive.","p2_title":"Operable","p2_desc":"User interface components and navigation must be operable.","p3_title":"Understandable","p3_desc":"Information and the operation of the user interface must be understandable.","p4_title":"Strong","p4_desc":"Content must be strong enough to be interpreted by many user agents, including assistive technologies."}},"sc_names":{"1.1.1":"Non-text Content","1.2.1":"Audio-only and Video-only (Prerecorded)","1.2.2":"Captions (Prerecorded)","1.2.3":"Audio Description or Media Alternative (Prerecorded)","1.2.4":"Captions (Live)","1.2.5":"Audio Description (Prerecorded)","1.3.1":"Info and Relationships","1.3.2":"Meaningful Sequence","1.3.3":"Sensory Characteristics","1.3.4":"Orientation","1.3.5":"Identify Input Purpose","1.4.1":"Use of Color","1.4.2":"Audio Control","1.4.3":"Contrast (Minimum)","1.4.4":"Resize Text","1.4.5":"Images of Text","1.4.10":"Reflow","1.4.11":"Non-text Contrast","1.4.12":"Text Spacing","1.4.13":"Content on Hover or Focus","2.1.1":"Keyboard","2.1.2":"No Keyboard Trap","2.1.4":"Character Key Shortcuts","2.2.1":"Timing Adjustable","2.2.2":"Pause, Stop, Hide","2.3.1":"Three Flashes or Below Threshold","2.4.1":"Bypass Blocks","2.4.2":"Page Titled","2.4.3":"Focus Order","2.4.4":"Link Purpose (In Context)","2.4.5":"Multiple Ways","2.4.6":"Headings and Labels","2.4.7":"Focus Visible","2.4.11":"Focus Not Obscured (Minimum)","2.4.12":"Focus Not Obscured (Improved)","2.4.13":"Focus Appearance","2.5.1":"Pointer Gestures","2.5.2":"Pointer Cancellation","2.5.3":"Label in Name","2.5.4":"Motion Actuation","2.5.7":"Dragging Movements","2.5.8":"Target Size (Minimum)","3.1.1":"Language of Page","3.1.2":"Language of Parts","3.2.1":"On Focus","3.2.2":"On Input","3.2.3":"Consistent Navigation","3.2.4":"Consistent Identification","3.2.6":"Consistent Help","3.3.1":"Error Identification","3.3.2":"Labels or Instructions","3.3.3":"Error Suggestion","3.3.4":"Error Prevention (Legal, Financial, Data)","3.3.7":"Redundant Entry","3.3.8":"Accessible Authentication (Minimum)","3.3.9":"Accessible Authentication (Improved)","4.1.1":"Parsing","4.1.2":"Name, Role, Value","4.1.3":"Status Messages"},"hub":{"title":"WCAG 2.2 Success Criteria & Global Standards","description":"Verbatim normative references for WCAG 2.1 Level AA, WCAG 2.2, and EN 301 549."},"toc":{"heading":"Table of Contents","wcag":"WCAG 2.2 Standards","north_america":"North America","international":"International Standards","seo_benefits":"SEO & AEO Benefits"},"seo":{"heading":"SEO & AEO Benefits of Accessibility","paragraph1":"Implementing accessibility for SEO benefits 2025 and beyond. Digital accessibility directly improves Core Web Vitals and organic search rankings. By using semantic HTML for AEO (Answer Engine Optimization), you enable AI answer engines to accurately parse your content's intent.","paragraph2":"Key optimizations include a logical heading hierarchy for screen readers and crawlers, high color contrast ratios, and strong alt text best practices. Following the POUR principles of web accessibility (Perceivable, Operable, Understandable, Strong) ensures your site is both human-centric and crawler-friendly."},"criteria":{"heading":"WCAG 2.2 Success Criteria","count":"{count} criteria","principle_1":"1. Perceivable","principle_2":"2. Operable","principle_3":"3. Understandable","principle_4":"4. Strong"},"badges":{"obsolete":"Obsolete","new_in_22":"New in 2.2"},"na":{"heading":"North America","baseline_label":"Baseline","official_source":"Official Source"},"intl":{"heading":"International Standards","alignment_label":"Alignment","official_source":"Official Source"},"detail":{"standard_label":"WCAG 2.2 Standard","level_label":"Level {level}","en301549_label":"EN 301 549: {clause}","normative_title":"Normative Text","understanding_title":"Understanding {id}","how_to_comply":"How to Comply","common_failures":"Common Failures","aeo_fact_check":"AEO Fact-Check","mapped_to_en301549":"Directly mapped to EN 301 549 Clause {clause}.","backward_compatible_yes":"Backward compatible with WCAG 2.1: Yes.","backward_compatible_no":"Backward compatible with WCAG 2.1: New in 2.2.","obsolete_note":"This criterion is obsolete in WCAG 2.2 and has been removed from conformance requirements.","found_bug":"Found a bug?","found_bug_desc":"Export this Success Criterion requirement directly to your ticketing system.","export_jira":"Export to JIRA","export_linear":"Linear","pagination_previous":"Previous","pagination_next":"Next","official_link_label":"W3C Technical Documentation","related_tool_heading":"Related Compliance Tool","related_tool_desc":"Use this tool to automatically test and validate elements against SC {id} requirements.","ref_nav_heading":"Reference Navigation","ref_nav_all_wcag":"All WCAG Criteria","ref_nav_eaa":"EAA Law Tracker","ref_nav_glossary":"A-Z Glossary","last_verified":"Last Verified: March 2026"}},"what-next-banner":{"label":"What to do next","heading":"What to do next","card1":{"eyebrow":"Guided Assessment","title":"Guided EAA Self-Assessment","bodyWithTool":"Turn your {toolName} results into a formal WCAG 2.2 / EAA compliance record with a Word report.","bodyGeneric":"Turn your results into a formal WCAG 2.2 / EAA compliance record with a Word report.","cta":"Start assessment →"},"card2":{"eyebrow":"Pro Tool","defaultTitle":"Compliance Report Builder","bodySpecificTool":"Unlock deeper analysis with a 7-day free trial.","bodyDefault":"Package your findings into a audit report. Word and PDF export.","cta":"Unlock with trial →"},"card3":{"eyebrow":"7-Day Free Trial","title":"Try all {count} Pro tools free","body":"No credit card required. Evidence Vault, Annex IV Technical File, Statement Wizard, and more.","cta":"Start free trial →"}},"alt-text-pro":{"meta":{"toolId":"Alt-text-pro","title":"Alt Text Quality Checker Pro"},"badge":"Pro","title":"Alt Text Quality Checker Pro","description":"Batch scan up to 20 URLs or sitemap-sample 20% of your pages, image thumbnails, alt text review, and CSV export.","wizardBanner":{"toolName":"Alt Text Analyser"},"proGateFeatures":["Batch-scan alt text across up to 20 URLs at once","Sitemap scanner, crawl up to 500 pages with automatic rate-limit handling","Image thumbnail preview alongside each finding","Status badges: missing, empty, suspicious, decorative, with remediation guidance","Export complete image audit as CSV for handoff to development teams"],"infoPanel":{"toggle":"What this tool checks, and why alt text is a fundamental legal requirement","whatItDoes":{"heading":"What this tool does","description":"Paste up to 20 URLs at once. The batch processor fetches each page, extracts every element, and checks its alt text status.","paragraph1":"Paste up to 20 URLs at once. The batch processor fetches each page, extracts every <img> element, and checks its alt text status. Each image is categorised as: missing (no alt attribute at all, a hard failure), empty (alt=\"\", verify it is truly decorative), suspicious (filename, very short text, or likely auto-generated), decorative (explicitly marked with empty alt), or has-text (alt text is present and non-empty). Results are shown with image thumbnails and exportable as CSV.","paragraph2":"This is the Pro batch version, the free single-URL alt text checker is also available in the tools menu."},"legalRequirement":{"heading":"Why alt text is the most commonly cited accessibility failure","intro":"Missing alt text on images is consistently the #1 most commonly found accessibility failure in automated audits globally (WebAIM Million, 2024: found on 54.5% of tested home pages). It is also one of the easiest to fix, making it a high-priority target for compliance programmes.","wcagLabel":"WCAG 2.2 SC 1.1.1","wcagBody":"Non-text Content, Level A. Every non-decorative image must have a text alternative that serves the equivalent purpose. A missing alt attribute is an automatic Level A failure, the lowest and most fundamental conformance level. There is no excuse for this failure in any serious accessibility programme.","eaaLabel":"EAA 2025","eaaBody":"European Accessibility Act (Directive 2019/882), applies from 28 June 2025. Requires WCAG 2.1 AA via EN 301 549 (clause 9.1.1.1). Missing alt text will be a primary finding in any EAA enforcement investigation and is trivially detectable by automated scanners.","enLabel":"EN 301 549","enBody":"Clause 9.1.1.1 directly maps to WCAG SC 1.1.1. Compliance with EN 301 549 creates a legal presumption of conformity under the EAA and the Web Accessibility Directive.","ukLabel":"UK PSBAR","ukBody":"Public Sector Bodies Accessibility Regulations 2018. The CDDO's automated monitoring specifically checks for missing alt text. It is the single most cited failure in public sector monitoring reports.","adaLabel":"ADA / Section 508","adaBody":"Missing image alt text is cited in the majority of ADA website accessibility demand letters and Department of Justice investigations. It is a near-certain finding in any Section 508 audit."},"goodAltText":{"heading":"What good alt text looks like","informative":"Informative images: Describe the content and function, \"Bar chart showing UK disability employment rate 2019–2024, peaking at 54.3% in 2023.\"","functional":"Functional images (buttons/links): Describe the destination or action, \"Go to checkout\", not \"button\".","decorative":"Decorative images: Use alt=\"\", do not describe. An empty alt causes screen readers to skip the image.","imagesOfText":"Images of text: The alt text should match the text in the image exactly.","avoid":"Avoid: filenames (\"img_4532.jpg\"), \"click here\", \"image of\", or alt text that duplicates nearby caption text."},"howToUse":{"heading":"How to use this tool","steps":["Paste URLs to scan, product pages, blog posts, home page, image-heavy marketing pages.","Review the summary table: pages with missing alt must be fixed first.","Open individual accordions to review suspicious alt text, these need a human judgement call.","Export as CSV and send to your CMS team or developers. Use as evidence in a WCAG audit report."]}},"statusLabels":{"missing":"Missing","empty":"Empty","decorative":"Decorative","hasText":"Has Text","suspicious":"Suspicious"},"statusDescriptions":{"missing":"No alt attribute present, fails SC 1.1.1.","empty":"Empty alt text (alt=\"\"), verify if image is truly decorative.","decorative":"Marked decorative with empty alt, acceptable if image adds no meaning.","hasText":"Alt text present and non-empty, looks good.","suspicious":"Alt text may be auto-generated, a filename, or very short, review manually."},"decisionTree":{"heading":"Alt Text Decision Tree","subtitle":"Ask these questions in order for every image you review.","step1Question":"Is the image purely decorative?","step1Detail":"Does it add no information, e.g. A background pattern, a divider, a stock photo with no content value?","step1AnswerYes":"Yes →","step1Answer":"Use alt=\"\". Screen readers will skip it. Never leave alt absent, that is a hard failure.","step2Question":"Is the image a link or button?","step2Detail":"Is the image the only content inside an anchor or button element?","step2AnswerYes":"Yes →","step2Answer":"Describe the destination or action, not the image. \"Go to homepage\" not \"logo\". \"Search\" not \"magnifying glass\".","step3Question":"Does the image contain text?","step3Detail":"A sign, screenshot, infographic with embedded labels, a badge with text?","step3AnswerYes":"Yes →","step3Answer":"The alt must contain the exact same text as shown in the image.","step4Question":"Is the image a chart, graph, or diagram?","step4Detail":"Does it convey data or relationships that can't be summarised briefly?","step4AnswerYes":"Yes →","step4Answer":"Provide a brief summary in alt (e.g. \"Bar chart: UK site visits Q1 2024\") and a full data table or long description in the surrounding page content.","step5Question":"Is it an informative photo or illustration?","step5AnswerYes":"Yes →","step5Answer":"Describe what matters, the content, not what kind of image it is. Never start with \"image of\" or \"photo of\". Keep it under 150 characters where possible.","steps":[{"question":"Is the image purely decorative?","detail":"Does it add no information, e.g. A background pattern, a divider, a stock photo with no content value?","answer":"Use alt=\"\". Screen readers will skip it. Never leave alt absent, that is a hard failure."},{"question":"Is the image a link or button?","detail":"Is the image the only content inside an anchor or button element?","answer":"Describe the destination or action, not the image."},{"question":"Does the image contain text?","detail":"A sign, screenshot, infographic with embedded labels, a badge with text?","answer":"The alt must contain the exact same text as shown in the image."},{"question":"Is the image a chart, graph, or diagram?","detail":"Does it convey data or relationships that can’t be summarised briefly?","answer":"Provide a brief summary in alt and a full data table or long description in the surrounding page content."},{"question":"Is it an informative photo or illustration?","answer":"Describe what matters, the content, not what kind of image it is. Never start with “image of” or “photo of”. Keep it under 150 characters where possible."}]},"writingTemplates":{"heading":"Writing Templates by Image Type","subtitle":"Copy and adapt for common image categories.","egPrefix":"E.g.","avoidPrefix":"Avoid:","items":{"decorative":{"type":"Decorative","rule":"Alt=\"\"","example":"Background texture, horizontal rule, icon that duplicates adjacent text.","avoid":"Never omit the alt attribute entirely, that is a failure. Alt=\"\" is correct."},"logo":{"type":"Logo / Brand Mark","rule":"Alt=\"[Organisation name]\"","example":"\"Acme Corp\", if it links to home, alt=\"Acme Corp, home\"","avoid":"Avoid: alt=\"logo\", alt=\"image\""},"product":{"type":"Product Image","rule":"Alt=\"[Product name], [key distinguishing detail]\"","example":"\"Nike Air Max 90, white with blue swoosh, side view\"","avoid":"Avoid: alt=\"product\", alt=\"shoe\""},"chart":{"type":"Data Chart / Graph","rule":"Alt=\"[Chart type]: [subject] [key finding or range]\"","example":"\"Line chart: UK web accessibility litigation 2018–2024, rising from 12 to 89 cases\"","avoid":"Avoid vague alt. Provide full data nearby."},"person":{"type":"Team / Person Photo","rule":"Alt=\"[Name], [Role] at [Organisation]\"","example":"\"Sarah Chen, Head of Design at Acme Corp\"","avoid":"Avoid: alt=\"team member\", alt=\"headshot\""},"icon":{"type":"Icon (standalone, functional)","rule":"Alt=\"[Action or meaning]\"","example":"\"Search\", \"Close menu\", \"Download PDF\", \"Share on LinkedIn\"","avoid":"Avoid: alt=\"icon\", alt=\"button\""}}},"inputModes":{"pasteUrls":"Paste URLs","sitemapScanner":"Sitemap Scanner","sitemapLocked":"Sitemap Scanner","sitemapLockedTitle":"Upgrade to Pro to use the Sitemap Scanner"},"input":{"urlLabel":"URLs to analyse, one per line (max 20)","urlPlaceholder":"Https://example.com\nhttps://example.com/about\nhttps://example.com/products","sitemapLabel":"Sitemap URL","sitemapPlaceholder":"Https://example.com/sitemap.xml","loadSitemap":"Load Sitemap","loadingSitemap":"Loading…"},"sitemap":{"urlsFound":"{count, plural, one {# URL found in sitemap} other {# URLs found in sitemap}}","fullScanNote":"Full site will be scanned","sampleNote":"{count, plural, one {# page} other {# pages}} will be sampled (20% of site)","readyToScan":"Ready to scan"},"queue":{"queued":"{count, plural, one {# URL queued} other {# URLs queued}}","manualLimit":"(only first {limit} will be scanned)","fullSite":"(full site)","sample20":"(20% sample)"},"actions":{"runScan":"Start Scan","scanning":"Scanning","exportCsv":"Export CSV","rescanFailed":"Rescan Failed","expandAll":"Expand all","collapseAll":"Collapse all"},"progress":{"rateLimited":"Rate limited, waiting {seconds}s before retrying page {current} of {total}…","scanning":"Scanning {current} of {total}…","doNotClose":"Do not close this window, the scanner runs at up to 80 pages per minute and may take several minutes to complete."},"results":{"summary":"Summary","urlsScanned":"URLs Scanned","totalImages":"Total Images","issuesFound":"Issues Found","passing":"Passing","missingAlt":"Missing Alt","scanSummaryHeading":"Scan Summary, {count, plural, one {# URL} other {# URLs}}","detailedResults":"Detailed Results","rescanFailedWithCount":"{label} ({count})"},"table":{"url":"URL","totalImages":"Total Images","missingAlt":"Missing Alt","emptyAlt":"Empty Alt","issues":"Issues","status":"Status","thumbnail":"Thumbnail","altText":"Alt Text","issue":"Issue","missingLabel":"MISSING","emptyLabel":"(empty)","errorLabel":"Error","doneLabel":"Done","noneLabel":"None","issueCount":"{count, plural, one {# issue} other {# issues}}","imageCount":"{count, plural, one {# img} other {# imgs}}","noImagesOnPage":"No images found on this page.","errorPrefix":"Error: {message}","unknownError":"Unknown error"},"filterIssues":{"issuesOnly":"Issues only","allUrls":"All URLs"},"rateLimitError":"Rate limited, max retries exceeded. Try scanning fewer pages or try again later.","networkError":"Network error, could not reach the server.","trialRestriction":"Pro only, Upgrade to export","trialRestrictionTitle":"Upgrade to Pro to export documents"},"alt-text-prompter":{"meta":{"title":"Alt Text Prompter","description":"Learn to write WCAG-compliant alt text with type-specific guidance, feedback, unhelpful pattern detection, and AI image analysis."},"header":{"title":"Alt Text Prompter","subtitle":"Learn to write WCAG-compliant alt text with type-specific guidance, feedback, unhelpful pattern detection, and AI image analysis.","badge":"Pro Tool"},"features":["Type-specific alt text guidance for 8 image types: product, chart, icon, screenshot, and more","Real-time feedback with quality score and unhelpful pattern detection","AI image analysis, upload an image, get a suggested alt text powered by Claude","Full compliance references: EAA, WCAG 2.2, ADA, and Section 508"],"tabs":{"guide":"Guide & Check","ai":"AI Generate","law":"The Law"},"imageTypes":{"product":{"label":"Product Photo","purpose":"Help blind users understand what a product is when they cannot see the image.","include":["What is it? (wallet, shirt, phone case)","Key features: colour, material, size","Notable details: brand, patterns, special features","The view in this specific image (front, side, back)"],"good":[{"text":"Black leather iPhone 15 case with MagSafe ring, back view showing camera cutout","why":"Names product, material, compatibility, and view"},{"text":"Red cotton t-shirt with white stripe detail, on wooden table with size chart visible","why":"Colour, material, key detail, context"},{"text":"Silver stainless steel kitchen knife with 8-inch blade and wooden handle","why":"Material, size, key components named"},{"text":"Gold wedding band with satin finish and engraved initials, shown on ring stand","why":"Material, finish, personalisation detail, context"}],"bad":[{"text":"Product","reason":"Too vague, describes nothing about the item"},{"text":"Nice wallet","reason":"Subjective, doesn't describe the actual product"},{"text":"Image of item","reason":"\"Image of\" is redundant; \"item\" conveys nothing"},{"text":"Beautiful red dress for summer","reason":"\"Beautiful\" is subjective, add material and size instead"},{"text":"Product_photo_1234.jpg","reason":"Filename, never use filenames as alt text"}],"length":"Aim for 80–150 characters, enough to describe key features without becoming marketing copy."},"chart":{"label":"Chart / Graph","purpose":"Convey the data and meaning, not the visual appearance. Users need the information, not the design.","include":["Chart type: bar chart, pie chart, line graph, scatter plot","What is being measured (sales, temperature, participants)","Key data points: highest, lowest, main trends","Time period or categories shown"],"good":[{"text":"Bar chart: monthly site traffic Jan–Jun 2024. Peak June: 14,500 visits. Consistent upward trend.","why":"Chart type, period, key stat, trend described"},{"text":"Pie chart of 2024 revenue by product. Software: 45%, Services: 35%, Support: 20%.","why":"Chart type, period, all values included"},{"text":"Line graph: temperature over 24h. Low 5°C at 6am, peak 22°C at 3pm, drops to 8°C at 11pm.","why":"Type, period, key data points with times"}],"bad":[{"text":"Graph","reason":"No information conveyed at all"},{"text":"Sales chart showing Q4 results","reason":"Where are the numbers? Users need the actual data"},{"text":"The blue line goes up and the red line goes down","reason":"Describes colours, explain what the lines mean"}],"note":"For complex charts, consider providing a data table below the image as an accessible alternative. Link to it with aria-describedby.","length":"Charts typically need 100–250 characters to convey key data. Link to a data table for very complex charts."},"icon":{"label":"Icon / Button","purpose":"Explain what the icon does, not what it looks like. Focus on function over appearance.","include":["What action or concept it represents","What happens when activated (for interactive icons)","Context only if needed"],"good":[{"text":"Save","why":"Clear function, brief and unambiguous"},{"text":"Delete","why":"Action is obvious and brief"},{"text":"Share to social media","why":"Function and context"},{"text":"Warning: session will expire soon","why":"Conveys the meaning of the warning icon"}],"bad":[{"text":"Disk","reason":"Why would they need to know it's a disk? Say 'Save'"},{"text":"Picture of a trash can","reason":"Describes the visual, should say 'Delete'"},{"text":"Image","reason":"No information at all"},{"text":"Icon_save_v2.svg","reason":"Filename, never use filenames as alt text"}],"note":"If the icon is inside a button with visible text (e.g. A Save button labelled 'Save'), use alt=\"\" to avoid repeating the label to screen reader users.","length":"Keep icon alt text under 30 characters. If the button already has a visible label, use alt=\"\"."},"screenshot":{"label":"Screenshot","purpose":"Describe what the screenshot shows, the key elements visible, and what the user should focus on.","include":["Application or interface (Gmail inbox, Figma, Checkout page)","Key elements visible: menu highlighted, button location","What is being shown: step in process, error state, before/after","User action being demonstrated (if a tutorial step)"],"good":[{"text":"Gmail inbox: 23 unread emails. Compose button highlighted top-left of screen.","why":"App, key stat, focus element identified"},{"text":"Step 2: Shipping form with Street, City, State, Zip fields. Next button bottom-right.","why":"Step context, visible fields, action element"},{"text":"Figma: button component in 3 sizes (small, medium, large) on white canvas.","why":"App, what's shown, detail"}],"bad":[{"text":"Screenshot","reason":"Screenshot of what application or step?"},{"text":"Computer screen","reason":"Obviously, describe what is on it"},{"text":"The window at the top left","reason":"No context, top left of what?"}],"length":"Screenshots typically need 100–250 characters as they contain more information than simple images."},"photo":{"label":"Photo / Image","purpose":"Describe important details, context, or meaning. If purely decorative, use alt=\"\" instead.","include":["Who or what is in the photo","What they are doing (action, not just presence)","Relevant context or setting","Mood or emotion only if it adds meaning to the content"],"good":[{"text":"Four people at conference table reviewing documents together, smiling","why":"Who, what they're doing, emotion adds context"},{"text":"Mountain landscape at sunset with orange sky and snow-capped peaks","why":"What, key visual details that matter"},{"text":"Excited group of graduates in caps and gowns celebrating outdoors","why":"Who, emotion with purpose, context"}],"bad":[{"text":"Photo","reason":"No information, same as having no alt text"},{"text":"People","reason":"What are they doing? Where?"},{"text":"Landscape","reason":"What kind? What does it show?"},{"text":"Happy moment","reason":"Too vague and subjective"},{"text":"Click here","reason":"Never use call-to-action text as alt text for an image"}],"note":"If the image is purely decorative (background texture, divider, illustration with no informational value), use alt=\"\", an empty string.","length":"Aim for 60–160 characters, enough to convey the important content."},"logo":{"label":"Logo","purpose":"Identify the brand or organisation. Usually just the name is sufficient.","include":["Company or brand name","What it links to, if it's a clickable home link","Any essential variant detail (e.g. 'dark mode version')"],"good":[{"text":"AccessibilityRef","why":"Just the brand name, simple and sufficient"},{"text":"Google, home page","why":"Brand + destination when the logo is a home link"},{"text":"WCAG 2.2 Level AA conformance badge","why":"What it is and what it represents"}],"bad":[{"text":"Logo","reason":"Which logo? Of whom?"},{"text":"Company logo with colorful design","reason":"Describes appearance, not identity"},{"text":"Our brand","reason":"Vague, name the brand"}],"length":"Logos typically only need the brand name, 5 to 30 characters."},"infographic":{"label":"Infographic","purpose":"Summarise the key information and message. Long descriptions or linked data may be needed for complex infographics.","include":["Overall topic or message of the infographic","Key statistics or facts presented","Comparisons, rankings, or sequences shown","Source or time period if displayed"],"good":[{"text":"5 steps to WCAG compliance: 1. Audit 2. Prioritise 3. Fix 4. Test 5. Monitor.","why":"Topic, all steps in order"},{"text":"Global internet users 2024: 5.4B total. Asia 2.9B, Europe 750M, Americas 1.1B.","why":"Topic, headline stat, regional breakdown"}],"bad":[{"text":"Infographic","reason":"No information conveyed"},{"text":"Statistics about the internet","reason":"Which statistics? What did it say?"}],"note":"For very complex infographics, provide a detailed long description below the image or link to a full text version with aria-describedby.","length":"Typically 100–300 characters. Use aria-describedby or a visible description below for complex content."},"decorative":{"label":"Decorative","purpose":"Decorative images add no information. They must have empty alt text so screen readers skip them entirely.","good":[{"text":"","why":"Alt=\"\", empty string tells screen readers to skip this image"}],"bad":[{"text":"Decorative image","reason":"Screen readers will announce \"Decorative image\", confusing and pointless"},{"text":"Background","reason":"Also unnecessary, just use alt=\"\""}],"note":"Correct HTML: $\"\"$ , note the empty alt attribute (not a missing one). A missing alt attribute causes screen readers to announce the filename instead, which is worse.","length":"Always alt=\"\", no characters needed."}},"guide":{"step1":"Step 1, What type of image?","step2Heading":"Step 2, Read the guidelines","step3Heading":"Step 3, Write your alt text","step4Heading":"Step 4, Feedback","altTextSuffix":"Alt Text","whatToInclude":"What to include","goodExamplesHeading":"Good examples","avoidHeading":"Avoid","lengthLabel":"Length:","decorativeHelpText":"For decorative images, click \"Check\" with the field empty to confirm correct usage. If you type anything here, it will be flagged as an issue.","decorativePlaceholder":"Leave empty for decorative, alt=\"\"","writePlaceholder":"Write your alt text for a {type}…","characterCount":"{count} characters","checkButton":"Check my alt text","selectTypePrompt":"Select an image type above to get started","decorativeEmptyExample":"Alt=\"\" (empty string)"},"feedbackPanel":{"verdictExcellent":"Excellent alt text","verdictGood":"Good, minor improvements possible","verdictNeedsImprovement":"Needs improvement","verdictSignificantIssues":"Significant issues found","decorativeNote":"· Decorative, empty is correct","characterContext":"{chars} characters · {type}","copy":"Copy","copied":"Copied!","complianceTitle":"Why this satisfies accessibility law","complianceBody":"Your alt text satisfies WCAG 2.2 SC 1.1.1 Non-text Content (Level A) by providing a text alternative that conveys the equivalent purpose of the image to users who cannot see it. This is the foundational requirement referenced by every major accessibility law."},"feedbackMessages":{"decorativeCorrect":"Correct, empty alt text tells screen readers to skip this decorative image","decorativeError":"Decorative images must have alt=\"\" (empty string), remove the text you have written","noAltText":"No alt text entered, type something to get feedback","imageOfRedundant":"\"Image of\" / \"Photo of\" is redundant, screen readers already announce the image role","singleGenericWord":"Single generic word, this conveys the same information as having no alt text","fileExtension":"Contains a file extension, looks like a filename was used instead of real alt text","filenameLike":"Looks like a filename or auto-generated label, write descriptive alt text instead","callToAction":"\"Click here\" / \"Read more\" / \"Download\", never use call-to-action text as alt text","onlyNumbers":"Contains only numbers, this is not a meaningful description","allCaps":"All-caps alt text, write in normal sentence case for better screen reader pronunciation","marketingSuperlatives":"Contains marketing superlatives ('amazing', 'stunning', etc.), alt text should describe, not sell","placeholderValue":"Looks like a placeholder or debugging value, replace with real descriptive text","onlyPunctuation":"Contains only punctuation or whitespace, this is not meaningful alt text","tooShort":"Too short ({chars} chars), add more detail; aim for at least {min} characters","goodLength":"Good length, detailed enough","tooLong":"Very long ({chars} chars), try to trim to under {max} characters","missingNumbers":"Missing numbers, chart alt text must include actual data values, not just descriptions","includesNumbers":"Includes numerical data","missingChartType":"Doesn't mention chart type, add 'bar chart', 'pie chart', 'line graph', etc.","mentionsChartType":"Mentions chart type","missingProductDescriptor":"Missing colour or material, product alt text should describe what it's made of or its colour","includesProductDescriptor":"Includes colour or material description","iconTooLong":"Too long for an icon, keep icon alt text brief, typically under 30 characters","iconGoodLength":"Good length for an icon description","noCommonIssues":"No common issues detected"},"ai":{"title":"AI Alt Text Generator","panelHeading":"AI Image Analysis","panelDescription":"Upload a photo and Claude will generate WCAG-compliant alt text, explain why it is appropriate, and flag any unhelpful patterns.","usesRemaining":"Uses remaining this month","monthlyLimitReached":"Monthly limit reached","monthlyLimitNote":"Your 20 AI analysis uses reset at the start of next month. Use the Guide & Check tab for unlimited manual feedback in the meantime.","imageTypeHint":"Image type, helps the AI give better context-specific alt text","uploadHeading":"Upload an image","uploadHint":"JPEG, PNG, WebP, GIF · Max 5 MB · {count, plural, one {# use} other {# uses}} remaining this month","uploadAriaLabel":"Upload image file","analysing":"Analysing image…","errorPrefix":"Error: {message}","monthlyLimit":"Monthly limit reached, resets next month","loginRequired":"Please log in to use AI alt-text generation","fileTooLarge":"Image too large, maximum 5 MB","invalidFormat":"Please upload a JPEG, PNG, GIF, or WebP image","analysisFailed":"AI analysis failed","resultHeading":"AI-Generated Alt Text","characterCount":"{count} characters","reasoningHeading":"Why this alt text is appropriate","complianceHeading":"Compliance","unhelpfulHeading":"Unhelpful pattern warning","uploadLabel":"Upload an image","selectType":"Image type","uploadButton":"Upload & Analyse","loading":"Analysing image…","suggestedAlt":"Suggested alt text","reasoning":"Reasoning","compliance":"Compliance note","copyAlt":"Copy alt text","copied":"Copied!","remaining":"{count} AI analyses remaining this month"},"law":{"title":"Which laws require alt text?","jurisdiction":"Jurisdiction","clause":"Clause","detail":"Detail","intro":"The legal requirement","introBody":"Alt text is not optional, it is a legal requirement under multiple laws globally. Every major accessibility law references a single WCAG criterion as its technical basis.","wcagPanel":{"levelLabel":"Level A","title":"WCAG 2.2 SC 1.1.1, Non-text Content","subtitle":"The foundational requirement, most basic WCAG level","w3cLink":"W3C guidance →","requiresHeading":"What it requires","requiresShort":"All non-text content must have a text alternative that serves the equivalent purpose.","requiresLong":"Every <img> must have an alt attribute. If the image conveys information, the alt text must convey the same information. If it is purely decorative, alt=\"\" signals to screen readers to skip it. A missing alt attribute is worse than empty, it causes the filename to be read aloud.","impactHeading":"Real-world impact","impactBody":"A screen reader user browsing a product page hears \"img_12345.jpg\" for every missing alt attribute. They cannot determine what the product is, what it looks like, or whether they want to buy it. On a news site, missing alt text on article images means blind users cannot access the same information as sighted users, a direct form of discrimination under the EAA and ADA."},"responsivePanel":{"title":"Responsive images, srcset and