See also: IRC log
<trackbot> Date: 25 February 2010
<jeanne> trackbot, start meeting
<trackbot> Meeting: User Agent Accessibility Guidelines Working Group Teleconference
<trackbot> Date: 25 February 2010
<jeanne> http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100224/Overview.html
<kford> How is it going there?
<jeanne> Just setting up...
<kford> Hello to everyone and sorry I'm not there in person.
<jeanne> http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100224/Overview.html
<jeanne> meeting: UAWG F2F Day 1
<jeanne> scribe: greg
<jeanne> scribe:kford
<scribe> Scribe: kford
<mhakkinen> http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100224/Overview.html
Group taking care of housekeeping items.
<jeanne> http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100224/MasterUAAG20100224.html
JA: Let's start with questions Jeanne had.
Jeanne: We had some new SC 4.9.9 to 4.9.13. We need some titles for these.
JA Proposes scale viewport for 4.9.11
Group discussing if this is all media or not.
GL: Options are move some out or
come up with better name.
... Would it make sense to separate into one based on media and
one that isn't.
JA: Do we just say scale playback viewport?
<scribe> ACTION: JA to update title of 4.9.11 to scale playback viewport [recorded in http://www.w3.org/2010/02/25-ua-minutes.html#action01]
<trackbot> Created ACTION-300 - Update title of 4.9.11 to scale playback viewport [on Jim Allan - due 2010-03-04].
/me how do I assign to someone else, just assigned to the wrong person.
<jeanne> new version with todays edits: http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100225/MasterUAAG20100225.html
Action 300 really belongs on JS.
<trackbot> Sorry, couldn't find user - 300
Group discussion what is really meant by scaling and sizing.
MH: Want to be able to limit keeping and not lose aspect ratio.
That's limit clipping.
JA: I've seen players that let you double size of player and media still stays within aspect ratio.
GL: Do we want the user to be able to make the actual video larger but not at the cost of losing something else e.g. cropping or scaling that loses the aspect ratio.
<mhakkinen> User has the ability to adjust the size of the content within the playback viewport, with the option to preserve aspect ratio and to adjust the size of the playback viewport to avoid cropping.
<mhakkinen> User has the ability to adjust the size of the content within the playback viewport, with the option to preserve aspect ratio and to adjust the size of the playback viewport to avoid cropping, within the limits of the containing viewport.
JS: What level are we talking about?
More discussion about scaling, size. Some video may only be scalable by certain sizes.
GL: Do we think it is acceptable to not allow scaling to the full size of the viewport?
<greg> Kim suggested "User has the ability to adjust the size of the content up to the full height or width of the containing viewport, with the option to preserve aspect ratio and to adjust the size of the playback viewport to avoid cropping, within the limits of the containing viewport."
JS: I'm not sure at AA we need an option to preserve aspect ratio as an option.
JA: Default is that aspect ratio is always preserved. User can turn it off.
JS: This means developer has to add ability to turn this ability of preservation off.
More discussion about preservation of aspect ratio and what option implies.
<mhakkinen> User has the ability to adjust the size of the content up to the full height or width of the containing viewport, with the ability to preserve aspect ratio and to adjust the size of the playback viewport to avoid cropping, within the limits of the containing viewport
<jeanne> issue: Review the document for consistency of the use of option: option, ability, by default, on/off, or always.
<trackbot> Created ISSUE-65 - Review the document for consistency of the use of option: option, ability, by default, on/off, or always. ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/65/edit .
Discussion of what option is about continues.
G: Makes point about options that are on by default and uses keyboard option needinGL: to be on by default or keyboard user would be stuck.
<jeanne> kim: the use of "by default should be rarely used so as not to limit developer unnecessarily and should only be used when the non default option would prevent accessibility.
<jallan> GL: use "user has the ability" vs "user has the option" throughout the document
GL: If we really want the ability to turn off/on important options we should use on/off explicitedly.
Group returning to actual 4.9.11 SC.
<mhakkinen> User has the ability to adjust the size of the time-based media up to the full height or width of the containing viewport, with the ability to preserve aspect ratio and to adjust the size of the playback viewport to avoid cropping, within the limits of the containing viewport
GL: We don't restrict this to time based media right now. If this is what we mean we should be explicit.
<jallan> techniques: if the codec does not support unlimited resizing, this will limit the users ability for resizing
Group talking about issues that arise from exceptions and how to handle. For example audio.
<jallan> MH: scaling limit imposed by the media
<mhakkinen> User has the ability to adjust the size of the time-based media up to the full height or width of the containing viewport, with the ability to preserve aspect ratio and to adjust the size of the playback viewport to avoid cropping, within the limits of the containing viewport, and by any scaling limitations imposed by the media itself.
<mhakkinen> User has the ability to adjust the size of the time-based media up to the full height or width of the containing viewport, with the ability to preserve aspect ratio and to adjust the size of the playback viewport to avoid cropping, within the limits of the containing viewport and any scaling limitations imposed by the media itself.
<mhakkinen> User has the ability to adjust the size of the time-based media up to the full height or width of the containing viewport, with the ability to preserve aspect ratio and to adjust the size of the playback viewport to avoid cropping, within the scaling limitations imposed by the media itself.
Jeanne is updating draft live with change.
<jeanne> http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100225/MasterUAAG20100225.html
Group now looking for title on 4.9.12.
↑4.9.12↑ TITLE NEEDED↑. User has ability to scale and position alternative media tracks independent of base video. (Level AAA)↑
Group revisits examples of this like a presentation at csun that scrolled 5 lines of captioning.
Title for 4.9.12 is scale and position of alternative media tracks.
↑4.9.13↑ TITLE NEEDED↑. User has ability to control the contrast and brightness of the content within the playback viewport. ↑
GL Need levels on a couple of these.
<jallan> University of Toronto had working examples 10 years ago. Geoff Freed and Larry Goldberg session at CSUN 2 years ago showed many examples caption in different locations, but not the user could disconnect and move where needed.
<jallan> discussion of contrast/brightness of only video vs all media. what should the recommended range be.
<jallan> ACTION: jallan to find appropriate range of contrast/brighness adjustment [recorded in http://www.w3.org/2010/02/25-ua-minutes.html#action02]
<trackbot> Created ACTION-301 - Find appropriate range of contrast/brighness adjustment [on Jim Allan - due 2010-03-04].
<jeanne> ACTION: jeanne to put in Status notes that the group needs expertise in contrast bright adjustment range for video for low vision [recorded in http://www.w3.org/2010/02/25-ua-minutes.html#action03]
<trackbot> Created ACTION-302 - Put in Status notes that the group needs expertise in contrast bright adjustment range for video for low vision [on Jeanne Spellman - due 2010-03-04].
<jallan> new title: 4.9.13 adjust playback contrast and brightness
<jallan> need to be consistent...do we use time-based media or playback viewport.
<jallan> GL: need to define playback viewport
Group talking about if playback is really a short hand to time based media.
Looking at definitions.
<jallan> definition synchronized media
<jallan> audio or video synchronized with another format for presenting information and/or with time-based interactive components, unless the media is a media alternative for text that is clearly labeled as such
<jeanne> ACTION: Mhakkinen to draft a definition of Time-Based Media and Playback [recorded in http://www.w3.org/2010/02/25-ua-minutes.html#action04]
<trackbot> Sorry, couldn't find user - Mhakkinen
<jeanne> ACTION: hakkinen to draft a definition of Time-Based Media and Playback [recorded in http://www.w3.org/2010/02/25-ua-minutes.html#action05]
<trackbot> Created ACTION-303 - Draft a definition of Time-Based Media and Playback [on Markku Hakkinen - due 2010-03-04].
<jeanne> ACTION: kim to review document for consistency of use of "option" with jeanne [recorded in http://www.w3.org/2010/02/25-ua-minutes.html#action06]
<trackbot> Sorry, couldn't find user - kim
<jeanne> ACTION: kimberly to review document for consistency of use of "option" with jeanne [recorded in http://www.w3.org/2010/02/25-ua-minutes.html#action07]
<trackbot> Created ACTION-304 - Review document for consistency of use of "option" with jeanne [on Kimberly Patch - due 2010-03-04].
/me volunteers for new scribe?
<jallan> http://lists.w3.org/Archives/Public/w3c-wai-ua/2009JulSep/0023.html
<jeanne> http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100225/MasterUAAG20100225.html
<jeanne> 4.8.1 Configure Position: For graphical user agent user interfaces with toolbars, the user can add, remove and configure the position of user agent user interface controls on those toolbars from a pre-defined set of controls. (Level AAA)
<jeanne> When the user has the ability to arrange interface controls, the interface becomes flexible enough to meet the needs of people with disabilities, including cognitive disabilities.
<jeanne> Example:
<jeanne> A user with cognitive disabilities can create a toolbar that contains only the functions they need without other components that could distract. The user agent provides a dialog box with a list of available components that users can choose to add or remove from a toolbar, and organize in any order. The dialog box and controls are programmatically available to assistive technology and can be operated by keyboard via cut and paste.
<jeanne> 4.8.2 Restore Default Toolbars: The user can restore the default toolbar configuration. (Level AAA)
<jeanne> Error recovery is an important support for users with cognitive disabilities and for users who may not be able to see changes to the interface. A user making changes to a toolbar configuration needs a simple ability to reset the toolbar to the default configuration and start again.
<jeanne> Example:
<jeanne> The dialog box for creating toolbar has a keyboard accessible button at the bottom labeled "Reset".
4.6.2: Find Direction:
Intent:
Searching in any direction from the current point of focus allows for maximum flexibility in allowing the user to easily locate the text used in the search.
Example:
A user has been reading through a web page and wants to quickly locate a phrase previously read. When opening the browser’s page search feature, the user has options to search forward and backward from the current location. If the search reaches an endpoint in the document, the user is notified that the search has wrapped around, such as with an alert box or other indication.
Resources:
4.6.3 Match Found
Intent:
The user should be alerted of a successful search and be able to easily view the successful search and related text.
Example:
When a successful search happens within a document, the viewport scrolls so the user can read at least the surrounding sentence. The user can also quickly initiate a search for the same text if the match in question is not the desired instance of the found text.
Resources:
<jallan> GL: enhance 4.6.2 greatly reduce amount of reading they need to read through to find the information they need. Improve navigation efficiency for people with dexterity issues.
<jallan> ... Improve navigation efficiency which is expecially important for people with dexterity issues (telephone based browsing, speech input users, etc.). Or reducing the number of utterances for people using speech input
<jallan> dexterity issues, every keystroke is time consuming, tiring, or painful
<jeanne> http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100225/MasterUAAG20100225.html
<jallan> 4.6.3 Match Found Intent: The user should be alerted of a successful search and be able to easily view the successful search and related text. Example: When a successful search happens within a document, the viewport scrolls so the user can read at least the surrounding sentence. The user can also quickly initiate a search for the same text if the match in question is not the desired...
<jallan> ...instance of the found text.
<greg> For intent of 4.6.2: It is important to provide explicit feedback when a search reaches the end of the document and starts again from the beginning, or vice versa, so that a user who cannot easily see scroll bars and other passive feedback mechanisms does not end up searching through the document over and over again without realizing it.
<sharper> http://lists.w3.org/Archives/Public/w3c-wai-ua/2010JanMar/0009.html
<jeanne> http://lists.w3.org/Archives/Public/w3c-wai-ua/2010JanMar/0009.html
<greg> Re Simon's 4.6.1, "search within rendered content for text and text alternatives" makes it sound like you're search FOR rather than WITHIN the text.
<jallan> 4.6.1 Find: The user can perform a search within rendered content (e.g., not hidden with a style) within text and text alternatives, for any sequence of characters from the document character set. (Level A)
<mhakkinen> 4.6.1 Find: The user can perform a search within rendered content (e.g., not hidden with a style), including text alternatives, for any sequence of characters from the document character set. (Level A)
this seems good.
<jallan> Resolution: > 4.6.1 Find: The user can perform a search within rendered content (e.g., not hidden with a style), including text alternatives, for any sequence of characters from the document character set. (Level A)
<greg> Re 4.6.2 "from any selected or focused location", does that mean that when selection and focus are separated, the user has the choice of which location to search from?
<jallan> discussing 4.6.2. search from focus or selection.
<jallan> KP: also an issue for keyboard vs mouse, easy to change focus with mouse
<sharper> Find Direction: The user has the option of searching forward or
<sharper> backward within any selected or focused location in content. The user will
<sharper> be notified of changes in search direction; and when the search reaches
<sharper> the upper or lower extent of the content based on the search direction.
<sharper> (Level A)
<jallan> > Find Direction: The user has the option of searching forward or backward from focused location in content or within any selected content. The user will be notified of changes in search direction; and when the search reaches the upper or lower extent of the content based on the search direction. (Level A)
<jallan> Find Direction: The user has the option of searching forward or backward from the focused location in content. The user will be notified of changes in search direction; and when the search reaches the upper or lower extent of the content based on the search direction. (Level A)
<jallan> AAA search within selection- lots of mentions of a particular word, but want to limit the search area of finding the particular word.
<jallan> for instance in a blog. in word processing very useful.
<jallan> JS protest inclusion as AAA
<jallan> KF, KP +1
<jallan> discussion of use case
<jallan> SH: google docs, might have this feature.
<jallan> KF: conformance, hard to build a use case for this. AAA should not be a wish list.
<jallan> KP: would be useful in google doc, but may not be as useful in web pages.
<jallan> SH: protest. we should include this.
<jallan> ... can we put this in the document and as the reviewers at the next draft for feedback.
<greg> Since there is debate over whether searching within a selection should be an SC, a compromise is to make it a best practice discussed in the Implementation document, rather than an actual SC.
<jallan> For implementation.. It is recommended that the user also has the ability to search forward or
<jallan> backward within any selected content. @@needs some explanation. how to keep searching within the selected content
<jallan> discussing 4.6.3
<jallan> GL: "Or, if the caret has been moved, from its new location." seems to overlap with 4.6.1
<jallan> JA: +1
<jallan> KP: but should be included in the implementation.
<jallan> 4.6.3 Match Found: When there is a match, it is highlighted, and the viewport moves so that the matched text content is at least partially within it. The user can search for the next instance of the text from the location of the match.
<jallan> ACTION: Mark to write sc 4.6.x UA informs user of the number of matches found (AAA), implementation - important for dyslexics, site research. [recorded in http://www.w3.org/2010/02/25-ua-minutes.html#action08]
<trackbot> Sorry, couldn't find user - Mark
<jallan> ACTION: Markku to write sc 4.6.x UA informs user of the number of matches found (AAA), implementation - important for dyslexics, site research. [recorded in http://www.w3.org/2010/02/25-ua-minutes.html#action09]
<trackbot> Created ACTION-305 - Write sc 4.6.x UA informs user of the number of matches found (AAA), implementation - important for dyslexics, site research. [on Markku Hakkinen - due 2010-03-04].
<jallan> ACTION: Kim to write sc for when match is found, user can jump to that point in the content. [recorded in http://www.w3.org/2010/02/25-ua-minutes.html#action10]
<trackbot> Sorry, couldn't find user - Kim
<jallan> ACTION: KP to write sc for when match is found, user can jump to that point in the content. [recorded in http://www.w3.org/2010/02/25-ua-minutes.html#action11]
<trackbot> Created ACTION-306 - Write sc for when match is found, user can jump to that point in the content. [on Kimberly Patch - due 2010-03-04].
<jallan> http://lists.w3.org/Archives/Public/w3c-wai-ua/2010JanMar/0080.html
<jallan> KF: item 5. what do we want people to list. the examples confuse me
<jallan> JS: eg. mathml, someone would want to know that it is accessibly supported.
<jallan> KF: but we have no requirements for mathml
<jallan> KP: it is useful to have a list so someone can look up
<jallan> KF: so IEx is level A compliant with uaag20. mathml has nothing to do with that.
<jallan> GL: fine, but user may need to know about mathml
<jallan> KF: this is a nice to have. not required.
<jallan> KF: browser with no search. conformance claim, I would say I comply with 4.6 because I include the search plugin for the cool browser
<jallan> JS: this is an opportunity to meet some requirements you might otherwise not meet
<jallan> ... eg. ability to resize video. some format would not meet the requirements. so you can say I conform but I exclude formatxx.
<jallan> KF: need better examples.
<jallan> KF: Flash
<jallan> GL: list of 2 things, things you support in an accessible way, and things that you support but are not accessible.
<jallan> list might include:
<jallan> ... html (versions)
<jallan> ... css (versions)
<jallan> ... video/audio codecs included with install
<jallan> ... plugins (own or 3rd party - must be specific) that are needed to meet specific SC
/me Do we want this scribed and who wants to scribe?
<jallan> discussion of conformance
<jallan> discussion of creating a tool for folks to submit conformance claims.
<jallan> ...who will monitor and maintain and verify
<jallan> ... do we want a formal or informal claim of compliance. WCAG has formal, ATAG has informal
<jallan> KF: do most specs have a conformance section,
<jallan> JS: all WAI documents have them. ATAG says posting conformance to the web is optional, because there are so many authoring tools. UAAG has a narrower scope
<jallan> JS: is posting a claim a requirement for conformance
<jallan> ... claim on a collection of technologies.
<jallan> ... is included, exclude technologies part of conformance
<jeanne> scribe:mhakkinen
JA: i think posting a claim is a
good thing, browsers to meet level A will have to do that.
There are some things they can exclude.
... my concern, is that if UA doesn't do TTS, does it then
exclude the level A's related to TTS?
JS: If you don't have TTS, then you say that with JAWS it is.
GL: Don't want UA claiming UAAG conformance but excluding half of UAAG?
<jeanne> http://lists.w3.org/Archives/Public/w3c-wai-ua/2010JanMar/0077.html
GL: give rationale for what is not applicable.
e.g., we don't comply with this because we are on a system (such as a kiosk) that does not support AT
<kford> conformance claim. The user agent is not required to meet the
JS: table conformance discussion for now. JS will integrate with draft.
<kford> requirements of UAAG 2.0 during the production of the web content
<kford> A declaration that the success criterion is not applicable and a
<kford> rationale for why not.
<jeanne> ACTION: JS to put the Conformance proposal into the document for further discussion. [recorded in http://www.w3.org/2010/02/25-ua-minutes.html#action12]
<trackbot> Created ACTION-307 - Put the Conformance proposal into the document for further discussion. [on Jeanne Spellman - due 2010-03-04].
<greg> I'm concerned that, while the Conformance Claims section allows listing SC that are inapplicable to the UA, the Conformance Requirements section does not provide for any exceptions, including on the grounds of inapplicability (e.g. stand-along systems that don't allow addiiton of assistive technology).
<greg> Therefore we're discussing modifying Conformance Requirements to include wording about exceptions where SC are inapplicable.
<greg> See ISO 9241-171 for example wording: Conformance with this part of ISO 9241 is achieved by satisfying all the applicable requirements and by the provision of a systematic list of all the recommendations that have been satisfied. Any requirements that have been determined not to be applicable shall also be listed, together with a statement of the reasons why they are not applicable.
JA: A UA could say we don't do TTS and the AT vendor could claim conformance, when there SR is used with the UA.
KF: what does saying "it works with JAWS" really mean?
<greg> Conformance claim would ideally distinguish whether compliance with a success criterion is available (a) by default, (b) with configuration changes that can be made through the product or the platform, (c) with separate software (e.g. Firefox add-in).
<jallan> http://www.w3.org/WAI/UA/impl-pr2/evaluations/eval_win_ie6.html
JA: example of IE6 eval with UAAG1 posted
GL: distinguish between external sw/plugins you pay for or are free.
KF: should not ref cost. May not be as efficient.
<greg> Users can also benefit from a report on compliance with constellations or sets of success criteria, which could help them distinguish whether it was accessible to people with their needs (e.g. great on keyboard, even if lousy on screen reader access).
table this discussion for now.
<jeanne> ACTION: Jeanne to put proposals for Implementing Principle 4 for next week's survey. [recorded in http://www.w3.org/2010/02/25-ua-minutes.html#action13]
<trackbot> Created ACTION-308 - Put proposals for Implementing Principle 4 for next week's survey. [on Jeanne Spellman - due 2010-03-04].
pairing up and picking numbers
<kford> 3.8.1-3 override of speech characteristics
<kford> Intent:
<kford> The objective of these success criteria is to allow the user to customize the specified speech characteristics to settings that aare appropriate to the way the user needs to consume the audio information. Users may need to increase the volume to a level within their range of perception for example. Users may also wish to increase the rate of synthesized speech because they can understand...
<kford> ...it at a faster rate than the author-defined rate.
<kford> Example:
<kford> A telephone based web browser starts reading back a web page. The user can press a key to increase the rate at which the information is read back. Similarly, the user may be using this telephone browser inaa noisy environment such as a crowded subway. With a key press the user can quickly increase the volume of the speech being heard.
<kford> 3.8.1-3 override of speech characteristics
<kford> Intent:
<kford> The objective of these success criteria is to allow the user to customize the specified speech characteristics to settings that aare appropriate to the way the user needs to consume the audio information. Users may need to increase the volume to a level within their range of perception for example. Users may also wish to increase the rate of synthesized speech because they can understand...
<kford> ...it at a faster rate than defaults of the user agent.
<kford> Example:
<kford> A telephone based web browser starts reading back a web page. The user can press a key to increase the rate at which the information is read back. Similarly, the user may be using this telephone browser inaa noisy environment such as a crowded subway. With a key press the user can quickly increase the volume of the speech being heard.
Intent of Success Criterion 3.7.1:
User agents can render audio from a variety sources, and in some cases, multiple audio tracks may be present
on a single page. Screen reader or self voicing browser users may encounter content where the presentation
volume of an audio track makes it difficult to hear the text to speech synthesis of their screen reader or browser.
Users should be able to globally set the volume of audio track globally, rather than having
to adjust the volume of each audio track player.
Examples of Success Criterion 3.7.1:
A user agent provides a master audio volume control that applies to all audio tracks rendered from content. The user may
define a default volume level through a preferences dialog that is retained across browsing sessions.
3.7.1 Global Volume: The user can globally set volume of all audio
tracks it renders (including a "mute" setting) through available
operating environment mechanisms. (Level A)
Intent of Success Criterion 3.7.1:
User agents can render audio tracks from a variety sources, and in some cases, multiple audio tracks may be present
on a single page. User of a screen reader or self voicing browser user may encounter content where the presentation
volume of an audio track makes it difficult to hear the text to speech synthesis of their screen reader or browser.
Users should be able to globally set the volume of audio track, rather than having
to adjust the volume of each audio track being played.
Examples of Success Criterion 3.7.1:
A user agent provides a master audio volume control that applies to all audio tracks rendered from content. The user may
define a default volume level through a preferences dialog that is retained across browsing sessions.
revised 3.7.1 follows:
Guideline 3.7 Provide volume configuration.
3.7.1 Global Volume: The user can globally set volume of all audio tracks it renders (including a "mute" setting) through available operating environment mechanisms. (Level A)
Intent of Success Criterion 3.7.1:
User agents can render audio tracks from a variety sources, and in some cases, multiple audio tracks may be present on a single page. User of a screen reader or self voicing browser user may encounter content where the presentation volume of an audio track makes it difficult to hear the text to speech synthesis of their screen reader or browser. Users should be able to globally set the volume of audio track, rather than having to adjust the volume of
each audio track being played.
Examples of Success Criterion 3.7.1:
A user agent provides a master audio volume control that applies to all audio tracks rendered from content. The user may define a default volume level through a preferences dialog that is retained across browsing sessions.
A user encounters a page with two advertisments and one video which began playback on page load complete. A global mute command in the user agent allows the user to immediately silences the playing audio tracks, while leaving their screen reader's text to speech synthesizer volume at their preferred level.
3.7.1 Global Volume: The user can globally set volume of all audio tracks it renders (including a "mute" setting) through available operating environment mechanisms. (Level A)
Intent of Success Criterion 3.7.1:
User agents can render audio tracks from a variety sources, and in some cases, multiple audio tracks may be present on a single page. Users should be able to globally set the volume of audio track, rather than having to adjust the volume of each audio track being played.
Examples of Success Criterion 3.7.1:
An operating system provides a master audio volume control that applies to all audio tracks rendered within the environment, including the user agent. The user may define a default volume level through a preferences dialog that is retained across sessions.
A user encounters a page with two advertisments and one video which began playback on page load complete. A global mute command, supported via a mute key on the user's keyboard, allows the user to immediately silence the playing audio tracks.
3.7.2 Speech Volume: The user agent allows the user to adjust the volume of all audio tracks it renders, independent or relative to the volume level at the operating environment.
Intent of Success Criterion 3.7.2:
Users of a screen reader or self voicing browser may encounter content where the presentation volume of an audio track makes it difficult to hear the text to speech synthesis of their screen reader or browser. Users should be able to set the individual volume of audio tracks rendered by the user agent, including text to speech synthesis, independent of the operating environment's volume settings.
Examples of Success Criterion 3.7.2:
A self-voicing user agent provides separate audio volume controls the speech synthesizer and audio tracks rendered from content. The user may define default volume levels through a preferences dialog that is retained across browsing sessions.
A user encounters a page a video which begins playback on page load complete. A volume control for rendered audio tracks allows the user to immediately silence the audio track, while leaving their screen reader's text to speech synthesizer volume at their preferred level.
my nokia linux phone just rebooted
<kford> I'll call you back.
<kford> But is this burning all your cell minutes, do you want me to use the regular line?
it is still booting.
no, you can use this line, I have a good plan.
<kford> I was just saying that in your second sentence it needs to be audio tracks or an audio track.
you can try calling now
<kford> 3.8.4 speech features
<kford> Intent:
<kford> Synthetic speech can be difficult to understand at times. The purpose of this criteria is to offer controls that allow the user to clarify items that tend to need clarification when using synthetic speech.
<kford> Example:
<kford> The speech synthesizer incorrectly pronounces the last name of a user. A dictionary allows the user to enter a spelling of the name that produces the correct pronunciation from the synthetic speech.
<kford> A speech synthesizer is repeating a phone number. The user wishes to easily copy this number so switches to a mode where each digit is spoken as a unique word e.g. five, five, five and so on.
<kford> 3.8.4 speech features
<kford> Intent:
<kford> The synthetic speech presentation of text can be difficult to understand at times. Success criteria here are aimed at giving the user the ability to adjust the way in which the speech synthesizer presents text to improve understandability.
<kford> The purpose of this criteria is to offer controls that allow the user to clarify items that tend to need clarification when using synthetic speech.
<kford> Example:
<kford> The speech synthesizer incorrectly pronounces the last name of a user. A dictionary allows the user to enter a spelling of the name that produces the correct pronunciation from the synthetic speech.
<kford> A speech synthesizer is repeating a phone number. The user wishes to easily copy this number so switches to a mode where each digit is spoken as a unique word e.g. five, five, five and so on.
Intent of Success Criterion 3.13.1:
Links within Web content can result in actions that may change context, open new browser windows, or result in downloads of content or media that the user cannot view. The intent of this criterion is to provide sufficient information to users identify the purpose of a link, the type of content to be linked to, and whether the content will appear within the current viewport or open in a new viewport.
Examples of Success Criterion 3.13.1:
A user encounters a link on a product support Web site that identifies that more information is available regarding the use of a product. The link content indicates the information is in a document format that is not familiar to the user, and that it will be opened in a new browser Window. The user finds a second link indicating that the same information is available as an HTML page, and will be viewed in the current browser window.
Revised 3.13.1:
Guideline 3.13 Provide link information.
3.13.1 Basic Link Information: The following information is provided for each link (Level A):
(a) link element content,
(b) link title,
(c) technology type: of the linked Web resource,
(d) internal/external: whether the link is internal to the resource (e.g., the link is to a target in the same Web page),
(e) new viewport: whether the author has specified that the resource will open in a new viewport.
Intent of Success Criterion 3.13.1:
Links within Web content can result in actions that may change context, open new browser windows, or result in downloads of content or media that the user cannot view. The intent of this criterion is to provide sufficient information so that users may identify the purpose of a link, the type of content to be linked to, and whether the content will appear within the current viewport or open in a new viewport.
Examples of Success Criterion 3.13.1:
A user encounters a link on a product support Web site that identifies that more information is available regarding the use of a product. The link content indicates the information is in a document format that is not familiar to the user, and that it will be opened in a new browser Window. The user finds a second link indicating that the same information is available as an HTML page, and will be viewed in the current browser window.
<kford> 3.9 stylesheets
<kford> Intent:
<kford> CSS stylesheets allow for extensive customization of the rendering of web content. Such customization is frequently used to make web content accessible to a wide range of user needs. These success criteria ensure that users of web browsers can fully take advantage of the stylesheets offered by web authors of that the users have created.
<kford> Example:
<kford> A user finds yellow text on a black background easiest to read. When a web site is loaded, the user agent alerts the user that the web author has created several stylesheets for the web site. The user selects a stylesheet named yellow on black from a menu in the user agent listing all available stylesheets. The web content is then rendered using this stylesheet.
<kford> On a shared computer a web site is rendered with black text on a white background that is normally in full color. The user agent notifies the user that a user-defined stylesheet has been applied to the web page and the user easily disables this stylesheet. The web site is now rendered in full color.
Examples of Success Criterion 3.13.2:
Users may not readily determine, from link content or context, that the target page has already been visited. A user agent may indicate through color, or in the case of a self-voicing browser, through a spoken announcement, that a link has been previously visited.
A user is deciding whether to download the lite or full version of a new browser plug-in. Because the user is on a mobile internet connection, download time and cost is a significant concern. The link to each download provides the size of the file, allowing the user to decide which should be downloaded.
A student is searching for research articles in cell biology. An article of interest provides and english summary on the author's Web site, but the link to the full article indicates that the content is in a language the student does not understand.
Intent of Success Criterion 3.13.2:
The intent of this criterion is to provide extended information that allows users to determine whether a link should be selected, based upon whether the link has been previously visited, by the size of the content to be downloaded when the link is selected, or by the language of the linked content.
KF: propose removal of 3.8.5
<jallan> Group agrees about removal of 3.8.5
<jeanne> ACTION: JS to remove 3.8.5 [recorded in http://www.w3.org/2010/02/25-ua-minutes.html#action14]
<trackbot> Created ACTION-309 - Remove 3.8.5 [on Jeanne Spellman - due 2010-03-04].
<jeanne> ACTION: Jeanne to remove 3.13.2 and put a note in the status saying that this was deleted because it was not an accessibility issue. [recorded in http://www.w3.org/2010/02/25-ua-minutes.html#action15]
<trackbot> Created ACTION-310 - Remove 3.13.2 and put a note in the status saying that this was deleted because it was not an accessibility issue. [on Jeanne Spellman - due 2010-03-04].
<jallan> discussion of 3.13.1 all except (a) could be done by UA, but none currently do.
<jallan> KP: A and E (link text, and open in new window) should be Level A, others should be AA or AAA or removed.
<jallan> ... discussion by all
<jallan> what about configuring the UA to only go to pages that the browser can render
<greg> 3.13 SC should include wordings restricting it to recognized qualities (e.g. technology type when specified as a link attribute by the author, or new viewport when specified using target attribute rather than javascript).
<jallan> ACTION: JS make 3.13.1 A and E level A, make B, C, D, level AAA. use same wording. Basic Link Information: The following information is provided for each link [recorded in http://www.w3.org/2010/02/25-ua-minutes.html#action16]
<trackbot> Created ACTION-311 - Make 3.13.1 A and E level A, make B, C, D, level AAA. use same wording. Basic Link Information: The following information is provided for each link [on Jeanne Spellman - due 2010-03-04].
<jallan> rssagent, make minutes
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/g/GL:/ Found Scribe: greg Found Scribe: kford Inferring ScribeNick: kford Found Scribe: kford Inferring ScribeNick: kford Found Scribe: mhakkinen Inferring ScribeNick: mhakkinen Scribes: greg, kford, mhakkinen ScribeNicks: kford, mhakkinen Default Present: +1.512.406.aaaa, +1.512.406.aabb, kford, Simon_Harper, [Microsoft] Present: Jallan Kim Simon_Harper Simon_Harper_(partial day) greg jeanne kford mhakkinen Regrets: Patrick_Lauke Simon_Harper Found Date: 25 Feb 2010 Guessing minutes URL: http://www.w3.org/2010/02/25-ua-minutes.html People with action items: hakkinen ja jallan jeanne js kim kimberly kp mark markku mhakkinen WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]