Merge pull request #500 from w3c/maryjom-patch-5

Issue 394: Update 1.4.10 Reflow in SC Problematic for Closed

success-criteria-problematic-for-closed-functionality.md

@@ -27,7 +27,7 @@ For non-web software on products with closed functionality, those who implement
 </ul></li>
 <li><a href="#resize-text">1.4.4 Resize Text</a> — Non-web software on closed functionality products may offer more limited text rendering support than the support found in user agents for the Web. As a result, meeting Success Criterion 1.4.4 in a closed environment may place a much heavier burden on the content author.</li>
 <li><a href="#images-of-text">1.4.5 Images of Text</a> — To enable assistive technology to modify displayed text (e.g., adjusting contrast, increasing font size), machine-readable text is needed, as opposed to mere images of text. Not all ICT with closed functionality has the capability to support visual modification of displayed text or images of text, given there is no interoperability with assistive technology and/or lack of platform support.</li>
-<li><a href="#reflow">1.4.10 Reflow</a> — Some software on ICT with closed functionality does not support scrolling content, or zooming, or changing the viewport (examples include, but are not limited to, software for self-service transaction machines or kiosks).  Therefore, some other non-WCAG requirements would be needed for products with closed functionality to ensure that content is readable by persons with low vision without scrolling in two dimensions.
+<li><a href="#reflow">1.4.10 Reflow</a> — Some software on ICT with closed functionality does not support scrolling content, or zooming, or changing the size of a viewport or scrollable content area to the specified width/height (examples include, but are not limited to, software for self-service transaction machines or kiosks).  Therefore, some other non-WCAG requirements would be needed for products with closed functionality to ensure that content is readable by persons with low vision without scrolling in two dimensions.
 
 <div class="note">Some ICT with closed functionality does not display large chunks of text and only has UI controls.  In such cases, two-dimensional scrolling to access the text and UI controls may be considered essential, thus meeting an exception, and the success criterion would be satisfied.</div></li>
 <li><a href="#non-text-contrast">1.4.11 Non-text Contrast</a> — There are cases where applying this success criterion to non-web software on products with closed functionality is problematic: