- From: Jonathan Avila <jon.avila@levelaccess.com>
- Date: Thu, 27 Jul 2017 14:13:39 +0000
- To: Laura Carlson <laura.lee.carlson@gmail.com>
- CC: Alastair Campbell <acampbell@nomensa.com>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>, Amani Ali <aali@nomensa.com>
Yes for web content we should use viewport and drop resolution. I wonder though for PDF readers how we can measure that. Jon Sent from my iPhone > On Jul 27, 2017, at 10:00 AM, Laura Carlson <laura.lee.carlson@gmail.com> wrote: > > Hi Alastair and Jon, > > Thanks, Alastair. > > Jon, are you okay with us changing “Window size” to “Viewport size”, > and dropping the display resolution column on the spreadsheet? In the > Github issue you had mentioned that we should, "note the screen > resolution used as well when zoom is used." [1] > > Kindest Regards, > Laura > > [1] https://github.com/w3c/wcag21/issues/78#issuecomment-317840594 > >> On 7/27/17, Alastair Campbell <acampbell@nomensa.com> wrote: >> Hi Laura, >> >> I think “Window size” should be “Viewport size”, and we can drop the display >> resolution column. >> >> For you (and Amani) on a Mac they are the same thing, anyone testing on >> windows should resize their window until the width is reported as 1280px in >> the inspector (for the HTML element). >> >> If you are on a display larger than 1280, I suggest using something like the >> webdev toolbar to resize the window, you can put in custom sizes to that. >> >> To note, Amani has tested the Alexa top 50 [1], and is adding some ‘smaller’ >> sites so we don’t have a sample completely skewed to large properties. >> >> So far everything that fails at 400% also fails at 100% (I think, will >> check), and that is mostly for fixed-height containers. >> >> Cheers, >> >> -Alastair >> >> 1] There are a few which block the script with content-headers, but only a >> few. >> >> > > > -- > Laura L. Carlson
Received on Thursday, 27 July 2017 14:14:11 UTC