Skip to content
https://frenchmeadows.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
7
REVIEW
3
PASS
14
INFO
0
Checks
24
14 PASS 3 REVIEW 7 FIX
D
Mobile Keyboard & Autofill
Action
12/12 eligible field(s) missing autocomplete or inputmode
FIX
12/12 eligible field(s) missing autocomplete or inputmode
Warning::
4 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: name, email, tel, country-name.
Got: <input type="text" name="name" id="shopeetech-bis-popup-form-name">, <input type="email" id="shopeetech-bis-popup-form-email">, <input type="tel" id="shopeetech-bis-popup-form-mobile">, <select name="country" id="shopeetech-bis-popup-form-country">
Warning::
8 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, tel, numeric.
Got: <input type="search" name="country_filter" id="country-filter-input">, <input type="search" name="country_filter" id="country-filter-input">, <input type="search" name="q" id="Search-In-Modal">, <input type="email" name="contact[email]" id="NewsletterForm--template--27312687153456__newsletter_DV4HYN">, <input type="email" name="contact[email]" id="NewsletterForm--sections--27312683909424__footer">
F
404 Error Page
Action
HTTP 429, custom page
FIX
HTTP 429, custom page
Warning::
Unexpected status code: HTTP 429
Expected HTTP 404 but received 429. This may confuse search engine crawlers.
Got: HTTP 429
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 429 ✗Page Title Verifying your connection... ✓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
Theme color only
FIX
Theme color only
Info::
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.
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 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.

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Form Accessibility
Action
6 of 14 controls have issues
REVIEW
6 of 14 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="country" id="shopeetech-bis-popup-form-country">
Warning::
5 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="name" id="shopeetech-bis-popup-form-name">; <input type="email" id="shopeetech-bis-popup-form-email">; <input type="tel" id="shopeetech-bis-popup-form-mobile">; <input type="number" id="shopeetech-bis-popup-form-amount">; <textarea id="shopeetech-bis-popup-form-customMessage">
Info::
8 control(s) properly labeled
14 controls
8 labeled
5 placeholder only
1 unlabeled
ControlTypeLabelMethod
#country-filter-inputsearchSearchfor/id
#country-filter-inputsearchSearchfor/id
#Search-In-ModalsearchSearchfor/id
#NewsletterForm--template--27312687153456__newsletter_DV4HYNemailEmailfor/id
#NewsletterForm--sections--27312683909424__footeremailEmailfor/id
#bis_email_checkboxcheckboxnone
#bis_sms_checkboxcheckboxnone
#bis_whatsApp_checkboxcheckboxnone
#shopeetech-bis-popup-form-amountnumber(Enter quantity)placeholder only
#shopeetech-bis-popup-form-customMessagetextarea(Enter Custom message)placeholder only
#shopeetech-bis-popup-form-nametext(Enter name)placeholder only
#shopeetech-bis-popup-form-emailemail(Email address)placeholder only
#shopeetech-bis-popup-form-mobiletel(Enter mobile number)placeholder only
#shopeetech-bis-popup-form-countryselect(none)none

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

<select name="country" id="shopeetech-bis-popup-form-country">

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="name" id="shopeetech-bis-popup-form-name">; <input type="email" id="shopeetech-bis-popup-form-email">; <input type="tel" id="shopeetech-bis-popup-form-mobile">; <input type="number" id="shopeetech-bis-popup-form-amount">; <textarea id="shopeetech-bis-popup-form-customMessage">

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

B
Tabindex Anti-Patterns
0 positive, 5 -1-on-focusable
REVIEW
0 positive, 5 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <input id="bis_hp_field">
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.)
C
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 2 pass AA only
a Privacy Policy
3.29:1
#000000
on
#516450
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

1 contrast failures on background images/gradients

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

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Cookie consent21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Country/region21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Country/region21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Item added to your c…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 French Meadows21.00:13.0:1
#000000
#FFFFFF
Pass
h2 New Arrivals21.00:13.0:1
#000000
#FFFFFF
Pass
h2 New Arrivals & Fresh…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Collections21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Best Sellers21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Discover your inner …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Follow us on Instagr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Fairies Have All the…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 French Meadows Corse…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Policy21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Quick links21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Subscribe to our ema…21.00:13.0:1
#000000
#FFFFFF
Pass
title French Meadows5.50:14.5:1
#000000
#6F8973
Pass
p We and our partners,…21.00:14.5:1
#000000
#FFFFFF
Pass
a Privacy Policy3.29:14.5:1
#000000
#516450
Fail
span Manage preferences5.51:14.5:1
#000000
#71887C
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
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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

A+
Heading Hierarchy
57 headings
PASS
57 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Cookie consent
  • H2 Country/region
  • H1 (empty)
  • H2 Country/region
  • H2 Item added to your cart
  • H2 French Meadows
  • H2 New Arrivals
  • H2 New Arrivals & Fresh Restocks
  • H3 Brown Duelist Corset Belt
  • H3 Brown Duelist Corset Belt
  • H3 Black Botanical Corset
  • H3 Black Botanical Corset
  • H3 Lacey Vampire Blouse
  • H3 Lacey Vampire Blouse
  • H3 Black Satin Ballerina Stays
  • H3 Black Satin Ballerina Stays
  • H3 Black Ramie Agnes Stays
  • H3 Black Ramie Agnes Stays
  • H3 Black Velvet Bell Sleeve Dress
  • H3 Black Velvet Bell Sleeve Dress
  • H2 Collections
  • H3 Corsets
  • H3 Corsets
  • H3 Chemises
  • H3 Chemises
  • H3 Accessories
  • H3 Accessories
  • H3 Dresses
  • H3 Dresses
  • H3 Skirts
  • H3 Skirts
  • H3 Other Clothing
  • H3 Other Clothing
  • H2 Best Sellers
  • H3 Darcy Shirt
  • H3 Darcy Shirt
  • H3 Victorian Bloomers
  • H3 Victorian Bloomers
  • H3 Leather Renaissance Belt
  • H3 Leather Renaissance Belt
  • H3 Elven Medieval Belt Pouch
  • H3 Elven Medieval Belt Pouch
  • H2 Discover your inner adventurer
  • H3 Quilted Gambeson
  • H3 Quilted Gambeson
  • H3 Pirate Captain's Coat
  • H3 Pirate Captain's Coat
  • H3 Darcy Shirt
  • H3 Darcy Shirt
  • H3 Black Pirate Vest
  • H3 Black Pirate Vest
  • H2 Follow us on Instagram
  • H2 Fairies Have All the Best Secrets!
  • H2 French Meadows Corsets
  • H2 Policy
  • H2 Quick links
  • H2 Subscribe to our emails

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+
Heading Text Quality
All 57 heading(s) have substantive, well-formed text
PASS
All 57 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 73 images OK
PASS
All 73 images OK
Info::
15 decorative image(s) correctly marked
Info::
58 image(s) with good alt text
73 images 58 good alt text 15 decorative
All images have appropriate alt text.
A+
Form Input Types
14 form control(s) checked, no type mismatches
PASS
14 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
14 form control(s) checked, no input-semantic issues
PASS
14 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+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
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 8 visible text node(s) render at >= 12 CSS pixels
PASS
All 8 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::
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.
A
Lighthouse Accessibility Audits
Score 93/100 — 3 failing, 29 passed
PASS
93

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Instagram post opens in a popup div.instafeed-new-layout-container > div.instafeed-new-layout-wrapper > div.instafeed-new-layout-item > div.instafeed-new-layout-item-container
Instagram post opens in a popup div.instafeed-new-layout-container > div.instafeed-new-layout-wrapper > div.instafeed-new-layout-item > div.instafeed-new-layout-item-container
Instagram post opens in a popup div.instafeed-new-layout-container > div.instafeed-new-layout-wrapper > div.instafeed-new-layout-item > div.instafeed-new-layout-item-container
Instagram post opens in a popup div.instafeed-new-layout-container > div.instafeed-new-layout-wrapper > div.instafeed-new-layout-item > div.instafeed-new-layout-item-container
Instagram post opens in a popup div.instafeed-new-layout-container > div.instafeed-new-layout-wrapper > div.instafeed-new-layout-item > div.instafeed-new-layout-item-container
Instagram post opens in a popup div.instafeed-new-layout-container > div.instafeed-new-layout-wrapper > div.instafeed-new-layout-item > div.instafeed-new-layout-item-container

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
FREE SHIPPING ON U.S. ORDERS +$99 div.page-width > div.announcement-bar > p.announcement-bar__message > span
View all div.color-scheme-1 > div#collection-template--27312687153456__featured_collection > div.center > a.button
read more about us div.rich-text__wrapper > div.rich-text__blocks > div.rich-text__buttons > a.button
View all div.color-scheme-1 > div#collection-template--27312687153456__featured_collection_HyVDcJ > div.center > a.button
Fairies Have All the Best Secrets! section#shopify-section-template--27312687153456__newsletter_DV4HYN > div.newsletter > div.newsletter__wrapper > h2.inline-richtext
Subscribe to our newsletter for subcriber only sales and discounts, to hear abo… div.newsletter > div.newsletter__wrapper > div.newsletter__subheading > p
form#contact_form > div.newsletter-form__field-wrapper > div.field > input#NewsletterForm--template--27312687153456__newsletter_DV4HYN form#contact_form > div.newsletter-form__field-wrapper > div.field > input#NewsletterForm--template--27312687153456__newsletter_DV4HYN
Email form#contact_form > div.newsletter-form__field-wrapper > div.field > label.field__label
Policy div.footer__content-top > div.footer__blocks-wrapper > div.footer-block > h2.footer-block__heading
Sizing Guide div.footer-block > ul.footer-block__details-content > li > a.link
Shipping & Returns div.footer-block > ul.footer-block__details-content > li > a.link
Privacy Policy div.footer-block > ul.footer-block__details-content > li > a.link
Terms & Conditions div.footer-block > ul.footer-block__details-content > li > a.link
Sitemap div.footer-block > ul.footer-block__details-content > li > a.link
Quick links div.footer__content-top > div.footer__blocks-wrapper > div.footer-block > h2.footer-block__heading
Search div.footer-block > ul.footer-block__details-content > li > a.link
Home div.footer-block > ul.footer-block__details-content > li > a.link
Shop All div.footer-block > ul.footer-block__details-content > li > a.link
Affiliate Program div.footer-block > ul.footer-block__details-content > li > a.link
Returns and Cancellations div.footer-block > ul.footer-block__details-content > li > a.link
Subscribe to our emails div.footer__content-top > div.footer-block--newsletter > div.footer-block__newsletter > h2.footer-block__heading
form#ContactFooter > div.newsletter-form__field-wrapper > div.field > input#NewsletterForm--sections--27312683909424__footer form#ContactFooter > div.newsletter-form__field-wrapper > div.field > input#NewsletterForm--sections--27312683909424__footer
Email form#ContactFooter > div.newsletter-form__field-wrapper > div.field > label.field__label
© 2026, French Meadows div.footer__content-bottom > div.footer__content-bottom-wrapper > div.footer__copyright > small.copyright__content
French Meadows div.footer__content-bottom-wrapper > div.footer__copyright > small.copyright__content > a
Powered by Shopify div.footer__content-bottom-wrapper > div.footer__copyright > small.copyright__content > a

These are opportunities to improve the legibility of your content.

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
@french.meadows div.page-width > div#shopify-block-AWFBjOGhFWEtaWmI3b__instafeed_app_block_g4npfJ > div.instafeed-bottom-link-wrapper > a
○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]` 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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●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
●ARIA IDs are unique
●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
○`[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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback