diff --git a/understanding/20/resize-text.html b/understanding/20/resize-text.html index 899450df9f..2fc1cadaf2 100644 --- a/understanding/20/resize-text.html +++ b/understanding/20/resize-text.html @@ -20,30 +20,35 @@

In brief

Intent of Resize Text

- - +

The intent of this Success Criterion is to ensure that visually rendered text, including - text-based controls (text characters that have been displayed so that they can be - seen [vs. text characters that are still in data form such as ASCII]) can be scaled - successfully so that it can be read directly by people with mild visual disabilities, - without requiring the use of assistive technology such as a screen magnifier. Users - may benefit from scaling all content on the Web page, but text is most critical. + controls and labels using text, can be made larger so that it can be read more easily by + people with milder visual impairments, without requiring the use of assistive technology + (such as a screen magnifier). Users may benefit from scaling all content on the Web page, + but text is most critical.

The scaling of content is primarily a user agent responsibility. User agents that satisfy - UAAG 1.0 Checkpoint 4.1 allow users to configure text scale. The author's responsibility is to create Web - content that does not prevent the user agent from scaling the content effectively. + UAAG 1.0 Checkpoint 4.1 + allow users to configure text scale through a number of mechanisms - including zoom (of the entire page's content), + magnification, text-only resizing, and allowing the user to configure a size for rendered text. + The author's responsibility is to create Web content that does not prevent the user agent from scaling the content effectively. Authors may satisfy this Success Criterion by verifying that content does not interfere with user agent support for resizing text, including text-based controls, or by providing direct support for resizing text or changing the layout. An example of direct support might be via server-side script that can be used to assign different style sheets.

+ +

Content satisfies the Success Criterion if it can be scaled up to 200% using at least one text scaling + mechanism supported by user agents.

+ -

If the author is using a technology whose user agents do not provide zoom support, - the author is responsible for providing this type of functionality directly or for - providing content that works with the type of functionality available in the user agent. - If the user agent doesn't provide zoom functionality but does let the user change the +

If the author is using a technology whose user agents do not provide support for specific text scaling mechanisms, + the author is responsible for providing this type of functionality directly, or providing + content that works with the type of functionality provided by the user agent. For instance, if the + user agent doesn't provide full-page zoom functionality, but does let the the user change the + text size, the author is responsible for ensuring that the content remains usable when the text is resized.

@@ -62,7 +67,7 @@

Intent of Resize Text

can be accessed, is provided to the user in some way besides the fact that it is truncated.

-

Content satisfies the Success Criterion if it can be scaled up to 200%, that is, up +

Content satisfies the Success Criterion if it can be scaled up to 200% - that is, up to twice the width and height. Authors may support scaling beyond that limit, however, as scaling becomes more extreme, adaptive layouts may introduce usability problems. For example, words may be too wide to fit into the horizontal space available to them, @@ -77,7 +82,7 @@

Intent of Resize Text

a minimum magnification of 200%. Above 200%, zoom (which resizes text, images, and layout regions and creates a larger canvas that may require both horizontal and vertical scrolling) may be more effective than text resizing. Assistive technology dedicated - to zoom support would usually be used in such a situation and may provide better accessibility + to zoom support would usually be used in such a situation, and may provide better accessibility than attempts by the author to support the user directly.

@@ -87,7 +92,6 @@

Intent of Resize Text

we suggest using text wherever possible. It is also harder to change foreground and background contrast and color combinations for images of text, which are necessary for some users. -

@@ -101,254 +105,149 @@

Intent of Resize Text

1.4.3: Visual Presentation.

-

Benefits of Resize Text

- -

Examples of Resize Text

- - + -

Resources for Resize Text

- - + -

Techniques for Resize Text

- - +
-

Sufficient Techniques for Resize Text

- - - -

Additional Techniques (Advisory) for Resize Text

- - -

Failures for Resize Text

- - -
diff --git a/understanding/20/visual-presentation.html b/understanding/20/visual-presentation.html index 73bd6dcc73..e3c7cc7f4c 100644 --- a/understanding/20/visual-presentation.html +++ b/understanding/20/visual-presentation.html @@ -17,12 +17,10 @@

In brief

- - +

Intent of Visual Presentation

-

The intent of this Success Criterion is to ensure that visually rendered text is presented in such a manner that it can be perceived without its layout interfering with its readability. People with some cognitive, language and learning disabilities @@ -69,13 +67,12 @@

Intent of Visual Presentation

together, so that it is difficult for them to locate word boundaries.

-

The resizing provision ensures that visually rendered text (text characters that have - been displayed so that they can be seen [vs. text characters that are still in data - form such as ASCII]) can be scaled successfully without requiring that the user - scroll left and right to see all of the content. When the content has been authored - so that this is possible, the content is said to reflow. This permits people with - low vision and people with cognitive disabilities to increase the size of the text - without becoming disoriented. +

The resizing provision ensures that visually rendered text, including + controls and labels using text, can be made larger without requiring the user to then + scroll left and right to see all of the content. When the content has been authored + so that this is possible, the content is said to reflow. This permits people with + low vision and people with cognitive disabilities to increase the size of the text + without becoming disoriented.

The scaling of content is primarily a user agent responsibility. User agents that @@ -111,12 +108,11 @@

Intent of Visual Presentation

-
+

Benefits of Visual Presentation

- - +

This Success Criterion helps low vision users by letting them see text without distracting presentational features. It lets them configure text in ways that will be easier for them to see by letting them control the color and size of blocks of text. @@ -127,22 +123,17 @@

Benefits of Visual Presentation

-
@@ -156,318 +147,219 @@

Examples of Visual Presentation

Examples of glyphs include "A", "→" (an arrow symbol), and "さ" (a Japanese character).

-

Resources for Visual Presentation

- - -

Techniques for Visual Presentation

- -

Sufficient Techniques for Visual Presentation

- -

- Instructions: Since this is a multi-part success criterion, you must satisfy one of the numbered items for each of the requirements below.

- - -
-
- - -
-
- - -
-
- - -
-
- - -
-

Additional Techniques (Advisory) for Visual Presentation

- -

Failures for Visual Presentation

- - -