- From: Detlev Fischer <detlev.fischer@testkreis.de>
- Date: Tue, 3 Nov 2020 09:52:57 +0100
- To: public-mobile-a11y-tf@w3.org
Hi Alastair, all, The appended "Unless the target:::2 clause is perhaps not the most elegant solution, but if put before the exception bullets, it would probably overload the text. Is there any reason not to turn the nested case into an extra exception though? (And what about the overlapping targets that Patrick mentioned? Would we need some extra explanation that in case of overlapping targets those witrh a higher x-axis value take precedence and overlapped content below targes higher up is to be discounted in targt size calculations?) Detlev Am 02.11.2020 um 23:32 schrieb Alastair Campbell: > Patrick wrote: >> Is that not what was intended? I'm lost now... > I think you were referring to Jake's original text. > > Sunday evening (our time) I suggested: > “For each target, the distance to the furthest side of each adjacent target is at least 24 CSS pixels, except when:” > > Detlev wrote: >> "I wouldn't assume that 'any adjacent target' includes nested targets... So I guess some extra language would be needed for the edge case of nested targets?" > Good point, so working the extension in would be something like: > > For each target, the distance to the furthest side of each adjacent target is at least 24 CSS pixels, except when: > - Inline: The target is in a sentence or block of text; > - User Agent Control: The size or spacing of targets is determined by the user agent and is not modified by the author; > - Essential: A particular presentation of the target is essential to the information being conveyed. > Unless the target is enclosed within another target, where it has a minimum height and width of 24 CSS pixels. > > Cheers, > > -Alastair -- Detlev Fischer DIAS GmbH (Testkreis is now part of DIAS GmbH) Mobil +49 (0)157 57 57 57 45 http://www.dias.de Beratung, Tests und Schulungen für barrierefreie Websites
Received on Tuesday, 3 November 2020 08:53:10 UTC