WebAIM Feedback - SC 1.4.10 – Linearization

[jared-w-smith]

Reflowing content into a single column provides numerous benefits. This SC should, however, be clarified to refer to not inhibiting reflow based on user customization of your content rather than suggesting that authors must provide “a mechanism” for reflowing content, such as a “Linearize page” control on each web page.

Additionally, this SC should be scoped to primarily apply to text content, and generally longer blocks of text at that. If applied to other types of content, such as horizontally oriented toolbars, tree widgets, etc., this would require significant author effort and would result in non-standard presentations that would most often be less accessible.

Some clarification of the overlaps of Linearization and text sizing may be necessary. Is single-column reflow also required at 400% text sizing without horizontal scrolling?

WebAIM supports the premise of this SC, but does not support adoption of this SC as drafted.

[DavidMacDonald]

@jared-w-smith There is a lot going on with these SCs right now. The resize and linearization were split out, because some users don't need resizing ... they have tunnel vision, and need a narrow field of view. I think some members want linearization to apply to ALL content, while others, such as myself, think that "blocks of text" is more achievable. Horizontal menus etc... will be tough... but perhaps it can be managed with exceptions.

Follow the full discussion here:
#58

[allanj-uaag]

if you can get a mobile view regardless of device size that would solve the problem. Many website have a responsive design (mobile first). If low vision users had an easy way to get a mobile view they would have a linearized experience...menus, content, etc.

…

On Tue, Apr 4, 2017 at 3:08 PM, David MacDonald ***@***.***> wrote: This is a lot going on with these SCs right now. The resize and linearization were split out, because some users don't need resizing ... they have tunnel vision, and need a narrow field of view. I think some members want linearization to apply to ALL content, while other, such as myself, think that "blocks of text" is more achievable. Horizontal menus etc... Follow the full discussion here: #58 <#58> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#249 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AG_WL78JzHRjB-QOXLKjqrT17gfTcj7Qks5rsqNDgaJpZM4MwVsu> .

-- Jim Allan, Accessibility Coordinator Texas School for the Blind and Visually Impaired 1100 W. 45th St., Austin, Texas 78756 voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/ "We shape our tools and thereafter our tools shape us." McLuhan, 1964

[DavidMacDonald]

Yes that would be the primary technique to meet this SC... However, a lot of sites approach Mobile in other ways like sniffing for the device itself rather the viewport. It is for these, for applications, and a hundred other outliers that we have to get into the weeds... I'd love to have an SC that just said "Use Responsive Design" but that would be the end of us.

[mraccess77]

@allanj-uaag FYI I use 800x600 and I often get the mobile view of a site. It's not a given as there are other methods that sites use and some have smaller breakpoints before going responsive - -but changing the resolution or the zoom level or both will often trigger it.

[allanj-uaag]

Jon, In the best of worlds, on demand mobile view (as well as triggering, or sniffing) would be ideal. I have seen mobile sites that have a button "see full site". Why not the reverse?

…

On Wed, Apr 5, 2017 at 7:52 AM, Jonathan Avila ***@***.***> wrote: @allanj-uaag <https://github.com/allanj-uaag> FYI I use 800x600 and I often get the mobile view of a site. It's not a given as there are other methods that sites use and some have smaller breakpoints before going responsive - -but changing the resolution or the zoom level or both will often trigger it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#249 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AG_WL_3yQNgA88k_9xpwdidOT0xatKX0ks5rs46VgaJpZM4MwVsu> .

-- Jim Allan, Accessibility Coordinator Texas School for the Blind and Visually Impaired 1100 W. 45th St., Austin, Texas 78756 voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/ "We shape our tools and thereafter our tools shape us." McLuhan, 1964

[steverep]

Recommend this issue be closed as the Linearization SC did not reach working group consensus and thus will not be in 2.1. Much of the desired content requirements, however, are covered by the Zoom Content SC.