accessibility statement

seen&heard is built to be readable, navigable and usable by as many people as possible - including people who use assistive technology, people with motor or cognitive differences, people with low vision and people who simply find dense interfaces hard to be inside.

we treat accessibility as part of the design, not an addition to it.

seen&heard targets conformance with WCAG 2.1 level AA (the international standard for web accessibility) and the requirements of the Israeli regulation Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) 5573–2013, in line with the Israeli standard IS 5568.

we are working towards full conformance. some surfaces of the platform are still in progress, and we name those honestly below.

• semantic HTML structure throughout
• keyboard navigation for all interactive elements
• visible focus indicators on links, buttons and form controls
• sufficient color contrast for body text and interactive elements
• text scaling without breaking layout up to 200%
• descriptive alt text on functional images
• ability to navigate the canvas without dragging - keyboard arrows and skip controls are supported
• close-on-escape behaviour for all overlays and popups
• the mood-color overlays do not encode information by color alone - mood is also named in text

we are still improving the following:

infinite canvas panning is gesture-led and may be difficult for some users. a keyboard-friendly jump to next post control is being implemented.

animated entrances for cards and the confirmation screen use motion that some users find disorienting. a reduce motion setting (via the operating system's prefers-reduced-motion preference) is honoured throughout and animations are minimised when it is on.

mobile screen reader testing is ongoing as the mobile build is finalised.

if any of these limitations affect your experience, please tell us. we are listening.

questions, requests and reports about accessibility on seen&heard can be sent to the accessibility coordinator:

if something on this platform is not usable for you, we want to know. include:

• a description of the problem
• the page or surface where it happened
• the device, browser and any assistive technology you were using
• a screenshot or screen recording, if one is possible

we will respond, investigate and report back on what we find.

this statement will be updated when the platform changes meaningfully or when we receive feedback that improves it. the last updated date at the top of the page reflects the most recent revision.