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

Expand/clarify understanding for 1.4.4 Resize Text, harmonise 1.4.8 Visual Presentation #2270

Merged
merged 13 commits into from
Aug 7, 2024
Merged
Show file tree
Hide file tree
Changes from 6 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 19 additions & 16 deletions understanding/20/resize-text.html
Original file line number Diff line number Diff line change
Expand Up @@ -14,32 +14,35 @@ <h2>Intent of Resize text</h2>


<p>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.
</p>

<p>The scaling of content is primarily a user agent responsibility. User agents that
satisfy
<a href="https://www.w3.org/TR/WAI-USERAGENT/guidelines.html#tech-configure-text-scale">UAAG 1.0 Checkpoint 4.1</a> 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.
<a href="https://www.w3.org/TR/WAI-USERAGENT/guidelines.html#tech-configure-text-scale">UAAG 1.0 Checkpoint 4.1</a>
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 reference size for rendered text.
mbgower marked this conversation as resolved.
Show resolved Hide resolved
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.
</p>

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

<p>The author cannot rely on the user agent to satisfy this Success Criterion for HTML
content if users do not have access to a user agent with zoom support. For example,
if they work in an environment that requires them to use IE 6.
through a specific text scaling mechanism if users do not have access to a user agent with that particular mechanism.
mbgower marked this conversation as resolved.
Show resolved Hide resolved
</p>

<p>If the author is using a technology whose user agents do not provide zoom support,
the author is responsible to provide this type of functionality directly or to provide
content that works with the type of functionality provided by the user agent. If the
user agent doesn't provide zoom functionality but does let the user change the
<p>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 to provide
mbgower marked this conversation as resolved.
Show resolved Hide resolved
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.
</p>
Expand All @@ -58,7 +61,7 @@ <h2>Intent of Resize text</h2>
can be accessed, is provided to the user in some way besides the fact that it is truncated.
</p>

<p>Content satisfies the Success Criterion if it can be scaled up to 200%, that is, up
<p>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,
Expand All @@ -73,7 +76,7 @@ <h2>Intent of Resize text</h2>
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.
</p>

Expand Down Expand Up @@ -131,7 +134,7 @@ <h2>Examples of Resize text</h2>
</li>

<li>
A user uses a zoom function in his user agent to change the scale of the content.
A user uses a full-page zoom function in their user agent to change the scale of the content.
patrickhlauke marked this conversation as resolved.
Show resolved Hide resolved
All the content scales uniformly, and the user agent provides scroll bars, if necessary.

</li>
Expand Down
13 changes: 6 additions & 7 deletions understanding/20/visual-presentation.html
Original file line number Diff line number Diff line change
Expand Up @@ -59,13 +59,12 @@ <h2>Intent of Visual Presentation</h2>
together, so that it is difficult for them to locate word boundaries.
</p>

<p>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.
<p>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.
</p>

<p>The scaling of content is primarily a user agent responsibility. User agents that
Expand Down