SC3.2.1: Some designers didn't understand what the SC meant just by looking at the headline summary

[jfhector]

The headline summary currently reads:

Changes on focus: Make sure that just navigating to an interactive control with the keyboard doesn't trigger any action, and doesn't move the keyboard focus somewhere else.

Designers scored the clarity of that statement 3/5.

They wrote "it doesn't tell me what I shouldn't do"

[taliazdc]

I think there is an expectation during this testing that perhaps this would be the only level of detail provided. Would this be best remedied with an example which we will eventually provide? Is there a way to clarify with a simple example in the headline summary eg

Changes on focus: Make sure that navigating to an interactive control with the keyboard doesn't trigger actions or moves keyboard focus to elsewhere, such as automaticallly submitting forms.

I am of the opinion that providing an example of what they shouldn't do is too much detail for the headline, but that's just me

[jfhector]

Mm.. initially I read your post and thought "yes of course you're right, an example will help."

Then, I tried to come up with one. And it seems like the only typical failure of this success criterion is when developers programmatically move the keyboard focus elsewhere, automatically, when an element gets focused.

If I'm correct that that is the only typical failure, then that should be the example. (But we're already kind of naming that example).

Maybe a next step would be to look into what the typical failures of this success criterion are. Might be worth looking at the GDS WCAG primer, or the BBC guidelines.

Here's the official success criterion for reference:

Success Criterion 3.2.1 On Focus (Level A): When any user interface component receives focus, it does not initiate a change of context.

and 'change of context' is defined here.