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 4 REVIEW 7 FIX

Link & Button Quality

Action

21 issue(s) across 335 links and 394 buttons

FIX

21 issue(s) across 335 links and 394 buttons

6 link(s) with no accessible text

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

Got: https://alembika.com/collections/slinky-matte-jersey-essentials; https://alembika.com/collections/family; https://blog.alembika.com/just-a-thought/elections/; https://blog.alembika.com/the-edit/all-year-essentials-wardrobe-staples/; https://blog.alembika.com/alembika/alembikawomen/meet-olesya/; https://blog.alembika.com/the-well/fall-fashion-for-a-fun-night-out/

3 link(s) with generic text

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

Got: https://blog.alembika.com/just-a-thought/elections/ ("READ More"); https://blog.alembika.com/the-edit/all-year-essentials-wardrobe-staples/ ("read more"); https://blog.alembika.com/the-well/fall-fashion-for-a-fun-night-out/ ("read more")

19 link(s) open in new tab without warning

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

Got: https://alembika.com/policies/privacy-policy; https://www.instagram.com/alembika_usa/; https://facebook.com/alembikausa; https://www.youtube.com/@alembikausa; https://pinterest.com/alembika_usa; /collections/shop-all-new/products/essential-slinky-flounce-top-caramel; /collections/shop-all-new/products/essential-slinky-flounce-top-teal; /collections/shop-all-new/products/essential-slinky-flounce-top-garnet; /collections/shop-all-new/products/essential-slinky-flounce-top-teal; /collections/shop-all-new/products/essential-slinky-flounce-top-garnet (+9 more)

12 button(s) with no accessible text

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

Got: button.collapsible-trigger (#529 on page); button.collapsible-trigger (#564 on page); button.collapsible-trigger (#574 on page); button.collapsible-trigger (#606 on page); button.collapsible-trigger (#636 on page); button.collapsible-trigger (#658 on page); button.collapsible-trigger (#680 on page); button.collapsible-trigger (#699 on page); button.collapsible-trigger (#731 on page); button.collapsible-trigger (#748 on page) (+2 more)

307 link(s) with descriptive text

335 links

6 empty

3 generic text

19 new tab

12 empty buttons

Element	Text	Issue	Suggested Fix
https://alembika.com/policies/privacy-po…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/alembika_usa/	instagram Instag…	new tab	Add '(opens in new tab)' to text
https://facebook.com/alembikausa	Facebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@alembikausa	YouTube	new tab	Add '(opens in new tab)' to text
https://pinterest.com/alembika_usa	Pinterest	new tab	Add '(opens in new tab)' to text
https://alembika.com/collections/slinky-…	(empty)	empty	Add link text or aria-label
/collections/shop-all-new/products/essen…	Caramel	new tab	Add '(opens in new tab)' to text
/collections/shop-all-new/products/essen…	Teal	new tab	Add '(opens in new tab)' to text
/collections/shop-all-new/products/essen…	Garnet	new tab	Add '(opens in new tab)' to text
/collections/shop-all-new/products/essen…	Teal	new tab	Add '(opens in new tab)' to text
/collections/shop-all-new/products/essen…	Garnet	new tab	Add '(opens in new tab)' to text
/collections/shop-all-new/products/essen…	Caramel	new tab	Add '(opens in new tab)' to text
/collections/shop-all-new/products/essen…	Garnet	new tab	Add '(opens in new tab)' to text
/collections/shop-all-new/products/essen…	Teal	new tab	Add '(opens in new tab)' to text
/collections/shop-all-new/products/essen…	Caramel	new tab	Add '(opens in new tab)' to text
/collections/shop-all-new/products/essen…	Black	new tab	Add '(opens in new tab)' to text
/collections/shop-all-new/products/essen…	Teal	new tab	Add '(opens in new tab)' to text
/collections/shop-all-new/products/essen…	Garnet	new tab	Add '(opens in new tab)' to text
https://alembika.com/collections/family	(empty)	empty	Add link text or aria-label
https://blog.alembika.com/just-a-thought…	(empty)	empty	Add link text or aria-label
https://blog.alembika.com/just-a-thought…	READ More	generic text	Replace with descriptive text
Before: READ More Suggested: Elections
https://blog.alembika.com/the-edit/all-y…	(empty)	empty	Add link text or aria-label
https://blog.alembika.com/the-edit/all-y…	read more	generic text	Replace with descriptive text
Before: read more Suggested: All Year Essentials Wardrobe Staples
https://blog.alembika.com/alembika/alemb…	(empty)	empty	Add link text or aria-label
https://blog.alembika.com/the-well/fall-…	(empty)	empty	Add link text or aria-label
https://blog.alembika.com/the-well/fall-…	read more	generic text	Replace with descriptive text
Before: read more Suggested: Fall Fashion For A Fun Night Out
https://altcha.org/	Visit Altcha.org	new tab	Add '(opens in new tab)' to text
https://altcha.org/	Visit Altcha.org	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

689 links and buttons have descriptive text

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

https://alembika.com/collections/slinky-matte-jersey-essentials; https://alembika.com/collections/family; https://blog.alembika.com/just-a-thought/elections/; https://blog.alembika.com/the-edit/all-year-essentials-wardrobe-staples/; https://blog.alembika.com/alembika/alembikawomen/meet-olesya/; https://blog.alembika.com/the-well/fall-fashion-for-a-fun-night-out/

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.

https://blog.alembika.com/just-a-thought/elections/ ("READ More"); https://blog.alembika.com/the-edit/all-year-essentials-wardrobe-staples/ ("read more"); https://blog.alembika.com/the-well/fall-fashion-for-a-fun-night-out/ ("read 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://alembika.com/policies/privacy-policy; https://www.instagram.com/alembika_usa/; https://facebook.com/alembikausa; https://www.youtube.com/@alembikausa; https://pinterest.com/alembika_usa; /collections/shop-all-new/products/essential-slinky-flounce-top-caramel; /collections/shop-all-new/products/essential-slinky-flounce-top-teal; /collections/shop-all-new/products/essential-slinky-flounce-top-garnet; /collections/shop-all-new/products/essential-slinky-flounce-top-teal; /collections/shop-all-new/products/essential-slinky-flounce-top-garnet (+9 more)

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.collapsible-trigger (#529 on page); button.collapsible-trigger (#564 on page); button.collapsible-trigger (#574 on page); button.collapsible-trigger (#606 on page); button.collapsible-trigger (#636 on page); button.collapsible-trigger (#658 on page); button.collapsible-trigger (#680 on page); button.collapsible-trigger (#699 on page); button.collapsible-trigger (#731 on page); button.collapsible-trigger (#748 on page) (+2 more)

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

Tap Target Adequacy

Action

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

FIX

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

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

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.

Got: #000000

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

18 headings, 2 skip(s)

REVIEW

18 headings, 2 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.

Heading level skipped: H3 → H5 (missing H4)

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

1 empty heading(s)

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

H2 Cookie consent
H2 Currency
H1 Alembika U.S.
H2 Rich Hues. Smooth Moves.
H2 Gather in Style
H2 blueberry
H2 ozai n ku
H2 essentials
H2 trunk shows & pop-up Shops
H2 halloween chic
H2 ALEMBIKA MAGAZINE
H2 Currency
H4 Cart • 0 skipped
H3 Your cart is empty
H3 Essential Slinky Ultimate Top, Garnet
H3 Essential Slinky Flouncy Tee, Caramel
H3 Essential Slinky Flouncy Tee, Teal
H5 (empty)

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

Mobile Keyboard & Autofill

Action

4/6 eligible field(s) missing autocomplete or inputmode

REVIEW

4/6 eligible field(s) missing autocomplete or inputmode

4 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" id="Search">, <input type="email" name="values[email]" id="field-email">, <input type="email" name="email" id="email_01JXG4BQ3264S63CMSCG7HNY9Y">, <input type="email" name="email" id="email_01JXG4BQ3264S63CMSCG7HNY9Y">

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found – Alembika U.S. ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 5 fail WCAG AA

REVIEW

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

15 pass 5 fail WCAG AA

title Designer Clothing | Get Ready for Fall |…

2.48:1

#000000

#474A6F

needs 4.5:1 (normal text)

16px · top of page (header area)

span Manage preferences

2.01:1

#000000

#483F20

needs 4.5:1 (normal text)

16px · above the fold

button Accept

2.04:1

#000000

#494021

needs 4.5:1 (normal text)

16px · above the fold

button Decline

2.08:1

#000000

#4B4122

needs 4.5:1 (normal text)

16px · above the fold

a Skip to content

2.20:1

#000000

#4E4524

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Cookie consent	6.89:1	3.0:1	#000000	#9192A9	Pass
h2 Currency	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 blueberry	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ozai n ku	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 essentials	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 trunk shows & pop-up…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 halloween chic	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ALEMBIKA MAGAZINE	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Currency	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Your cart is empty	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Essential Slinky Ult…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Essential Slinky Flo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Essential Slinky Flo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Designer Clothing \| …	2.48:1	4.5:1	#000000	#474A6F	Fail
p We and our partners,…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Privacy Policy	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Manage preferences	2.01:1	4.5:1	#000000	#483F20	Fail
button Accept	2.04:1	4.5:1	#000000	#494021	Fail
button Decline	2.08:1	4.5:1	#000000	#4B4122	Fail
a Skip to content	2.20:1	4.5:1	#000000	#4E4524	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

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

A+

Alt Text Quality

All 46 images OK

PASS

All 46 images OK

40 decorative image(s) correctly marked

6 image(s) with good alt text

46 images 6 good alt text 40 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 11 controls labeled

PASS

All 11 controls labeled

11 control(s) properly labeled

11 controls

11 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#CartNoteDrawer	textarea	PLEASE NOTE: Sale price does not apply on previously purchased items.	for/id
#Search	search	Search	for/id
#altcha_checkbox_56357576	checkbox	Verified	for/id
#field-firstName	text	Full Name *	for/id
#field-email	email	Email *	for/id
#field-OydqKlfwrq	textarea	What do you need help with? *	for/id
#email_01JXG4BQ3264S63CMSCG7HNY9Y	email	Email	aria-label
#email_01JXG4BQ3264S63CMSCG7HNY9Y	email	Email	aria-label
select	select	Select Essential Slinky Ultimate Top, Garnet variant	aria-label
select	select	Select Essential Slinky Flouncy Tee, Caramel variant	aria-label
select	select	Select Essential Slinky Flouncy Tee, Teal variant	aria-label

A+

Form Input Types

11 form control(s) checked, no type mismatches

PASS

11 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

11 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

Tabindex Anti-Patterns

0 positive, 3 -1-on-focusable

PASS

0 positive, 3 -1-on-focusable

tabindex="-1" on naturally-focusable <input>

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

tabindex="-1" on naturally-focusable <input>

Iframe Accessibility

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

PASS

1/4 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 12 visible text node(s) render at >= 12 CSS pixels

PASS

All 12 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 90/100 — 4 failing, 31 passed

PASS

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

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

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
main#MainContent > div#shopify-section-template--16564985036870__scrolling_text_bNMYYn > div.scrolling-text > div.scrolling-text__inner `main#MainContent > div#shopify-section-template--16564985036870__scrolling_text_bNMYYn > div.scrolling-text > div.scrolling-text__inner`
div.hero-natural--template--16564985036870__slideshow_zTdnQF > div#Slideshow-template--16564985036870__slideshow_zTdnQF > div.slideshow__slide > a.hero__slide-link `div.hero-natural--template--16564985036870__slideshow_zTdnQF > div#Slideshow-template--16564985036870__slideshow_zTdnQF > div.slideshow__slide > a.hero__slide-link`
div.hero-natural--template--16564985036870__slideshow_7AEUye > div#Slideshow-template--16564985036870__slideshow_7AEUye > div.slideshow__slide > a.hero__slide-link `div.hero-natural--template--16564985036870__slideshow_7AEUye > div#Slideshow-template--16564985036870__slideshow_7AEUye > div.slideshow__slide > a.hero__slide-link`
main#MainContent > div#shopify-section-template--16564985036870__scrolling_text_wny8hp > div.scrolling-text > div.scrolling-text__inner `main#MainContent > div#shopify-section-template--16564985036870__scrolling_text_wny8hp > div.scrolling-text > div.scrolling-text__inner`
Shop NOW `div.flex-grid > div.flex-grid__item > div.promo-grid__container > a.promo-grid__slide-link`
shop NOW `div.flex-grid > div.flex-grid__item > div.promo-grid__container > a.promo-grid__slide-link`
shop now `div.flex-grid > div.flex-grid__item > div.promo-grid__container > a.promo-grid__slide-link`
Shop now `div.flex-grid > div.flex-grid__item > div.promo-grid__container > a.promo-grid__slide-link`
Shop This `div.flex-grid > div.flex-grid__item > div.promo-grid__container > a.promo-grid__slide-link`
see events `div.flex-grid > div.flex-grid__item > div.promo-grid__container > a.promo-grid__slide-link`

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
CART • 0 `div.styles_CartPreview__card__ > div > div.upcart-internal-header > h4`

These are opportunities to improve keyboard navigation in your application.

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.grid > div.grid__item > div > a `div.grid > div.grid__item > div > a`
div.grid > div.grid__item > div > a `div.grid > div.grid__item > div > a`
div.grid > div.grid__item > div > a `div.grid > div.grid__item > div > a`
div.grid > div.grid__item > div > a `div.grid > div.grid__item > div > a`

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
Caramel `div > div.pl-swatches-collection > div.pl-swatches-collection__container > a.pl-swatches-collection__link`
Teal `div > div.pl-swatches-collection > div.pl-swatches-collection__container > a.pl-swatches-collection__link`
Garnet `div > div.pl-swatches-collection > div.pl-swatches-collection__container > a.pl-swatches-collection__link`
Teal `div > div.pl-swatches-collection > div.pl-swatches-collection__container > a.pl-swatches-collection__link`
Garnet `div > div.pl-swatches-collection > div.pl-swatches-collection__container > a.pl-swatches-collection__link`
Caramel `div > div.pl-swatches-collection > div.pl-swatches-collection__container > a.pl-swatches-collection__link`
Garnet `div > div.pl-swatches-collection > div.pl-swatches-collection__container > a.pl-swatches-collection__link`
Teal `div > div.pl-swatches-collection > div.pl-swatches-collection__container > a.pl-swatches-collection__link`
Caramel `div > div.pl-swatches-collection > div.pl-swatches-collection__container > a.pl-swatches-collection__link`
Black `div > div.pl-swatches-collection > div.pl-swatches-collection__container > a.pl-swatches-collection__link`
Teal `div > div.pl-swatches-collection > div.pl-swatches-collection__container > a.pl-swatches-collection__link`
Garnet `div > div.pl-swatches-collection > div.pl-swatches-collection__container > a.pl-swatches-collection__link`

These items highlight common accessibility best practices.

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

●Select elements have associated label elements.

●`[accesskey]` values are unique

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

●ARIA attributes are used as specified for the element's role

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

●Elements use only permitted ARIA attributes

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

●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

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

●Elements with visible text labels have matching 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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

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

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

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

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