https://github.com/w3c/wcag/issues/1432
Jake: current wording doesn't
prevent overlapping targets and overlapping targets would make
target size smaller
... this is not the original intent – if the target spacing is
overlapping it's 18, not 24
... because it says the target and the nearest edge of the
closest target. You can end up with targets of 8 x 8 pixels and
you need to add it on top because four plus eight is 12, but
then they are only 16 pixels.
Sukriti: but if we don't allow spacing to be part of this we dincentivize that behavior. I really think we should go with a 24 pixel version of the AAA version
Jake: the issue is that breaks a lot of webpages.
Sukriti: the other counterargument that people were making is 24 is not enough. We could say to keep it online that spacing cannot overlap. It becomes a tough thing to explain within an already complex – center of the target.
Jake: the disadvantage of the 24
pixel will be all these links need to have a lot more padding
four links that aren't part of a sentence or block of
text
... the other option, they don't need padding the only thing
that they need is to have a margin top of eight pixels. You
leave those targets alone, but you need to create way more
margin. In the other case you need to create bigger target
areas. The result is the same but the way to adjust everything
is completely different.
... although we would like the 24 the other one might work
better because it doesn't require as much to be adjusted
... target 18 high you do not have to do anything about it in
the second version, but if there is no other target around you
do not need to change it in the second version
Sukriti: if -looking is not an
issue just hitting a target, that makes sense
... how can we explain this well
Added overlapping to address this issue
<scribe> ACTION: Sukriti will send note to Alastair about the change
<trackbot> Error creating an ACTION: could not connect to Tracker. Please mail <sysreq@w3.org> with details about what happened.
<scribe> ACTION: Sukriti will send note to Alastair about the change
<trackbot> Error creating an ACTION: could not connect to Tracker. Please mail <sysreq@w3.org> with details about what happened.
This is scribe.perl Revision of Date Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Default Present: JakeAbma, Kim, Sukriti Present: JakeAbma Kim Sukriti No ScribeNick specified. Guessing ScribeNick: Kim_patch Inferring Scribes: Kim_patch WARNING: No "Topic:" lines found. Found Date: 29 Oct 2020 People with action items: note send sukriti will WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]