Skip to content
https://earthsky.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
47
GRADE
F
FIX
6
REVIEW
6
PASS
1
INFO
0
Checks
13
1 PASS 6 REVIEW 6 FIX
D
Landmark Structure
Action
5 landmarks
FIX
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
4 <nav> landmark(s) found
Warning::
1 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No contentinfo (footer) landmark
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 (missing!) CONTENTINFO (missing!)

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

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

F
Heading Hierarchy
Action
37 headings, 6 skip(s)
FIX
37 headings, 6 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Sign Up for Our Amazing Newsletter!
  • H6 Visible planets and night sky guide for April and May skipped
  • H6 The Lyrid meteor shower peaks tonight. Don’t miss it!
  • H6 Meteor showers are here! 10 easy tips for watching
  • H2 Lights out for birds during spring migration!
  • H5 Black hole Cygnus X-1 has fast, powerful dancing jets skipped
  • H5 Summer solstice in Mars’ southern hemisphere is April 25
  • H3 Happy Earth Day! Why do we celebrate it on April 22?
  • H3 Earth images from space: 10 incredible photos of our planet
  • H3 Sun news: Sun-stuff could reach Earth this week
  • H3 Visible planets and night sky guide for April and May
  • H3 A pileus cloud means bad weather is on the way
  • H3 The Lyrid meteor shower peaks tonight. Don’t miss it!
  • H3 Meteor showers are here! 10 easy tips for watching
  • H3 Meet M13, the Great Globular Cluster in Hercules
  • H4 Follow on Bluesky
  • H3 Subscribe now! A daily update with Science news, great photos, sky alerts.
  • H3 Space
  • H5 Black hole Cygnus X-1 has fast, powerful dancing jets skipped
  • H5 Summer solstice in Mars’ southern hemisphere is April 25
  • H5 Earth images from space: 10 incredible photos of our planet
  • H5 Can we find alien life in groups of similar planets?
  • H3 Astronomy Essentials
  • H5 Visible planets and night sky guide for April and May skipped
  • H5 The Lyrid meteor shower peaks tonight. Don’t miss it!
  • H5 Meteor showers are here! 10 easy tips for watching
  • H5 Meet M13, the Great Globular Cluster in Hercules
  • H3 Earth
  • H5 Lights out for birds during spring migration! skipped
  • H5 Happy Earth Day! Why do we celebrate it on April 22?
  • H5 A pileus cloud means bad weather is on the way
  • H5 Small ants clean larger ants in a surprising twist of nature
  • H3 Human World
  • H5 Happy Earth Day! Why do we celebrate it on April 22? skipped
  • H5 International Dark Sky Week is April 13 to 20
  • H5 Native Americans played dice more than 12,000 years ago
  • H5 Pareidolia is seeing things like faces in random objects

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

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

F
Form Accessibility
Action
7 of 7 controls have issues
FIX
7 of 7 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit">; <input type="submit">; <input type="text" name="cpro_hp_feedback_field_285191">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email" id="EMAIL">; <input type="search" name="s" id="search">; <input type="email" name="email" id="email">
7 controls
0 labeled
3 placeholder only
4 unlabeled
ControlTypeLabelMethod
#EMAILemail(Email address)placeholder only
#searchsearch( Search...)placeholder only
#emailemail(Email Address)placeholder only
inputsubmit(none)none
inputsubmit(none)none
inputsubmit(none)none
cpro_hp_feedback_field_285191text(none)none

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

<input type="submit">; <input type="submit">; <input type="submit">; <input type="text" name="cpro_hp_feedback_field_285191">

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="email" name="email" id="EMAIL">; <input type="search" name="s" id="search">; <input type="email" name="email" id="email">

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
Not found
FIX
Not found
Info::
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.

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::
4 navigation landmark(s) detected
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 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Page not found – EarthSky Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA 14 pass AA only
h3 Sign Up for Our Amazing Newsletter!
2.86:1
#000000
on
#555658
needs 3.0:1 (large text)
19px · top of page (header area)
title EarthSky | Updates on your cosmos and wo…
2.63:1
#000000
on
#4F5153
needs 4.5:1 (normal text)
16px · top of page (header area)
p A daily update by email. Science news, g…
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · top of page (header area)
div Your email address will only be used for…
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · top of page (header area)
a Privacy Policy
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
div Thank you! Your submission has been rece…
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Lights out for birds…3.24:13.0:1
#000000
#5E5E5E
Pass
h3 Sign Up for Our Amaz…2.86:13.0:1
#000000
#555658
Fail
h3 Happy Earth Day! Why…3.24:13.0:1
#000000
#5E5E5E
Pass
h3 Earth images from sp…3.24:13.0:1
#000000
#5E5E5E
Pass
h3 Sun news: Sun-stuff …3.24:13.0:1
#000000
#5E5E5E
Pass
h3 Visible planets and …3.24:13.0:1
#000000
#5E5E5E
Pass
h3 A pileus cloud means…3.24:13.0:1
#000000
#5E5E5E
Pass
h3 The Lyrid meteor sho…3.24:13.0:1
#000000
#5E5E5E
Pass
h3 Meteor showers are h…3.24:13.0:1
#000000
#5E5E5E
Pass
h3 Meet M13, the Great …3.24:13.0:1
#000000
#5E5E5E
Pass
h3 Subscribe now! A dai…3.24:13.0:1
#000000
#5E5E5E
Pass
h3 Space3.24:13.0:1
#000000
#5E5E5E
Pass
h3 Astronomy Essentials3.24:13.0:1
#000000
#5E5E5E
Pass
h3 Earth3.24:13.0:1
#000000
#5E5E5E
Pass
h3 Human World3.24:13.0:1
#000000
#5E5E5E
Pass
title EarthSky | Updates o…2.63:14.5:1
#000000
#4F5153
Fail
p A daily update by em…3.66:14.5:1
#000000
#666666
Fail
div Your email address w…3.66:14.5:1
#000000
#666666
Fail
a Privacy Policy3.66:14.5:1
#000000
#666666
Fail
div Thank you! Your subm…3.66:14.5:1
#000000
#666666
Fail

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.

B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 26 passed
REVIEW
88

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
Accept All div.cmpboxbtns > span#cmpwelcomebtnyes > a.cmpboxbtn > span#cmpbntyestxt
Earth div.full-height > a.post-card-v2-max > div.post-card-content > div.badge
Space div.w-dyn-item > div.post-card > a.thumbnail-small > div.badge

These are opportunities to improve the legibility of your content.

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
Black hole Cygnus X-1 has fast, powerful dancing jets div.w-dyn-item > div.post-card > a.post-heading-link > h5.post-heading-small
Black hole Cygnus X-1 has fast, powerful dancing jets div.w-dyn-item > div.post-card > a.post-heading-link > h5.post-heading-small
Visible planets and night sky guide for April and May div.w-dyn-item > div.post-card > a.post-heading-link > h5.post-heading-small
Lights out for birds during spring migration! div.w-dyn-item > div.post-card > a.post-heading-link > h5.post-heading-small
Happy Earth Day! Why do we celebrate it on April 22? div.w-dyn-item > div.post-card > a.post-heading-link > h5.post-heading-small

These are opportunities to improve keyboard navigation in your application.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.cp-popup-wrapper > div.cp-popup > div.cp-popup-content > input.cpro-hp-field div.cp-popup-wrapper > div.cp-popup > div.cp-popup-content > input.cpro-hp-field

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.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small
div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small
div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small
div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small
div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small
div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small
div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small
div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small
div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small
div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small
div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small
div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small
div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small
div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small
div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small
div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small div.grid-small > div.w-dyn-item > div.post-card > a.thumbnail-small
div.section > div.wrapper > div.connect-2 > a.connect-link div.section > div.wrapper > div.connect-2 > a.connect-link
div.section > div.wrapper > div.connect-2 > a.connect-link div.section > div.wrapper > div.connect-2 > a.connect-link
div.section > div.wrapper > div.connect-2 > a.connect-link div.section > div.wrapper > div.connect-2 > a.connect-link
div.section > div.wrapper > div.connect-2 > a.connect-link div.section > div.wrapper > div.connect-2 > a.connect-link
div.section > div.wrapper > div.connect-2 > a.connect-link div.section > div.wrapper > div.connect-2 > a.connect-link

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
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
Input buttons have discernible text.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
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
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
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
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
`<input type="image">` elements have `[alt]` text
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
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.
Uses ARIA roles only on compatible elements
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.
A+
Alt Text Quality
All 53 images OK
PASS
All 53 images OK
Info::
52 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
53 images 1 good alt text 52 decorative
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback