Accessibility
NeuralClaim exists to make invention accessible to people the system usually leaves out. Disabled inventors are part of who we build for, so accessibility is not a compliance afterthought for us. It is the same promise the rest of the product makes: your circumstances should not decide whether your idea gets taken seriously.
What we aim for
We work to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the standard most widely used to judge whether a website is usable by people with disabilities. We treat that as the bar to clear, and we keep working toward it as the product grows.
What is built in
Accessibility is part of how the product is built, not bolted on after:
- The app is operable by keyboard, with a clearly visible focus indicator. Dialogs move your focus inside when they open, keep it there, and return it to where you were when they close.
- Controls carry proper labels for screen readers, and new replies in a conversation are announced as they arrive.
- A built-in Accessibility panel in Settings lets you reduce motion and increase contrast, saved on your device. We also honor your operating system’s reduced-motion setting automatically.
- We test with automated tools, including Google Lighthouse and the axe accessibility engine, and we review by hand as we build.
Honest about where we are
We are a small, early company, and we are not going to claim to be “certified” or “fully compliant.” Accessibility is never finished: the app changes often, and automated tools cannot catch everything a real person using assistive technology would. We test continually, we fix what we find, and where some part of NeuralClaim is not yet fully usable for you, we want to hear about it so we can put it right.
Tell us, and get help
If you run into a barrier anywhere in NeuralClaim, or you need something in a different format, email hello@neuralclaim.ai and tell us what happened and what would help. We read every message, we will work with you to find a way through in the meantime, and we treat accessibility problems as real bugs, not edge cases.