Our target
Nyxora Sync aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. This is a target, not a certification. The site has not yet been independently audited.
What is in place
- Semantic headings, landmarks, lists, and form labels; a visible focus outline on interactive elements.
- Keyboard-operable navigation, dialogs, menus, filters, and forms, including Escape to close dialogs.
- Text alternatives for meaningful icons and empty alt text for decorative images.
- Theme-aware color contrast designed against the WCAG AA thresholds for normal and large text.
- Layouts that reflow at 200% zoom and on narrow screens without requiring horizontal scrolling for prose.
- No autoplaying audio or video. The homepage has a slow, low-contrast ambient visual that becomes a still image when reduced motion is requested.
- Reduced-motion support: page transitions, reveal effects, and the homepage visual are removed or made static when your system asks for less motion.
- Code blocks that remain readable and copyable without a mouse.
- Forms that report errors in text, not color alone, and keep their labels associated with inputs.
Known limitations
- No independent audit yet. The checks above are part of development, not a formal conformance test with assistive technology.
- The code playground. The live preview runs inside a sandboxed frame and the editor is a plain text area. Some screen-reader and mobile keyboard combinations may still be awkward; the lesson text and code samples are complete without the playground.
- User-generated images. Project screenshots are treated as decorative. A project owner can describe the image in the project description, but there is no separate alt-text field yet.
- Third-party resources. Linked videos, articles, and documentation are outside our control and may not meet the same standard.
- Older lessons. A few diagrams or long code samples may need better structure on small screens. They are being fixed as they are reviewed.
How we test
Accessibility is checked during development with keyboard-only navigation, browser zoom, automated linting, and contrast review of the theme palette. When a barrier is reported, we reproduce it, fix it, and add the case to the checks for future changes.
Compatibility
The site is tested in current versions of Chrome, Firefox, Safari, and Edge on desktop, and in mobile Safari and Chrome on a small viewport. It does not require JavaScript for reading lessons, but interactive progress, the playground, and community features do.
Report a barrier
If something blocks you, use the contact form and choose “General question” or “Bug or broken page”. Describe the page, what you were trying to do, the assistive technology or input method you use, and what happened. You can also open a GitHub issue labeled accessibility.
We will acknowledge the report, tell you whether we can reproduce it, and explain what we plan to do. Reports about a lesson's code or explanation are handled like any other content correction.
Feedback on this statement
This statement is reviewed when the site changes substantially. If something here is inaccurate, say so through the contact form; an honest statement is more useful than an optimistic one.