Accessibility report for blcustom.com
Based on an automated WCAG 2.1 Level AA scan on September 25, 2026.
blcustom.com does not yet meet WCAG 2.1 Level AA, the accessibility standard written into U.S. and EU law. This automated scan found 4 types of barrier affecting people with disabilities.
On this page, the most frequent barrier is "Some buttons have no description that screen readers can announce" — found on 3 elements. In total the scan flagged 7 issues across 4 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.
What needs fixing to meet the standard
Some buttons have no description that screen readers can announce.
WCAG 4.1.2 (Level A) Section 508EN 301 549 Affects screen-reader users
Why it matters: Visual users see an icon (a heart, a trash can, an X), but screen-reader users hear only 'button' — they don't know if it'll favorite a post, delete it, or close a dialog. This is a critical accessibility blocker and a top lawsuit driver.
How to fix it: Every button needs a text label. If you can't put text inside the button (icon-only design), in your platform's button settings look for an 'Aria label' or 'Screen reader text' field — fill it with what the button does ('Close', 'Add to cart', 'Open menu').
Links inside paragraphs are distinguishable from the surrounding text by color alone.
WCAG 1.4.1 (Level A) EN 301 549 Affects low-vision and colorblind users
Why it matters: If a user is colorblind or sees in grayscale, they can't tell which words are clickable. WCAG requires another visual cue (underline, bold, icon) in addition to color.
How to fix it: Add an underline to links inside paragraphs. In most theme editors there's a 'link style' setting — turn underlines back on. The underline is the standard convention; it's also more discoverable for everyone.
Get compliant, free
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.
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.
An accessibility rule failed on this page.
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.
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 (da39754a4a28aa5a…).
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 →