Skip to main content
NestBoard
NestBoard
Start free
Accessibility

Built for every pair of hands in the house.

NestBoard is made for multi-generational households, which makes accessibility the product, not a feature. Here's what works today, what doesn't yet, and how to tell us when something's hard to use.

LAST UPDATED: JUNE 11, 2026

1. Our commitment

NestBoard is built for whole households: kids, parents, grandparents, and caregivers. That means accessibility is not a checkbox for us; it is the audience. A shared calendar that a grandparent cannot read is not a shared calendar.

We aim for the spirit and, increasingly, the letter of WCAG 2.1 AA. We are a small team and not everything is perfect yet, so this page is honest about what works today and what is still on the bench.

2. What works today

Zoom everywhere: you can pinch-zoom and resize text on every page, including inside the mobile apps. We removed the viewport restrictions that block zooming because locking zoom fails the people who need it most.

Dark and light themes: a full dark mode (easier on light-sensitive eyes) and a warm light theme, both using a consistent token system so contrast stays intentional rather than accidental.

Keyboard navigation: the marketing site and app are usable from the keyboard, with a skip-to-content link at the top of every public page so keyboard users are not forced through the whole menu.

Semantic structure: real headings, labelled form fields, alt text on meaningful images, and status messages announced via ARIA live regions, the foundations screen readers depend on.

Calm by design: no flashing content, no autoplaying video, no aggressive animation. The product brief is literally "calm," which happens to be an accessibility feature.

Large touch targets: primary actions meet the 44px minimum so they are tappable by small hands and unsteady ones alike.

3. Known limitations

Screen readers: the foundations are in place, but we have not yet completed a full VoiceOver / TalkBack pass of every screen in the apps. Some flows will work well; some will be clumsy. This is at the top of the roadmap below.

iOS Dynamic Type: the iOS app does not yet follow the system text-size setting. Pinch-zoom works everywhere as the interim path.

Reduced motion: we keep animation minimal by design, but we do not yet consistently honor the system "reduce motion" preference.

No formal audit yet: we have not commissioned a third-party WCAG audit. We will, once the product surface stabilizes after launch.

4. On the roadmap

A full screen-reader pass (VoiceOver on iOS/iPadOS, TalkBack on Android, NVDA on the web) with fixes for what it finds.

Honoring prefers-reduced-motion across the app.

iOS Dynamic Type support.

A formal WCAG 2.1 AA self-assessment, published on this page.

5. Tell us when something is hard to use

If anything in NestBoard is difficult to see, read, tap, or navigate, for you or anyone in your household, we genuinely want to know. Email hello@mynestboard.com with "Accessibility" in the subject line.

A real person reads every message, usually within a day. Accessibility reports go to the front of the bug queue.

Get the household on the same page.

2 weeks free, all features. Five minutes to set up. Bring whoever you live with.

Start your household See features