SleepNav is currently in beta.

Accessibility Statement for SleepNav CDSS

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.

How accessible this website is

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.

What to do if you cannot access parts of this website

If you need information on this website in a different format, or if you experience any accessibility barriers, please contact us:

Reporting accessibility problems

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.

Technical information about this website’s accessibility

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. No known non-compliances remain at the date of this statement. Automated accessibility scanning is not currently part of our build pipeline; adding it was a recommendation of the 18 March 2026 audit and remains outstanding. Until it is in place, accessibility is re-checked by manual review when pages change.

Non-accessible content

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.

Issues identified and remediated on 18 March 2026

  • Skip-to-main-content link was missing on all pages (WCAG 2.4.1 Bypass Blocks). Now added to all pages.
  • Focus indicators were missing on interactive buttons in the guided consultation (WCAG 2.4.7 Focus Visible). Focus-visible ring styles now applied to 50+ interactive elements.
  • Form labels were not associated with inputs on the settings page, and the dashboard code input had no label (WCAG 1.3.1 Info and Relationships). Labels now correctly associated via for/id attributes; screen-reader-only labels added where visual labels are not appropriate.
  • Table headers were missing scope attributes across all data tables (WCAG 1.3.1). scope=“col” now applied to 97 header elements across 13 templates.
  • Colour contrast failures on several elements (WCAG 1.4.3 Contrast Minimum): brand green backgrounds with white text (3.19:1, now 4.57:1), placeholder text (2.54:1, now 4.83:1), LOW risk badge (3.30:1, now 5.02:1), and clinical “Not assessed” display text (2.43:1, now 4.63:1). All now meet the 4.5:1 AA minimum.
  • Decorative SVG icons were not hidden from assistive technology. aria-hidden=“true” now applied to 21+ decorative SVGs.
  • Modal dialogs (lightbox, MFA) lacked proper ARIA roles and focus management. Now include role=“alertdialog”, aria-modal, aria-labelledby, focus save/restore on close.

Disproportionate burden

No disproportionate burden claims are made. All identified issues have been remediated.

Content not within scope of the accessibility regulations

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.

Preparation of this accessibility statement

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.

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 against the server, which lacks the shared libraries required for headless Chromium and where the deploying user has no permission to install them.

We tested the following pages and flows:

  • Login and MFA authentication
  • Dashboard
  • Code decode and guided consultation (all 6 phases)
  • Patient report generation
  • Knowledge Navigator
  • Account settings
  • Admin dashboard (pharmacy and pharmacist management)