Accessibility

A public site has to be usable

The organisations we build for publish information people are entitled to read. A page that only works for a mouse, a pair of good eyes, and a quiet room has failed that job. Accessibility is how the interface is built: headings in order, names on controls, contrast that holds, a keyboard path through every task, and text that is still text.

We follow WCAG as the shared definition of that work. It applies to a Drupal theme, to an editorial form, and to a React, Angular, or Vue interface the same way. The guideline is used while the component is written, because a template that ships inaccessible is expensive to unwind once content is in it.

In the theme, the form, and the application

Drupal gives the work a head start when the theme uses semantic markup and leaves the content in HTML. We keep it that way. Custom widgets, menus, and media are checked for focus, name, and what they announce. PDFs and video are called out when they are the inaccessible copy of something that should have been a page.

A custom frontend gets the same review against the same tasks: can someone complete them without seeing the screen, without a pointer, on a phone, with the text enlarged. We would rather remove a pattern than document an exception. Findings are written so a developer can fix them, with the page and the behaviour named.

• WCAG applied during the build of themes, templates, and custom interfaces.
• Keyboard access, visible focus, labels, and a heading order that matches the page.
• Editorial screens included, so publishers are not locked out of their own CMS.
• Issues written against the component, for the team that will maintain it.

What this engagement is

This is design and engineering against WCAG, inside the Drupal and Cloud work we already do. It is not a badge and it is not a legal opinion. If you need an independent audit for a procurement file, we will build so that audit has something solid to read, and we will say where an external reviewer should look. Tell us the site and the deadline. We reply within 24 hours.

This work sits inside Cloud & AI Development. Request information — tell us the organisation, the platform, and the constraint.