Skip to content
https://popsockets.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
7 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 7 <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.
B
Landmark Structure
31 landmarks
REVIEW
31 landmarks
Info::
<main> landmark present
Info::
7 <nav> landmark(s) found
Warning::
1 of 7 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV "main menu" 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

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

C
Heading Hierarchy
Action
5 headings, 2 skip(s)
REVIEW
5 headings, 2 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Find Your Favorites
  • H1 Créez le vôtre
  • H5 Sélectionnez votre région ci-dessous skipped
  • H1 Nous livrons à France duplicate H1
  • H5 Video modal title skipped

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

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

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

C
Alt Text Quality
Action
2 of 521 images have issues
REVIEW
2 of 521 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
333 decorative image(s) correctly marked
Info::
186 image(s) with good alt text
521 images 186 good alt text 333 decorative 2 missing
IssueCount
missing2 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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Sites-AMER-Site ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Favicon & Branding
Action
7 icon(s) detected
REVIEW
7 icon(s) detected
Info::
favicon.ico present at site root
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'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA
h1 Nous livrons à France
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
32px · bottom of viewport
span Press Alt+1 for screen-reader mode, Alt+…
1.24:1
#000000
on
#1B183D
needs 4.5:1 (normal text)
16px · top of page (header area)
a Accessibility Screen-Reader Guide, Feedb…
1.79:1
#000000
on
#2E3A3D
needs 4.5:1 (normal text)
16px · top of page (header area)
title PopSockets | The Original Phone Grip | M…
1.93:1
#000000
on
#3D3D3D
needs 4.5:1 (normal text)
16px · top of page (header area)
label fr-FR
1.93:1
#000000
on
#3D3D3D
needs 4.5:1 (normal text)
16px · top of page (header area)
label EUR
1.93:1
#000000
on
#3D3D3D
needs 4.5:1 (normal text)
16px · above the fold
label twravuXaWQ60GDtJGr3n5TigSVohRzw8htb71LpF…
1.93:1
#000000
on
#3D3D3D
needs 4.5:1 (normal text)
16px · above the fold
label { "SELECT_PHONE": "Sélectionnez votre …
1.75:1
#000000
on
#3B3535
needs 4.5:1 (normal text)
16px · above the fold
textarea { "SELECT_PHONE": "Sélectionnez votre …
1.25:1
#000000
on
#231B1D
needs 4.5:1 (normal text)
16px · above the fold
p Supprimer le bon de réduction ?
1.41:1
#000000
on
#26272A
needs 4.5:1 (normal text)
16px · above the fold
div Voulez-vous vraiment supprimer le bon de…
1.34:1
#000000
on
#242326
needs 4.5:1 (normal text)
16px · above the fold
button Non
1.57:1
#000000
on
#293035
needs 4.5:1 (normal text)
16px · above the fold
button Oui
1.57:1
#000000
on
#293035
needs 4.5:1 (normal text)
16px · above the fold
div Félicitations! Vous bénéficiez de la …
1.57:1
#000000
on
#293035
needs 4.5:1 (normal text)
16px · above the fold
div GRATUIT
1.59:1
#000000
on
#2A3135
needs 4.5:1 (normal text)
16px · mid-page
a Passer au contenu principal
1.74:1
#000000
on
#363637
needs 4.5:1 (normal text)
16px · mid-page
a Passer au contenu du pied de page
1.63:1
#000000
on
#313232
needs 4.5:1 (normal text)
16px · mid-page
span start animation
1.87:1
#000000
on
#3B3B3B
needs 4.5:1 (normal text)
16px · mid-page
button start
1.85:1
#000000
on
#3A3A3A
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Nous livrons à Fran…1.93:13.0:1
#000000
#3D3D3D
Fail
span Press Alt+1 for scre…1.24:14.5:1
#000000
#1B183D
Fail
a Accessibility Screen…1.79:14.5:1
#000000
#2E3A3D
Fail
title PopSockets | The Ori…1.93:14.5:1
#000000
#3D3D3D
Fail
label fr-FR1.93:14.5:1
#000000
#3D3D3D
Fail
label EUR1.93:14.5:1
#000000
#3D3D3D
Fail
label twravuXaWQ60GDtJGr3n…1.93:14.5:1
#000000
#3D3D3D
Fail
label { "SELECT_PHONE": "…1.75:14.5:1
#000000
#3B3535
Fail
textarea { "SELECT_PHONE": "…1.25:14.5:1
#000000
#231B1D
Fail
p Supprimer le bon de …1.41:14.5:1
#000000
#26272A
Fail
div Voulez-vous vraiment…1.34:14.5:1
#000000
#242326
Fail
button Non1.57:14.5:1
#000000
#293035
Fail
button Oui1.57:14.5:1
#000000
#293035
Fail
div Félicitations! Vous…1.57:14.5:1
#000000
#293035
Fail
div GRATUIT1.59:14.5:1
#000000
#2A3135
Fail
a Passer au contenu pr…1.74:14.5:1
#000000
#363637
Fail
a Passer au contenu du…1.63:14.5:1
#000000
#313232
Fail
span start animation1.87:14.5:1
#000000
#3B3B3B
Fail
button start1.85:14.5:1
#000000
#3A3A3A
Fail
a France10.86:14.5:1
#FFFFFF
#3D3D3D
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+
Form Accessibility
All 9 controls labeled
PASS
All 9 controls labeled
Info::
9 control(s) properly labeled
9 controls
9 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#localIdinputfr-FRfor/id
#cCodeinputEURfor/id
#apKeyinputtwravuXaWQ60GDtJGr3n5TigSVohRzw8htb71LpFaaPNtffp3uGozquMtX8VRVz5guUw5jriHoJVuolGaTVTDs4qHt6GIzuJfor/id
#transTexttextarea{ "SELECT_PHONE": "Sélectionnez votre modèle de téléphone:", "SELECT_CASE": "Coque standard ou MagSafe ?", "GOT_IT": "OK", "BACK": "<- Retour", "NEXT": "Suivant ->", "CLOSE": "Fermer", "ADD_TO_CART": "Ajouter au panier", "PREVIEW_3D": "Aperçu en 3D", "PLANT_BASED": "Fabriqué avec des matériaux à base de plantes", "TOGGLE_DEVICE": "Changer la couleur de l’appareil", "DEVICE_COLOR": "Couleur de l’appareil", "TOOLTIP_EDIT_COLOR": "Appuyez sur + pour changer la couleur", "TOOLTIP_EDIT_DESIGN": "Modifier votre design", "TOOLTIP_ADD": "Appuyez pour ajouter des photos, des stickers et du texte.", "TOOLTIP_TAP_TO_CONTINUE": "Appuyez ici pour continuer", "TOOLTIP_VIEW_3D": "Visualiser votre design en 3D", "ADD_IMAGE": "Ajouter une image", "ADD_TEXT": "Ajouter du texte", "ADD_STICKERS": "Ajouter des autocollants", "ART_COLLECTIONS": "Collections d’images", "ART_STICKERS": "Collections de stickers", "ART_UPLOAD_BODY": "Parcourez les collections d’images ou téléchargez vos propres photos ou illustrations pour commencer.", "ART_STICKER_UPLOAD_BODY": "Parcourez les collections de stickers ou créez les vôtres", "ART_UPLOAD_OWN": "+ Téléchargez votre visuel", "ART_STICKER_UPLOAD_OWN": "+ Créez votre design", "ART_SELECT_IMAGE": "Sélectionnez une image à ajouter à votre design.", "ART_STICKER_SELECT_IMAGE": "Sélectionnez un sticker à ajouter à votre design.", "ART_USE_SELECTED": "Ajouter cette image", "ART_STICKER_USE_SELECTED": "Ajouter des stickers", "ART_UPLOAD_IMAGE": "Télécharger une image", "ART_EDIT_IMAGE": "Modifier votre image", "ART_STICKER_EDIT_IMAGE": "Créer votre propre sticker", "ART_ADD_THIS": "Ajouter cette image", "ART_STICKER_ADD_THIS": "Ajouter ce sticker", "ART_MY_IMAGES": "Mes images", "ART_MY_STICKERS": "Mes stickers", "ART_ADD_MY_IMAGES": "", "ART_ADD_MY_STICKERS": "", "PICSART_LOADING": "Faire de l’art", "PICSART_REMOVE_BG": "Supprimer l’arrière-plan", "PICSART_EFFECTS": "Effets", "PICSART_TEXTURES": "Textures", "PICSART_TRANSFERS": "Transfert de style", "PICSART_CANCEL": "Annuler", "ATC_CONFIRM_BODY": "Avez-vous terminé votre design personnalisé ?", "ATC_CONFIRM_CONFIRM": "Ajouter au panier", "ATC_CONFIRM_CANCEL": "Pas encore, continuer à personnaliser", "DESIGN_CONFIRM_BODY": "Vous perdrez la progression actuelle de votre design personnalisé", "DESIGN_CONFIRM_CONFIRM": "OK", "DESIGN_CONFIRM_CANCEL": "Non merci, continuer à personnaliser", "CANCEL_BODY": "Vous serez redirigé vers l’écran de sélection des produits et perdrez votre progression actuelle", "CANCEL_CONFIRM": "OK", "CANCEL_CANCEL": "Non merci, continuer à personnaliser", "CASE_INFO_BODY": "Pour une expérience optimale, nous vous recommandons d’utiliser nos poignées et porte-cartes MagSafe avec une coque de téléphone MagSafe.", "CASE_INFO_CONFIRM": "OK", "CASE_INFO_CANCEL": "Personnaliser une coque de téléphone MagSafe", "UPLOAD_IMAGE": "Télécharger une image", "UPLOAD_DROPHINT": "Déposez vos fichiers ici", "UPLOAD_MYDEVICE": "Importer depuis votre appareil", "UPLOAD_INSTAGRAM": "Instagram", "UPLOAD_BROWSE": "Parcourir les fichiers", "UPLOAD_CANCEL": "<- Annuler", "UPLOAD_AUTHENTICATE": "Veuillez vous authentifier avec {'%{pluginName}'} pour sélectionner les fichiers", "UPLOAD_AUTHENTICATEWITH": "Connectez-vous à {'%{pluginName}'}", "UPLOAD_LOADING": "Chargement en cours…", "UPLOAD_LOGOUT": "Déconnexion", "UPLOAD_UPLOADING": "Téléchargement en cours…", "UPLOAD_COMPLETE": "Complet", "UPLOAD_DONE": "Terminé", "UPLOAD_0_FILES": "Télécharger {'%{smart_count}'} image'", "UPLOAD_1_FILES": "Télécharger {'%{smart_count}'} images'", "UPLOAD_2_FILES": "Télécharger {'%{smart_count}'} images'", "UPLOAD_NOTE": "Images jusqu’à 10 Mo uniquement", "UPLOAD_DISCLAIMER": "En continuant, je confirme que j’ai tous les droits nécessaires pour télécharger ce contenu. <a href='' target='_blank'>Plus d'infos</a>", "UPLOAD_DISCLAIMER_LONG": "Je confirme que j'ai les droits nécessaires sur le contenu téléchargé et qu'il n'enfreint aucun droit d'auteur, marque, design ou autre droit de tiers, y compris les droits d'image, et que le contenu est également conforme aux conditions contractuelles de PopSockets. PopSockets se réserve le droit de refuser le contenu non contractuel et d'annuler les commandes. Je suis conscient qu'en cas de violation des conditions générales d'achat, je dois indemniser Popsockets contre les réclamations de tiers conformément à l'article .<a href='https://www.popsockets.fr/pages/terms-and-conditions.html?lang=fr_FR'>10 des Conditions Générales de Vente</a>.<br><br>Les produits personnalisés ne peuvent pas être retournés pour un remboursement, un crédit en magasin ou un remplacement, sauf s'ils sont défectueux.", "AGREE":"Je possède les droits sur cette image.", "FILE_LIMIT_SIZE": "Ce fichier dépasse la taille maximale autorisée (10 Mo)", "IMAGE_SIZE_ERROR": "Les dimensions de l’image, {'{uploaded}'}, sont plus petites que les {'{required}'} requises", "IMAGE_MAX_SIZE_ERROR": "Les dimensions de l’image, {'{uploaded}'}, sont plus élevées que les {'{required}'} autorisées", "LAYER_DELETE": "Supprimer", "EDIT_TIP_SINGLE": "Sélectionnez un calque et faites-le glisser vers la Corbeille pour le supprimer", "EDIT_TIP_MULTIPLE": "Sélectionnez un calque à modifier et placez-le au-dessus ou au-dessous d’un autre calque. Faire glisser vers la Corbeille pour supprimer", "REPLACE_IMAGE": "Changer l’image", "REPLACE_STICKER": "Changer le sticker", "SAVE_CHANGES": "Enregistrer les modifications", "FILE_TYPE_ERROR": "Vous ne pouvez télécharger que : image/*, .jpg, .jpeg, .png, .gif, .heic, .tiff", "LOOKS": "Inserts Looks™️", "LOOKS_INFO": "Inserts graphiques customisables et interchangeables Looks™️", "PLUS_LOOKS": "+ Inserts Looks™️" }for/id
#acj0l3e6lb1itextSaisir un mot clé ou un numéro d'articlearia-label
#acj0l3e6lb1itextSaisir un mot clé ou un numéro d'articlearia-label
#acj0l3e6lb1itextSaisir un mot clé ou un numéro d'articlearia-label
emailIdtextEmailaria-label
#countryListselectcountry select dropdownaria-label
A
Lighthouse Accessibility Audits
Score 91/100 — 4 failing, 29 passed
PASS
91

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Nous livrons à France Bienvenue! Vous pouvez facilement: Achetez dans votre … body.modal-open > div.international > div#globaleWelcomeModal

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
France div.row > div.col-md-10 > div#footer-global-e-section > a#globaleCountrySelect
Conditions générales div.col-md-10 > div.content-asset > div.d-inline-flex > a
Politiques div.col-md-10 > div.content-asset > div.d-inline-flex > a
Propriété intellectuelle div.col-md-10 > div.content-asset > div.d-inline-flex > a
Accessibilité du site Web div.col-md-10 > div.content-asset > div.d-inline-flex > a

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.experience-component > div.photo-tile-container > figure.photo-tile-figure > a.hero-background-link div.experience-component > div.photo-tile-container > figure.photo-tile-figure > a.hero-background-link

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.

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
Acheter la Collection div.hero-text > div.hero-buttons > div.hero-button > a.btn
Aura MagSafe PopCase div.product-tile > div > div.pdp-link > a.link
Fairy Glass Kindle PopCase div.product-tile > div > div.pdp-link > a.link
Mew Metronome Dream MagSafe PopCase div.product-tile > div > div.pdp-link > a.link
Cocoa Umber Petrified MagSafe PopCase div.product-tile > div > div.pdp-link > a.link
Piracy Isn't Dead MagSafe PopCase div.product-tile > div > div.pdp-link > a.link
Mirror Fireheart MagSafe PopCase div.product-tile > div > div.pdp-link > a.link
Fireheart Kindle PopCase div.product-tile > div > div.pdp-link > a.link
Fairyglass MagSafe PopCase div.product-tile > div > div.pdp-link > a.link
Fairy Glass Kindle PopCase div.product-tile > div > div.pdp-link > a.link
Au Revoir Marie MagSafe PopCase div.product-tile > div > div.pdp-link > a.link
Berry Soda MagSafe PopCase div.product-tile > div > div.pdp-link > a.link
The Honey Division MagSafe PopCase div.product-tile > div > div.pdp-link > a.link
S'inscrire form > div.email-input > div.input-group > button.btn
○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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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.
●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
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○`<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