Update techniques/general/G226.html

Co-authored-by: Hidde de Vries <[email protected]>

Author: 2 people

techniques/general/G226.html

@@ -22,7 +22,7 @@ <h4>Describe any pertinent and meaningful text on the screen</h4>
    <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. 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 (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 <code>aria-label</code> 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.</p>
    <h4>When a main page or dialog appears, say its title and describe its features</h4>