- From: Jonathan Avila <jon.avila@ssbbartgroup.com>
- Date: Tue, 24 Jan 2017 16:06:56 +0000
- To: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>, "GLWAI Guidelines WG org" <w3c-wai-gl@w3.org>
- Message-ID: <DM5PR03MB27804047BF4AD3CD9014503D9B750@DM5PR03MB2780.namprd03.prod.outlook.com>
Alistair, Ø I guess you would have to wheedle text-only resizing in to somehow fail sites according to 1.4.4? No. The issue happens with normal browser zoom – I am using chrome on Wndows. Ø (I hadn’t thought this was controversial, as Jared pointed it out a while ago [1]). I’m sorry – but when you live with this on a daily basis it becomes more than an academic discussion. I’m not judging/picking on any of these pages – just providing them as evidence of an issue. Keep in mind I use low resolution like 1024x768 and even 800x600 – so some of the issues I run into may be encountered at a different zoom level for me. Also keep in mind that these example I found in 5 minutes. I could find more/better ones that might trigger at different zoom levels. Online presentations includes collaboration tools have an issues where zooming in actually causes some content to get smaller! http://www.slidesnack.com/templates-examples/online-presentation-examples#1 One example of snap scrolling where the text is cut off but you can’t scroll to it. http://guidobouman.github.io/jquery-panelsnap/ Example where content is off the right edge but there is no horizontal scrollbar. https://css-tricks.com/examples/ScrollingSidebar/ Another example is floating fixed potion content. http://www.w3schools.com/jquerymobile/tryit.asp?filename=tryjqmob_toolbars_fixed Header text overlaps content https://css-tricks.com/persistent-headers/ Jonathan Jonathan Avila Chief Accessibility Officer SSB BART Group jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com> 703.637.8957 (Office) Visit us online: Website<http://www.ssbbartgroup.com/> | Twitter<https://twitter.com/SSBBARTGroup> | Facebook<https://www.facebook.com/ssbbartgroup> | LinkedIn<https://www.linkedin.com/company/355266?trk=tyah> | Blog<http://www.ssbbartgroup.com/blog/> See you at CSUN in March!<http://info.ssbbartgroup.com/CSUN-2017_Sessions.html> The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited. From: Alastair Campbell [mailto:acampbell@nomensa.com] Sent: Tuesday, January 24, 2017 10:35 AM To: public-low-vision-a11y-tf; GLWAI Guidelines WG org Subject: Re: New Wiki page with SC text proposals to combine issues 79, 78, and 74 > On this list we’ve had this discussion many times that every site does not pass SC 1.4.4 – at least without taking drastic measures such as turning off CSS. There are many ways to break 1.4.4 with floating fixed position content, snap to scrolling, use of overflow, etc. I must have missed those (pre-2014 when I joined?), but with browser zoom becoming the default across browsers since about 2009, “text can be resized up to 200%” with browser zoom, so on the face of it *almost* every site passes by default. (I hadn’t thought this was controversial, as Jared pointed it out a while ago [1]). I guess you would have to wheedle text-only resizing in to somehow fail sites according to 1.4.4? Anyway, we agree on the aim, so presumably you’re happy that we’re aiming for zoom+reflow up to 400%? Cheers, -Alastair 1] https://alastairc.ac/2013/08/browser-zoom-great-for-accessibility/#comment-165794
Received on Tuesday, 24 January 2017 16:07:40 UTC