Skip to content
https://trustindex.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
44
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 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
Warning::
2 of 2 <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 (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

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

F
Alt Text Quality
Action
21 of 56 images have issues
FIX
21 of 56 images have issues
Critical::
21 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
35 image(s) with good alt text
56 images 35 good alt text 21 missing
IssueCount
missing21 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
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-1r75f4
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://trustindex.io/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://trustindex.io/manifest.json

Manifest contains invalid JSON.

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::
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 2 <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
Heading Hierarchy
31 headings, 2 skip(s)
REVIEW
31 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 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Skyrocket Your Sales with Customer Reviews
  • H3 Create a Free Account skipped
  • H2 9 Functions that increase your sales
  • H3 Breathtaking review widgets
  • H3 137 Review Platforms
  • H3 Social Feed Widgets
  • H3 Easy review collection
  • H3 Review Image generator
  • H3 Company e-mail signatures
  • H3 Review Certificate
  • H3 Trustmarks
  • H3 Reply to reviews with ChatGPT
  • H2 Skyrocket Your Sales with Customer Reviews. No coding required.
  • H2 Show off your best reviews on your website
  • H3 The advantages of review widgets
  • H2 Why do our users love Trustindex?
  • H2 Some of our best clients
  • H2 Skyrocket Your Sales with Customer Reviews. No coding required.
  • H2 Our mission is simple just like our tool
  • H5 17M+ skipped
  • H5 3M+
  • H5 17.7%
  • H5 900.000+
  • H2 Amazing support to get more customers
  • H3 Display Reviews
  • H3 Display Feed
  • H3 Get Returning Customers
  • H3 Free Workshop
  • H3 Trustindex
  • H3 For Businesses
  • H3 For Reviewers

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
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="pre_profile[email]" id="floatingInput">; <input type="password" name="pre_profile[password]" id="exampleInputPassword1">; <input type="text" name="pre_profile[website]" id="input-website">
3 controls
0 labeled
3 placeholder only
0 unlabeled
ControlTypeLabelMethod
#floatingInputemail(E-mail address)placeholder only
#exampleInputPassword1password(Password)placeholder only
#input-websitetext(Website URL)placeholder only

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

<input type="email" name="pre_profile[email]" id="floatingInput">; <input type="password" name="pre_profile[password]" id="exampleInputPassword1">; <input type="text" name="pre_profile[website]" id="input-website">

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

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
B
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 25 passed
REVIEW
82

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
Customise div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn
Reject All div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn
Accept All div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn

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
Create a Free Account div.row > div.col-xl-5 > div#reg-form > h3.mb-4
17M+ div.col-lg-5 > div.row > div.col-sm-6 > h5

These are opportunities to improve keyboard navigation in your application.

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
nav.navbar > div.container > a.navbar-brand > img.trustindex-logo nav.navbar > div.container > a.navbar-brand > img.trustindex-logo
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.owl-stage > div.owl-item > div.item > img.img-fluid div.owl-stage > div.owl-item > div.item > img.img-fluid
div.row > div.col-lg-3 > a.navbar-brand > img.trustindex-logo div.row > div.col-lg-3 > a.navbar-brand > img.trustindex-logo

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
body > nav.navbar > div.container > a.navbar-brand body > nav.navbar > div.container > a.navbar-brand
div.container > div.row > div.col-lg-3 > a.navbar-brand div.container > div.row > div.col-lg-3 > a.navbar-brand

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.

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.

○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
●Form elements have associated labels
●`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.
●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
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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
○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.
○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.
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 Skyrocket Your Sales…18.96:13.0:1
#000000
#F5F3F0
Pass
h2 9 Functions that18.96:13.0:1
#000000
#F5F3F0
Pass
h2 your sales18.96:13.0:1
#000000
#F5F3F0
Pass
h2 Skyrocket Your Sales…18.96:13.0:1
#000000
#F5F3F0
Pass
h2 Show off your18.96:13.0:1
#000000
#F5F3F0
Pass
h2 on your website18.96:13.0:1
#000000
#F5F3F0
Pass
h2 Why do our users lov…18.96:13.0:1
#000000
#F5F3F0
Pass
h2 Some of our best cli…18.96:13.0:1
#000000
#F5F3F0
Pass
h2 Skyrocket Your Sales…18.96:13.0:1
#000000
#F5F3F0
Pass
h2 Our mission is simpl…18.96:13.0:1
#000000
#F5F3F0
Pass
h2 Amazing support to g…18.96:13.0:1
#000000
#F5F3F0
Pass
h3 Create a Free Accoun…18.96:13.0:1
#000000
#F5F3F0
Pass
h3 Breathtaking review …18.96:13.0:1
#000000
#F5F3F0
Pass
h3 Review Platforms18.96:13.0:1
#000000
#F5F3F0
Pass
h3 Social Feed Widgets18.96:13.0:1
#000000
#F5F3F0
Pass
h3 Easy review collecti…18.96:13.0:1
#000000
#F5F3F0
Pass
h3 Review Image generat…18.96:13.0:1
#000000
#F5F3F0
Pass
h3 Company e-mail signa…18.96:13.0:1
#000000
#F5F3F0
Pass
h3 Review Certificate18.96:13.0:1
#000000
#F5F3F0
Pass
h3 Trustmarks18.96:13.0:1
#000000
#F5F3F0
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.

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

Send Feedback