Accessibility Statement.

Kneady People is for people who work with the body. That includes people who experience the web differently. This page is honest about where we're strong on accessibility and where we know we're still catching up.

Effective June 11, 2026

Our target

We work toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA as the design and engineering baseline for the platform. We are not fully conformant everywhere yet — known gaps are listed below, and we treat each one as an active remediation item rather than an accepted limitation.

Kneady People aims to comply with the Americans with Disabilities Act (ADA) Title III as applied to digital services, and with comparable accessibility laws in other jurisdictions where we operate. We treat accessibility as a continuous obligation rather than a checkbox — improvements ship on the same cadence as the rest of the product.

Accessibility coordinator

Nick Peterka serves as the Kneady People accessibility coordinator. If you need help, want to escalate an issue, or request information in an alternative format, contact hello@kneadypeople.com with the subject “Accessibility”.

What works well today

• Semantic HTML. The site is built on standard HTML elements with appropriate roles, labels, and landmarks. Screen readers get a sensible reading order.
• Keyboard navigation.We aim for every interactive control (links, buttons, form fields, tool inputs) to be reachable and operable from the keyboard, with tab order following the visual order and a visible focus indicator. Where you find a control that is not, please report it — see “How to report a problem” below.
• Color contrast.We have reviewed our own design system's color contrast against WCAG 2.1 AA and believe our primary text colors meet the 4.5:1 body-text threshold on the surfaces where they appear. Our two lightest accent colors — the camel and stone tones — are reserved for large text, decorative labels, and interface elements where the 3:1 threshold applies; we do not use them for small body copy. We aim never to rely on color alone to signal state — important signals also use text, icons, or shape. We don't control the contrast of user-generated or third-party embedded content; if you find a contrast problem, please report it (below) and we'll fix it.
• Resizable text. Zoom to 200% without breaking layouts. Container queries make the tool UIs respond to text size, not just viewport width.
• Reduced motion. If your OS reports prefers-reduced-motion: reduce, we disable the decorative animations in Nebula and Lava scenes (the Brain Break tool) and reduce hover transforms elsewhere.
• Form labels & error messages. Every form field has an associated label. Errors are announced inline and are programmatically tied to the field they refer to.
• Skip targets. The marketing pages place the main content first in the DOM after the nav so screen-reader users can land on the headline without traversing a long menu.

Known gaps

We are working on these. They are not done.

• Captions on Podcast episodes.The podcast hasn't launched yet. When it does, every episode will ship with transcripts, and the embedded player will support captions.

Recently closed

Items we've resolved. We keep them listed for a while so you can see the direction of travel.

• Brain Break canvas animations. The Ocean and Stars scenes render to a <canvas>, which previously presented a blank surface to a screen reader. Each now carries an image role and a text description of the scene, so the decorative animation has a programmatic equivalent.
• Map pins on the Directory teaser. The homepage teaser now renders the same keyboard-accessible Leaflet map as /directory rather than the old absolutely-positioned decorative pins; its non-interactive search overlay is hidden from assistive technology.
• Hover-only details.The tool gallery cards no longer hide any text behind hover — every card's text is present and reachable without a pointer.
• Color-contrast review.We reviewed the design system's color contrast against WCAG 2.1 AA — see “What works well today” above for the result.

Assistive technology we test with

• VoiceOver (macOS, iOS)
• NVDA (Windows)
• Keyboard-only navigation
• Browser zoom up to 200%

We aim to support the current and previous major versions of Safari, Chrome, Firefox, and Edge.

How to report a problem

If you hit an accessibility issue — anything from a missing label to a feature you can't use with your assistive technology — please tell us. We treat accessibility reports as real bugs.

Email hello@kneadypeople.com with the subject “Accessibility”. Include the page you were on, what you were trying to do, and what happened (or didn't). If it's helpful, mention which assistive technology you're using. We prioritize material accessibility issues and aim to address them within a reasonable timeframe given the scope of the fix.

Standards & alternatives

If you need information from Kneady People in an alternative accessible format (large print, plain text, a different encoding), email hello@kneadypeople.com and we'll do our best to provide it.