Aaccessibilitychecker.eu
← Back home

Accessibility Audit Report

chatgpt.com

Completed27 Jun 2026, 12:00viewport 756 × 413

Accessibility score

F31 / 100
Critical issues

Weighted by issue severity and affected elements.

Affected elements by severity

Critical1
Serious1
Moderate1
Minor1

4

Rule violations

4

Affected elements

15

Passed checks

0

Manual review

Executive summary

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.

Methodology

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

Digital Accessibility Act readiness

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.

Priority implication: treat critical checkout, booking, account, payment and support barriers as commercial and compliance risks, not only technical defects. Remediation evidence can help demonstrate due diligence if customers, public buyers or regulators request proof of accessibility work.

Findings

4 rule violations, grouped by severity.

Critical1 rule · 1 element
Serious1 rule · 1 element
Moderate1 rule · 1 element
Minor1 rule · 1 element

Critical

1 rule · 1 element
Criticalmeta-refresh

1

element

Delayed refresh under 20 hours must not be used

Ensure <meta http-equiv="refresh"> is not used for delayed refresh

WCAG 2.0 AWCAG 2.2.1

Why it matters

Blocks people with disabilities from using core functionality. Fix as a top priority.

How to fix

  • <meta> tag forces timed refresh of page (less than 20 hours)

Where — sample elements

meta[http-equiv="refresh"]

<meta http-equiv="refresh" content="360">

Serious

1 rule · 1 element
Serioushtml-has-lang

1

element

<html> element must have a lang attribute

Ensure every HTML document has a lang attribute

WCAG 2.0 AWCAG 3.1.1

Why it matters

Causes significant barriers for assistive-technology users. Should be fixed soon.

How to fix

  • The <html> element does not have a lang attribute

Where — sample elements

html

<html dir="ltr">

Moderate

1 rule · 1 element
Moderatepage-has-heading-one

1

element

Page should contain a level-one heading

Ensure that the page, or at least one of its frames contains a level-one heading

Best practice

Why it matters

Creates friction and a degraded experience for some users.

How to fix

  • Page must have a level-one heading

Where — sample elements

html

<html dir="ltr">

Minor

1 rule · 1 element
Minorempty-heading

1

element

Headings should not be empty

Ensure headings have discernible text

Best practice

Why it matters

A small usability issue with limited impact.

How to fix

  • Element does not have text that is visible to screen readers
  • aria-label attribute does not exist or is empty
  • aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
  • Element has no title attribute

Where — sample elements

#LanO3

<h2 id="LanO3"></h2>

Passed checks15

Automated checks that returned no violations on this page.

  • aria-allowed-role
  • aria-deprecated-role
  • aria-hidden-body
  • aria-required-attr
  • aria-roles
  • avoid-inline-spacing
  • document-title
  • heading-order
  • landmark-main-is-top-level
  • landmark-no-duplicate-main
  • landmark-one-main
  • landmark-unique
  • meta-viewport-large
  • meta-viewport
  • region

Choose Your Path to Compliance

Select the option that works best for you

AI-Powered Fix Instructions

Get detailed, step-by-step instructions with AI assistance to fix issues yourself

  • Code examples and solutions
  • Priority-based guidance
  • Instant access

Full Manual Audit by Expert

Order a comprehensive manual audit from accessibility specialists

  • Expert human review
  • Detailed remediation report
  • Priority support