Since 28 June 2025, Directive (EU) 2019/882, better known as the European Accessibility Act, has been in force across all 27 EU Member States. Patient-facing websites, disease awareness platforms, and digital health tools must now conform to WCAG 2.2 AA through the harmonised standard EN 301 549. Pharmaceutical companies are fully in scope. Only microenterprises with fewer than 10 employees and under €2 million turnover are exempt, which excludes essentially every marketing authorisation holder operating in Europe.
The stakes are concrete. Penalties can reach €100,000 or 4% of annual turnover depending on Member State implementation, alongside corrective orders and restricted market access. 2026 is the first full year in which national authorities actively supervise compliance, which means brand teams that treated the deadline as a soft target are now visible.
And the baseline is poor. Industry research suggests roughly 1 in 5 Europeans needs digital accommodations, while 96% of websites still fail basic accessibility tests. Pharma sites, with their PDFs, patient journeys, and layered consent flows, are rarely in the compliant 4%.
A credible WCAG audit on a pharma website has two halves that cannot be separated: an automated scan that maps the terrain, and a designer-led review that decides the route.
The automated half runs a crawler across the entire live property. Every page, every reusable component, every PDF linked from a patient journey. Nothing is sampled. An audit skill then checks each element against WCAG 2.2 AA criteria: contrast ratios, mobile font sizing, heading structure, screen-reader labels, keyboard focus order, form field labelling, and video captions. On a 100-page pharma site, this now takes around three hours in Promedia's workflow. The manual equivalent used to take three weeks.
The output is grouped by root cause rather than by page. If one design token fails contrast, that is one finding, not the 200 places it appears across the site. This is the shift that makes remediation economically sensible: fix the token once at the design-system level and hundreds of downstream instances resolve at the same time.
Automated accessibility scanning works by parsing the rendered DOM of each page and comparing it against machine-checkable success criteria. It is fast and consistent, and it catches the failures that have clear pass/fail rules: missing alt text, insufficient contrast, unlabeled form inputs, empty link text, invalid heading hierarchies.
What it does not catch is judgement. A crawler can confirm that an image has an alt attribute. It cannot decide whether the alt text meaningfully describes the injection-site diagram it accompanies. It can confirm a video has captions. It cannot check whether those captions accurately convey the dosing instruction in the voiceover.
Independent accessibility research consistently puts the ceiling of automated coverage at roughly 25 to 40 percent of WCAG issues. EN 301 549 conformance explicitly requires manual testing with assistive technologies across real user workflows. This is not a Promedia opinion. It is how the standard is written.
The part that matters is what happens after the report lands. A designer sits with the findings and reads them against real patient journeys. This is where automation stops and expertise starts.
Consider a button that fails contrast. A tool will flag it and move on. A designer asks: where does this button live? If it is the primary CTA on a self-administration video page, where a patient with low vision needs to press play to learn how to inject a biologic, that finding jumps to the top of the backlog. If it is a tertiary link in a cookie preferences drawer, it can wait for the next design-system release.
Promedia's demo workflow captures this principle as: AI assists the review, designers decide what to fix. The recommended cadence is a quarterly automated agent run to build a backlog, then fixes applied first at the design-system level and subsequently on the live website. That order matters. Fixing the design system prevents the same failure being reintroduced by the next agency, the next campaign, the next content refresh.
When a designer prioritises, they typically sort findings into four buckets:
This is the plan that goes to Medical, Regulatory, and the brand team. Not a 400-row spreadsheet.
An automated audit is a diagnostic. It tells you what is broken and where, at scale, quickly, and repeatably. A manual audit is a clinical assessment. It tells you what to do about it, in what order, and why.
Running only the automated half leaves 60 to 75 percent of real accessibility barriers undetected and produces a backlog with no prioritisation logic. Running only the manual half is prohibitively slow and cannot cover a 100-page site quarterly. The two halves are complementary, not alternatives.
This is also why Promedia positions application audits as Stage 12 of its patient engagement lifecycle, an ongoing feedback loop after everyday delivery to patients rather than a one-off pre-launch check. Governance checks and incremental improvements precede the audit stage, which frames WCAG reviews as continuous quality assurance rather than a compliance panic.
Yes. Directive (EU) 2019/882 applies to any organisation placing products or services on the EU market that fall within its scope, which includes patient-facing websites, disease awareness platforms, patient portals, and digital health tools. Only microenterprises with fewer than 10 employees and under €2 million turnover are exempt, which excludes essentially all pharmaceutical marketing authorisation holders operating in Europe.
No. Automated scanners detect roughly 25 to 40 percent of WCAG issues, primarily the machine-checkable ones like contrast ratios and missing labels. EN 301 549 conformance requires manual testing with assistive technologies across real user workflows. Any vendor claiming full compliance from a scan alone is misrepresenting what the standard requires.
For patient-facing pharma sites, the highest-impact criteria are contrast and text sizing (patients often have age-related vision changes), keyboard and screen-reader access to dosing and self-administration content, captions and transcripts for instructional video, form accessibility for adverse-event reporting, and accessible PDFs for patient information leaflets. WCAG 2.2 AA covers all of these, and while WCAG 2.2 is not yet formally in EN 301 549, it is the sensible forward-looking target.
A quarterly automated audit paired with a designer-led review is the working cadence Promedia recommends. Quarterly is frequent enough to catch regressions introduced by campaigns, content updates, and third-party embeds, and infrequent enough that the remediation backlog stays manageable. Any major site release or design-system change should trigger an additional audit outside the quarterly rhythm.
If your last accessibility check was a pre-launch scan by an agency that has since moved on, treat that as a baseline, not a compliance position. Commission a full-site automated audit against WCAG 2.2 AA, then sit a designer with the findings and a map of your patient journeys. Fix the design-system root causes first. Push the remaining items into a prioritised backlog with owners and dates.
The European Accessibility Act is not going to be enforced uniformly overnight, but the direction is clear and the reputational cost of a public accessibility failure in a patient-facing context is higher than any fine. Better to have a live remediation plan than a clean-looking scan.
If you want to see how a designer-led review session actually runs on a pharma site, Promedia's accessibility team is happy to walk through one with your brand and Medical leads.
One short email when we publish. No spam, no sales pitch. Unsubscribe whenever.
