1. Overview

Lesson 2 gave each element a name, a role and a state. This lesson is about how the elements fit together. A TalkBack user meets your screen one item at a time, in a line. So the order of that line matters. Headings let them skip ahead. Actions hidden in gestures must be reachable another way. Changes that happen away from their focus must be announced.

Several WCAG 2.2 criteria cover this. 1.3.2 Meaningful sequence and 2.4.3 Focus order cover the order. 2.4.6 Headings and labels covers headings. 2.5.1 Pointer gestures and 2.5.7 Dragging movements cover gestures. 4.1.3 Status messages covers announcements. EN 301 549 carries them as clauses 11.1.3.2, 11.2.4.3, 11.2.4.6, 11.2.5.1, 11.2.5.7 and 11.4.1.3. Clause 11.2.4.2 Non-web software titled replaces Page titled. The 11.5.2 accessibility-service clauses add actions (11.5.2.11 and 11.5.2.12), focus (11.5.2.13) and change notification (11.5.2.15).

Standards covered: WCAG 2.2 success criteria 1.3.1, 1.3.2, 2.1.1, 2.4.3, 2.4.6, 2.4.7, 2.5.1, 2.5.7 and 4.1.3 · EN 301 549 V4.1.1 clauses 11.1.3.1, 11.1.3.2, 11.2.1.1, 11.2.4.2, 11.2.4.3, 11.2.4.6, 11.2.4.7, 11.2.5.1, 11.2.5.7, 11.4.1.3, 11.5.2.11 to 11.5.2.13 and 11.5.2.15.

Unlock the rest of this lesson

You have read the free preview of Reading order, groups, custom actions and announcements in Module 6: Android accessibility. The full lesson, its knowledge check and the module certificate come with a plan, bought here on the web.

Buy a plan here with a card and the rest of the course unlocks. You will sign in first, with Apple or Google, which is what the plan is attached to. No iPhone or Mac needed.

Buy a plan Already bought? Sign in

Free with no account: the first lesson, Why accessibility, and who it is for, the European Accessibility Act flashcards and the overview of every lesson.

Sources