Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 5 REVIEW 7 FIX

Form Accessibility

Action

8 of 47 controls have issues

FIX

8 of 47 controls have issues

4 control(s) without accessible label

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

Got: <select>; <select>; <select>; <select>

4 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text" name="q_final_name" id="q_final_name">; <input type="email" name="q_final_email" id="q_final_email">; <input type="tel" name="q_final_phone" id="q_final_phone">; <input type="text" name="q_final_verify_code" id="q_final_verify_code">

39 control(s) properly labeled

47 controls

39 labeled

4 placeholder only

4 unlabeled

Control	Type	Label	Method
#osano-cm-dialog-toggle--category_MARKETING	checkbox		none
#osano-cm-dialog-toggle--category_PERSONALIZATION	checkbox		none
#osano-cm-dialog-toggle--category_ANALYTICS	checkbox		none
#WyzeSearch-In-Modal	search	Search	for/id
q_property_type	radio		none
q_property_type	radio		none
q_property_type	radio		none
q_home_size	radio		none
q_home_size	radio		none
q_home_size	radio		none
q_home_size	radio		none
q_exterior_doors	radio		none
q_exterior_doors	radio		none
q_exterior_doors	radio		none
q_exterior_doors	radio		none
q_entry_point	radio		none
q_entry_point	radio		none
q_entry_point	radio		none
q_entry_point	radio		none
q_garage	radio		none
q_garage	radio		none
q_garage	radio		none
q_garage	radio		none
q_backyard	radio		none
q_backyard	radio		none
q_backyard	radio		none
q_backyard	radio		none
q_concerns	checkbox		none
q_concerns	checkbox		none
q_concerns	checkbox		none
q_concerns	checkbox		none
q_concerns	checkbox		none
q_concerns	checkbox		none
q_concerns	checkbox		none
q_concerns	checkbox		none
q_monitoring	radio		none
q_monitoring	radio		none
q_monitoring	radio		none
#NewsletterForm--sections--17063379468450__footer	email	Email	for/id
#q_final_email	email	(Your email address *)	placeholder only
#q_final_phone	tel	(Phone number)	placeholder only
#q_final_verify_code	text	(Enter code sent to your phone)	placeholder only
#q_final_name	text	(Your name *)	placeholder only
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none

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

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Link & Button Quality

Action

4 issue(s) across 186 links and 48 buttons

FIX

4 issue(s) across 186 links and 48 buttons

1 link(s) with no accessible text

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

Got: https://www.wyze.com/pages/service-plans

1 link(s) with generic text

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

Got: https://manage.kmail-lists.com/subscriptions/unsubscribe?a=Yb5ave&g=RAmEVq ("here")

13 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="/products/wyze-battery-cam-pro"]; a[href="/products/wyze-bulb-cam"]; a[href="/products/wyze-battery-video-doorbell"]; a[href="/products/wyze-lock-bolt-v2"]; a[href="/products/wyze-bulb-color"]; a[href="/products/wyze-cordless-vacuum-s"]; a[href="/products/wyze-scale-ultra"]; a[href="/products/wyze-scale-x"]; a[href="/products/wyze-headphones"]; a[href="/products/wyze-battery-cam-pro-ca"] (+3 more)

13 link(s) open in new tab without warning

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

Got: https://www.wyze.com/policies/privacy-policy; https://support.wyze.com/hc/en-us; https://account.wyze.com?locale=en&region_country=US; https://my.wyze.com/live; https://support.wyze.com/hc/en-us; https://apps.apple.com/us/app/wyze-make-your-home-smarter/id1288415553; https://play.google.com/store/apps/details?id=com.hualai; https://www.tiktok.com/@wyze; https://www.youtube.com/c/WyzeCam; https://twitter.com/WyzeCam (+3 more)

2 button(s) with no accessible text

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

Got: button.wyze-header-meganav__mobile-toggle (#262 on page); button.wyze-chat-banner__trigger (#783 on page)

158 link(s) with descriptive text

186 links

1 empty

1 generic text

13 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://www.wyze.com/policies/privacy-po…	Privacy Policy	new tab	Add '(opens in new tab)' to text
/products/wyze-battery-cam-pro	Bestseller …	img no alt	Add alt attribute to the image
/products/wyze-bulb-cam	Design Award Winner 2025 …	img no alt	Add alt attribute to the image
/products/wyze-battery-video-doorbell	Wyze Battery Video Doorbell …	img no alt	Add alt attribute to the image
/products/wyze-lock-bolt-v2	NEW …	img no alt	Add alt attribute to the image
/products/wyze-bulb-color	Wyze Bulb Color …	img no alt	Add alt attribute to the image
/products/wyze-cordless-vacuum-s	Wyze Cordless Vacuum S …	img no alt	Add alt attribute to the image
/products/wyze-scale-ultra	Wyze Scale Ultra …	img no alt	Add alt attribute to the image
/products/wyze-scale-x	Wyze Scale X …	img no alt	Add alt attribute to the image
/products/wyze-headphones	Wyze Noise-Cancelling Headphon…	img no alt	Add alt attribute to the image
https://www.wyze.com/pages/service-plans	(empty)	empty	Add link text or aria-label
https://support.wyze.com/hc/en-us	Help	new tab	Add '(opens in new tab)' to text
https://account.wyze.com?locale=en&regio…	Login to your Wyze account	new tab	Add '(opens in new tab)' to text
https://my.wyze.com/live	View my camera live streams wi…	new tab	Add '(opens in new tab)' to text
/products/wyze-battery-cam-pro-ca	Battery Powered Cam — Wyze B…	img no alt	Add alt attribute to the image
/products/wyze-duo-cam-doorbell	2k Dual Cameras — Wyze Duo D…	img no alt	Add alt attribute to the image
/products/wyze-palm-lock	4.5 Rating on Amazon	img no alt	Add alt attribute to the image
/products/wyze-palm-lock	Fast Palm Reader — Wyze Palm…	img no alt	Add alt attribute to the image
https://support.wyze.com/hc/en-us	FAQ & help center	new tab	Add '(opens in new tab)' to text
https://manage.kmail-lists.com/subscript…	here	generic text	Replace with descriptive text
Before: here Suggested: Unsubscribe?A=Yb5ave&G=Ramevq
https://apps.apple.com/us/app/wyze-make-…	Wyze on the App Store	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Wyze on the Play Store	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@wyze	TikTok	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/c/WyzeCam	YouTube	new tab	Add '(opens in new tab)' to text
https://twitter.com/WyzeCam	Twitter	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/WyzeCam	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/wyze/	Instagram	new tab	Add '(opens in new tab)' to text
https://discord.gg/wyze	Discord	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

204 links and buttons have descriptive text

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

https://www.wyze.com/pages/service-plans

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://manage.kmail-lists.com/subscriptions/unsubscribe?a=Yb5ave&g=RAmEVq ("here")

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

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

a[href="/products/wyze-battery-cam-pro"]; a[href="/products/wyze-bulb-cam"]; a[href="/products/wyze-battery-video-doorbell"]; a[href="/products/wyze-lock-bolt-v2"]; a[href="/products/wyze-bulb-color"]; a[href="/products/wyze-cordless-vacuum-s"]; a[href="/products/wyze-scale-ultra"]; a[href="/products/wyze-scale-x"]; a[href="/products/wyze-headphones"]; a[href="/products/wyze-battery-cam-pro-ca"] (+3 more)

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.wyze.com/policies/privacy-policy; https://support.wyze.com/hc/en-us; https://account.wyze.com?locale=en&region_country=US; https://my.wyze.com/live; https://support.wyze.com/hc/en-us; https://apps.apple.com/us/app/wyze-make-your-home-smarter/id1288415553; https://play.google.com/store/apps/details?id=com.hualai; https://www.tiktok.com/@wyze; https://www.youtube.com/c/WyzeCam; https://twitter.com/WyzeCam (+3 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.wyze-header-meganav__mobile-toggle (#262 on page); button.wyze-chat-banner__trigger (#783 on page)

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

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.

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

60 headings, 1 skip(s)

REVIEW

60 headings, 1 skip(s)

Multiple H1 headings (2 found)

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

Heading level skipped: H1 → H3 (missing H2)

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

2 empty heading(s)

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

H1 (empty)
H3 Cameras skipped
H3 Trusted by 10+ million households
H4 Wyze Battery Cam Pro
H4 Wyze Bulb Cam
H4 Wyze Battery Video Doorbell
H3 Smart Home
H3 Smart Homes Choose Wyze
H4 Wyze Lock Bolt v2
H4 Wyze Bulb Color
H4 Wyze Cordless Vacuum S
H3 Lifestyle
H3 Making great technology accessible to everyone
H4 Wyze Scale Ultra
H4 Wyze Scale X
H4 Wyze Noise-Cancelling Headphones
H3 AI-powered security
H3 Back
H2 Country/region - Language
H1 Wyze Window Cam duplicate H1
H2 Great technology accessible to everyone
H3 Battery Cam Pro
H3 Video Doorbell
H3 Bulb Cam
H3 Lock Bolt v2
H3 Duo Cam Pan
H3 Palm Lock
H3 Ultra Bodyscan
H3 Cam v4
H2 Hold on, we're preparing your security system...
H2 Your personalized security system is ready!
H2 Do you want expert tips for setting up your security system?
H2 See our AI chat agent for your results!
H2 Build your smarter home.
H2 Security Cameras
H2 Video Doorbells
H2 Smart Locks
H2 Smart Lighting
H2 Trusted by over 12 million households
H3 Battery Powered Cam
H3 2k Dual Cameras
H3 Fast Palm Reader
H2 Security Cameras
H2 Smart Homes
H2 (empty)
H2 Health & Lifestyle
H2 Home Monitoring
H2 Trusted by over 12 million households
H2 #1
H2 5,000+
H2 12 million+
H2 Why Wyze?
H2 Support
H2 Get involved
H2 Company
H2 Subscribe to our newsletter
H2 My cart
H3 Popular Categories
H2 In people's carts right now...
H2 Popular add-ons

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

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

Alt Text Quality

Action

9 of 69 images have issues

REVIEW

9 of 69 images have issues

9 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

33 decorative image(s) correctly marked

27 image(s) with good alt text

69 images 27 good alt text 33 decorative 9 missing

Issue	Count
missing	9 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

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 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Wyze Window Cam

1.29:1

#000000

#202023

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Country/region - Language

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Great technology accessible to everyone

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Hold on, we're preparing your security s…

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Your personalized security system is rea…

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Do you want expert tips for setting up y…

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

h2 See our AI chat agent for your results!

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Build your smarter home.

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Security Cameras

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Video Doorbells

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Smart Locks

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Smart Lighting

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Trusted by over 12 million households

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Trusted by over

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

h2 12 million households

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

h2 5,000+

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

h2 12 million+

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Why Wyze?

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Support

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Get involved

1.29:1

#000000

#202023

needs 3.0:1 (large text)

24px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Wyze Window Cam	1.29:1	3.0:1	#000000	#202023	Fail
h2 Country/region - Lan…	1.29:1	3.0:1	#000000	#202023	Fail
h2 Great technology acc…	1.29:1	3.0:1	#000000	#202023	Fail
h2 Hold on, we're prepa…	1.29:1	3.0:1	#000000	#202023	Fail
h2 Your personalized se…	1.29:1	3.0:1	#000000	#202023	Fail
h2 Do you want expert t…	1.29:1	3.0:1	#000000	#202023	Fail
h2 See our AI chat agen…	1.29:1	3.0:1	#000000	#202023	Fail
h2 Build your smarter h…	1.29:1	3.0:1	#000000	#202023	Fail
h2 Security Cameras	1.29:1	3.0:1	#000000	#202023	Fail
h2 Video Doorbells	1.29:1	3.0:1	#000000	#202023	Fail
h2 Smart Locks	1.29:1	3.0:1	#000000	#202023	Fail
h2 Smart Lighting	1.29:1	3.0:1	#000000	#202023	Fail
h2 Trusted by over 12 m…	1.29:1	3.0:1	#000000	#202023	Fail
h2 Trusted by over	1.29:1	3.0:1	#000000	#202023	Fail
h2 12 million household…	1.29:1	3.0:1	#000000	#202023	Fail
h2 5,000+	1.29:1	3.0:1	#000000	#202023	Fail
h2 12 million+	1.29:1	3.0:1	#000000	#202023	Fail
h2 Why Wyze?	1.29:1	3.0:1	#000000	#202023	Fail
h2 Support	1.29:1	3.0:1	#000000	#202023	Fail
h2 Get involved	1.29:1	3.0:1	#000000	#202023	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.

Lighthouse Accessibility Audits

Score 85/100 — 4 failing, 27 passed

REVIEW

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#shopify-section-sections--17063379370146__wyze_header_meganav_3UKYnR > div.wyze-header-meganav-wrapper > header.header > button.wyze-header-meganav__mobile-toggle `div#shopify-section-sections--17063379370146__wyze_header_meganav_3UKYnR > div.wyze-header-meganav-wrapper > header.header > button.wyze-header-meganav__mobile-toggle`
div.relative > div.flex > div.livex-1qtyrp3 > button.p-1 `div.relative > div.flex > div.livex-1qtyrp3 > button.p-1`
div#livex-regular-header-container > div#livex-regular-header-top-container > div.livex-1i49dfn > button.mantine-focus-auto `div#livex-regular-header-container > div#livex-regular-header-top-container > div.livex-1i49dfn > button.mantine-focus-auto`
div#livex-regular-header-container > div#livex-regular-header-top-container > div.livex-1i49dfn > button#mantine-xhmb0snr4-target `div#livex-regular-header-container > div#livex-regular-header-top-container > div.livex-1i49dfn > button#mantine-xhmb0snr4-target`

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.two-image-banner > div.two-image-banner__banner > div.media > img.two-image-banner__image `div.two-image-banner > div.two-image-banner__banner > div.media > img.two-image-banner__image`
div.two-image-banner > div.two-image-banner__banner > div.media > img.two-image-banner__image `div.two-image-banner > div.two-image-banner__banner > div.media > img.two-image-banner__image`
div.two-image-banner > div.two-image-banner__banner > div.media > img.two-image-banner__image `div.two-image-banner > div.two-image-banner__banner > div.media > img.two-image-banner__image`
div.two-image-banner > div.two-image-banner__banner > div.media > img.two-image-banner__image `div.two-image-banner > div.two-image-banner__banner > div.media > img.two-image-banner__image`
div#DuoImages-template--17063387103394__18b5fbe0-679c-41a7-9244-a71584a8b612 > div.duoImages__main-container > div.duoImages__media > img.duoImages__image `div#DuoImages-template--17063387103394__18b5fbe0-679c-41a7-9244-a71584a8b612 > div.duoImages__main-container > div.duoImages__media > img.duoImages__image`
div.duoImages__card-container > div.duoImages__card > div.duoImages__media > img.duoImages__image `div.duoImages__card-container > div.duoImages__card > div.duoImages__media > img.duoImages__image`
div#DuoImages-template--17063387103394__639c0989-309c-4ad0-98c9-3760b2474797 > div.duoImages__main-container > div.duoImages__media > img.duoImages__image `div#DuoImages-template--17063387103394__639c0989-309c-4ad0-98c9-3760b2474797 > div.duoImages__main-container > div.duoImages__media > img.duoImages__image`
div.duoImages__card-container > div.duoImages__card > div.duoImages__media > img.duoImages__image `div.duoImages__card-container > div.duoImages__card > div.duoImages__media > img.duoImages__image`
div#livex-regular-header-top-container > div#livex-logo-agent-name-container > div#livex-logo-container > img#livex-logo-image `div#livex-regular-header-top-container > div#livex-logo-agent-name-container > div#livex-logo-container > img#livex-logo-image`

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.kaxsdc > iframe#ibody `body.kaxsdc > iframe#ibody`

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
Go to slide 1 `div#splide01 > ul.splide__pagination > li > button.splide__pagination__page`
Go to slide 2 `div#splide01 > ul.splide__pagination > li > button.splide__pagination__page`
Go to slide 3 `div#splide01 > ul.splide__pagination > li > button.splide__pagination__page`

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

●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

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●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

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

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○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

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

A+

Landmark Structure

13 landmarks

PASS

13 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.