Skip to content
https://backlinko.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
3
REVIEW
7
PASS
3
INFO
0
Checks
13
3 PASS 7 REVIEW 3 FIX
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: #ffffff
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::
5 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 5 <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.
B
Landmark Structure
12 landmarks
REVIEW
12 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
5 of 5 <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 MAIN 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

B
Heading Hierarchy
24 headings, 2 skip(s)
REVIEW
24 headings, 2 skip(s)
Info::
Single H1 present
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.
  • H2 About cookies on this site
  • H3 Semrush helps you:
  • H3 Backlinko readers get:
  • H2 Welcome to Backlinko
  • H1 Learn How to Win in the Future of AI Search
  • H3 How to Create an Effective SEO Strategy in 2026 skipped
  • H3 12 Best SEO Tools for 2026 (Used by Our Team Daily)
  • H3 Generative Engine Optimization (GEO): How to Win in AI Search
  • H3 LLM Seeding: A New SEO Strategy to Get Mentioned by LLMs
  • H3 7 Strategies to Get High Quality Backlinks in 2026
  • H2 Editor’s Picks
  • H3 On-Page SEO: The Definitive Guide
  • H3 28 Ways to Increase Traffic to Your Website
  • H3 How to Rank Higher (& Get More Visibility) on Google
  • H3 9 Courses That Actually Teach SEO and AI Search (Free + Paid)
  • H3 7 Proven Ways to Increase Your Domain Authority in 2026
  • H3 How to Conduct an AI + SEO Competitor Analysis in 2026
  • H3 Free Tool
  • H2 Find Keyword Ideas in Seconds
  • H2 Latest How-To Guides
  • H2 Backlinko Resource Hubs
  • H4 Learn skipped
  • H4 Company
  • H4 Connect

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

B
Form Accessibility
4 of 4 controls have issues
REVIEW
4 of 4 controls have issues
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">; <input type="text" name="url">; <input type="email" name="email" id="form-item-email">; <input type="text" id="keyword-overview-widget-input">
4 controls
0 labeled
4 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtext(Search)placeholder only
urltext(Enter domain, keyword or URL)placeholder only
#form-item-emailemail(Email Address)placeholder only
#keyword-overview-widget-inputtext(Enter keyword)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text">; <input type="text" name="url">; <input type="email" name="email" id="form-item-email">; <input type="text" id="keyword-overview-widget-input">

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

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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 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 Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Backlinko
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Backlinko ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode standalone ✓
Name Backlinko Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 1 icon(s)
A+
Alt Text Quality
All 15 images OK
PASS
All 15 images OK
Info::
15 image(s) with good alt text
15 images 15 good alt text
All images have appropriate alt text.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Learn How to Win in …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 About cookies on thi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Welcome to Backlinko21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Editor’s Picks21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Find Keyword Ideas i…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Latest How-To Guides21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Backlinko Resource H…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Backlinko readers ge…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 How to Create an Eff…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 12 Best SEO Tools fo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Generative Engine Op…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 LLM Seeding: A New S…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 7 Strategies to Get …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 On-Page SEO: The Def…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 28 Ways to Increase …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 How to Rank Higher (…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 9 Courses That Actua…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 7 Proven Ways to Inc…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 How to Conduct an AI…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Free Tool21.00:13.0: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, 26 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.

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.css-w8j2lc > div.css-1ezowm5 > div.css-124fu8r > button div.css-w8j2lc > div.css-1ezowm5 > div.css-124fu8r > button
div.css-1gmiqn5 > div.css-93tl4h > div.css-1181h5a > button#keyword-overview-widget-button div.css-1gmiqn5 > div.css-93tl4h > div.css-1181h5a > button#keyword-overview-widget-button

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
FEATURED RESOURCES div.css-15yd0a7 > div > div > span.css-1bdzmd5
Start Now div.css-1w4z2rt > div.css-15yd0a7 > div > a.css-11srpij
FEATURED RESOURCES div.css-15yd0a7 > div > div > span.css-1bdzmd5
Start Now div.css-1w4z2rt > div.css-15yd0a7 > div > a.css-11srpij
FEATURED RESOURCES div.css-15yd0a7 > div > div > span.css-1bdzmd5
Start Now div.css-1w4z2rt > div.css-15yd0a7 > div > a.css-11srpij

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
How to Create an Effective SEO Strategy in 2026 div.css-yw0cdh > article.css-10svfql > a > h3
Learn div.css-atrq9l > div.css-1bt10q5 > div.css-oq7glm > h4.css-9c5ng1

These are opportunities to improve keyboard navigation in your application.

○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
●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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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.
○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
○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