Accessibility report for springfootwear.com
Based on an automated WCAG 2.1 Level AA scan on June 29, 2026.
Under the ADA in the U.S. — and the European Accessibility Act in the EU — business websites must be accessible. springfootwear.com was checked against WCAG 2.1 Level AA, and 13 types of barrier were flagged.
On this page, the most frequent barrier is "Some links have no readable text — usually icon-only links" — found on 13 elements. In total the scan flagged 35 issues across 13 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.
The barriers on this page — and the fixes
An element has a screen-reader hint that doesn't apply to its role.
WCAG 4.1.2 (Level A) EN 301 549 Affects screen-reader users
Why it matters: Inappropriate hints can confuse or break screen-reader announcements.
How to fix it: Developer fix: 'this aria-* attribute isn't allowed on this role; remove it or change the role'.
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 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 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').
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.
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.
A custom input control (search box, range slider, custom date picker) has no name.
WCAG 4.1.2 (Level A) EN 301 549 Affects screen-reader users
Why it matters: Custom controls are common in modern site builders — they look fancy but break for screen-reader users when not labeled.
How to fix it: This is a developer fix. Ask: 'custom inputs with role=textbox / searchbox / slider / spinbutton need an aria-label or aria-labelledby'.
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.
A frame on the page can't be navigated by keyboard.
WCAG 2.1.1 (Level A) EN 301 549 Affects keyboard-only users
Why it matters: Keyboard users get stuck — they can't reach interactive content inside the frame.
How to fix it: Developer fix: 'iframes containing interactive content shouldn't have tabindex=-1 on their parent or content'.
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').
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'.
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.
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 (55cc8a21c23d24ef…).
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 →
An independent snapshot of this page was also saved to the Internet Archive. View the archived page →