- From: John Foliot <john@foliot.ca>
- Date: Wed, 25 Aug 2021 15:47:44 -0400
- To: "Patrick H. Lauke" <redux@splintered.co.uk>
- Cc: W3C WAI ig <w3c-wai-ig@w3.org>
- Message-ID: <CAFmg2sVSrj_wLq0R8Q=w8khtT8z_3KPFLvSw=5nrp-w68o6BDQ@mail.gmail.com>
+1 to Patrick, however I also take Wayne's point - this is an issue. HOW to remediate or mitigate this issue is a second question, and whether that can be factored into WCAG 3 world perhaps be a third question. But thank you Wayne for pointing out a problem that I for one had never thought about, but that I totally understand and agree is concerning. JF On Wed, Aug 25, 2021 at 2:25 PM Patrick H. Lauke <redux@splintered.co.uk> wrote: > Just adding here that the 341x256 pixels measure is only relevant for a > browser at 1024x768 on a relatively small 15-17 inch screen at "typical" > viewing distance of about 2 feet. As soon as you factor in larger screens, > closer viewing distances, zoom factors, the measure becomes > irrelevant/inaccurate (or rather, balloons out to larger numbers). > > Also, agree that this is a problem related to the user agent, not > something the author can/should take into account. > > P > -- > Patrick H. Lauke > > www.splintered.co.uk | https://github.com/patrickhlauke > http://flickr.com/photos/redux/ | http://redux.deviantart.com > twitter: @patrick_h_lauke | skype: patrick_h_lauke > > -- *John Foliot* | Senior Industry Specialist, Digital Accessibility | W3C Accessibility Standards Contributor | "I made this so long because I did not have time to make it shorter." - Pascal "links go places, buttons do things"
Received on Wednesday, 25 August 2021 19:48:16 UTC