- From: David Berman <berman@davidberman.com>
- Date: Mon, 11 Aug 2025 16:47:15 +0000 (UTC)
- To: public-agwg-comments@w3.org
- Message-ID: <CAJkui0b0WEqV55nvGWvjybAwyxkDf9HMdN8nZ0c=z=tvJV-sOg@mail.gmail.com>
Hi committee, Thank you again for all the amazing work! Regarding the following existing wording within Understanding SC 2.5.8: Target Size (Minimum) (Level AA): “Except when... Inline: The target is in a sentence or its size is otherwise constrained by the line-height of non-target text;” If one follows the guidance you provide here, there are situations where people are going to do the opposite of what I’m confident you would have hoped they would do. Let me explain by example... Consider a Table of Contents within a 100-page EPUB or PDF file of a textbook where each entry in the Table of Contents has the entire entry hypertext linked (to take you, for instance, to the first page of a chapter). One would hope that the “Inline” exception would apply; however, the target is not “in a sentence” nor is it “constrained by the line-height of non-target text” (because all of the text surrounding it also has targets). Thus, it would seem that in order to fulfil your instructions and not be able to use the “Inline” exception, that one would have to increase the line spacing between consecutive baselines of the wording in the entire TOC to at least 24 pixels (even more if there are descending letters, such as y or p, which there are bound to be). This would result in a typical TOC in a textbook that spanned perhaps 3 book pages now spanning 6 or more book pages. And if there are dot leaders, the gap is even more extreme. If you agree that this is an undesirable outcome, then the vocabulary of the exception should be broadened to allow for the arrangement of text that I am describing to also fall within the exception. Would you agree, or should we indeed insist that such TOCs have at least 24 pixels between TOC elements? And if you do agree, would you like help with the proposed wording (as I have ideas on how we get there without tradeoffs)? - David Berman CPWA, ADS -- David Berman, RGD, FGDC, CPWA <https://u5854113.ct.sendgrid.net/ls/click?upn=u001.TruWcfStDA3rMeBhnDmEZnEqhWqE2EzM6uwvjvFBRAliVPmjm1f963X3pX0vVQlePN7D8kA424BkhvGZcWWLig-3D-3DeVZo_2C9kj0upxMObWw1Pw1sux7n8ATq630uX2EmJrrxRSHohusMxWwjcGOWnSj9ahSruWa3Szjv8LGCkqQcv0DXbcuvbdqAwYyKgYMPbSkUHBTtyRemLhxBFzHHNRgfklODd6czqHYAXICPH3zlzeBm8-2B7IoYAD8-2BiyY7VXCYCy1JMGY-2FvDXDKziUxbKLALodd5QlY21v-2B4RHLPkmZiJJHitCQ-3D-3D>, ADS <https://u5854113.ct.sendgrid.net/ls/click?upn=u001.TruWcfStDA3rMeBhnDmEZnEqhWqE2EzM6uwvjvFBRAliVPmjm1f963X3pX0vVQlePN7D8kA424BkhvGZcWWLig-3D-3DbXqV_2C9kj0upxMObWw1Pw1sux7n8ATq630uX2EmJrrxRSHohusMxWwjcGOWnSj9ahSruWa3Szjv8LGCkqQcv0DXbchmRHzx0PpzB5Yu1fOisKDf0bkIH6DDvkPXgJkTIOTorQc9HwCQrVkpuVfLl9KwTQYGZmF1o-2FKtZQ6yxd17uX2H5nzrTA4IvQO2G-2B-2FSC6AcqdfVBtC-2BVnAZFrX9KTeoYHA-3D-3D> | LinkedIn he/him David Berman Communications | berman@davidberman.com | @davidberman +1-613-728-6777 | 340 Selby Avenue, Ottawa K2A 3X6 High Level Advisor, United Nations | Invited Expert, W3C | Global chair, International Association of Accessibility Professionals | Carleton University Access Network chair Next accessibility event: 14 November 2024 (buy a ticket now and get the past recording and learning guide immediately) davidberman.com/next Do Good book news: "Don't just do good design ... do good!" I respectfully and gratefully acknowledge that the work I do takes place on unceded Algonquin Anishinaabe territory. This message may contain proprietary information. Unauthorized disclosure/copying/distribution of contents prohibited.
Received on Monday, 11 August 2025 16:47:21 UTC