Accessibility

Our Commitment to Accessibility

Last updated: March 2026

Statement: March 2026

Our Commitment

Digital 520 is committed to ensuring that our website is accessible to everyone, including people with disabilities. We believe that equal access to information and functionality is not a feature — it is a baseline expectation. Our goal is to design and maintain a digital experience that is usable by as many people as possible, regardless of ability, assistive technology, or browsing environment.

We are actively working to bring our website into conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at the AA level, published by the World Wide Web Consortium (W3C). These guidelines are the internationally recognized benchmark for web accessibility and serve as the foundation for our ongoing efforts.

Accessibility is a shared responsibility across our team. As we build new features, commission new content, and iterate on our design system, accessibility review is part of that process — not an afterthought applied at the end.

Standards We Follow

Our target conformance standard is WCAG 2.1 Level AA. This standard is organized around four foundational principles — often referred to by the acronym POUR — which together describe what it means for web content to be accessible:

Perceivable

Information and interface components must be presentable to users in ways they can perceive — including through assistive technologies such as screen readers or alternative text for images.

Operable

All interface components and navigation must be operable. Users must be able to interact with the site using a keyboard alone, without relying on a mouse or pointer device.

Understandable

Content and operation of the interface must be understandable. This includes clear language, predictable behavior, and helpful error identification in forms and interactive elements.

Robust

Content must be robust enough to be interpreted reliably by a wide variety of current and future user agents — including assistive technologies such as screen readers and braille displays.

We aim for compatibility with commonly used assistive technologies, including screen readers (NVDA, JAWS, and VoiceOver), keyboard-only navigation, and high-contrast display modes across major browsers and operating systems.

What We Have Done

As part of our ongoing accessibility work, we have implemented or are actively pursuing the following measures across the Digital 520 website:

  • Semantic HTML structure throughout the site, using appropriate heading hierarchies, landmark regions, lists, and native HTML elements to support assistive technology navigation.
  • Descriptive alt text on all meaningful images, including logos and decorative graphics — with empty alt attributes used intentionally for purely decorative images to avoid redundant announcements.
  • Color contrast ratios meeting or exceeding the WCAG 2.1 AA minimum thresholds (4.5:1 for normal text, 3:1 for large text and UI components) across all primary content areas.
  • Keyboard navigability for all interactive elements, including navigation menus, forms, and call-to-action buttons, ensuring users who do not use a mouse can access all functionality.
  • ARIA labels and roles on icon-only buttons and interactive components where the visual context is insufficient to convey purpose to a screen reader.
  • Skip-to-content links are currently in progress and will be added to allow keyboard users to bypass repetitive navigation blocks.
  • Responsive design that adapts gracefully across screen sizes, devices, and zoom levels up to 200% without loss of content or functionality.
  • Focus indicators on all interactive elements to ensure keyboard users can always identify their location on the page.

Known Limitations

We are transparent about areas where our site does not yet fully meet accessibility standards. We are actively working to address these, and we welcome feedback from users who encounter any barriers.

  • Custom cursor: The animated cursor used on this site is a visual enhancement only. It does not interfere with keyboard navigation, screen reader behavior, or pointer-based assistive technology. Users with pointer accessibility needs will not be affected by this component.
  • Third-party scheduling widget (Calendly): Our booking flow uses Calendly's embedded scheduling tool. Calendly's accessibility implementation is subject to their own standards and practices, which are outside our direct control. Users with accessibility needs who experience difficulty with the Calendly widget are encouraged to contact us directly to arrange a consultation through an alternative method.
  • Legacy PDF documents: Some older insight reports and downloadable documents may not be fully tagged for screen reader access, as they were produced prior to our current accessibility standards. We are working to remediate these files and will prioritize the most frequently accessed documents.

If you encounter an accessibility barrier not described above, please do not hesitate to contact us. Your feedback is how we identify gaps and improve. We take every accessibility report seriously and respond promptly.

Ongoing Efforts

We treat accessibility as a continuous discipline rather than a one-time compliance checkpoint. Our commitment is embedded in how we build and maintain this site:

  • New pages and features are reviewed for accessibility before being published, including evaluation against WCAG 2.1 AA success criteria.
  • We test with keyboard navigation and screen reader software as part of our quality assurance process.
  • We monitor updates to WCAG standards and relevant guidance from the W3C Web Accessibility Initiative (WAI), and we update our approach as those standards evolve.
  • We conduct periodic audits of existing content and components to identify regressions or previously undetected gaps.
  • We review third-party tools and integrations for accessibility implications before adding them to the site.

Feedback & Contact

We welcome feedback on the accessibility of the Digital 520 website. If you encounter any barriers, find content that is difficult to access, or need information in an alternative format, please reach out to us directly. We aim to respond to all accessibility-related inquiries within 2 business days.

When contacting us about an accessibility issue, it is helpful (though not required) to include the URL of the page where you encountered the barrier, a description of the difficulty you experienced, and the assistive technology or browser you were using. This information helps us investigate and resolve issues more efficiently.