Re: Target size updates

Hi everyone,

I’d like to summarise these for the new year:


  1.  Inline exception

That change (for 2.5.8) is in PR 2856:
https://github.com/w3c/wcag/pull/2856/files

That seems to have good support. There were a couple of questions on the github thread, but seem resolved.

If this is approved, we can do an errata for 2.5.5 separately: https://github.com/w3c/wcag/issues/2857



  1.  Target offset

This is the PR: https://github.com/w3c/wcag/pull/2798/files

Starting with the exception text:
“Spacing: The target is non-overlapping and has a <a>target offset</a> is at least 24 CSS pixels to every adjacent target;”
And updating the target-offset definition to work out offset primarily horizontally & vertically.

Michael floated an update to the text, but as a couple of people didn’t think it was as clear, I’ll stick to the PR as it is.

Gregg noted that you can get some odd results with non-rectangular shapes that slightly overlap the offset. E.g:
[A circle to the left of a square, almost but not quite above the square. A green arrow across the top of the square stops where it meets the circle. A line across the circle that meets the square is much shorter.]

However, any formulation which starts with diagonals will not solve the issue raised:
https://github.com/w3c/wcag/issues/2695#issue-1391222860

Any control that are mostly vertically aligned, but some instances stick out a bit, you get odd pass/fails.

On balance, I think it would be better to make the common cases simple, which the current PR does.

Kind regards,

-Alastair

--

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