KesherWeb accessibility
Club members are all ages. Somebody in your club reads with the text size turned right up, and somebody else uses a screen reader. Kesher should work for them.
Where we are
What is actually true today
We aim at WCAG 2.1 Level AA. We have not had an independent audit, so this is a statement of intent and current practice rather than a certification — claiming a conformance level nobody has checked would be worth nothing.
Keyboard
Every control is reachable by keyboard, and focus is visibly outlined rather than hidden.
Text size
Type is set in relative units, so the app follows your device's text-size setting instead of overriding it.
Contrast
Colours are chosen for contrast, and a club's own palette is checked at runtime so text stays legible on whatever background they pick.
Reduced motion
If your device asks for reduced motion, animation and smooth scrolling switch off.
Light and dark
Pages follow your system theme rather than forcing one on you.
Structure
Real headings, labelled form fields and described images, so a screen reader can make sense of a page.
Being honest about it
Where we know we fall short
No independent audit yet. Photos uploaded by members carry whatever caption the poster wrote, so alternative text is only as good as what officers and members type. Some admin tables scroll sideways on a small phone. And parts of the officer screens have had less accessibility attention than the member app.
We would rather list these than imply the whole thing is finished.
Tell us
If something blocks you, that is a bug
Not a feature request — a bug, and we will treat it as one. Write to us from the contact page, say what you were trying to do and what got in the way, and a person will read it.
If you use assistive technology, telling us which one helps us reproduce the problem.