Merge pull request #530 from w3c/ChrisLoiselle-patch-2

Update quoting and period method for success-criteria-problematic-for…

comments-by-guideline-and-success-criterion.md

@@ -55,7 +55,7 @@ This applies directly as written, and as described in [Intent from Understanding
 
 <div class="note wcag2ict">
 
-The WCAG 2 definition of “[captions](https://www.w3.org/TR/WCAG22/#dfn-captions)” notes that “in some countries, captions are called subtitles”. They are also sometimes referred to as “subtitles for the hearing impaired.” Per the definition in WCAG 2, to meet this success criterion, whether called captions or subtitles, they would have to provide “synchronized visual and/or [text alternative](https://www.w3.org/TR/WCAG22/#dfn-text-alternative) for both speech and non-speech audio information needed to understand the media content” where non-speech information includes “sound effects, music, laughter, speaker identification and location”.</div>
+The WCAG 2 definition of “[captions](https://www.w3.org/TR/WCAG22/#dfn-captions)” notes that “in some countries, captions are called subtitles”. They are also sometimes referred to as “subtitles for the hearing impaired". Per the definition in WCAG 2, to meet this success criterion, whether called captions or subtitles, they would have to provide “synchronized visual and/or [text alternative](https://www.w3.org/TR/WCAG22/#dfn-text-alternative) for both speech and non-speech audio information needed to understand the media content” where non-speech information includes “sound effects, music, laughter, speaker identification and location”.</div>
 
 ##### audio-description-or-media-alternative-prerecorded
 
@@ -81,7 +81,7 @@ This applies directly as written, and as described in [Intent from Understanding
 
 <div class="note wcag2ict">
 
-The WCAG 2 definition of “[captions](https://www.w3.org/TR/WCAG22/#dfn-captions)” notes that “In some countries, captions are called subtitles”. They are also sometimes referred to as “subtitles for the hearing impaired.” Per the definition in WCAG 2, to meet this success criterion, whether called captions or subtitles, they would have to provide “synchronized visual and/or [text alternative](https://www.w3.org/TR/WCAG22/#dfn-text-alternative) for both speech and non-speech audio information needed to understand the media content” where non-speech information includes “sound effects, music, laughter, speaker identification and location”.</div>
+The WCAG 2 definition of “[captions](https://www.w3.org/TR/WCAG22/#dfn-captions)” notes that “In some countries, captions are called subtitles”. They are also sometimes referred to as “subtitles for the hearing impaired". Per the definition in WCAG 2, to meet this success criterion, whether called captions or subtitles, they would have to provide “synchronized visual and/or [text alternative](https://www.w3.org/TR/WCAG22/#dfn-text-alternative) for both speech and non-speech audio information needed to understand the media content” where non-speech information includes “sound effects, music, laughter, speaker identification and location”.</div>
 
 ##### audio-description-prerecorded
 

comments-on-definitions-in-wcag-2.2-glossary-in-appendix-a.md

@@ -427,7 +427,7 @@ For non-web software, “AccessibleName” (or the corresponding term used in di
 
 ##### Applying “programmatically determined” to Non-Web Documents and Software
 
-This applies directly as written and as described in the WCAG 2 glossary, replacing “user agents, including assistive technologies,” with “assistive technologies and accessibility features of software” and adding “and accessibility features of software” after “assistive technology”.
+This applies directly as written and as described in the WCAG 2 glossary, replacing “user agents, including assistive technologies", with “assistive technologies and accessibility features of software” and adding “and accessibility features of software” after “assistive technology”.
 
 With this substitution and addition, it would read:
 

success-criteria-problematic-for-closed-functionality.md

@@ -43,7 +43,7 @@ For non-web software on products with closed functionality, those who implement
 <li><a href="#bypass-blocks">2.4.1 Bypass Blocks</a> — The WCAG2ICT interpretation of this success criterion replaces "sets of Web pages" with "sets of software programs" which are extremely rare - especially for closed functionality software. However, being able to bypass blocks of content that are repeated within software is generally considered best practice.</li>
 <li><a href="#page-titled">2.4.2 Page Titled</a> — Where the software is part of a product that provides a single function, or has a menu-driven interface, the intent of this success criterion would be met without needing an explicit title.</li>
 <li><a href="#link-purpose-in-context">2.4.4 Link Purpose (In Context)</a> — This success criterion relies upon text and context being made available in a programmatically determinable form.</li>
-<li><a href="#multiple-ways">2.4.5 Multiple Ways</a> — The WCAG2ICT interpretation of this success criterion replaces "set of Web pages" with "set of software programs." Such sets, particularly in the context of closed functionality software, are exceedingly rare. There are a number of notes in the section <a href="#applying-sc-2-4-5-multiple-ways-to-non-web-documents-and-software">Applying SC 2.4.5 Multiple Ways to Non-Web Documents and Software</a> that are applicable to closed functionality software.</li> 
+<li><a href="#multiple-ways">2.4.5 Multiple Ways</a> — The WCAG2ICT interpretation of this success criterion replaces "set of Web pages" with "set of software programs". Such sets, particularly in the context of closed functionality software, are exceedingly rare. There are a number of notes in the section <a href="#applying-sc-2-4-5-multiple-ways-to-non-web-documents-and-software">Applying SC 2.4.5 Multiple Ways to Non-Web Documents and Software</a> that are applicable to closed functionality software.</li> 
 <li><a href="#focus-visible">2.4.7 Focus Visible</a> — Presumes that there is a mode of operation where focus can be moved and controlled by keyboard. Some closed systems may offer tactilely discernible input such as a numeric keypad or other functional groups of keys, but do not offer any mechanism for conveying focus because the user interface is designed not to need that. For example, the keys are used to select options from a spoken menu rather than to move an onscreen focus element between multiple options. In this case, there is no concept of focus, thus there is no need for a visible indicator and this success criterion would be satisfied.</li>  
 <li><a href="#pointer-cancellation">2.5.2 Pointer Cancellation</a> — As noted in the section <a href="#applying-sc-2-5-2-pointer-cancellation-to-non-web-documents-and-software">Applying SC 2.5.2 Pointer Cancellation to Non-Web Documents and Software</a>, examples of ‘essential’ functionality are features for meeting environmental energy usage requirements (like waking a device from sleep, power saver mode, and low power state).</li>  
 <li><a href="#label-in-name">2.5.3 Label in Name</a> — Requires information in a programmatically determinable form; specifically, the programmatic name contains the text of the visual label.</li>