Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 3 REVIEW 5 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

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

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

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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 ✗

Alt Text Quality

2 of 2 images have issues

REVIEW

2 of 2 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 images 2 missing

Issue	Count
missing	2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Lighthouse Accessibility Audits

Score 87/100 — 4 failing, 26 passed

REVIEW

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.

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
body > iframe `body > 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.card-top > figure.w-100 > div.dib > a.art-link `div.card-top > figure.w-100 > div.dib > a.art-link`
div.card-top > figure.w-100 > div.dib > a.art-link `div.card-top > figure.w-100 > div.dib > a.art-link`
div.card-top > figure.w-100 > div.dib > a.art-link `div.card-top > figure.w-100 > div.dib > a.art-link`
div.card-top > figure.w-100 > div.dib > a.art-link `div.card-top > figure.w-100 > div.dib > a.art-link`
div.card-top > figure.w-100 > div.dib > a.art-link `div.card-top > figure.w-100 > div.dib > a.art-link`
div.card-top > figure.w-100 > div.dib > a.art-link `div.card-top > figure.w-100 > div.dib > a.art-link`
div.card-top > figure.w-100 > div.dib > a.art-link `div.card-top > figure.w-100 > div.dib > a.art-link`
div.card-right > div.w-100 > div.dib > a.art-link `div.card-right > div.w-100 > div.dib > a.art-link`
div.card-right > div.w-100 > div.dib > a.art-link `div.card-right > div.w-100 > div.dib > a.art-link`
div.card-right > div.w-100 > div.dib > a.art-link `div.card-right > div.w-100 > div.dib > a.art-link`
div.card-right > div.w-100 > div.dib > a.art-link `div.card-right > div.w-100 > div.dib > a.art-link`
div.card-right > div.w-100 > div.dib > a.art-link `div.card-right > div.w-100 > div.dib > a.art-link`
footer.wpds-c-jHFhWE > div.wpds-c-eQbjSQ > div.wpds-c-Kzyvj > a.wpds-c-bEBODO `footer.wpds-c-jHFhWE > div.wpds-c-eQbjSQ > div.wpds-c-Kzyvj > a.wpds-c-bEBODO`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Trending Exercise timing Commanders uniform Eric Swalwell Dog gardening Baby el… `div > div.PJLV > div.wpds-c-bzYzZp > ul.wpds-c-qdpUL`
WP Intelligence Ask The Post AI WP Creative Group Diversity & Inclusion Careers… `div.wpds-c-dCLTmK > div#radix-:rb: > div.wpds-c-gsubXz > ul.wpds-c-iYXqXc`
Trending Politics Elections Opinions National World Style Sports Business Clima… `div.wpds-c-dCLTmK > div#radix-:rd: > div.wpds-c-gsubXz > ul.wpds-c-iYXqXc`
WP Intelligence Enterprise Subscriptions Become a Subscriber Gift Subscriptions… `div.wpds-c-dCLTmK > div#radix-:rf: > div.wpds-c-gsubXz > ul.wpds-c-iYXqXc`
Contact the Newsroom Contact Customer Care Contact the Opinions Team Advertise … `div.wpds-c-dCLTmK > div#radix-:rh: > div.wpds-c-gsubXz > ul.wpds-c-iYXqXc`

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
WP Intelligence `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Ask The Post AI `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
WP Creative Group `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Diversity & Inclusion `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Careers `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Media & Community Relations `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Accessibility Statement `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Trending `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Politics `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Elections `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Opinions `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
National `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
World `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Style `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Sports `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Business `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Climate `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Well+Being `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
D.C., Md., & Va. `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Obituaries `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Weather `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Arts & Entertainment `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Recipes `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
WP Intelligence `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Enterprise Subscriptions `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Become a Subscriber `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Gift Subscriptions `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Mobile & Apps `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Newsletters & Alerts `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Washington Post Live `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Reprints & Permissions `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Post Store `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Books & E-Books `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Print Special Editions Store `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Today’s Paper `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Public Notices `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Contact the Newsroom `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Contact Customer Care `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Contact the Opinions Team `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Advertise `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Licensing & Syndication `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Request a Correction `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Send a News Tip `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Report a Vulnerability `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`
Download the Washington Post App `div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ`

These are opportunities to improve the experience of reading tabular or list data using 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

●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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[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 with `role="dialog"` or `role="alertdialog"` have accessible names.

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

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○ARIA input fields 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 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

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

○Identical links have the same purpose.

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

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

H1 This site can’t be reached

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

No links or buttons

PASS

No links or buttons

No links or buttons on this page

0 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

A+

Dark Mode Support

Full dark mode support

PASS

Full dark mode support

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: light dark

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

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 light dark ✓Dark theme-color #fff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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