Accessibility report for innovebw.com
Based on an automated WCAG 2.1 Level AA scan on July 21, 2026.
Accessibility isn't a nice-to-have — it's the law. This automated WCAG 2.1 Level AA scan of innovebw.com flagged 7 types of barrier to fix.
On this page, the most frequent barrier is "Some links have no readable text — usually icon-only links" — found on 5 elements. In total the scan flagged 19 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
A dropdown menu has no description.
WCAG 4.1.2 (Level A) Section 508EN 301 549 Affects screen-reader and cognitive-disability users
Why it matters: Screen-reader users hear 'combo box, has popup' but not what the dropdown is for. They can't fill out forms reliably.
How to fix it: In your form editor, check that each dropdown has a visible label above or beside it. If your platform has separate label/field settings, both must be filled.
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).
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.
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').
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 page is missing a main heading (H1).
Affects screen-reader users
Why it matters: Screen-reader users use the H1 to confirm they landed on the right page. The H1 is also a strong SEO signal — Google uses it to understand what the page is about.
How to fix it: Add a clear, descriptive H1 to the top of the page. In website builders, this is usually the 'Title' or 'Page heading' setting. Each page should have exactly one H1.
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 (0a4955edf3a9b68d…).
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 →