Accessibility Statement
How Solvebility approaches accessibility across our calculators, guides, and the rest of solvebility.com — and how to reach us if something isn’t working for you.
Our approach
Solvebility runs on a mix of custom calculators and standard WordPress content, and we try to catch accessibility problems before a tool ever goes live rather than patching them afterward.
- New calculators get a keyboard-only pass and a screen reader check before publishing, not just a visual review.
- Input fields, sliders, and result panels are built with labels and ARIA roles from the start, not bolted on later.
- We re-audit older tools on a rolling basis as we update them, since a handful were built before this process was in place.
Conformance status
The Web Content Accessibility Guidelines (WCAG) set three conformance levels — A, AA, and AAA. Solvebility targets WCAG 2.1 Level AA and is currently partially conformant: most of the site meets this bar, but some calculators and embedded content don’t yet, and we’re working through the list rather than treating it as finished.
Tell us what’s not working
If a calculator, form, or page gives you trouble with a keyboard, screen reader, or any other assistive technology, we want to know about it. Send us the page address and a quick description of what happened — that’s usually enough for us to reproduce and fix it.
Technical specifications
Accessibility on Solvebility depends on how well these technologies work with your browser and any assistive tools installed on your device:
Known limitations
We haven’t solved everything yet. Here’s what we know about, in plain terms:
How we check our work
We combine manual testing — keyboard-only navigation, spot checks with a screen reader — with automated scanners such as WAVE and axe. Neither approach catches every issue on its own, which is part of why the feedback channel above matters as much as the testing does.
This statement was last reviewed in July 2026 and applies to solvebility.com.