- From: Jeanne Spellman <jeanne@w3.org>
- Date: Fri, 13 Jan 2012 19:49:25 -0500
- To: Kelly Ford <Kelly.Ford@microsoft.com>
- CC: WAI-ua <w3c-wai-ua@w3.org>
Note: this was NOT an official working group meeting, but rather a subgroup working together to draft proposals. No formal decisions were made. On 1/13/2012 4:36 PM, Kelly Ford wrote: > [W3C]<http://www.w3.org/> > > - DRAFT - > User Agent Accessibility Guidelines Working Group Teleconference > 13 Jan 2012 > > See also: IRC log<http://www.w3.org/2012/01/13-ua-irc> > > Attendees > Present > +1.425.883.aaaa, kford, Greg_Lowney, Jeanne, Kim_Patch, Wayne > Regrets > Chair > SV_MEETING_CHAIR > Scribe > Greg > Contents > > * Topics<http://www.w3.org/2012/01/13-ua-minutes.html#agenda> > * 2.11.7<http://www.w3.org/2012/01/13-ua-minutes.html#item01> > * 2.11.8<http://www.w3.org/2012/01/13-ua-minutes.html#item02> > * 2.11.9<http://www.w3.org/2012/01/13-ua-minutes.html#item03> > * 2.11.11<http://www.w3.org/2012/01/13-ua-minutes.html#item04> > * 2.11.12<http://www.w3.org/2012/01/13-ua-minutes.html#item05> > * Kim's Summarys<http://www.w3.org/2012/01/13-ua-minutes.html#item06> > * Wayne's proposal for 2.5<http://www.w3.org/2012/01/13-ua-minutes.html#item07> > * Summary's<http://www.w3.org/2012/01/13-ua-minutes.html#item08> > * 5.3.1<http://www.w3.org/2012/01/13-ua-minutes.html#item09> > * 2.3.x<http://www.w3.org/2012/01/13-ua-minutes.html#item10> > * Summary of Action Items<http://www.w3.org/2012/01/13-ua-minutes.html#ActionSummary> > > ________________________________ > > <trackbot> Date: 13 January 2012 > > <mhakkinen> i am on an competing concall... no end in sight. I will be here on irc. > > <jeanne> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012JanMar/0011.html > > <jeanne> http://www.w3.org/WAI/UA/2011/ED-UAAG20-20111227/#gl-store-prefs > > <jeanne> http://www.w3.org/WAI/UA/2011/ED-IMPLEMENTING-UAAG20-20111227/#gl-store-prefs > > <jeanne> Mark, there is an Editor's note in the Media section that says - @@ Editors' Note: If an author uses windows media player inside the video element, the browser needs to map its native controls to the embedded wmp controls, and provide access to all the controls. @@ -- Is this something you remember? Do you want to do anything with it, or should we let it go. > > <mhakkinen> just a sec. > > <mhakkinen> I think we should let it go at this point. > > <jeanne> excellent, I agree. > > <KimPatch> Sorry for the late entry -- is there a different conference code for the call? > > 2.7.2 Persistent Accessibility Settings: User agent accessibility preference settings persist between sessions. (Level A) > > * Examples of Success Criterion 2.7.2 : > > o Lynn has moderately low vision, and sets the default zoom level, font size, and colors to make pages easier for her to read. Because those settings are persistent, she doesn't have to manually restore her settings every time she starts the browser. > > o Brian has to adjust some settings in his browser to make it fully compatible with his speech input system. It's difficult for him to get it set up, since he can't fully operate the browser until it's done, so once it's configured this way he relies on it staying in that configuration even if he upgrades the browser, restarts his system and so forth. > > 2.7.3 Restore all to default: The user can restore all preference settings to default values. (Level A) > > * Examples of Success Criterion 2.7.3 : > > o Ron accidentally changes a browser setting that makes his browser incompatible with his screen reader, preventing him from changing it back. He instead restarts his browser using a command line option that starts it in the default configuration, which he's able to use, and from there he can change the setting that caused him problems. > > 2.7.4 Multiple Sets of Preference Settings: The user can save and retrieve multiple sets of user agent preference settings. (Level AA) > > * Examples of Success Criterion 2.7.4 : > > o When Hiroki is carrying his tablet computer he operates it with the built-in touchscreen, but when at his desk he links it to a Bluetooth keyboard and mouse, and redirects the display to a full-size computer monitor. The browser allows him to quickly switch between two completely different configurations for these different environments. > > o Davy has moderately low vision and prefers to adjust the contrast of media differently during the day than at night. Because this requires a number of different steps, for different types of media and aspects of the browser's display, he has two user profiles, one for each environment. > > o Aaron usually uses a keyboard and mouse, but when his repetitive strain injury is bothering him he prefers to use the mouse and avoid using the keyboard as much as possible. At those times he users his browser's user preference profiles to load a different configuration that's optimized for the mouse, including custom toolbars that make most of the commands he uses available as toolbar... > > scribe: buttons. > > <kford> Sample text for 3.3.3 and 3.3.4 > > <kford> 3.3.3 > > <kford> Martha goes to an app store on her computer and notices that an update for the web browser she uses is available. She installs it and finds a welcome page talking about the new features in this release when she launches the updated version of the browser. One of the links on that page says "What's new For Accessibility". following this link Martha reads about the accessibility improvements adde > > <kford> d and discovers this update had added a feature allowing her to have tooltips displayed for elements when she is using caret browsing. the text says, "In this version, we added the ability to display tooltips on elements with a title attribute when using the keyboard. With caret browsing turned on simply arrow onto an element with a title and the tooltip will remain visible while the caret... > > <kford> ...is within the element." > > <kford> 3.3.4 > > <kford> Bob downloads a new web browser on his mobile phone. he's never used this software before and also uses a screen reader that is part of his phone's operating system. He opens a help option for the web browser and finds an accessibility section that gives details on the various accessibility features of the browser such as screen layout, interaction with his screen reader and a list of... > > <kford> ...supported touch gestures. > 2.11.7 > > <jeanne> Jared has a print disability which makes it laborious to read text. He is watching a technical training video which will display section objectives or summary questions as text. When the text flashes by too quickly for him to read, he presses a key command to skip back an increment so he can read the text, or pause the video if more time is required. > > <jeanne> ____ has difficulty with bright or flashing video. When she encounters a flashing transition in a video, she quickly presses a key command to forward the video past the flashing, then carefully uses the slider to adjust the video back to the start of the next section avoiding the flashing material. > 2.11.8 > > <jeanne> Marka is blind and is listening to a video of an hour-long lecture. The section she is in has some complex material that builds on material from an earlier section. While a sighted user could pause the video and move the slider back until she recognized visually distinct content from the section she wanted, Marka uses a control to skip back section by section until she finds the material she > > <jeanne> wants to review. When she is finished, Marka uses the control to move forward section by section until she reaches the original topic. > 2.11.9 > > <jeanne> Marka is listening to a video of a lecture. The professor is demonstrating a chemistry experiment and is not speaking during a key part. Since she cannot see what the professor is demonstrating, Marka brings up a menu of the available tracks and discovers that there is a audio description track avaialbe. Marka selects the description track, rewinds a few minutes, and listens to the description > > <jeanne> of the experiment. > > <jeanne> Gorges is deaf, and enjoys current run movies. He subscribes to a web service that streams major popular movies. While he speaks english, a certain movie uses a slang that he doesn't understand. He pauses the movie, selects a menu of caption tracks and finds a Spanish caption track. He then watches the rest of the movie with Spanish captioning. > 2.11.11 > > <jeanne> _______ has low vision and works in a noisy environment that makes it difficult to listen to instructional videos. When he enlarges the text of the captions to a viewable size, they block most of the video image. ____ selects an option that displays the caption track in a separate window, which he positions below the video image so they captions do not block the video image. > 2.11.12 > > <jeanne> ______ has low vision that requires a higher contrast to discern the image. When _____ is watching an instructional video, he selects a menu that allows him to increase the contrast of the video, to make it easier for him to see the important content. > > <jeanne> _____ has photoepilepsy and is watching an amateur video taken on a sunny day near the water. Concerned that the video may contain flashing that could trigger a seizure, _____ selects a menu of video controls that allow her to reduce the brightness and contrast of the video. While some of the detail is lost, ______ can safely watch the video. > > <KimPatch> 2.10 Summary > Kim's Summarys > > <KimPatch> 2.10 Summary > > <KimPatch> The user can avoid potential seizures with a default browser configuration that does not flash more three times a second above a luminescence or color threshold (2.10.1), or at all (2.10.2). > > <KimPatch> 2.11 Summary > > <KimPatch> The user can control background images (2.11.1), render and control placeholders for time-based media and executable content (2.11.2, 2.11.3, 2.11.4), adjust playback of prerecorded time-based media (2.11.5), control time-based media and animation (2.11.6), navigate time-based media by time (2.11.7) or semantics (2.11.8), specify time-based media tracks (2.11.9), scale and position alternative med > > <KimPatch> ia tracks (2.11.11), and adjust contrast and brightness of visual time-based media (2.11.12). > > <kford> Updated version, see last sentence of first example. > > <kford> 3.3.3 > > <kford> Martha goes to an app store on her computer and notices that an update for the web browser she uses is available. She installs it and finds a welcome page talking about the new features in this release when she launches the updated version of the browser. One of the links on that page says "What's new For Accessibility". following this link Martha reads about the accessibility improvements adde > > <kford> d and discovers this update had added a feature allowing her to have tooltips displayed for elements when she is using caret browsing. the text says, "In this version, we added the ability to display tooltips on elements with a title attribute when using the keyboard. With caret browsing turned on simply arrow onto an element with a title and the tooltip will remain visible while the caret... > > <kford> ...is within the element." The text also informs Martha that this feature is off by default and that she should go to accessibility settings to turn it on. > > <kford> 3.3.4 > > <kford> Bob downloads a new web browser on his mobile phone. he's never used this software before and also uses a screen reader that is part of his phone's operating system. He opens a help option for the web browser and finds an accessibility section that gives details on the various accessibility features of the browser such as screen layout, interaction with his screen reader and a list of... > > <kford> ...supported touch gestures. > > <KimPatch> The user can avoid potential seizures with a default browser configuration that does not flash more three times a second above a luminescence or color threshold (2.10.1), or does not flash at all (2.10.2). > > <KimPatch> The user can control background images (2.11.1), render and control placeholders for time-based media and executable content (2.11.2, 2.11.3, 2.11.4), adjust playback of prerecorded time-based media (2.11.5), control time-based media and animation (2.11.6), navigate time-based media by time (2.11.7) or semantics (2.11.8), specify time-based media tracks (2.11.9), scale and position alternative med > > <KimPatch> ia tracks (2.11.11), and adjust contrast and brightness of visual time-based media (2.11.12). > > Maybe "...adjust the playback rate of (2.11.5) and stop/pause/resume (2.11.6) media and animation..." > > <KimPatch> 2.10 > > <KimPatch> The user can avoid potential seizures with a default browser configuration that does not flash more than three times a second above a luminescence or color threshold (2.10.1), or does not flash at all (2.10.2). > > <KimPatch> 2.11 > > <KimPatch> The user can control background images (2.11.1), render and control placeholders for time-based media and executable content (2.11.2, 2.11.3, 2.11.4), adjust playback of prerecorded time-based media (2.11.5), control (2.11.6), navigate, (2.11.7) and specify tracks for time-based media (2.11.9), scale and position alternative media tracks (2.11.11), and adjust contrast and brightness of... > > <KimPatch> ...visual time-based media (2.11.12). > > "The user can prevent types of flashing that commonly cause seizures (2.10.1) or flashing altogether (2.10.2)" > Wayne's proposal for 2.5 > > <Wayne> 1.11.1 Access Relationships: > > <Wayne> The user can access explicitly-defined relationships based on the > > <Wayne> user's position in content (e.g. show form control's label, show > > <Wayne> label's form control, show a cell's table headers). (Level A) > > <Wayne> 2.5.3 Location in Hierarchy > > <Wayne> The user can view the path of nodes leading from the root of any > > <Wayne> content hierarchy in which the structure and semantics are implied by > > <Wayne> presentation, as opposed to an explicit logical structure with defined > > <Wayne> semantics (such as the HTML5 Canvas Element), or as a consequence of > > <Wayne> decentralized-extensibility (such as the HTML5 item / itemprop > > <Wayne> microdata elements), and only if the user agent keeps an internal > > <Wayne> model of the hierarchy that it does not expose via the [DOM] or some > > <Wayne> other accessibility mechanism. (Level A) . > > <Wayne> Jan Richards Substitute 2.5.3 > > <Wayne> The user can view the path of nodes leading from the root to the > > <Wayne> current focussed element. > > <Wayne> 2.5.5 Access to Relationships which Aid Navigation: > > <Wayne> The user can access explicitly-defined relationships based on the > > <Wayne> user's position in content, and the path of nodes leading from the > > <Wayne> root of any content hierarchy to that position. (Level AA) > > <Wayne> Ambiguities: > > <Wayne> What is the difference between 1.11.1 and 2.5.5. Also, what does "the > > <Wayne> root of any content hierarchy to that position" mean? > > <Wayne> 2.5.5 Access to Relationships which Aid Navigation: The user can access explicitly-defined relationships based on the user's position in content, and the path of nodes leading from the root of any content hierarchy to that position. (Level AA) > > <Wayne> Jan Richards Substitute 2.5.3 > > <Wayne> The user can view the path of nodes leading from the root to the current focussed element. > Summary's > > <KimPatch> 2.10 Summary > > <KimPatch> The user can prevent (2.10.1) or avoid (2.10.2) types of flashing that commonly cause seizures. > > <KimPatch> 2.11 Summary > > <KimPatch> The user can control background images (2.11.1); render and control placeholders for time-based media and executable content (2.11.2, 2.11.3, 2.11.4); adjust playback (2.11.5), stop/pause/resume (2.11.6), navigate, (2.11.7) and specify tracks for prerecorded time-based media (2.11.9); scale and position alternative media tracks (2.11.11); and adjust contrast and brightness of visual... > > <KimPatch> ...time-based media (2.11.12). > > <KimPatch> Note: normalize animation and prerecorded time based media in 2.11 sc's > > "The user can prevent flashing in ways that are moderately cautious (2.10.1) or extremely cautious (2.10.2)." > > <kford> Proposed 5.1.1: > > <kford> Note, this is shorter than what is in the document today. > > <kford> the operating system on which a user agent is running, generally has expected conventions around accessibility for areas such as keyboard behavior, support of an accessibility API user interface design, and other standards related to accessibility. The intent of this success criteria is to ensure that user agents comply with the basic accessibility requirmenets on where they are in use. > > <jeanne> Wayne, we are reconvening if you want to join us > > <Wayne> requirements [of the platform in use] > > Uh, oh! 5.1.1 and 5.3.2 seem significantly overlapping... > > 5.1.1 Follow Accessibility Guidelines: Non-web-based user agent user interfaces follow user interface accessibility guidelines for the platform. (Level A) > > 5.3.2 Implement Accessibility Features of platform: Implement and cite in the conformance claim the accessibility features of content and platform technology specifications. Accessibility features are those that are either (Level A)... > > <kford> Updated 5.1.1. > > <kford> the platform on which a user agent is running has expected conventions around accessibility for areas such as keyboard behavior, support of an accessibility API user interface design, and other standards related to accessibility. The intent of this success criteria is to ensure that user agents comply with the basic accessibility requirements on where they are in use. > > Here's our Intent for 5.3.2 Implement Accessibility Features of Platform: > > If browsers and players don't seamlessly conform to platform accessibility features, then users can't easily take advantage of those features. Software that has versions for different platforms, may have to handle accessibility differently on different platforms or operating systems. In order to show that you have implemented the accessibility features of the platform correctly, these... > > scribe: features are identified in the conformance claim. > > The user should be able to easily discover detailed information about the user agent's adherence to accessibility standards, including those related to content such as MSAA or JAA, and third-party standards such as ISO 9241-171, and should be able to do so without installing and testing the accessibility features. > > We plan to delete 5.1, and use Kelly's new Intent paragraph for 5.3.2. > 5.3.1 > > 5.3.1 Implement accessibility features of content specs: Implement and cite in the conformance claim the accessibility features of content specifications. Accessibility features are those that are either (Level A) > > * identified as such in the specification or > > * allow authors to satisfy a requirement of WCAG. > > Intent of Success Criterion 5.3.1: > > Accessibility features are included in content specs to provide features required by users with various disabilities. If those features are not fully supported by the user agent, users can't easily take advantage of those features. The user should be able to easily discover detailed information about the user agent's adherence to accessibility standards, including those related to content... > > scribe: such as HTML and WAI-ARIA, and should be able to do so without installing and testing the accessibility features. This will allow them to make informed decisions about whether or not to they will be able to use, and therefore should install, a new product or version of that product. > > <scribe> New Example: > > o Jordy uses a web site which uses WAI-ARIA to identify the functions of custom controls. If he were to use a web browser that didn't support this aspect of WAI-ARIA and expose that information to assistive technology, the web site would be unusable with his web browser. Therefore Jordy needs to choose a web browser that he knows fully supports WAI-ARIA, and he determines this by reading... > > scribe: product documentation and UAAG conformance claims posted on the Web. > > <jeanne> https://www.w3.org/2002/09/wbs/36791/20120113/ > 2.3.x > > <Wayne> 2.3.x Discover navigation and activation keystrokes (former 2.5.1): The user can discover direct navigation and activation keystrokes both programmatically and via perceivable labels. (Level A) > > <Wayne> Intent: This SC reduces the cognigative load for keyboard interface users. Navigation by keyboard interface may vary by platform, user agent and assistive technology. Taken as a whole this creates hardship for keyboard interface users. The user of the keyboard interface needs perceivable labels to learn and be and operate navigation effectively. > > <Wayne> To be written > > <kford> -rrsagent, make minutes > > Summary of Action Items > -- _______________________________ Jeanne Spellman W3C Web Accessibility Initiative jeanne@w3.org
Received on Saturday, 14 January 2012 00:49:33 UTC