Updated Reflow understanding doc

understanding/21/reflow.html

@@ -16,8 +16,8 @@ <h2>In brief</h2>
 				<dt>What to do</dt><dd>Allow long lines and other related content to reflow within .</dd>
         <dt>Why it's important</dt><dd>People who need bigger text find it difficult if they need to scroll to two directions to read long lines which do not reflow.</dd>
 			</dl>
-
 		</section>
+
     <section id="intent">
         <h2>Intent of this Success Criterion</h2>
         <p>The intent of the Reflow success criterion is to allow users who need to enlarge (zoom in) content, to read multiline text content without having to scroll in multiple directions. Lines of text that extend beyond the sizing requirements defined by this success criterion will result in the need for such scrolling, the act of which can significantly increases both the physical and cognitive effort required to read. Decreasing the necessary effort can help mitigate the likelihood of a user losing their place when they reach the end of a non-reflowing line, and then need to scroll back to the start of the next line to continue reading.</p>
@@ -34,7 +34,8 @@ <h2>Intent of this Success Criterion</h2>
           <p>An important factor in being able to support Reflow is for the user agent to allow users to adjust the size of content within the window that the content is presented within. For instance, the browser's viewport.</p>
           <p>Technologies such as HTML/CSS, PDF and ePub have methods of reflowing content to adjust to the size of the viewport. When appropriately authored, users can use zooming features, provided by the user agent (browser), to enlarge the content within the viewport. Unless otherwise prevented by author styling, the content of the web page will reflow (wrap) to adjust to the size of the viewport - while the actual user agent, and any UI provided directly by the user agent, remain scaled to the zoom level set by the operating system.</p>
         </div>
-
+     </section>
+
       <section>
         <h3>Horizontally and vertically scrolling content</h3>
         <p>A common way for many article-driven web pages to meet the Reflow success criterion is to ensure that the presentation of a web page can adjust to a single column of content, fitting into a 320 CSS pixel wide viewport and only requiring a user scroll vertically to read the content of the web page.
@@ -170,7 +171,7 @@ <h3>Overlap with other success criteria</h3>
         <p>When reviewing a web page for Reflow, issues related to other WCAG success criteria might be discovered. The following are some examples of potential overlaps wish such criteria.</p>
 
         <h4>Resize Text</h4>
-        <p>The focus of the Reflow success criterion is to ensure that users are not prevented from zooming into web pages, and when doing so text within sections of content will wrap so that the text can be read without having to scroll in two directions. <a href="https://gist.github.com/scottaohara/resize-text"></a>Success criterion 1.4.4 Resize Text</a> overlaps with this goal, as it should be possible to increase the size of all text to at least 200% while simultaneously meeting the reflow requirement. For many web pages, the text of the page is expected to continue to enlarge as the browser magnification increases, so that users can magnify text up to (and beyond) 400%. In an implementation where text does not consistently increase its size as people zoom in (such as when it is transformed based on a media query to adapt to small-screen usage), it must still be possible to get to 200% enlargement to satisfy the Resize Text criterion. It is important to note that the intent of Reflow will commonly result in the enlargement of text, there Reflow does not specifically require any text size enlargement be reached. There may even be instances where one needs to prevent some text from becoming too large, and thus requiring unwanted bi-directional scrolling.
+        <p>The focus of the Reflow success criterion is to ensure that users are not prevented from zooming into web pages, and when doing so text within sections of content will wrap so that the text can be read without having to scroll in two directions. <a href="https://gist.github.com/scottaohara/resize-text">Success criterion 1.4.4 Resize Text</a> overlaps with this goal, as it should be possible to increase the size of all text to at least 200% while simultaneously meeting the reflow requirement. For many web pages, the text of the page is expected to continue to enlarge as the browser magnification increases, so that users can magnify text up to (and beyond) 400%. In an implementation where text does not consistently increase its size as people zoom in (such as when it is transformed based on a media query to adapt to small-screen usage), it must still be possible to get to 200% enlargement to satisfy the Resize Text criterion. It is important to note that the intent of Reflow will commonly result in the enlargement of text, there Reflow does not specifically require any text size enlargement be reached. There may even be instances where one needs to prevent some text from becoming too large, and thus requiring unwanted bi-directional scrolling.
         </p>
         <p>
           For example, if at the default browser setting of 100% zoom, text is set at 20px when the window is 1280 CSS pixels wide, at 200% zoom it will visually appear at twice the size. After zooming by 400% the page reflows to fit within the 320 CSS pixel viewport, the author may decide to set the page's text size to 10px. The text is now half the original size in CSS pixels, but as it has been enlarged to 400%, so it is still displayed at twice the size compared to the default browser setting of 100% zoom. It is not required to achieve 200% text enlargement while remaining inside a specific breakpoint (as zooming may result in the variation for a new breakpoint becoming active), but it should still be possible to get 200% text enlargement in some way compared to the default 100% zoom.