Important note: This Wiki page is edited by participants of the AGWG. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.
Reflow to Single Column
- Linearization (new Reflow) GitHub Issue
- SC for viewing | SC for editing
- SC in full draft guideline
- Understanding doc for viewing | Understanding doc for editing | Understanding doc in master
- 1 SC Shortname
- 2 SC Text
- 3 Suggested Priority Level
- 4 Related Glossary additions or changes
- 5 What Principle and Guideline the SC falls within.
- 6 Description
- 7 Benefits
- 8 Testability
- 9 Techniques
- 10 Related Information
Reflow to Single Column - Linearize
A mechanism is available to view content as a single column, except for parts of the content where the spatial layout is essential to the function and understanding of the content.
Suggested Priority Level
Related Glossary additions or changes
- Correct Reading Sequence
- any sequence where words and paragraphs are presented in an order that does not change the meaning of the content. (From WCAG 2.0 Glossary)
What Principle and Guideline the SC falls within.
Principle 1, Guideline 1.4 (Distinguishable) is the most appropriate location for this new success criteria. This is because it focuses on presentation of content in a single column of elements with all text in single column format.
Guideline 1.3 (Flexible Date) is essential for reflow. SC 1.3.2 (Meaningful Sequences) establishes the necessary structure for reflow to occur. Without reflow SC 1.4.4 (Resize Text) could not be extended to enable very large text. Finally, without reflow restriction of column size would be difficult. This allows raising the level of SC 1.4.8(2) (Visual Presentation (width)) to Level A.
The final fit for reflow is in Principle 2, Guideline 2.4 (Navigation). Most people with low vision could benefit from a single column view of a page. This is because items get lost in a two dimensional presentation. (See Benefits below)
Relevant Guidelines and Success Criteria
- Guideline 1.3 Flexible Data
- Guideline 1.4 Distinguishable
- Guideline 2.4 Navigable
Content can be viewed in a single column. All text is presented in single column format and the Line Length SC ensures that all lines of text word wrap to fit the available space. Data tables will have a standard tabular display, a two-dimensional matrix. Some user agents do not support active data such as form controls in reflow. In these cases the content author is not responsible for creating content that reflows.
This good reflow of HTML was accomplished by a custom style sheet.
Properly reflowed PDF text.
Improper characters used by the author for spaces. This causes words to jam together with reflow. This authoring problem occurs frequently with PDF.
One important need of most people with low vision is to reconfigure a presentation from a normal two-dimensional page to a one-dimensional organization of data. This is not always the case, but it is a frequent need. For quick scanning the original structure may be useful to scan for recognizable items. This is usually done when the user knows a page and is looking for just one thing. In cases where careful examination of the page is necessary one column presentation is needed. The reasons are given below.
- Continuous Reading: Many people, with and without disabilities, find it more difficult to read when they must scroll from the bottom of a column of text to the top of another column. With low vision the need is greater. To go from one column to next frequently requires paging up several screens to get from the bottom of one column to the top of the next. Additionally, using a small scrollbar and cursor is difficult with limited sight. This makes getting from the bottom of a column and finding the top of the next column more difficult. Reading flow degrades and comprehension suffers.
- Reliable Searching: (visual navigation of the viewport) Searching for a specific item within a page of information is difficult for almost everyone with low vision. This is because the field of vision is limited either by enlargement requirements, or physical visual field loss due to tunnel vision. The ability to only scroll in one dimension vertical only or horizontal only but not two dimensions, dramatically simplifies this problem. A person can start at the top of the page and move element by element down the page until the bottom, and be certain that every item has been scanned. (TSBVI,Specific Eye Conditions, Corresponding Impact on Vision, And Related Educational Considerations)
- Resizing Text on a Large Scale: Two column or more do not support large print text. Even if text stays within column boundaries, multi-column format will not provide enough space for text in large print. Even medium length words will not fit for sizes exceeding 250%. This causes excessive hyphenation and becomes distracting. This criterion is a necessary condition for useful text resize criterion for people with visual acuity worse than 20/70. Many people in this range require print size greater than 1/2 in. (1 cm.). This cannot be sustained with standard formats. content.
User Need: Users can set blocks of text in one continuous block, instead of in multiple columns.
- PDF: With a user agent that enables reflow, use the reflow option to see content reflowed into one column. No lines should be truncated. If this operation is successful the document passes.
Existing Relevant Techniques
- G57: Ordering the content in a meaningful sequence (Note: Correct Reading Sequence and meaningful sequence are the same in this context.)
- F1: Failure of Success Criterion 1.3.2 due to changing the meaning of content by positioning information with CSS
- HTML: Write content so that the source order of perceivable elements defines a correct reading sequence. It is perfectly appropriate to include items that are not displayed to users in any convenient order. Such elements do not disrupt the correct reading sequence of the entire page. Make sure that elements that are not to be perceived are marked in a standard way like "display: none" or "visibility: hidden" so they can be ignored by a reformatting program. Test your document with no style in your user agent(s). See that it makes sense as a page and is fully operable. After this content is arranged and tested, positioning and other block formatting of the page. Use style sheets for positioning so that it can be removed and the resulting view is readable and operable.
- HTML: Use media queries based on em units for reflow to single column. Reason: When the line length shrinks below a certain number of characters, reflow to a single column is triggered whether the reduced character count is caused by shortened lines or increased font size. This makes the reflow to single column accessible on more devices.
- Fxx: Text becomes unreadable because of reflow.
- Fxx: Failure of Success Criteria [Text Colors] and [Reflow to Single Column] due to inserting important information by using the background-image property of CSS.
Note: This is necessary because non-decorative images cannot be reflowed.
- lvtf-ACTION-89: Post reflow to wcag github - on Jim Allan, November 17, 2016
- HTML Source Order vs CSS Display Order - Adrian Roselli
- Re: lvtf-ACTION-89: Post reflow to wcag github - Jim Allan, 28 November 2016
- Reflow is ready, and so is Line length - Wayne Dick, 15 November 2016
- Terminology Question (LVTF thread) Wayne Dick, 1 November 2016
- Latest Reflow - Wayne Dick, 31 October 2016
- Reflow test case (Thread) - Alastair Campbell, 23 October 2016
- Reflow Final Draft Wayne Dick, 4 October 2016
- Reflow LVTF Thread 30 September 2016
- I have made changes to Line Length and Reflow to Single Column - Wayne Dick, 20 August 2016
- Requirements doc - Alastair Campbell, 18 February 2016
- WCAG WG 2.1 GitHub Issue 58 - Opened by Jim Allan, 28 November 2016
- Reflow to Single Column - WCAG 1.4.8 item 5 or New item LVTF GitHub SC Issue #7
- 17 November 2016 LVTF Minutes
- 27 October 2016 LVTF Minutes
- 20 October 2016 LVTF Minutes
- 13 October 2016 LVTF Minutes
- 06 October 2016 LVTF Minutes (Informal Meeting)
- 29 September 2016 LVTF Minutes
- 4 May 2016 LVTF minutes
- Ready for WCAG - 1 December 2016
- [LVTF] New SC proposal - Issue 58:Reflow to Single Column - WCAG WG Survey, 28 November 2016
- Survey items for October 20 LVTF meeting