RE: New Wiki page with SC text proposals to combine issues 79, 78, and 74

Ø  Every browser, and tools for them, allow users to change any of those aspects. In the same way that every site now passes 1.4.4 Resize text because zoom is in every browser, it puts no requirement on authors. It is ignorable.



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.

But I agree with what you are trying to say “And in the same way that 1.4.4 does not meet the user-requirements for reading, it doesn’t help the users.”

Jonathan

From: Alastair Campbell [mailto:acampbell@nomensa.com]
Sent: Tuesday, January 24, 2017 3:58 AM
To: Gregg C Vanderheiden; 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


The problem is that this:

“nothing is done in the content to prevent the user agents from making the changes.”



Is always true regardless of what the author does.

​

Every browser, and tools for them, allow users to change any of those aspects. In the same way that every site now passes 1.4.4 Resize text because zoom is in every browser, it puts no requirement on authors. It is ignorable.



And in the same way that 1.4.4 does not meet the user-requirements for reading, it doesn’t help the users.



It needs to go one step beyond that, it needs to say that when users apply these changes (as specified in the understanding perhaps?), the site does/doesn’t do things specified in the techniques / failures that prevent people from reading or using the page.



-Alastair