Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

11 PASS 5 REVIEW 8 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

Form Accessibility

Action

15 of 15 controls have issues

FIX

15 of 15 controls have issues

2 control(s) without accessible label

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

Got: <input type="text" id="settingCurrentName">; <input type="text" id="successLinkInput">

13 control(s) rely on placeholder only

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

Got: <input type="text" id="searchPaid">; <input type="text" id="searchFree">; <input type="text" id="searchOrders">; <input type="text" id="searchHistory">; <input type="text" id="settingNewName">; <input type="password" id="settingCurrentPassword">; <input type="password" id="settingNewPassword">; <input type="password" id="settingConfirmPassword">; <input type="email" id="loginEmail">; <input type="password" id="loginPassword"> (+3 more)

15 controls

0 labeled

13 placeholder only

2 unlabeled

Control	Type	Label	Method
#searchPaid	text	(Search premium products...)	placeholder only
#searchFree	text	(Search free products...)	placeholder only
#searchOrders	text	(Search my library...)	placeholder only
#searchHistory	text	(Search transactions...)	placeholder only
#settingNewName	text	(New Username)	placeholder only
#settingCurrentPassword	password	(Current Password)	placeholder only
#settingNewPassword	password	(New Password)	placeholder only
#settingConfirmPassword	password	(Confirm New Password)	placeholder only
#loginEmail	email	(Enter Your Email)	placeholder only
#loginPassword	password	(••••••••)	placeholder only
#signupName	text	(Enter Your Name)	placeholder only
#signupEmail	email	(Enter Your Email)	placeholder only
#signupPassword	password	(••••••••)	placeholder only
#settingCurrentName	text	(none)	none
#successLinkInput	text	(none)	none

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

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

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

<input type="text" id="searchPaid">; <input type="text" id="searchFree">; <input type="text" id="searchOrders">; <input type="text" id="searchHistory">; <input type="text" id="settingNewName">; <input type="password" id="settingCurrentPassword">; <input type="password" id="settingNewPassword">; <input type="password" id="settingConfirmPassword">; <input type="email" id="loginEmail">; <input type="password" id="loginPassword"> (+3 more)

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

Mobile Keyboard & Autofill

Action

9/9 eligible field(s) missing autocomplete or inputmode

FIX

9/9 eligible field(s) missing autocomplete or inputmode

7 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: current-password, email.

Got: <input type="password" id="settingCurrentPassword">, <input type="password" id="settingNewPassword">, <input type="password" id="settingConfirmPassword">, <input type="email" id="loginEmail">, <input type="password" id="loginPassword">

2 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" id="loginEmail">, <input type="email" id="signupEmail">

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Alt Text Quality

Action

24 of 24 images have issues

REVIEW

24 of 24 images have issues

24 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

24 images 24 missing

Issue	Count
missing	24 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

Form Input Types

4 input(s) using type=text where a specific type would help

REVIEW

4 input(s) using type=text where a specific type would help

Input "searchPaid" should use type="search" (currently type="text")

Field name "searchPaid" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Input "searchFree" should use type="search" (currently type="text")

Field name "searchFree" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Input "searchOrders" should use type="search" (currently type="text")

Field name "searchOrders" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Input "searchHistory" should use type="search" (currently type="text")

Field name "searchHistory" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Mobile-Readable Font Sizes

95% of visible text renders at >= 12 CSS px (2 below threshold)

REVIEW

95% of visible text renders at >= 12 CSS px (2 below threshold)

2 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <div> 11.0px ("Support & Legal"); <div> 11.0px ("System").

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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

h1 WELCOME TO DIGITAL PRODUCTS STORE

1.05:1

#000000

#030A0C

needs 3.0:1 (large text)

32px · bottom of viewport

h2 User Name

1.11:1

#000000

#031317

needs 3.0:1 (large text)

24px · mid-page

h2 Latest Arrivals

1.05:1

#000000

#030A0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Premium Products

1.05:1

#000000

#030A0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Free Downloads

1.05:1

#000000

#030A0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 My Library

1.05:1

#000000

#030A0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Purchase History

1.05:1

#000000

#030A0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Support Channels

1.05:1

#000000

#030A0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Terms & Conditions

1.05:1

#000000

#030A0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Privacy Policy

1.05:1

#000000

#030A0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Refund Policy

1.05:1

#000000

#030A0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 App Settings

1.05:1

#000000

#030A0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Login

1.05:1

#000000

#030A0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Access Granted!

1.05:1

#000000

#030A0C

needs 3.0:1 (large text)

24px · bottom of viewport

h3 https://t.me/+wr8pBfY7IkQyMTM1

1.05:1

#000000

#030A0C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Account Settings

1.05:1

#000000

#030A0C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 System Data

1.05:1

#000000

#030A0C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Description

1.05:1

#000000

#030A0C

needs 3.0:1 (large text)

19px · bottom of viewport

title Digital Products Store

1.06:1

#000000

#040C0F

needs 4.5:1 (normal text)

16px · top of page (header area)

div LOADING STORE...

1.06:1

#000000

#040C0F

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 WELCOME TO DIGITAL P…	1.05:1	3.0:1	#000000	#030A0C	Fail
h2 User Name	1.11:1	3.0:1	#000000	#031317	Fail
h2 Latest Arrivals	1.05:1	3.0:1	#000000	#030A0C	Fail
h2 Premium Products	1.05:1	3.0:1	#000000	#030A0C	Fail
h2 Free Downloads	1.05:1	3.0:1	#000000	#030A0C	Fail
h2 My Library	1.05:1	3.0:1	#000000	#030A0C	Fail
h2 Purchase History	1.05:1	3.0:1	#000000	#030A0C	Fail
h2 Support Channels	1.05:1	3.0:1	#000000	#030A0C	Fail
h2 Terms & Conditions	1.05:1	3.0:1	#000000	#030A0C	Fail
h2 Privacy Policy	1.05:1	3.0:1	#000000	#030A0C	Fail
h2 Refund Policy	1.05:1	3.0:1	#000000	#030A0C	Fail
h2 App Settings	1.05:1	3.0:1	#000000	#030A0C	Fail
h2 Login	1.05:1	3.0:1	#000000	#030A0C	Fail
h2 Access Granted!	1.05:1	3.0:1	#000000	#030A0C	Fail
h3 https://t.me/+wr8pBf…	1.05:1	3.0:1	#000000	#030A0C	Fail
h3 Account Settings	1.05:1	3.0:1	#000000	#030A0C	Fail
h3 System Data	1.05:1	3.0:1	#000000	#030A0C	Fail
h3 Description	1.05:1	3.0:1	#000000	#030A0C	Fail
title Digital Products Sto…	1.06:1	4.5:1	#000000	#040C0F	Fail
div LOADING STORE...	1.06:1	4.5:1	#000000	#040C0F	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 Hierarchy

19 headings

PASS

19 headings

Single H1 present

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H2 User Name
H1 WELCOME TO DIGITAL PRODUCTS STORE
H2 Latest Arrivals
H2 Premium Products
H2 Free Downloads
H2 My Library
H2 Purchase History
H2 Support Channels
H3 https://t.me/+wr8pBfY7IkQyMTM1
H2 Terms & Conditions
H2 Privacy Policy
H2 Refund Policy
H2 App Settings
H3 Account Settings
H3 System Data
H2 Login
H2 (empty)
H3 Description
H2 Access Granted!

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 1 all-caps heading(s)

A+

Link & Button Quality

3 links, 49 buttons — all OK

PASS

3 links, 49 buttons — all OK

3 link(s) with descriptive text

3 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

52 links and buttons have descriptive text

Form Input Quality

1 input-semantic issue(s) across 15 form control(s)

PASS

1 input-semantic issue(s) across 15 form control(s)

5 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" id="settingCurrentPassword">, <input type="password" id="settingNewPassword">, <input type="password" id="settingConfirmPassword"> (+2 more).

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

All 1 iframe(s) have descriptive titles

PASS

All 1 iframe(s) have descriptive titles

All 1 iframe(s) have title attributes

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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.

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 18 passed

PASS

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

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
body > div.header > div.brand-section > img#headerLogo `body > div.header > div.brand-section > img#headerLogo`
body > div.container > div#homeTab > img#storeBanner `body > div.container > div#homeTab > img#storeBanner`
div#homeTab > div#homeLatestGrid > div.product-card > img.product-image `div#homeTab > div#homeLatestGrid > div.product-card > img.product-image`
div#homeTab > div#homeLatestGrid > div.product-card > img.product-image `div#homeTab > div#homeLatestGrid > div.product-card > img.product-image`
div#homeTab > div#homeLatestGrid > div.product-card > img.product-image `div#homeTab > div#homeLatestGrid > div.product-card > img.product-image`
div#homeTab > div#homeLatestGrid > div.product-card > img.product-image `div#homeTab > div#homeLatestGrid > div.product-card > img.product-image`
div#homeTab > div#homeLatestGrid > div.product-card > img.product-image `div#homeTab > div#homeLatestGrid > div.product-card > img.product-image`
div#homeTab > div#homeLatestGrid > div.product-card > img.product-image `div#homeTab > div#homeLatestGrid > div.product-card > img.product-image`
div#homeTab > div#homeLatestGrid > div.product-card > img.product-image `div#homeTab > div#homeLatestGrid > div.product-card > img.product-image`
div#homeTab > div#homeLatestGrid > div.product-card > img.product-image `div#homeTab > div#homeLatestGrid > div.product-card > img.product-image`

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

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-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●`[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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

○`[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

○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

○`<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

○Form elements have associated labels

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○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.

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