Accessibility
Here's what we've actually done to make this site usable with a keyboard or a screen reader — described honestly, not copied from a bigger company's compliance page. This isn't an independently audited or certified statement; it's what our own testing has covered so far.
1. Keyboard navigation
Every menu, dropdown, and modal on this site can be opened, used, and closed without a mouse. A "skip to content" link is the very first thing a keyboard user reaches on any page, letting you jump straight past the navigation bar. The mobile menu and every dialog trap keyboard focus inside themselves while open (so Tab can't silently escape to something hidden behind them) and correctly hand focus back to whatever you opened them from when you close them.
2. Screen reader support
Form errors and success messages are announced automatically as they appear, not just shown visually. Icon-only buttons have real text labels, not just an icon. Buttons that toggle a state — showing a password, expanding a menu — update their own label as that state changes, instead of describing only what they looked like when the page first loaded.
3. Color contrast
Text and interactive borders are checked against WCAG's contrast math, not just eyeballed — one low-contrast border color used across the whole site was found and replaced this way.
4. Tested in a real browser, not just reviewed as code
The items above were verified by actually tabbing, clicking, and reading through the site with keyboard and screen-reader-style tooling — not just checked by reading the markup and assuming it would work.
5. What's not finished yet
A handful of decorative icons on some of our conversion tool pages haven't been swept yet — cosmetic only (a screen reader may read a redundant icon name next to a label that's already there), never a missing label on something you need to interact with. We're working through the rest.
6. What we're aiming for
Our target is WCAG 2.1 Level AA. We're not claiming to be fully there across every page yet, or independently certified — this page will be updated as more of the site is covered.
7. Found a problem?
If something on this site doesn't work with a keyboard or screen reader the way it should, please tell us via the Contact page — real reports are what actually gets fixed, faster than an internal audit alone would find it.