Skip to content
https://brightlocal.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
Heading Hierarchy
Action
31 headings, 4 skip(s)
FIX
31 headings, 4 skip(s)
Warning::
Multiple H1 headings (3 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: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Everything you need to master local SEO
  • H3 Build your local marketing skills with free, expert-led courses
  • H1 Shine bright, locally.
  • H3 For Local Businesses skipped
  • H3 For Agencies & Consultants
  • H1 We empower businesses to thrive and grow locally. duplicate H1
  • H3 Proven results for real businesses skipped
  • H2 How we can help you
  • H1 All-new AI Insights duplicate H1
  • H3 Real people, unrivalled support skipped
  • H3 Top-notch learning resources
  • H2 The data behind our difference
  • H2 Unlock your potential with our free tools
  • H3 Local SERP Checker
  • H3 Rank Fluctuation Monitor
  • H3 Google Review Link Generator
  • H2 Upskill with our Learning Hub
  • H3 Local Consumer Review Survey 2026: Star Ratings Keep Rising, Old Reviews Don’t Cut It
  • H3 Introducing the BrightLocal MCP Server: Talk to your Data and Take Action in your Favorite AI Tools
  • H3 Experts’ Predictions for Local Marketing in 2026
  • H2 Join thousands of happy customers using BrightLocal
  • H2 Sign up to our Newsletter
  • H4 Platform skipped
  • H4 Popular Features
  • H4 Tailored For You
  • H4 Solutions
  • H4 Free Tools
  • H4 The Learning Hub
  • H4 Company
  • H4 Support
  • H2 Start your BrightLocal Journey

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

D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
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::
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
Form Accessibility
Action
4 of 9 controls have issues
REVIEW
4 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="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">
Info::
5 control(s) properly labeled
9 controls
5 labeled
0 placeholder only
4 unlabeled
ControlTypeLabelMethod
#CybotCookiebotDialogBodyLevelButtonNecessarycheckboxNecessaryfor/id
#CybotCookiebotDialogBodyLevelButtonPreferencescheckboxPreferencesfor/id
#CybotCookiebotDialogBodyLevelButtonStatisticscheckboxStatisticsfor/id
#CybotCookiebotDialogBodyLevelButtonMarketingcheckboxMarketingfor/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformationcheckboxDo not sell or share my personal informationfor/id
#CybotCookiebotDialogBodyLevelButtonPreferencesInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonStatisticsInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonMarketingInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonNecessaryInlinecheckbox(none)none

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

<input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">

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

C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

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
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
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 "Primary Nav" MAIN CONTENTINFO footer

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

A+
Alt Text Quality
1 of 93 images have issues
PASS
1 of 93 images have issues
Warning::
1 image(s) with generic alt text
Info::
15 decorative image(s) correctly marked
Info::
77 image(s) with good alt text
93 images 77 good alt text 15 decorative 1 generic
IssueCount
generic1 image(s)
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 Shine bright, locall…20.85:13.0:1
#000000
#FFFEFD
Pass
h1 We empower businesse…20.85:13.0:1
#000000
#FFFEFD
Pass
h1 All-new AI Insights20.85:13.0:1
#000000
#FFFEFD
Pass
h2 How we can help you20.85:13.0:1
#000000
#FFFEFD
Pass
h2 The data behind our …20.85:13.0:1
#000000
#FFFEFD
Pass
h2 Unlock your potentia…20.85:13.0:1
#000000
#FFFEFD
Pass
h2 Upskill with our Lea…20.85:13.0:1
#000000
#FFFEFD
Pass
h2 Join thousands of ha…20.85:13.0:1
#000000
#FFFEFD
Pass
h2 Sign up to our Newsl…20.85:13.0:1
#000000
#FFFEFD
Pass
h2 Start your BrightLoc…20.85:13.0:1
#000000
#FFFEFD
Pass
h3 Everything you need …20.85:13.0:1
#000000
#FFFEFD
Pass
h3 Build your local mar…20.85:13.0:1
#000000
#FFFEFD
Pass
h3 For Local Businesses20.85:13.0:1
#000000
#FFFEFD
Pass
h3 For Agencies & Consu…20.85:13.0:1
#000000
#FFFEFD
Pass
h3 Proven results for r…20.85:13.0:1
#000000
#FFFEFD
Pass
h3 Real people, unrival…20.85:13.0:1
#000000
#FFFEFD
Pass
h3 Top-notch learning r…20.85:13.0:1
#000000
#FFFEFD
Pass
h3 Local SERP Checker20.85:13.0:1
#000000
#FFFEFD
Pass
h3 Rank Fluctuation Mon…20.85:13.0:1
#000000
#FFFEFD
Pass
h3 Google Review Link G…20.85:13.0:1
#000000
#FFFEFD
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 92/100 — 3 failing, 29 passed
PASS
92

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.flex > div.flex > div.flex > button.flex div.flex > div.flex > div.flex > button.flex
div.flex > div.flex > div.flex > button.flex div.flex > div.flex > div.flex > button.flex

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
Faithworks div.flex > div.mt-auto > div.mb-4 > p.font-inter
West Coast Self-Storage div.flex > div.mt-auto > div.mb-4 > p.font-inter
Voyage Media Works div.flex > div.mt-auto > div.mb-4 > p.font-inter
PestCo Holdings div.flex > div.mt-auto > div.mb-4 > p.font-inter
form#hsForm_6784da89-ef83-4940-8f31-9f964e244646 > div.hs_firstname > div.input > input#firstname-6784da89-ef83-4940-8f31-9f964e244646 form#hsForm_6784da89-ef83-4940-8f31-9f964e244646 > div.hs_firstname > div.input > input#firstname-6784da89-ef83-4940-8f31-9f964e244646
form#hsForm_6784da89-ef83-4940-8f31-9f964e244646 > div.hs_email > div.input > input#email-6784da89-ef83-4940-8f31-9f964e244646 form#hsForm_6784da89-ef83-4940-8f31-9f964e244646 > div.hs_email > div.input > input#email-6784da89-ef83-4940-8f31-9f964e244646
form#hsForm_6784da89-ef83-4940-8f31-9f964e244646 > div.hs_submit > div.actions > input.hs-button form#hsForm_6784da89-ef83-4940-8f31-9f964e244646 > div.hs_submit > div.actions > input.hs-button

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
For Local Businesses div.relative > div.flex > div.flex > h3.m-0
Proven results for real businesses div.flex > div.flex > div.flex > h3.font-inter
Real people, unrivalled support div.rounded-2xl > div.px-xl > div.flex-1 > h3.m-0
PLATFORM div.flex > div.grid > div.flex > h4.font-medium

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
●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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●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.
●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.
●`[lang]` attributes have a valid value
●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 input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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 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>`.
○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.
○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