Browse & Analyze

Browse recent website audits and performance trends

Explore technology stacks detected across the web

Side-by-side technology comparisons and market share

Curated technology stacks and the sites that use them

Editorial deep-dives on the state of web performance

Browse and download favicons from analyzed websites

Learn

Common questions about BeaverCheck scores and checks

How we calculate scores across 100+ checks

The story behind BeaverCheck and the team

Practical guides to fix common web performance issues

Migration Guides

Step-by-step guides for moving between web technologies

Definitions for performance, SEO, and web platform terms

Contrast Checker

Check WCAG color contrast ratios between any two colors

Inspect HTTP response headers for any URL

Analyze SSL/TLS certificate details and chain

Look up DNS records for any domain

Redirect Checker

Trace the full redirect chain for any URL

Real-user INP and Core Web Vitals from Google's Chrome UX Report.

RESTful API for programmatic website audits

Embed an auto-updating health score badge on your site

https://BeyondCarat.com

Accessibility

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

SCORE

75

GRADE

C

FIX

7

REVIEW

3

PASS

14

INFO

0

Checks

24

14 PASS 3 REVIEW 7 FIX

D

Mobile Keyboard & Autofill

Action

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

FIX

4/5 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-In-Modal-1">, <input type="search" name="q" id="Search-In-Modal">, <input type="email" name="contact[email]">, <input type="email" name="email" id="email_01KPJ5ME9EWCDM1NPF2TJ2EJT2">

D

Tabindex Anti-Patterns

Action

0 positive, 24 -1-on-focusable

FIX

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

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

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 ✗

B

Iframe Accessibility

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

REVIEW

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

<iframe> missing title attribute (src="https://beyondcarat.com/web-pixels@81a24193wb0bf602apf85b30fcm71c6b379/custom/w…")

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.

<iframe> missing title attribute (src="https://beyondcarat.com/web-pixels@81a24193wb0bf602apf85b30fcm71c6b379/custom/w…")

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.

<iframe> missing title attribute (src="")

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

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

B

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 20 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Country/region	4.21:1	3.0:1	#000000	#726F6C	Pass
h2 Language	4.21:1	3.0:1	#000000	#726F6C	Pass
h2 Country/region	4.21:1	3.0:1	#000000	#726F6C	Pass
h2 Shop By Shape	4.21:1	3.0:1	#000000	#726F6C	Pass
h2 Engagement Ring	4.21:1	3.0:1	#000000	#726F6C	Pass
h2 Why Choose Us	4.21:1	3.0:1	#000000	#726F6C	Pass
h2 Design Your Dream Ri…	4.21:1	3.0:1	#000000	#726F6C	Pass
h2 Explore Collection	4.21:1	3.0:1	#000000	#726F6C	Pass
h2 Featured collection	4.21:1	3.0:1	#000000	#726F6C	Pass
h2 IGI Certified Lab-Gr…	4.21:1	3.0:1	#000000	#726F6C	Pass
h2 Shop By Style	4.21:1	3.0:1	#000000	#726F6C	Pass
h2 What our customers s…	4.21:1	3.0:1	#000000	#726F6C	Pass
h2 Frequently Asked Que…	4.21:1	3.0:1	#000000	#726F6C	Pass
h3 Round	4.21:1	3.0:1	#000000	#726F6C	Pass
h3 Oval	4.21:1	3.0:1	#000000	#726F6C	Pass
h3 Pear	4.21:1	3.0:1	#000000	#726F6C	Pass
h3 Marquise	4.21:1	3.0:1	#000000	#726F6C	Pass
h3 Cushion	4.21:1	3.0:1	#000000	#726F6C	Pass
h3 Emerald	4.21:1	3.0:1	#000000	#726F6C	Pass
h3 Radiant	4.21:1	3.0:1	#000000	#726F6C	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

11 landmarks

PASS

11 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <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

70 headings

PASS

70 headings

Single H1 present

1 empty heading(s)

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

H2 Country/region
H2 Language
H1 (empty)
H2 Country/region
H2 Shop By Shape
H3 Round
H3 Oval
H3 Pear
H3 Marquise
H3 Cushion
H3 Emerald
H3 Radiant
H3 Princess
H3 Asscher
H3 Heart
H2 Engagement Ring
H3 Serena Blossom Solitaire Round Diamond Engagement Ring in White Gold
H3 Serena Blossom Solitaire Round Diamond Engagement Ring in White Gold
H3 Twisted Side Stone Princess Diamond Engagement Ring in Platinum
H3 Twisted Side Stone Princess Diamond Engagement Ring in Platinum
H3 Grace Three Stone Round Diamond Engagement Ring in Platinum
H3 Grace Three Stone Round Diamond Engagement Ring in Platinum
H3 Flora Guardian Solitaire Oval Diamond Engagement Ring in Yellow Gold
H3 Flora Guardian Solitaire Oval Diamond Engagement Ring in Yellow Gold
H2 Why Choose Us
H2 Design Your Dream Ring
H2 Explore Collection
H3 Engagement Rings
H3 Engagement Rings
H3 Diamond Earrings
H3 Diamond Earrings
H3 Tennis Bracelets
H3 Tennis Bracelets
H3 Diamond Necklace
H3 Diamond Necklace
H2 Featured collection
H3 Grace Three Stone Round Diamond Engagement Ring in Platinum
H3 Grace Three Stone Round Diamond Engagement Ring in Platinum
H3 Twisted Side Stone Princess Diamond Engagement Ring in Platinum
H3 Twisted Side Stone Princess Diamond Engagement Ring in Platinum
H3 Isabella Legacy Side Stone Marquise Diamond Engagement Ring in Platinum
H3 Isabella Legacy Side Stone Marquise Diamond Engagement Ring in Platinum
H3 Isabella Legacy Side Stone Asscher Diamond Engagement Ring in Platinum
H3 Isabella Legacy Side Stone Asscher Diamond Engagement Ring in Platinum
H2 IGI Certified Lab-Grown
H2 Shop By Style
H3 Solitaire Rings
H3 Solitaire Rings
H3 Three Stone Rings
H3 Three Stone Rings
H3 Halo Rings
H3 Halo Rings
H3 Side Stone Rings
H3 Side Stone Rings
H2 What our customers say
H3 Sarah Johnson
H3 Michael Chen
H3 Emily Rodriguez
H3 David Thompson
H3 Jessica Martinez
H3 Robert Kim
H2 Frequently Asked Question
H3 What type of diamonds do you use?
H3 Is moissanite better than diamonds?
H3 Will the jewelry fade or lose shine?
H3 Is your jewelry waterproof?
H3 About Us
H3 Contact
H3 Support
H3 Education

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

PASS

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

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

A+

Alt Text Quality

All 70 images OK

PASS

All 70 images OK

4 decorative image(s) correctly marked

66 image(s) with good alt text

70 images 66 good alt text 4 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 4 controls labeled

PASS

All 4 controls labeled

4 control(s) properly labeled

4 controls

4 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#Search-In-Modal-1	search	Search	for/id
#Search-In-Modal	search	Search	for/id
contact[email]	email	Enter your email	aria-label
#email_01KPJ5ME9EWCDM1NPF2TJ2EJT2	email	Email	for/id

A

Link & Button Quality

203 links, 23 buttons — all OK

PASS

203 links, 23 buttons — all OK

4 link(s) open in new tab without warning

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

Got: https://www.facebook.com/profile.php?id=61585621430312; http://instagram.com/beyondcarat; https://www.pinterest.com/beyondcarat/; https://klaviyo.com/features/forms-web-personalization?utm_medium=referral&ut…

199 link(s) with descriptive text

203 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/profile.php?id=…	Facebook	new tab	Add '(opens in new tab)' to text
http://instagram.com/beyondcarat	Instagram	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/beyondcarat/	Pinterest	new tab	Add '(opens in new tab)' to text
https://klaviyo.com/features/forms-web-p…	Created with Klaviyo - opens i…	new tab	Add '(opens in new tab)' to text

222 links and buttons have descriptive text

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

https://www.facebook.com/profile.php?id=61585621430312; http://instagram.com/beyondcarat; https://www.pinterest.com/beyondcarat/; https://klaviyo.com/features/forms-web-personalization?utm_medium=referral&ut…

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

4 form control(s) checked, no type mismatches

PASS

4 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

4 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

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+

Mobile-Readable Font Sizes

All 45 visible text node(s) render at >= 12 CSS pixels

PASS

All 45 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

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 97/100 — 1 failing, 31 passed

PASS

97

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Engagement Rings `div.card__content > div.card__information > h3.card__heading > a.full-unstyled-link`
Diamond Earrings `div.card__content > div.card__information > h3.card__heading > a.full-unstyled-link`
Tennis Bracelets `div.card__content > div.card__information > h3.card__heading > a.full-unstyled-link`
Solitaire Rings `div.card__content > div.card__information > h3.card__heading > a.full-unstyled-link`
Three Stone Rings `div.card__content > div.card__information > h3.card__heading > a.full-unstyled-link`
Halo Rings `div.card__content > div.card__information > h3.card__heading > a.full-unstyled-link`
2 days ago `div.ai-review-card-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-header-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-info-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > p.ai-review-date-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr`
Verified Purchase `div.ai-reviews-container-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-reviews-grid-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-card-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-verified-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr`
1 week ago `div.ai-review-card-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-header-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-info-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > p.ai-review-date-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr`
Verified Purchase `div.ai-reviews-container-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-reviews-grid-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-card-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-verified-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr`
2 weeks ago `div.ai-review-card-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-header-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-info-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > p.ai-review-date-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr`
Verified Purchase `div.ai-reviews-container-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-reviews-grid-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-card-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-verified-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr`
3 weeks ago `div.ai-review-card-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-header-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-info-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > p.ai-review-date-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr`
1 month ago `div.ai-review-card-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-header-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-info-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > p.ai-review-date-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr`
Verified Purchase `div.ai-reviews-container-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-reviews-grid-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-card-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-verified-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr`
1 month ago `div.ai-review-card-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-header-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-info-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > p.ai-review-date-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr`
Verified Purchase `div.ai-reviews-container-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-reviews-grid-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-card-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr > div.ai-review-verified-ark9kavpxsm8vnvvxdaigenblockbdd20afnujfhr`

These are opportunities to improve the legibility of your content.

○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

●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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Uses ARIA roles only on compatible elements

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

●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

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

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

○All heading elements contain content.

○Identical links have the same purpose.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

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

Send Feedback