Skip to main content

Pharma Website Accessibility Audit: Why WCAG 2.2 Fails Repeat

WCAG & Accessibility·5 min read

Most pharma sites look accessible. Very few actually are. Promedia recently completed a WCAG 2.2 audit of Takeda Belgium's monaoh.com, applying the same methodology used earlier this year for J&J, GSK, Amgen, and AbbVie properties. The pattern repeats across every brand: capable teams, professional visual design, and a raft of accessibility failures baked in below the surface.

This is the state of pharma web in 2025. Sites were built without accessibility in the original brief, and now the European Accessibility Act is in active enforcement. The question is no longer whether to audit. It is how to audit efficiently, and what to fix first.

How to audit a pharma website for WCAG 2.2 compliance

A useful pharma website accessibility audit starts at the design system, not the page. Automated scanners catch roughly 40% of WCAG 2.2 issues, according to accessibility testing research from AllAccessible. They miss focus visibility, consistent help patterns, redundant entry, and authentication flows. Those require manual expert review.

Promedia's methodology combines both. An AI-assisted pass across the full component library surfaces token-level failures in hours rather than weeks, producing a prioritized fix list. A manual layer then validates screen reader behavior, keyboard navigation, and the interaction patterns automation cannot see. In the Takeda audit, this hybrid approach produced a Design System Health score of 78/100, with 132 critical findings and 57 warnings traced back to just four root causes.

The critical detail: accessibility scored only 33/100 as a dimension, well below naming and semantics (99), token architecture (86), and consistency (83). A site can look well-structured and still be functionally inaccessible.

Why do pharma websites fail accessibility standards

The failures cluster in predictable places. Brand palettes get designed for print, where contrast ratios are measured differently. On screen, at small sizes, they drop below AA. Cookie banners, the first interaction every visitor has, are frequently the least accessible element on the page. PDF resources sit on the site untagged for screen readers. Videos ship without captions or transcripts. Heading structure looks tidy in the layout but skips from H2 to H4 underneath, so screen reader users hear a broken outline.

Color contrast is the single most common structural failure. In one recent audit, a brand red CTA button (white text on #FF3838) failed WCAG 1.4.3 AA at a 3.6:1 ratio, when 4.5:1 is required. The same red appeared over 30 times across the site. Red text on white labels failed separately at 3.2:1. Darkening the brand red token from #FF3838 to #C0392B fixed all 30-plus instances simultaneously.

The same pattern showed up in secondary text. A grey body copy color at #939393, used for footer links, price labels, and descriptions, failed AA on white (3.1:1) and on light grey backgrounds (2.7:1). Roughly 120 instances across the system. One token update at color/content/secondary cascaded to every node.

These are not content problems. They are architecture problems.

How does a design system audit fix pharma web accessibility

Here is the economics: one button component used 80 times across a site is one fix at the source, or 80 fixes in production. A content review treats the second scenario as normal. A design system audit treats it as the failure to prevent.

When the audit lives at the token and component layer, fixes cascade. Changing the primary CTA color token repairs every button that inherits it. Fixing the heading component's semantic structure corrects the outline on every page that uses it. Retagging the PDF template applies to every future export. The audit becomes a foundation the rest of the estate builds on.

A structural audit typically returns three deliverables:

  • A WCAG 2.2 compliance report across the full component library, mapped to specific success criteria
  • A prioritized fix list ordered by cascade impact, so the highest-leverage tokens are addressed first
  • A brand consistency and token architecture review, because accessibility and brand integrity break together

Accessibility is cheaper when it is structural, not corrective. That is the whole thesis.

Frequently asked questions

What are the most common WCAG failures on pharma websites?

Color contrast on brand palettes, inaccessible cookie banners, untagged PDF resources, missing video captions, and heading structures that skip levels. These recur across almost every pharma site Promedia has audited in 2025, because they trace back to design decisions made before accessibility was part of the brief.

Is WCAG 2.2 now legally required in Europe?

Effectively yes for pharma. The European Accessibility Act entered enforcement on June 28, 2025, and references WCAG 2.2 conformance as the practical compliance standard. WCAG 2.2 also became ISO/IEC 40500:2025 in October 2025, which accelerates formal adoption into national law across EU member states.

What is the difference between a content review and a design system audit for accessibility?

A content review checks pages one at a time and produces fixes at the page level. A design system audit checks tokens and components, so one fix cascades to every instance. If a button appears 80 times, a content review generates 80 tickets. A design system audit generates one.

How does inaccessible brand color contrast affect pharma site compliance?

Color contrast failures under WCAG 1.4.3 are among the most cited AA violations and the easiest to prove in a legal complaint. A brand red that fails at 3.6:1 instead of the required 4.5:1 is a documented non-conformance every time it appears. Fixing the underlying color token is usually a one-line change that resolves dozens of instances at once.

Where to start

If you manage a pharma digital estate in Europe, the useful next step is not another page-by-page review. It is a design system audit that maps every WCAG 2.2 failure back to its root cause, ranks fixes by cascade impact, and gives your team a defensible compliance position before the next enforcement cycle.

Promedia runs this audit as a fixed-scope engagement, using the same methodology applied to Takeda, J&J, GSK, Amgen, and AbbVie properties this year. If it would be useful to see where your estate stands, that conversation is worth having before the audit letter arrives, not after.

Get pharma comms insights.

One short email when we publish. No spam, no sales pitch. Unsubscribe whenever.