Skip to content
https://wordstream.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
D
Heading Hierarchy
Action
34 headings, 4 skip(s)
FIX
34 headings, 4 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 → H5 (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::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H4 Guides
  • H4 Recommended Reads
  • H4 PPC 101
  • H4 Recent Articles
  • H1 Stop wasting money in Google Ads
  • H3 Get an instant audit of your account with the Free Google Ads Performance Grader. skipped
  • H2 Get a true readon your performance
  • H5 The Google Ads Performance Grader skipped
  • H2 Get ready to grow your business
  • H3 142M
  • H3 279M
  • H3 $15.9B
  • H2 Seize your potential
  • H2 The definitive guide to Google Ads performance
  • H5 NEW INDUSTRY BENCHMARKS FOR 2025 skipped
  • H2 Keyword research made fast and easy
  • H5 THE FREE KEYWORD TOOL skipped
  • H2 The WordStream Blog
  • H3 31 Call to Action Examples + How to Write Your Own
  • H3 More articles
  • H3 How to Use Google Ads Brand Guidelines for Cleaner Automated Assets
  • H3 15 Tiny Copy Tweaks That Immediately Improve Conversions
  • H3 How Much Do TikTok Ads Cost in 2026?
  • H2 Learn more about marketing
  • H3 2025 Google Ads Benchmarks: Competitive Data & Insights for Your Industry
  • H3 6 Easy Ways to Save Money in Google Ads NOW!
  • H3 The Last Guide to Google Ads Account Structure You'll Ever Need
  • H4 Free Tools
  • H4 Explore Topics
  • H4 Learn
  • H4 Marketing Tips
  • H4 Company
  • H4 Solutions
  • H4 Contact Us

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

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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <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.
C
Landmark Structure
Action
4 landmarks
REVIEW
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 (missing!) 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

B
Form Accessibility
2 of 3 controls have issues
REVIEW
2 of 3 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="s">; <input type="search" name="s">
Info::
1 control(s) properly labeled
3 controls
1 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#Emailemail*for/id
ssearch(Search)placeholder only
ssearch(Search)placeholder only

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

<input type="search" name="s">; <input type="search" name="s">

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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | WordStream ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ 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 2 pass AA only
h2 Get ready to grow your business
2.22:1
#000000
on
#00487C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Seize your potential
2.22:1
#000000
on
#00487C
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Get an instant audit of your account wit…
2.22:1
#000000
on
#00487C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 How to Use Google Ads Brand Guidelines f…
2.22:1
#000000
on
#00487C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 15 Tiny Copy Tweaks That Immediately Imp…
2.22:1
#000000
on
#00487C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 How Much Do TikTok Ads Cost in 2026?
2.22:1
#000000
on
#00487C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 2025 Google Ads Benchmarks: Competitive …
2.22:1
#000000
on
#00487C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 6 Easy Ways to Save Money in Google Ads …
2.22:1
#000000
on
#00487C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 The Last Guide to Google Ads Account Str…
2.22:1
#000000
on
#00487C
needs 3.0:1 (large text)
19px · bottom of viewport
a Free Tools
2.93:1
#000000
on
#4C586F
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Google Ads
1.39:1
#000000
on
#002162
needs 4.5:1 (normal text)
16px · top of page (header area)
a Performance Grader
1.42:1
#000000
on
#002363
needs 4.5:1 (normal text)
16px · above the fold
p Find out if you're making costly mistake…
1.45:1
#000000
on
#002565
needs 4.5:1 (normal text)
16px · above the fold
p Get your grade
1.48:1
#000000
on
#002766
needs 4.5:1 (normal text)
16px · above the fold
a Facebook Ads
1.51:1
#000000
on
#002967
needs 4.5:1 (normal text)
16px · above the fold
a Performance Grader
1.53:1
#000000
on
#002A68
needs 4.5:1 (normal text)
16px · above the fold
p Get ready to improve your reach, results…
1.57:1
#000000
on
#002C6A
needs 4.5:1 (normal text)
16px · above the fold
p Get your grade
1.60:1
#000000
on
#002E6B
needs 4.5:1 (normal text)
16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Get ready to grow yo…2.22:13.0:1
#000000
#00487C
Fail
h2 Seize your potential2.22:13.0:1
#000000
#00487C
Fail
h3 Get an instant audit…2.22:13.0:1
#000000
#00487C
Fail
h3 How to Use Google Ad…2.22:13.0:1
#000000
#00487C
Fail
h3 15 Tiny Copy Tweaks …2.22:13.0:1
#000000
#00487C
Fail
h3 How Much Do TikTok A…2.22:13.0:1
#000000
#00487C
Fail
h3 2025 Google Ads Benc…2.22:13.0:1
#000000
#00487C
Fail
h3 6 Easy Ways to Save …2.22:13.0:1
#000000
#00487C
Fail
h3 The Last Guide to Go…2.22:13.0:1
#000000
#00487C
Fail
title WordStream | Online …5.24:14.5:1
#000000
#7F7F7F
Pass
a Blog5.24:14.5:1
#000000
#7F7F7F
Pass
a Free Tools2.93:14.5:1
#000000
#4C586F
Fail
a Google Ads1.39:14.5:1
#000000
#002162
Fail
a Performance Grader1.42:14.5:1
#000000
#002363
Fail
p Find out if you're m…1.45:14.5:1
#000000
#002565
Fail
p Get your grade1.48:14.5:1
#000000
#002766
Fail
a Facebook Ads1.51:14.5:1
#000000
#002967
Fail
a Performance Grader1.53:14.5:1
#000000
#002A68
Fail
p Get ready to improve…1.57:14.5:1
#000000
#002C6A
Fail
p Get your grade1.60:14.5:1
#000000
#002E6B
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+
Alt Text Quality
All 27 images OK
PASS
All 27 images OK
Info::
4 decorative image(s) correctly marked
Info::
23 image(s) with good alt text
27 images 23 good alt text 4 decorative
All images have appropriate alt text.
A
Lighthouse Accessibility Audits
Score 90/100 — 4 failing, 24 passed
PASS
90

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Get your grade form#mktoForm_18806 > div.mktoButtonRow > span.mktoButtonWrap > button.mktoButton
Grade My Account div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button
Get My Guide div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a#ws-tool
Find My Keywords div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a#ws-tool

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
Get an instant audit of your account with the Free Google Ads Performance Grade… div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > h3
THE GOOGLE ADS PERFORMANCE GRADER div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > h5
NEW INDUSTRY BENCHMARKS FOR 2025 div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > h5
THE FREE KEYWORD TOOL div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > 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

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy Policy div.ot-sdk-eight > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●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
●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
●Identical links have the same purpose.
○`[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
○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
○Image elements do not have `[alt]` attributes that are redundant text.
○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