Accessibility report for frankieshop.com
Based on an automated WCAG 2.1 Level AA scan on August 7, 2026.
Under the ADA in the U.S. — and the European Accessibility Act in the EU — business websites must be accessible. frankieshop.com was checked against WCAG 2.1 Level AA, and 5 types of barrier were flagged.
On this page, the most frequent barrier is "Some elements have positive tabindex values, forcing a custom focus order" — found on 6 elements. In total the scan flagged 13 issues across 5 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
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 elements have positive tabindex values, forcing a custom focus order.
Affects keyboard-only users
Why it matters: Custom focus orders are nearly always confusing — focus jumps around unexpectedly. Best practice is to never use positive tabindex.
How to fix it: Developer fix: 'replace tabindex=1/2/3... with tabindex=0 (or remove entirely); use DOM order to control focus order'.
There are multiple top banners (headers) on the page when there should be one.
Affects screen-reader users
Why it matters: Screen-reader users get confused by duplicate landmarks — they don't know which is the 'real' header.
How to fix it: Developer fix: 'only one element should have role=banner or be a top-level <header>; remove duplicates'.
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.
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 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'.
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 (e1979377f5094e17…).
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 →