Lowercase “Kanji”

techniques/failures/F32.html

@@ -3,7 +3,7 @@
                     spacing within a word</h1><section class="meta"><p class="id">ID: F32</p><p class="technology">Technology: failures</p><p class="type">Type: Failure</p></section><section id="applicability"><h2>When to Use</h2>
       <p>All technologies.</p>
    </section><section id="description"><h2>Description</h2>
-      <p>The objective of this technique is to describe how using white space characters, such as space, tab, line break, or carriage return, to format individual words visually can be a failure to present meaningful sequences properly. When blank characters are inserted to control letter spacing within a word, they may change the interpretation of the word or cause it not to be programmatically recognized as a single word. 
+      <p>The objective of this technique is to describe how using white space characters, such as space, tab, line break, or carriage return, to format individual words visually can be a failure to present meaningful sequences properly. When blank characters are inserted to control letter spacing within a word, they may change the interpretation of the word or cause it not to be programmatically recognized as a single word.
           </p>
       <p>Inserting white space characters into an initialism is not an example of this
                         failure, since the white space does not change the interpretation of the
@@ -13,40 +13,40 @@
    </section><section id="examples"><h2>Examples</h2>
       <section class="example">
          <h3>Failure due to adding white space in the middle of a word</h3>
-         
+
             <p>This example has white spaces within a word to space out the letters
                                 in a heading. Screen readers may read each letter individually
                                 instead of the word "Welcome."</p>
-         
+
 <pre xml:space="preserve"><code class="language-html">&lt;h1&gt;W e l c o m e&lt;/h1&gt;</code>
 </pre>
-         
+
             <p>&amp;nbsp; can also be used to add white space, producing similar failures:</p>
-         
+
 <pre xml:space="preserve"><code class="language-html">&lt;h1&gt;H&amp;nbsp;E&amp;nbsp;L&amp;nbsp;L&amp;nbsp;O&lt;/h1&gt;</code></pre>
       </section>
       <section class="example">
          <h3>White space in the middle of a word changing its meaning</h3>
-         
-            <p>In Japanese, Han characters (Kanji) may have multiple readings that
+
+            <p>In Japanese, Han characters (kanji) may have multiple readings that
                                 mean very different things. In this example, the word is read
                                 incorrectly because screen readers may not recognize these
                                 characters as a word because of the white space between the
                                 characters. The characters mean "Tokyo," but screen readers say
                                 "Higashi Kyo".</p>
-         
+
 <pre xml:space="preserve"><code class="language-html">&lt;h1&gt;東　京&lt;/h1&gt;</code></pre>
       </section>
       <section class="example">
          <h3>Using line break characters to format vertical text</h3>
-         
+
             <p>In the row header cell of a data table containing Japanese text,
                                 authors often create vertical text by using line break characters.
                                 However screen readers are not able to read the words in vertical
                                 text correctly because the line breaks occur within the word. In the
                                 following example, "東京都"(Tokyo-to) will be read "Higashi Kyo
                                 Miyako".</p>
-         
+
 <pre xml:space="preserve"><code class="language-html">&lt;table&gt;
    &lt;caption&gt;表1.　都道府県別一覧表&lt;/caption&gt;
    &lt;tr&gt;
@@ -80,4 +80,4 @@ <h3>Using line break characters to format vertical text</h3>
       </section>
    </section><section id="related"><h2>Related Techniques</h2><ul>
       <li><a href="../css/C8">C8</a></li>
-   </ul></section><section id="resources"><h2>Resources</h2></section></body></html>
+   </ul></section><section id="resources"><h2>Resources</h2></section></body></html>

techniques/general/G120.html

@@ -23,8 +23,8 @@ <h2>Description</h2>
 		<section id="examples">
 			<h2>Examples</h2>
       <section class="example">
-				<p>In the following example of Japanese text, the information giving the pronunciation in Han characters (Kanji) is rendered in parentheses immediately following the text.</p>
-         
+				<p>In the following example of Japanese text, the information giving the pronunciation in Han characters (kanji) is rendered in parentheses immediately following the text.</p>
+
 <pre xml:space="preserve"><code class="language-html">&lt;p&gt;慶應大学 (けいおうだいがく)&lt;/p&gt;</code></pre>
       </section>
 		</section>
@@ -57,4 +57,4 @@ <h2>Related Techniques</h2>
 			<h2>Resources</h2>
 		</section>
 	</body>
-	</html>
+	</html>

techniques/html/H62.html

@@ -28,8 +28,8 @@ <h2>Description</h2>
 		<section id="examples">
 			<h2>Examples</h2>
       <section class="example">
-				<h3>Ruby markup providing pronunciation information for an initialism</h3> 
-        <p>This example uses Ruby annotation to give the pronunciation of the initialism (acronym) formed by the first letters of the words Web Content Accessibility Guidelines. The letters WCAG are the base (the rb element), and the pronunciation information is shown by the Ruby text (the <code>rt</code> element). The Ruby parenthesis element <code>rp</code> is used for user agents that do not support Ruby annotations to indicate that the text in the <code>rt</code> element provides the pronunciation information. The pronunciation information is rendered in parentheses immediately following the base text. (User agents that support Ruby do not show the parentheses.) </p> 
+				<h3>Ruby markup providing pronunciation information for an initialism</h3>
+        <p>This example uses Ruby annotation to give the pronunciation of the initialism (acronym) formed by the first letters of the words Web Content Accessibility Guidelines. The letters WCAG are the base (the <code>rb</code> element), and the pronunciation information is shown by the Ruby text (the <code>rt</code> element). The Ruby parenthesis element <code>rp</code> is used for user agents that do not support Ruby annotations to indicate that the text in the <code>rt</code> element provides the pronunciation information. The pronunciation information is rendered in parentheses immediately following the base text. (User agents that support Ruby do not show the parentheses.) </p>
 <pre xml:space="preserve"><code class="language-html">&lt;p&gt;When we talk about these guidelines, we often just call them
   &lt;ruby&gt;
     &lt;rb&gt;WCAG&lt;/rb&gt;
@@ -41,7 +41,7 @@ <h3>Ruby markup providing pronunciation information for an initialism</h3>
       </section>
       <section class="example">
          <h3>Ruby annotation for Japanese</h3>
-         <p>The following is an example in Japanese. For Japanese, the Ruby is used to give the reading of Han characters (Kanji). the Ruby parenthesis element <code>rp</code> is used for user agents that do not support Ruby annotations to indicate that the text in the <code>rt</code> element provides the pronunciation information. The pronunciation information is rendered in parentheses immediately following the base text. (User agents that support Ruby do not show the parentheses.)</p>
+         <p>The following is an example in Japanese. For Japanese, the Ruby is used to give the reading of Han characters (kanji). the Ruby parenthesis element <code>rp</code> is used for user agents that do not support Ruby annotations to indicate that the text in the <code>rt</code> element provides the pronunciation information. The pronunciation information is rendered in parentheses immediately following the base text. (User agents that support Ruby do not show the parentheses.)</p>
 
 <pre lang="ja"><code class="language-html">&lt;p&gt;
   &lt;ruby&gt;
@@ -100,4 +100,4 @@ <h2>Resources</h2>
 		</ul>
 	</section>
 </body>
-</html>
+</html>

understanding/20/pronunciation.html

@@ -7,21 +7,21 @@
 </head>
 <body>
    <h1>Understanding Pronunciation</h1>
-   
+
    <section id="brief">
       <h2>In brief</h2>
       <dl>
          <dt>Goal</dt><dd>Users can identify the pronunciation of ambiguous words.</dd>
          <dt>What to do</dt><dd>Indicate how to pronounce a word, where its meaning is otherwise unclear.</dd>
-         <dt>Why it's important</dt><dd>Some people, including those with cognitive disabilities, may not understand the meaning of content.</dd> 
+         <dt>Why it's important</dt><dd>Some people, including those with cognitive disabilities, may not understand the meaning of content.</dd>
       </dl>
 
    </section>
-   
+
    <section id="intent">
       <h2>Intent of Pronunciation</h2>
-      
-      
+
+
       <p>The intent of this success criterion is to help people who are blind, people who have
          low vision, and people with reading disabilities to understand content in cases where
          meaning depends on pronunciation. Often words or characters have different meanings,
@@ -34,52 +34,52 @@ <h2>Intent of Pronunciation</h2>
          or indeterminate unless the pronunciation is known, then providing some means of determining
          the pronunciation is needed.
       </p>
-      
+
       <p>
          	For example, in the English language heteronyms are words that are spelled the same
          but have different pronunciations and meanings, such as the words desert (abandon)
          and desert (arid region). If the proper pronunciation can be determined from the context
          of the sentence, then nothing is required.  If it cannot then some mechanism for determining
          the proper pronunciation would be required. Additionally, in some languages certain
          characters can be pronounced in different ways. In Japanese, for example, there are
-         characters like Han characters (Kanji) that have multiple pronunciations. Screen readers
+         characters like Han characters (kanji) that have multiple pronunciations. Screen readers
          may speak the characters incorrectly without the information on pronunciation. When
          read incorrectly, the content will not make sense to users.
       </p>
-      
-      
+
+
    </section>
    <section id="benefits">
       <h2>Benefits of Pronunciation</h2>
-      
-      
-      <p>This success criterion may help people who: 
-         
+
+
+      <p>This success criterion may help people who:
+
       </p>
-      
+
       <ul>
-         
+
          <li>have difficulty decoding words</li>
-         
+
          <li>have difficulty using context to aid understanding</li>
-         
+
          <li>use technologies that read the words aloud</li>
-         
+
       </ul>
-      
+
    </section>
-   
+
    <section id="examples">
       <h2>Examples of Pronunciation</h2>
-      
+
       <dl>
          <dt>Giving the reading of a person's name</dt>
          <dd>Web content in Japanese provides kana (Japanese phonetic syllabary characters) written
-               next to Han characters (Kanji)  show the pronunciation of a person's name. The kana
+               next to Han characters (kanji)  show the pronunciation of a person's name. The kana
                is provided to users in parentheses right after the word. Giving the reading of the
-               words written in Han characters (Kanji) allows both sighted users and screen readers
+               words written in Han characters (kanji) allows both sighted users and screen readers
                to read/pronounce the words correctly. Note that screen readers will speak the word
-               twice: the Han characters (Kanji) that can be pronounced in a wrong way are read first
+               twice: the Han characters (kanji) that can be pronounced in a wrong way are read first
                and then kana is spoken in order to provide the correct reading.</dd>
          <dt>Showing the reading of the words by ruby element</dt>
          <dd>Web content using HTML provides kana (phonetic syllabary characters) written
@@ -100,23 +100,23 @@ <h2>Examples of Pronunciation</h2>
                Japanese text. Pronunciation information is provided to show the correct reading of
                the Chinese and Korean characters.</dd>
       </dl>
-      
+
       <div class="note">
-         
+
          <p>For Japanese, the ruby element is used for showing the "reading" rather than "pronunciation."
-            
+
          </p>
-         
+
       </div>
-      
+
    </section>
-   
+
    <section id="resources">
       <h2>Resources for Pronunciation</h2>
-      
-      
+
+
    </section>
-   
+
    {% # Data for associated techniques is defined in understanding/understanding.11tydata.js %}
    {% include "understanding/techniques.html" %}
 </body>

understanding/20/readable.html

@@ -7,16 +7,16 @@
 </head>
 <body>
    <h1>Understanding Readable</h1>
-   
-   
+
+
    <section id="intent">
       <h2>Intent of Readable</h2>
-      
-      
+
+
       <p>The intent of this guideline is to allow text content to be read by users and by assistive
          technology, and to ensure that information necessary for understanding it is available.
       </p>
-      
+
       <p>People with disabilities experience text in many different ways. For some the experience
          is visual; for some it is auditory; for some it is tactile; for still others it is
          both visual and auditory. Some users experience great difficulty in recognizing written
@@ -30,16 +30,16 @@ <h2>Intent of Readable</h2>
          may be unable to present text correctly unless the language and direction of the text
          are identified; while these may be minor problems for most users, they can be enormous
          barriers for users with disabilities. In cases where meaning cannot be determined
-         without pronunciation information (for example, certain Japanese Kanji characters),
+         without pronunciation information (for example, certain Japanese kanji characters),
          pronunciation information must be available as well
       </p>
-      
+
    </section>
-   
+
    <section id="advisory">
       <h3>Additional Techniques (Advisory) for Readable</h3>
-      
+
    </section>
-   
+
 </body>
 </html>