Skip to main content

Accessibility

Web experiences should be available for all to enjoy

Drupal - Support from the ground up

A long history of engagement with accessibility support

The Drupal community has long had strong support for accessibility across core functionality and the default themes - it's been a key feature for years now.

Core development is guided by the Accessibility Team, who review Drupal's experiences and development processes to ensure they keep growing in their support for an open web.

Out of the box

With additional effort following the #GAADPledge in 2022, Drupal’s out-of-box experience provides a baseline that already fulfils most key WCAG guidelines. Various core templates and code intrinsically support and encourage accessible markup and thoughtful site building. This gives a very strong starting point upon which to build the customer-facing designs and the custom functionalities.

Drupal's Accessibility Coding Standards define more specifically how we developers should go about building web experiences that are accessible to all.

Building accessible sites

Considerate builds and thoughtful development

We are passionate that web users should have a good user experience, and our strong UX & design principles firmly support compliance with WCAG guidelines and principles.

Awareness across our team means we can notice things like poor colour contrast before they reach later reviews, and our flexibility allows us to make on-the-fly adjustments to designs, colours and interactions throughout the build process as needed, with little fuss.

We've helped many of our clients build sites that work for a wide base of accessibility needs. Drupal has often made those changes simple and quick, so there's no reason that accessibility should take the back seat behind the SEO budget.

When building to a specified WCAG compliance level, we can:

  • Build with both Drupal’s Accessibility Coding Standards and WAI’s Accessibility Principles in mind
  • Proactively review and configure Drupal’s editorial workflows to support accessibility; for example, requiring alt text be provided for applicable imagery
  • Test bespoke functionality for keyboard navigation and visibility
  • Perform accessibility audits throughout the build
  • Produce a report on the completed site build, providing final assurance

Where the content, design or functionality do not intrinsically fulfil WCAG 2.2 AAA guidelines, we will work with you to review the issues and develop pragmatic solutions within the time and budget restrictions.

Accessibility audits

We can review your site's markup and usability and bring back an itemised report, with effort estimates.

Or take up a Site Audit and we can cover a range of other issues, too.