Accessibility report for carparts.com
Based on an automated WCAG 2.1 Level AA scan on July 31, 2026.
Under the ADA in the U.S. — and the European Accessibility Act in the EU — business websites must be accessible. carparts.com was checked against WCAG 2.1 Level AA, and 9 types of barrier were flagged.
On this page, the most frequent barrier is "An accessibility rule failed on this page" — found on 42 elements. In total the scan flagged 86 issues across 9 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 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.
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').
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 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').
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 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 element marked as an image is missing its description.
WCAG 1.1.1 (Level A) Section 508EN 301 549 Affects screen-reader users
Why it matters: Same as missing image alt — screen-reader users get nothing where they should hear a description.
How to fix it: Ask your developer: 'elements with role=img need aria-label or aria-labelledby'.
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.
Some images have alt text that duplicates nearby visible text.
Affects screen-reader users
Why it matters: Screen-reader users hear the same content twice — the surrounding text and then the alt text. Annoying, not blocking. Lower-priority fix.
How to fix it: Find images where the caption or nearby paragraph already says what the image shows, and either change the alt text to add new info or set the alt to empty (so the screen reader skips it as decorative).
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 (dce3606b589014a0…).
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 →