Accessibility score
Weighted by issue severity and affected elements.
Affected elements by severity
4
Rule violations
4
Affected elements
15
Passed checks
0
Manual review
chatgpt.com scored 31/100 — a failing grade driven by issues that block core functionality for people with disabilities.
Across the page, automated checks flagged 4 distinct rule violations affecting 4 elements: 1 critical, 1 serious, 1 moderate, and 1 minor. The critical failures — delayed refresh under 20 hours must not be used — prevent screen-reader and keyboard users from completing key tasks.
A further 0 checks could not be evaluated automatically and require manual review, while 15 checks passed. Remediating the one critical rule and the most frequent serious issue — <html> element must have a lang attribute — will clear the highest-impact barriers first.
Scanned against WCAG 2.0 / 2.1 success criteria at a 756 × 413 viewport, with the results mapped to practical EN 301 549 and European Accessibility Act readiness. Automated testing detects only part of WCAG risk; pair it with manual keyboard and assistive-technology testing for full coverage.
Legal compliance risk
Since 28 June 2025, the European Accessibility Act (Directive (EU) 2019/882) has applied to covered digital services across the EU market. Many organizations refer to this as the Digital Accessibility Act in procurement and compliance work. In practice, websites, apps, e-commerce, banking, transport, media and support journeys should align with EN 301 549 and WCAG AA expectations.
Non-compliance can trigger formal complaints, corrective orders, national authority investigations, financial penalties in EUR, reputational harm, contract loss, and restrictions on placing or keeping a non-conforming service in the market. This audit found 4 accessibility issues that may expose your organization to this risk and should be remediated promptly.
4 rule violations, grouped by severity.
1
element
Ensure <meta http-equiv="refresh"> is not used for delayed refresh
Why it matters
Blocks people with disabilities from using core functionality. Fix as a top priority.
How to fix
Where — sample elements
meta[http-equiv="refresh"]
<meta http-equiv="refresh" content="360">
1
element
Ensure every HTML document has a lang attribute
Why it matters
Causes significant barriers for assistive-technology users. Should be fixed soon.
How to fix
Where — sample elements
html
<html dir="ltr">
1
element
Ensure that the page, or at least one of its frames contains a level-one heading
Why it matters
Creates friction and a degraded experience for some users.
How to fix
Where — sample elements
html
<html dir="ltr">
1
element
Ensure headings have discernible text
Why it matters
A small usability issue with limited impact.
How to fix
Where — sample elements
#LanO3
<h2 id="LanO3"></h2>
Automated checks that returned no violations on this page.
Select the option that works best for you
Get detailed, step-by-step instructions with AI assistance to fix issues yourself
Order a comprehensive manual audit from accessibility specialists
Legal compliance risk
Since 28 June 2025, the European Accessibility Act (Directive (EU) 2019/882) has applied to covered digital services across the EU market. Many organizations refer to this as the Digital Accessibility Act in procurement and compliance work. In practice, websites, apps, e-commerce, banking, transport, media and support journeys should align with EN 301 549 and WCAG AA expectations.
Non-compliance can trigger formal complaints, corrective orders, national authority investigations, financial penalties in EUR, reputational harm, contract loss, and restrictions on placing or keeping a non-conforming service in the market. This audit found 4 accessibility issues that may expose your organization to this risk and should be remediated promptly.