Skip to content

Commit

Permalink
Update text-spacing.html
Browse files Browse the repository at this point in the history 
Incorporated changes from #1457 into a clean PR
  • Loading branch information
@mbgower
mbgower committed Oct 30, 2024
1 parent b99ada8 commit 11191cf
Showing 1 changed file with 17 additions and 19 deletions.
36 changes: 17 additions & 19 deletions understanding/21/text-spacing.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -17,22 +17,23 @@ <h2>In brief</h2>
</section>
<section id="intent">
<h2>Intent</h2>
<p>The intent of this Success Criterion (SC) is to ensure that when people override author specified text spacing to improve their reading experience, content is still readable and operable. Each of the requirements stipulated in the SC's four bullets helps ensure text styling can be adapted by the user to suit their needs.</p>
<p>The specified metrics set a minimum baseline. The values in between the author's metrics and the metrics specified in this SC should not have loss of content or functionality.</p>
<p>The intent of this Success Criterion (SC) is to ensure that when people override author-specified text spacing to improve their reading experience, content is still readable and operable. Each of the requirements stipulated in the SC's four bullets helps ensure text styling can be adapted by the user to suit their needs.</p>
<p>The metrics set a target for a minimum increase in text spacing that must be met. Starting from the author's baseline implementation, any increase in spacing for any of these four style properties up to and including these targets should not result in the loss of content or functionality.</p>
<p>This SC focuses on the adaptability of content to an increase in spacing between lines, words, letters, and paragraphs. Any combination of these may assist a user with effectively reading text. As well, ensuring that content correctly adapts when users override author settings for spacing also significantly increases the likelihood other style preferences can be set by the user. For example, a user may need to change to a wider font family than the author has set in order to effectively read text. </p>
<section>
<h3 id="authorresp">Author Responsibility </h3>
<p>This SC does not dictate that authors must set all their content to the specified metrics, nor does the SC intend to imply that all users will adjust the specified metrics. Rather, it specifies that should a user choose to set any of these metrics they can do so without any loss of content or functionality. The author requirement is both to not interfere with a user's ability to override the author settings, and to ensure that content thus modified does not break content in the manners shown in figures 1 through 3 in Effects of Not Allowing for Spacing Override.</p>

<p>In some human languages and scripts, some of the metrics specified by the SC are inapplicable. For example, languages such as Japanese do not use spacing following paragraphs, meaning that users are unlikely to make any paragraph spacing changes in practice. The exception in this SC allows authors to ignore text style properties which are inapplicable to the combination of language and script being used.</p>

<p>It is beneficial for users if authors use any locally available guidance for improving readability in the local language or writing system. If the user chooses to go beyond the metrics specified, any resulting loss of content or functionality is the user's responsibility.</p>

<p>Further, this SC is not concerned with <em>how</em> users change the line height and spacing metrics. It does not require that content implement its own mechanisms to allow users to do this. It is not a failure of the content if a user agent or platform does not provide a way for users to do this. Content does not fail this SC if the method chosen by the user - for instance, the use of an extension or bookmarklet - fails to correctly set the line height and spacing text properties on the content (provided that the content is not actively and purposely preventing the properties from being added).</p>
<p>This SC does not dictate that authors must set all their content to the specified metrics, or provide a mechanism to do so. Rather, it specifies that an author's content has the ability to be set to those metrics without loss of content or functionality. The author requirement is both to not interfere with a user's ability to override the author settings, and to ensure that content thus modified does not break content in the manners shown in figures 1 through 3 in <a href="#effects-not-allowing">Effects of Not Allowing for Spacing Override</a>. The values in the SC are a baseline. Authors are encouraged to allow spacing to surpass the values specified, not see them as a ceiling.</p>
<p>It is beneficial for users if authors use any locally available guidance for improving readability in the local language or writing system. Conversely, in some human languages and scripts, some of the metrics specified by the SC are inapplicable. For example, languages such as Japanese do not use spacing following paragraphs, meaning that users are unlikely to make any paragraph spacing changes in practice. The exception in this SC allows authors to ignore text style properties which are inapplicable to the combination of language and script being used. </p>
</section>
<section>
<h4 id="applicability">Applicability</h4>
<p>If the markup-based technologies being used are capable of overriding text to the Success Criterion's metrics, then this SC is applicable. For instance Cascading Style Sheet/HTML technologies are quite able to allow for the specified spacing metrics. Plugin technologies would need to have a built-in ability to modify styles to the specified metrics. Currently, this SC does not apply to PDF as it is not implemented using markup.</p>
<p>Examples of text that are typically not affected by <a>style properties</a> and not expected to adapt are:</p>
<h3 id="userresp">User Responsibility</h3>
<p>The user may choose to exceed the spacing adjustments in the SC. The ability to read and derive meaning from the overridden spacing rests with the user. If large increases in spacing reduce readability, or cause loss of content or functionality, the user can adjust or return to spacing within the bounds of the SC. How such changes are achieved is up to the user, who may choose a user stylesheet, bookmarklet, extension, or application. Regardless, the user needs the flexibility to adjust spacing -- and within the bounds set in the SC, without loss of content or functionality.</p>
<p>Further, this SC does not require that content implement its own mechanisms to allow users to do this. It is not a failure of the content if a user agent or platform does not provide a way for users to do this. Content does not fail this SC if the method chosen by the user - for instance, the use of an extension or bookmarklet - fails to correctly set the line height and spacing text properties on the content (provided that the content is not actively and purposely preventing the properties from being added). </p>
</section>
<section>
<h3 id="applicability">Applicability</h3>
<p>If the markup-based technologies being used are capable of overriding text to the Success Criterion's metrics, then this SC is applicable. For instance Cascading Style Sheet/HTML technologies are quite able to allow for the specified spacing metrics. Plugin technologies would need to have a built-in ability to modify styles to the specified metrics. Currently, this SC does not apply to PDF, as the portable document format is not implemented using markup.</p>
<p>Examples of text typically not affected by <a>style properties</a> and not expected to adapt are:</p>
<ul>
<li>Video captions embedded directly into the video frames and not provided as an associated caption file</li>
<li><a>Images of text</a></li>
Expand All @@ -50,22 +51,19 @@ <h4 id="ellipses">Use of ellipses</h4>
<p>Where text is not truncated but it is when text is spaced, if there is no mechanism to show the truncated text, it fails this Success Criterion.</p>
</section>
</section>
<section>
<h3 id="userresp">User Responsibility</h3>
<p>The ability to read and derive meaning from the overridden spacing rests with the user. The user may choose to exceed the spacing adjustments in the SC. If the increased spacing causes loss of content or functionality, the user will adjust or return to the author’s original spacing or spacing within the bounds of the SC. Regardless, the user needs the flexibility to adjust spacing within the bounds set in the SC without loss of content or functionality. Such changes may be achieved via user stylesheet, bookmarklet, extension, or application.</p>
</section>


<section>
<h3 id="effects-not-allowing">Effects of Not Allowing for Spacing Override</h3>
<p>The following images show some types of failures when authors do not take into consideration that users may override spacing to the metrics specified in this Success Criterion.</p>
<p>The following images show some types of failures when authors do not take into consideration that users may override spacing to the metrics specified in this Success Criterion.</p>
<section>
<h4 id="cutoff">Text Cut Off</h4>
<p>The bottom portion of the words &quot;Your Needs&quot; is cut off in a heading making that text unreadable in Figure 1. It should read &quot;We Provide a Mobile Application Service to Meet Your Needs.&quot;</p>
<figure id="figure-text-cut">
<figcaption>Vertical text cut off is a failure.</figcaption>
<img src="img/spacing_cutoff_fail_vertical.png" alt="Heading text truncated vertically." width="420" height="190" />
</figure>
<p>In Figure 2 the last portion of text is cut off in three side-by-side headings. The first heading should read &quot;A cog in the wheel&quot;, but it reads &quot;A cog in the whe&quot;. Only half of the second &quot;e&quot; is visible and the letter &quot;l&quot; is completely missing. The second heading should read &quot;A penny for your thoughts&quot;. But it reads &quot;A penny for your&quot;. The third should read &quot;Back to the drawing board.&quot; But it reads &quot;Back to the drawi&quot;. </p>
<p>In Figure 2 the last portion of text is cut off in three side-by-side headings. The first heading should read &quot;A cog in the wheel&quot; but it reads &quot;A cog in the whe&quot;. Only half of the second &quot;e&quot; is visible and the letter &quot;l&quot; is completely missing. The second heading should read &quot;A penny for your thoughts&quot; but it reads &quot;A penny for your&quot;. The third should read &quot;Back to the drawing board.&quot; but it reads &quot;Back to the drawi&quot;. </p>
<figure id="figure-horiz-text-cut">
<figcaption>Horizontal text cut off is a failure.</figcaption>
<img src="img/spacing_cutoff_fail_horizontal.png" alt="3 side-by-side headings with truncated text." width="509" height="184" />
Expand All @@ -86,7 +84,7 @@ <h2>Benefits</h2>
<ul>
<li>People with low vision who require increased space between lines, words, and letters are able to read text.</li>
<li>People with dyslexia may increase space between lines, words, and letters to increase reading speed.</li>
<li>Although not required by this SC, white space between blocks of text can help people with cognitive disabilities discern sections and call out boxes.</li>
<li>Although not required by this SC, white space between blocks of text can help people with cognitive disabilities discern sections and call-out boxes.</li>
</ul>
</section>
<section id="examples">
Expand Down

0 comments on commit 11191cf

Please sign in to comment.