Focus Maintains Context

[chriscm2006]

A focus change should not result in a context change, such as focusing another control.

Effected Technology: TalkBack
Type: Serious - WCAG 2.1 A - Violation
Success Criteria: 3.2.1

User Story

As a TalkBack User I am using an Activity that utilizes constraint layouts heavily.

Inaccessible

1. Open an Activity
2. Move Accessibility Focus to a View(1)
3. This View initiates an Accessibility Focus event to View(2)

The Change of Context in 3 is in violation of WCAG 3.2.1.

Accessible

1. Open an Activity
2. Move Accessibility Focus to a View
3. Focus remains on View(1)

[goodwitch]

@chriscm2006 I'm looking super closely at the normative for WCAG 2.1 SC 3.2.1 On Focus: When any component receives focus, it does not initiate a change of context. (Level A)

In step 1, I believe "open an ACTIVITY" is not a change in focus, but a user activating a control.
Step 2 is the result of a person triggering that "ACTIVITY" (ACCESSIBILITY FOCUS is moved to a VIEW)
Step 3 moves ACCESSIBILITY FOCUS to another control (the user didn't do anything)

What worries me...is that I perceive the VIEW as "not a control". Yes...we have ACCESSIBILITY FOCUS going from VIEW to another control with no user interaction...but is it "another control" on the same screen? In the normative, component means a user interface control, not just static content. And in the micro-moment of loading a VIEW, moving ACCESSIBILITY FOCUS to a useful user interface component/control (like a search field) on that page would be allowed.

I think to meet the F52: Failure of Success Criterion 3.2.1 and 3.2.5 due to opening a new window as soon as a new page is loaded it would need to go like this:

1. Open an ACTIVITY
2. Move ACCESSIBILITY FOCUS to a VIEW(1)
3. This VIEW initiates an ACCESSIBILITY FOCUS event to another VIEW(2)

What do you think?

[chriscm2006]

I believe I was not as semantically correct as you are, but we are on the same page. I'll update to your wording. What if I added a step

2.B: No new content is loaded.

Could the more general wording then apply? Curiosity, NOT important for this Issue.

[goodwitch]

Chris, Yes. I'm on board. Minor edit suggestion...where you have just the word "View"....I suggest changing it to View(1) so everyone who reads it is crystal clear.

Inaccessible

1. Open an Activity
2. Move Accessibility Focus to a View(1)
3. This View**(1)** initiates an Accessibility Focus event to View(2)
4. The Change of Context in 3 is in violation of WCAG 3.2.1.

Accessible

1. Open an Activity
2. Move Accessibility Focus to a View(1)
3. Focus remains on View(1)