Accessibility Statement — TLV Next (tlvnext.com)

Statement date: 18 September 2026 · Last updated: 2 October 2026 · Version 0.8

1. Our commitment

TLV Next is a free public map run by one person. We want as many people as possible to be able to use it, including people who use a keyboard, a screen reader, magnification or high contrast. This page says honestly what works today, what does not yet, and how to reach us.

2. Legal basis and whether an exemption applies

In Israel, web accessibility is governed by the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 5773-2013, regulation 35 and following. They require internet services to the public to meet Israeli Standard 5568 (based on WCAG 2.0) at level AA and to publish an accessibility statement in a prominent place listing the adjustments made and a contact for reporting problems.

The regulations exempt an operator whose annual turnover is under NIS 100,000 (regulation 35 exemptions for small turnover; "turnover" is defined by reference to VAT transactions, income-tax income or family income and allowances). This site earns nothing and is run by an individual; the operator's understanding is that the small-turnover exemption applies. We publish this statement and pursue accessibility voluntarily, not because we claim to be fully bound.

The regulations also state that a provider is not responsible for adjustments in content not created by it, and contain an exemption for maps. The 3D map is the site's own, so we do not rely on the map exemption for it, but the aerial photographs and municipal geometry are third-party content.

3. What is accessible today

• Keyboard. Everything on the screen except the 3D map itself can be reached and operated from the keyboard: the address box, its clear button and its suggestion list (Tab, arrow keys, Enter to choose, Escape to close); on a phone, the folded search button that reopens the box; the "today / coming" mode switch; the legend-and-information button and, inside it, the aerial-year slider; the hour button, the hour slider, the date button and the button that closes the slider; the language button; the share and "my location" buttons; and the About dialog — which opens with focus on its close button, closes with Escape and returns focus to the link that opened it. Escape also closes an open card, dismisses a note showing a link to copy, and folds the legend sheet when focus is in it, putting focus back on the button that opens it. Every control shows a visible focus ring that measures at least 3:1 against what surrounds it: a solid outline on the address box and on the controls in the dark panels, and a two-tone ring, one dark line and one light, on the buttons over the map and on the map itself, so that one of the two lines stands out on any part of the photograph. The map layer adds no Tab stop of its own. The hour slider announces its value as a time ("18:30"), not as a number, and the aerial-year slider announces the year it shows.
• Address search. The search box is an ARIA combobox: the suggestions are a listbox, the arrow keys move through them, the highlighted suggestion is announced to a screen reader, and the number of results is announced in a polite live region.
• Text and contrast. Interface text uses system fonts at readable sizes. Contrast was measured on the rendered page on 24 September 2026, where the translucent panel shows the map through it: the main text is far above the AA requirement of 4.5:1, and the secondary grey measures 4.6 to 5.5:1, just above it. The smallest grey does not reach it, and is listed below as a known gap.
• Right-to-left. The interface is built for Hebrew (RTL) and English (LTR) with correct text direction.
• Structure. Headings, labels and buttons carry text names; controls that only show an icon have an ARIA label.
• Mobile. On a phone the controls take one row at the top and one at the bottom, and the search box folds into a button once the map is moved. The mode switch and the share and my-location buttons are at least 44 pixels in both directions, checked by automated tests. The site works at narrow widths and in landscape without horizontal scrolling. A card can be dragged down to close it, and always also has a close button.
• No motion traps. Nothing flashes; no content auto-plays. The sliding of cards and panels is switched off when the device asks for reduced motion.

4. What is not yet accessible

• The 3D map itself. The map is drawn on a WebGL canvas. It has no text alternative, cannot be read by a screen reader, and it gives no spoken feedback when the camera moves. The camera itself can be moved from the keyboard: once the map has focus (Tab to it), the arrow keys pan, + and − zoom, and Shift with the arrow keys rotates and tilts. A card can be opened from the keyboard in two ways: a searched address opens the card of its building, and a list of the permits and plans in view, in the legend panel, opens the card of each. The list shows up to the 30 nearest the centre of the view; move or zoom the map to reach the others. A building with no address of its own can still be opened only by clicking or tapping it. The map itself still gives a screen reader nothing to read: this is now the main gap.
• No map without WebGL2. The map needs WebGL2, a graphics feature of the browser and the device. Where it is not available (for example with hardware acceleration switched off, or on an older device), the map is not shown at all: the page says so in words, and the address search, the legend, About and the language switch keep working.
• The smallest grey text. The search placeholder, the disabled "coming" label, the notes in the legend, the small labels in cards (such as "year built") and the kind line at the top of a card are drawn in a grey measured at 2.6 to 3.1:1 on the rendered page (the placeholder 2.2 to 2.7:1), below the AA requirement of 4.5:1 for text at that size. This is a known, unfixed gap.
• Screen-reader path to permit details. A text list of permits and plans for a searched address, usable without the map, is planned but not built.
• Colour meaning. A standing building's colour shows the year it was built, and in the 3D view only the colour shows it. The legend explains the scale, and a building's card gives the year in words where it is known. What exists, what is permitted and what is planned also differ by shape (solid, see-through, a wireframe, a boundary on the ground), not by colour alone.
• Evidence text from PDFs. Quoted regulation text is shown as read by the AI and may not be perfectly structured.
• Aerial photographs carry no description beyond the year.

5. Browsers and assistive technology

The site is built and automatically smoke-tested in Chromium (Chrome and Edge) and in WebKit, the engine Safari uses, at a desktop size and at an iPhone size. It is expected to work in current Firefox, on desktop and on Android, but no systematic testing in Firefox is recorded. No testing with a screen reader has been carried out yet: the sections above describe the interface as built and as measured in the code, not as tried with assistive technology.

6. Report a problem or ask for an accessible alternative

If something does not work for you, or you need the information about a specific address in an accessible form (for example, a plain text list of permits and plans), write to tlvnext@bdbd.net — or, if you would rather not use email, open an issue on the project's issue tracker on GitHub — and say which page, which browser and which assistive technology you use. The operator is a single volunteer and will reply as soon as practical, aiming within 14 days.

7. Accessibility coordinator

Not required for an individual operator with no employees. Contact person for accessibility: the operator, reachable at tlvnext@bdbd.net or through the project's issue tracker on GitHub.

8. Exemptions and adjustments

Voluntary compliance; small-turnover exemption under regulation 35 believed to apply (see section 2). No adjustment has been granted or requested by a service accessibility authoriser.