Skip to content
https://theseocover.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
6
REVIEW
7
PASS
11
INFO
0
Checks
24
11 PASS 7 REVIEW 6 FIX
F
Alt Text Quality
Action
26 of 27 images have issues
FIX
26 of 27 images have issues
Critical::
26 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
26 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with good alt text
27 images 1 good alt text 26 missing
IssueCount
missing26 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-ay8knh
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://theseocover.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://theseocover.com/manifest.json

Manifest contains invalid JSON.

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: #00070f
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::
3 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 3 <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
26 landmarks
REVIEW
26 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <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 "Sections" 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

C
Mobile Keyboard & Autofill
Action
2/3 eligible field(s) missing autocomplete or inputmode
REVIEW
2/3 eligible field(s) missing autocomplete or inputmode
Warning::
2 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email, search.
Got: <input type="email" name="email">, <input type="search" name="q">
C
Tabindex Anti-Patterns
Action
0 positive, 8 -1-on-focusable
REVIEW
0 positive, 8 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
C
Mobile-Readable Font Sizes
Action
77% of visible text renders at >= 12 CSS px (78 below threshold)
REVIEW
77% of visible text renders at >= 12 CSS px (78 below threshold)
Warning::
78 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.0px ("Today's cover story"); <span> 11.0px ("Live"); <b> 11.0px ("Hugging Face Blog"); <p> 11.0px ("· 2026-09-22 ·"); <a> 11.0px ("Read →").
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 SEO Voices
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Newsletters
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Podcasts
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Communities
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Daily Brief
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Most-read
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 From the desk
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Topic
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 SEO Experts
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Essential Tools
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Latest
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Essential Tools
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Free Learning
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Conferences
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Browser Extensions
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Technical SEO
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 AI Search
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Content Strategy
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Analytics & Measurement
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 AI Tools
1.03:1
#000000
on
#00060E
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 SEO Voices1.03:13.0:1
#000000
#00060E
Fail
h2 Newsletters1.03:13.0:1
#000000
#00060E
Fail
h2 Podcasts1.03:13.0:1
#000000
#00060E
Fail
h2 Communities1.03:13.0:1
#000000
#00060E
Fail
h2 Daily Brief1.03:13.0:1
#000000
#00060E
Fail
h2 Most-read1.03:13.0:1
#000000
#00060E
Fail
h2 From the desk1.03:13.0:1
#000000
#00060E
Fail
h2 Topic1.03:13.0:1
#000000
#00060E
Fail
h2 SEO Experts1.03:13.0:1
#000000
#00060E
Fail
h2 Essential Tools1.03:13.0:1
#000000
#00060E
Fail
h2 Latest1.03:13.0:1
#000000
#00060E
Fail
h2 Essential Tools1.03:13.0:1
#000000
#00060E
Fail
h2 Free Learning1.03:13.0:1
#000000
#00060E
Fail
h2 Conferences1.03:13.0:1
#000000
#00060E
Fail
h2 Browser Extensions1.03:13.0:1
#000000
#00060E
Fail
h3 Technical SEO1.03:13.0:1
#000000
#00060E
Fail
h3 AI Search1.03:13.0:1
#000000
#00060E
Fail
h3 Content Strategy1.03:13.0:1
#000000
#00060E
Fail
h3 Analytics & Measurem…1.03:13.0:1
#000000
#00060E
Fail
h3 AI Tools1.03:13.0:1
#000000
#00060E
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.

A+
Heading Hierarchy
48 headings
PASS
48 headings
Info::
Single H1 present
  • H1 The SEOCover
  • H2 Jun Kim, oMLX creator and maintainer, joins Hugging Face to support the MLX community
  • H2 SEO Voices
  • H2 Newsletters
  • H2 Podcasts
  • H2 Communities
  • H2 Daily Brief
  • H2 Most-read
  • H2 From the desk
  • H2 Topic
  • H3 Technical SEO
  • H3 AI Search
  • H3 Content Strategy
  • H3 Analytics & Measurement
  • H3 AI Tools
  • H3 Link Building
  • H3 AI Agents
  • H3 Local SEO
  • H3 AI Models
  • H2 SEO Experts
  • H3 Barry Schwartz
  • H3 Lily Ray
  • H3 Brian Dean
  • H3 Glen Allsopp
  • H3 John Mueller
  • H3 Patrick Stox
  • H3 Aleyda Solís
  • H2 Essential Tools
  • H3 Google Search Console — Free Search Performance Data
  • H3 Screaming Frog SEO Spider — Desktop Site Crawler
  • H3 Ahrefs — SEO Toolset for Keywords, Backlinks & Content
  • H2 Latest
  • H3 3 Steps To Win B2B Brand Consideration, Day Zero Decides The Shortlist
  • H3 Jun Kim, oMLX creator and maintainer, joins Hugging Face to support the MLX community
  • H3 Google Business Profiles Permanently Closed Option Gone?
  • H3 Gemini Notebook Pages Spamming Google Search
  • H3 Google AI Overview Links Pushing You To AI Mode Over Web Pages
  • H3 Transformers now runs llama.cpp quants
  • H3 Google Business Profiles Email: Detected A Spike In Spam Reviews
  • H3 Google Merchant Center Updates Requirements For Google Store Ratings
  • H3 Google Analytics Adds Include Filters For Hostnames
  • H3 Japanese Google Search Office Hours（ #Google検索オフィスアワー 2026 年 09 月 24 日）
  • H3 Google's AI contribution pilot pays publishers
  • H3 Job Boards Say Google Indexing API Requests Get No Response
  • H2 Essential Tools
  • H2 Free Learning
  • H2 Conferences
  • H2 Browser Extensions
A+
Heading Text Quality
All 48 heading(s) have substantive, well-formed text
PASS
All 48 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
emailemailEmail addressaria-label
qsearchSearch resourcesaria-label
A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
A
Lighthouse Accessibility Audits
Score 90/100 — 2 failing, 21 passed
PASS
90

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
01 app-sidebar-section > section.idx > header.idx__head > span.idx__num
WORTH FOLLOWING section.idx > header.idx__head > div.idx__meta > p.idx__sub
02 app-sidebar-section > section.idx > header.idx__head > span.idx__num
SUBSCRIBE & LEARN section.idx > header.idx__head > div.idx__meta > p.idx__sub
03 app-sidebar-section > section.idx > header.idx__head > span.idx__num
ON THE COMMUTE section.idx > header.idx__head > div.idx__meta > p.idx__sub
04 app-sidebar-section > section.idx > header.idx__head > span.idx__num
WHERE SEOS TALK section.idx > header.idx__head > div.idx__meta > p.idx__sub
READ FULL TAKE → li.daily-brief__item > div#daily-brief-body-0 > p.daily-brief__cta > a
WEBSITE-DESIGN section.desk-feed > div.desk-feed__grid > a.desk-card > span.desk-card__lane
AI section.desk-feed > div.desk-feed__grid > a.desk-card > span.desk-card__lane
WEBSITE-DESIGN section.desk-feed > div.desk-feed__grid > a.desk-card > span.desk-card__lane
SEO-AEO-GEO section.desk-feed > div.desk-feed__grid > a.desk-card > span.desk-card__lane
01 div.body-grid__main > section#topics > header.browse-section__head > span.browse-section__num
02 div.body-grid__main > section#experts > header.browse-section__head > span.browse-section__num
03 div.body-grid__main > section#tools > header.browse-section__head > span.browse-section__num
01 section#tools > ul.tool-list > li.tool-row > div.tool-row__num
02 section#tools > ul.tool-list > li.tool-row > div.tool-row__num
03 section#tools > ul.tool-list > li.tool-row > div.tool-row__num
04 div.body-grid__main > section#latest > header.browse-section__head > span.browse-section__num
More in Technical SEO → div.body-grid__main > section#latest > div.see-more > a.see-more__link
05 app-sidebar-section > section.idx > header.idx__head > span.idx__num
DAILY-DRIVER TOOLBELT section.idx > header.idx__head > div.idx__meta > p.idx__sub
06 app-sidebar-section > section.idx > header.idx__head > span.idx__num
WHERE TO START section.idx > header.idx__head > div.idx__meta > p.idx__sub
07 app-sidebar-section > section.idx > header.idx__head > span.idx__num
INDUSTRY GATHERINGS section.idx > header.idx__head > div.idx__meta > p.idx__sub
08 app-sidebar-section > section.idx > header.idx__head > span.idx__num
ALWAYS INSTALLED section.idx > header.idx__head > div.idx__meta > p.idx__sub
THE DAILY BRIEF app-newsletter-signup > section.news > div.news__copy > p.news__eyebrow

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.trending-strip__rail > a.trending-strip__card > span.trending-strip__thumb > img div.trending-strip__rail > a.trending-strip__card > span.trending-strip__thumb > img
app-article-row > article.article-row > a.article-row__thumb > img app-article-row > article.article-row > a.article-row__thumb > img
app-article-row > article.article-row > a.article-row__thumb > img app-article-row > article.article-row > a.article-row__thumb > img
app-article-row > article.article-row > a.article-row__thumb > img app-article-row > article.article-row > a.article-row__thumb > img

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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●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.
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback