Accessibility statement

DGTL targets WCAG 2.2 Level AA conformance.

Accessibility is a product requirement on every engagement we deliver. That standard applies to the DGTL website itself. This page documents our conformance target, the current scope, known issues, how to report a barrier, and our enforcement procedure.

Last reviewed 2026-08-18

Conformance target

Standard
Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. Mapped to Section 508 of the Rehabilitation Act and EN 301 549 for enterprise and public sector procurement.
Scope
The public DGTL website at withdgtl.com and every subpage. Third-party embeds (Cal.com, future analytics vendors) inherit their own conformance level; DGTL is responsible for the surfaces DGTL builds.
Status
Partially conformant. A full accessibility remediation pass shipped with the site launch, and conformance is reviewed on an ongoing basis. The Known Issues section below tracks what remains, each item with a dated remediation target.
Assessment approach
A combination of automated scanning (axe-core in CI, Lighthouse Accessibility), manual keyboard walks, and screen reader verification with NVDA on Firefox and VoiceOver on Safari. A formal VPAT 2.5 ACR is in progress.

Conformant patterns

Patterns DGTL implements site-wide to meet or exceed WCAG 2.2 AA. Not an exhaustive list, but the load-bearing commitments.

  • Skip-to-content link at the top of every page
  • Semantic HTML5 landmarks (header, nav, main, footer) with accessible names
  • Heading hierarchy starting at a single H1, monotonic H2 through H6
  • Keyboard-reachable primary navigation including the Services mega menu (Enter, Space, ArrowDown to open, Escape to close)
  • Focus-visible outline on every interactive element (2px coral-700, 2px offset)
  • prefers-reduced-motion respected across every Motion component via a centralized getVariants helper
  • Minimum 44x44 touch targets on mobile controls
  • Form labels tied to inputs via htmlFor, errors announced via a single atomic aria-live region
  • SVG data visualizations expose structured readouts via <title>/<desc> and a visually-hidden <dl>
  • Animated counters expose their final value to assistive tech immediately via sr-only text
  • Contact form server action redirects to a dedicated /contact/thank-you route for predictable post-submission focus and announcement

Known issues

Honest disclosure of where DGTL is not yet at the target. Each item has a description, impact, and remediation plan.

Cookie consent banner

Issue: The current cookie consent banner is a custom component, not a certified consent management platform.

Impact: Does not yet produce a signed audit trail of consent choices or expose every granular vendor toggle that a strict CMP offers.

Plan: Scheduled for replacement with a certified consent management platform (Cookiebot, Osano, or CookieYes), alongside the analytics and advertising rollout.

VPAT 2.5 Accessibility Conformance Report

Issue: A formal VPAT 2.5 ACR is not yet published against the public website.

Impact: Enterprise procurement teams that require a signed VPAT as a gating document cannot self-serve it from this page yet.

Plan: Draft targeted for Q4 2026 once the remaining known issues below are closed. The VPAT will be made available on request via the /trust page.

Video captions and transcripts

Issue: DGTL does not yet host video content on the public website.

Impact: Not an active gap today, but any video added in the future will require captions (WCAG 1.2.2) and a transcript (WCAG 1.2.3) at publish time.

Plan: Captions and transcripts are a required deliverable on every video production in the DGTL Studio practice. The standard applies to DGTL's own content as well.

Feedback and reporting a barrier

If you hit an accessibility barrier on any DGTL page, please let us know. We acknowledge reports within 48 hours and prioritize fixes alongside active development.

Accessibility contact:
accessibility@withdgtl.com
Response target:
48 hours for acknowledgement. Remediation timeline depends on severity and the active sprint window.
What to include:
The URL, a description of the barrier, your assistive technology and browser if relevant, and whether a workaround exists.

Enforcement procedure

DGTL is committed to resolving reported barriers in a timely manner. If a report is not acknowledged or resolved to your satisfaction, escalate to hello@withdgtl.com with a reference to the original report. DGTL supports the enforcement procedures outlined in EN 301 549 and Section 508 where they apply.

See also: Trust and security, Who we serve.