SleepNav CDSS – Accessibility Statement. Last updated: 5 September 2026.
This accessibility statement applies to the SleepNav Clinical Decision Support System at cdss.sleepnav.com.
This website is operated by Snorer.com Ltd. We want as many people as possible to be able to use this service. That means you should be able to change colours, contrast levels and fonts using browser or device settings, navigate most of the website using a keyboard, and use the website with a screen reader.
We are committed to making SleepNav accessible to all pharmacist users. The system is a web-based application accessed via standard browsers. Following a comprehensive WCAG 2.2 Level AA audit on 18 March 2026, all identified issues have been remediated.
The audit found that the site already had correct semantic landmarks, heading hierarchy, language attributes, and full keyboard navigation without traps. Remediation addressed colour contrast, focus indicators, form label associations, table header semantics, ARIA roles on modals, and a skip-to-content link. The site uses proper heading structure (h1 through h4), semantic HTML landmarks, and all clinical alert banners pass colour contrast requirements.
If you need information on this website in a different format, or if you experience any accessibility barriers, please contact us:
We are always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we are not meeting accessibility requirements, please contact us at contact@sleepnav.com.
Snorer.com Ltd is committed to making this website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This website is partially compliant with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. A comprehensive audit was conducted on 18 March 2026. All issues identified during the audit have been remediated. Automated accessibility scanning, which that audit recommended, was implemented on 5 September 2026 and its coverage was widened the same day: an axe-core scan of forty-one pages, being the ten public pages, thirteen pages of the pharmacist service, the locked-session screen, the page-not-found and access-denied error pages, and fifteen administrative pages, held to a recorded baseline so that the number of detected issues may fall and may not rise. It is run on demand; running it automatically on every change is not yet in place and remains outstanding. The baseline is 464 detected issues across those forty-one pages: 453 colour contrast, 10 form fields without an associated label, and one link distinguished only by colour. Thirty of those pages had never been scanned before, and 379 of the 464 issues are on them, so the rise from the first baseline of 85 is the first measurement of pages not previously measured rather than a deterioration in any page. Six of the 464 arose when the page-not-found page was moved onto the shared page template: it previously used its own private styling and so avoided seven contrast issues that the shared template carries on every other page, and those seven are counted honestly here rather than avoided by keeping that page inconsistent. One template has no automated coverage and we say so rather than imply otherwise: the server-error page, which cannot be reached without provoking an unhandled error. These are long-standing rather than new, and the manual method used in March did not surface them; we record them here rather than report their absence, and they are being addressed. Accessibility continues to be re-checked by manual review when pages change.
A WCAG 2.2 AA audit conducted on 18 March 2026 identified 29 issues (4 critical, 14 serious, 9 moderate, 2 minor). All issues were remediated on the same date. The following summarises the issues found and the actions taken.
No disproportionate burden claims are made. All identified issues have been remediated.
Patient-facing PDF reports generated by the system are not covered by these regulations. The PDF reports contain no patient-identifiable information and are intended to be printed and annotated by the pharmacist in consultation.
This statement was prepared on 18 March 2026 and was last reviewed on 18 March 2026. It was revised on 14 August 2026 to correct the description of the testing method below; no re-test was carried out on that date and no finding changed. It was revised again on 5 September 2026, when automated scanning was implemented and run for the first time, and later the same day when that scanning was widened from eleven pages to forty-one; the 18 March findings and their remediations are unchanged, and the issues that scan detects are reported above.
This website was last tested on 18 March 2026. Testing was carried out internally by manual expert analysis: review of the rendered HTML of 16 pages fetched with an authenticated session, static analysis of the page templates, CSS inspection and JavaScript review, together with keyboard navigation, colour contrast and screen reader landmark checks. Automated browser-based scanning (axe-core, pa11y) could not be run at that time: the server lacks the shared libraries headless Chromium needs and the deploying user cannot install system packages. That obstacle was resolved on 5 September 2026 by unpacking those libraries into the user's own directory, which needs no such permission, and automated scanning has run since.
We tested the following pages and flows: