ampproject.org Accessibility Report

Accessibility audit of ampproject.org — scanned on Feb 20, 2026

Technology
0 /100
D Poor

5 issues found across 2 categories

3 Critical 2 Major

WCAG Compliance Overview

Perceivable 2 issues
Operable 2 issues
Understandable 0 issues
Robust 1 issues

Issues Found

Links missing accessible name

Critical

Links must have discernible text so screen reader users understand their purpose.

WCAG 2.4.4
1 element(s) affected
  • <a href="https://blog.amp.dev/">
How to fix

Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

Form inputs missing labels

Critical

Form elements must have associated labels so users know what information to enter.

WCAG 1.3.1
1 element(s) affected
  • <select name="(no name)">
How to fix

Add <label> elements with matching for attributes, or use aria-label.

Buttons missing accessible name

Critical

Buttons must have discernible text for screen reader users.

WCAG 4.1.2
8 element(s) affected
  • <button>
  • <button>
  • <button>
  • <button>
  • <button>
How to fix

Add text content, aria-label, or title to all <button> elements.

Heading levels skip order

Major

Headings should follow a logical order (h1 → h2 → h3) without skipping levels.

WCAG 1.3.1
14 element(s) affected
  • <h5> "Easily create websites with a great page experienc" (after h1)
  • <h5> "Immerse readers in visual and tappable stories the" (after h1)
  • <h5> "Send emails of the future with personalized dynami" (after h1)
  • <h5> "Serve lightning fast and secure eye-catching creat" (after h1)
  • <h6> "Stories" (after h1)
How to fix

Restructure headings to follow sequential order. Don't skip from h1 to h3.

No skip navigation link

Major

Pages should have a mechanism to bypass repeated navigation blocks.

WCAG 2.4.1
1 element(s) affected
  • No skip navigation link found
How to fix

Add a 'Skip to main content' link as the first focusable element on the page.

Top Priority Fixes

Here are the most impactful changes ampproject.org should make to improve accessibility:

  1. #1
    Buttons missing accessible name Critical

    Add text content, aria-label, or title to all <button> elements.

  2. #2
    Links missing accessible name Critical

    Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

  3. #3
    Form inputs missing labels Critical

    Add <label> elements with matching for attributes, or use aria-label.

Frequently Asked Questions

Is ampproject.org accessible?

ampproject.org scored 39/100 (grade D) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is ampproject.org WCAG compliant?

Our scan found 5 accessibility issues on ampproject.org. Full WCAG compliance requires addressing all critical and major issues identified above.

Is ampproject.org EAA compliant?

The European Accessibility Act requires websites to meet WCAG 2.1 AA standards. Check the detailed report above to see ampproject.org's compliance status.

What accessibility issues does ampproject.org have?

See the full issue list above with severity levels, affected elements, and recommended fixes for ampproject.org.

Scan Your Own Website

Get a free accessibility report for your website in seconds.

Scan Your Website Free View Pricing