- From: Bradley-Montgomery, Rachael <rmontgomery@loc.gov>
- Date: Tue, 10 Jan 2023 18:57:40 +0000
- To: Alastair Campbell <acampbell@nomensa.com>, "'w3c-waI-gl@w3. org'" <w3c-wai-gl@w3.org>
- Message-ID: <E746A6E6-79F5-45C4-B45C-97B0DDFD39B3@loc.gov>
Hello,
I am comfortable with this as long as the understanding document explains the details and addresses potential gaming. Also, I realize that we are nesting bullets but can we explore formatting this exception as a bulleted list for readability?
Inline: The target is:
· in a sentence,
· in a bulleted or numbered list, or
· its size is otherwise constrained by the line-height of non-target text;
Kind regards,
Rachael
From: Alastair Campbell <acampbell@nomensa.com>
Date: Tuesday, January 10, 2023 at 1:50 PM
To: WCAG <w3c-wai-gl@w3.org>
Subject: Re: Target Size (Min) Updates
Resent-From: WCAG <w3c-wai-gl@w3.org>
Resent-Date: Tuesday, January 10, 2023 at 1:49 PM
Hi everyone,
We had a good post-meeting discussion on this which I’ll round up here.
We got to this formulation:
“Inline: The target is in a sentence, or is in a bulleted or numbered list, or its size is otherwise constrained by the line-height of non-target text;”
The factors we discussed for that were:
* Dropping the page-type concepts such as “body” and “main”.
* Focusing on the presentation of the content of lists (which can be emphasised in the understanding doc).
* That is useful for cross-technology application;
* It could be slightly gamed (e.g. add bullets to your navigation), but that seems unlikely.
* If you update the CSS to remove the bullets, you can also bump the list height up a bit to pass. (I.e. default lists are excepted.)
* Updates to the commas and “or”s to make it more readable.
* It should improve the cross-tester reliability.
Kind regards,
-Alastair
Received on Tuesday, 10 January 2023 18:57:56 UTC