Accessibility report for dexterrussellcutlery.com
Based on an automated WCAG 2.1 Level AA scan on July 28, 2026.
Under the ADA in the U.S. — and the European Accessibility Act in the EU — business websites must be accessible. dexterrussellcutlery.com was checked against WCAG 2.1 Level AA, and 11 types of barrier were flagged.
On this page, the most frequent barrier is "Some content on the page isn't inside a recognized region (header, nav, main, footer, aside)" — found on 81 elements. In total the scan flagged 136 issues across 11 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 form fields have no label that screen readers can announce.
WCAG 4.1.2 (Level A) Section 508EN 301 549 Affects screen-reader and cognitive-disability users
Why it matters: Visually you can see what each field is for (next to a 'Name:' or 'Email:' text), but screen-reader users hear only 'edit text' if there's no programmatic label connecting the text to the field. The result: blind users can't tell what to type where.
How to fix it: In a website builder, every form field has a 'Label' field or similar. Make sure every input has one filled in. Placeholder text (the gray hint inside the field) does NOT count as a label — it has to be a real label.
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 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.
The page doesn't declare what language it's in.
WCAG 3.1.1 (Level A) EN 301 549 Affects screen-reader users
Why it matters: Screen readers use this to pick the right voice and pronunciation rules. Without it, English content might be read with a French accent (or vice versa).
How to fix it: In your platform's site settings, find a 'Site language' option and set it (English = en, Spanish = es, etc.). Most modern platforms do this automatically — if it's missing, ask your developer to add lang='en' to the html element.
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 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.
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.
This page has no 'main content' region marked.
Affects screen-reader users
Why it matters: Screen-reader users press a single shortcut to jump to the main content, skipping menus and headers. Without a marked main region, they have to tab through everything.
How to fix it: Most modern platforms add this automatically. If yours doesn't, ask your developer to wrap the main content in a <main> element.
The page tells mobile browsers users can't zoom in.
WCAG 1.4.4 (Level AA) EN 301 549 Affects low-vision and colorblind users
Why it matters: People with low vision rely on pinch-zoom to read small text. Disabling zoom is a real WCAG failure and a common lawsuit target.
How to fix it: In platform site settings, look for a 'Mobile zoom' or 'Pinch zoom' option and enable it. If your developer added user-scalable=no in a viewport meta tag, ask them to remove it.
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'.
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 (7772bc95dbcae55c…).
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 →