Accessibility report for hickoryfarms.com
Based on an automated WCAG 2.1 Level AA scan on July 14, 2026.
Accessibility isn't a nice-to-have — it's the law. This automated WCAG 2.1 Level AA scan of hickoryfarms.com flagged 5 types of barrier to fix.
On this page, the most frequent barrier is "Some buttons or links are too small to tap reliably on touch screens" — found on 20 elements. In total the scan flagged 31 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.
Accessibility issues found, with 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 buttons or links are too small to tap reliably on touch screens.
WCAG 2.5.8 (Level AA) Affects low-vision and colorblind users
Why it matters: WCAG 2.2 requires touch targets to be at least 24×24 pixels. Small targets are a problem for users with hand tremors, large fingers, or motor disabilities. They're also frustrating for everyone.
How to fix it: In your editor, increase padding around small icon buttons. If your developer is involved, ask them to ensure all interactive elements have minimum 24×24 CSS pixels of clickable area.
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.
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.
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'.
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 (c387f886459c48bf…).
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 →