Accessibility Statement.
In plain language.

EngineeringID is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards to achieve this.

Accessibility is part of our definition of done. New features must meet our internal accessibility checklist before they ship.

• Conformance target: Web Content Accessibility Guidelines (WCAG) 2.2 Level AA
• Conformance status: Partially conformant. Some content does not yet fully meet AA — see Known Limitations.
• Section 508 (US): Aligned via WCAG 2.2 AA, which satisfies the Revised 508 Standards.
• EN 301 549 / EAA: Aligned for the web software clauses (Chapter 9 — Web). A formal accessibility statement is published below per Article 7 of the EAA / Web Accessibility Directive template.
• VPAT / ACR: A current Voluntary Product Accessibility Template (VPAT 2.5) Accessibility Conformance Report is available on request — email [email protected].

• Keyboard navigation: every interactive element is reachable and operable via keyboard. A "Skip to main content" link is the first focusable element on every page.
• Visible focus: a 2px focus ring is shown on every focusable element using the active theme color. High-contrast users get a 3px ring.
• Semantic structure: ARIA landmarks (banner, navigation, main, contentinfo), a single <h1> per page, and a logical heading hierarchy.
• Forms: every input has an associated label; errors are announced via role="alert" and linked through aria-describedby; layout is reserved so error messages don't shift content.
• Live regions: flash messages and toasts use role="status" / role="alert" with aria-live so screen readers announce them.
• Reduced motion: the platform honors the prefers-reduced-motion media query — animations, transitions, and smooth scrolling are minimized.
• User accessibility preferences: each account can set text size (default / large / xl), icon size (default / large), and a high-contrast theme override. These settings persist across sessions and devices. Configure them at Settings → Accessibility.
• Internationalization: interface available in 11 languages including right-to-left support for Arabic and Hebrew. The page lang and dir attributes are set automatically.
• Color contrast: themes are designed against a 4.5:1 minimum (3:1 for large text and UI components). The high-contrast preference raises this further.
• Resizable text: content reflows up to 200% zoom without horizontal scrolling on standard viewports.

• Stamp / signature editor: the visual stamp editor relies on direct manipulation. A keyboard-only equivalent for fine positioning is in progress; today, batch sealing with saved templates provides a fully keyboard-accessible alternative path.
• Embedded PDF viewer: third-party PDF rendering may not expose all controls to assistive technology in older browsers. Documents can always be downloaded and opened in your assistive tech of choice.
• Complex data grids: some admin tables (audit logs, verification queue) use virtualization that may interact imperfectly with screen-reader virtual cursors. We provide CSV export as a parallel path.
• Marketing-page motion: a few hero illustrations rely on parallax. prefers-reduced-motion disables these.
• Third-party widgets: Stripe Checkout and Calendly are embedded as-is from those providers. We track their published accessibility statements and surface known gaps to our customers on request.

If you encounter a barrier not listed here, please tell us — see Feedback & Contact below.

• Screen readers: NVDA on Windows, VoiceOver on macOS and iOS, TalkBack on Android.
• Browsers: latest two versions of Chrome, Firefox, Safari, and Edge.
• Magnifiers and zoom: browser zoom 100–400%, Windows Magnifier, macOS Zoom.
• Voice control: Voice Control on macOS / iOS, Dragon NaturallySpeaking on Windows (smoke-tested).
• Automated tooling: axe-core in CI on every pull request; Lighthouse accessibility audits run weekly.

Please contact us if you encounter accessibility barriers on EngineeringID or need content in an alternative format.

• Email: [email protected]
• Subject line: please use "Accessibility Feedback" so it routes to the right team.
• Response time: we aim to acknowledge accessibility reports within two business days and provide a substantive response within ten business days.
• What to include: the URL of the page, what you tried to do, what happened, the assistive technology and browser you used, and the operating system version.

• United States: you may file a complaint with the U.S. Department of Justice's Civil Rights Division under the Americans with Disabilities Act (ADA).
• European Union: each Member State designates an enforcement authority under the European Accessibility Act (Directive (EU) 2019/882). Contact details for your country are listed by the European Commission.
• Canada: complaints under the Accessible Canada Act can be directed to the Accessibility Commissioner at the Canadian Human Rights Commission.
• United Kingdom: the Equality and Human Rights Commission (EHRC) enforces the Public Sector Bodies Accessibility Regulations 2018 and the Equality Act 2010.

• Preparation method: self-assessment against WCAG 2.2 AA combined with automated testing (axe-core, Lighthouse) and manual screen-reader testing on the most-used flows.
• Date prepared: April 26, 2026.
• Last reviewed: April 26, 2026.
• Next review: at minimum every 12 months, or sooner if material platform changes warrant.
• External audit: a third-party WCAG 2.2 AA audit by an independent firm is planned. This statement will be updated to reflect the audit's findings and a Voluntary Product Accessibility Template (VPAT 2.5) will be published. TODO: schedule external audit (Deque, TPGi, or Level Access) and link the resulting VPAT here.