Accessibility report for glossier.com
Based on an automated WCAG 2.1 Level AA scan on July 13, 2026.
Accessibility isn't a nice-to-have — it's the law. This automated WCAG 2.1 Level AA scan of glossier.com flagged 8 types of barrier to fix.
On this page, the most frequent barrier is "An interactive element (link, button) is inside another interactive element" — found on 39 elements. In total the scan flagged 63 issues across 8 categories of WCAG 2.1 Level AA.
WCAG 2.1 Level AA is the standard U.S. courts apply under the ADA, and the law across the EU under the European Accessibility Act. These barriers block screen-reader, keyboard-only, and low-vision users — and every one of them is fixable. Here's how.
Accessibility issues found, with fixes
Some form fields have no label that screen readers can announce.
WCAG 4.1.2 (Level A) Section 508EN 301 549 Affects screen-reader and cognitive-disability users
Why it matters: Visually you can see what each field is for (next to a 'Name:' or 'Email:' text), but screen-reader users hear only 'edit text' if there's no programmatic label connecting the text to the field. The result: blind users can't tell what to type where.
How to fix it: In a website builder, every form field has a 'Label' field or similar. Make sure every input has one filled in. Placeholder text (the gray hint inside the field) does NOT count as a label — it has to be a real label.
Fix it free and meet WCAG 2.1 AA
The free wcagcheckr browser extension finds every one of these issues on your own pages and gives you the fix recipe for each — at no cost. Run it, fix what it finds, and re-check this page anytime.
Own this site? Fix the issues, then re-scan — this report updates automatically, and comes down entirely once you pass.
An accessibility rule failed on this page.
WCAG 1.3.1 (Level A) EN 301 549 Affects screen-reader users
Why it matters: Some users — particularly those using screen readers, keyboard-only navigation, or who have low vision or motor disabilities — may have trouble using this part of the page.
How to fix it: Share the technical rule ID with your developer. They can look up the full fix at https://dequeuniversity.com/rules/axe.
An accessibility rule failed on this page.
WCAG 1.3.1 (Level A) EN 301 549 Affects screen-reader users
Why it matters: Some users — particularly those using screen readers, keyboard-only navigation, or who have low vision or motor disabilities — may have trouble using this part of the page.
How to fix it: Share the technical rule ID with your developer. They can look up the full fix at https://dequeuniversity.com/rules/axe.
An interactive element (link, button) is inside another interactive element.
WCAG 4.1.2 (Level A) EN 301 549 Affects keyboard-only users
Why it matters: Keyboard and screen-reader users can't reliably reach the inner element. Common in 'card-as-link' designs where a button sits inside a clickable card.
How to fix it: Developer fix: 'avoid putting buttons inside links or links inside buttons; use a single interactive element with internal helpers'.
Some buttons or links are too small to tap reliably on touch screens.
WCAG 2.5.8 (Level AA) Affects low-vision and colorblind users
Why it matters: WCAG 2.2 requires touch targets to be at least 24×24 pixels. Small targets are a problem for users with hand tremors, large fingers, or motor disabilities. They're also frustrating for everyone.
How to fix it: In your editor, increase padding around small icon buttons. If your developer is involved, ask them to ensure all interactive elements have minimum 24×24 CSS pixels of clickable area.
Heading levels skip — for example, an H2 jumps directly to an H4 with no H3 between them.
Affects screen-reader users
Why it matters: Screen-reader users navigate by heading levels. Skipped levels suggest missing content and break the page's outline. Confusing for everyone.
How to fix it: In your editor, find the headings that skip levels and either bump them up to the right level (H4 → H3 if no H2 exists between) or insert the missing level. Headings should follow a logical outline like a document outline.
Some content on the page isn't inside a recognized region (header, nav, main, footer, aside).
Affects keyboard-only users
Why it matters: Screen-reader users navigate by these regions. Content outside any region can be missed when skimming.
How to fix it: Developer fix: 'wrap orphaned page content in semantic landmark elements (<main>, <aside>, <nav>) so it's reachable via landmark nav'.
A heading on this page has no text.
Affects screen-reader users
Why it matters: Screen-reader users navigate pages by jumping between headings. An empty heading is dead air — they don't know what the section is about.
How to fix it: Find the empty heading in your editor (often a section title that was deleted but the heading element remained) and either delete it or add real heading text.
This is an automated scan and catches a portion of accessibility barriers; full WCAG 2.1 Level AA conformance also requires manual and assistive-technology testing. See our methodology for what we do and don't claim.
Learn more
How this report was produced
This report is an automated scan of the page as it was publicly served on
,
using [email protected]. The captured page and these results are sealed with a
tamper-evident hash (c05ab69e1db84b3f…).
We report only what the page publicly returned at that time.
This seal is anchored to a trusted RFC-3161 timestamp via freetsa.org on . Independently verify this receipt →