Accessibility
Accessibility Statement
RelayHub is being designed so ordinary people can understand, operate, recover, and use local-first communication infrastructure without needing specialist technical knowledge.
1. Our Commitment
RelayHub aims to make its website, documentation, products, and user interfaces accessible, understandable, and usable by as many people as practical.
Accessibility is not treated as an optional extra. It is part of the product’s usability, recovery, safety, and trust model.
2. Plain Language
RelayHub avoids unnecessary technical language wherever possible. User-facing materials should explain outcomes, risks, limitations, and next steps in ordinary language.
Terms such as Ready, Local-Only, Degraded, Updating, Recovering, and Error should be explained clearly and consistently.
3. Visual Accessibility
RelayHub aims to support readable text, strong contrast, responsive layouts, and clear visual hierarchy.
Status should not rely on colour alone. Where practical, status should also be communicated through text, icon shape, pattern, label, or supporting explanation.
4. Keyboard and Screen Reader Support
Core website and product flows should be usable with keyboard navigation and meaningful labels for assistive technologies.
Important actions such as setup, support export, recovery, update approval, reset, and transfer should not depend solely on mouse or touch interaction where a keyboard-accessible alternative is practical.
5. Mobile Accessibility
RelayHub’s website and future local web interfaces should work on mobile-width screens, including phones used during setup, recovery, and field operation.
6. Recovery Accessibility
Recovery instructions should be findable, readable, and usable under stress. Recovery should not depend on hidden knowledge, terminal access, or specialist expertise for ordinary user flows.
7. Documentation Accessibility
Documentation should be structured, searchable, printable where useful, and written for both non-technical users and deeper technical operators.
Critical setup and recovery guidance should remain available offline where practical.
8. Current Status
RelayHub is currently in early design and validation planning. Accessibility work will continue as product pages, documentation, local interfaces, and support materials are developed.
9. Feedback
Accessibility feedback can be sent to:
hello@relayhub.tech