- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Mon, 24 Apr 2017 13:31:07 +0000
- To: Jonathan Avila <jon.avila@ssbbartgroup.com>
- CC: "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
I think we might be heading down an unnecessary rabbit hole here, there is an implicit assumption in WCAG 2.0 that SCs should apply in all default states unless specified otherwise. [1] E.g. being keyboard accessible shouldn’t depend on what screen size you use. If the size of elements discussed in SCs are specified in CSS pixels or percentages of viewport, then that should be applicable across devices. It does mean a tester may have to try things at different screensizes. E.g. If something (like a menu) disappears off-screen, the CSS/JS should adjust it so that you don’t tab through background-items at that size. The test procedure for graphics contrast (currently) requires you to know the size of 3px for testing a graphical object’s size. That graphic might be different (CSS pixel) sizes at different screen dimensions depending on how the layout adapts. The test procedure says something like: Adjust the size of the browser window until the graphic is at its smallest size, then measure the thickness of the graphical object… I think each SC should apply for all ‘default’ presentations, so in an HTML context that means all media-query specified sizes. A non-default presentation would be where a user over-rides something like text-styles, colour or layout. I consider zoom as default because it is the same as a smaller window size, i.e. author-specified. Cheers, -Alastair 1] https://lists.w3.org/Archives/Public/w3c-wai-gl/2017JanMar/0108.html
Received on Monday, 24 April 2017 13:31:43 UTC