Re: Target size updates

Great  progress 

Conditional +1 

IF
1) We include the note in the SC  
> “constrained by” does not mean a link has to be the maximum size of the line-height, it means that the line-height has to be less than 24px. 
> I.e. an 8px high link (such as a superscript text-link) is excepted if the line height is under 24px. it doesn’t have to be the height of the line-height.

2) We define  Block of text   (suggestion provided below)

Otherwise — very clever.  Lots of good work - esp on target offset.  Amazingly robust I think.

Gregg




> On Dec 19, 2022, at 12:45 PM, Alastair Campbell <acampbell@nomensa.com> wrote:
> 
> Hi everyone,
>  
> Please +1 if this seems fine, or comment / question if it does not. 
> (This is prior to a Call for Consensus”.)
>  
> At the WCAG 2.x meeting on Friday we discussed two updates to Target Size (Min).
>  
> Inline exception
>  
> We updated the working document:
> https://docs.google.com/document/d/1khsB3Qo8P8VkvTOw2_akHJx_PiXF8HuZ6uKc7uyI1qQ/edit#
>  
> Notes:
> We went with “line-height” as simpler language, and added a note to explain that can mean width if it is a vertical language.
> 
> “constrained by” does not mean a link has to be the maximum size of the line-height, it means that the line-height has to be less than 24px. 
> I.e. an 8px high link (such as a superscript text-link) is excepted if the line height is under 24px. it doesn’t have to be the height of the line-height.
GV: Is there also a note to this effect?   This is good but not clear from SC without a note
> 
> It starts with “The target is in a sentence” as that captures many cases in a simple to understand way.

GV: the full text in   #2798 says    "The target is in a sentence or block of text;"    ( This is good)  Do we define "block of text"?

GV SUGGEST:   Maybe "A string of words with a string of words above and/or below it. Examples are a paragraph of text, menus, and bulleted lists of text. "
> 
> If this is approved, we can do an errata for 2.5.5 separately https://github.com/w3c/wcag/issues/2857
>  
> That change (for 2.5.8) is in PR 2856:
> https://github.com/w3c/wcag/pull/2856/files
>  
>  


> Target offset
>  
> We went with idea 7 from this working document:
> https://docs.google.com/document/d/1qhh9VgBC_6HD2emkvql2Hn83iSChwlhGBs5_E9gkdEM/edit#heading=h.j7ts5ij6ruh4
>  
> Notes:
> The SC text is updated to say “the target is non-overlapping and has a target offset of at least 24 CSS pixels to every adjacent target.”. Removing overlapping targets from the scope removes a lot of the odd/niche cases.

> The notes have been moved into the main definition text so they are normative.
> 
> It continues with the goal of keeping it simpler by considering the horizontal and vertical axes as the primary methods of calculation.
>  
> This is in PR: https://github.com/w3c/wcag/pull/2798/files
>  
> These represent solutions to issues raised during CR, and we would like to get approval on these very soon.
>  
> If you have any concerns, please raise them here. If none of forthcoming we’ll CFC them soon.
>  
> Kind regards,
>  
> -Alastair
>  
> -- 
>  
> @alastc / www.nomensa.com <http://www.nomensa.com/>