Re: Focus appearance update

Hi everyone,

Based on a little off-list conversation, the nub of it seemed to be the ambiguity of “can” in:
“For components which wrap onto multiple lines as part of a sentence or block of text (such has hypertext links), the bounding box *can* be established based on how the component would appear on a single line.”

To keep testing consistent, it seems appropriate to make that:
“For components which wrap onto multiple lines as part of a sentence or block of text (such has hypertext links), the bounding box *is* based on how the component would appear on a single line.”

That should appear in the editors draft soon.

-Alastair


From: Wilco Fiers
Hey Alastair,
It isn't clear in this version when to use the real bounding box, and when to use this imagined one-line variation of the bounding box. My guess based on the discussion is that this should be "whichever of the two bounding boxes has the shortest side", but that's not at all obvious from the text. You can take that to mean different things. Like whichever results in the largest minimum focus indicator, or whichever bounding box has the smallest / largest area / perimeter. Different versions of that change the calculation on different edge cases.



On Fri, Jul 1, 2022 at 6:49 PM Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>> wrote:
Hi everyone,

In the last update before CFC we’re integrating the text from the last meeting to deal with wrapped links.

After the meeting Michael Gower noticed that we already have (clashing) text in the definition of “minimum bounding box”, and it would make more sense to include it there.

So the branch has been updated to include that:
https://github.com/w3c/wcag/pull/2420/files#diff-951af9e4a0995712c1febbcefe2a63d456ea746283c6983ef89075c7ade89113

If anyone has any concerns about this change, please let me know.

Kind regards,

-Alastair

--

@alastc / www.nomensa.com<http://www.nomensa.com>




--
Wilco Fiers
Axe-core & Axe-linter product owner - WCAG 3 Project Manager - Facilitator ACT Task Force
[cid:BCBD7D4B-677E-4B95-AE3F-60005DBD9EE4]