Skip to content
https://www.oxo.co.in

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
10
REVIEW
3
PASS
11
INFO
0
Checks
24
11 PASS 3 REVIEW 10 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark 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 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

F
Form Accessibility
Action
26 of 27 controls have issues
FIX
26 of 27 controls have issues
Critical::
24 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="quantity">; <input type="text" name="quantity">; <input type="text" name="quantity">; <input type="text" name="quantity">; <input type="text" name="quantity">; <input type="text" name="quantity">; <input type="text" name="quantity">; <input type="text" name="quantity">; <input type="text" name="quantity">; <input type="text" name="quantity"> (+14 more)
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="search">; <input type="text" name="email">
Info::
1 control(s) properly labeled
27 controls
1 labeled
2 placeholder only
24 unlabeled
ControlTypeLabelMethod
agreecheckboxnone
emailtext(Your email)placeholder only
searchtext(Search for products...)placeholder only
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none
quantitytext(none)none

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

<input type="text" name="quantity">; <input type="text" name="quantity">; <input type="text" name="quantity">; <input type="text" name="quantity">; <input type="text" name="quantity">; <input type="text" name="quantity">; <input type="text" name="quantity">; <input type="text" name="quantity">; <input type="text" name="quantity">; <input type="text" name="quantity"> (+14 more)

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" name="search">; <input type="text" name="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

D
Mobile Keyboard & Autofill
Action
1/1 eligible field(s) missing autocomplete or inputmode
FIX
1/1 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="text" name="email">
D
404 Error Page
Action
HTTP 404, custom page
FIX
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Heading Hierarchy
Action
7 headings, 1 skip(s)
REVIEW
7 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Our Brands
  • H3 About Us
  • H5 OXO Group of Companies skipped
  • H3 What they say about us
  • H3 Customer Service
  • H3 My Account
  • H3 Newsletter

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

16 pass 4 fail WCAG AA 1 pass AA only
title Oxo
1.78:1
#000000
on
#313846
needs 4.5:1 (normal text)
16px · top of page (header area)
span Menu
1.78:1
#000000
on
#313846
needs 4.5:1 (normal text)
16px · top of page (header area)
span Outerwear Capri
1.78:1
#000000
on
#313846
needs 4.5:1 (normal text)
16px · above the fold
span Outerwear Leggings
1.78:1
#000000
on
#313846
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 Our Brands19.26:13.0:1
#000000
#F5F5F5
Pass
h3 About Us19.26:13.0:1
#000000
#F5F5F5
Pass
h3 What they say about …19.26:13.0:1
#000000
#F5F5F5
Pass
h3 Customer Service19.26:13.0:1
#000000
#F5F5F5
Pass
h3 My Account19.26:13.0:1
#000000
#F5F5F5
Pass
h3 Newsletter19.26:13.0:1
#000000
#F5F5F5
Pass
title Oxo1.78:14.5:1
#000000
#313846
Fail
span Menu1.78:14.5:1
#000000
#313846
Fail
span Dhotis and Shirts8.75:14.5:1
#000000
#A7A7AA
Pass
span New18.52:14.5:1
#000000
#F1F0F5
Pass
span Menswear - Shirt15.26:14.5:1
#000000
#DCDBE1
Pass
span Menswear Dhotis9.09:14.5:1
#000000
#ABAAAE
Pass
span Womens Wear17.88:14.5:1
#000000
#EDECF2
Pass
span New5.32:14.5:1
#000000
#7C808B
Pass
span Outerwear Capri1.78:14.5:1
#000000
#313846
Fail
span Outerwear Leggings1.78:14.5:1
#000000
#313846
Fail
span Outerwear Pyjama21.00:14.5:1
#000000
#FFFFFF
Pass
span Womens Innerwear21.00:14.5:1
#000000
#FFFFFF
Pass
span Mens Wear21.00:14.5:1
#000000
#FFFFFF
Pass
span New21.00:14.5:1
#000000
#FFFFFF
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.

C
Lighthouse Accessibility Audits
Action
Score 75/100 — 5 failing, 12 passed
REVIEW
75

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.mobile-bar-group > div.mobile-search-wrapper > div#search > button.dropdown-toggle div.mobile-bar-group > div.mobile-search-wrapper > div#search > button.dropdown-toggle

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.mobile-bar-group > div.mobile-cart-wrapper > div#cart > a.dropdown-toggle div.mobile-bar-group > div.mobile-cart-wrapper > div#cart > a.dropdown-toggle
div#banners-6a7df7394919e > div.module-body > div.module-item > a div#banners-6a7df7394919e > div.module-body > div.module-item > a
div#banners-6a7df7394d4cc > div.module-body > div.module-item > a div#banners-6a7df7394d4cc > div.module-body > div.module-item > a
div#banners-6a7df7394f9ec > div.module-body > div.module-item > a div#banners-6a7df7394f9ec > div.module-body > div.module-item > a
div.caption > div.extra-group > div > a.btn div.caption > div.extra-group > div > a.btn
div.caption > div.extra-group > div > a.btn div.caption > div.extra-group > div > a.btn
div.caption > div.extra-group > div > a.btn div.caption > div.extra-group > div > a.btn
div.caption > div.extra-group > div > a.btn div.caption > div.extra-group > div > a.btn
div.caption > div.extra-group > div > a.btn div.caption > div.extra-group > div > a.btn
div.caption > div.extra-group > div > a.btn div.caption > div.extra-group > div > a.btn
div.caption > div.extra-group > div > a.btn div.caption > div.extra-group > div > a.btn
div.caption > div.extra-group > div > a.btn div.caption > div.extra-group > div > a.btn
div.icons-menu > ul > li.menu-item > a div.icons-menu > ul > li.menu-item > a
div.icons-menu > ul > li.menu-item > a div.icons-menu > ul > li.menu-item > a
div.icons-menu > ul > li.menu-item > a div.icons-menu > ul > li.menu-item > a
div.icons-menu > ul > li.menu-item > a div.icons-menu > ul > li.menu-item > a
div.icons-menu > ul > li.menu-item > a div.icons-menu > ul > li.menu-item > a
div.icons-menu > ul > li.menu-item > a div.icons-menu > ul > li.menu-item > a
div.icons-menu > ul > li.menu-item > a div.icons-menu > ul > li.menu-item > a
div.icons-menu > ul > li.menu-item > a div.icons-menu > ul > li.menu-item > a
div.icons-menu > ul > li.menu-item > a div.icons-menu > ul > li.menu-item > a
div.icons-menu > ul > li.menu-item > a div.icons-menu > ul > li.menu-item > 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
Latest div.tab-container > ul.nav > li.tab-2 > a
New div.image > div.product-labels > span.product-label > b
Oxo div.stats > span.stat-1 > span > a
New div.image > div.product-labels > span.product-label > b
Oxo div.stats > span.stat-1 > span > a
New div.image > div.product-labels > span.product-label > b
Oxo div.stats > span.stat-1 > span > a
New div.image > div.product-labels > span.product-label > b
Oxo div.stats > span.stat-1 > span > a
New div.image > div.product-labels > span.product-label > b
Oxo div.stats > span.stat-1 > span > a
New div.image > div.product-labels > span.product-label > b
Oxo div.stats > span.stat-1 > span > a
New div.image > div.product-labels > span.product-label > b
Oxo div.stats > span.stat-1 > span > a
New div.image > div.product-labels > span.product-label > b
Oxo div.stats > span.stat-1 > span > a
Privacy Policy div.checkbox > label > a.agree > b
Copyright © 2021, OXO Group of Companies, All Rights Reserved ul.module-body > li.menu-item > a > span.links-text
Login ul > li.menu-item > a > span.links-text
Register ul > li.menu-item > a > span.links-text
Wishlist ul > li.menu-item > a > span.links-text
Contact ul > li.menu-item > a > span.links-text
Call us ul > li.menu-item > a > span.links-text

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
OXO Group of Companies div.block-body > div.block-wrapper > div.block-content > h5

These are opportunities to improve keyboard navigation in your application.

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.mobile html.mobile

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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●Touch targets have sufficient size and spacing.
●Identical links have the same purpose.
○`[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 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
○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.
○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.
○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.
A+
Heading Text Quality
All 7 heading(s) have substantive, well-formed text
PASS
All 7 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 62 images OK
PASS
All 62 images OK
Info::
13 decorative image(s) correctly marked
Info::
49 image(s) with good alt text
62 images 49 good alt text 13 decorative
All images have appropriate alt text.
A
Form Input Types
2 input(s) using type=text where a specific type would help
PASS
2 input(s) using type=text where a specific type would help
Info::
Input "search" should use type="search" (currently type="text")
Field name "search" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "email" should use type="email" (currently type="text")
Field name "email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
A+
Form Input Quality
27 form control(s) checked, no input-semantic issues
PASS
27 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
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <input>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
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://www.youtube.com/embed/AoC0vEzrOy8?hd=1&wmode=opaque&controls=1&showinfo…")
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+
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 45 visible text node(s) render at >= 12 CSS pixels
PASS
All 45 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