IS 5568 Part 1
Website and application accessibility for public web and app surfaces, including Israel-specific requirements.
Accessibility statement
Equal digital access is part of the agreement workflow.
EEZYDOX aims to provide accessible website, app, signing, and document experiences for people with disabilities. This statement describes the standards we target, the display preferences and features already in place, known limitations, and how to request help.
- Last updated
- May 28, 2026
- Conformance status
- Implementation in progress. We do not claim full conformance until formal audit evidence supports it.
- Next planned review
- November 28, 2026
Standards
Our target is Israeli compliance plus modern WCAG coverage.
EEZYDOX is being built against the Israeli accessibility framework while using WCAG 2.2 AA as a practical engineering target for modern web applications.
IS 5568 Part 2
Digital document accessibility for generated agreements, certified PDFs, evidence packages, and invoices.
WCAG 2.2 AA target
Additional engineering coverage for focus visibility, reduced motion, target size, drag alternatives, and accessible authentication.
Current features
Accessibility foundations already built into the product.
These features are part of the platform baseline and continue to be tested as workflows evolve.
Display preferences
Users can adjust text size, high contrast, readable spacing, link highlighting, reduced motion, and stronger focus outlines in this browser, and drag the accessibility helper vertically if it covers page content.
Keyboard navigation
A global skip link, semantic controls, visible focus states, and route-level keyboard testing are part of the accessibility baseline.
Semantic structure
Pages use landmarks, headings, labels, and accessible names so assistive technology can understand the workflow.
Language and RTL support
The app sets language and direction for English, Hebrew, Arabic, Russian, and any surfaced additional locale.
Reduced motion
Animations and visual effects are reduced when a user has enabled reduced-motion preferences.
Known limitations
Areas still being remediated or audited.
We publish limitations carefully so users can request an accessible accommodation while remediation continues.
- The display preferences are optional browser-level controls. They do not replace assistive technology, individualized accommodations, or formal accessibility remediation.
- Some generated PDFs may be visually accurate before the full tagged-PDF accessibility pipeline is complete. Accessible HTML or document alternatives can be requested.
- BYOC PDF overlay and field-placement workflows are high priority for keyboard and screen-reader review because they include drag, zoom, and visual placement controls.
- Payment, map/autocomplete, media, and other third-party interfaces are reviewed as part of the vendor accessibility audit program.
Digital documents
Accessible documents are part of the product commitment.
EEZYDOX generates legal documents, invoices, certified PDFs, and evidence packages. Our target is selectable text, correct language, meaningful reading order, semantic headings and tables where supported, and accessible alternatives when a PDF limitation is still being remediated.
Need an accessible version?
Contact support with the document type and agreement reference. We will triage the request and provide an accommodation path.
Testing
Accessibility is a release gate for core workflows.
Automated scans catch only part of the problem. EEZYDOX combines automated checks with manual keyboard, screen-reader, mobile, RTL, and document review.
- Playwright and axe smoke scans run on representative public routes and the accessibility widget in LTR and RTL viewports.
- Critical flows are reviewed with keyboard-only navigation before release.
- Formal screen-reader passes are planned for NVDA, VoiceOver, and mobile assistive technology.
- Mobile widths and Hebrew or Arabic RTL layouts are included in manual audit samples.
- Generated PDFs and evidence packages are reviewed for selectable text, language, reading order, headings, tables, and RTL behavior.
Report an accessibility issue or request help.
If you encounter an accessibility barrier or need an accessible version of a document, contact us. We aim to acknowledge accessibility requests within 2 business days and triage them within 5 business days.
Accessibility contact
[email protected]Legal and policy contact
[email protected]Please include
- The page, document, or workflow where the issue occurred.
- Your browser, device, and operating system.
- Assistive technology used, if relevant.
- The expected accommodation or accessible format requested.