Accessibility Statement

Last updated: 2026-01-15

Contact: mayday@d-i.ai (acknowledgement within 2 business days; target resolution 15 days)

Scope

This statement covers the public website at d-i.ai, including:

Public pages and landing pages
Contact and subscription forms
Newsletters and downloadable assets we publish
Embedded media we control (images, audio, video)

Third-party platforms (e.g., payment processor, embedded players, map widgets) follow their own accessibility policies. We review their conformance before integration and provide alternatives where needed.

Standard & target level

We aim to conform to WCAG 2.1 Level AA.
Roadmap: align new and refactored components with WCAG 2.2 AA where feasible (focus appearance, dragging motions, etc.).

Conformance status

Partially conformant. The majority of core user journeys (read content, subscribe, contact us) are usable with keyboard and assistive technologies. Some legacy assets and styles still require remediation (see section 6).

Assessment methods

We use a mixed approach:

Manual testing with keyboard-only navigation (Tab/Shift+Tab/Enter/Space), visible focus, logical tab order
Screen reader checks (NVDA/JAWS on Windows, VoiceOver on macOS/iOS)
Tool-based audits (automated rulesets for color contrast, landmarks, ARIA, headings)
Content reviews (alt text quality, link purpose, form labels, error messaging)

Cadence: baseline audit each quarter; targeted audits before major releases.

Supported environments (tested combinations)

We aim to support the two latest versions of:

Desktop browsers: Chrome, Firefox, Edge, Safari
Mobile: iOS Safari, Android Chrome
Assistive tech (sampling): NVDA + Firefox/Chrome (Windows), VoiceOver + Safari (macOS/iOS)

If you rely on a different setup, contact us for an accommodation or alternative format.

Known limitations & timeline

Alternative text: some hero images and decorative backgrounds inherited from older templates lack proper alt or are announced unnecessarily.
Fix: re-tag as decorative or add concise alt; within 60 days.
Color contrast: a few button/link states on photo backgrounds may dip below AA in certain lightness values.
Fix: adjust tokens/overlays; within 60 days.
PDF tagging: one PDF is not fully tagged (reading order, headings).
Fix: provide accessible HTML equivalent and remediate PDF; within 60 days.

Key accessibility practices we implement

Keyboard access to interactive elements; visible focus ring; skip-to-content link
Semantic structure: one H1 per page, logical headings, landmarks (header/nav/main/footer)
Images & media: descriptive alt for informative images; empty alt for decorative; captions/transcripts for A/V content we control
Forms: programmatic labels, clear required-field indication, inline error messages tied to fields, ARIA where appropriate
Links & buttons: clear purpose in context; distinguishable from body text beyond color alone
Motion & flashing: no auto-playing audio; no content that flashes more than 3 times/second
Language attributes and meaningful page titles

Alternatives & assistance

On request, we provide alternative formats (HTML or plain text for documents, captions/transcripts for media). If a control or document blocks your task, email mayday@d-i.ai and we’ll propose a solution.

Third-party content & exemptions

User-generated or third-party embeds may have constraints; when an accessible equivalent exists, we link it.
Archived materials (legacy content retained for record-keeping) are remediated on demand or replaced with accessible summaries.

Governance & continuous improvement

Ownership: the Product Lead is responsible for accessibility, supported by Design/Content.
Training: editors receive guidance on alt text, headings, link wording, and media captions.
Change control: new components must pass our WCAG checklist before publication.
Reviews: statement updated semi-annually and after major releases.