Interpreting SC 1.4.4 and "How to meet SC 1.4.4" Well, there are also arguments in favour of such widgetsbut text resizing via the browser controls should work, regardless of whether such a widget is offered or not. has listed reasons to 'say no to text resize widgets'. We leave aside another option for meeting SC 1.4.4, sufficient technique G178 which covers controls for text resizing. So as the use of IE6, older versions of Firefox and other browsers not supporting page zoom may have fallen below 5%, one could be tempted to argue that the rationale for supporting text-only resizing is evaporating. The share of people still using IE6 differs strongly by country while Internet Explorer 6 Countdown estimates a world-wide share of 10.7% (June 2011) the share in Germany is much lower with 1.8% (UK 2.6%, US 2.0%). Understanding Success Criterion 1.4.4 explicitly refers to user agents that do not support page zoom, such as IE6 and Firefox before version 3. One check has to be the level of support for page zoom by user agents. While WCAG 2.0 state that text resizing is mainly a responsibility of the user agent, the page has to be built in a way that it does not prevent graceful text-only resizing (compare, for example, Check your design with text size increased to 200 percent by Roger Johannsson of 456 Berea St). Regarding the WCAG Working Group position, the article is still up-to-date today: the response from the WCAG Working Group regarding the text resize issue has not changed since the 2012 update was published, and failure F69 has not yet been updated. And there are mobile apps like Pocket that will provide a customisable reading experience for web pages saved during browsing. To some extent this negates the need for text-only zoom (on mobile). Many modern mobile browsers (Safari on iOS, IE11 on Windows 8.1, Blackberry Browser) now also include a reader mode that will present the page content in a simplified one-column view that can often be customised to suite users' reading preferences. Most mobile browsers have in common that a pinch gesture can be used to zoom in and out of a page. Some mobile browsers (Safari on iOS, Firefox on Android) do not offer text-only magnification that will lead to a text reflow, while others (Google Chrome) do. The mobile browsing experience is different. On non-responsive sites, supporting text-only magnification will still be beneficial for many users. On the same responsive site (look at for an example), text-only resizing may not have the desired effect or even lead to a behaviour that users would expect from page zoom - when layout elements are all defined in em, the entire content will grow as users trigger text-only zoom. On narrower screens, the multi-column layout shown on the desktop browser will become a single column layout - read Alastair Campbell's post Browser zoom great for accessibility. In the meantime, the growth of web usage on mobile devices and the spread of the responsive web design paradigm have changed the approach to text resizing somewhat.Ī well-designed responsive site will react to page zoom both by increasigng the text size and offering a simpler layout. At the time, the point of contention was whether the success criterion 1.4.4 could or should be interpreted as requiring web authors to support text-only resizing of web content (beyond supporting page zoom). The article was originally published in 2011 and last updated in January 2012. The original article discussed the requirements for web content text resizing in WCAG 2.0, as expressed in the success criterion 1.4.4 Resize text. Now WCAG WG has announced an overhaul of F69. So far, failure F69 has given us reason also to require text-only resizing to work. What do you need to do to ensure that users can resize the text on your web page? A quick look at WCAG's "How to meet 1.4.4 (Resize Text)" suggests that relying on browsers' page zoom is sufficient. Text resizing: Why page zoom is not good enough - or is it? (update September 2014)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |