Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 6 REVIEW 6 FIX

Mobile-Readable Font Sizes

Action

54% of visible text renders at >= 12 CSS px (5 below threshold)

FIX

54% of visible text renders at >= 12 CSS px (5 below threshold)

5 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: <span> 11.0px ("Worldwide Shipping"); <span> 11.0px ("Get Flat 10% OFF on all orders.✨ Use Cod..."); <span> 11.0px ("Easy Return And Exchange"); <a> 11.0px ("Submit A Request Within 24 Hours"); <span> 11.0px ("Free Shipping on all Prepaid Orders").

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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

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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

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 ModePartial Dark Mode

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Landmark Structure

4 landmarks

REVIEW

4 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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.

Page Structure — as a screen reader sees it

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

Heading Hierarchy

30 headings

REVIEW

30 headings

No H1 heading found

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

H2 Cookie consent
H2 Recommended products
H3 Aabha Golden Clutch
H3 Aabroo Black Flap Bag
H3 Aabroo White Flap Bag
H3 Aafreen Black Clutch
H3 Aaliya Silver Potli
H3 Aarish Golden Clutch
H2 Recommended products
H3 Aabha Golden Clutch
H3 Aabroo Black Flap Bag
H3 Aabroo White Flap Bag
H3 Aafreen Black Clutch
H3 Aaliya Silver Potli
H3 Aarish Golden Clutch
H2 Maximal - Modern - Global
H2 Discover What's New.
H2 Where Luxury Is Crafted By Hand
H3 POTLIS
H3 SHEEN EDIT
H3 EMBROIDERED
H3 FLAP BAGS
H3 NAYAB EDIT
H2 BESTSELLER
H3 Top Categories
H3 Discover
H3 Policies
H3 Sign Up Now
H4 Popular Searches
H3 Your cart

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

Form Accessibility

Action

4 of 5 controls have issues

REVIEW

4 of 5 controls have issues

1 control(s) without accessible label

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

Got: <select name="currencies" id="currencies">

3 control(s) rely on placeholder only

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

Got: <input type="search" name="q">; <input type="search" name="q">; <input type="search" name="q" id="mobileSearchInput">

1 control(s) properly labeled

5 controls

1 labeled

3 placeholder only

1 unlabeled

Control	Type	Label	Method
#NewsletterFormEmail-newsletter_LyxXMc	email	Email	for/id
q	search	(Search )	placeholder only
#mobileSearchInput	search	(SEARCH FOR...)	placeholder only
q	search	(Search )	placeholder only
#currencies	select	(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.

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

Link & Button Quality

Action

4 issue(s) across 235 links and 104 buttons

REVIEW

4 issue(s) across 235 links and 104 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://houseofwebhin.com/customer_authentication/redirect?locale=en&region_c…

3 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://houseofwebhin.com/policies/privacy-policy; /pages/return-request; https://www.shopify.com?utm_campaign=poweredby&utm_medium=shopify&utm_source=…

3 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.search-dropdown-close (#549 on page); button.search-dropdown-close (#1028 on page); button.cart-drawer-close (#2141 on page)

231 link(s) with descriptive text

235 links

1 empty

0 generic text

3 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://houseofwebhin.com/policies/priva…	Privacy Policy	new tab	Add '(opens in new tab)' to text
/pages/return-request	Submit A Request Within 24 Hou…	new tab	Add '(opens in new tab)' to text
https://houseofwebhin.com/customer_authe…	(empty)	empty	Add link text or aria-label
https://www.shopify.com?utm_campaign=pow…	Powered by Shopify	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

332 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://houseofwebhin.com/customer_authentication/redirect?locale=en&region_c…

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://houseofwebhin.com/policies/privacy-policy; /pages/return-request; https://www.shopify.com?utm_campaign=poweredby&utm_medium=shopify&utm_source=…

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.search-dropdown-close (#549 on page); button.search-dropdown-close (#1028 on page); button.cart-drawer-close (#2141 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

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 404 Not Found – House Of Webhin ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA

title House of Webhin | Luxury Handmade Clutch…

4.08:1

#000000

#C7345E

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Cookie consent	11.27:1	3.0:1	#000000	#E9AEBF	Pass
h2 Recommended products	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Recommended products	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Maximal - Modern - G…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Discover What's New.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Where Luxury Is Craf…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 BESTSELLER	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 POTLIS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 SHEEN EDIT	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 EMBROIDERED	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 FLAP BAGS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 NAYAB EDIT	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Top Categories	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Discover	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Policies	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Sign Up Now	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Your cart	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title House of Webhin \| Lu…	4.08:1	4.5:1	#000000	#C7345E	Fail
p We and our partners,…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Privacy Policy	16.92:1	4.5:1	#000000	#EAE6E2	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.

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

6 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: 6 all-caps heading(s)

Alt Text Quality

1 of 186 images have issues

PASS

1 of 186 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

185 image(s) with good alt text

186 images 185 good alt text 1 missing

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

A+

Form Input Types

5 form control(s) checked, no type mismatches

PASS

5 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

5 form control(s) checked, no input-semantic issues

PASS

5 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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"

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

Got: en

A+

Tabindex Anti-Patterns

78 explicit tabindex attribute(s) checked, no anti-patterns

PASS

78 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

Iframe Accessibility

1/7 iframe(s) missing title; 0 placeholder(s)

PASS

1/7 iframe(s) missing title; 0 placeholder(s)

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

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

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

Lighthouse Accessibility Audits

Score 90/100 — 3 failing, 27 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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Go to video 1 `section#shopify-section-template--21885140009212__how_gumlet_video_LwNBUz > section#how-gumlet-video-template--21885140009212__how_gumlet_video_LwNBUz > div.how-gumlet-video__container > div.how-gumlet-video__dots`

These are opportunities to improve the usage of ARIA in your application which 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
TRY OUR `section#how-bestsellers-template--21885140009212__how_bestsellers_carousel_jWmVex > div.how-bestsellers__container > header.how-bestsellers__header > p.how-bestsellers__label`
The Sheen Edit- MOP Bags `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
Potlis `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
Flap Bags `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
Box Clutches `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
Printed Clutches `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
Batua Bag `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
Customised Clutches `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
Nayab Edit `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
Embroidered Elegance `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
Facebook `ul.section-footer-column__social-list > li.footer-social-list__item > a.footer-social-list__item-link > span.footer-social-list__item-label`
Instagram `ul.section-footer-column__social-list > li.footer-social-list__item > a.footer-social-list__item-link > span.footer-social-list__item-label`
About Us `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
FAQ's `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
Customer Reviews `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
Blogs `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
Contact Us `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
Terms & Conditions `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
Shipping Policy `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
Privacy Policy `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
Cancellation/ Return and Exchange Policy `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
Return Request `div.section-footer-column__menu > ul.section-footer-column__menu-list > li.section-footer-column__menu-list-item > a`
Welcome to the Webhin Tribe! Unlock 10% off + early access to the latest drops!… `div.section-footer-column > div.section-footer-column-newsletter > div.section-footer-column-newsletter__description > p`
form#contact_form > div.newsletter-form-container > div.newsletter-form-email > input#NewsletterFormEmail-newsletter_LyxXMc `form#contact_form > div.newsletter-form-container > div.newsletter-form-email > input#NewsletterFormEmail-newsletter_LyxXMc`
© 2025 House Of Webhin `div.section-footer-colophon > div.section-footer-colophon__inner > div.section-footer-colophon__text > span`
Powered by Shopify `div.section-footer-colophon__inner > div.section-footer-colophon__text > span > a`
INR ₹ `form#localization_form > div.disclosure > button.disclosure__button > span`
Popular Searches `body.template-index > div#shopify-section-sections--21885139321084__footer > div.house-of-webhin-popular-searches > h4`

These are opportunities to improve the legibility of your content.

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
section#shopify-section-template--21885140009212__how_hero_b4dxyk > section#how-hero-template--21885140009212__how_hero_b4dxyk > div.how-hero__wrapper > img.how-hero__image `section#shopify-section-template--21885140009212__how_hero_b4dxyk > section#how-hero-template--21885140009212__how_hero_b4dxyk > div.how-hero__wrapper > img.how-hero__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.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

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

●`[role]`s have all required `[aria-*]` attributes

●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

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

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

●Buttons have an accessible name

●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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●Elements use only permitted ARIA attributes

●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

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

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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○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

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