RigWave accessibility
Simple language and usable controls are part of the product, not decoration.
Website target: WCAG 2.2 AA, verified rather than assumed.
The site includes a keyboard skip-to-content link, visible focus treatment, focus spacing and reduced-motion handling. Accessibility will continue to be checked with real keyboard, zoom, mobile and screen-reader testing before public launch.
Need an accessibility adjustment or accessible support?
If a disability or access need makes this site, the private-beta process or RigWave harder to use, email support@rigwavesystems.co.uk. Tell us the barrier you hit and the practical reasonable adjustment or accessible format that would help. You do not need to send medical details for an ordinary adjustment request. If the normal self-service route is not usable, ask for an accessible alternative. Do not send passwords, stream keys, API keys or payment-card details.
This is a support and adjustment route, not a claim that every final accessibility check has already passed. Final supported accessibility behaviour remains tied to the exact tested release.
Plain English
Instructions should tell the user what to press, what will happen and what result to expect, without assuming technical knowledge.
Readable interface
Strong contrast, scalable text and clear status wording are design requirements.
Keyboard and focus
The final release should verify keyboard navigation and visible focus where the control type supports it.
Warnings that explain
A warning should say what the risk is and what the safe next action is, rather than showing a vague error.
Reduced overload
Users should be able to work through a small number of clear choices rather than face every advanced setting at once.
Verified at launch
Final supported accessibility behaviour must be tested on the exact public release and listed honestly.
Calm progress, not flashing screens
Long-running work should show meaningful milestones without repeatedly repainting the whole interface or changing captions every few seconds.
Predictable help and next actions
Help, recovery and ADVANCED DETAILS should stay in consistent places so the user does not have to remember where each screen hides them.
Focus stays visible
Keyboard focus must remain visible and should not be hidden behind sticky navigation or other author-created content.