Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 3 REVIEW 8 FIX

Alt Text Quality

Action

13 of 120 images have issues

FIX

13 of 120 images have issues

13 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

3 image-in-link without alt text

An image inside a link with no alt creates an empty link.

27 image(s) with alt text over 125 characters

80 image(s) with good alt text

120 images 80 good alt text 13 missing

Issue	Count
missing	13 image(s)
too long	27 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Tap Target Adequacy

Action

10 tap target(s) too small or too close together

FIX

10 tap target(s) too small or too close together

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

404 Error Page

Action

HTTP 403, custom page

FIX

HTTP 403, custom page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 403 ✗Page Title Verifying your connection... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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 ✗

Heading Hierarchy

Action

69 headings, 1 skip(s)

REVIEW

69 headings, 1 skip(s)

No H1 heading found

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

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H3 Gift Card - La Femme en Noir
H3 Häxan Witch Sun Hat in Black
H3 Häxan Witch Sun Hat in Natural
H3 Brontë Blouse in Ivory
H3 Brontë Blouse in Black
H3 Duchess Corset in Black Cotton Sateen
H3 Baudelaire Swing Dress in Hunter Green
H3 Baudelaire Swing Dress in Black
H3 Gift Card - La Femme en Noir
H3 Häxan Witch Sun Hat in Black
H3 Häxan Witch Sun Hat in Natural
H3 Brontë Blouse in Ivory
H3 Brontë Blouse in Black
H3 Duchess Corset in Black Cotton Sateen
H3 Baudelaire Swing Dress in Hunter Green
H3 Baudelaire Swing Dress in Black
H3 PRE-ORDER - Baudelaire Wiggle Dress in Oxblood
H3 PRE-ORDER - Baudelaire Swing Dress in Oxblood
H3 PRE-ORDER - Baudelaire Wiggle Dress in Hunter Green
H3 PRE-ORDER - Baudelaire Wiggle Dress in Black
H3 PRE-ORDER - Ambrosia Dress in Black
H3 PRE-ORDER - Morticia Dress in Black
H3 PRE-ORDER - Coffin Cotton Beach Towel in Black
H3 PRE-ORDER - Gothic Umbrella in Black
H3 FINAL SALE - Sleepy Hollow™ Pumpkin Bag
H3 FINAL SALE - Faux Leather Opera Gloves in Hunter Green
H3 FINAL SALE - Faux Leather Opera Gloves in Navy
H3 FINAL SALE - Southern Gothic Skirt in Crimson
H3 FINAL SALE - Heroine Maxi Dress in Medusa Print
H3 FINAL SALE - Solstice Babydoll Dress in Black Chiffon
H3 FINAL SALE - Georgette Wrap Top in Olive
H3 FINAL SALE - Georgette Wrap Top in Ivory
H2 Shop Collaborations
H3 Nosferatu
H3 Nosferatu
H3 Crimson Peak
H3 Crimson Peak
H3 Sleepy Hollow
H3 Sleepy Hollow
H3 VAMPIRA
H3 VAMPIRA
H2 New & Coveted
H3 Victorian Silk Blouse in Black
H3 CRIMSON PEAK™ Edith Victorian Gown in Ivory
H3 Lady Mourning Victorian Gown in Black
H3 Faux Leather Opera Gloves in Black
H3 Vamp Batwing Sunglasses in Black
H3 Black Marilyn Lace Gown in Black
H2 Pre-Orders
H3 PRE-ORDER - Baudelaire Wiggle Dress in Oxblood
H3 PRE-ORDER - Baudelaire Swing Dress in Oxblood
H3 PRE-ORDER - Baudelaire Wiggle Dress in Hunter Green
H3 PRE-ORDER - Baudelaire Wiggle Dress in Black
H3 PRE-ORDER - Ambrosia Dress in Black
H3 PRE-ORDER - Morticia Dress in Black
H3 PRE-ORDER - Coffin Cotton Beach Towel in Black
H3 PRE-ORDER - Gothic Umbrella in Black
H2 LOYALTY IS ALWAYS REWARDED
H2 About the Brand
H2 ETHICALLY MADE PRODUCTION
H2 REVIEWS
H2 SUBSCRIBE
H3 Contact Us
H3 Explore
H3 Stay Connected
H2 My cart
H2 Important Notice: Pre-Order Items in Your Cart
H4 Choose Options skipped
H4 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

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

Link & Button Quality

Action

4 issue(s) across 207 links and 777 buttons

REVIEW

4 issue(s) across 207 links and 777 buttons

3 link(s) with no accessible text

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

Got: /products/pre-order-juliet-sheer-lace-maxi-dress-in-black; /collections/collaborations; a.block (#1246 on page)

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /pages/about-us-test ("Learn more")

3 link(s) open in new tab without warning

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

Got: https://www.facebook.com/lafemmeennoir/; https://www.instagram.com/la_femme_en_noir_/; https://www.tiktok.com/@lafemmeennoirofficial

200 link(s) with descriptive text

207 links

3 empty

1 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/products/pre-order-juliet-sheer-lace-ma…	(empty)	empty	Add link text or aria-label
/collections/collaborations	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
/pages/about-us-test	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: About Us Test
https://www.facebook.com/lafemmeennoir/	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/la_femme_en_no…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@lafemmeennoiroff…	TikTok	new tab	Add '(opens in new tab)' to text

977 links and buttons have descriptive text

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

/products/pre-order-juliet-sheer-lace-maxi-dress-in-black; /collections/collaborations; a.block (#1246 on page)

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

Generic link text like 'click here' doesn't describe the destination.

/pages/about-us-test ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://www.facebook.com/lafemmeennoir/; https://www.instagram.com/la_femme_en_noir_/; https://www.tiktok.com/@lafemmeennoirofficial

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h2 Shop Collaborations

1.02:1

#000000

#000401

needs 3.0:1 (large text)

24px · bottom of viewport

h2 New & Coveted

1.02:1

#000000

#000401

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Pre-Orders

1.02:1

#000000

#000401

needs 3.0:1 (large text)

24px · bottom of viewport

h2 LOYALTY IS ALWAYS REWARDED

1.02:1

#000000

#000401

needs 3.0:1 (large text)

24px · bottom of viewport

h2 About the Brand

1.02:1

#000000

#000401

needs 3.0:1 (large text)

24px · bottom of viewport

h2 ETHICALLY MADE PRODUCTION

1.02:1

#000000

#000401

needs 3.0:1 (large text)

24px · bottom of viewport

h2 REVIEWS

1.02:1

#000000

#000401

needs 3.0:1 (large text)

24px · bottom of viewport

h2 SUBSCRIBE

1.02:1

#000000

#000401

needs 3.0:1 (large text)

24px · bottom of viewport

h2 My cart

1.02:1

#000000

#000401

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Important Notice: Pre-Order Items in You…

1.02:1

#000000

#000401

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Gift Card - La Femme en Noir

1.02:1

#000000

#000401

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Häxan Witch Sun Hat in Black

1.02:1

#000000

#000401

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Häxan Witch Sun Hat in Natural

1.02:1

#000000

#000401

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Brontë Blouse in Ivory

1.02:1

#000000

#000401

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Brontë Blouse in Black

1.02:1

#000000

#000401

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Duchess Corset in Black Cotton Sateen

1.02:1

#000000

#000401

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Baudelaire Swing Dress in Hunter Green

1.02:1

#000000

#000401

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Baudelaire Swing Dress in Black

1.02:1

#000000

#000401

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Nosferatu

1.02:1

#000000

#000401

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Nosferatu

1.02:1

#000000

#000401

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Shop Collaborations	1.02:1	3.0:1	#000000	#000401	Fail
h2 New & Coveted	1.02:1	3.0:1	#000000	#000401	Fail
h2 Pre-Orders	1.02:1	3.0:1	#000000	#000401	Fail
h2 LOYALTY IS ALWAYS RE…	1.02:1	3.0:1	#000000	#000401	Fail
h2 About the Brand	1.02:1	3.0:1	#000000	#000401	Fail
h2 ETHICALLY MADE PRODU…	1.02:1	3.0:1	#000000	#000401	Fail
h2 REVIEWS	1.02:1	3.0:1	#000000	#000401	Fail
h2 SUBSCRIBE	1.02:1	3.0:1	#000000	#000401	Fail
h2 My cart	1.02:1	3.0:1	#000000	#000401	Fail
h2 Important Notice: Pr…	1.02:1	3.0:1	#000000	#000401	Fail
h3 Gift Card - La Femme…	1.02:1	3.0:1	#000000	#000401	Fail
h3 Häxan Witch Sun Hat…	1.02:1	3.0:1	#000000	#000401	Fail
h3 Häxan Witch Sun Hat…	1.02:1	3.0:1	#000000	#000401	Fail
h3 Brontë Blouse in Iv…	1.02:1	3.0:1	#000000	#000401	Fail
h3 Brontë Blouse in Bl…	1.02:1	3.0:1	#000000	#000401	Fail
h3 Duchess Corset in Bl…	1.02:1	3.0:1	#000000	#000401	Fail
h3 Baudelaire Swing Dre…	1.02:1	3.0:1	#000000	#000401	Fail
h3 Baudelaire Swing Dre…	1.02:1	3.0:1	#000000	#000401	Fail
h3 Nosferatu	1.02:1	3.0:1	#000000	#000401	Fail
h3 Nosferatu	1.02:1	3.0:1	#000000	#000401	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+

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

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)

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#predictive-search-input	search	Search	for/id
#footer-newsletter-email	email	Email Address	for/id
input	checkbox		none

A+

Form Input Types

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

3 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

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

PASS

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

No tabindex anti-patterns detected

Iframe Accessibility

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

PASS

1/3 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+

Mobile-Readable Font Sizes

All 151 visible text node(s) render at >= 12 CSS pixels

PASS

All 151 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

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 92/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.

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
div#shopify-section-template--20169236054086__lookbook_QcJCCc > lookbook-section#Lookbook-template--20169236054086__lookbook_QcJCCc > div.lookbook__frame--mobile > img.w-full `div#shopify-section-template--20169236054086__lookbook_QcJCCc > lookbook-section#Lookbook-template--20169236054086__lookbook_QcJCCc > div.lookbook__frame--mobile > img.w-full`

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

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
Go to slide 1 `section#Hero-template--20169236054086__hero_U9WXfE > hero-slider > div.hero__dots > button.hero__dot`
Go to slide 2 `section#Hero-template--20169236054086__hero_U9WXfE > hero-slider > div.hero__dots > button.hero__dot`
Go to slide 1 `section#Hero-template--20169236054086__hero > hero-slider > div.hero__dots > button.hero__dot`
Go to slide 2 `section#Hero-template--20169236054086__hero > hero-slider > div.hero__dots > button.hero__dot`
Go to slide 1 `section#Hero-template--20169236054086__hero_Y8qXTq > hero-slider > div.hero__dots > button.hero__dot`
Go to slide 2 `section#Hero-template--20169236054086__hero_Y8qXTq > hero-slider > div.hero__dots > button.hero__dot`
Go to slide 1 `section.bg-black > collection-slider.block > div.flex > button.w-[10px]`
Go to slide 2 `section.bg-black > collection-slider.block > div.flex > button.w-[10px]`
Go to slide 3 `section.bg-black > collection-slider.block > div.flex > button.w-[10px]`
Go to slide 4 `section.bg-black > collection-slider.block > div.flex > button.w-[10px]`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NOSFERATU `section.bg-black > collection-slider.block > div.collection-slider-track > a.collection-slide`
CRIMSON PEAK `section.bg-black > collection-slider.block > div.collection-slider-track > a.collection-slide`
SLEEPY HOLLOW `section.bg-black > collection-slider.block > div.collection-slider-track > a.collection-slide`
VAMPIRA `section.bg-black > collection-slider.block > div.collection-slider-track > a.collection-slide`

○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

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

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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

●Identical links have the same purpose.

○`[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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○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

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

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

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