Dyslexia
A readable font, wider letter and word spacing, and a guide that holds the line you are on.
IncluApp gives the other four a way through in one tap — their profile, their controls, their language — without a ticket, a rebuild or a call to your developer.
Accessibility is not a cost line. It is the part of your funnel nobody is measuring.
Named for people, not features.
Nobody has to know which switch to hunt for.
A readable font, wider letter and word spacing, and a guide that holds the line you are on.
Motion off, a reading guide on, and the rest of the screen kept quiet.
Larger text, stronger contrast, a bigger cursor, titles and links picked out.
Animation stopped, auto-play blocked, the page held still.
Structure highlighted, one line in focus, distractions removed.
Monochrome rendering with motion switched off.
For the visitor who wants to tune it.
A profile sets these in one go. Any of them can still be moved by hand.
In their words, not yours.
A control panel in a language someone cannot read is one more barrier. IncluApp opens in your visitor's own language, and the list keeps growing.
Your accessibility statement is published the same way, localised for whoever asks to see it.
Give them the interface this afternoon. One line of code, any stack, flat licence from $99 a year.
Questions Buyers Ask.
Six one-tap profiles and the individual controls behind them, covering contrast, text, highlighting, cursor, navigation, media and motion. The visitor picks what they need and your page adapts around them.
No. A profile does the work. One tap on Dyslexia or Epilepsy applies the whole set of controls that profile needs, and anything can still be adjusted by hand afterwards.
Yes. The panel opens in the visitor's own language, with more languages added over time, and your accessibility statement is localised the same way.
No. Nothing is fetched on an ordinary page view. The interface loads on demand, so the weight only exists for the visitor who opens it.