A patient with chronic pain should not need pain-free hands to read a website about managing pain. That paradox is what Promedia found auditing changepain.be, the Grünenthal Belgium platform on chronic pain, against WCAG 2.2 AA. The pattern was not unique to one brand. It is the baseline state of pharma web in 2026: capable teams, considered design, accessibility simply never written into the original brief.
The context has shifted. Directive (EU) 2019/882, the European Accessibility Act, became enforceable across all 27 Member States on 28 June 2025, and 2026 is the first full year national authorities actively supervise compliance. Any existing accessibility gap on a patient-facing pharma site is now an active liability, not a future obligation.
And the audience impact is not abstract. Research in Pain Practice found that 58% of adults with chronic pain report a disability, and 62% of those link that disability directly to their pain. The people a disease-awareness site is built for are, statistically, the people most likely to be locked out of it.
The failure modes are strikingly consistent across the sector. On changepain.be, the Promedia audit surfaced the same five issues we document on nearly every pharma site we review:
None of this is negligence. It is sequencing. Accessibility is treated as a QA pass at the end of a build, not as a constraint written into the component library at the start. Add the fact that automated scanners only detect around a quarter to a third of WCAG issues, and teams relying on tooling alone end up with a false sense of compliance.
The audience numbers compound the problem. Roughly 7% of working-age adults have a severe dexterity difficulty, a figure that rises sharply in chronic-pain populations where motor impairment is a direct symptom. About 33% of people with mobility impairments navigate the web primarily by keyboard, which turns missing focus indicators and broken heading structures into hard blockers, not inconveniences.
The EAA brings patient-facing websites, disease awareness platforms, and digital health tools fully in scope. Conformance is measured against WCAG 2.2 AA through the harmonised European standard EN 301 549. The exemption is narrow: only microenterprises with fewer than 10 employees and under €2 million turnover are out of scope, which means essentially every pharmaceutical company operating in the EU is in.
Penalties vary by Member State implementation but can reach €100,000 or 4% of annual turnover. A complete compliance programme also requires a public accessibility statement, accessible documentation, and demonstrable assistive-technology compatibility, not just a passing Lighthouse score.
This matters commercially as well as legally. A 2024 industry survey found 67% of pharma CEOs expect healthcare organisations to face the same customer-service and accessibility expectations as other consumer sectors. Up to 50% of patients globally do not adhere to prescribed treatment, and unengaged patients are up to three times more prone to delayed care and dropouts. A disease-awareness site that excludes its target audience is a patient-engagement failure before it is a legal one.
A defensible audit combines automated scanning, manual review, and assistive-technology testing. Promedia's methodology is AI-assisted, designer-decided: agents surface candidate issues at scale, designers decide what gets fixed and how. On a recent sample engagement, a WCAG 2.1 AA audit covered 3 of 5 pages and scanned 1,098 nodes, enough to confirm that node-level remediation is impractical without a fix at the source.
A workable sequence looks like this:
Quarterly agent-run audits keep a backlog current. That backlog should be addressed first in Figma, then propagated to the live site.
A design-system audit shifts the unit of repair from the page to the component. One button component fixed in Figma resolves dozens or hundreds of instances in production. One heading-hierarchy rule corrected at the token level reshapes the screen-reader experience across every template that uses it.
The economics are straightforward. Node-level remediation on a mid-size pharma site means hundreds of individual tickets, each with its own QA cycle. Component-level remediation means a handful of design decisions that cascade automatically. Accessibility is cheaper when it is structural, not corrective, and the gap widens with every new campaign page added on top of a non-compliant foundation.
For pharma teams, the practical implication is to treat the design system itself as the regulated asset. Contrast ratios, minimum tap target sizes, focus-state styling, heading semantics, and PDF tagging conventions all belong in the component library and its documentation. Campaign teams then inherit compliance by default.
The recurring issues are low colour contrast on body text and CTAs, tap targets too small for users with motor impairment, heading structures that skip levels, missing or invisible focus indicators on interactive elements, and untagged PDF resources that assistive technology cannot parse. Most of these trace back to design-system components, not individual page builds.
Yes, substantially. A single component fix in Figma can resolve dozens or hundreds of production instances in one pass. Node-level remediation requires a separate ticket, developer effort, and QA cycle for each occurrence, which is why Promedia recommends design-system remediation first, live-site patches second.
If your team is unsure where you stand, start with a scoped audit of your highest-traffic patient site and insist the findings are mapped to design-system components, not individual pages. That single reframing is what turns an accessibility programme from a rolling cost into a one-time structural investment. Promedia runs this methodology across pharma awareness platforms in Belgium and the wider EU, and we are happy to share the approach with teams who want to assess their own exposure before supervisory authorities do it for them.
One short email when we publish. No spam, no sales pitch. Unsubscribe whenever.
