spec/css3-flexbox/accessibility: edited

Author: bojcampbell

spec/css3-flexbox/accessibility.txt

@@ -37,8 +37,8 @@ box 1, box 2, box 3
 
 ===== Solution =====
 
-====1.) When the visual order is changed via Flexbox, the UA Tab order should logically follow the newly arranged box tree====
-
+==== 1.) When the visual order is changed via Flexbox, the UA Tab order should logically follow the newly arranged box tree====
+==== 2.) The Box Tree visual change should be mapped to the Accessibility API so that AT’s have the same experience.====
 
 == DOM order (unchanged) ==
 box 1, box 2, box 3
@@ -52,7 +52,7 @@ box 3, box 2, box 1
 == Diagram ==
 {{:spec:css3-flexbox:flexbox3.jpg|}}
 
-==== 2.) The Box Tree visual change should be mapped to the Accessibility API so that AT’s have the same experience.====
+
 
 
 
@@ -61,6 +61,7 @@ box 3, box 2, box 1
 ======= Proposal Statement =======
 
 
+==== Proposal ==== 
 If Flexbox is used to rearrange content, the box tree and accessibility API should be updated to also change the keyboard and screen reader flow to match the new visual layout.
 
 **Original W3C Working Draft** http://www.w3.org/TR/css-flexbox-1/#order-accessibility
@@ -71,7 +72,8 @@ The order property does not affect ordering in non-visual media (such as speech)
 
 The order property **affects** ordering in non-visual media (such as speech). Likewise, order **affects** the default traversal order of sequential navigation modes (such as cycling through links, see e.g. nav-index [CSS3UI] or tabindex [HTML40]). Authors must use order only for visual, not logical, reordering of content; style sheets that use order to perform logical reordering are non-conforming.
 
-**Arguments Against the Proposal** 
+==== Arguments Against the Proposal ====
+
   - The interaction will not be consistent with content that has been similarly visually rearranged with Float and does not change the logical order
   - Flexbox will lose the intended opportunity to rearrange the visual order without changing the logical tabbing order for keyboard users
   - It will be difficult to implement and track the logical order change to the box tree and the accessibility tree
@@ -80,7 +82,7 @@ The order property **affects** ordering in non-visual media (such as speech). Li
   - Devs should not be using Flexbox to fix problems with the layouts
   - Blind users will end up with a different experience on mobile than desktop
 
-**Rebuttals to Arguments Against**
+==== Rebuttals to Arguments Against ====
   - Float is already recognized as a risk for keyboard users and only advised if the logical order already makes sense without any CSS http://www.w3.org/TR/2005/WD-WCAG20-CSS-TECHS-20050630/#float
   - No evidence or example that this is a desirable outcome
   - This is the direction CSS is moving and the risk is too great to ignore due to effort
@@ -89,7 +91,7 @@ The order property **affects** ordering in non-visual media (such as speech). Li
   - Devs will continue to do this regardless of best practices. It’s easy and has major performance implications
   - Blind users want the same experience that visual users get in each context
 
-**Additional Arguments for the Proposal**
+==== Additional Arguments for the Proposal ====
   - Developers recognize Flexbox as a performance enhancer and are using it in lieu of javascript
   - High Contrast mode users are at risk of jumping around a screen causing confusion as they see only a small portion of the screen
   - Visual Keyboard users have difficulty tabbing to information that visually shows up early but is logically near the end. Example: navigation list that is logically at the end but moved to the middle left using flexbox