Update G226.html

Removed the references to a slide presentation

Author: mbgower

techniques/general/G226.html

@@ -7,26 +7,26 @@
       <p>This technique is most appropriate in instructional, marketing, and other videos where the narrative is intended to be informational. In such cases, a soundtrack which reinforces the visual "takeaways" in the video will be vital to blind people and people with low vision, and may be of use to many users, including some users with cognitive disabilities.</p>
    </section><section id="examples"><h2>Examples</h2>
       <h3>An instructional video is scripted with narration that describes important visual content</h3>
-   <p>Someone creating a instructional video demonstrating the features of an application, or recording a slide presentation, prepares a script where what is being shown visually is reinforced through the narration, to arrive at an efficient and cost-effective means of making accessible videos and presentations.</p>
-   <p>Several key strategies help the narration improve a video's accessibility. Each is described more fully in the following subsections:</p>
+   <p>Someone creating an instructional video demonstrating the features of an application prepares a script where what is being shown visually is reinforced through the narration, to arrive at an efficient and cost-effective means of making a more accessible video.</p>
+   <p>Several key strategies are followed to improve the video's narration. Each is described more fully in the following subsections:</p>
    <ol>
-      <li>Describe any pertinent and meaningful text on the screen or slide</li>
+      <li>Describe any pertinent and meaningful text on the screen</li>
       <li>Avoid saying only “this” or “here” to describe UI components</li>
       <li>For better context, describe elements by sensory perceptions as well as by label</li>
       <li>Fully describe sequences of action, including any dynamic content that appears</li>
       <li>When a main page or dialog appears, say its title and describe its features</li>
       <li>When using a mouse to show something (such as to hover, select, scroll, and open), say what you are doing</li>
    </ol>
-   <h4>Describe any pertinent and meaningful text on the screen or slide </h4>
+   <h4>Describe any pertinent and meaningful text on the screen</h4>
    <p>When referring to URLs, dialogs, labels, and headings, read out the text. Sometimes presenters (narrators) just highlight or point to text; speaking the visible text ensures this meaningful text is made accessible to everyone including blind users or those with low vision. When describing actions a user can do, be sure to specifically state the button names to improve the context (for example, "choose the green 'Go' button").</p>
    <h4>Avoid saying only “this” or “here” to describe UI components</h4>
-   <p>This goes hand in hand with the first rule to announce text on the screen. When presenters (narrators) point out “this button” or say “you'll see this”, they are typically referring to a visual cue they are providing on the screen or slide. Someone who can't see the screen or slide lacks the context to understand what is being referenced. Replace or augment “this” and “here” with the labels/titles to provide context: “Choose the blue Save button”, “The Profile Settings dialog appears, with several options.”</p>
+   <p>This goes hand in hand with the first rule to announce text on the screen. When presenters (narrators) point out “this button” or say “you'll see this”, they are typically referring to a visual cue they are providing on the screen. Someone who can't see the screen lacks the context to understand what is being referenced. Replace or augment “this” and “here” with the labels/titles to provide context: “Choose the blue Save button”, “The Profile Settings dialog appears, with several options.”</p>
    <h4>For better context, describe elements by sensory perceptions as well as by label</h4>
-   <p>Including position and other sensory qualities like color can really help some low vision users and users with cognitive disabilities. However, you will want to include other context, such as structural headings, in addition to position (which is usually not very helpful to blind user). For components with visible labels, always read out the label when referring to the component. Where a visible label is absent, but you are aware of other programmatic labeling that will be read by the screen reader (for example, the aria-label property or page regions), use that text. Also include placement and structure (headings) on the page or slide (for example, “the red “Cancel” button at the bottom right of the dialog”, “Select the “online only” radio button in the Settings options”).</p>
+   <p>Including position and other sensory qualities like color can really help some low vision users and users with cognitive disabilities. However, you will want to include other context, such as structural headings, in addition to position (which is usually not very helpful to blind user). For components with visible labels, always read out the label when referring to the component. Where a visible label is absent, but you are aware of other programmatic labeling that will be read by the screen reader (for example, the aria-label property or page regions), use that text. Also include placement and structure (headings) on the page (for example, “the red “Cancel” button at the bottom right of the dialog”, “Select the “online only” radio button in the Settings options”).</p>
    <h4>Fully describe sequences of action, including any dynamic content that appears</h4>
-   <p>When you are demonstrating a process, be sure to describe all steps you are carrying out. As well, announce when status messages appear, such as “loading”, and when other content appears or disappears on the screen or slide.</p>
-   <h4>When a main page, new slide, or dialog appears, say its title and describe its features</h4>
-   <p>When a dialog, slide, or page appears, read out its title. For a new page, also describe its purpose or any distinguishing characteristics. Practice a natural storytelling style that does not simply read the text on the slide or screen.</p>
+   <p>When you are demonstrating a process, be sure to describe all steps you are carrying out. As well, announce when status messages appear, such as “loading”, and when other content appears or disappears on the screen.</p>
+   <h4>When a main page or dialog appears, say its title and describe its features</h4>
+   <p>When a dialog or page appears, read out its title. For a new page, also describe its purpose or any distinguishing characteristics. Practice a natural storytelling style that does not simply read the text on the screen.</p>
    <h4>When using a mouse to show something (such as to hover, select, scroll, or open), say what you are doing</h4>
    <p>When performing complex interactions, especially by mouse, it is sometimes helpful to announce what you plan to do before doing it, then narrate while you are interacting with it, and finally summarize what you just did.</p>
    <h3>Additional narration is added to gaps in the existing soundtrack</h3>