Access is part of website quality.

Nardux is working to keep this website understandable, keyboard-usable, responsive and compatible with common user preferences while testing continues.

Implemented features and open verification are stated separately.

The current website has passed HTML validation, Lighthouse accessibility audits and axe WCAG checks in Chrome and Firefox across all 28 pages. Scripted evidence also covers keyboard interaction, form announcements, 320px and 640px reflow, custom text spacing, reduced motion and forced colours.

Native NVDA testing in current Chrome and Firefox, VoiceOver with Safari and representative physical-device testing remain pending. Automated and scripted checks do not establish formal WCAG conformance.

Foundations that support different ways of navigating.

STRUCTURE

Semantic content

Headings, landmarks, lists, tables, breadcrumbs and native disclosure elements organize page meaning.

KEYBOARD

Operable navigation

The mobile menu supports keyboard opening, tab navigation, Escape dismissal and focus return.

FOCUS

Visible position

Interactive controls use visible focus treatment, and every page provides a static skip link that works without JavaScript.

REFLOW

Narrow-width layout

Primary content reflows at 320 CSS pixels, with wide comparison tables contained in labelled scroll regions.

PREFERENCES

Motion and contrast support

Styles include reduced-motion and forced-colour considerations while preserving information without animation.

RESILIENCE

No-JavaScript fallbacks

Core content, primary navigation and page actions remain available when custom enhancement scripts do not run.

Automated and keyboard checks are not complete conformance evidence.

Browser automation cannot fully assess comprehension, screen-reader experience, magnification, voice control, cognitive load or every operating-system and browser combination.

Native VoiceOver with Safari, NVDA and representative physical-device testing have not been completed. The site uses a self-hosted font with an Arial fallback; initial page rendering does not depend on a third-party font request.

If a page, control, document or contact method creates a barrier, use the accessibility email below and request an alternative format or route.

Tell us what prevented access.

Email admin@nardux.com. Nardux will review what can be reproduced, identify an interim alternative where practical and track a correction or documented limitation.

No public response-time guarantee is made before the role mailbox and operating coverage are production-tested. Do not include passwords, user-generated content, health information or other sensitive case material.

Page title or safe URLTask you were trying to completeWhat happened insteadBrowser and device if knownAssistive technology if relevantPreferred contact or format

This statement covers the public Nardux website.

It does not certify third-party websites, client systems or future tools merely linked from or discussed on these pages.

Last updated: October 18, 2026

This statement will be revised when production deployment, assistive-technology testing, legal review or material website changes provide new evidence.

Questions about this statement.

Does Nardux claim WCAG conformance?

No formal conformance level is currently claimed. The available automated and scripted WCAG 2.2 AA test matrix passed, while native screen-reader, Safari and physical-device acceptance remains open.

Can I request information in another format?

Yes. Email the accessibility contact with the page or information needed and the preferred format. Availability depends on the source material and a practical accessible alternative.

Does the site work without JavaScript?

Core content, the fallback primary navigation, page links and skip link remain available. JavaScript enhances the shared navigation and interactive form experience.

What should I avoid sending in a barrier report?

Do not send passwords, client data, user content, health details or sensitive case evidence. A safe description of the page, task and observed barrier is enough to begin.

Found a barrier on the public website?

Send the page, task and problem in the format that works for you.

Email Accessibility