Accessibility report for craftshack.com
Based on an automated WCAG 2.1 Level AA scan on July 6, 2026.
Accessibility isn't a nice-to-have — it's the law. This automated WCAG 2.1 Level AA scan of craftshack.com flagged 7 types of barrier to fix.
On this page, the most frequent barrier is "An accessibility rule failed on this page" — found on 61 elements. In total the scan flagged 121 issues across 7 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
An accessibility rule failed on this page.
WCAG 4.1.2 (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.
Some text on this page is too light to read against its background.
WCAG 1.4.3 (Level AA) EN 301 549 Affects low-vision and colorblind users
Why it matters: People with low vision, older eyes, or anyone reading on a sunny phone screen can't make out faint text. Color blindness affects about 1 in 12 men and 1 in 200 women. Insufficient contrast is the #1 most-common cause of accessibility lawsuits — every Domino's-style ADA suit cites it.
How to fix it: If you use a website builder (Squarespace, Wix, Shopify, WordPress with a theme), open your site styles or theme color settings and pick darker text colors or lighter backgrounds. Aim for very dark text on white, or very light text on dark. Free check at webaim.org/resources/contrastchecker. If you have a developer, ask them to ensure all text meets WCAG AA contrast (4.5:1 for normal text, 3:1 for large text).
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').
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.
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.
The page tells mobile browsers users can't zoom in.
WCAG 1.4.4 (Level AA) EN 301 549 Affects low-vision and colorblind users
Why it matters: People with low vision rely on pinch-zoom to read small text. Disabling zoom is a real WCAG failure and a common lawsuit target.
How to fix it: In platform site settings, look for a 'Mobile zoom' or 'Pinch zoom' option and enable it. If your developer added user-scalable=no in a viewport meta tag, ask them to remove it.
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'.
An element is marked as decorative but is also focusable or has a description — contradictory.
Affects screen-reader users
Why it matters: Screen readers handle this inconsistently; some announce it anyway, some don't, leaving users with mixed experiences.
How to fix it: Developer fix: 'role=presentation/none cannot coexist with focusability or aria-label'.
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 (31a30989cb0dd680…).
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 →