Accessibility
Everyone should be able to use these tools.
We aim for Get Solve Spring to be usable by as many people as possible, including people who use screen readers, keyboard navigation, magnification, or voice control. We design with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA in mind.
What we've done
- Every calculator input has a visible label, and errors are announced and explained in text
- All features work with a keyboard, with a clearly visible focus outline
- Results are announced to screen readers when they update
- Text and controls meet contrast guidelines, and color is never the only signal
- Pages use headings, landmarks, and a "skip to main content" link
- Layouts adapt from small phones to large screens, and text can be enlarged
- Animations are minimal and respect the "reduce motion" setting
Known limits
We're a small site and test as we build. Some pages may still have issues we haven't found.
Report a barrier
If something doesn't work for you, please tell us which page and what happened. Email hello@getsolvespring.com or use the contact form. We'll do our best to fix it and, in the meantime, help you get the answer you need.