Accessibility

F

Heading Hierarchy

Action

38 headings, 14 skip(s)

FIX

38 headings, 14 skip(s)

Multiple H1 headings (7 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H6 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H6 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 AMP is a web component framework to easily create user-first experiences for the web.
H1 AMP Websites duplicate H1
H5 Easily create websites with a great page experience out-of-the-box using AMP’s ready-to-go web components. skipped
H1 Web Stories duplicate H1
H5 Immerse readers in visual and tappable stories they can share anywhere on the open web. skipped
H1 AMP Emails duplicate H1
H5 Send emails of the future with personalized dynamic content and interactive elements that engage readers. skipped
H1 AMP Ads duplicate H1
H5 Serve lightning fast and secure eye-catching creatives. skipped
H1 The latest news duplicate H1
H6 Stories skipped
H4 Web Story Forms unlock more ways to engage your audience
H6 Bento skipped
H4 Introducing Bento
H6 Stories skipped
H4 Web Stories call to action buttons get an upgrade
H6 Websites skipped
H4 Easy TikTok embedding with the new amp-tiktok
H6 Stories skipped
H4 Richer interactions in Web Stories
H6 Stories skipped
H4 Better video performance in Web Stories
H1 Explore AMP success stories duplicate H1
H6 websites skipped
H4 AMP helps the Washington Post increase returning users from mobile search by 23%
H6 websites skipped
H4 Teads brings AMP'd mobile video inventory to nearly 100 publishers
H6 websites skipped
H4 Carved increases conversion rate by 75% with AMP and PWA
H6 websites skipped
H4 WompMobile consistently improves e-commerce clients’ conversion rates with AMP sites
H5 Follow us
H5 Overview
H5 Docs
H5 Community
H5 OpenJS Foundation
H5 Events
H5 AMP Brand Materials

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

D

Favicon & Branding

Action

9 icon(s) detected

FIX

9 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

D

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #005af0

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Search

Skip Link

Labeled Navigation 1 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

B

Link & Button Quality

9 issue(s) across 82 links and 20 buttons

REVIEW

9 issue(s) across 82 links and 20 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://blog.amp.dev/

8 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.ap-formats-navigation-icon-wrapper (#346 on page); button.ap-formats-navigation-icon-wrapper (#355 on page); button.ap-formats-navigation-icon-wrapper (#364 on page); button.ap-formats-navigation-icon-wrapper (#373 on page); button (#502 on page); button (#504 on page); button (#585 on page); button (#587 on page)

81 link(s) with descriptive text

82 links

1 empty

0 generic text

0 new tab

8 empty buttons

Element	Text	Issue	Suggested Fix
https://blog.amp.dev/	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

93 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://blog.amp.dev/

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Icon-only buttons need an aria-label so screen readers can announce them.

button.ap-formats-navigation-icon-wrapper (#346 on page); button.ap-formats-navigation-icon-wrapper (#355 on page); button.ap-formats-navigation-icon-wrapper (#364 on page); button.ap-formats-navigation-icon-wrapper (#373 on page); button (#502 on page); button (#504 on page); button (#585 on page); button (#587 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

B

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 - amp.dev ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

B

Lighthouse Accessibility Audits

Score 81/100 — 7 failing, 23 passed

REVIEW

81

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Bento Introducing Bento December 8, 2021 `amp-base-carousel#teaser-carousel-news > div.i-amphtml-carousel-content > div.i-amphtml-carousel-scroll > a.-nr`
Stories Web Stories call to action buttons get an upgrade September 15, 2021 `amp-base-carousel#teaser-carousel-news > div.i-amphtml-carousel-content > div.i-amphtml-carousel-scroll > a.-nr`
Websites Easy TikTok embedding with the new amp-tiktok September 13, 2021 `amp-base-carousel#teaser-carousel-news > div.i-amphtml-carousel-content > div.i-amphtml-carousel-scroll > a.-nr`
Stories Richer interactions in Web Stories August 26, 2021 `amp-base-carousel#teaser-carousel-news > div.i-amphtml-carousel-content > div.i-amphtml-carousel-scroll > a.-nr`
Stories Better video performance in Web Stories August 24, 2021 `amp-base-carousel#teaser-carousel-news > div.i-amphtml-carousel-content > div.i-amphtml-carousel-scroll > a.-nr`
websites Teads brings AMP'd mobile video inventory to nearly 100 publishers Adv… `amp-base-carousel#success-stories > div.i-amphtml-carousel-content > div.i-amphtml-carousel-scroll > a.-nr`
websites Carved increases conversion rate by 75% with AMP and PWA E-Commerce `amp-base-carousel#success-stories > div.i-amphtml-carousel-content > div.i-amphtml-carousel-scroll > a.-nr`
websites WompMobile consistently improves e-commerce clients’ conversion rates … `amp-base-carousel#success-stories > div.i-amphtml-carousel-content > div.i-amphtml-carousel-scroll > a.-nr`

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
`body.ap--websites > main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news`
`body.ap--websites > main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-success-stories`

When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na`
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na`
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na`
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na`
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na`
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na`
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-success-stories > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-success-stories > div.-na`
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-success-stories > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-success-stories > div.-na`
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-success-stories > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-success-stories > div.-na`
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-success-stories > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-success-stories > div.-na`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.ap-formats > aside.ap-formats-navigation > div.ap-formats-navigation-wrapper > button.ap-formats-navigation-icon-wrapper `section.ap-formats > aside.ap-formats-navigation > div.ap-formats-navigation-wrapper > button.ap-formats-navigation-icon-wrapper`
section.ap-formats > aside.ap-formats-navigation > div.ap-formats-navigation-wrapper > button.ap-formats-navigation-icon-wrapper `section.ap-formats > aside.ap-formats-navigation > div.ap-formats-navigation-wrapper > button.ap-formats-navigation-icon-wrapper`
section.ap-formats > aside.ap-formats-navigation > div.ap-formats-navigation-wrapper > button.ap-formats-navigation-icon-wrapper `section.ap-formats > aside.ap-formats-navigation > div.ap-formats-navigation-wrapper > button.ap-formats-navigation-icon-wrapper`
section.ap-formats > aside.ap-formats-navigation > div.ap-formats-navigation-wrapper > button.ap-formats-navigation-icon-wrapper `section.ap-formats > aside.ap-formats-navigation > div.ap-formats-navigation-wrapper > button.ap-formats-navigation-icon-wrapper`
div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-prev-slot > button `div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-prev-slot > button`
div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-next-slot > button `div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-next-slot > button`
div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-prev-slot > button `div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-prev-slot > button`
div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-next-slot > button `div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-next-slot > button`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.-l > ul.-h > li.-p > a.ap-a-ico `div.-l > ul.-h > li.-p > a.ap-a-ico`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Easily create websites with a great page experience out-of-the-box using AMP’s … `section.ap-formats > div#ap-formats-format-websites > div.ap-formats-format-content > h5.ap-h5`
Immerse readers in visual and tappable stories they can share anywhere on the o… `section.ap-formats > div#ap-formats-format-stories > div.ap-formats-format-content > h5.ap-h5`
Send emails of the future with personalized dynamic content and interactive ele… `section.ap-formats > div#ap-formats-format-email > div.ap-formats-format-content > h5.ap-h5`
Serve lightning fast and secure eye-catching creatives. `section.ap-formats > div#ap-formats-format-ads > div.ap-formats-format-content > h5.ap-h5`
Stories `a.-nr > div.-ni > div.-nf > h6`
websites `a.-nr > div.-ni > div.-nf > h6`

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Got it! `body.ap--websites > amp-consent#consent > div#consent-popup > button.ap-a-btn`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[role]`s are contained by their required parent element

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

A

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

A+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 good alt text

All images have appropriate alt text.

A

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <select>

1 controls

0 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
select	select	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: amp.dev

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name amp.dev ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name amp.dev Display Mode standalone Theme Color #005af0 Background Color #ffffff Icons 8 icon(s)

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 AMP is a web compone…	8.73:1	3.0:1	#000000	#00B8CC	Pass
h1 AMP Websites	8.73:1	3.0:1	#000000	#00B8CC	Pass
h1 Web Stories	8.73:1	3.0:1	#000000	#00B8CC	Pass
h1 AMP Emails	8.73:1	3.0:1	#000000	#00B8CC	Pass
h1 AMP Ads	8.73:1	3.0:1	#000000	#00B8CC	Pass
h1 The latest news	8.73:1	3.0:1	#000000	#00B8CC	Pass
h1 Explore AMP success …	8.73:1	3.0:1	#000000	#00B8CC	Pass
title AMP - a web componen…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span AMP	19.95:1	4.5:1	#000000	#F9F9F9	Pass
button About	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div AMP Websites	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Create flawless web …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Web Stories	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Snackable Stories fo…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div AMP Ads	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Super fast ads on th…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div AMP Email	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Next gen email	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a How AMP works	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Vision & Mission	21.00:1	4.5:1	#000000	#FFFFFF	Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.