Skip to content
https://grist.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
D
Form Accessibility
Action
6 of 15 controls have issues
FIX
6 of 15 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">; <input type="submit" id="searchsubmit">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s" id="menu-search-input">
Info::
9 control(s) properly labeled
15 controls
9 labeled
1 placeholder only
5 unlabeled
ControlTypeLabelMethod
#CybotCookiebotDialogBodyLevelButtonNecessarycheckboxNecessaryfor/id
#CybotCookiebotDialogBodyLevelButtonPreferencescheckboxPreferencesfor/id
#CybotCookiebotDialogBodyLevelButtonStatisticscheckboxStatisticsfor/id
#CybotCookiebotDialogBodyLevelButtonMarketingcheckboxMarketingfor/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformationcheckboxDo not sell or share my personal informationfor/id
#input_2296123289_1emailEmail Addressfor/id
ak_hp_textareatextareaΔnone
#input_1295107632_1emailEmail Addressfor/id
ak_hp_textareatextareaΔnone
#menu-search-inputtext(Search)placeholder only
#CybotCookiebotDialogBodyLevelButtonStatisticsInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonMarketingInlinecheckbox(none)none
#searchsubmitsubmit(none)none
#CybotCookiebotDialogBodyLevelButtonNecessaryInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonPreferencesInlinecheckbox(none)none

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

<input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">; <input type="submit" id="searchsubmit">

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

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="s" id="menu-search-input">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: App
Info::
192x192 icon present
PWA Install Criteria Not Installable
Name App ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗
Name App Icons 6 icon(s)
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: #e6ffa0
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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
Info::
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
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
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 2 <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
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV MAIN ASIDE CONTENTINFO footer

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

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

B
Heading Hierarchy
79 headings
REVIEW
79 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Get a weekly dose of climate inspiration in your inbox
  • H2 Menu
  • H2 Search
  • H2 Go To
  • H2 Topics
  • H2 (empty)
  • H2 Get a weekly dose of climate inspiration in your inbox
  • H3 How deep-red Utah helped launch a portable plug-in solar movement
  • H2 The Weekly Get Grist's Free Weekly Newsletter
  • H2 Latest
  • H2 Latest
  • H3 The Trump administration wants to take an ax to the East’s last great forests
  • H3 War, climate change, and AI: What’s at stake at this year’s UN Indigenous forum
  • H3 The state of solar: Despite partisan rhetoric, the industry is still booming
  • H3 The world desperately needs to decarbonize shipping. Can nations find a consensus?
  • H3 Maine presses pause on large data centers. Will other states follow its lead?
  • H3 A more troubling picture of sea level rise is coming into view
  • H2 Featured
  • H2 Featured
  • H3 The Green New Deal has evolved. Now it’s all about ‘affordability.’
  • H3 At the UN, Indigenous leaders tackle how to enforce global climate court rulings
  • H3 We asked climate leaders what’s keeping them inspired. Here’s what they said.
  • H2 Recent
  • H3 Deep-diving robots help crack the mystery of Antarctica’s vanishing sea ice
  • H3 American farmers bet on solar. Then Trump changed the rules.
  • H3 Ask a Climate Therapist: Why should I plan for my future when I feel we don’t have one?
  • H3 Climate adaptation funding is scarce. Private investors could help.
  • H2 Topics
  • H3 Grist reports on topics like Politics, Energy, Equity, Solutions, and how they intersect with
  • H2 Energy
  • H3 The most polluting LNG project in the US is being built in Louisiana
  • H3 Oil companies accused of massive accounting fraud in New Mexico
  • H3 There’s hope for the offshore wind industry — yes, really
  • H3 How EVs could solve a problem with America’s rickety grid
  • H3 Data centers are straining the grid. Can they be forced to pay for it?
  • H2 Solutions
  • H3 The skylines of the future will be made of wood
  • H3 What to expect when you’re expecting the end of the world
  • H3 Pocket gardens: The tiny urban oases with surprisingly big benefits
  • H3 Texas saw a $50B future in clean energy. Then the political winds shifted.
  • H3 The frantic, high-tech fight to stop climate-fueled dengue fever
  • H2 Staff Picks
  • H3 What’s behind your eye-popping power bill? We broke it down, region by region.
  • H3 Chicago has the most lead pipes in the nation. We mapped them all.
  • H3 First came the wildfire. Then came the scams.
  • H3 Alaska’s $44 billion bet on natural gas
  • H3 A guide to the 4 minerals shaping the world’s energy future
  • H3 In Arizona, a fight against a deadly fungus is under threat from Trump’s health policies
  • H3 A look at the growing ‘disaster economy’ turning crisis into cash
  • H3 Keep Reading
  • H3 They survived the hurricane. Their insurance company didn’t.
  • H3 Trump raised $8 million for Hurricane Helene survivors. Where did it all go?
  • H3 Scams are rampant after natural disasters. Here’s how to protect yourself.
  • H3 Two years after a wildfire took everything, Maui homeowners are facing a new threat: Foreclosure
  • H3 How to track disaster spending in your community
  • H3 Featured
  • H3 First came the wildfire. Then came the scams.
  • H3 How Vermont lost track of millions in FEMA flood recovery funds
  • H3 Disasters destroyed their homes. Then the real estate ‘vultures’ swooped in.
  • H3 Republicans deployed a little-known law to open Minnesota wilderness to mining
  • H3 A ‘super typhoon’ just devastated the Mariana Islands — months before peak storm season
  • H3 ‘A bellwether for new forms of repression’: 2 Indigenous rights advocates remain behind bars in Russia
  • H3 Hurricane Helene ravaged farmers’ topsoil. They’re still fighting to build it back.
  • H2 Watch This
  • H3 This simple metal tube helps scientists predict drought before it happens
  • H3 In the race to find critical minerals, there’s a ‘gold mine’ literally at our shoreline
  • H3 This enzyme is responsible for life on Earth. It’s a hot mess.
  • H3 An early-life wildfire exposure sickened these monkeys for decades
  • H3 The Gulf Coast is home to one of the last healthy coral reefs. It’s surrounded by oil.
  • H3 Trump and the Illinois governor keep feuding over an invasive fish
  • H3 Many companies want clean energy. Georgia Power will soon let them build it.
  • H3 New York City unveils its first rest stop for delivery workers
  • H3 Trump wants to shutter FEMA. Will Markwayne Mullin get it done?
  • H2 Subscribe
  • H2 Looking Forward
  • H2 The Daily
  • H2 Topics
  • H2 Company
  • H2 More

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

C
Alt Text Quality
Action
3 of 91 images have issues
REVIEW
3 of 91 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
1 image(s) with generic alt text
Info::
8 image(s) with alt text over 125 characters
Info::
12 decorative image(s) correctly marked
Info::
68 image(s) with good alt text
91 images 68 good alt text 12 decorative 1 generic 2 missing
IssueCount
missing2 image(s)
generic1 image(s)
too long8 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

B
Favicon & Branding
24 icon(s) detected
REVIEW
24 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found | Grist ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
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)
ElementRatioRequiredFGBGResult
h2 Get a weekly dose of…14.45:13.0:1
#000000
#D6D6D6
Pass
h2 Menu14.45:13.0:1
#000000
#D6D6D6
Pass
h2 Search14.45:13.0:1
#000000
#D6D6D6
Pass
h2 Go To14.45:13.0:1
#000000
#D6D6D6
Pass
h2 Topics14.45:13.0:1
#000000
#D6D6D6
Pass
h2 Get a weekly dose of…14.45:13.0:1
#000000
#D6D6D6
Pass
h2 The Weekly14.45:13.0:1
#000000
#D6D6D6
Pass
h2 Latest14.45:13.0:1
#000000
#D6D6D6
Pass
h2 Featured14.45:13.0:1
#000000
#D6D6D6
Pass
h2 Featured14.45:13.0:1
#000000
#D6D6D6
Pass
h2 Recent14.45:13.0:1
#000000
#D6D6D6
Pass
h2 Topics14.45:13.0:1
#000000
#D6D6D6
Pass
h2 Energy14.45:13.0:1
#000000
#D6D6D6
Pass
h2 Solutions14.45:13.0:1
#000000
#D6D6D6
Pass
h2 Staff Picks14.45:13.0:1
#000000
#D6D6D6
Pass
h2 Watch This14.45:13.0:1
#000000
#D6D6D6
Pass
h2 Subscribe14.45:13.0:1
#000000
#D6D6D6
Pass
h2 Looking Forward14.45:13.0:1
#000000
#D6D6D6
Pass
h2 The Daily14.45:13.0:1
#000000
#D6D6D6
Pass
h2 Topics14.45:13.0:1
#000000
#D6D6D6
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.

A
Lighthouse Accessibility Audits
Score 93/100 — 2 failing, 28 passed
PASS
93

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Play video div.large-tease__art-wrapper > div.tease-art > figure.tease-art__figure > a.play-button
Play video article.small-tease > div.tease-art > figure.tease-art__figure > a.play-button
Play video article.small-tease > div.tease-art > figure.tease-art__figure > a.play-button
Play video article.small-tease > div.tease-art > figure.tease-art__figure > a.play-button
Play video article.small-tease > div.tease-art > figure.tease-art__figure > a.play-button

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.

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
Privacy Policy div#CybotCookiebotDialogBodyContentText > p > a > span
Show details div#CybotCookiebotDialogBody > div.CybotCookiebotDialogBodyBottomWrapper > div#CybotCookiebotDialogBodyEdgeMoreDetails > a#CybotCookiebotDialogBodyEdgeMoreDetailsLink
Donate ul.nav__items > li.nav__item > a.button > span
Get Grist's Free Weekly Newsletter div.hp-topper__subscription > div.hp-topper-newsletter > h2.subsection-header > span
Support Grist div.footer__cta-wrapper > div.footer__cta > a.button > span

These are opportunities to improve the legibility of your content.

○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
●`[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
●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.
●Links have a discernible name
●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.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●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 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
○`<frame>` or `<iframe>` elements have a title
○`<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.
○`<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.
○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.

Send Feedback