Accessibility Watch

Accessibility report for foryourparty.com

Accessibility grade: D
Based on an automated WCAG 2.1 Level AA scan on August 8, 2026.

Accessibility isn't a nice-to-have — it's the law. This automated WCAG 2.1 Level AA scan of foryourparty.com flagged 9 types of barrier to fix.

On this page, the most frequent barrier is "Some text on this page is too light to read against its background" — found on 22 elements. In total the scan flagged 63 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.

Accessibility issues found, with fixes

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.

Or remove this report without fixing →

An element has a screen-reader hint that doesn't apply to its role.

aria-allowed-attr · critical · 3 instances

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'.

Technical details for your developer →

An accessibility rule failed on this page.

aria-hidden-focus · serious · 1 instance

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.

Technical details for your developer →

Some text on this page is too light to read against its background.

color-contrast · serious · 22 instances

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).

Technical details for your developer →

Some links have no readable text — usually icon-only links.

link-name · serious · 2 instances

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').

Technical details for your developer →

An accessibility rule failed on this page.

listitem · serious · 16 instances

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.

Technical details for your developer →

An accessibility rule failed on this page.

landmark-unique · moderate · 1 instance

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.

Technical details for your developer →

An accessibility rule failed on this page.

aria-allowed-role · minor · 4 instances

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.

Technical details for your developer →

Some images have alt text that duplicates nearby visible text.

image-redundant-alt · minor · 10 instances

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).

Technical details for your developer →

An element is marked as decorative but is also focusable or has a description — contradictory.

presentation-role-conflict · minor · 4 instances

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'.

Technical details for your developer →

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 (4693e2dd4a8bb936…). 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 →