Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 28 -1-on-focusable

FIX

0 positive, 28 -1-on-focusable

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

F

404 Error Page

Action

HTTP 429, custom page

FIX

HTTP 429, custom page

Unexpected status code: HTTP 429

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

Got: HTTP 429

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

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

D

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.

D

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.

D

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 ✗

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

4 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 4 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

B

Link & Button Quality

522 links, 9 buttons — all OK

REVIEW

522 links, 9 buttons — all OK

1 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/en-es"]

5 link(s) open in new tab without warning

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

Got: https://www.forest-ink.com/policies/privacy-policy; https://www.facebook.com/forestink; https://www.instagram.com/forestinkclothing/; https://www.youtube.com/@forestink; https://www.tiktok.com/@forestinkclothing

516 link(s) with descriptive text

522 links

0 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.forest-ink.com/policies/priv…	learn more about cookies	new tab	Add '(opens in new tab)' to text
/en-es	Forest Ink	img no alt	Add alt attribute to the image
/en-es/collections/asylum	<img class="rimage__image" src…	img no alt	Add alt attribute to the image
/en-es/collections/sedition	<img class="rimage__image" src…	img no alt	Add alt attribute to the image
/en-es/collections/softcore	<img class="rimage__image" src…	img no alt	Add alt attribute to the image
/en-es/collections/vendetta	<img class="rimage__image" src…	img no alt	Add alt attribute to the image
/en-es/collections/vampires-kiss-pt-2	<img class="rimage__image" src…	img no alt	Add alt attribute to the image
/en-es/collections/rogue	<img class="rimage__image" src…	img no alt	Add alt attribute to the image
/en-es/collections/asylum	<img class="rimage__image" src…	img no alt	Add alt attribute to the image
/en-es/collections/sedition	<img class="rimage__image" src…	img no alt	Add alt attribute to the image
/en-es/collections/softcore	<img class="rimage__image" src…	img no alt	Add alt attribute to the image
/en-es/collections/vendetta	<img class="rimage__image" src…	img no alt	Add alt attribute to the image
/en-es/collections/vampires-kiss-pt-2	<img class="rimage__image" src…	img no alt	Add alt attribute to the image
/en-es/collections/rogue	<img class="rimage__image" src…	img no alt	Add alt attribute to the image
/en-es/products/free-gift	Birthday Swim Blind Bag	img no alt	Add alt attribute to the image
/en-es/products/carmilla-one-piece-swims…	Carmilla One Piece Swimsuit	img no alt	Add alt attribute to the image
/en-es/products/josephine-one-piece-swim…	Josephine One Piece Swimsuit	img no alt	Add alt attribute to the image
/en-es/products/nocturne-bikini-top	Nocturne Bikini Top	img no alt	Add alt attribute to the image
/en-es/products/covenant-bikini-bloomers	Covenant Bikini Bloomers	img no alt	Add alt attribute to the image
/en-es/products/moonlight-bikini-bloomer…	Moonlight Bikini Bloomers	img no alt	Add alt attribute to the image
/en-es/products/katherine-bikini-top	Katherine Bikini Top	img no alt	Add alt attribute to the image
/en-es/products/katherine-bikini-bottoms	Katherine Bikini Bottoms	img no alt	Add alt attribute to the image
/en-es/products/strange-passion-swim-ski…	Strange Passion Swim Skirt	img no alt	Add alt attribute to the image
/en-es/products/rosario-swim-skirt	Rosario Swim Skirt	img no alt	Add alt attribute to the image
/en-es/collections/fall-edit-1	October Edit …	img no alt	Add alt attribute to the image
/en-es/collections/restock	Shop Restocks	img no alt	Add alt attribute to the image
/en-es/collections/tops	Shop Tops	img no alt	Add alt attribute to the image
/en-es/collections/dresses	Shop Dresses	img no alt	Add alt attribute to the image
/en-es/collections/swimwear	Shop All Swim	img no alt	Add alt attribute to the image
https://www.facebook.com/forestink	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/forestinkcloth…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@forestink	Youtube	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@forestinkclothin…	Tiktok	new tab	Add '(opens in new tab)' to text

525 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/en-es"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://www.forest-ink.com/policies/privacy-policy; https://www.facebook.com/forestink; https://www.instagram.com/forestinkclothing/; https://www.youtube.com/@forestink; https://www.tiktok.com/@forestinkclothing

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

B

Iframe Accessibility

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

REVIEW

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

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

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.

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.

C

Mobile-Readable Font Sizes

Action

71% of visible text renders at >= 12 CSS px (2 below threshold)

REVIEW

71% of visible text renders at >= 12 CSS px (2 below threshold)

2 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: <div> 10.0px ("Currency"); <button> 10.0px ("Spain (EUR\u00a0€)").

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA 7 pass AA only

h2 October Edit

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

title Forest Ink

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

div Cookie Policy

2.70:1

#000000

on

#5C5048

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)

Element	Ratio	Required	FG	BG	Result
h2 October Edit	1.00:1	3.0:1	#000000	#000000	Fail
title Forest Ink	1.00:1	4.5:1	#000000	#000000	Fail
div Cookie Policy	2.70:1	4.5:1	#000000	#5C5048	Fail
span This website uses co…	6.63:1	4.5:1	#000000	#A18D7F	Pass
a Learn More	6.89:1	4.5:1	#000000	#A49082	Pass
a Got it!	7.08:1	4.5:1	#000000	#A79283	Pass
a Skip to content	7.16:1	4.5:1	#000000	#A79385	Pass
div Shopping cart	6.78:1	4.5:1	#000000	#A28F80	Pass
a Check out	7.02:1	4.5:1	#000000	#A49284	Pass
div Your cart is empty	7.18:1	4.5:1	#000000	#A89385	Pass
a Start shopping	7.16:1	4.5:1	#000000	#A79385	Pass
p Free U.S Shipping on…	6.99:1	4.5:1	#000000	#A69182	Pass
p Free U.S Returns and…	6.86:1	4.5:1	#000000	#A39081	Pass
div Currency	7.24:1	4.5:1	#000000	#A89485	Pass
button Spain (EUR €)	6.94:1	4.5:1	#000000	#A69083	Pass
span Albania	6.71:1	4.5:1	#000000	#A28E7E	Pass
span (ALL L)	7.13:1	4.5:1	#000000	#A69384	Pass
span Algeria	7.17:1	4.5:1	#000000	#A89384	Pass
span (DZD د.ج)	7.28:1	4.5:1	#000000	#AA9485	Pass
span Andorra	7.41:1	4.5:1	#000000	#AC9588	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

6 landmarks

PASS

6 landmarks

<main> landmark present

4 <nav> landmark(s) found

All <nav> elements are properly labeled

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

2 headings

PASS

2 headings

Single H1 present

1 empty heading(s)

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

H1 (empty)
H2 October Edit

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 2 heading(s) have substantive, well-formed text

PASS

All 2 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 30 images OK

PASS

All 30 images OK

29 decorative image(s) correctly marked

1 image(s) with good alt text

30 images 1 good alt text 29 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
q	text	Search Store	aria-label

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "q" should use type="search" (currently type="text")

Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

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

Got: en

A+

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

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 97/100 — 2 failing, 28 passed

PASS

97

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

Names and labels

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.logo-area > div.logo-area__right > div.logo-area__right__inner > a.cart-link `div.logo-area > div.logo-area__right > div.logo-area__right__inner > a.cart-link`
ul.navigation__tier-2 > li.navigation__column > div.menu-promotion > a.menu-promotion__link `ul.navigation__tier-2 > li.navigation__column > div.menu-promotion > a.menu-promotion__link`
ul.navigation__tier-2 > li.navigation__column > div.menu-promotion > a.menu-promotion__link `ul.navigation__tier-2 > li.navigation__column > div.menu-promotion > a.menu-promotion__link`
ul.navigation__tier-2 > li.navigation__column > div.menu-promotion > a.menu-promotion__link `ul.navigation__tier-2 > li.navigation__column > div.menu-promotion > a.menu-promotion__link`
ul.navigation__tier-2 > li.navigation__column > div.menu-promotion > a.menu-promotion__link `ul.navigation__tier-2 > li.navigation__column > div.menu-promotion > a.menu-promotion__link`
ul.navigation__tier-2 > li.navigation__column > div.menu-promotion > a.menu-promotion__link `ul.navigation__tier-2 > li.navigation__column > div.menu-promotion > a.menu-promotion__link`
ul.navigation__tier-2 > li.navigation__column > div.menu-promotion > a.menu-promotion__link `ul.navigation__tier-2 > li.navigation__column > div.menu-promotion > a.menu-promotion__link`
div#section-id-template--23914184638699__slideshow_DJwwF4 > div.slideshow > div.slide > a.image-overlay__image-link `div#section-id-template--23914184638699__slideshow_DJwwF4 > div.slideshow > div.slide > a.image-overlay__image-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
Got it! `body.template-index > div.cc-window > div.cc-compliance > a#ba-cookie-dismiss`

○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

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

●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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●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

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

○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

○Form elements have associated labels

○Links are distinguishable without relying on color.

○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

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