Accessibility statement

Last updated: 6 October 2026. The Hebrew version prevails.

Our commitment

UseTimer (https://usetimer.app) aims to be usable by everyone, including people with disabilities, in line with the Israeli Equal Rights for Persons with Disabilities Law (1998) and its Service Accessibility Regulations (2013).

Accessibility goal and verification scope

We are working towards Israeli Standard IS 5568 and WCAG levels A and AA. This is a commitment to improvement, not WCAG certification or a claim that every AA requirement has been achieved throughout the service.

On 5 October 2026, the account, plans and accessibility statement pages were checked locally in Chromium and Firefox using automated axe-core checks, keyboard navigation and layouts at 390 and 1440 pixels wide. Signed-in account and plan screens used synthetic data, without purchases or changes to a real account. Representative dark-mode colours and doubled text size were also checked by doubling each element’s computed font size in an automated browser test; this simulates text resizing, not a full browser-zoom test of the service.

An earlier local assessment on 5 October 2026 covered account, plans and statement pages before the redesign. On 6 October, design 0.9 received focused Chromium checks on desktop and narrow layouts, Hebrew/English, light/dark, keyboard navigation, simulated text resizing, contrast and axe-core. Firefox coverage was limited: some checks used a test server and some rendered source files with synthetic API responses. Test-environment resource-loading failures remain recorded; this does not establish Firefox network-path or whole-service acceptance.

Changes on the checked pages

• A skip-to-main-content link and focusable target, including on account and plans pages.
• Semantic content structure, labelled account fields and visible keyboard focus.
• Text status and error messages on account and plans pages.
• Layouts that accommodate narrow screens and resized text; this does not establish coverage of every screen.
• Language and direction defined for the Hebrew and English statement.

Known limitations and exclusions

• Automated checks cannot detect every accessibility barrier. A complete manual assessment with screen readers, people with disabilities or physical devices has not been completed.
• The local checks do not verify real sign-in, email delivery, Fiduso payment or third-party accessibility. We do not claim testing in every browser, including Edge and Safari.
• Report screens were checked in selected states; not every chart, export or API-documentation view has been assessed. PDF tagging and complete screen-reader alternatives for charts have not been verified.
• The current downloads version is release candidate 0.9.3-rc.1. Current checks cover source-level contrast, 78 JVM unit tests, lint with 0 errors and 12 warnings. The desktop packages have been rebuilt. Linux passed 13/13 CTest groups (71 Qt tests and 6 Python tests), plus offscreen and ldd checks; Windows has static PE dependency-closure checks only. This does not establish full GUI runtime acceptance, with no new phone or Windows runtime test. Prior 0.9.0-rc.1 functional testing used a Samsung SM-A366B phone, a Windows 11 virtual machine and an isolated Linux X11/Openbox environment. These historical checks are not runtime proof for 0.9.3-rc.1. Android is signed; Windows is unsigned. These are not complete native accessibility assessments; TalkBack and KDE Wayland were not checked in the prior run and remain unverified for the current version.
• User-entered or imported content may introduce accessibility barriers.

We continue to improve accessibility. If you encounter a barrier, contact us so we can investigate and offer assistance or an alternative way to obtain the information.

Physical access

UseTimer is an online-only service with no office open to the public.

Contact the accessibility coordinator

Avi Ezra, [email protected]. Please include the page address, a description of the problem, what you were trying to do, and the browser and assistive technology you used. We will reply as soon as possible.