Skip to content
https://office-project-beat-box-front-end.vercel.app

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
9
REVIEW
5
PASS
10
INFO
0
Checks
24
10 PASS 5 REVIEW 9 FIX
F
Heading Hierarchy
Action
39 headings, 5 skip(s)
FIX
39 headings, 5 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H6 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 BeatBox Headphone Pro
  • H4 Wireless Headphones skipped
  • H2 Shop by Category
  • H2 Our Collections
  • H3 BeatBox Signature Series
  • H3 BeatBox Gaming Collection
  • H3 BeatBox Pro Collection
  • H3 Best Sellers
  • H5 BeatBox AirBuds 100 skipped
  • H5 boAt Airdopes 131
  • H5 BeatBox BoomCan 2.0
  • H5 JBL Tune 510BT
  • H5 boAt BassHeads 225
  • H5 BeatBox BassHeads 100
  • H5 JBL Quantum 100
  • H5 BeatBox Headphone Pro
  • H2 Daily Deals
  • H1 BeatBox Headphone Pro
  • H4 Wireless Headphones skipped
  • H3 14
  • H3 32
  • H3 43
  • H1 ₹6999 duplicate H1
  • H6 BeatBox Party Blast skipped
  • H6 JBL Quantum 100
  • H6 JBL Tune 510BT
  • H6 boAt Rockerz 550
  • H5 Top Rated Brand
  • H5 Flagship Innovation
  • H5 24/7 Premium Support
  • H3 #BeatBoxVibes
  • H6 1 Year Warranty skipped
  • H6 7 Days Replacement
  • H6 Free Express Shipping
  • H6 Secure Checkout
  • H5 BEATBOX
  • H6 Shop
  • H6 Support
  • H6 Company

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

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
Mobile Keyboard & Autofill
Action
2/2 eligible field(s) missing autocomplete or inputmode
FIX
2/2 eligible field(s) missing autocomplete or inputmode
Warning::
1 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: email.
Got: <input type="email">
Warning::
1 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">
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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 Missing
✓ 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::
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.
B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">; <input type="email">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtext(Search drops, headsets...)placeholder only
inputemail(Enter your email address)placeholder only

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

<input type="text">; <input type="email">

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
Tap Target Adequacy
Action
6 tap target(s) too small or too close together
REVIEW
6 tap target(s) too small or too close together
Warning::
6 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
C
Mobile-Readable Font Sizes
Action
84% of visible text renders at >= 12 CSS px (36 below threshold)
REVIEW
84% of visible text renders at >= 12 CSS px (36 below threshold)
Warning::
36 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: <p> 10.9px ("Explore"); <span> 9.9px ("Popular"); <span> 8.8px ("BEATBOX"); <span> 11.2px ("40 Hours Battery"); <span> 11.7px ("5.0").
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
h1 BeatBox Headphone Pro
1.01:1
#000000
on
#000207
needs 3.0:1 (large text)
32px · bottom of viewport
h1 ₹6999
1.01:1
#000000
on
#000207
needs 3.0:1 (large text)
32px · bottom of viewport
h2 BeatBox Headphone Pro
1.02:1
#000000
on
#000308
needs 3.0:1 (large text)
24px · mid-page
h2 Shop by
1.01:1
#000000
on
#000207
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our
1.01:1
#000000
on
#000207
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Daily
1.01:1
#000000
on
#000207
needs 3.0:1 (large text)
24px · bottom of viewport
h3 BeatBox Signature Series
1.01:1
#000000
on
#000207
needs 3.0:1 (large text)
19px · bottom of viewport
h3 BeatBox Gaming Collection
1.01:1
#000000
on
#000207
needs 3.0:1 (large text)
19px · bottom of viewport
h3 BeatBox Pro Collection
1.01:1
#000000
on
#000207
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Best
1.01:1
#000000
on
#000207
needs 3.0:1 (large text)
19px · bottom of viewport
h3 #BeatBox
1.01:1
#000000
on
#000207
needs 3.0:1 (large text)
19px · bottom of viewport
title BeatBox - Premium Audio
3.98:1
#000000
on
#6255E8
needs 4.5:1 (normal text)
16px · top of page (header area)
span ⚡ GRAB THE LOOT: Free Shipping & 1-Yea…
1.02:1
#000000
on
#010308
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span BEAT
1.02:1
#000000
on
#010308
needs 4.5:1 (normal text)
16px · top of page (header area)
span BOX
1.03:1
#000000
on
#03050A
needs 4.5:1 (normal text)
16px · top of page (header area)
span BEAT
1.02:1
#000000
on
#010308
needs 4.5:1 (normal text)
16px · above the fold
span BOX
1.02:1
#000000
on
#010308
needs 4.5:1 (normal text)
16px · above the fold
button Categories
1.01:1
#000000
on
#000207
needs 4.5:1 (normal text)
16px · above the fold
a Daily Deals
1.01:1
#000000
on
#000207
needs 4.5:1 (normal text)
16px · above the fold
a Best Sellers
1.01:1
#000000
on
#000207
needs 4.5:1 (normal text)
16px · above the fold

1 contrast failures on background images/gradients

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

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 BeatBox Headphone Pr…1.01:13.0:1
#000000
#000207
Fail
h1 ₹69991.01:13.0:1
#000000
#000207
Fail
h2 BeatBox Headphone Pr…1.02:13.0:1
#000000
#000308
Fail
h2 Shop by1.01:13.0:1
#000000
#000207
Fail
h2 Our1.01:13.0:1
#000000
#000207
Fail
h2 Daily1.01:13.0:1
#000000
#000207
Fail
h3 BeatBox Signature Se…1.01:13.0:1
#000000
#000207
Fail
h3 BeatBox Gaming Colle…1.01:13.0:1
#000000
#000207
Fail
h3 BeatBox Pro Collecti…1.01:13.0:1
#000000
#000207
Fail
h3 Best1.01:13.0:1
#000000
#000207
Fail
h3 #BeatBox1.01:13.0:1
#000000
#000207
Fail
title BeatBox - Premium Au…3.98:14.5:1
#000000
#6255E8
Fail
span ⚡ GRAB THE LOOT: F…1.02:14.5:1
#000000
#010308
Fail
span BEAT1.02:14.5:1
#000000
#010308
Fail
span BOX1.03:14.5:1
#000000
#03050A
Fail
span BEAT1.02:14.5:1
#000000
#010308
Fail
span BOX1.02:14.5:1
#000000
#010308
Fail
button Categories1.01:14.5:1
#000000
#000207
Fail
a Daily Deals1.01:14.5:1
#000000
#000207
Fail
a Best Sellers1.01:14.5:1
#000000
#000207
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.

B
Lighthouse Accessibility Audits
Score 80/100 — 5 failing, 20 passed
REVIEW
80

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.container-fluid > div.position-relative > div.d-flex > button.rounded-circle div.container-fluid > div.position-relative > div.d-flex > button.rounded-circle
div.position-relative > div.d-flex > div.d-flex > button.btn div.position-relative > div.d-flex > div.d-flex > button.btn
div.position-relative > div.d-flex > div.d-flex > button.btn div.position-relative > div.d-flex > div.d-flex > button.btn
div.position-relative > div.d-flex > div.d-flex > button.btn div.position-relative > div.d-flex > div.d-flex > button.btn
div.position-relative > div.d-flex > div.d-flex > button.btn div.position-relative > div.d-flex > div.d-flex > button.btn
div.position-relative > div.d-flex > div.d-flex > button.btn div.position-relative > div.d-flex > div.d-flex > button.btn
div.position-relative > div.d-flex > div.d-flex > button.btn div.position-relative > div.d-flex > div.d-flex > button.btn
div.container-fluid > div.position-relative > div.d-flex > button.rounded-circle div.container-fluid > div.position-relative > div.d-flex > button.rounded-circle
div.row > div.col-12 > form.position-relative > button.btn div.row > div.col-12 > form.position-relative > button.btn

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
div.container-fluid > div.d-flex > div.d-flex > a.btn div.container-fluid > div.d-flex > div.d-flex > a.btn
div.row > div.col-12 > div.d-flex > a.btn div.row > div.col-12 > div.d-flex > a.btn
div.row > div.col-12 > div.d-flex > a.btn div.row > div.col-12 > div.d-flex > a.btn
div.row > div.col-12 > div.d-flex > a.btn div.row > div.col-12 > div.d-flex > a.btn
div.row > div.col-12 > div.d-flex > a.btn div.row > div.col-12 > div.d-flex > a.btn

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
EXPLORE div > div > div > p
View All section#shop-by-categories > div > div > 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
WIRELESS HEADPHONES div.row > div#gravity-hero-text > div.text-start > h4.gradient-text
BeatBox AirBuds 100 a.text-decoration-none > div.product-card > div.product-card-body > h5.product-card-name
Wireless Headphones div.glass-card > div.row > div.col-lg-7 > h4.mb-4
BeatBox Headphone Pro div.row > div.col-12 > div.glass-card > h6.fw-bold
1 Year Warranty div.col-12 > div.d-flex > div > h6.fw-bold

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.position-relative > div.d-flex > div.d-flex > button.btn div.position-relative > div.d-flex > div.d-flex > button.btn
div.position-relative > div.d-flex > div.d-flex > button.btn div.position-relative > div.d-flex > div.d-flex > button.btn
div.position-relative > div.d-flex > div.d-flex > button.btn div.position-relative > div.d-flex > div.d-flex > button.btn
div.position-relative > div.d-flex > div.d-flex > button.btn div.position-relative > div.d-flex > div.d-flex > button.btn
div.position-relative > div.d-flex > div.d-flex > button.btn div.position-relative > div.d-flex > div.d-flex > button.btn
div.position-relative > div.d-flex > div.d-flex > button.btn div.position-relative > div.d-flex > div.d-flex > button.btn

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
●Image elements have `[alt]` attributes
●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
●`[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
●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
●Document has a main landmark.
●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.
○`[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
○`<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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○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
Landmark Structure
5 landmarks
PASS
5 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 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
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Info::
3 heading(s) are too short (≤2 characters) to convey meaning
Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H3: "14" - H3: "32" - H3: "43"
Got: 3 ≤2-char heading(s)
Info::
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+
Alt Text Quality
All 30 images OK
PASS
All 30 images OK
Info::
30 image(s) with good alt text
30 images 30 good alt text
All images have appropriate alt text.
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "Search drops, headsets..." should use type="search" (currently type="text")
Field name "Search drops, headsets..." suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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
5 explicit tabindex attribute(s) checked, no anti-patterns
PASS
5 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://api.razorpay.com/v1/checkout/public?traffic_env=baseline&build=247362bd…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
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