Accessibility — Ubuntu Roots Coaching™

Last updated: September 2026

At Ubuntu Roots, belonging is meaningless if anyone is excluded. This site is built with accessibility as a foundational principle, targeting conformance with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. If you encounter a barrier, please tell us — we are committed to continuous improvement and will respond promptly.

1. Our commitment

Digital spaces should reflect the inclusivity we champion in our practice. Whether you navigate with a screen reader, rely on keyboard input, experience cognitive differences, or use assistive technologies, we want this site to be usable by you. That commitment includes ongoing improvement, transparent communication about our current status and known limitations, and a responsive approach when barriers are reported.

2. What we have implemented

The following are in place today.

Semantic structure

Content uses proper HTML landmarks and a logical heading hierarchy for screen-reader navigation.

Skip navigation

A "Skip to content" link lets keyboard users jump straight to the main content.

Keyboard operability

The interactive elements — the five-dimensions selector and the Living Tree diagram and its enlarge view — are operable by keyboard, with focus managed so nothing traps or strands you.

Visible focus

Interactive elements show a clear focus indicator when reached by keyboard.

Colour is never the only signal

Where colour conveys meaning, labels and text carry the same information, so nothing depends on colour alone.

Reduced motion

We honour the prefers-reduced-motion system setting.

Responsive layout

The site reflows for different screen sizes and supports zooming to 200% without loss of content.

Text alternatives

Meaningful images carry descriptive alternative text; decorative graphics are marked so assistive technology can skip them.

3. Known limitations

We aim for full conformance and prefer to be honest about where we are not yet there. As of the date above:

Our most recent audit identified a text-contrast issue on some elements, which we are correcting.
We are completing verification of form error messaging and mobile touch-target sizing against the WCAG 2.2 AA minimums.

This section is updated as items are resolved.

4. Compatible technologies

We aim to support commonly used assistive technologies and current browsers. Older versions may experience degraded accessibility.

Screen readers

NVDA, JAWS, VoiceOver, TalkBack, and Narrator.

Browsers

Current versions of Chrome, Firefox, Safari, and Edge.

Input methods

Keyboard and switch navigation, speech recognition, and touch interfaces.

5. How to report a barrier

Your feedback directly shapes our work. Please email [email protected] with the page, a description of the problem, and the assistive technology you were using, if any. We aim to acknowledge reports within a few business days and to prioritise fixes by severity — barriers that block essential tasks first.

6. Escalation

If you are not satisfied with our response, you may request a further review by replying to the same address, and you retain the right to lodge a complaint with the relevant authority in your jurisdiction (for example, the U.S. Department of Justice or a state attorney general in the United States, or your local supervisory authority in the EU or UK).

Belonging is universal

This statement is an affirmation of our core philosophy: belonging cannot be selective. When someone cannot access this space because of a barrier we created or failed to remove, we have fallen short of the spirit of Ubuntu. Thank you for holding us accountable.

Umuntu ngumuntu ngabantu — a person is a person through other people.

This statement describes our current accessibility practices and commitments as of the date noted above and is not a warranty of specific performance. WCAG is a trademark of the World Wide Web Consortium (W3C).