Accessibility statement

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. This is the standard most US federal, state, and EU enforcement uses (DOJ Title II rule of April 2024, EN 301 549 in Europe), and is the same bar the EU Accessibility Act enforces from June 2025.

The marketing site, dashboard, public collection page, and the embed widget itself are all in scope.

The site is substantially conformant with WCAG 2.2 AA, with one known caveat noted below. "Substantially conformant" means most content fully meets AA criteria, with minor exceptions tracked publicly.

What's in place today:

• Skip-to-content link as the first focusable element on every page.
• Semantic landmarks (header, nav, main, footer) on every route.
• Color contrast verified — body text ≥ 7:1 against the warm cream background; interactive elements ≥ 4.5:1.
• All interactive elements have a visible :focus-visible ring (2px solid accent + 4px halo, ≥ 3:1 contrast on both light and dark backgrounds).
• scroll-padding-top: 88px so hash anchors are not obscured by the sticky nav (SC 2.4.11 Focus Not Obscured).
• Touch targets ≥ 44×44 px on mobile (SC 2.5.8 Target Size).
• aria-current="page" on the active nav link.
• Mobile menu drawer with focus moved on open, restored to trigger on close, body scroll locked.
• prefers-reduced-motion respected on every animation, scroll reveal, marquee, and transition.
• Form labels associated with inputs; errors announced via aria-live; honeypot fields are aria-hidden.
• Headings follow document order (H1 → H2 → H3) without skipping levels.
• Images have alt text or are aria-hidden when decorative.
• Color is never the only carrier of meaning — status indicators include text + icon + position.

• The Wall of Love embed widget renders inside a Shadow DOM on customer sites. Customer-side keyboard navigation works, but screen-reader heading hierarchy depends on where the widget is placed on the host page — we recommend customers place it inside a section with an appropriate <h2> heading.
• The schema-org review generator's live SERP preview uses Google's actual SERP visual conventions, which include color-only state on some elements. Tool output (the JSON-LD code) is fully accessible; the preview is illustrative.
• Some legacy blog posts use prose formatting that doesn't always include explicit ARIA roles; we're upgrading them as content is touched.

The site is tested with:

• VoiceOver on macOS Safari and iOS Safari.
• NVDA on Windows Firefox.
• Keyboard-only navigation on Chrome / Safari / Firefox.
• Browser zoom up to 400% without horizontal scroll.
• Forced colors / high-contrast mode on Windows.
• prefers-reduced-motion enabled.

If you use an assistive technology not on this list and hit a barrier, please tell us — we'll add coverage.

If a page or feature isn't accessible to you, email accessibility@plauditly.app with:

• The URL or feature where you encountered the issue.
• What you tried to do.
• What went wrong (and what assistive technology / browser / OS you were using, if you know).

We aim to acknowledge within 2 business days and to fix or provide an accessible alternative within 10 business days for issues affecting your ability to use the service. Larger structural fixes may take longer, in which case we'll keep you posted.

• Quarterly axe-core + Lighthouse audits across the dashboard and marketing site.
• Manual keyboard + screen-reader walkthroughs before any major release.
• Migration to nonce-based CSP (improves security; doesn't affect accessibility, but tracked here for transparency).
• Adding axe automation to CI so regressions can't ship.

If we can't resolve an accessibility issue through the email process above, you can:

• US — file a complaint with the US Department of Justice under the ADA: ada.gov/file-a-complaint
• EU/UK — file with the equivalent national authority enforcing the EU Web Accessibility Directive or UK Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, as applicable.

We'd rather hear from you directly first — most issues are fixable quickly and don't need a formal process.