Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reflow to Single Column - WCAG 1.4.8 item 5 or New item #7

Open
allanj-uaag opened this issue Jun 21, 2016 · 2 comments
Open

Reflow to Single Column - WCAG 1.4.8 item 5 or New item #7

allanj-uaag opened this issue Jun 21, 2016 · 2 comments

Comments

@allanj-uaag
Copy link
Contributor

Wayne's proposal: Content shall enable users to reflow any multi-column presentation to a single column presentation.

This seems part of 1.4.8 item 5.

Current wording:
1.4.8 Visual Presentation: For the visual presentation of blocks of text, a mechanism is available to achieve the following: (Level AAA)

  1. Foreground and background colors can be selected by the user.2. 
    
  2. Width is no more than 80 characters or glyphs (40 if CJK). 
    
  3. Text is not justified (aligned to both the left and the right margins). 
    
  4. Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing. 
    
  5. Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window.
    

From the Understanding 1.4.8 document
emphasis enclosed by @@ - note single column layout is not required.

This provision does not mean that a user would never need to use horizontal scrolling. It only means that they would not need to use horizontal scrolling back and forth to read a line of text. @@for example, if a page consisted of two equal sized columns of text, it would automatically meet this provision. Enlarging the page would mean that the first column was completely on screen and the user could just scroll vertically down the page to read it. To read the second column, they would horizontally scroll to the right, where the right hand column would then fit entirely within the width of the screen, and read that column without further horizontal scrolling.@@

There are 2 approaches to this:
0. change level to AA

  1. leave the wording of 5 as is. Change the wording of the understanding document to mean that single column layout is necessary. Responsive design should cover this. If the author would allow the user to select the "mobile layout" regardless of viewport dimensions. So, even if a user has a 32 inch monitor they could choose the Mobile Layout (which is usually a single column).
  2. ADD a new item to the list
    1.4.8
    6. Content can be displayed as a single column regardless of viewport or device size.
@allanj-uaag
Copy link
Contributor Author

allanj-uaag commented Jun 23, 2016

Proposal: Blocks of text can be displayed as a single column. (Level A)

with the addition of one of the following at Level AA

Proposal: Users can view all content linearized in a single column. Justification follows the same primary alignment as the base language. (Level AA)
or
Proposal: Users can choose to have all content linearized in a single column, with the same primary alignment. (Level AA)

@allanj-uaag
Copy link
Contributor Author

Question: we have a user need
3.4.4 Justification Users can change the justification / alignment (left, right, full/both, centered) of blocks of text.
Is this the justification for the primary alignment? Is the user need robust enough to cover the primary alignment. WCAG will challenge all points that do not have a user need.
seems in on the call on 6/23 there may have been a separate need for a mechanism to right align (or primary) all content just to get everything on the right margin to make it easier to find.
I tested this page with no styles, all linerarized, all on left margin, and all functions still worked!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant