Wcag22inbrief eow

[mbgower]

Including the "Why" phrase from EOWG, and repositioning above the normative text.

Previews of each:

• Accessible Authentication Min
• Accessible Authentication enh
• Consistent help
• Dragging movements
• Focus appearance
• Focus not obscured enh
• Focus not obscured min
• Redundant entry
• Target size min

[mbgower]

Received the following comments from @gundulaniemann in survey. I am going to respond here for posterity:

accessible authentication:
I am confused as to what is restricted with which accessible authentication level.
The what to do
"Don’t make people recognize objects or recall personal information to login"
and
"Don’t make people solve, memorize, or transcribe something to log in."
to me basically means the same. Rather the second restricts more, yet it was cited from the 'minimum' version.

You aren't alone in your observation that the SCs are cumulative but ALSO redundant. It make a challenge providing a succinct summary that stands alone. The WG previously voted not to restate the earlier requirement as part of the enhanced 'in brief'. I've nonetheless tried to add a tiny bit of connecting text, which has been reworded. Please review to see if it's any better.

Dragging Movements:
The SC is about mouse and touch, and the point is that the user cannot perform a reliable and exact dragging movement. This should be reflected int he Why it's important section.
Suggestion:
Some people cannot perform an exact dragging movement.

The EO folks are interested in focusing on inability as opposed to difficulty, hence "Some people cannot use a mouse to drag items". As well, although you are correct that touchscreens are relevant, the use of "mouse" was felt to be more immediately recognizable than "pointer", which is nonetheless used in the what to do section -- so 'mouse' provides a recognizable synonym.

Focus not obscured enhanced:
The point is not, what people do not use nor whether they would be able to use a mouse, but what users in fact chose to use.
Why it's important: People who use a keyboard need to easily see what has keyboard focus.

focus not obscured minimum:
The point is not, what people do not use nor whether they would be able to use a mouse, but what users in fact chose to use.
Why it's important: People who use a keyboard need to see what has keyboard focus.

Getting back to the EO perspective, many people not as familiar with accessibility will more quickly understand 'oh, it's for people who can't use a mouse'. The keyboard is obviously present in the same sentence and in the prior line. And of course the Understanding document provides in depth infor on the needs of those reliant on the keyboard API. This wording also gets us away from saying "keyboard" twice in one brief line!

redundant entry:
not sure about the grammar as I not a native speaker.
Some people with cognitive disabilities have difficulty to remember what they entered before.

Corrected

target size minimum:
I prefer "cannot" instead of "find it hard to".

Adopted.