Accessibility
Make your Drupal website usable for more people. We assess important user tasks, turn barriers into practical improvements and agree how your team will check the results.
Assess tasks from start to finish
People need to understand information and complete tasks, also with a keyboard, magnification or a screen reader. That’s why we test the important journeys, such as searching, signing in or submitting a form, including error messages and confirmations. Reusable components, documents and media are included too, within the agreed scope.
We agree upfront which WCAG version and level we assess against, and which pages, states and assistive tools we cover. Automated tools help find problems, but according to W3C no tool alone can determine whether a website conforms. Skilled manual evaluation remains necessary.
From findings to practical fixes
For each finding, we describe the task, the problem, the WCAG criterion and a proposed fix. That way a developer can reproduce the issue and an editor knows which content to change. We prioritise by the barrier for users and by how widely a component is reused.
You confirm scope and priorities. Design, development and editorial teams each get their own actions, and we agree whether fixes and retesting are part of the assignment. Assessing selected pages is no guarantee that all content conforms. We always state what we assessed and where the limits are.
Make AI answers accessible too
An answer interface such as Trusted Answers needs more than readable text. Users must be able to enter a question, see that an answer is on its way, reach that answer and use the source links, also with a keyboard and assistive technology. AI can suggest alternative text or simpler explanations, but an editor always checks the meaning. And when the conversation can’t provide a suitable answer, the regular information and contact route stay within reach.
Check fixes and prevent recurring barriers
After a change, we repeat the task and check related components. Visible focus on one button doesn’t solve every keyboard issue. Where it makes sense, we involve people who use assistive technology themselves, to better understand practical barriers.
Reusable Drupal components improve a fix across many pages at once, but they spread a mistake just as widely. That’s why we turn recurring findings into design agreements, editorial guidelines and checks at every release. So accessibility doesn’t depend on one periodic audit.
Why Dropsolid?
We carry accessibility through design, content, Drupal components and testing. It becomes a fixed responsibility in delivery, not something you check afterwards. We connect design and content with technical delivery, and through consultancy your team works out decisions and responsibilities.
For UZA, we made accessibility and inclusion a core priority of the new platform. Getting started yourself? Our checklist with 11 guidelines helps you spot the most important barriers. Which legal requirements apply to your organisation depends on your situation. We’ll look at that together.
Which task needs to become usable for more people?
Start with the tasks where a barrier affects people most. Bring an important user journey, known problems and any earlier evaluations. Then we’ll decide together what needs to be assessed or fixed.