Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 5 REVIEW 3 FIX

Link & Button Quality

Action

12 issue(s) across 170 links and 7 buttons

FIX

12 issue(s) across 170 links and 7 buttons

6 link(s) with no accessible text

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

Got: https://web.dev/explore/ai; https://web.dev/explore/how-to-optimize-inp?utm_source=web.dev&utm_medium=cards&utm_campaign=inp-cwv; https://web.dev/identity; https://web.dev/learn/html; https://web.dev/learn/css; https://web.dev/learn/javascript

6 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://web.dev/explore/ai ("Learn more"); https://web.dev/explore/how-to-optimize-inp?utm_source=web.dev&utm_medium=cards&utm_campaign=inp-cwv ("Learn more"); https://web.dev/identity ("Learn more"); https://web.dev/html ("Learn more"); https://web.dev/css ("Learn more"); https://web.dev/javascript ("Learn more")

158 link(s) with descriptive text

170 links

6 empty

6 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://web.dev/explore/ai	(empty)	empty	Add link text or aria-label
https://web.dev/explore/ai	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Ai
https://web.dev/explore/how-to-optimize-…	(empty)	empty	Add link text or aria-label
https://web.dev/explore/how-to-optimize-…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: How To Optimize Inp?Utm Source=Web.Dev&Utm Medium=Cards&Utm Campaign=Inp Cwv
https://web.dev/identity	(empty)	empty	Add link text or aria-label
https://web.dev/identity	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Identity
https://web.dev/html	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Html
https://web.dev/css	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Css
https://web.dev/javascript	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Javascript
https://web.dev/learn/html	(empty)	empty	Add link text or aria-label
https://web.dev/learn/css	(empty)	empty	Add link text or aria-label
https://web.dev/learn/javascript	(empty)	empty	Add link text or aria-label

165 links and buttons have descriptive text

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

https://web.dev/explore/ai; https://web.dev/explore/how-to-optimize-inp?utm_source=web.dev&utm_medium=cards&utm_campaign=inp-cwv; https://web.dev/identity; https://web.dev/learn/html; https://web.dev/learn/css; https://web.dev/learn/javascript

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

Generic link text like 'click here' doesn't describe the destination.

https://web.dev/explore/ai ("Learn more"); https://web.dev/explore/how-to-optimize-inp?utm_source=web.dev&utm_medium=cards&utm_campaign=inp-cwv ("Learn more"); https://web.dev/identity ("Learn more"); https://web.dev/html ("Learn more"); https://web.dev/css ("Learn more"); https://web.dev/javascript ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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 ✗

Heading Hierarchy

50 headings

REVIEW

50 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H3 Building a better web, together
H3 Navigation API is now Baseline Newly available
H3 AI and the web
H3 Optimize INP
H3 Payments & Identity
H2 Explore the web platform
H3 HTML
H3 CSS
H3 JavaScript
H2 Learn the web platform
H3 Learn HTML
H3 Learn CSS
H3 Learn JavaScript
H3 Keep up on web development news
H2 Baseline
H3 February 2026 Baseline monthly digest
H3 January 2026 Baseline monthly digest
H3 December 2025 Baseline monthly digest
H3 November 2025 Baseline monthly digest
H2 CSS and UI design
H3 Adapting typography to user preference using CSS
H3 New CSS color spaces and functions in all major engines
H3 What are source maps?
H3 CSS subgrid
H2 Core Web Vitals
H3 The most effective ways to improve Core Web Vitals
H3 How to optimize INP
H3 Common misconceptions about how to optimize LCP
H3 Best practices for measuring Web Vitals in the field
H2 Progressive Web Apps
H3 Learn PWA
H3 TransformStream is now supported cross browser.
H3 New patterns for amazing apps
H3 Project Fugu API showcase
H2 Accessible for all
H3 Learn Accessibility
H3 Testing web design color contrast
H3 Building the main navigation for a website
H3 Community highlight: Melanie Sumner
H2 Payments and identity
H3 Create a passkey for passwordless logins
H3 Sign in with a passkey
H3 Web payments overview
H3 Payment and address form best practices
H2 Developer Newsletter
H3 web.dev
H3 web.dev
H3 Contribute
H3 Related Content
H3 Follow

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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 | Page Not Found | web.dev ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

10 icon(s) detected

REVIEW

10 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

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

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: #3740ff

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

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

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 2 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Explore the web plat…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Learn the web platfo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Baseline	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 CSS and UI design	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Core Web Vitals	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Progressive Web Apps	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Accessible for all	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Payments and identit…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Developer Newsletter	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Building a better we…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Keep up on web devel…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 web.dev	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 web.dev	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Contribute	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Related Content	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Follow	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title web.dev	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	12.06:1	4.5:1	#000000	#A3C7F6	Pass
button Resources	4.66:1	4.5:1	#000000	#1A73E8	Pass
li Web Platform	4.66:1	4.5:1	#000000	#1A73E8	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.

Landmark Structure

17 landmarks

PASS

17 landmarks

<main> landmark present

6 <nav> landmark(s) found

1 of 6 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A+

Alt Text Quality

All 10 images OK

PASS

All 10 images OK

8 decorative image(s) correctly marked

2 image(s) with good alt text

10 images 2 good alt text 8 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
q	text	Search	aria-label
input	text	Type to filter	aria-label

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: web.dev

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

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

Name web.dev Display Mode standalone Theme Color #3740ff Background Color #fff Icons 8 icon(s)

Lighthouse Accessibility Audits

Score 90/100 — 3 failing, 26 passed

PASS

Accessibility

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Start course `div.devsite-landing-row-item-description > div.devsite-landing-row-item-body > div.devsite-landing-row-item-buttons > a.button`
Start course `div.devsite-landing-row-item-description > div.devsite-landing-row-item-body > div.devsite-landing-row-item-buttons > a.button`
Start course `div.devsite-landing-row-item-description > div.devsite-landing-row-item-body > div.devsite-landing-row-item-buttons > a.button`
Read the blog `div.devsite-landing-row-item-description > div.devsite-landing-row-item-body > div.devsite-landing-row-item-buttons > a.button`

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.devsite-landing-row-group > div.devsite-landing-row-item > devsite-iframe > iframe `div.devsite-landing-row-group > div.devsite-landing-row-item > devsite-iframe > iframe`

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.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a `div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a`
div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a `div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a`
div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a `div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a`
image `div.devsite-landing-row-group > div.devsite-landing-row-item > div.devsite-landing-row-item-description > a`
web `div.devsite-landing-row-group > div.devsite-landing-row-item > div.devsite-landing-row-item-description > a`
timer `div.devsite-landing-row-group > div.devsite-landing-row-item > div.devsite-landing-row-item-description > a`
div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a `div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a`
div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a `div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a`
div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a `div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a`

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.

○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

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●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 input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

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

○ARIA toggle fields have accessible names

○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

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

○Input buttons have discernible text.

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

○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.

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

○Elements with visible text labels have matching accessible names.

○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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.