Accessibility
Built in, not bolted on.
TextGopher™ is meant to work for everyone — with a keyboard, a screen reader, or any assistive technology. We design for access from the first line of markup and test as we build.
Comfort settings apply instantly and save on your device only. Nothing is sent anywhere.
What we build in
Access is a design requirement.
Every page and screen is built to these baselines, then checked before it ships.
Semantic structure
Real headings, landmarks, and labels so screen readers can navigate the page the way it’s meant to be read.
Full keyboard access
Navigation, tabs, menus, and expandable content all work without a mouse, in a logical order.
Visible focus
Clear, high-contrast focus states so you always know where you are on the page.
Readable contrast
Text and interface colors are chosen to stay legible, and can be strengthened further on demand.
Respects your preferences
We honor reduced-motion and high-contrast system settings, and layer optional comfort controls on top.
Reflows on any screen
Layouts adapt from phone to desktop without horizontal scrolling or content getting cut off.
On this site
Comfort settings, on your terms.
Optional adjustments you can turn on right now. They apply instantly and stay on this device — we never send them anywhere.
Larger text
Increase text size across the page.
Higher contrast
Darken text and strengthen borders and focus.
Reduce motion
Turn off nonessential transitions and animation.
Emphasize links
Underline links and strengthen focus and hover.
How we test
Effort you can check our work on.
- Automated accessibility checks run against pages as part of our build.
- Manual keyboard passes on new and changed screens — every interactive element, in order.
- Screen-reader review of key flows, including sign-in, pricing, and the opportunity dashboard.
- Color and contrast are verified against WCAG 2.1 AA thresholds.
- Accessibility issues are logged and prioritized as bugs, not backlog.
Scope & limitations
Honest about where we are.
Accessibility is ongoing work, and we’d rather be straight with you than overclaim.
- This statement covers the TextGopher™ marketing site and customer dashboard.
- Some steps rely on trusted third parties — for example, secure checkout runs on Stripe, whose experience we don’t control.
- We target WCAG 2.1 Level AA. This page describes our approach and effort; it is not a claim of formal certification against a specific standard.
Something hard to use? Tell us.
If any part of TextGopher™ gets in your way, we treat it as a bug to fix. Tell us what you were trying to do, what got in the way, and the device or assistive technology you were using — and we’ll work with you on an accessible way through in the meantime.
We read every accessibility report and prioritize fixes.