Skip to content
https://successstory.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
8
REVIEW
4
PASS
12
INFO
0
Checks
24
12 PASS 4 REVIEW 8 FIX
F
Heading Hierarchy
Action
45 headings, 16 skip(s)
FIX
45 headings, 16 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
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 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (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 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 SuccessStory
  • H4 Welcome Back !!!
  • H6 Forgot Password ? skipped
  • H5 Don't have an Account? Sign Up
  • H4 Sign Up
  • H6 By Signing up you accept our terms of Serivce & privacy policy skipped
  • H5 Have an Account? Sign in
  • H4 Forgot password
  • H5 Password Remember? Sign in
  • H2 Most Expensive Halloween Costumes
  • H2 It is no use saying, 'We are doing our best.' You have got to succeed in doing what is necessary.
  • H5 -Winston Churchill - skipped
  • H2 Colonel Sanders
  • H2 10 Most Expensive Nuts
  • H2 Canva
  • H2 Dave Ramsey
  • H6 Profile Dave Ramsay is a renowned US businessman, author, motivational speaker, radio host and TV personality. His mission is to make people spend without incurring debt as it is an essential factor skipped
  • H2 Chitose Abe
  • H6 Profile Japanese fashion designer Chitose Abe has created a niche for self with her urban, sporty and delicately feminine designs. She created her label Sacai in 1999 after 8 long years of working un skipped
  • H2 Zhong Shanshan
  • H6 The richest people in the world usually come in the form of tech innovators, investment tycoons, and fashion moguls. But Asia’s richest man doesn’t fit any of those titles. Zhong S... skipped
  • H2 Victoria Azarenka
  • H6 Profile Victoria Azarenka is a professional tennis player of Belarusian origin. She is ... skipped
  • H2 Nike, Inc.
  • H6 History Nike was previously known as Blue Ribbon Sports (RBS) founded in 1964 by Phil Knight and Bill Bowerman. Phil Knight was a middle distance runner hailing from Portland who trained unde... skipped
  • H2 Most Expensive Batman Collectibles
  • H6 Ever since he was introduced in the late 1930s, Bruce Wayne a.k.a. Batman has become a pop culture icon. He has graced both the big and small screen and is one of the faces of... skipped
  • H2 Jimmy Bartel
  • H2 Anahi Giovanna
  • H2 Heloise Waislitz
  • H2 Morrisons
  • H6 Profile WM Morrisons Supermarkets Plc headquartered in Bradford, West Yorkshire, UK has a chain of more than 500 supermarkets selling groceries and food. It was established in the year 1899 by Willia skipped
  • H2 Most Expensive Sleepwear for Women
  • H6 Every woman would like to have a refreshing and rejuvenating morning after comfortable sleep. Comfortable bed and warm blanket are two important things to get peaceful sleep. However, for a woman wear skipped
  • H2 Lee Chong Wei
  • H6 Profile Dato' Lee Chong Wei is a professional Chinese Badminton player of Malaysian origin. Lee is a singles player. He is the third Malaysian player to be rated ‘first’ for 199 consecutive weeks skipped
  • H2 Want to Be Successful?
  • H5 Learn Secrets from People Who Already Made It skipped
  • H5 Please enter valid Email
  • H2 Most Expensive Earbuds
  • H6 Music is the soul of the body, whenever feeling lonely and temperamental, all people do is pick the iPod, put on the favorite music and relax. Music is not only soothing to the ears, but also changes skipped
  • H2 Mitchell Goldhar
  • H6 It was back in 1994 in Barrie, Onatrio that Mitchell Goldhar built the first Walmart store in Canada. Since then, SmartCentres, his company based out of Toronto has gone on to develop 177 new Walmart skipped
  • H2 Physical Worlds Beyond Creation and Imagination: Es Devlin
  • H6 In celebration of this year’s upcoming Mother’s Day, SuccessStory will be featuring posts throughout this week related to celebrating the power of successful working mothers everywhere. Today, we skipped

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

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

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

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 66/100 — 6 failing, 10 passed
FIX
66

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
header > div.container > div.logo > button.menu-btn header > div.container > div.logo > button.menu-btn
nav.main-navbar-content > div.scroll-wrapper > div.scrollbar-inner > button.close nav.main-navbar-content > div.scroll-wrapper > div.scrollbar-inner > button.close
body > header > div.container > button.user-icon body > header > div.container > button.user-icon
header > div.container > div.search-sec > button.icon header > div.container > div.search-sec > button.icon

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
ul > li > div.post-img > a ul > li > div.post-img > a
ul > li > div.post-img > a ul > li > div.post-img > a
ul > li > div.post-img > a ul > li > div.post-img > a

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
SPENDIT div.container > div.banner-feature-img > div.banner-quote > a.category
PEOPLE div.container > ul > li > a.category
PEOPLE div.container > ul > li > a.category
PEOPLE div.container > ul > li > a.category
PEOPLE ul > li > div.post-text > a.category
COMPANY ul > li > div.post-text > a.category
SPENDIT ul > li > div.post-text > a.category
section.subscribe-sec > div.container > div.form > input#useremail_subscriptionblock section.subscribe-sec > div.container > div.form > input#useremail_subscriptionblock
SPENDIT div.container > ul > li > a.category
PEOPLE div.container > ul > li > a.category
PEOPLE div.container > ul > li > a.category

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
Learn Secrets from People Who Already Made It div.main-container > section.subscribe-sec > div.container > 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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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-hidden="true"]` is not present on the document `<body>`
●Image elements have `[alt]` attributes
●Form elements have associated labels
●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
●Touch targets have sufficient size and spacing.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` 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 use only permitted ARIA attributes
○`[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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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.
○No element has a `[tabindex]` value greater than 0
○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.
○Identical links have the same purpose.
○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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 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
8 of 8 controls have issues
REVIEW
8 of 8 controls have issues
Warning::
8 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s" id="s">; <input type="email" name="inputEmail" id="inputEmail">; <input type="password" name="inputPass" id="inputPass">; <input type="text" name="inputRegisterName" id="inputRegisterName">; <input type="text" name="inputRegisterEmail" id="inputRegisterEmail">; <input type="password" name="inputRegisterPass" id="inputRegisterPass">; <input type="text" name="inputForgotEmail" id="inputForgotEmail">; <input type="email" name="subscribe-mail" id="useremail_subscriptionblock">
8 controls
0 labeled
8 placeholder only
0 unlabeled
ControlTypeLabelMethod
#stext(Search)placeholder only
#inputEmailemail(Email id)placeholder only
#inputPasspassword(Password)placeholder only
#inputRegisterNametext(Name)placeholder only
#inputRegisterEmailtext(Email)placeholder only
#inputRegisterPasspassword(Password)placeholder only
#inputForgotEmailtext(Registered Email id)placeholder only
#useremail_subscriptionblockemail(Email Address)placeholder only

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

<input type="text" name="s" id="s">; <input type="email" name="inputEmail" id="inputEmail">; <input type="password" name="inputPass" id="inputPass">; <input type="text" name="inputRegisterName" id="inputRegisterName">; <input type="text" name="inputRegisterEmail" id="inputRegisterEmail">; <input type="password" name="inputRegisterPass" id="inputRegisterPass">; <input type="text" name="inputForgotEmail" id="inputForgotEmail">; <input type="email" name="subscribe-mail" id="useremail_subscriptionblock">

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 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
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
h2 Most Expensive Halloween Costumes
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 It is no use saying, 'We are doing our b…
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Colonel Sanders
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport
h2 10 Most Expensive Nuts
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Canva
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Dave Ramsey
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Chitose Abe
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Zhong Shanshan
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Victoria Azarenka
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Nike, Inc.
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Most Expensive Batman Collectibles
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Jimmy Bartel
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Anahi Giovanna
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Heloise Waislitz
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Morrisons
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Most Expensive Sleepwear for Women
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Lee Chong Wei
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Want to Be Successful?
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Most Expensive Earbuds
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mitchell Goldhar
1.01:1
#000000
on
#040003
needs 3.0:1 (large text)
24px · bottom of viewport

2 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 Most Expensive Hallo…1.01:13.0:1
#000000
#040003
Fail
h2 It is no use saying,…1.01:13.0:1
#000000
#040003
Fail
h2 Colonel Sanders1.01:13.0:1
#000000
#040003
Fail
h2 10 Most Expensive Nu…1.01:13.0:1
#000000
#040003
Fail
h2 Canva1.01:13.0:1
#000000
#040003
Fail
h2 Dave Ramsey1.01:13.0:1
#000000
#040003
Fail
h2 Chitose Abe1.01:13.0:1
#000000
#040003
Fail
h2 Zhong Shanshan1.01:13.0:1
#000000
#040003
Fail
h2 Victoria Azarenka1.01:13.0:1
#000000
#040003
Fail
h2 Nike, Inc.1.01:13.0:1
#000000
#040003
Fail
h2 Most Expensive Batma…1.01:13.0:1
#000000
#040003
Fail
h2 Jimmy Bartel1.01:13.0:1
#000000
#040003
Fail
h2 Anahi Giovanna1.01:13.0:1
#000000
#040003
Fail
h2 Heloise Waislitz1.01:13.0:1
#000000
#040003
Fail
h2 Morrisons1.01:13.0:1
#000000
#040003
Fail
h2 Most Expensive Sleep…1.01:13.0:1
#000000
#040003
Fail
h2 Lee Chong Wei1.01:13.0:1
#000000
#040003
Fail
h2 Want to Be Successfu…1.01:13.0:1
#000000
#040003
Fail
h2 Most Expensive Earbu…1.01:13.0:1
#000000
#040003
Fail
h2 Mitchell Goldhar1.01:13.0:1
#000000
#040003
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
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Warning::
3 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H6: 199 chars - H6: 200 chars - H6: 183 chars
Got: 3 >120-char heading(s)
A+
Alt Text Quality
All 1 images OK
PASS
All 1 images OK
Info::
1 image(s) with good alt text
1 images 1 good alt text
All images have appropriate alt text.
A
Form Input Types
3 input(s) using type=text where a specific type would help
PASS
3 input(s) using type=text where a specific type would help
Info::
Input "s" should use type="search" (currently type="text")
Field name "s" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "inputRegisterEmail" should use type="email" (currently type="text")
Field name "inputRegisterEmail" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
Info::
Input "inputForgotEmail" should use type="email" (currently type="text")
Field name "inputForgotEmail" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
A
Form Input Quality
1 input-semantic issue(s) across 8 form control(s)
PASS
1 input-semantic issue(s) across 8 form control(s)
Info::
2 password field(s) missing or with invalid `autocomplete`
Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="inputPass">, <input type="password" name="inputRegisterPass">.
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 75 visible text node(s) render at >= 12 CSS pixels
PASS
All 75 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback