• UserControlRender

Guideline 4. Ensure user control of rendering

4.1 Configure text scale (P1)

(Original)

1. Allow global configuration of the scale of visually rendered text content. Preserve distinctions in the size of rendered text as the user increases or decreases the scale.
2. As part of satisfying provision one of this checkpoint, provide a configuration option to override rendered text sizes specified by the author or user agent defaults.
3. As part of satisfying provision one of this checkpoint, offer a range of text sizes to the user that includes at least:
   • the range offered by the conventional utility available in the operating environment that allows users to choose the text size (e.g., the font size), or
   • if no such utility is available, the range of text sizes supported by the conventional APIs of the operating environment for drawing text.

Sufficient techniques

1. The user agent may satisfy provision one of this checkpoint through a number of mechanisms, including zoom, magnification, and allowing the user to configure a reference size for rendered text (e.g., render text at 36 points unless otherwise specified). For example, for CSS2 [CSS2] user agents, the medium value of the font-size property corresponds to a reference size.

Normative inclusions and exclusions

1. The word "scale" is used in this checkpoint to mean the general size of text.
2. The user agent is not required to satisfy this requirement through proportional scaling. What must hold is that if rendered text A is smaller than rendered text B at one value of the configuration setting of provision one, then text A will still be smaller than text B at another value of this configuration setting.

3. Conformance profile labels: VisualText

UAAG2 ISSUES

4.2 Configure font family (P1)

(Original)

1. Allow global configuration of the font family of all visually rendered text content.
2. As part of satisfying provision one of this checkpoint, provide a configuration option to override font families specified by the author or by user agent defaults.
3. As part of satisfying provision one of this checkpoint, offer a range of font families to the user that includes at least:
   • the range offered by the conventional utility available in the operating environment that allows users to choose the font family, or
   • if no such utility is available, the range of font families supported by the conventional APIs of the operating environment for drawing text.

Sufficient techniques

1. For text that cannot be rendered properly using the user's preferred font family, the user agent should substitute an alternative font family.

Normative inclusions and exclusions

1. Conformance profile labels: VisualText

Notes

• For example, allow the user to specify that all text is to be rendered in a particular sans-serif font family.

UAAG2 ISSUES

4.3 Configure text colors (P1)

(Original)

1. Allow global configuration of the foreground and background color of all visually rendered text content.
2. As part of satisfying provision one of this checkpoint, provide a configuration option to override foreground and background colors specified by the author or user agent defaults.
3. As part of satisfying provision one of this checkpoint, offer a range of colors to the user that includes at least:
   • the range offered by the conventional utility available in the operating environment that allows users to choose colors, or
   • if no such utility is available, the range of colors supported by the conventional APIs of the operating environment for specifying colors.

Normative inclusions and exclusions

1. Color includes black, white, and grays.

2. Conformance profile labels: VisualText

Notes

• User configuration of foreground and background colors may inadvertently lead to the inability to distinguish ordinary text from selected text or focused text. See checkpoint 10.2 for more information about highlight styles.

UAAG2 ISSUES

4.4 Slow multimedia (P1)

(Original)

1. Allow the user to slow the presentation rate of rendered audio and animation content (including video and animated images).
2. As part of satisfying provision one of this checkpoint, for a visual track, provide at least one setting between 40% and 60% of the original speed.
3. As part of satisfying provision one of this checkpoint, for a prerecorded audio track including audio-only presentations, provide at least one setting between 75% and 80% of the original speed.
4. When the user agent allows the user to slow the visual track of a synchronized multimedia presentation to between 100% and 80% of its original speed, synchronize the visual and audio tracks (per checkpoint 2.6). Below 80%, the user agent is not required to render the audio track.

Normative inclusions and exclusions

1. Conformance profile labels: Animation, Audio

Notes

• The style exception of this checkpoint is based on the assumption that authors have satisfied the requirements of the "Web Content Accessibility Guidelines 1.0" [WCAG10] not to convey information through style alone (e.g., through color alone or style sheets alone).

UAAG2 EDIT HISTORY

• Simplifying proposal: http://lists.w3.org/Archives/Public/w3c-wai-ua/2007JulSep/0020.html

• the purpose of the audio, animation, etc. should not matter. The user should be able to stop it (CP3.2) or slow it down (CP4.4). How is the UA to know what is stylistic and what is real content? it doesn't matter what the role is, the user still needs control.
• removed exclusion 1 (was "The user agent is not required to satisfy this checkpoint for audio and animations whose recognized role is to create a purely stylistic effect. Purely stylistic effects include background sounds, decorative animated images, and effects caused by style sheets. ")

4.5 Start, stop, pause, and navigate multimedia (P1)

(Original)

1. Allow the user to stop, pause, and resume rendered audio and animation content (including video and animated images) that last three or more seconds at their default playback rate.
2. Allow the user to navigate efficiently within rendered audio and animations (including video and animated images) that last three or more seconds at their default playback rate.

Sufficient techniques

1. The user agent may satisfy the navigation requirement of provision two of this checkpoint through forward and backward serial access techniques (e.g., advance five seconds), or direct access techniques (e.g., start playing at the 10-minute mark), or some combination.

Normative inclusions and exclusions

1. When using serial access techniques to satisfy provision two of this checkpoint, the user agent is not required to play back content during advance or rewind (though doing so may help orient the user).
2. When the user pauses a real-time audio or animation, the user agent may discard packets that continue to arrive during the pause.
3. This checkpoint applies to content that is either rendered automatically (e.g., on load) or on explicit request from the user.
4. The user agent is not required to satisfy this checkpoint for audio and animations whose recognized role is to create a purely stylistic effect; see checkpoint 4.4 for more information about what constitutes a stylistic effect.
5. Conformance profile labels: Animation, Audio

Notes

• The lower bound of three seconds is part of this checkpoint since control is not required for brief audio and animation content, such as short clips or beeps. Respect synchronization cues per checkpoint 2.6.

UAAG2 ISSUES

• JR: 4.5.2 What's the use case for this being here?

4.6 Do not obscure captions (P1)

(Original)

1. For graphical viewports, allow configuration so that captions synchronized with a visual track in content are not obscured by it.

Sufficient techniques

1. Render captions "on top" of the visual track and, as part of satisfying checkpoint 4.3, allow the user to configure the foreground and background color of the rendered captions text.
2. Render captions and video in separate viewports.

Normative inclusions and exclusions

UAAG2 ISSUES

• Only if "caption" semantics are known

4.7 Global volume control (P1)

(Original)

1. Allow global configuration of the volume of all rendered audio.

2. As part of satisfying provision one of this checkpoint, allow the user to choose zero volume (i.e., silent).

Normative inclusions and exclusions

1. This checkpoint must be satisfied for all implemented specifications that produce sound; see the section on conformance profiles.
2. Conformance profile labels: Audio
3. Conformance detail: For both content and user agent

Notes

• User agents should allow configuration of volume through available operating environment mechanisms.

UAAG2 ISSUES

• UA's do not currently render sound natively, they require an external process. only that process can control the volume of the audio rendered by that process. Process may or may not be native to OS. The UA may not know about audio control seperate from the OS.

• JR: This issue is actually covered in the techniques where it is clear that the UA can rely on the OS.

• JR: Why say “Rendered Audio” are there other kinds?

4.8 Independent volume control (P1)

(Original)

1. Allow independent control of the volumes of rendered audio content synchronized to play simultaneously.

Normative inclusions and exclusions

1. The user control required by this checkpoint includes the ability to override author-specified volumes for the relevant sources of audio.
2. The user agent is not required to satisfy this checkpoint for audio whose recognized role is to create a purely stylistic effect; see checkpoint 4.4 for more information about what constitutes a stylistic effect.
3. Conformance profile labels: Audio

Notes

• The user agent should satisfy this checkpoint by allowing the user to control independently the volumes of all audio sources (e.g., by implementing a general audio mixer type of functionality). See checkpoint 4.10 for information about controlling the volume of synthesized speech.

UAAG2 ISSUES

• UA that have roles to control audio are usually "plug-ins" or screen readers. not 'standard' user agents
• definition of "recongnized" in normative inclusions #2 is not the same as UAAG definition of "recongnize", definition of "recognize" is too focused on HTML

change normative inclusion #2 UA should be required to adjust volume for all audio content - stylistic or semantic

• in the note: need to clarify by adding "including foreground and background audio" (semantic vs. sytlistic - regardless of the stated 'role' of the content)

4.9 Configure synthesized speech rate (P1)

(Original)

1. Allow configuration of the synthesized speech rate, according to the full range offered by the speech synthesizer.

Normative inclusions and exclusions

1. Conformance profile labels: Speech

Notes

• The range of synthesized speech rates offered by the speech synthesizer may depend on natural language.

UAAG2 ISSUES

• this is very screen reader specific.most UA that are self-voiceing are using extensions or plug-ins

(where do plug-in and extensions fit in UAAG?) [editor note: this may be irrelevant, as the checkpoint only pertains to UA attempting compliance in the Speech area]

• JR: I think all the speech items need a group discussion

4.10 Configure synthesized speech volume (P1)

(Original)

1. Allow control of the synthesized speech volume, independent of other sources of audio.

Normative inclusions and exclusions

1. The user control required by this checkpoint includes the ability to override author-specified synthesized speech volume.
2. Conformance profile labels: Speech

Notes

• See checkpoint 4.8 for information about independent volume control of different sources of audio.

UAAG2 ISSUES

• JR: I think all the speech items need a group discussion

4.11 Configure synthesized speech characteristics (P1)

(Original)

1. Allow configuration of synthesized speech characteristics according to the full range of values offered by the speech synthesizer.

Normative inclusions and exclusions

1. Conformance profile labels: Speech

Notes

• Some speech synthesizers allow users to choose values for synthesized speech characteristics at a higher abstraction layer, i.e., by choosing from present options that group several characteristics. Some typical options one might encounter include: voice (e.g., adult male voice, female child voice, robot voice), pitch, and stress. Ranges for values may vary among speech synthesizers.

UAAG2 ISSUES

• JR: I think all the speech items need a group discussion

4.12 Specific synthesized speech characteristics (P2)

(Original)

1. Allow configuration of synthesized speech pitch. Pitch refers to the average frequency of the speaking voice.
2. Allow configuration of synthesized speech pitch range. Pitch range specifies a variation in average frequency.
3. Allow configuration of synthesized speech stress. Stress refers to the height of "local peaks" in the intonation contour of the voice.
4. Allow configuration of synthesized speech richness. Richness refers to the richness or brightness of the voice.

Normative inclusions and exclusions

1. Conformance profile labels: Speech

Notes

• This checkpoint is more specific than checkpoint 4.11. It requires support for the voice characteristics listed in the provisions of this checkpoint. Definitions for these characteristics are based on descriptions in section 19 of the Cascading Style Sheets Level 2 Recommendation [CSS2]; refer to that specification for additional informative descriptions. Some speech synthesizers allow users to choose values for synthesized speech characteristics at a higher abstraction layer, for example, by choosing from present options distinguished by gender, age, or accent. Ranges of values may vary among speech synthesizers.

UAAG2 ISSUES

• All (1-4) This is very dependent on the speech synthesizer and beyond the control of the UA [editor note: delete this. CP is only for Speech conformance]

• JR: I think all the speech items need a group discussion

4.13 Configure synthesized speech features (P2)

(Original)

1. Provide support for user-defined extensions to the synthesized speech dictionary.
2. Provide support for spell-out: where text is spelled one character at a time, or according to language-dependent pronunciation rules.
3. Allow at least two configurations for speaking numerals: one where numerals are spoken as individual digits, and one where full numbers are spoken.
4. Allow at least two configurations for speaking punctuation: one where punctuation is spoken literally, and one where punctuation is rendered as natural pauses.

Normative inclusions and exclusions

1. Conformance profile labels: Speech

Notes

• Definitions for the functionalities listed in the provisions of this checkpoint are based on descriptions in section 19 of the Cascading Style Sheets Level 2 Recommendation [CSS2]; refer to that specification for additional informative descriptions.

UAAG2 ISSUES

• may not be completely controllable by the UA. there is negotiation between html, UA rendering, and text to speech engine.
• allow user to control components (speech characteristics) seperately, but there may be a synergistic effect with in the TTS, and additional synergies with other markup (Voice XML, etc.)
• settings feed off of each other with unexpected consequences. User is unsure which componnent is at fault...UA, or TTS, or markup
• symbols and dictionary definitions, are unique to each TTS, it is a speech setting of sorts
• TTS is trying to determine context of string of information to determine inflection, etc
• difficult to control, sythesizer has specific settings different from html settings. e.g. HP (Hewelt Packard), configure UA to not expand abbr, then send HP to synthsizer, and sythesizer says 'horsepower' as its own generated expansion.

• JR: Not sure what to do here – but checkpoint seems badly named – maybe "Configure the Format of Synthesized Speech"

• JR: I think all the speech items need a group discussion

4.14 Choose style sheets (P1)

(Original)

1. Allow the user to choose from and apply alternative author style sheets (such as linked style sheets).
2. Allow the user to choose from and apply at least one user style sheet.
3. Allow the user to turn off (i.e., ignore) author and user style sheets.

Normative inclusions and exclusions

1. This checkpoint only applies to user agents that support style sheets.

Notes

• By definition, the user agent's default style sheet is always present, but may be overridden by author or user styles. Developers should not consider that the user's ability to turn off author and user style sheets is an effective way to improve content accessibility; turning off style sheet support means losing the many benefits they offer. Instead, developers should provide users with finer control over user agent or content behavior known to raise accessibility barriers. The user should only have to turn off author and user style sheets as a last resort.

UAAG2 ISSUES

• user selectable javascript changing DOM on page load (where does this fit in guidelines) http://www.opera.com/support/tutorials/userjs/

• JR: Hard to imagine a P1 requirement for user defined Javascript