Foundations
Accessibility
Neoncite/UI targets keyboard, focus, naming, contrast, reduced-motion, and semantic accessibility while preserving an intentionally dark visual system.
Dark-only constraint
Neoncite/UI is intentionally dark-mode only. It does not support light mode. Projects with accessibility requirements for light interfaces or high-contrast modes should evaluate whether this constraint is compatible with their needs. prefers-contrast: more is partially supported through increased glow intensity.
In the current token implementation, high-contrast preference strengthens hairlines and muted text while reducing non-essential glows to limit visual noise. The sentence above is retained verbatim as the public compatibility notice requested for the project.
Interaction baseline
- • Interactive controls must expose an accessible name, including icon-only buttons.
- • Focus-visible indication must remain perceptible on OLED-black surfaces.
- • Radix-backed composites preserve their documented keyboard and focus behavior.
- • Non-essential animation respects prefers-reduced-motion.
- • Neon accents used as body-size text are checked against the OLED-black surface.
Contrast preferences
Under prefers-contrast: more, the token layer raises hairline visibility to approximately 40%, increases muted-text contrast, and suppresses decorative glow shadows. This is partial high-contrast support rather than a promise of a separate high-contrast theme.
Testing
The repository combines React Testing Library behavior tests with Playwright and axe checks. Automated checks supplement manual keyboard, screen-reader, zoom, forced-colors, and platform accessibility testing; they do not replace it.