Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 18 -1-on-focusable

FIX

0 positive, 18 -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.)

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

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: #171717

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.

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

6 navigation landmark(s) detected

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 6 <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

Mobile-Readable Font Sizes

91% of visible text renders at >= 12 CSS px (3 below threshold)

REVIEW

91% of visible text renders at >= 12 CSS px (3 below threshold)

3 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> 11.0px ("Pioneers of Smart Wallets"); <span> 10.0px ("Est. 2024"); <div> 10.0px ("Built Into Every Wallet").

B

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found – Ventro ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA

h2 Your cart is currently empty.

1.06:1

#000000

on

#090B0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What is VentroTap™?

1.06:1

#000000

on

#090B0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Genesis vs Owen

1.06:1

#000000

on

#090B0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Laser Engraving,

1.06:1

#000000

on

#090B0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Done In-House

1.06:1

#000000

on

#090B0A

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Tap Your Wallet

1.06:1

#000000

on

#090B0A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Profile Opens Instantly

1.06:1

#000000

on

#090B0A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Contact Shared

1.06:1

#000000

on

#090B0A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Choose Your Wallet

1.06:1

#000000

on

#090B0A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Add Your Message

1.06:1

#000000

on

#090B0A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 We Engrave It

1.06:1

#000000

on

#090B0A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Delivered To You

1.06:1

#000000

on

#090B0A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Support

1.06:1

#000000

on

#090B0A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Support

1.06:1

#000000

on

#090B0A

needs 3.0:1 (large text)

19px · bottom of viewport

title Ventro | Premium Smart Wallets with NFC …

1.27:1

#000000

on

#1F1F1F

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.27:1

#000000

on

#1F1F1F

needs 4.5:1 (normal text)

16px · top of page (header area)

button Wallets

4.11:1

#000000

on

#6E6E6C

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

span Bags

1.09:1

#000000

on

#0E0E0C

needs 4.5:1 (normal text)

16px · above the fold

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 Your cart is current…	1.06:1	3.0:1	#000000	#090B0A	Fail
h2 What is VentroTap™…	1.06:1	3.0:1	#000000	#090B0A	Fail
h2 Genesis vs Owen	1.06:1	3.0:1	#000000	#090B0A	Fail
h2 Laser Engraving,	1.06:1	3.0:1	#000000	#090B0A	Fail
h2 Done In-House	1.06:1	3.0:1	#000000	#090B0A	Fail
h3 Tap Your Wallet	1.06:1	3.0:1	#000000	#090B0A	Fail
h3 Profile Opens Instan…	1.06:1	3.0:1	#000000	#090B0A	Fail
h3 Contact Shared	1.06:1	3.0:1	#000000	#090B0A	Fail
h3 Choose Your Wallet	1.06:1	3.0:1	#000000	#090B0A	Fail
h3 Add Your Message	1.06:1	3.0:1	#000000	#090B0A	Fail
h3 We Engrave It	1.06:1	3.0:1	#000000	#090B0A	Fail
h3 Delivered To You	1.06:1	3.0:1	#000000	#090B0A	Fail
h3 Support	1.06:1	3.0:1	#000000	#090B0A	Fail
h3 Support	1.06:1	3.0:1	#000000	#090B0A	Fail
title Ventro \| Premium Sma…	1.27:1	4.5:1	#000000	#1F1F1F	Fail
a Skip to content	1.27:1	4.5:1	#000000	#1F1F1F	Fail
em Free name engraving …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Wallets	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Wallets	4.11:1	4.5:1	#000000	#6E6E6C	Fail
span Bags	1.09:1	4.5:1	#000000	#0E0E0C	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

11 landmarks

PASS

11 landmarks

<main> landmark present

6 <nav> landmark(s) found

4 of 6 <nav> elements are unlabeled

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

Skip navigation link present

Page Structure — as a screen reader sees it

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

24 headings

PASS

24 headings

Multiple H1 headings (2 found)

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

1 empty heading(s)

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

H1 Ventro
H2 Your cart is currently empty.
H1 Where Craft Meets Innovation duplicate H1
H2 What is VentroTap™?
H3 Tap Your Wallet
H3 Profile Opens Instantly
H3 Contact Shared
H2 Genesis Series
H2 Genesis vs Owen
H2 Owen Series
H2 Heritage Series
H2 Porter Men's
H2 Porter Women's
H2 Smart Additions
H2 Laser Engraving,Done In-House
H3 Choose Your Wallet
H3 Add Your Message
H3 We Engrave It
H3 Delivered To You
H2 Our Corporate Partners
H2 Thousands of Verified Reviews
H2 (empty)
H3 Support
H3 Support

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

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

PASS

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

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

A+

Alt Text Quality

All 173 images OK

PASS

All 173 images OK

2 image(s) with alt text over 125 characters

84 decorative image(s) correctly marked

87 image(s) with good alt text

173 images 87 good alt text 84 decorative

Issue	Count
too long	2 image(s)

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#CartNoteForm-sections--22635524784405__cart-drawer	textarea	Order note	for/id
#CartDiscountForm-sections--22635524784405__cart-drawer	text	Discount code	for/id
#SearchFormInput-sections--22635524784405__search-drawer	search	Search	for/id

A

Link & Button Quality

172 links, 93 buttons — all OK

PASS

172 links, 93 buttons — all OK

40 link(s) open in new tab without warning

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

Got: /pages/ventrotapdetails; /pages/ventro-warranty-policy; https://ventro.com.bd/pages/our-engravings-custom-laser-engraving-by-ventro; /pages/ventro-warranty-policy; https://ventro.com.bd/pages/our-engravings-custom-laser-engraving-by-ventro; /pages/ventrotapdetails; /pages/ventro-warranty-policy; https://ventro.com.bd/pages/our-engravings-custom-laser-engraving-by-ventro; /pages/ventro-warranty-policy; /pages/ventro-warranty-policy (+30 more)

132 link(s) with descriptive text

172 links

0 empty

0 generic text

40 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/pages/ventrotapdetails	VentroTap™ Enabled	new tab	Add '(opens in new tab)' to text
/pages/ventro-warranty-policy	3 Years Warranty	new tab	Add '(opens in new tab)' to text
https://ventro.com.bd/pages/our-engravin…	Personalization Options	new tab	Add '(opens in new tab)' to text
/pages/ventro-warranty-policy	1 Year Warranty	new tab	Add '(opens in new tab)' to text
https://ventro.com.bd/pages/our-engravin…	Personalization Options	new tab	Add '(opens in new tab)' to text
/pages/ventrotapdetails	VentroTap™ Enabled	new tab	Add '(opens in new tab)' to text
/pages/ventro-warranty-policy	3 Years Warranty	new tab	Add '(opens in new tab)' to text
https://ventro.com.bd/pages/our-engravin…	Personalization Options	new tab	Add '(opens in new tab)' to text
/pages/ventro-warranty-policy	1 or 3 Years Warranty	new tab	Add '(opens in new tab)' to text
/pages/ventro-warranty-policy	1 Years Warranty	new tab	Add '(opens in new tab)' to text
/	Ventro	new tab	Add '(opens in new tab)' to text
/products/owen-classic-microfiber-leathe…	Owen Classic \| Microfiber Leat…	new tab	Add '(opens in new tab)' to text
/products/porter-tote	Porter Tote \| A work bag for t…	new tab	Add '(opens in new tab)' to text
/products/owen-classic-microfiber-leathe…	Owen Classic \| Microfiber Leat…	new tab	Add '(opens in new tab)' to text
/products/genesis-elan	Genesis Élan \| Textured Full …	new tab	Add '(opens in new tab)' to text
/products/heritage-artisan	Heritage Artisan \| Handcrafted…	new tab	Add '(opens in new tab)' to text
/products/genesis-artisan	Genesis Artisan \| Handcrafted …	new tab	Add '(opens in new tab)' to text
/products/genesis-core	Genesis Core \| Full Grain Leat…	new tab	Add '(opens in new tab)' to text
/products/genesis-core	Genesis Core \| Full Grain Leat…	new tab	Add '(opens in new tab)' to text
/products/genesis-artisan	Genesis Artisan \| Handcrafted …	new tab	Add '(opens in new tab)' to text
/products/genesis-elan	Genesis Élan \| Textured Full …	new tab	Add '(opens in new tab)' to text
/products/genesis	VentroTap Activation	new tab	Add '(opens in new tab)' to text
/	Ventro	new tab	Add '(opens in new tab)' to text
/products/genesis-artisan	Genesis Artisan \| Handcrafted …	new tab	Add '(opens in new tab)' to text
/	Ventro	new tab	Add '(opens in new tab)' to text
/products/genesis-elan	Genesis Élan \| Textured Full …	new tab	Add '(opens in new tab)' to text
/products/genesis-artisan	Genesis Artisan \| Handcrafted …	new tab	Add '(opens in new tab)' to text
/	Ventro	new tab	Add '(opens in new tab)' to text
/products/tracker	Wallet Tracker \| Apple & Andro…	new tab	Add '(opens in new tab)' to text
/products/genesis-elan	Genesis Élan \| Textured Full …	new tab	Add '(opens in new tab)' to text
/	Ventro	new tab	Add '(opens in new tab)' to text
/products/mepc-customization-charge	Customization charge	new tab	Add '(opens in new tab)' to text
/products/genesis-artisan	Genesis Artisan \| Handcrafted …	new tab	Add '(opens in new tab)' to text
/products/genesis-elan	Genesis Élan \| Textured Full …	new tab	Add '(opens in new tab)' to text
/products/genesis-artisan	Genesis Artisan \| Handcrafted …	new tab	Add '(opens in new tab)' to text
/products/genesis-core	Genesis Core \| Full Grain Leat…	new tab	Add '(opens in new tab)' to text
/products/genesis-artisan	Genesis Artisan \| Handcrafted …	new tab	Add '(opens in new tab)' to text
/products/owen-classic-microfiber-leathe…	Owen Classic \| Microfiber Leat…	new tab	Add '(opens in new tab)' to text
/products/genesis-core	Genesis Core \| Full Grain Leat…	new tab	Add '(opens in new tab)' to text
/products/mepc-customization-charge	Customization charge	new tab	Add '(opens in new tab)' to text

225 links and buttons have descriptive text

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

/pages/ventrotapdetails; /pages/ventro-warranty-policy; https://ventro.com.bd/pages/our-engravings-custom-laser-engraving-by-ventro; /pages/ventro-warranty-policy; https://ventro.com.bd/pages/our-engravings-custom-laser-engraving-by-ventro; /pages/ventrotapdetails; /pages/ventro-warranty-policy; https://ventro.com.bd/pages/our-engravings-custom-laser-engraving-by-ventro; /pages/ventro-warranty-policy; /pages/ventro-warranty-policy (+30 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

A+

Form Input Types

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

3 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

Iframe Accessibility

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

PASS

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

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

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 1 failing, 31 passed

PASS

100

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.

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
Shop Best Sellers `div#root > div.z-composer > div.fixed > div.entrypoint-shadow`

○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

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

●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

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

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

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

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` have 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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.