Skip to content
https://techdirt.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
36
GRADE
F
FIX
10
REVIEW
2
PASS
1
INFO
0
Checks
13
1 PASS 2 REVIEW 10 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
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.

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

F
Heading Hierarchy
Action
41 headings, 12 skip(s)
FIX
41 headings, 12 skip(s)
Warning::
Multiple H1 headings (10 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
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::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Kash Patel’s Defamation Suit Against The Atlantic Is Designed To Generate Headlines, Not Win In Court
  • H3 from the fbi-slapps dept skipped
  • H1 You Can’t Vote Out Amazon Web Services: Fighting Internet Contracts One Library At A Time duplicate H1
  • H3 from the librarians-take-a-stand dept skipped
  • H1 Judge Acquits Penis Costume-Wearing Grandma While Saying Some Dumb Stuff About Probable Cause duplicate H1
  • H3 from the first-amendment-isn't-subjective dept skipped
  • H1 Daily Deal: The Complete Big Data And Power BI Bundle duplicate H1
  • H3 from the good-deals-on-cool-stuff dept skipped
  • H1 The Kids Are (Mostly) Alright: New Pew Study Deflates The Social Media Panic duplicate H1
  • H3 from the another-moral-panic-bubble-popped dept skipped
  • H1 CBS Hosting Dinner Praising Trump And His Love Of The First Amendment duplicate H1
  • H3 from the lying-liars-and-the-lies-they-tell dept skipped
  • H1 YouTuber Copyright Struck After Others Layer AI Voiceovers On Video Game Music duplicate H1
  • H3 from the fix-this-youtube dept skipped
  • H1 Caught In The Crackdown: As Arrests At Anti-ICE Protests Piled Up, Prosecutions Crumbled duplicate H1
  • H3 from the lying-liars dept skipped
  • H3 “We Must Identify Him”
  • H3 “They Were Just Randomly Grabbing People”
  • H3 Felony Charges Downgraded
  • H3 In Handcuffs and Intimidated
  • H1 Palantir Goes Mask-Off For Fascism. It Won’t End Well. duplicate H1
  • H3 from the a-very-bad-bet dept skipped
  • H1 Rep. Mike Johnson Tries, Fails To Sneak Clean Section 702 Re-Authorization Past The Goal Line duplicate H1
  • H3 from the not-today,-second-rate-satan dept skipped
  • H3 Techdirt Daily Newsletter
  • H2 Get all our posts in your inbox with the Techdirt Daily Newsletter!
  • H4 The Techdirt Greenhouse skipped
  • H2 Monday
  • H2 Sunday
  • H2 Saturday
  • H2 Friday
  • H2 Thursday
  • H2 Wednesday
  • H2 Tuesday
  • H5 More skipped
  • H2 Email This Story
  • H3 (empty)
  • H2 Tools & Services
  • H2 Company
  • H2 Contact
  • H2 More

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

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

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

F
Alt Text Quality
Action
32 of 46 images have issues
FIX
32 of 46 images have issues
Critical::
32 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
31 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
7 decorative image(s) correctly marked
Info::
7 image(s) with good alt text
46 images 7 good alt text 7 decorative 32 missing
IssueCount
missing32 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
Form Accessibility
Action
6 of 9 controls have issues
FIX
6 of 9 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="checkbox" id="user_toggle_checkbox">; <input type="submit" name="td_subscribe" id="td_subscribe">; <input type="submit">; <input type="submit">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="q">; <input type="email" name="email" id="sub_email">
Info::
3 control(s) properly labeled
9 controls
3 labeled
2 placeholder only
4 unlabeled
ControlTypeLabelMethod
#tabs_toggle_checkboxcheckboxTechdirtfor/id
data[email]emailPlease leave this field emptynone
#form_email_2emailEmail Address *aria-label
qsearch(Search Techdirt)placeholder only
#sub_emailemail(Enter Your Email Address)placeholder only
#user_toggle_checkboxcheckbox(none)none
#td_subscribesubmit(none)none
inputsubmit(none)none
inputsubmit(none)none

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

<input type="checkbox" id="user_toggle_checkbox">; <input type="submit" name="td_subscribe" id="td_subscribe">; <input type="submit">; <input type="submit">

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="search" name="q">; <input type="email" name="email" id="sub_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
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 ModeNo Dark Mode Detected
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 66/100 — 11 failing, 18 passed
FIX
66

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#header > div#hdr_search > form#searchform > button.search-submit div#header > div#hdr_search > form#searchform > button.search-submit

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.maincol-top > div > a > img div.maincol-top > div > a > img
div.postbody > div.details > a > img.topic_icon div.postbody > div.details > a > img.topic_icon
div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img
div.postbody > div.details > a > img.topic_icon div.postbody > div.details > a > img.topic_icon
div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img
div.postbody > div.details > a > img.topic_icon div.postbody > div.details > a > img.topic_icon
div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img
div.postbody > div.details > a > img.topic_icon div.postbody > div.details > a > img.topic_icon
div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img
div.postbody > div.details > a > img.topic_icon div.postbody > div.details > a > img.topic_icon
div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img
div.postbody > div.details > a > img.topic_icon div.postbody > div.details > a > img.topic_icon
div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img
div.postbody > div.details > a > img.topic_icon div.postbody > div.details > a > img.topic_icon
div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img
div.postbody > div.details > a > img.topic_icon div.postbody > div.details > a > img.topic_icon
div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img
div.postbody > div.details > a > img.topic_icon div.postbody > div.details > a > img.topic_icon
div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img
div.postbody > div.details > a > img.topic_icon div.postbody > div.details > a > img.topic_icon
div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img div.storyfooter > a.expanderlink > span.td-expand-collapse-text > img
body.home > img body.home > img

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.maincol-top > div > div > iframe div.maincol-top > div > div > iframe
figure.wp-block-embed > div.wp-block-embed__wrapper > div.bluesky-embed > iframe figure.wp-block-embed > div.wp-block-embed__wrapper > div.bluesky-embed > iframe
figure.wp-block-embed > div.wp-block-embed__wrapper > div.bluesky-embed > iframe figure.wp-block-embed > div.wp-block-embed__wrapper > div.bluesky-embed > iframe
figure.wp-block-embed > div.wp-block-embed__wrapper > div.bluesky-embed > iframe figure.wp-block-embed > div.wp-block-embed__wrapper > div.bluesky-embed > iframe
figure.wp-block-embed > div.wp-block-embed__wrapper > div.bluesky-embed > iframe figure.wp-block-embed > div.wp-block-embed__wrapper > div.bluesky-embed > 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#maincolumn > div.maincol-top > div > a div#maincolumn > div.maincol-top > div > a
div.story > div.postbody > div.details > a div.story > div.postbody > div.details > a
div.story > div.postbody > div.details > a div.story > div.postbody > div.details > a
div.story > div.postbody > div.details > a div.story > div.postbody > div.details > a
div.story > div.postbody > div.details > a div.story > div.postbody > div.details > a
div.story > div.postbody > div.details > a div.story > div.postbody > div.details > a
div.story > div.postbody > div.details > a div.story > div.postbody > div.details > a
div.story > div.postbody > div.details > a div.story > div.postbody > div.details > a
div.story > div.postbody > div.details > a div.story > div.postbody > div.details > a
div.story > div.postbody > div.details > a div.story > div.postbody > div.details > a
div.story > div.postbody > div.details > a div.story > div.postbody > div.details > 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.

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
EXPAND ALL POSTS div#maincolumn > div.maincolumn_head > div#expandercontrols > a.expand-all
COLLAPSE ALL POSTS div#maincolumn > div.maincolumn_head > div#expandercontrols > a.collapse-all
Follow Techdirt div#rightcolumn > section > div#techdirt_social-2 > div.rightcolumn_head
Subscribe to Our Newsletter div#rightcolumn > section > div#mailpoet_form-2 > div.rightcolumn_head
A weekly news podcast from Mike Masnick & Ben Whitelaw div#middle > div#rightcolumn > div > p
Mike Masnick div#rightcolumn > div > p > b
Ben Whitelaw div#rightcolumn > div > p > b
Subscribe now to Ctrl-Alt-Speech » div#middle > div#rightcolumn > div > a
Essential Reading div#rightcolumn > section > div#techdirt_featured-2 > div.rightcolumn_head
Techdirt Deals div#middle > div#rightcolumn > section > div.rightcolumn_head
BUY NOW div.scw-wrap > div.scw-item > a.scw-price > div.scw-buy
Techdirt Insider Discord div#rightcolumn > section > div#techdirt_discord-2 > div.rightcolumn_head
deadspatula: div#chat-msgs > ul#messages > li.msg > span.handle
intelati: div#chat-msgs > ul#messages > li.msg > span.handle
[article] ul#messages > li.msg > span.msg-text > a
candescence: div#chat-msgs > ul#messages > li.msg > span.handle
[video] ul#messages > li.msg > span.msg-text > a
[article] ul#messages > li.msg > span.msg-text > a
Leah Abram: div#chat-msgs > ul#messages > li.msg > span.handle
[article] ul#messages > li.msg > span.msg-text > a
BentFranklin: div#chat-msgs > ul#messages > li.msg > span.handle
Become an Insider! div#chat-wrap > div#chat-footer > p > a.chat-cta-btn
Older Stuff div#rightcolumn > section > div#techdirt_older_stuff-2 > div.rightcolumn_head

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Floor64 div#bottom > div#pagefoot > div.ftrcopyright > a
privacy policy body.home > div.widget > div#eu-cookie-law > a

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
from the fbi-slapps dept div#storywrap-535620 > div.story > div.postbody > h3
from the librarians-take-a-stand dept div#storywrap-535478 > div.story > div.postbody > h3
from the first-amendment-isn't-subjective dept div#storywrap-535530 > div.story > div.postbody > h3
from the good-deals-on-cool-stuff dept div#storywrap-535661 > div.story > div.postbody > h3
from the another-moral-panic-bubble-popped dept div#storywrap-535504 > div.story > div.postbody > h3
from the lying-liars-and-the-lies-they-tell dept div#storywrap-535558 > div.story > div.postbody > h3
from the fix-this-youtube dept div#storywrap-535280 > div.story > div.postbody > h3
from the lying-liars dept div#storywrap-535428 > div.story > div.postbody > h3
from the a-very-bad-bet dept div#storywrap-535548 > div.story > div.postbody > h3
from the not-today,-second-rate-satan dept div#storywrap-535520 > div.story > div.postbody > h3
The Techdirt Greenhouse div#techdirt_featured-2 > div.rightcolumn_main > div#recreading > h4
More section > div#techdirt_older_stuff-2 > div.rightcolumn_main > h5

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Defamation div.postbody > div.details > p > a
Legal Issues div.postbody > div.details > p > a
Free Speech div.postbody > div.details > p > a
Deals div.postbody > div.details > p > a
Studies div.postbody > div.details > p > a
Failures div.postbody > div.details > p > a
Copyright div.postbody > div.details > p > a
Free Speech div.postbody > div.details > p > a
Failures div.postbody > div.details > p > a
Privacy div.postbody > div.details > p > a
https://hachyderm.io/@estherschi... ul#messages > li.msg > span.msg-text > a
Twitter div.menu-tools-services-container > ul#menu-tools-services > li#menu-item-297 > a
Facebook div.menu-tools-services-container > ul#menu-tools-services > li#menu-item-298 > a
RSS div.menu-tools-services-container > ul#menu-tools-services > li#menu-item-299 > a
Podcast div.menu-tools-services-container > ul#menu-tools-services > li#menu-item-300 > a
About Us div.menu-company-container > ul#menu-company > li#menu-item-187583 > a
Privacy div.menu-company-container > ul#menu-company > li#menu-item-187582 > a
Help & Feedback div.menu-contact-container > ul#menu-contact > li#menu-item-344296 > a
Media Kit div.menu-contact-container > ul#menu-contact > li#menu-item-167590 > a
Copia Institute div.menu-more-container > ul#menu-more > li#menu-item-309 > a
Insider Shop div.menu-more-container > ul#menu-more > li#menu-item-310 > a
Support Techdirt div.menu-more-container > ul#menu-more > li#menu-item-167588 > a
Designed with WordPress. div#bottom > div#pagefoot > div.ftrcopyright > a.imprint

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `[colspan]` attribute may improve the experience for screen reader users. Learn more about captions.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Monday 10:53 Daily Deal: The Complete Arduino, Raspberry Pi & ESP32 Bundle (0)… section > div#techdirt_older_stuff-2 > div.rightcolumn_main > table
○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
●Input buttons have discernible text.
●Form elements have associated labels
●ARIA attributes are used as specified for the element's role
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Deprecated ARIA roles were not used
●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-hidden="true"]` elements do not contain focusable descendents
○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 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
○`<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.
○`<td>` elements in a large `<table>` have one or more table headers.
B
Favicon & Branding
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::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 18 fail WCAG AA
REVIEW

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

2 pass 18 fail WCAG AA
h2 in your inbox with the Techdirt Daily Ne…
1.80:1
#000000
on
#393838
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Email This Story
1.80:1
#000000
on
#393838
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tools & Services
1.80:1
#000000
on
#393838
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Company
1.80:1
#000000
on
#393838
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Contact
1.80:1
#000000
on
#393838
needs 3.0:1 (large text)
24px · bottom of viewport
h2 More
1.80:1
#000000
on
#393838
needs 3.0:1 (large text)
24px · bottom of viewport
h3 from the
1.80:1
#000000
on
#393838
needs 3.0:1 (large text)
19px · bottom of viewport
h3 dept
1.80:1
#000000
on
#393838
needs 3.0:1 (large text)
19px · bottom of viewport
h3 from the
1.80:1
#000000
on
#393838
needs 3.0:1 (large text)
19px · bottom of viewport
h3 dept
1.80:1
#000000
on
#393838
needs 3.0:1 (large text)
19px · bottom of viewport
h3 from the
1.80:1
#000000
on
#393838
needs 3.0:1 (large text)
19px · bottom of viewport
h3 dept
1.80:1
#000000
on
#393838
needs 3.0:1 (large text)
19px · bottom of viewport
h3 from the
1.80:1
#000000
on
#393838
needs 3.0:1 (large text)
19px · bottom of viewport
h3 dept
1.80:1
#000000
on
#393838
needs 3.0:1 (large text)
19px · bottom of viewport
h3 from the
1.80:1
#000000
on
#393838
needs 3.0:1 (large text)
19px · bottom of viewport
h3 dept
1.80:1
#000000
on
#393838
needs 3.0:1 (large text)
19px · bottom of viewport
h3 from the
1.80:1
#000000
on
#393838
needs 3.0:1 (large text)
19px · bottom of viewport
h3 dept
1.80:1
#000000
on
#393838
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 in your inbox with t…1.80:13.0:1
#000000
#393838
Fail
h2 Email This Story1.80:13.0:1
#000000
#393838
Fail
h2 Tools & Services1.80:13.0:1
#000000
#393838
Fail
h2 Company1.80:13.0:1
#000000
#393838
Fail
h2 Contact1.80:13.0:1
#000000
#393838
Fail
h2 More1.80:13.0:1
#000000
#393838
Fail
h3 from the21.00:13.0:1
#000000
#FFFFFF
Pass
h3 dept21.00:13.0:1
#000000
#FFFFFF
Pass
h3 from the1.80:13.0:1
#000000
#393838
Fail
h3 dept1.80:13.0:1
#000000
#393838
Fail
h3 from the1.80:13.0:1
#000000
#393838
Fail
h3 dept1.80:13.0:1
#000000
#393838
Fail
h3 from the1.80:13.0:1
#000000
#393838
Fail
h3 dept1.80:13.0:1
#000000
#393838
Fail
h3 from the1.80:13.0:1
#000000
#393838
Fail
h3 dept1.80:13.0:1
#000000
#393838
Fail
h3 from the1.80:13.0:1
#000000
#393838
Fail
h3 dept1.80:13.0:1
#000000
#393838
Fail
h3 from the1.80:13.0:1
#000000
#393838
Fail
h3 dept1.80:13.0:1
#000000
#393838
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
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 Page not found | Techdirt ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback