1.4.4 Resize Text

I just realized that we have been worrying about a non-existent problem regarding 1.4.4


We have been worrying that inlarging the text to 200% was not supported on all products, particularly focusing on mobile where it makes some fonts larger but not necessarily all.

This worry was predicated on thinking that it meant inlarging the text in a fashion that would word wrap etc. so there would be no horizontal scrolling. (or vertical for top/down languages) 

In fact,  this provision only requires that the content can be ZOOMED to 200%.    There is in fact no requirement in 1.4.4 for “no horizontal scrolling”.    As desirable as this is - it was not in 1.4.4.   And in fact the techniques for 1.4.4 acutally list magnification or zoom  as being a sufficient technique.

THEREFORE

- there is no need for this note  on non-web Software.

NOTE 2:   For non-web software <applewebdata://48D194E6-B852-42BC-9806-C58E1E24B0DF#nonWebSoftware>, sometimes the platform provides text scaling to 200% for most, but not all text (e.g. headings, which are naturally large, may not be increased in size to 200%, but other text does increase to 200%). In such cases, authors would only need to support text scaling to the extent provided by user settings in the platform, without losing content or functionality, to satisfy this success criterion.

nor for this phrase in the requirement 

either up to 200 percent or, if the platform provides text resizing capabilities but it does not reach 200 percent for all text, up to the text sizing capabilities of the platform.



THERE IS A CONCERN HOWEVER  

for things like KIOSKS where the OS functions are blocked  and for products that do not have an OS with ZOOM capability  (dedicated function products like a themostat )     So we DO need to address those.

But on the other hand - we should not be requiring zoom on things that already have large print (larger than 200% of normal body text)





SO I SUGGEST

FOR NON-WEB DOCUMENTS — we go with just 

10.1.4.4         Resize text

Where ICT is, or includes, a non-web document <applewebdata://888B6B35-7AF1-4389-B09F-CAA28ABD5FC0#NonWebDocument>,
the non-web document shall satisfy the WCAG 2.2 Success Criterion 1.4.4 Resize text <https://www.w3.org/TR/WCAG22/#resize-text>.

NOTE 1:  Content for which there are software players, viewers or editors, or platforms with a 200 percent zoom feature would automatically meet this success criterion when used with such players, unless the content will not work with the zoom.

NOTE 2:  It is best practice to use only fonts that allow for scaling without loss of quality (e.g. pixelized presentation). This applies in particular to embedded fonts.

NOTE 3:  For ICT where the absolute size of the text can be controlled, it is best practice is for the default presentation of text to have an x-height of at least 1.2mm. For a 14 inch screen at 1920 x 1080 screen resolution with no zooming or display scaling, this means the x-height of the default text before zoom needs to be at least as big as Arial at 16 CSS px, and if zoom is not provided, the minimum size of the text in at least one setting would be 2.4mm or 32 CSS px.


FOR NON-WEB SOFTWARE — we go with just 

11.1.4.4         Resize text <>
Where ICT is, or includes,  <>non-web software <applewebdata://125FA220-F17F-4FA0-922D-84A1AA37083D#nonWebSoftware> that provides a user interface <applewebdata://125FA220-F17F-4FA0-922D-84A1AA37083D#userInterface>,
the non-web software <applewebdata://125FA220-F17F-4FA0-922D-84A1AA37083D#nonWebSoftware> shall allow text to be resized up to 200% without loss of content or functionality, except where the absolute size of the text is known or controlled by the software and the minimum font size is already 2.4mm or larger

NOTE 1:   The Intent section in Understanding 1.4.4 Resize Text <https://www.w3.org/WAI/WCAG22/Understanding/resize-text.html> refers to the ability to allow users to enlarge the text on screen at least up to 200% without needing to use assistive technologies <https://w3c.github.io/wcag2ict/#dfn-assistive-technologies>. This means that the non-web software <https://w3c.github.io/wcag2ict/#software> supports the zoom features of the underlying platform software or that the  non-web software <https://w3c.github.io/wcag2ict/#software> provides some means for enlarging the text to 200% without loss of content  <https://w3c.github.io/wcag2ict/#content-on-and-off-the-web>or functionality.

NOTE 2:  The techniques for 1.4.4 Resize Text  list the normal Zoom feature of browsers and platforms to be sufficient to meet SC 1.4.4 and to not require that the Zoom feature wrap the text.  A pinch zoom feature such as is found on mobile phones would meet this description if they allow zoom of at least 200%.

NOTE 3:  Some applications such as kiosks or digital signs already have print that is larger than 200% of typical body text. Where their minimum text size is already known and of large print size, this requirement does not require additional zoom.  

NOTE 4:  Some applications do not allow access to the underlying platform zoom features or run on platforms without an underlying zoom feature.  If their minimum physical font size is not known or is less than 2.4 mm, then the application would need to provide a feature that provides 200% zoom or creates a known minimum font size of 2.4mm.  

NOTE 5:   Good practice is for the default presentation for text to have an x-height that's at least as big as Arial at 16 CSS px so that it is 32 CSS after 200% zoom.





Thoughts ?  

Gregg