This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
spec:css3-flexbox:accessibility [2015/01/20 16:10] – bojcampbell | spec:css3-flexbox:accessibility [2015/01/20 16:32] – [The Holy Grail web layout] bojcampbell | ||
---|---|---|---|
Line 40: | Line 40: | ||
The holy grail layout is mentioned in example 7 of the Flexbox spec, acting as the go-to example of tab order not following visual order. | The holy grail layout is mentioned in example 7 of the Flexbox spec, acting as the go-to example of tab order not following visual order. | ||
+ | http:// | ||
Line 83: | Line 84: | ||
==== Proposal ==== | ==== 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. | + | If Flexbox is used to rearrange content |
**Original W3C Working Draft** http:// | **Original W3C Working Draft** http:// | ||
Line 91: | Line 92: | ||
**Proposed Change** | **Proposed Change** | ||
- | 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. | + | The order property **is able to affect the** ordering in non-visual media (such as speech). Likewise, order **may affect** the default traversal order of sequential navigation modes (such as cycling through links, see e.g. nav-index [CSS3UI] or tabindex [HTML40]). |
+ | |||
==== Arguments Against the Proposal ==== | ==== Arguments Against the Proposal ==== |