Reflow has nothing to do with resizing the size of the text at all. Reflow was introduced to support users with low vision to easier navigate zoomed-in experiences by giving them a viewport size that – guaranteed – would not scroll horizontally. It totally conforms if your website grows to twice the width and height when resizing the text to 200%, even if that means horizontal scrolling. And, more importantly, this success criterion gives no guidance on scrolling. As long as the text does not get completely lost (for example through overflow: hidden or text running into each other or behind other objects), your layout is allowed to break. That said, this SC is relatively permissive. Of course some ways are better than others and adjusting the viewport to resize text is frequently the most consistent way to do it, especially on websites that have been implemented in a responsive way. Changing the viewport by changing the display resolution.Zooming the page using browser features (viewport resizing).Resizing only the text (classic text resizing).As long as the way to resize the text is “accessibility supported”, it is a valid way to conform to WCAG: Note how the success criterion does not specify a specific method to reach this state of two times the font size. The requirement is that, except for captions and images of text, text can be resized up to 200% without losing content or functionality. This success criterion that was introduced with WCAG 2.0 on level AA covers text resizing without assistive technologies. While these two success criteria seem related, they cover different use cases. There seems to be a confusion about the relationship and how to test for the WCAG 2.1 Success Criteria 1.4.4 Resize Text and 1.4.10 Reflow.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |