Accessibility Statement

Stublet is an app and website for finding sublets in Israel. We believe that finding a temporary place to live — or subletting your own apartment while you're abroad, on reserve duty, or away for a semester — should be open to everyone, including people with disabilities.

We work to make the service accessible in line with Israel's Equal Rights for Persons with Disabilities (Accessibility Adaptations to Service) Regulations, 5773-2013.

We want to be straightforward about this: we are not claiming that the service currently meets the standard in full. No comprehensive accessibility audit has been completed that would let us claim that. What we do state here is what we have already done, what is still missing, and how to reach us when something doesn't work — and this document is updated as we make progress.

The standard: Israeli Standard SI 5568 Part 1, September 2023 edition — "Web content accessibility guidelines". The standard is identical to the W3C's WCAG 2.0 (11 December 2008), with national modifications.

Standard text: https://www.gov.il/he/departments/legalInfo/israeli_accessibility_standards_pdf

WCAG 2.0: https://www.w3.org/TR/WCAG20/

Conformance level we're working toward: Level AA — the level required by regulation 35A(a).

Please note: the Israeli standard is based on WCAG version 2.0, not 2.1 or 2.2. We say so explicitly so as not to claim conformance with a version the standard itself does not adopt.

What this statement covers:

• The stublet.app website, all pages
• The Stublet app for iOS and Android

Technologies this statement relies upon:

• On the web — HTML, CSS and JavaScript, in current browsers
• In the app — React Native on top of the operating system's accessibility layer: VoiceOver on iOS and TalkBack on Android. There is no dedicated Israeli standard for mobile apps, so under regulation 35C(b) the criteria are applied as far as the operating system allows, across two common operating systems

Statement date: 26 July 2026.

These adaptations are already in place:

• Hebrew and full RTL — the entire interface is built for right-to-left reading, not a translation pasted onto a left-to-right layout
• Dark and light modes — colours follow the user's system preference, for anyone sensitive to contrast or screen brightness
• Screen reader support — interactive components carry a role (accessibilityRole), a readable name (accessibilityLabel) and a state (accessibilityState), so VoiceOver and TalkBack announce a button, link or checkbox with its meaning rather than as an anonymous element
• Touch targets — key controls are designed to a minimum 44-point touch target
• Legal text — the Terms and Privacy consent text meets a contrast ratio of at least 4.5:1, in both light and dark mode
• Skip to content — the website has a "skip to content" link that becomes visible during keyboard navigation
• Page structure — the site's information and legal pages are built from hierarchical headings and in-page navigation links

We are deliberately not presenting a blanket list of criteria "passed". These are the adaptations we can actually point to.

We would rather list what isn't right yet than make a sweeping claim that isn't accurate. As at the statement date:

• No comprehensive accessibility audit of the app against every criterion in the standard has been carried out yet. One is in progress, and this statement will be updated to reflect it
• Colour contrast — we have identified places in the interface where secondary text (for example listing details in list view, helper text) does not reach the required contrast ratio. This is being fixed in stages; the legal and consent text has already been corrected
• Keyboard navigation on the website — not every link on the site has a sufficiently clear focus indicator during keyboard navigation
• User-uploaded content — listing descriptions and photos are written and uploaded by hosts themselves. We are not responsible for the text they write, but we are responsible for providing accessible infrastructure for it (regulation 35B). We have added an image-description field for every listing photo, offered to the host as they create the listing. Filling it in is optional and up to the host, so some photos will have no human-written description — in that case the listing title is announced instead
• Maps — the map view is built on Google and Apple map components whose accessibility support is limited. Wherever a map is shown, the substantive information (city, neighbourhood, distance) is also presented as text

If you hit an accessibility barrier that isn't listed here, please tell us. A report like that is the fastest way for a problem to reach the top of the fix list.

Accessibility contact: Nadav Keynan, founder of Stublet.

Email: [email protected]

To be clear: Stublet employs fewer than 25 people and is therefore not required to appoint an accessibility coordinator under regulation 91(a). The contact above is a real point of contact for anything accessibility-related, not a statutory appointment.

How to report:

• Email [email protected] with "Accessibility" in the subject
• Describe what you were trying to do and where you got stuck — for example "search screen, TalkBack screen reader, the filter button isn't announced"
• Tell us which operating system and which device or browser, and if you use assistive technology, which one

What happens next:

• We'll acknowledge your message
• We'll aim to fix the problem, or offer an alternative way to get the service, within 14 business days
• If the fix is complex and needs longer, we'll tell you the timeline and what the interim alternative is

Under regulation 35A(d), a service provider has up to 60 days from receiving notice to remedy an accessibility defect. Our 14-business-day target is a voluntary commitment, stricter than the regulations require.

If you've contacted us and haven't had a satisfactory response, or you'd rather go to an external body, you may contact the Commission for Equal Rights of Persons with Disabilities at the Ministry of Justice.

The Commission is the body empowered to handle complaints about failure to meet accessibility obligations under the Equal Rights for Persons with Disabilities Law, 5758-1998.

• Commission website: https://www.gov.il/he/departments/moj_disability_rights
• Public enquiries centre: *6763

The Commission's current contact details are published on its own website — we recommend checking there before getting in touch.

Your right to contact the Commission does not depend on contacting us first, and is not affected by having done so.