Accessibility report for pinklily.com
Based on an automated WCAG 2.1 Level AA scan on June 10, 2026.
Under the ADA in the U.S. — and the European Accessibility Act in the EU — business websites must be accessible. pinklily.com was checked against WCAG 2.1 Level AA, and 1 type of barrier were flagged.
On this page, the most frequent barrier is "Some links have no readable text — usually icon-only links" — found on 4 elements. In total the scan flagged 4 issues across 1 category 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.
The barriers on this page — and the fixes
Fix these to meet the legal standard — at no cost
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.
Some links have no readable text — usually icon-only links.
WCAG 4.1.2 (Level A) Section 508EN 301 549 Affects screen-reader users
Why it matters: Screen-reader users hear 'link' but not where the link goes. Users navigate by listening to a list of links — useless if every entry is just 'link, link, link'.
How to fix it: In your site editor, for icon-only links (social-media icons, navigation arrows), set an 'Aria label' or 'Title' field describing where it goes ('Follow us on Twitter', 'Next page').
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 (48ec1ebeefd3b7ed…).
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 →