Text reflowing on screen zoom3/11/2024 The past is not important, but in the future I hope the WG remembers this Would WCAG have passed without support for refreshableīraille? The deep problem was that reflow is as important as refreshableīraille, and the WG missed that critical fact. It was exactly like removing refreshable braille from the non-visual Supports time base reading with a screen reader. The WG did not understand the importance of reflow to the user group.Įnlarged text with reflow is to people with visual acuity loss as Wrapped with HTML 4, CSS 2 and ECMAScript. Professional programmer could design pages that enlarged to 200% and word Media queries made reflow easy when they became available, but a However, reflow becameĬommon with the Apple 2E. That was how you had to read research journals. Used closed circuit TV to read print on paper, it was the only way to read. Recognize the magnitude of an error so that we don't make it again.Įnlargement without reflow was never accessible. I don't want to relitigate the past, but sometimes it is important to On Fri, Apr 27, 2018, 1:46 PM WayneEDick wrote: Whenever we think of an exception to allowing reflow just remember we are removing a feature that is as important as refreshable braille. The past is not important, but in the future I hope the WG remembers this truth. Would WCAG have passed without support for refreshable braille? The deep problem was that reflow is as important as refreshable braille, and the WG missed that critical fact. It was exactly like removing refreshable braille from the non-visual reading toolkit. It is a static reading medium that supports time base reading with a screen reader. Enlarged text with reflow is to people with visual acuity loss as refreshable braille is to blindness. The WG did not understand the importance of reflow to the user group. It wasn't trivial, but it wasn't that hard. Media queries made reflow easy when they became available, but a professional programmer could design pages that enlarged to 200% and word wrapped with HTML 4, CSS 2 and ECMAScript. However, reflow became common with the Apple 2E. For those like me who used closed circuit TV to read print on paper, it was the only way to read. I don't want to relitigate the past, but sometimes it is important to recognize the magnitude of an error so that we don't make it again.Įnlargement without reflow was never accessible. When will we see an update to some of these failures bringing more clarity around this SC? 2.1? Authoring experiences that work with text-only resize is much more difficult and relies on fluid non-fixed sizing.īoth Firefox and Safari allow for text-only as an option for native browser zoom now which makes things interesting. With the responsive web, it is pretty easy to create an experience that would pass this SC with it only being browser zoom with modern browsers that support media queries and that have great browser zoom. Some folks believe a browser zoom (where everything just scales up ctrl +/-) is a sufficient technique, while others interpret the SC so that enlarging the text only to 200% must not cause the text, image or controls to be clipped, truncated or obscured. There is disagreement around how this SC is interpreted. Until then, if the content passes the success criterion using any of the listed sufficient techniques, then it does not meet this failure. We are planning to revise this failure in a future update. Note: The Working Group has discovered many misunderstandings about how to test this failure. Is it text-only resize or browser zoom? Nobody knows. Throughout WCAG 1.4.4 Techniques there is reference to an upcoming clarification around a common misunderstanding of this SC.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |