2.5.8: Further Examples Required

[benja11y]

To fully understand the impact this SC will have, further examples should be provided that include complex widgets that contain multiple, but separate, discrete targets. Examples could include material design style navigation drawers, date pickers, compact tab controls, ARIA <select>-style controls or interactive toast messages that partially obscure content underneath.

This issue has been raised on behalf of TPGi, based on an internal consultation process. An article containing all of our comments can be found on our blog, along with an introduction and acknowledgments.

[detlevhfischer]

@benja11y I had a look at the various material design components and nothing strikes me as potenial fail here. Elements may be smaller than 24 x 24 px but there seems to be always ample spacing. So I am just curious where you see the benefit of adding examples from that design vocabulary. I would imagine edge cases ould be more important to cover.

[detlevhfischer]

@benja11y I just checked a few of the ARIA Authoring practices examples: Date picker spin button example: Spin buttons 20 x 20 px but sufficient space above and plenty sidewards

Combobox examples: The example below shows line height is set to 24 px so it just meets the SC:

The same seems to be the case on the other combobox examples. If there are any examples you'd like to call out, let me know. So far I do not see what adding further examples from either source will add.

[becka11y]

@benja11y I believe the above comment is for you :-)

[detlevhfischer]

Proposed Working Group answer: The Target Size (Minimum) requirement does not apply to targets while they are (partly) obscured by dynamic content, but it does of course apply to targets in any new content displayed (as long as it is not subject to one of the exceptions). To clarify this, we have added a new section to the Understanding document of Target Size (Minimum). #2024

[alastc]

Closing with #2024