Re: Target size update

I like it!

On Tue, Mar 30, 2021, 6:07 PM Alastair Campbell <acampbell@nomensa.com>
wrote:

> Hi everyone,
>
>
>
> We ran out of time on the call, but I wanted to explain the option I
> suggested.
>
>
>
> We had quite a few suggestions documented:
>
>
> https://docs.google.com/document/d/15dOWrY08WXWvzdmRNFoFYF1odpTu3WYbexNm06FOhuI/edit
>
>
>
> The one that popped out to me was to separate the measure into a
> definition. We got so contorted trying to explain it in the SC text, it
> needs a bit of space.
>
>
>
> Overall, I think that would look like this:
>
>
>
> Targets have an area of at least 24 by 24 CSS pixels, except if:
>
>
>
>    - *Spacing*: The *target offset* is at least 24 CSS pixels to every
>    adjacent target;
>    - *Inline*: The target is in a sentence or block of text;
>    - *Essential*: A particular presentation of the target is essential to
>    the information being conveyed.
>
>
>
> *Target offset*: the distance measured from the farthest point of a
> target, to the nearest point of the second target. Offset includes the
> target and spacing around the target. The offset from A to B may be
> different then the offset from B to A, if the size of these targets differ.
>
>
>
> Just remembering that the first sentence of the definition should be able
> to replace where that definition is used. E.g. The ‘the distance measured
> from the farthest point of a target, to the nearest point of the second
> target‘ is at least 24 CSS pixels to every adjacent target;
>
>
>
> I’m hoping that captured all the comments?
>
>
>
> If people aren’t comfortable with putting that in a definition then I
> think it could be reconfigured back into the SC, and the rest of the
> definition could become a note.
>
>
>
> Kind regards,
>
>
>
> -Alastair
>
>
>
> --
>
>
>
> @alastc / www.nomensa.com
>
>
>