Accessibility

A system is not useful if people cannot use it.

Hadenorbis targets WCAG 2.2 Level AA and treats accessibility as part of design, content, engineering and ongoing governance.

Current approach

Built into the system, then verified with people.

Automated checks can find important issues, but they cannot establish full conformance or replace keyboard, zoom, assistive-technology and human review.

Structure

Meaningful pages.

Landmarks, one clear page heading and logical section order support navigation and comprehension.

Input

Keyboard first.

Interactive controls are intended to work without a pointer and show a visible focus state.

Perception

Readable in both themes.

Concrete light and dark translations preserve hierarchy, contrast and non-colour cues.

Motion

Respect user preference.

Decorative motion is non-essential and reduced when the operating system requests less movement.

Feedback and support

Tell us where the system creates friction.

Useful reports include the page, task, browser or assistive technology involved and what you expected to happen. No diagnosis or personal medical information is needed.

Request an alternative or report a barrier

Email hello@hadenorbis.com with “Accessibility” in the subject. We will aim to acknowledge the report and explain the next step; a formal response-time commitment requires operational approval.

Known review areas

Complete manual testing across representative screen readers and browsers.
Verify all production content, media alternatives and downloadable documents.
Test 200% and 400% zoom, reflow and high-contrast preferences across public and protected routes.
Review any third-party provider or embedded experience before enablement.