Skip to content
https://renaissancejewel.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
71
GRADE
C
FIX
7
REVIEW
9
PASS
8
INFO
0
Checks
24
8 PASS 9 REVIEW 7 FIX
D
Mobile Keyboard & Autofill
Action
8/8 eligible field(s) missing autocomplete or inputmode
FIX
8/8 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.
Got: <input type="email" name="email" id="halo-notify-email">
Warning::
7 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">, <input type="search" name="q" id="Search-In-Modal">, <input type="email" name="contact[email]">, <input type="email" name="contact[email]" id="NewsletterForm--sections--22211653599490__1f746ce7-225d-4414-aada-b8b7bb8a76a1">, <input type="email" name="email" id="halo-notify-email">
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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
Info::
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
Info::
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.
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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
Info::
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)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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.
C
Heading Hierarchy
Action
30 headings, 1 skip(s)
REVIEW
30 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 +1 888-863-7990
  • H3 (empty)
  • H3 Trending
  • H3 Trending
  • H3 The Bestsellers Edit
  • H3 Forever Bands
  • H3 The Earring Edit
  • H3 Layered & Lovely
  • H3 Trending
  • H3 Trending
  • H1 Renaissance Jewel
  • H1 The Art of the Diamond duplicate H1
  • H2 Explore Our Diamond Jewelry
  • H2 The Signature Edit
  • H2 Crafted to Last a Lifetime
  • H2 Loved by Thousands
  • H2 Design Something Entirely Your Own
  • H2 Stay in Touch
  • H2 Renaissance Jewel
  • H2 Useful Links
  • H2 Information
  • H2 Let’s Keep In Touch
  • H2 Shop the look
  • H2 Choose Options
  • H5 (empty)
  • H5 Edit Option
  • H5 Back In Stock Notification
  • H3 Trending
  • H3 Trending
  • H3 Share this cart

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

B
Form Accessibility
2 of 10 controls have issues
REVIEW
2 of 10 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="text" id="share-cart-link-input">
Info::
8 control(s) properly labeled
10 controls
8 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#Search-In-ModalsearchSearchfor/id
#Search-In-ModalsearchSearchfor/id
contact[email]emailEmail addressaria-label
#NewsletterForm--sections--22211653599490__1f746ce7-225d-4414-aada-b8b7bb8a76a1emailYour emailfor/id
#halo-notify-emailemailLeave your email and we will notify as soon as the product / variant is back in stockfor/id
#customer_emailemailEmail Address *for/id
#customer_passwordpasswordPassword *for/id
#Search-In-ModalsearchSearchfor/id
inputsubmit(none)none
#share-cart-link-inputtext(none)none

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

<input type="submit">; <input type="text" id="share-cart-link-input">

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

B
Form Input Quality
2 input-semantic issue(s) across 10 form control(s)
REVIEW
2 input-semantic issue(s) across 10 form control(s)
Info::
1 password field(s) missing or with invalid `autocomplete`
Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="customer[password]">.
Info::
3 login form field(s) missing `autocomplete=username` (or `email`)
On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="email" name="contact[email]">, <input type="email" name="email">, <input type="email" name="customer[email]">.
B
Iframe Accessibility
2/2 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://renaissancejewel.com/web-pixels@a5bf51cfwabd6c495p49b74ff1maa529d2b/cus…")
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.
Warning::
<iframe> missing title attribute (src="https://renaissancejewel.com/web-pixels@a5bf51cfwabd6c495p49b74ff1maa529d2b/cus…")
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.
B
Tap Target Adequacy
1 tap target(s) too small or too close together
REVIEW
1 tap target(s) too small or too close together
Info::
1 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
C
Mobile-Readable Font Sizes
Action
84% of visible text renders at >= 12 CSS px (22 below threshold)
REVIEW
84% of visible text renders at >= 12 CSS px (22 below threshold)
Warning::
22 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: <span> 11.0px ("Ends Soon"); <a> 11.0px ("Shop the Sale →"); <span> 9.5px ("The Collection"); <span> 10.5px ("Shop Engagement Rings →"); <span> 11.5px ("Round").
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found – Renaissance Jewel ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
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 Renaissance Jewel
1.27:1
#000000
on
#2B1B13
needs 3.0:1 (large text)
32px · bottom of viewport
h1 The Art of the Diamond
1.27:1
#000000
on
#2B1B13
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Explore Our Diamond Jewelry
1.27:1
#000000
on
#2B1B13
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The Signature Edit
1.27:1
#000000
on
#2B1B13
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Crafted to Last a Lifetime
1.27:1
#000000
on
#2B1B13
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Loved by Thousands
1.27:1
#000000
on
#2B1B13
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Design Something Entirely Your Own
1.27:1
#000000
on
#2B1B13
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Stay in Touch
1.27:1
#000000
on
#2B1B13
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Renaissance Jewel
1.27:1
#000000
on
#2B1B13
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Useful Links
1.27:1
#000000
on
#2B1B13
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Information
1.27:1
#000000
on
#2B1B13
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Let’s Keep In Touch
1.27:1
#000000
on
#2B1B13
needs 3.0:1 (large text)
24px · bottom of viewport
h3 The Bestsellers Edit
1.27:1
#000000
on
#2B1B13
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Forever Bands
1.27:1
#000000
on
#2B1B13
needs 3.0:1 (large text)
19px · bottom of viewport
h3 The Earring Edit
1.27:1
#000000
on
#2B1B13
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Layered & Lovely
1.27:1
#000000
on
#2B1B13
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Share this cart
1.27:1
#000000
on
#2B1B13
needs 3.0:1 (large text)
19px · bottom of viewport
title Lab Grown Diamond Rings, Diamond Jewelry…
1.20:1
#000000
on
#1C1917
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.20:1
#000000
on
#1C1917
needs 4.5:1 (normal text)
16px · top of page (header area)
b 50% Off
1.20:1
#000000
on
#1C1917
needs 3.0:1 (large text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Renaissance Jewel1.27:13.0:1
#000000
#2B1B13
Fail
h1 The Art of the Diamo…1.27:13.0:1
#000000
#2B1B13
Fail
h2 Explore Our Diamond …1.27:13.0:1
#000000
#2B1B13
Fail
h2 The Signature Edit1.27:13.0:1
#000000
#2B1B13
Fail
h2 Crafted to Last a Li…1.27:13.0:1
#000000
#2B1B13
Fail
h2 Loved by Thousands1.27:13.0:1
#000000
#2B1B13
Fail
h2 Design Something Ent…1.27:13.0:1
#000000
#2B1B13
Fail
h2 Stay in Touch1.27:13.0:1
#000000
#2B1B13
Fail
h2 Renaissance Jewel1.27:13.0:1
#000000
#2B1B13
Fail
h2 Useful Links1.27:13.0:1
#000000
#2B1B13
Fail
h2 Information1.27:13.0:1
#000000
#2B1B13
Fail
h2 Let’s Keep In Touc…1.27:13.0:1
#000000
#2B1B13
Fail
h3 The Bestsellers Edit1.27:13.0:1
#000000
#2B1B13
Fail
h3 Forever Bands1.27:13.0:1
#000000
#2B1B13
Fail
h3 The Earring Edit1.27:13.0:1
#000000
#2B1B13
Fail
h3 Layered & Lovely1.27:13.0:1
#000000
#2B1B13
Fail
h3 Share this cart1.27:13.0:1
#000000
#2B1B13
Fail
title Lab Grown Diamond Ri…1.20:14.5:1
#000000
#1C1917
Fail
a Skip to content1.20:14.5:1
#000000
#1C1917
Fail
b 50% Off1.20:13.0:1
#000000
#1C1917
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.

B
Lighthouse Accessibility Audits
Score 83/100 — 6 failing, 24 passed
REVIEW
83

Accessibility

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

ARIA

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

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
MENU ✕ ENGAGEMENT RINGS → WEDDING BANDS → EARRINGS → NECKLACE → BRACELETS JEWEL… div.container > div.header-mobile__wrapper > div.header-mobile__item > aside.rj-mnav

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Add to Wishlist div.hp-prod-grid > article.hp-card > div.hp-media > div.hp-wish
Add to Wishlist div.hp-prod-grid > article.hp-card > div.hp-media > div.hp-wish
Add to Wishlist div.hp-prod-grid > article.hp-card > div.hp-media > div.hp-wish
Add to Wishlist div.hp-prod-grid > article.hp-card > div.hp-media > div.hp-wish

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
RINGS CRAFTED section#hp-ribbon > div.hp-wrap > div.hp-rb > span
FROM 2,000+ REVIEWS section#hp-ribbon > div.hp-wrap > div.hp-rb > span
INDEPENDENTLY CERTIFIED section#hp-ribbon > div.hp-wrap > div.hp-rb > span
FINISHED TO ORDER section#hp-ribbon > div.hp-wrap > div.hp-rb > span
© Copyright 2025, Renaissance Jewel All Rights Reserved. div.footer-block__bottom > div.footer__column-item > div.copyright__content > p.asmini

These are opportunities to improve the legibility of your content.

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.header-mobile__wrapper > div.header-mobile__item > div.mob-header-icons-right > a.mobile-menu-pin div.header-mobile__wrapper > div.header-mobile__item > div.mob-header-icons-right > a.mobile-menu-pin
sticky-header-mobile.header-mobile > div.container > div.custom-search-box > a.mobile-menu-pin sticky-header-mobile.header-mobile > div.container > div.custom-search-box > a.mobile-menu-pin

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
Search details-modal.header__iconItem > predictive-search.search-modal__form > details.search_details > summary.header__search-full

These items highlight common accessibility best practices.

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
SUBSCRIBE form-has-check.footer-block__newsletter-item > form#ContactFooter > div.newsletter-form__field-wrapper > button#Subscribe--sections--22211653599490__1f746ce7-225d-4414-aada-b8b7bb8a76a1
○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
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`[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
○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
○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
○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
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN ASIDE CONTENTINFO footer

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 Text Quality
All 30 heading(s) have substantive, well-formed text
PASS
All 30 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 151 images OK
PASS
All 151 images OK
Info::
1 decorative image(s) correctly marked
Info::
150 image(s) with good alt text
151 images 150 good alt text 1 decorative
All images have appropriate alt text.
A+
Form Input Types
10 form control(s) checked, no type mismatches
PASS
10 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
12 explicit tabindex attribute(s) checked, no anti-patterns
PASS
12 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback