Accessibility · more than one path

Learning should not depend on a single way of seeing or moving.

The support site and app are designed around clear hierarchy, readable contrast, touch-sized controls, alternatives to visual-only navigation, and motion that respects device preferences.

Structure

Semantic landmarks

Headings, lists, navigation labels, meaningful link text, and a skip link support keyboard and assistive-technology navigation.

Perception

Contrast and scale

Information is not communicated by color alone. The layout adapts to smaller screens and browser text enlargement without requiring a desktop width.

Motion

Reduced-motion respect

Decorative reveal and canopy motion stop when the device or browser requests reduced motion.

Input

Keyboard and touch

Interactive controls have visible focus states, descriptive labels, and practical touch targets. There are no drag-only tasks.

App navigation

List alternative

The app provides a list-oriented path in addition to the visual canopy map so learning does not depend on interpreting a diagram.

Language

Plain boundaries

Educational purpose, fictional cases, privacy behavior, and non-application status are stated directly rather than hidden in decorative copy.

Feedback route

Report an access barrier.

If a current app or support-site feature is difficult to use, contact the developer through the contact shown on the current Google Play listing. Include the page or screen, device or browser, assistive technology if relevant, and the action you were trying to complete.

Do not include confidential organizational, applicant, donor, beneficiary, financial, health, or grant information in an accessibility inquiry.