Our commitment and reference standard
NeuqOS is working toward a public experience that people can perceive, understand, navigate, and operate in different ways. We use the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as our current design and review reference.
This statement is not a certification. Accessibility depends on code, content, devices, assistive technologies, third-party services, and the task a person is trying to complete.
What the current experience supports
Across much of the public site, the experience includes:
- responsive layouts that adapt to smaller screens and text resizing;
- visible text labels on primary forms and controls;
- keyboard-operable native links, buttons, and form inputs where those elements are used;
- headings and page structure intended to make long content easier to scan;
- text alternatives for many meaningful images and icons marked as decorative where appropriate; and
- plain-language explanations and a direct contact route when an automated path is not suitable.
Support can vary by page. The list describes current design practices; it does not promise that every instance is already perfect.
Known limitations we are not hiding
- Motion: animation is used across public pages, and reduced-motion behaviour is not yet consistent everywhere.
- AI conversation: streamed or changing Ask Neuq content may be difficult for some screen-reader and cognitive-access users.
- Visual material: some charts, diagrams, product demonstrations, and decorative visualizations may need stronger text equivalents.
- Focus and keyboard paths: custom menus, dialogs, and interactive demonstrations have not all been verified end-to-end with keyboard-only use.
- Third-party experiences: Calendly and linked services are controlled partly by their providers and may behave differently from the NeuqOS site.
- Documents: older or supplied PDFs and downloadable documents may not have complete tags, reading order, or text alternatives.
These are active review areas. Publishing a limitation begins accountable repair. The work continues until the barrier is addressed or a dependable alternative exists.
Report a barrier or ask for another route
Email josh@neuqos.com with “Accessibility” in the subject line. Tell us:
- the page, document, or task;
- what got in the way;
- the format or outcome you need; and
- your browser, device, or assistive technology only if you are comfortable sharing it.
We will acknowledge the request, assess the barrier, and work with you on a reasonable alternative or repair. Depending on the material, an alternative might be a plain-text explanation, a document in another format, help completing a step, or a direct conversation.
How this statement stays useful
We review this statement when the public interface, core interaction patterns, or major third-party services change. The date above identifies the current public version.
The next material accessibility milestone is an end-to-end keyboard, focus, motion, contrast, form-label, and screen-reader review of the highest-use public journeys. Until that evidence exists, NeuqOS will not claim full WCAG conformance.
