Built for members of every age and ability

Hineni's design choices answer the WCAG 2.2 criteria that bear most directly on signing in, tapping and filling in forms.

• Members sign in with an emailed link. Criterion 3.3.8 rules out memory or retyping tests at sign-in, and the World Wide Web Consortium (W3C) lists email links as a sufficient technique.
• Primary buttons and answer rows measure at least 44 by 44 pixels. Criterion 2.5.8 sets 24 by 24 pixels, and W3C advises the larger enhanced size for important controls.
• Members never retype what they already gave. Criterion 3.3.7 asks that earlier answers be filled in or selectable, so Hineni carries name, phone and email forward.
• Help appears in the same place on every screen, naming the volunteer's coordinator, as criterion 3.2.6 asks.

Hineni designs for older adults because W3C notes that their needs overlap with disability needs, so a screen that works for them works for more members. Screens are checked with a keyboard, a screen reader and 200 percent zoom on a phone, and members can report any barrier they find.

W3C notes that ageing can bring declines in contrast sensitivity, fine motor control and short-term memory. Large tap targets, email-link sign-in and answers carried forward address each of those needs, and usability rounds with volunteers over 70 test them.

Report a barrier through the contact form on the Hineni demo page, and a member of the team that built Hineni will answer you by name. Tell us the screen you were on, what you tried to do and the device or assistive technology you used. A screenshot helps if you can take one.

Members can also tell the lay leader named on their sign-up, who can pass the report to the team. Reports help the team decide which improvements to make first.