More ways to browse. Fewer barriers.
People use the web with different devices, abilities and ways of navigating. This statement explains our approach, practical ways to use the site and how to tell us when something gets in your way.
Last updated
Our approach to accessibility
We want people to be able to understand our work, explore the website and contact us without unnecessary barriers. Accessibility is part of how we approach content, interface design and engineering, and it needs attention as pages and features change.
This statement covers the Nivarix public website. Separate products, client systems and external websites may have their own accessibility information. Their accessibility cannot be inferred from this statement.
The standard we work towards
The Web Content Accessibility Guidelines (WCAG) 2.2 Level AA are our working target. The guidelines organize accessibility around making content perceivable, operable, understandable and robust across different ways of using the web.
A working target is not a claim that every page meets every success criterion. We are not presenting this statement as independent certification or a completed conformance audit. Content changes, integrations and differences between assistive technologies can reveal barriers that still need attention.
Using the website with a keyboard
The public site includes a skip link to move past repeated navigation and into the main content. Press Tab from the start of a page to reveal it. Continue using Tab to move forward between links and controls, or Shift + Tab to move backwards.
Visible focus styling helps show the current control. Links can be followed with Enter; buttons and expandable disclosures use their standard keyboard actions. Where a menu or dialog is open, Escape can be used when that control supports dismissal. If focus becomes hidden, trapped or unexpectedly moves, please report the page and the steps that led to it.
Page structure and assistive technology
We use page headings, landmarks and descriptive link text to make content easier to scan visually and navigate with assistive technology. Forms use labels to identify the information being requested, and controls should expose a meaningful name and state.
Informative images should have alternative text that explains their purpose. Decorative graphics should not add unnecessary announcements. If an image, button or link is announced in a confusing way, the page address and the wording you heard can help us locate the issue.
Reading, zoom and smaller screens
Layouts are designed to adapt to different screen sizes, with readable line lengths and space between interactive elements. You can use your browser’s text and zoom controls to enlarge content. Page meaning should not depend on a particular screen size, colour alone or a precise pointer movement.
Longer documents, including this statement, include section links to help you reach relevant content. At smaller sizes the contents list is expandable. If increasing text size causes content to overlap, disappear or require unnecessary horizontal scrolling, tell us which browser and zoom level you used.
Motion and visual presentation
The site uses transitions and occasional entrance effects to support the presentation of content. Reduced-motion preferences are used to limit motion for people who request it through their device or browser settings. Core information should remain available without needing to watch an animation.
If motion makes a page difficult to use, enable the reduced-motion or animation setting provided by your operating system. You can also report the page and the effect involved. We consider contrast, focus visibility and readability when updating the interface, while recognizing that individual needs and display settings vary.
Forms and verification
The contact form identifies required information and provides feedback when a submission needs attention. A security verification service, Cloudflare Turnstile, may be required before the server accepts an enquiry. That service depends on external scripts and can be affected by browser settings, assistive technology or network restrictions.
If the form or verification step is a barrier, you can email us directly using the details below or use the other contact options. You do not need to complete the website form to report an accessibility issue. Avoid including passwords, personal records or other sensitive information in a report.
Browser features and connected content
The website is built with standard web technologies and is intended to work in current browsers. Core written content is rendered as part of the page, while interactive features such as filtering, menus and form verification may require JavaScript. A browser extension, restrictive network or older software can affect those features.
We cannot claim testing with every browser and assistive-technology combination. External websites, embedded services and content supplied by other organizations can also have limitations outside our direct control. Report a problem with the context you have, even if you are not sure what caused it.
Tell us about a barrier
A useful report describes what you were trying to do and what prevented you from completing it. You do not need technical expertise or a diagnosis to contact us, and you do not need to disclose a disability.
Where it happened
Share the page address, the link or control involved, and whether the problem occurs consistently or only sometimes.
What you experienced
Describe the expected result and what happened instead. A short set of steps or a screenshot can help when you are comfortable providing one.
Your setup, if known
Include your browser, device, zoom setting and any assistive technology that seems relevant. This information is optional.
What would help
Tell us if you need the information in another format or would prefer a particular way to continue the conversation.
How feedback helps us improve
We use reported barriers to understand the affected task, reproduce the issue where possible and identify an appropriate next step. A problem that prevents someone from reading essential information or contacting us deserves particular attention. We may ask for clarification if the report does not give enough context.
Some issues can be addressed in content or code; others depend on a provider or require a broader change. Where practical, we can discuss another way to provide the information while an issue is being considered. This statement does not promise a fixed resolution time for every report. Personal information in your message is handled as described in our Privacy notice.
Reviewing the experience over time
Accessibility work includes checking semantic structure, keyboard interaction, responsive presentation and the effect of interface changes. Automated diagnostics can identify some problems, but they cannot establish that a whole experience is accessible or replace feedback from people using it.
New pages, revised content and changes to connected services can introduce regressions. We use findings from implementation checks and reported issues to guide improvements. The date at the top identifies this statement’s current version; the approach and guidance may be updated as the website develops.
Accessibility feedback
Tell us what got in the way.
Email the page address and what you were trying to do. If another format or contact method would help, tell us what works for you.