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

Form Accessibility

Action

23 of 25 controls have issues

FIX

23 of 25 controls have issues

20 control(s) without accessible label

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

Got: <input type="radio" id="bonne-nuit-pajamas-chocolate-red-XXS">; <input type="radio" id="bonne-nuit-pajamas-chocolate-red-XS">; <input type="radio" id="bonne-nuit-pajamas-chocolate-red-S">; <input type="radio" id="bonne-nuit-pajamas-chocolate-red-M">; <input type="radio" id="bonne-nuit-pajamas-chocolate-red-L">; <input type="radio" id="bonne-nuit-pajamas-chocolate-red-XL">; <input type="radio" id="calvin-beanie-black-O/S">; <input type="radio" id="mini-marin-socks-light-blue-butterscotch-O/S">; <input type="radio" id="bonne-nuit-pajamas-tan-pale-blue-XXS">; <input type="radio" id="bonne-nuit-pajamas-tan-pale-blue-XS"> (+10 more)

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">

2 control(s) properly labeled

25 controls

2 labeled

3 placeholder only

20 unlabeled

Control	Type	Label	Method
email	email	Email Address	aria-label
email	email	Email Address	aria-label
q	search	(Search)	placeholder only
q	search	(Search Keywords)	placeholder only
q	search	(Search Keywords)	placeholder only
#bonne-nuit-pajamas-chocolate-red-XS	radio	(none)	none
#bonne-nuit-pajamas-chocolate-red-S	radio	(none)	none
#bonne-nuit-pajamas-chocolate-red-M	radio	(none)	none
#bonne-nuit-pajamas-chocolate-red-L	radio	(none)	none
#bonne-nuit-pajamas-chocolate-red-XL	radio	(none)	none
#calvin-beanie-black-O/S	radio	(none)	none
#mini-marin-socks-light-blue-butterscotch-O/S	radio	(none)	none
#bonne-nuit-pajamas-tan-pale-blue-XXS	radio	(none)	none
#bonne-nuit-pajamas-tan-pale-blue-XS	radio	(none)	none
#bonne-nuit-pajamas-tan-pale-blue-S	radio	(none)	none
#bonne-nuit-pajamas-tan-pale-blue-M	radio	(none)	none
#bonne-nuit-pajamas-tan-pale-blue-L	radio	(none)	none
#bonne-nuit-pajamas-tan-pale-blue-XL	radio	(none)	none
#walker-scarf-dark-tan-speckle-O/S	radio	(none)	none
#walker-gloves-dark-tan-speckle-O/S	radio	(none)	none
#otto-scarf-port-sunset-O/S	radio	(none)	none
#otto-triangle-scarf-camel-sunset-O/S	radio	(none)	none
#striped-bobby-socks-cream-pine-oxblood-O/S	radio	(none)	none
#calvin-beanie-red-O/S	radio	(none)	none
#bonne-nuit-pajamas-chocolate-red-XXS	radio	(none)	none

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

<input type="radio" id="bonne-nuit-pajamas-chocolate-red-XXS">; <input type="radio" id="bonne-nuit-pajamas-chocolate-red-XS">; <input type="radio" id="bonne-nuit-pajamas-chocolate-red-S">; <input type="radio" id="bonne-nuit-pajamas-chocolate-red-M">; <input type="radio" id="bonne-nuit-pajamas-chocolate-red-L">; <input type="radio" id="bonne-nuit-pajamas-chocolate-red-XL">; <input type="radio" id="calvin-beanie-black-O/S">; <input type="radio" id="mini-marin-socks-light-blue-butterscotch-O/S">; <input type="radio" id="bonne-nuit-pajamas-tan-pale-blue-XXS">; <input type="radio" id="bonne-nuit-pajamas-tan-pale-blue-XS"> (+10 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.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Mobile Keyboard & Autofill

Action

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

FIX

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

2 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" name="email">, <input type="email" name="email">

5 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: search, email.

Got: <input type="search" name="q">, <input type="search" name="q">, <input type="email" name="email">, <input type="search" name="q">, <input type="email" name="email">

Mobile-Readable Font Sizes

Action

36% of visible text renders at >= 12 CSS px (42 below threshold)

FIX

36% of visible text renders at >= 12 CSS px (42 below threshold)

42 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: <a> 9.0px ("Cart"); <p> 10.0px ("Shop Le Drop"); <p> 10.0px ("Shop Outerwear"); <p> 6.0px ("Newest"); <h3> 11.0px ("Bonne Nuit Pajamas").

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

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

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

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

4 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 4 <nav> element(s)

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.

Landmark Structure

Action

16 landmarks

REVIEW

16 landmarks

<main> landmark present

Multiple <main> landmarks (4 found)

A page should have only one <main> landmark.

4 <nav> landmark(s) found

1 of 4 <nav> elements are unlabeled

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

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

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

Link & Button Quality

Action

2 issue(s) across 168 links and 62 buttons

REVIEW

2 issue(s) across 168 links and 62 buttons

7 link(s) open in new tab without warning

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

Got: https://lalignenyc.com/collections/la-ligne-x-dianna-agron; https://lalignenyc.com/collections/la-ligne-x-dianna-agron; https://lalignenyc.com/pages/behind-the-label; https://lalignenyc.com/stores; https://lalignenyc.com/in-line; https://lalignenyc.com/collections; https://www.pii.ai

2 button(s) with no accessible text

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

Got: button.hidden (#152 on page); button.close-btn (#442 on page)

161 link(s) with descriptive text

168 links

0 empty

0 generic text

7 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://lalignenyc.com/collections/la-li…	Entre Amis	new tab	Add '(opens in new tab)' to text
https://lalignenyc.com/collections/la-li…	Entre Amis	new tab	Add '(opens in new tab)' to text
https://lalignenyc.com/pages/behind-the-…	About The Brand	new tab	Add '(opens in new tab)' to text
https://lalignenyc.com/stores	Stores	new tab	Add '(opens in new tab)' to text
https://lalignenyc.com/in-line	La Bande	new tab	Add '(opens in new tab)' to text
https://lalignenyc.com/collections	Stories	new tab	Add '(opens in new tab)' to text
https://www.pii.ai	PieEye Inc.	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

221 links and buttons have descriptive text

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

https://lalignenyc.com/collections/la-ligne-x-dianna-agron; https://lalignenyc.com/collections/la-ligne-x-dianna-agron; https://lalignenyc.com/pages/behind-the-label; https://lalignenyc.com/stores; https://lalignenyc.com/in-line; https://lalignenyc.com/collections; https://www.pii.ai

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.hidden (#152 on page); button.close-btn (#442 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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 10 fail WCAG AA

REVIEW

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

10 pass 10 fail WCAG AA

h2 Line up & we'll share 10% off your first…

1.00:1

#000000

needs 3.0:1 (large text)

24px · mid-page

h2 Coat Check

2.35:1

#FFFFFF

#ADA8A6

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Best Of La Ligne

2.35:1

#FFFFFF

#ADA8A6

needs 3.0:1 (large text)

24px · bottom of viewport

h2 La Ligne Jean

2.35:1

#FFFFFF

#ADA8A6

needs 3.0:1 (large text)

24px · bottom of viewport

h2 La Ligne

2.35:1

#FFFFFF

#ADA8A6

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Jean

2.35:1

#FFFFFF

#ADA8A6

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Personal

2.35:1

#FFFFFF

#ADA8A6

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Touch

2.35:1

#FFFFFF

#ADA8A6

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Follow Us

2.35:1

#FFFFFF

#ADA8A6

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Le Drop

2.35:1

#FFFFFF

#ADA8A6

needs 3.0:1 (large text)

24px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 La Ligne New York	8.93:1	3.0:1	#000000	#ADA8A6	Pass
h2 Line up & we'll shar…	1.00:1	3.0:1	#000000	#000000	Fail
h2 New In	8.93:1	3.0:1	#000000	#ADA8A6	Pass
h2 Coat Check	2.35:1	3.0:1	#FFFFFF	#ADA8A6	Fail
h2 Newest	8.93:1	3.0:1	#000000	#ADA8A6	Pass
h2 Best Of La Ligne	2.35:1	3.0:1	#FFFFFF	#ADA8A6	Fail
h2 La Ligne Jean	2.35:1	3.0:1	#FFFFFF	#ADA8A6	Fail
h2 La Ligne	2.35:1	3.0:1	#FFFFFF	#ADA8A6	Fail
h2 Jean	2.35:1	3.0:1	#FFFFFF	#ADA8A6	Fail
h2 Stripe	8.93:1	3.0:1	#000000	#ADA8A6	Pass
h2 Your Life	8.93:1	3.0:1	#000000	#ADA8A6	Pass
h2 Personal	2.35:1	3.0:1	#FFFFFF	#ADA8A6	Fail
h2 Touch	2.35:1	3.0:1	#FFFFFF	#ADA8A6	Fail
h2 Follow Us	2.35:1	3.0:1	#FFFFFF	#ADA8A6	Fail
h2 Le Drop	2.35:1	3.0:1	#FFFFFF	#ADA8A6	Fail
h2 Line up & we'll shar…	8.93:1	3.0:1	#000000	#ADA8A6	Pass
h3 Cart	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h3 SEARCH	16.04:1	3.0:1	#000000	#E5E0DD	Pass
h3 MENU	16.16:1	3.0:1	#000000	#E5E1DE	Pass
h3 Bonne Nuit Pajamas	8.93:1	3.0:1	#000000	#ADA8A6	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.

Heading Hierarchy

35 headings, 1 skip(s)

PASS

35 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

H3 Cart
H3 SEARCH
H3 MENU
H2 Line up & we'll share 10% off your first order.
H4 Recent skipped
H4 La Ligne & Banana Republic
H4 La Ligne x Erin Walsh
H4 More stories
H1 La Ligne New York
H2 New In
H2 Coat Check
H2 Newest
H3 Bonne Nuit Pajamas
H3 Calvin Beanie
H3 Mini Marin Socks
H3 Bonne Nuit Pajamas
H3 Walker Scarf
H3 Walker Gloves
H3 Otto Scarf
H3 Otto Triangle Scarf
H3 Striped Bobby Socks
H3 Calvin Beanie
H2 Best Of La Ligne
H2 La Ligne Jean
H3 The Stripe: Bold. Universal. Timeless. Democratic.
H2 La Ligne Jean
H2 Stripe Your Life
H2 Personal Touch
H2 Follow Us
H2 Le Drop
H2 Line up & we'll share 10% off your first order.
H3 COMPANY
H3 CARE
H3 CONNECT
H3 LEGAL

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

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+

Alt Text Quality

All 36 images OK

PASS

All 36 images OK

36 image(s) with good alt text

36 images 36 good alt text

All images have appropriate alt text.

A+

Form Input Types

25 form control(s) checked, no type mismatches

PASS

25 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Document Language

Lang attribute set to "EN"

PASS

Lang attribute set to "EN"

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

Got: EN

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

Iframe Accessibility

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

PASS

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

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

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

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 24 passed

PASS

100

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.

○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

●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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

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

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

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

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

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