Zam!

Accessibility

Accessibility Statement

Zam! is built to be usable by as many people as possible. Accessibility is part of how we review new pages, product flows, forms, navigation, and account features.

Our accessibility target

Zam! targets WCAG 2.1 AA conformance for new landing page elements and product experiences. Where practical, we also review new work against WCAG 2.2 AA guidance.

Because Zam! is still evolving, accessibility work is ongoing. We do not treat this statement as a one-time checkbox, and we do not claim full conformance without a formal audit.

What Zam! actively supports

Keyboard access

Navigation, buttons, links, forms, and key controls should be reachable without a mouse.

Visible focus

Interactive elements should show a clear focus state so keyboard users can track where they are.

Semantic structure

Pages should use meaningful headings, landmarks, labels, and native HTML before custom behavior.

Forms and errors

Forms should include labels, useful instructions, and error messages that explain what needs attention.

Contrast-aware design

Text, controls, and interface states should remain readable across supported themes and screen sizes.

Reduced motion

Motion-heavy effects should respect users who request reduced motion in their system settings.

How Zam! reviews accessibility

For new public pages and major product flows, Zam! checks the areas most likely to block real use.

  • Keyboard-only navigation
  • Focus order and focus visibility
  • Color contrast
  • Form labels and validation messages
  • Reduced-motion behavior
  • Screen-reader-friendly structure where applicable
  • Mobile viewport behavior and text wrapping

Known limitations

Zam! is currently in active development. Some beta product areas may still need accessibility review, especially newly added settings, sync, billing, and account-management flows.

When we find an issue, we prioritize fixes that block sign-in, budgeting, billing, account access, or support.

Report an accessibility issue

If you run into an accessibility barrier, contact accessibility@zambudget.com.

Helpful details include:

  • The page or feature where the issue happened
  • Your browser and device
  • Any assistive technology you were using
  • What you expected to happen
  • What actually happened
Please do not send recovery keys, magic links, passwords, full card numbers, or private budget exports.

Last reviewed

June 15, 2026