Accessibility
Accessibility Statement
Last examined: 23 July 2026
TechNiv is committed to making this website usable by everyone, regardless of ability or technology. This statement follows the Equal Rights for Persons with Disabilities Law, 1998 and the Equal Rights for Persons with Disabilities Regulations (Service Accessibility Adjustments), 2013 — and says plainly what's been done, what's been tested, and what hasn't.
Standard followed
This site targets:
- Israeli Standard 5568 (IS 5568) — the local adoption of WCAG 2.0 at Level AA.
- Equal Rights for Persons with Disabilities Regulations (Service Accessibility Adjustments), 2013 — Chapter C, covering service-providing websites.
Accessibility features on this site
- Keyboard navigation. Every link and button is reachable and operable by keyboard alone, in a logical order, with a visible focus outline.
- Skip link. A "Skip to main content" link is the first focusable element on every page.
- Reduced motion respected. Anyone with
prefers-reduced-motionenabled gets a static page — CSS animations and the scroll-progress bar are disabled, and the auto-playing demo clip is paused automatically instead of looping. - Video is pausable and described. The one auto-playing clip has a visible Pause/Play button and an accessible name plus a linked text description, so it's never a moving element a visitor is stuck with.
- No-JS fallback. If JavaScript fails to load, all content is immediately visible rather than stuck hidden behind a scroll animation.
- Decorative elements hidden. Background effects and icons are marked so assistive technology skips them; only purely decorative graphics use
aria-hidden— the demo video itself is exposed with a label and description, not hidden. - Color contrast. Text and interactive elements meet a minimum 4.5:1 contrast ratio for body copy, 3:1 for large text and UI components.
- Responsive by default. Content reflows for screen size and remains usable at up to 200% zoom.
Known limitations
We'd rather publish the limitations we actually know about than a generic disclaimer. As of the date above:
- Screen readers have not been manually tested. Testing to date is automated (axe-core) only — the site has not yet been manually verified with NVDA, JAWS, or VoiceOver.
- Mobile menu keyboard behavior. The mobile menu opens and closes correctly by mouse or keyboard, but until recently pressing Escape did not close it — this has now been fixed.
- Third-party resources. Web fonts are loaded from Google Fonts and are not under our direct control.
- No independent certification. This site has not yet been reviewed by a licensed accessibility auditor (מורשה נגישות).
If you hit a barrier that isn't listed here, please tell us — see the contact details below.
Physical accessibility
TechNiv does not receive the public at a physical office. Services are delivered entirely remotely — by WhatsApp, email, and video call — so physical premises accessibility does not apply.
How and when this was tested
So the claims above can be checked rather than taken on trust:
- Date of last examination: 23 July 2026.
- Automated testing: axe-core, run against the English homepage, Hebrew homepage, and this statement, at desktop (1280px) and mobile (375px) widths, checked against WCAG 2.0 A/AA and WCAG 2.1 AA. 0 automated violations found at either width on the date above. Automated tools alone cannot certify full WCAG compliance — see manual review below.
- Manual review: a manual pass (DOM/semantics mapping, keyboard interaction, responsive reflow at 640px simulating 200% zoom) was carried out on 23 July 2026, which is what surfaced the video pause-control and Escape-key issues fixed on this date. Full manual screen-reader testing (NVDA/JAWS/VoiceOver) has not yet been performed.
- Not yet performed: manual screen-reader testing and independent certified audit by a licensed accessibility consultant (מורשה נגישות).
This examination was carried out internally by the site's own operator. A prior version of this statement contained inaccuracies (claiming English-only when a Hebrew version exists, and claiming the demo video was fully disabled by reduced-motion when only its CSS animations were) — both were corrected on the date above to match the site as it actually behaves.
Accessibility coordinator
As a one-person operation, I handle accessibility requests, complaints, and suggestions directly:
Report an accessibility issue
If something on this site is a barrier for you, please get in touch using the details above. To help resolve it quickly, include:
- The page where you hit the issue
- What you were trying to do, and what went wrong
- The browser, device, and assistive technology you were using, if any
Questions about accessibility?
Happy to help, and to keep improving this for everyone.