Skip to content
https://css-tricks.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
D
Alt Text Quality
Action
7 of 50 images have issues
FIX
7 of 50 images have issues
Critical::
7 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with alt text over 125 characters
Info::
39 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
50 images 3 good alt text 39 decorative 7 missing
IssueCount
missing7 image(s)
too long1 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
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 403 Page Title Just a moment... Custom Styling Navigation Homepage Link Search Form
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
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: #ff7a18
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <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
Favicon & Branding
7 icon(s) detected
REVIEW
7 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
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Present
Manifest Icons Missing
Multiple Sizes Present
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
h1 Search results
1.37:1
#000000
on
#252525
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Popular
1.35:1
#000000
on
#242424
needs 3.0:1 (large text)
24px · mid-page
h2 this
1.35:1
#000000
on
#242424
needs 3.0:1 (large text)
24px · mid-page
h2 month
1.35:1
#000000
on
#242424
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Fresh From the Almanac
1.37:1
#000000
on
#252525
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Latest CSS Guides
1.37:1
#000000
on
#252525
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Classic Tricks
1.37:1
#000000
on
#252525
needs 3.0:1 (large text)
24px · bottom of viewport
h2 No results found
1.37:1
#000000
on
#252525
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Filter options
1.37:1
#000000
on
#252525
needs 3.0:1 (large text)
24px · bottom of viewport
title CSS-Tricks - A Website About Making Webs…
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · top of page (header area)
div CSS-Tricks
1.13:1
#000000
on
#131313
needs 4.5:1 (normal text)
16px · top of page (header area)
span Articles
1.50:1
#000000
on
#2C2C2C
needs 4.5:1 (normal text)
16px · top of page (header area)
span Guides
1.48:1
#000000
on
#2B2B2B
needs 4.5:1 (normal text)
16px · above the fold
span Almanac
1.48:1
#000000
on
#2B2B2B
needs 4.5:1 (normal text)
16px · above the fold
span Links
1.46:1
#000000
on
#2A2A2A
needs 4.5:1 (normal text)
16px · above the fold
span Picks
1.46:1
#000000
on
#2A2A2A
needs 4.5:1 (normal text)
16px · above the fold
span Shuffle
1.46:1
#000000
on
#2A2A2A
needs 4.5:1 (normal text)
16px · above the fold
span Search
1.44:1
#000000
on
#292929
needs 4.5:1 (normal text)
16px · above the fold
div Direct link to the article Making Comple…
1.44:1
#000000
on
#292929
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Search results1.37:13.0:1
#000000
#252525
Fail
h2 Popular1.35:13.0:1
#000000
#242424
Fail
h2 this1.35:13.0:1
#000000
#242424
Fail
h2 month1.35:13.0:1
#000000
#242424
Fail
h2 Fresh From the Alman…1.37:13.0:1
#000000
#252525
Fail
h2 Latest CSS Guides1.37:13.0:1
#000000
#252525
Fail
h2 Classic Tricks1.37:13.0:1
#000000
#252525
Fail
h2 No results found1.37:13.0:1
#000000
#252525
Fail
h2 Filter options1.37:13.0:1
#000000
#252525
Fail
title CSS-Tricks - A Websi…1.11:14.5:1
#000000
#111111
Fail
a Skip to main content1.11:14.5:1
#000000
#111111
Fail
div CSS-Tricks1.13:14.5:1
#000000
#131313
Fail
span Articles1.50:14.5:1
#000000
#2C2C2C
Fail
span Guides1.48:14.5:1
#000000
#2B2B2B
Fail
span Almanac1.48:14.5:1
#000000
#2B2B2B
Fail
span Links1.46:14.5:1
#000000
#2A2A2A
Fail
span Picks1.46:14.5:1
#000000
#2A2A2A
Fail
span Shuffle1.46:14.5:1
#000000
#2A2A2A
Fail
span Search1.44:14.5:1
#000000
#292929
Fail
div Direct link to the a…1.44:14.5:1
#000000
#292929
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 85/100 — 4 failing, 26 passed
REVIEW
85

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
NEWS div.article-article > header.article-publication-meta > div.tags > a
API div.article-article > header.article-publication-meta > div.tags > a
NEWS div.article-article > header.article-publication-meta > div.tags > a
FORMS div.article-article > header.article-publication-meta > div.tags > a
ARTIFICIAL INTELLIGENCE div.article-article > header.article-publication-meta > div.tags > a

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
article#post-392986 > div.article-article > div.author-row > img article#post-392986 > div.article-article > div.author-row > img
article#post-392794 > div.article-article > div.author-row > img article#post-392794 > div.article-article > div.author-row > img
article#post-393070 > div.article-article > div.author-row > img article#post-393070 > div.article-article > div.author-row > img
article#post-393306 > div.article-article > div.author-row > img article#post-393306 > div.article-article > div.author-row > img
article#post-391993 > div.article-article > div.author-row > img article#post-391993 > div.article-article > div.author-row > img
article#post-391438 > div.article-article > div.author-row > img article#post-391438 > div.article-article > div.author-row > img
footer.site-footer > div#teconsent > a#icon-id04999198214163916 > img footer.site-footer > div#teconsent > a#icon-id04999198214163916 > 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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#gform_fields_3 > div#field_3_1 > div.ginput_container > input#input_3_1 div#gform_fields_3 > div#field_3_1 > div.ginput_container > input#input_3_1
div#gform_wrapper_3 > form#gform_3 > div.gform-footer > input#gform_submit_button_3 div#gform_wrapper_3 > form#gform_3 > div.gform-footer > input#gform_submit_button_3

These are opportunities to improve keyboard navigation in your application.

Best practices

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
SELECT div.mini-card-grid > article#mini-post-392463 > div.tags > a
DESTRUCTURING div.mini-card-grid > article#mini-post-392714 > div.tags > a
JAVASCRIPT div.mini-card-grid > article#mini-post-392714 > div.tags > a
CSS FUNCTIONS div.mini-card-grid > article#mini-post-391573 > div.tags > a
SHAPES div.mini-card-grid > article#mini-post-391573 > div.tags > a

These items highlight common accessibility best practices.

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
`[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
`[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
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
All heading elements contain content.
Identical links have the same purpose.
`[accesskey]` values are unique
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
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 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.
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>`.
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
Landmark Structure
16 landmarks
PASS
16 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN ASIDE "Open Cookie Preferences Modal" 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

A
Heading Hierarchy
56 headings
PASS
56 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Making Complex CSS Shapes Using shape()
  • H2 Popular this month
  • H3 Abusing Customizable Selects
  • H3 Experimenting With Scroll-Driven corner-shape Animations
  • H3 JavaScript for Everyone: Destructuring
  • H3 An Exploit … in CSS?!
  • H3 Trying to Make the Perfect Pie Chart in CSS
  • H3 Responsive Hexagon Grid Using Modern CSS
  • H3 CSS Bar Charts Using Modern Functions
  • H3 Styling ::search-text and Other Highlight-y Pseudo-Elements
  • H2 Latest Articles
  • H2 Front-End Fools: Top 10 April Fools’ UI Pranks of All Time
  • H2 Sniffing Out the CSS Olfactive API
  • H2 What’s !important #8: Light/Dark Favicons, @mixin, object-view-box, and More
  • H2 Form Automation Tips for Happier User and Clients
  • H2 Generative UI Notes
  • H2 Quick Hits
  • H2 Collections
  • H2 Fresh From the Almanac
  • H3 view()
  • H3 view-timeline-axis
  • H3 view-timeline-inset
  • H3 scroll()
  • H3 scroll-timeline-axis
  • H3 scroll-timeline-name
  • H3 timeline-scope
  • H3 animation-range
  • H2 Latest CSS Guides
  • H3 CSS Color Functions
  • H3 Styling Counters in CSS
  • H3 CSS Anchor Positioning Guide
  • H3 CSS Selectors
  • H3 CSS Length Units
  • H3 CSS Container Queries
  • H3 CSS Media Queries Guide
  • H3 Cascade Layers Guide
  • H3 CSS Functions Guide
  • H3 CSS Gradients Guide
  • H3 CSS Custom Properties Guide
  • H2 Classic Tricks
  • H3 Scroll Animation
  • H3 Yellow Flash
  • H3 Self-Drawing Shapes
  • H3 Scroll Shadows
  • H3 Editable Style Blocks
  • H3 Scroll Indicator
  • H3 Border Triangles
  • H3 Pin Scrolling to Bottom
  • H3 Infinite Scrolling Background Image
  • H4 Keep up to date on web dev
  • H5 DigitalOcean
  • H5 CSS-Tricks
  • H5 Social
  • H1 Search results duplicate H1
  • H2 No results found
  • H2 Filter options

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

A
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="gform_submit_button_3">
Info::
3 control(s) properly labeled
4 controls
3 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#input_3_1emailEmailfor/id
ak_hp_textareatextareaΔnone
#jetpack-instant-search__box-input-1searchMagnifying Glassnone
#gform_submit_button_3submit(none)none

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

<input type="submit" id="gform_submit_button_3">

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback