By Vanale Apps · Studio learning guide · Sources and corrections
Published September 11, 2026
Try one task at a smaller screen width
Open a lesson or passage on a phone-sized screen. Can you read, navigate, and finish without scrolling sideways? If an important explanation appears only in a tiny screenshot, look for an equivalent text explanation. The W3C reflow criterion is a useful reference for why layout should adapt.
Enlarge text and use the keyboard
Increase browser text size or zoom, then try the same task again. Check whether labels disappear or controls overlap. If you use a keyboard, move through menus, buttons, and links without a mouse; the focus indicator should be visible and the order should make sense. W3C's resize-text guidance describes the underlying accessibility goal.
Check audio, video, and motion
If a lesson uses speech, look for captions or a usable text alternative. If animation is distracting, check whether a reduced-motion preference is respected. A visual effect should not carry essential instructions that disappear when motion is reduced.
Test the return path
After opening a lesson, can you find the next chapter, return to the index, and reach help? Write down the step where you got stuck. A specific blocked task is more actionable than a vague report that an app is “not accessible.”
Report what happened
Include the page, device, browser, assistive technology if used, expected action, and actual result when contacting product support. A company hub and each linked product can have different implementations; do not assume this guide certifies any product's accessibility. See the hub accessibility page for its own scope and feedback route.