Accessibility statement

This statement applies to Neolung at app.neolung.io, its desktop app (which loads the same interface), the signed report PDFs it produces, and its website at neolung.io.

We want as many people as possible to be able to use Neolung. For example, you should be able to:

• dictate a report by voice or type it: the dictation field takes typed text, and nothing needs a microphone;
• use it in light or dark mode, following your system;
• use it on a phone, with a layout for narrow screens.

Neolung is built to be used with a keyboard, with screen readers and when zoomed in, but this hasn't yet been checked by hand (see Preparation of this statement).

How accessible this service is

We know some parts aren't fully accessible:

• the signed report PDF has no structure for screen readers (headings, tables, reading order) and doesn't declare its language;
• a slide photo or CT image without a caption is described only as Slide photo;
• sign-in pages (run by our identity provider, Auth0, chosen and set up by us) haven't been checked;
• the manual audit hasn't been done, so other problems may remain.

Feedback and contact information

If you need information in a different format, such as the report in another format, email trust@neolung.io. We'll confirm within 3 working days and say what we'll do and by when.

Reporting accessibility problems

We're always looking to improve. If you find a problem not listed here, or think we're not meeting the requirements, email trust@neolung.io.

Enforcement procedure

Where the organisation using Neolung is a public sector body, such as an NHS Trust, the Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies Accessibility Regulations in Great Britain (the Equality Commission for Northern Ireland, ECNI, in Northern Ireland). If you're not happy with how a complaint is answered, contact the Equality Advisory and Support Service (EASS), or in Northern Ireland the ECNI.

Technical information about this service's accessibility

Neolung is committed to making its service accessible, in line with the regulations above that bind the organisations using it.

Compliance status

Neolung is partially compliant with WCAG 2.2 AA, due to the non-compliances listed below.

Non-accessible content: non-compliance with the accessibility regulations

1. The signed report PDF isn't tagged: no structure for assistive technology and no declared language. Fails 1.3.1 (info and relationships) and 3.1.1 (language of page). The same report is shown on screen in Neolung and can be copied. We plan a tagged PDF (PDF/UA) by 31 March 2027, as its own change, because it alters the file of a signed document and an earlier version's regenerated PDF must remain the same report.
2. A slide photo or CT image without a caption has only the generic text Slide photo (wrong for a CT image). Fails 1.1.1 (non-text content) where the photo carries information the caption should give. We plan to ask for a caption when a photo is added, by 31 March 2027.
3. Not yet assessed: sign-in and multi-factor authentication on Auth0's pages (3.3.8 accessible authentication, among others), and everything the manual audit below covers. They are part of the service, chosen and configured by Neolung, so they are within scope.

We don't claim disproportionate burden for anything.

What we're doing to improve accessibility

The dates below were approved by Neolung's product owner on 22 October 2026.

• A manual audit (below) by 31 January 2027, before any organisation uses Neolung with patient data, then once a year and after any major change to how a screen works.
• The items above by the dates given.
• The automated check on every release (below) stays a gate.

Preparation of this statement

This statement was prepared on 22 October 2026 and last reviewed on 22 October 2026.

It is based on a self-assessment by Neolung's developers, using automated testing only:

• On every release, the end-to-end smoke test (e2e/) runs axe-core 4.13 with the WCAG 2.0, 2.1 and 2.2 A and AA rules, plus the experimental label-in-name rule (2.5.3), in the light and the dark scheme. Contrast of text on buttons whose background axe can't read (drawn by a pseudo-element) is measured separately, at 4.5:1. Any violation fails the build and blocks the release.
• It checks the main screens as they first load, at 1280 and 390 px wide, signed in as an admin, a trainee, an admin who doesn't report cases, the clinical lead, an operator, a pathologist giving second opinions and someone without an account, with some screens also in Spanish; and these states once opened: the profile menu, a case's history and second opinions, asking for a second opinion, setting up AI and speech from a case, a profile section and one clinical review question. Signing, amending and adding a supplement, field errors and recording aren't checked yet.
• Automated checks find only part of WCAG's failures; keyboard use, focus, meaning, screen reader output and timing need a person.

First run, 22 October 2026, and what was fixed: