Droz
EN FR ES 中文 हिं
Request engagement →
Accessibility · Legal · Last updated 2026-05-21 · v1.0

Accessibility statement.

Droz Technologies is committed to making droz.tech usable by everyone, including people who use assistive technology. This page sets out our compliance target (WCAG 2.1 Level AA), our obligations under Ontario's AODA, the measures we have implemented, and how to report an accessibility issue.

1. Our commitment

Droz Technologies Inc. is committed to providing an accessible website for all users. We design, build, and maintain droz.tech to meet WCAG 2.1 Level AA and to comply with the Accessibility for Ontarians with Disabilities Act (AODA), 2005, including the Integrated Accessibility Standards Regulation (IASR, O. Reg. 191/11).

We treat accessibility as an institutional standard, not a one-time audit. The site's design system, the partials we ship, and the writer-agent checklist each include accessibility requirements at the component level.

2. Standards we target

  • WCAG 2.1 Level AA — the primary technical target. Section 508 (United States) and EN 301 549 (EU) are largely aligned with WCAG 2.1 AA; conformance with WCAG 2.1 AA implies substantial conformance with those standards.
  • AODA / IASR (Ontario) — applicable because Droz is an Ontario corporation with more than 50 employees and is a designated public-sector vendor through the Government of Canada supplier track.
  • Province of Quebec — Standard on the Accessibility of Government Web Sites (SGQRI 008-02) is referenced as a guideline for FR-CA content.
  • Mexico — NMX-I-NYCE-176-2018 (Mexican accessibility standard) referenced as a guideline for ES content delivered to Mexican audiences.

3. Measures we have taken

  • Semantic HTML. Every page uses <header>, <nav>, <main>, <section>, <article>, <aside>, and <footer> semantically. ARIA roles are applied where the semantic of the markup is ambiguous. ARIA labels are not used to paper over missing semantics.
  • Heading hierarchy. Each page has exactly one <h1>. Nested headings descend in order (<h2> → <h3> → <h4>) without skips.
  • Keyboard navigation. Every interactive element (links, buttons, form controls, mega-menus, the locale toggle, the mobile drawer) is reachable and operable with the keyboard. Focus is visible via the browser default plus an enhanced outline on form controls. The mega-menu opens on focus-within as well as hover, and closes on Escape.
  • Form accessibility. Every form field has an explicit <label for=…> associated by ID; error messages use aria-live="polite" to announce validation; the honeypot anti-spam field is aria-hidden="true" and positioned off-screen so it does not interfere with assistive tech.
  • Color contrast. Body text on light backgrounds meets WCAG AA contrast (≥ 4.5:1 for body, ≥ 3:1 for large display text). Dark-background bands use white text on the navy palette and meet AA.
  • Alternative text. Every <img> has an alt attribute. Decorative photos use alt=""; informative photos (certifications, client logos, field photography) carry descriptive alt text.
  • Focus management. The mobile drawer (slide-over) traps focus while open and returns focus to the trigger on close. The locale-fallback tooltip is keyboard-dismissible.
  • Language attributes. Every page sets <html lang="en"> (or lang="fr" / lang="es" per locale).
  • Reduced-motion support. Animations respect prefers-reduced-motion.
  • Typography & line-length. Body text uses Inter Tight at 17px with 1.7 line-height in the article template; display copy uses Droz Times with text-wrap: balance; line lengths are capped at 56–64ch.
  • Document downloads. The capabilities-statement PDF and media-kit files ship with accessible tags (titled PDFs, alt-tagged images). Documents that are not yet accessible are flagged in the auto-reply with a note offering an HTML alternative on request.
  • Skip link. Every page includes a "Skip to main content" link as the first focusable element. Visually hidden until focused.

4. Known limitations

We know of the following limitations and are addressing them:

  • Third-party logos. Some certification and partner logos in /assets/certifications/ and /assets/client-logos/ are provided as raster PNG/JPG/GIF without vector originals. Where the visual contrast of a logo is below AA on certain backgrounds, the surrounding caption text carries the meaning (e.g., "Mechanical engineers," "Canadian machinery vibration") so the visual is not the sole conveyance of information.
  • Background photography. Hero and division banner backgrounds are decorative and do not carry information; however, where text is overlaid on these images we maintain a gradient overlay that brings the contrast of overlaid text to AA.
  • Untranslated content during Phase 1–7. Until the FR / ES locale mirrors ship, the locale toggle navigates to the locale's home page with a tooltip when the sibling page does not yet exist. This is a transition state, not the steady state.

5. How to report an accessibility issue

If you encounter an accessibility barrier on droz.tech — content that is not reachable with assistive technology, a form you cannot complete, a document you cannot read — please tell us so we can fix it.

  • Email: accessibility@droz.tech (or contact@droz.tech if the alias is not yet provisioned).
  • Postal: Droz Technologies Inc., 4145 North Service Road, Burlington, Ontario, Canada — attention Accessibility.
  • Response time: we acknowledge accessibility reports within one business day. Remediation timelines depend on the nature of the issue:
    • Critical (page is unusable for a population) — fixed within 5 business days.
    • High (a function is unusable with assistive tech) — fixed within 10 business days.
    • Standard (cosmetic or non-blocking) — fixed in the next scheduled release.

When reporting, please include the page URL, a description of the barrier, the assistive technology or browser you are using, and (if possible) a screenshot or screen-recording.

6. Alternative formats

Documents available for download on droz.tech (the capabilities statement, media-kit files, insights PDFs, case-study PDFs) can be requested in an alternative accessible format — large-print, plain-text, audio, or a re-tagged PDF — by emailing accessibility@droz.tech. Alternative-format requests are fulfilled at no cost and as soon as practicable, generally within 10 business days.

7. Testing and assessment

We test droz.tech with: (a) the latest stable versions of Chrome, Firefox, and Safari on macOS, Windows, iOS, and Android; (b) the VoiceOver, JAWS, and NVDA screen readers; (c) keyboard-only navigation; (d) the axe-core automated accessibility scanner integrated into our build pipeline; (e) manual review against the WCAG 2.1 AA checklist.

Findings from automated and manual testing are tracked in the firm's internal issue tracker and reviewed each release. The accessibility statement is reviewed and re-published at least annually, or sooner when site changes are material.