Action 312 email thread

1.8.x Scale Viewport contents

The user can scale (change the size of content) and images within a viewport.

Note: this applies to all content within the viewport, including nested viewports. It is not the intent that nested viewports can have their contents scaled independently of the top-level viewport.

Summary

Details

Action-517 Action-513

These were related so I combined them creating a new SC.

Configure Toolbars: When graphical user agent user interface have toolbars or similar containers the user can add, remove, and reorder items within each toolbar. Also, the user can install, uninstall, show, hide, and reorder toolbars.

link to Chaals comments
http://lists.w3.org/Archives/Public/w3c-wai-ua/2011OctDec/0097.html
http://lists.w3.org/Archives/Public/w3c-wai-ua/2011OctDec/0068.html

Summary

Details

1.4.2 Preserving Size Distinctions

The user can specify whether or not distinctions in the size of rendered text are preserved when that text is rescaled (e.g. whether headers continue to be larger than body text). (Level A)

Intent

The relative size of text provides visual cues that help in understanding and navigating web content, such as when headings are in larger font than body text. This is particularly important because some content may be authored in a way that would make it difficult or impossible to understand if font distinctions were hidden. In these cases, users who set preferences to enlarge or reduce the text size need to have these visual cues preserved. On the other extreme, some users need to have all text rendered in a very specific font size in order for it to be legible. In these cases, the user needs to be able to override author-specified sizes as well as user agent defaults, reducing all text to a single size, even if this may make the structure of some content more difficult to understand, this is preferable than not being able to read it at all.

Examples

Lee has moderately low vision and finds text easiest to read at 16 pt Palatino. She chooses to have her browser display all in the Palatino font and at least 16 pt in size. Headlines remain proportionately larger than the body text (e.g. 24 pt and higher) in order to preserve headline prominence, allowing her to both distinguish headings and locate them easily on the screen.

OR

* Lee has moderately low vision and finds text easiest to read at 16 pt Palatino. When viewing a page she presses the Ctrl+Plus keyboard shortcut to enlarge the content until body text is 16 pt tall. Headlines remain proportionately larger than the body text (e.g. 24 pt and higher) in order to preserve headline prominence, allowing her to both distinguish headings and locate them easily on the screen.

* Alessio has very low vision and needs to use a screen magnifier at extreme settings, where a single character takes up the entire screen height. If the text size on the screen varied, some letters would be considerably taller than the screen, making them indistinguishable. Therefore he adjusts his browser settings so that all rendered text is exactly the same height as the menus and other user interface elements, and tunes his magnifier settings to for that font size.

Summary

Details