Skip to content
https://slashdot.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
46
GRADE
F
FIX
7
REVIEW
5
PASS
1
INFO
0
Checks
13
1 PASS 5 REVIEW 7 FIX
D
Form Accessibility
Action
20 of 27 controls have issues
FIX
20 of 27 controls have issues
Critical::
19 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="unickname">; <input type="password" name="upasswd">; <input type="submit" name="userlogin">; <input type="text">; <input type="text">; <input type="text">; <input type="text">; <input type="text">; <input type="text">; <input type="text"> (+9 more)
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="fhfilter">
Info::
7 control(s) properly labeled
27 controls
7 labeled
1 placeholder only
19 unlabeled
ControlTypeLabelMethod
login_tempcheckboxnone
aidradionone
aidradionone
aidradionone
aidradionone
aidradionone
aidradionone
fhfiltertext(Search)placeholder only
inputtext(none)none
inputtext(none)none
inputtext(none)none
inputtext(none)none
inputtext(none)none
inputtext(none)none
inputtext(none)none
inputtext(none)none
inputtext(none)none
inputtext(none)none
inputtext(none)none
inputtext(none)none
upasswdpassword(none)none
unicknametext(none)none
userloginsubmit(none)none
inputtext(none)none
inputtext(none)none
inputtext(none)none
#opt-togglecheckbox(none)none

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

<input type="text" name="unickname">; <input type="password" name="upasswd">; <input type="submit" name="userlogin">; <input type="text">; <input type="text">; <input type="text">; <input type="text">; <input type="text">; <input type="text">; <input type="text"> (+9 more)

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="fhfilter">

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
2 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 2 <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
Landmark Structure
Action
65 landmarks
REVIEW
65 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 "Global Navigation" MAIN (missing!) ASIDE CONTENTINFO footer

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

C
Heading Hierarchy
Action
33 headings
REVIEW
33 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Slashdot
  • H2 Boston Dynamics' Robot Dog Can Now Read Gauges, Spot Spills, and Reason (ieee.org) 2
  • H2 US Jobs Too Important To Risk Chinese Car Imports, Says Ford CEO (arstechnica.com) 26
  • H2 Compare the top business software of 2026
  • H2 Cal.com Is Going Closed Source Because of AI 26
  • H2 Live Nation Illegally Monopolized Ticketing Market, Jury Finds (cnn.com) 23
  • H2 Anna's Archive Loses $322 Million Spotify Piracy Case Without a Fight (torrentfreak.com) 39
  • H2 Snapchat Blames AI As It Cuts 1,000 Jobs 24
  • H2 Struggling Shoe Retailer Allbirds Pivots To AI, Stock Explodes More Than 700% 67
  • H2 Rivian's Illinois Factory Will Run On Recycled EV Batteries (yahoo.com) 35
  • H2 Norway Man Cured of HIV With Brother's Stem Cells 15
  • H2 Sony Boss Urges Theaters To Stop 30 Minutes of Trailers and Ads Before Movies (variety.com) 126
  • H2 Amazon Buys Globalstar For $10.8 Billion, Moving To Expand Its Satellite Internet Service (nytimes.com) 26
  • H2 Sony Is Removing Many Popular Features From Its Free OTA TV Options (cordcuttersnews.com) 75
  • H2 FCC Grants Netgear Conditional Approval For Routers (pcmag.com) 61
  • H2 Microsoft Reveals Major Price Increase For All Surface PCs (windowscentral.com) 36
  • H2 California Ghost-Gun Bill Wants 3D Printers To Play Cop, EFF Says (theregister.com) 135
  • H2 Slashdot Top Deals
  • H2 Compare the top business software of 2026
  • H2 Slashdot Top Deals
  • H2 Slashdot Deals
  • H2 Slashdot Poll
  • H3 By the end of 2026, how useful do you think agentic/multi-agent AI systems will actually be in your daily work or personal projects?
  • H3 (empty)
  • H3 Looks like someone has already voted from this IP. If you would like to vote please login and try again.
  • H3 By the end of 2026, how useful do you think agentic/multi-agent AI systems will actually be in your daily work or personal projects?
  • H3 (empty)
  • H2 Most Discussed
  • H2 Science
  • H2 This Day on Slashdot
  • H2 Sourceforge Top Downloads
  • H2 YOUR PRIVACY CHOICES (DO NOT SELL/SHARE/TARGET)
  • H3 Slashdot

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
5 of 21 images have issues
REVIEW
5 of 21 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 decorative image(s) correctly marked
Info::
15 image(s) with good alt text
21 images 15 good alt text 1 decorative 5 missing
IssueCount
missing5 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
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Bluesky ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 1 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Slashdot Top Deals16.98:13.0:1
#000000
#E7E7E7
Pass
h2 Slashdot Top Deals16.98:13.0:1
#000000
#E7E7E7
Pass
h2 Slashdot Poll16.98:13.0:1
#000000
#E7E7E7
Pass
h2 Most Discussed16.98:13.0:1
#000000
#E7E7E7
Pass
h2 YOUR PRIVACY CHOICES…16.98:13.0:1
#000000
#E7E7E7
Pass
h3 By the end of 2026, …16.98:13.0:1
#000000
#E7E7E7
Pass
h3 Looks like someone h…16.98:13.0:1
#000000
#E7E7E7
Pass
h3 By the end of 2026, …16.98:13.0:1
#000000
#E7E7E7
Pass
title Slashdot: News for n…6.75:14.5:1
#000000
#689B9B
Pass
span Slashdot14.70:14.5:1
#000000
#99EB99
Pass
span Stories21.00:14.5:1
#000000
#FFFFFF
Pass
li Firehose21.00:14.5:1
#000000
#FFFFFF
Pass
a All21.00:14.5:1
#000000
#FFFFFF
Pass
a Popular21.00:14.5:1
#000000
#FFFFFF
Pass
span Polls21.00:14.5:1
#000000
#FFFFFF
Pass
span Software21.00:14.5:1
#000000
#FFFFFF
Pass
span Thought Leadership21.00:14.5:1
#000000
#FFFFFF
Pass
a Submit21.00:14.5:1
#000000
#FFFFFF
Pass
label Search Slashdot21.00:14.5:1
#000000
#FFFFFF
Pass
span Login21.00:14.5:1
#000000
#FFFFFF
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 90/100 — 3 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.

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
Sony Boss Urges Theaters To Stop 30 Minutes of Trailers and Ads Before Movies tbody > tr > td.details > h4.longTitle

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

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#footer > div.bottom > div.follow > a.social div#footer > div.bottom > div.follow > a.social
div#footer > div.bottom > div.follow > a.social div#footer > div.bottom > div.follow > a.social

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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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.
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●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.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○Buttons have an accessible name
○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 a valid value for its `[lang]` attribute
○`<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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○`<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.
○Identical links have the same purpose.
○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