Accessibility statement

Last updated: June 3, 2026

Accessibility is part of doing this well, not a checkbox we bolt on at the end. We design and build both this website and our apps to work for people who navigate with a keyboard, use a screen reader, prefer reduced motion, need larger text, or rely on high contrast.

Our conformance target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. Accessibility is ongoing work: as we add features we test against this target, and we treat accessibility regressions as bugs.

What we do

• Keyboard navigation. Every interactive element is reachable and operable with a keyboard, menus close with Escape, and a “Skip to content” link lets you jump past the navigation.
• Visible focus. A clear focus indicator follows your position as you tab through the page.
• Screen reader support. We use semantic HTML and landmarks, label controls and icons for assistive technology, and announce status changes (like copying a code) without moving your focus.
• Reduced motion. When your system requests reduced motion, we disable non-essential animation, smooth scrolling, and auto-playing video.
• Contrast and color. We target WCAG AA contrast and never rely on color alone to convey meaning.
• Light and dark themes. A real theme toggle, plus support for browser zoom and resizable text, so you can read comfortably.
• Multiple languages. The site is available in several languages, with the page language exposed to assistive technology.

Why we don’t use an accessibility overlay

You won’t find a floating “accessibility” widget on our site. Third-party overlays don’t fix underlying accessibility issues, and they can interfere with the screen readers, magnifiers, and browser settings you already use and trust. We’d rather do the real work in the site itself and let your own tools do what they do best.

Our apps

Feather and Zap are native Windows apps and support the accessibility features built into Windows, including Narrator, NVDA, and JAWS, keyboard navigation, high-contrast themes, and display scaling. You can find details in our system requirements.

Known limitations

We’re honest about where we’re still improving. A few areas may not yet fully meet our target:

• Some product demo media (such as animated theme previews) auto-animate. We’re moving these to formats that respect your reduced-motion preference.
• Parts of the purchase flow are handled by our payment processor (Lemon Squeezy), whose checkout we don’t fully control.

If something here is blocking you, please tell us. We’ll prioritize a fix and, where we can, help you complete what you were trying to do in the meantime.