w3c / wcag

Web Content Accessibility Guidelines
https://w3c.github.io/wcag/guidelines/22/
Other
1.1k stars 250 forks source link

Target size minimum lacks guidance in the Understanding document on inline text #3500

Open mbgower opened 11 months ago

mbgower commented 11 months ago

During the formation of the SC, there was a lot of discussion on inline text and how to formulate wording that guided teams to how to determine when a link needed to have sufficient vertical space.

There is little about that in the understanding document. All it says is

Inline: The Success Criterion does not apply to inline targets in sentences, or where the size of the target is constrained by the line-height of non-target text. This exception is allowed because text reflow based on viewport size makes it impossible for authors to anticipate where links may be positioned relative to one another. When multiple links are embedded in blocks of texts in smaller text sizes, guaranteeing that undersized links in adjacent lines of text fulfill the spacing exception (their 24 CSS pixel diameter circle don't intersect any other links or their circles) would require a large line height which can be undesirable in many design contexts.

I think we need an illustration on how links are not sufficiently spaced in common body text presentations, as well as examples demarcating when a link's "size is otherwise constrained by the line-height of non-target text" and where a link needs to meet the spacing requirement. Technical examples involving various elements would be helpful (and could even form a technique). We should also explain what a sentence is.

patrickhlauke commented 11 months ago

I can probably try to tackle some visuals...

mbgower commented 11 months ago

Thanks, @patrickhlauke . Once you are have something ready to look at, change the WCAG 2.x project status to "Drafted" (just underneath the Labels section, and we will review.

dan-tripp-siteimprove commented 1 month ago

I'd like to give this a +1. And ask: until the Understanding doc gets updated, is there any source of guidance on the inline exception? I opened issue https://github.com/w3c/wcag/issues/3898 and then discovered a certain google doc which seems to be part of the discussion during the formation of the SC that mbgower mentioned above. But then I discovered some apparent contradictions in that google doc, so now once again I don't know whether those cases - which are common, in the wild - pass or fail. If anyone has any links which could clear this up, please let me know.