Where to start when testing your website for accessibility

Automated tools are a useful first step. They quickly identify obvious issues and give you a high-level view of how your site performs against the Web Content Accessibility Guidelines (WCAG).

One tool we regularly use is WAVE (Web Accessibility Evaluation Tool). It’s available as a Chrome extension or via the WAVE website.

After running a scan, WAVE highlights:

• Errors and contrast errors (the most critical issues to prioritise)
• Alerts
• Structural elements
• ARIA (Accessible Rich Internet Applications) attributes

In most cases, the errors and contrast errors are the most important to focus on. These typically flag failures against WCAG standards, such as missing alternative text, empty links or insufficient colour contrast.

Within the ‘details’ panel, you can:

• Click on a flagged icon to jump directly to the issue on the page
• View guidance on why it’s a problem
• See which WCAG success criterion it relates to
• Review suggestions on how to fix it

Automated tools are efficient, but they don’t tell the whole story. They cannot fully assess usability, context or real user interaction. That is where manual testing becomes essential.

Start with basic interaction on desktop.

Hover over links and buttons and ask:

• Does it look clickable?
• Does the cursor change to a pointer?
• Is there a clear visual change on hover?
• Are interactive elements clearly distinguishable from static text?

Interactive elements should be obvious. If users have to guess what is clickable, that is both a usability and accessibility issue.

Check radio buttons and checkboxes carefully. Labels should be easy to select and toggle. Small click areas or poorly associated labels can create unnecessary barriers.

Accessibility is also about physical interaction.

On mobile and tablet devices:

• Are touch targets large enough to tap comfortably?
• Is there enough spacing between buttons?
• Can users access all content without relying on hover?

The Nielsen Norman Group recommends a minimum touch target size of around 1cm x 1cm. While we design in pixels and rems, what matters is how it feels in a user’s hand.

Pay close attention to dynamic elements such as mega menus, tooltips or expandable sections. If something relies on hover on desktop, how does it behave on touch? Can users access the same content with a tap?

In healthcare and pharma, where information can be layered and detailed, these interaction gaps can quickly create friction.

Keyboard accessibility is a critical part of WCAG compliance and a common area of failure.

Put your mouse aside and use the tab key to move through the page.

Check:

• Can you reach all interactive elements using the keyboard?
• Is the focus state clearly visible?
• Can you activate buttons and submit forms using Enter or Space?
• Can you open and navigate menus?
• Can you close overlays or modals?

If you lose track of where you are on the page, or get stuck in a component, that creates a barrier for keyboard users.

For pharma organisations with forms, portals and gated content, keyboard testing is especially important.

Screen reader testing provides insight into how your content is announced and structured for users who rely on assistive technology.

Popular options include:

• NVDA (free, Windows)
• VoiceOver (built into macOS and iOS)

When testing, focus on:

• Heading structure and logical hierarchy
• Meaningful link text (avoid “click here”)
• Correct use of alternative text for images
• Clear form labels and error messages
• Logical reading order

Rather than focusing on differences between screen readers, concentrate on whether your site follows accessibility principles and WCAG best practice. Clear structure and semantic HTML usually lead to better outcomes across technologies.

Accessibility testing should not sit at the end of a project as a final QA check. It works best when it is embedded into design, content and development workflows.

That means:

• Testing early, not just before launch
• Logging issues clearly and prioritising them in your backlog
• Mapping fixes to specific WCAG success criteria
• Re-testing after updates or new feature releases

For organisations operating across multiple brands, markets and platforms, a structured accessibility assessment can provide clarity on compliance gaps, risk and prioritisation.

Testing is the starting point. Acting on what you find is what improves the experience for patients, HCPs and consumers, and reduces regulatory risk at the same time.