Testing display preferences, touch, and media

What you will learn

• Prepare comparable test environments and record settings, devices, input methods, and limitations.
• Establish keyboard and zoom-and-reflow baselines before changing specialized presentation or input conditions.
• Assess whether information, controls, states, and focus remain perceivable in forced colors.
• Assess automatic movement, user controls, reduced-motion behavior, and possible flashing safely.
• Test touch-target spacing, gesture alternatives, pointer cancellation, and task availability across portrait and landscape orientations.
• Compare audio, captions, transcripts, meaningful visual information, and player behavior while separating authored content from platform support.
• Classify evidence as a finding, passing behavior, a support limitation, or an incomplete check and identify proportionate follow-up testing.

Follow the path

1. Path checkpoint

   Prepare comparable test environments

   Record comparable environments, establish an ordinary baseline, and change one display, input, device, or media condition at a time.

   15 minutes

2. Testing method

   Testing keyboard accessibility

   Check whether every interactive element can be reached, identified, and operated with a keyboard in a logical sequence.

   15 minutes

3. Exercise

   Keyboard testing a preferences form

   Investigate a communication-preferences form and find four problems that affect keyboard access, operation, focus order, or focus visibility.

   15 minutes

4. Testing method

   Testing zoom and reflow

   Check whether content and functionality remain available when text is enlarged and the page reflows into a narrow CSS viewport.

   20 minutes

5. Exercise

   Testing an appointment booking at high zoom

   Test an appointment-booking page at a narrow zoom-equivalent width and with text enlarged to find four reflow and resizing problems.

   20 minutes

6. Testing method

   Testing forced colors and high contrast

   Check whether information, controls, states, and focus remain perceivable when a browser applies forced colors.

   20 minutes

7. Exercise

   Testing forced colors in a journey planner

   Compare a public-transport journey planner before and after forced colors and investigate lost information and interaction cues.

   20 minutes

8. Testing method

   Testing motion, animation, and flashing

   Check whether moving and animated content can be controlled and whether a page respects reduced-motion preferences safely.

   20 minutes

9. Exercise

   Testing motion preferences on a parcel-tracking dashboard

   Compare a parcel tracker before and after reduced motion and investigate movement that continues or cannot be controlled.

   20 minutes

10. Path checkpoint

    Separate defects from expected adaptation

    Classify observations consistently, separate authored behavior from platform support, and consolidate symptoms of one underlying problem.

    15 minutes

11. Testing method

    Testing mobile touch and orientation

    Check target size and spacing, orientation support, gesture alternatives, and pointer cancellation on touch interfaces.

    25 minutes

12. Exercise

    Testing touch interaction on a community-festival map

    Investigate target geometry, orientation, gesture alternatives, and cancellation in a festival map and schedule.

    25 minutes

13. Testing method

    Testing media accessibility

    Check prerecorded captions, transcripts, visual description, autoplay, and essential player operation across media alternatives.

    25 minutes

14. Exercise

    Testing a community announcement video

    Investigate captions, transcript content, visual-only information, and native player behavior in a short community-centre announcement.

    30 minutes

Complete this path across several sessions if needed. Revisit each Testing method while you complete its paired Exercise, and keep one comparison record so you can interpret what changes between test conditions.

The Exercises use separate fictional interfaces rather than one continuous product. Carry a consistent evidence structure between them, not application state or one cumulative target finding count. A useful result may be expected adaptation, passing behavior, an incomplete check, a platform-dependent observation, or a finding; not every condition should preserve authored styling or expose a defect.

Prepare comparable test environments

You need only:

• Basic familiarity with using a web browser
• Basic keyboard use

Individual methods may also ask you to use browser developer tools, operating-system settings, a physical or emulated mobile device, or media controls. Prepare only the environments you can test responsibly, and record when another device or platform is still needed.

Before each method-and-Exercise pair:

1. Record the device, operating system, browser, viewport, input method, theme, zoom or text-size condition, relevant user preferences, and available media support.
2. Identify which results come from physical hardware and which come from browser emulation. Treat emulation as useful evidence, not proof of physical-device behavior.
3. Learn how to enable and restore forced colors or another relevant contrast setting and the operating system’s reduced-motion preference before changing them.
4. Establish the primary task and its ordinary presentation, then change one condition at a time so comparisons remain meaningful.
5. Keep keyboard, pointer, touch, visual, and media observations distinct. One result must not stand in for a condition you did not test.
6. If content may flash, avoid prolonged exposure and follow the motion method’s safety guidance before investigating further.

This checkpoint prepares comparable conditions. Use each Testing method for its specific procedure and interpretation guidance.

Separate defects from expected adaptation

After keyboard, zoom and reflow, forced-colors, and motion practice, pause to classify what you observed before changing device and media conditions.

Distinguish between:

• an expected change in color, layout, animation, orientation, or player presentation;
• loss of information, operation, focus visibility, or task completion;
• behavior controlled by the author and behavior controlled by the browser, operating system, device, assistive technology, or media platform;
• a passing check and a check that remains incomplete; and
• one underlying problem and several symptoms of it under different conditions.

For relevant observations, record the task and state, tested condition, steps, expected and actual result, user impact, environment limitation, remediation direction, and retest condition. Not every field applies to every observation. Use the structure to keep enough evidence for another person to reproduce the result and to consolidate related symptoms without hiding meaningful differences between environments.

Where to go next

Apply the six techniques together in Reviewing a community centre open day before launch. The Testing journey uses one realistic workspace and asks you to make an evidence-based launch recommendation.

Use Your first accessibility review for optional broader practice with automated checks, visual review, text spacing, and forms. It is not a prerequisite for this self-contained path.

Keep the scope in mind

These six techniques do not form a comprehensive audit or conformance assessment. Emulation does not establish physical-device behavior, and one platform or media-player combination does not establish universal support. For real products, define the untested scope, arrange additional specialist testing where needed, and involve disabled people whose experiences and ways of using technology may differ from your own.

Read about the full scope and limitations of the Lab, including what its technical checks can and cannot establish.