Accessibility
This statement describes how accessible this website is, what we have tested, and what is still wrong with it. The last part is the part most accessibility statements leave out, so it is the part we have made longest.
Statement prepared 31 August 2026. It applies to baxtra.pages.dev, including the three portals, and to the PDF documents in the library. It is reviewed twice a year and after any substantial change to the site.
Partially conformant with WCAG 2.2 level AA
Partially conformant means that some parts of the site do not fully conform. We are not going to describe the site as compliant while we know of defects in it, and we know of several. They are listed further down this page with a date by which we expect each to be fixed.
Things you can rely on
Keyboard operation
Every interactive control can be reached and operated from the keyboard alone. A skip link is the first focusable element on every page. Modal dialogues trap focus while open and return it to the control that opened them. Press Ctrl + K anywhere for the command palette and ? for the full shortcut list.
Text and contrast
Body text meets the 4.5:1 contrast minimum against its background at the default setting. A higher-contrast mode and a comfort mode with increased text size and line spacing are both available from the tools rail on the left of every page, and both persist between visits.
Motion
Every animation on the site is disabled when your operating system reports a preference for reduced motion. Nothing moves, flashes or auto-advances without that check. There is no content on this site that flashes more than three times a second.
Structure
Pages use one h1 and a nested heading order
with no skipped levels. Landmarks are marked up so that a screen reader can jump between the
banner, the navigation, the main content and the footer.
Zoom and reflow
Content reflows to a single column at 320 CSS pixels and remains usable at 400 per cent zoom without horizontal scrolling, except for the data tables noted below.
Plain language where it matters
The patient-facing pages and the patient portal are written to a reading age of about twelve. The scientific pages are not, and deliberately so — but every technical term on them is defined in the glossary and shown on hover.
What does not work properly yet
Listed in the order we intend to fix them. Where a date has already passed and the item is still here, the item slipped and we have not updated the date to hide that.
| Defect | Where | WCAG criterion | Target |
|---|---|---|---|
| Wide data tables scroll horizontally rather than reflowing, and the scroll region is not announced as such. | Medicine database, pipeline, study finder | 1.4.10 Reflow | Q4 2026 |
| Several charts convey information by colour and position only. A text alternative exists beneath each one but it is not linked programmatically to the figure. | Pipeline lanes, researcher portal | 1.1.1 Non-text Content | Q4 2026 |
| Eleven of the twenty-six PDF documents are not tagged, so reading order in a screen reader is unreliable. All twenty-six have text layers and are searchable. | Document library | 1.3.1 Info and Relationships | Q1 2027 |
| Some slider controls in the researcher portal do not announce their current value on change. | Researcher portal | 4.1.2 Name, Role, Value | Q4 2026 |
| The command palette results list does not announce the number of results to screen reader users. | All pages | 4.1.3 Status Messages | Q4 2026 |
| Focus indication on the dark call-to-action bands is lower contrast than elsewhere on the site. | Several pages | 2.4.11 Focus Appearance | Q4 2026 |
| The three-dimensional molecular viewer has no non-visual equivalent. It is decorative and can be skipped, but it is not marked as decorative. | Science, medicines | 1.1.1 Non-text Content | Q1 2027 |
Testing method
Automated checking with an accessibility linter on every page in the build, which catches perhaps a third of what matters. Manual keyboard-only traversal of every page and every portal view. Screen reader testing with NVDA on Windows and VoiceOver on macOS, on the public pages and on the patient portal in full, and on a sample of the researcher portal.
We have not yet done testing with users who rely on assistive technology day to day. Until we have, this statement should be read as an internal assessment rather than an independent audit, and we would not want it read as more than that.
If something on this site does not work for you
Write to accessibility@baxtra.pages.dev. Tell us the page, what you were trying to do, and what happened instead. If you use assistive technology it helps to know which, but do not feel obliged to tell us anything about yourself that you would rather not.
We aim to reply within five working days. If the fix is quick we will make it and tell you when it is live. If it is not quick we will tell you that instead, with a date, and add it to the defect table above so that it is public rather than sitting in an inbox.
If you need information from this site in another format — a document read aloud, a large-print version, or a plain-text version of a PDF — ask at the same address and we will produce it. There is no charge and you do not need to give a reason.
Other things we publish about how we operate
The accessibility statement sits alongside the privacy notice, the code of conduct and the document library. All of them are written on the same principle: state the gaps rather than describe the intentions.