Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 4 REVIEW 5 FIX

Link & Button Quality

Action

9 issue(s) across 201 links and 48 buttons

FIX

9 issue(s) across 201 links and 48 buttons

5 link(s) with generic text

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

Got: /pages/community ("Learn More"); /pages/community ("Learn More"); /pages/community ("Learn More"); /pages/rare-impact/rare-impact-fund ("Learn More"); /pages/salesandpromotions ("Read More")

16 image-only link(s) without alt text

3 link(s) open in new tab without warning

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

Got: https://www.onbrand.com/brand/rare-beauty/; https://www.rarebeauty.com/policies/privacy-policy; https://www.cookiepro.com/products/cookie-consent/

4 button(s) with no accessible text

177 link(s) with descriptive text

201 links

0 empty

5 generic text

3 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
/collections/shop-all	Shop All	img no alt	Add alt attribute to the image
/collections/new	New	img no alt	Add alt attribute to the image
/collections/bestsellers	Bestsellers	img no alt	Add alt attribute to the image
/collections/fragrance	Fragrance	img no alt	Add alt attribute to the image
/collections/face	Face	img no alt	Add alt attribute to the image
/collections/eye	Eye	img no alt	Add alt attribute to the image
/collections/lip	Lip	img no alt	Add alt attribute to the image
/collections/body	Body	img no alt	Add alt attribute to the image
/collections/tools	Tools	img no alt	Add alt attribute to the image
/collections/online-only	Online Only	img no alt	Add alt attribute to the image
/pages/community	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Community
/pages/community	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Community
/pages/community	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Community
/collections/lip	Lip	img no alt	Add alt attribute to the image
/collections/eye	Eye	img no alt	Add alt attribute to the image
/collections/bestsellers	Bestsellers	img no alt	Add alt attribute to the image
/collections/lip	Lip	img no alt	Add alt attribute to the image
/collections/eye	Eye	img no alt	Add alt attribute to the image
/collections/bestsellers	Bestsellers	img no alt	Add alt attribute to the image
/pages/rare-impact/rare-impact-fund	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Rare Impact Fund
https://www.onbrand.com/brand/rare-beaut…	Partnerships	new tab	Add '(opens in new tab)' to text
/pages/salesandpromotions	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Salesandpromotions
https://www.rarebeauty.com/policies/priv…	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.cookiepro.com/products/cooki…	Powered by OneTrust Opens in a…	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
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

221 links and buttons have descriptive text

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

/pages/community ("Learn More"); /pages/community ("Learn More"); /pages/community ("Learn More"); /pages/rare-impact/rare-impact-fund ("Learn More"); /pages/salesandpromotions ("Read More")

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

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

https://www.onbrand.com/brand/rare-beauty/; https://www.rarebeauty.com/policies/privacy-policy; https://www.cookiepro.com/products/cookie-consent/

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

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.

Got: #ffffff

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

31 headings, 1 skip(s)

REVIEW

31 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

1 empty heading(s)

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

H1 Rare Beauty
H2 Try These Best Sellers
H3 Bestsellers
H3 Soft Pinch Liquid Blush
H2 FoundationShade Finder
H3 @RareBeauty
H3 This is Your Community
H3 This is Your Community
H3 This is Your Community
H3 Shop by Category
H2 Make an impact on mental health
H4 Sign up for email and/or texts for the latest updates, special offers, and more. skipped
H4 SHOP
H4 COMPANY
H4 CUSTOMER SERVICE
H3 Free Pocket Mirror w/$40 USD order. Code: MIRROR26.Read More
H3 Free Standard U.S. Shipping w/$50 USD order.Shop Now
H3 Choose your free sample!
H4 Positive Light Under Eye Brightener Sample Card
H3 We think you'll also love...
H3 Your cart is empty.
H3 (empty)
H3 Get the Look
H2 WE'VE GONE INTERNATIONAL!
H2 Privacy Preference Center
H3 Manage Consent Preferences
H4 Functional Cookies
H4 Targeting Cookies
H4 Strictly Necessary Cookies
H4 Performance Cookies
H3 Cookie List

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

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 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

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Lighthouse Accessibility Audits

Score 89/100 — 4 failing, 29 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.

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
Your Email `div.footer__newsletter > div#footerNewsletterForm > div.footer-newsletter__container > label.footer-newsletter__label`
JOIN US `div.footer__newsletter > div#footerNewsletterForm > div.footer-newsletter__container > button.footer-newsletter__button`
Your Mobile # `div.footer__newsletter > form#footerNewsletterTextForm > div.footer-newsletter-text__container > label.footer-newsletter-text__label`
JOIN US `div.footer__newsletter > form#footerNewsletterTextForm > div.footer-newsletter-text__container > button.footer-newsletter-text__button`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Bestsellers `section.home-product-carousel > div.home-product-carousel__container > header.section-header > h3.section-header__heading`
SIGN UP FOR EMAIL AND/OR TEXTS FOR THE LATEST UPDATES, SPECIAL OFFERS, AND MORE. `div.footer__container > div.footer__main > div.footer__newsletter > h4.footer__newsletter-heading`

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search Items in cart: 0. Toggle Cart 0 `header#header > div.header__container > div.nav-utilities > ul.nav-utilities__list`

These are opportunities to improve the experience of reading tabular or list data using 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
Items in cart: 0. Toggle Cart 0 `div.header__container > div.nav-utilities > ul.nav-utilities__list > button#cartCloseBtn`
JOIN US `div.footer__newsletter > div#footerNewsletterForm > div.footer-newsletter__container > button.footer-newsletter__button`
JOIN US `div.footer__newsletter > form#footerNewsletterTextForm > div.footer-newsletter-text__container > button.footer-newsletter-text__button`
Privacy Policy `div.footer__sub > div.footer__colophon > div.footer__colophon-text > a.footer__colophon-link`
Terms of Service `div.footer__sub > div.footer__colophon > div.footer__colophon-text > a.footer__colophon-link`
UGC Terms of Service `div.footer__sub > div.footer__colophon > div.footer__colophon-text > a.footer__colophon-link`
Your Privacy Choices `div.footer__sub > div.footer__colophon > div.footer__colophon-text > button#cookieSettingsTrigger`
CA Notice at Collection `div.footer__sub > div.footer__colophon > div.footer__colophon-text > a.footer__colophon-link`

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

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

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

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

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

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

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

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

○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

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

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

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

○Elements with visible text labels have matching accessible names.

○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

16 landmarks

PASS

16 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Alt Text Quality

All 50 images OK

PASS

All 50 images OK

24 decorative image(s) correctly marked

26 image(s) with good alt text

50 images 26 good alt text 24 decorative

All images have appropriate alt text.

Form Accessibility

1 of 11 controls have issues

PASS

1 of 11 controls have issues

1 control(s) without accessible label

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

Got: <input>

10 control(s) properly labeled

11 controls

10 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#footerNewsletterInput	text	Your Email	for/id
#footerNewsletterTextInput	tel	Your Mobile #	for/id
#ot-group-id-C0003	checkbox	Functional Cookies	for/id
#ot-group-id-C0004	checkbox	Targeting Cookies	for/id
#ot-group-id-C0002	checkbox	Performance Cookies	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id
input	input	(none)	none

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

<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

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Try These Best Selle…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Foundation	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shade	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Make an	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 on mental health	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 WE'VE GONE INTERNATI…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Privacy Preference C…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Bestsellers	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Soft Pinch Liquid Bl…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 @RareBeauty	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 This is	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Community	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 This is	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Community	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 This is	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Community	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Shop by	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Category	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Free Pocket Mirror w…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Free Standard U.S. S…	21.00:1	3.0:1	#000000	#FFFFFF	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.

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