W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > July to September 2010

Minutes of UAWG writers meeting 2 August 2010

From: Jeanne Spellman <jeanne@w3.org>
Date: Mon, 02 Aug 2010 18:12:58 -0400
Message-ID: <4C5742EA.2@w3.org>
To: UAWG <w3c-wai-ua@w3.org>
Minutes:
http://www.w3.org/2010/08/02-ua-minutes

IRC Log:
http://www.w3.org/2010/08/02-ua-irc

Text of Minutes:

    [1]W3C

       [1] http://www.w3.org/

                                - DRAFT -

    User Agent Accessibility Guidelines Working Group Teleconference

02 Aug 2010

    See also: [2]IRC log

       [2] http://www.w3.org/2010/08/02-ua-irc

Attendees

    Present
           Jim, Greg, Kelly, Kim, Jeanne

    Regrets
    Chair
           jim, kelly

    Scribe
           jeanne

Contents

      * [3]Topics
          1. [4]EOWG Comments on Working Draft
          2. [5]1.1.1
          3. [6]1.4.1 & 2
          4. [7]Guideline 1.2 Ensure that Web-based functionality is
             accessible. [Implementing 1.2]
          5. [8]3.11
          6. [9]3.1.4 Rendering Alternative (Enhanced): Provide the user
             with the global option to configure a cascade of types of
             alternatives to render by default, in case a preferred type
             is unavailable. If the alternative content has a different
             height or width, then the user agent will reflow the
             viewport. (Level AA)
          7. [10]3.11 Additions
          8. [11]3.1.3.1
          9. [12]3.13.1
      * [13]Summary of Action Items
      _________________________________________________________

    <trackbot> Date: 02 August 2010

    <scribe> Meeting: UAWG Writers' Group

    <scribe> scribe: jeanne

    <kford> Hey all. Kind of funky.

    Comments recieved from EOWG

    [14]http://lists.w3.org/Archives/Public/public-uaag2-comments/2010Ju
    l/0000.html

      [14] 
http://lists.w3.org/Archives/Public/public-uaag2-comments/2010Jul/0000.html

EOWG Comments on Working Draft

    [15]http://lists.w3.org/Archives/Public/public-uaag2-comments/2010Ju
    l/0000.html

      [15] 
http://lists.w3.org/Archives/Public/public-uaag2-comments/2010Jul/0000.html

    [16]http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100802/

      [16] http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100802/

    [17]http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100802/MasterUAAG20100
    802.html

      [17] 
http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100802/MasterUAAG20100802.html

    jim, KIm and I are talking about adding references to the operating
    system accessibility guides. Does that fit in with what you are
    doing?

    <AllanJ> yes.

    <AllanJ> here is the list for accessibility tools (high contrast,
    etc) and APIs

    <AllanJ> Related Resources for Success Criterion 1.1.1:

    <AllanJ>
    [18]http://www.microsoft.com/windowsxp/using/accessibility/default.m
    spx

      [18] 
http://www.microsoft.com/windowsxp/using/accessibility/default.mspx

    <AllanJ> [19]http://www.apple.com/accessibility/

      [19] http://www.apple.com/accessibility/

    <AllanJ>
    [20]http://www.linux.org/docs/ldp/howto/Accessibility-HOWTO/linuxos.
    html

      [20] 
http://www.linux.org/docs/ldp/howto/Accessibility-HOWTO/linuxos.html

    <AllanJ>
    [21]http://www.linuxfoundation.org/collaborate/workgroups/accessibil
    ity/iaccessible2

      [21] 
http://www.linuxfoundation.org/collaborate/workgroups/accessibility/iaccessible2

    <AllanJ> [22]http://developer.apple.com/ue/accessibility/

      [22] http://developer.apple.com/ue/accessibility/

    <AllanJ>
    [23]http://msdn.microsoft.com/en-us/library/dd373592%28VS.85%29.aspx

      [23] http://msdn.microsoft.com/en-us/library/dd373592%28VS.85%29.aspx

    <AllanJ> [24]http://msdn.microsoft.com/en-us/windows/ee815673.aspx

      [24] http://msdn.microsoft.com/en-us/windows/ee815673.aspx

    <kford> How are folks doing on time?

    [writing assignments]

1.1.1

    <AllanJ> Intent of Success Criterion 1.1.1:

    <AllanJ> The user should be able to easily discover detailed
    information about the user agent’s adherence to accessibility
    standards of the operating environment or adherence to external
    accessibility requirements without installing and testing the
    accessibility features.

    <AllanJ> Examples of Success Criterion 1.1.1 :

    <AllanJ> User agent X lists the platform accessibility tools (high
    contrast, show sounds, sticky keys, etc) supported. Additionally,
    the user agent lists all of the platform accessibility APIs or other
    APIs that are supported.

    <AllanJ> “Google Chrome supports the Windows Accessibility API
    (MSAA) to display accessibility information and events for its
    features and web content.
    [25]http://www.google.com/support/chrome/bin/answer.py?hl=en&answer=
    96831”

      [25] 
http://www.google.com/support/chrome/bin/answer.py?hl=en&answer=96831

    <AllanJ> Related Resources for Success Criterion 1.1.1:

    <AllanJ>
    [26]http://www.microsoft.com/windowsxp/using/accessibility/default.m
    spx

      [26] 
http://www.microsoft.com/windowsxp/using/accessibility/default.mspx

    <AllanJ> [27]http://www.apple.com/accessibility/

      [27] http://www.apple.com/accessibility/

    <AllanJ>
    [28]http://www.linux.org/docs/ldp/howto/Accessibility-HOWTO/linuxos.
    html

      [28] 
http://www.linux.org/docs/ldp/howto/Accessibility-HOWTO/linuxos.html

    <AllanJ>
    [29]http://www.linuxfoundation.org/collaborate/workgroups/accessibil
    ity/iaccessible2

      [29] 
http://www.linuxfoundation.org/collaborate/workgroups/accessibility/iaccessible2

    <AllanJ> [30]http://developer.apple.com/ue/accessibility/

      [30] http://developer.apple.com/ue/accessibility/

    <AllanJ>
    [31]http://msdn.microsoft.com/en-us/library/dd373592%28VS.85%29.aspx

      [31] http://msdn.microsoft.com/en-us/library/dd373592%28VS.85%29.aspx

    <AllanJ> [32]http://msdn.microsoft.com/en-us/windows/ee815673.aspx

      [32] http://msdn.microsoft.com/en-us/windows/ee815673.aspx

    <AllanJ> 1.1.1 Non-Web-Based Accessible (Level A): Non-Web-based
    user agent user interfaces comply with and cite the "Level A"
    requirements of standards or operating environment conventions that
    benefit accessibility. The "Level A" requirements are those that are
    functionally equivalent to WCAG Level A success criteria. (Level A)

    <AllanJ> 1.2, 1.2, 1.3 seems to over lap with 5.3

    <AllanJ> there is an existing proposal to renumber GL1. Also to move
    GL 1 to some other place in the document

    [33]http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100802/MasterUAAG20100
    802.html

      [33] 
http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100802/MasterUAAG20100802.html

    <greg> The user should be able to easily discover detailed
    information about the user agent’s adherence to accessibility
    standards of the operating environment or adherence to external
    accessibility requirements, and should be able to do so without
    installing and testing the accessibility features.

    <kford>
    [34]http://www.ddplus.com/index.php?module=modRDS&op=menu&category=&
    subcategory=&restaurant=90

      [34] 
http://www.ddplus.com/index.php?module=modRDS&op=menu&category=&subcategory=&restaurant=90

    <AllanJ> discussion of combining 1.1 and 1.2 with 1.3 ... need to
    put on a survey

    <AllanJ> also, discussion of moving relevant parts of GL 1 to 5.3

    <kford> we just lost you.

    We lost you..

    No video or sound from Microsoft.

    <kford> We areinvestigating.

    <kford> We areinvestigating.

    want us to call you?

    <kford> hold on, we going to try calling again

    survey: [35]http://www.w3.org/2002/09/wbs/36791/20100802/

      [35] http://www.w3.org/2002/09/wbs/36791/20100802/

    <greg> Suggest in 3.1.3 changing "Implement and cite in the
    conformance claim the accessibility features of a technology
    specification." to end with "of content and platform technology
    specifications".

    <greg> "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 HTML and
    WAI-ARIA, platform standards such as MSAA or JAA, and third-party
    standards such as ISO 9241-171."

    <greg> 1.4.1 Follow Specifications: Render content according to the
    technology specification. This includes any accessibility features
    of the technology (see Guideline 1.3). (Level A)

1.4.1 & 2

    1.4.1 Follow Specifications: Render content according to the
    technology specification. This includes any accessibility features
    of the technology (see Guideline 1.3). (Level A)

    <greg> Intent of Success Criterion 1.4.1:

    <greg> • End users and assistive technology products assume that
    content will be rendered in a predictable fashion. This success
    criterion ensures that user agents provide this level of
    predictability.

    <greg> • Note: It may be necessary to ignore aspects of the
    technology specification where they would actually harm, rather than
    improve, overall accessibility. In these cases user agent developers
    are encouraged to deviate from those aspects of the standard, and
    document the decision in their conformance claim. For example, the
    CSS spec says generated content should not appear in the DOM, so
    it's...

    <greg> ...not exposed to assistive technology and cannot be made
    accessible to blind users.

    <greg> * Examples of Success Criterion 1.4.1:

    <greg> • A user agent implements the WAI-ARIA (Accessible Rich
    Internet Applications) standard, and the developer follows the
    "Implementing ARIA" document by mapping ARIA roles and events to the
    supported platform accessibility infrastructure (MSAA, UIA, ____,
    etc.). This allows a screen reader that supports the platform
    infrastructure to correctly support ARIA in the user agent.

    <greg> • An organization creates an optional style sheet that
    enlarges fonts and adapts all colors for maximum contrast. They can
    be confident that when their Web site uses this style sheet it will
    work with any browser because those browsers have implemented CSS
    according to the CSS specification.

    <greg> For example, the CSS spec says generated content should not
    appear in the DOM. That would mean that generated content would not
    be exposed to assistive technology, and could not be made accessible
    to blind users, so user agents should instead expose the generated
    content through the DOM, and document their decision to ignore that
    aspect of the specification.

    <greg> For example, the CSS spec says generated content should not
    appear in the DOM, which may mean that generated content would not
    be exposed to assistive technology and thus may not be accessible to
    blind users. Therefore user agents should instead expose the
    generated content through the DOM, and document their decision to
    ignore that aspect of the specification.

    <greg> For example, the CSS spec says generated content should not
    appear in the DOM, which may mean that generated content would not
    be exposed to assistive technology and thus may not be accessible to
    blind users. User agents should instead expose the generated content
    through the DOM, and document their decision to ignore that aspect
    of the specification.

    <AllanJ> www.w3.org/TR/css3-animations/

    <AllanJ> www.w3.org/TR/css3-selectors/

    <greg> 1.4.2 Handle Unrendered Technologies: If the user agent does
    not render a technology, it allows the user to choose a way to
    handle content in that technology (e.g., by launching another
    application or by saving it to disk). (Level A)

    <AllanJ> www.w3.org/TR/css3-content/ - generated content is
    discussed here

    <AllanJ> kf: may need a new SC

    <greg> * Intent of Success Criterion 1.4.2:

    <greg> • Users who have disabilities may have fewer options in terms
    of how they access the information. Information is made available in
    a variety of fashions on the Internet, and at times a specific
    format may be the only way in which information is available. If the
    user agent cannot render that format it needs to let the user access
    that content through alternate means, such as invoking a...

    <greg> ...third-party renderer or saving the file to the user's hard
    drive.

    <greg> * Examples of Success Criterion 1.4.2 :

    <greg> • Tracy has low vision and finds it much more convenient to
    access her bank statement electronically than on paper, even though
    the electronic version is in a TIFF image, a format that her browser
    cannot render. In this case, the browser lets her save the image to
    her hard drive so she can open it in another program.

    <AllanJ> new SC if the browser does render something but does not do
    a good job of it

    <greg> The new SC Kelly was referring to was the idea that
    everything we say about providing alternative access to unsupported
    file types ALSO applies equally well to file types that are
    supported by the browser but not in a very accessible fashion. For
    example, the browser may support the VIDEO tag but add inaccessible
    play and pause controls, or a limited set of controls that don't
    include...

    <greg> ...advanced navigation options. In that case the user should
    have the ability to play the video in a third-party player that
    provides better or more sophisticated controls.

    <greg> That would not require the browser to host the third-party
    player, as it could launch the third-party application as a separate
    process and window, etc.

Guideline 1.2 Ensure that Web-based functionality is accessible.
[Implementing 1.2]

    <AllanJ> 1.2.1 Web-Based Accessible (Level A): User agent user
    interfaces that are rendered using Web standard technologies conform
    to WCAG Level "A". (Level A)

    <AllanJ> • Intent of Success Criterion 1.2.1:

    <AllanJ> Media players, other page elements that use the <object> or
    <embed> tags function as user agents independent of the hosting user
    agent. In compound documents, each separate part of the code
    (mathml, svg, etc), may function independently (including have a
    separate Document Object Model) of the hosting user agent. As such,
    the non-html code may have a unique parser. The parsed information
    may...

    <AllanJ> ...or may not be passed to the hosting user agent or the
    platform accessibility APIs. The user should be able to easily
    discover detailed information about the user agent’s adherence to
    accessibility standards of the hosting operating environment or
    adherence to external accessibility requirements without installing
    and testing the accessibility features.

    <AllanJ> • Examples of Success Criterion 1.2.1 :

    <AllanJ> Media player X lists the features of the platform
    accessibility tools (high contrast, show sounds, sticky keys, etc)
    supported within the embedded environment. Additionally, the user
    agent lists all of the platform accessibility APIs or other APIs
    that are supported.

    <AllanJ> • Related Resources for Success Criterion 1.2.1:

    <AllanJ>
    [36]http://www.adobe.com/accessibility/products/flashplayer/overview
    .html

      [36] 
http://www.adobe.com/accessibility/products/flashplayer/overview.html

    <AllanJ>
    [37]http://www.adobe.com/accessibility/products/compliance/#flashpla
    yer10

      [37] 
http://www.adobe.com/accessibility/products/compliance/#flashplayer10

    <AllanJ> [38]http://www.adobe.com/accessibility/products/compliance/

      [38] http://www.adobe.com/accessibility/products/compliance/

    <AllanJ> [39]http://webaim.org/techniques/captions/mediaplayers/

      [39] http://webaim.org/techniques/captions/mediaplayers/

    <AllanJ> [40]http://www.w3.org/2004/CDF/

      [40] http://www.w3.org/2004/CDF/

    <AllanJ> the above is for all of SC 1.2

    <greg> First draft:

    <greg> 1.4.3 Alternative content handlers: The user has the ability
    to select content elements and have them rendered in alternative
    viewers.

    <greg> Intent:

    <greg> When accessing media content on the Web, users with
    disabilities sometimes find they have a richer or more accessible
    experience in a third-party application than using their browser's
    build-in facilities. In these cases they want to be able to navigate
    to content in their browser, then save that content to their disk or
    launch it in a third-party application.

    <greg> Example:

    <greg> A browser support the VIDEO tag and adds its own play and
    pause controls, but the user prefers to view the video content in a
    third-party application that provides much more sophisticated
    navigation controls such as bookmarks, skip-forward and backwards,
    and the ability to speed playback without increasing pitch of the
    audio track.

    <greg> A browser support the VIDEO tag and adds its own play and
    pause controls, but George prefers to view the video content in a
    third-party application that provides much more sophisticated
    navigation controls such as bookmarks, skip-forward and backwards,
    and the ability to speed playback without increasing pitch of the
    audio track. In the browser, he right-clicks on the video to display
    a...

    <greg> ...context menu, and from that chooses "Open in…", and then
    chooses his preferred video player. The browser saves the video to a
    temporary location on the user's disks, then launches the player to
    show that file.

    <greg> Or: A browser support the VIDEO tag and adds its own play and
    pause controls, but George prefers to view the video content in a
    third-party application that provides much more sophisticated
    navigation controls such as bookmarks, skip-forward and backwards,
    and the ability to speed playback without increasing pitch of the
    audio track. In the browser, he right-clicks on the video to display
    a...

    <greg> ...context menu, and from that chooses "Open in…", and then
    chooses his preferred video player. The browser launches the player
    to show that video file in the browser's cache folder.

    <greg> The browser saves the video to a temporary location on the
    user's disks (or uses one already in its cache folder), then
    launches the player to show that file.

    <greg> In the case of streaming video that cannot be saved to disk,
    the browser launches the external viewer passing it the URL to the
    online video.

    Jim is working on 3.1.3

    <AllanJ> 3.1.3 Browse and Render: The user can browse the
    alternatives, switch between them, and render them according to the
    following (Level A):

    <AllanJ> a. synchronized alternatives for time-based media (e.g.,
    captions, audio descriptions, sign language) can be rendered at the
    same time as their associated audio tracks and visual tracks, and

    <AllanJ> b. non-synchronized alternatives (e.g., short text
    alternatives, long descriptions) can be rendered as replacements for
    the original rendered content.

    <AllanJ> a. Intent of Success Criterion 3.1.3:

    <AllanJ> a. There are times when a user cannot gain meaningful
    information from a time-based media element. The author may have
    provided synchronized alternatives for the media. The user should be
    able to easily discover the synchronized alternatives provided, and
    have them render synchronously with the default media.

    <AllanJ> b. There are times when a user cannot gain meaningful
    information from a non-time-based media element (images, charts,
    graphs, etc.). The author may have provided alternatives for this.
    The user should be able to easily discover the alternatives
    provided, and have them render in place of the default media.

    <AllanJ> b. Examples of Success Criterion 3.1.3:

    <AllanJ> a. Sam is deaf. He is watching a video on a web page. He
    cannot hear the audio. The author has provided captions for the
    video. The user agent detecting that captions exist, makes the
    caption button visible. The caption button toggles the captions
    on/off.

    <AllanJ> Sue is blind. She is watching a video on a web page. She
    cannot see the action on the screen. The author has provided
    audio-descriptions for the video. The user agent detecting that
    audio-descriptions exist, makes the AD button visible. The button
    toggles the audio-descriptions on/off.

    <AllanJ> b. Mary has a learning disability. She is reading a page
    with many images. The images are distracting. Mary is able to turn
    the images off, and reveal the alternative text (@alt) that the
    author provided. The alternative text is rendered in place of the
    images. Mary has the option of having the size of the image remain
    same or fit the size of the text.

    Topic 3.1.3

    <AllanJ> Some of the images are graphs. She cannot make sense of the
    graphs. The author has provided long descriptions for the graphs.
    Sue toggles the long-discription feature. The browser detects the
    presence of valid @long-descriptions and renders an actionable icon
    inline after an image. Mary can click on the icon, opening the
    long-description for that particular graph.

    <AllanJ> 3.1.3 Browse and Render: The user can browse the
    alternatives, switch between them, and render them according to the
    following (Level A):

    <AllanJ> a. synchronized alternatives for time-based media (e.g.,
    captions, audio descriptions, sign language) can be rendered at the
    same time as their associated audio tracks and visual tracks, and

    <AllanJ> b. non-synchronized alternatives (e.g., short text
    alternatives, long descriptions) can be rendered as replacements for
    the original rendered content.

    <AllanJ> a. Intent of Success Criterion 3.1.3:

    <AllanJ> a. There are times when a user cannot gain meaningful
    information from a time-based media element. The author may have
    provided synchronized alternatives for the media. The user should be
    able to easily discover the synchronized alternatives provided, and
    have them render synchronously with the default media.

    <kford> we lost Bos

    <AllanJ> b. There are times when a user cannot gain meaningful
    information from a non-time-based media element (images, charts,
    graphs, etc.). The author may have provided alternatives for this.
    The user should be able to easily discover the alternatives
    provided, and have them render in place of the default media.

    see above for text

    <AllanJ> b. Examples of Success Criterion 3.1.3:

    <AllanJ> a. Sam is deaf. He is watching a video on a web page. He
    cannot hear the audio. The author has provided captions for the
    video. The user agent detecting that captions exist, makes the
    caption button visible. The caption button toggles the captions
    on/off.

    <AllanJ> Sue is blind. She is watching a video on a web page. She
    cannot see the action on the screen. The author has provided
    audio-descriptions for the video. The user agent detecting that
    audio-descriptions exist, makes the AD button visible. The button
    toggles the audio-descriptions on/off.

    <AllanJ> b. Mary has a learning disability. She is reading a page
    with many images. The images are distracting. Mary is able to turn
    the images off, and reveal the alternative text (@alt) that the
    author provided. The alternative text is rendered in place of the
    images. Mary has the option of having the size of the image remain
    same or fit the size of the text.

    <AllanJ> Some of the images are graphs. She cannot make sense of the
    graphs. The author has provided long descriptions for the graphs.
    Sue toggles the long-discription feature. The browser detects the
    presence of valid @long-descriptions and renders an actionable icon
    inline after an image. Mary can click on the icon, opening the
    long-description for that particular graph.

    <AllanJ> note 1.4.3 above is a new SC.

    <AllanJ> kp: 1.4.3 should be level A

    <AllanJ> kf:it may be easy. worried about too many level A items

    <AllanJ> consensus of group is AA

    <AllanJ> ... for new 1.4.3

    <AllanJ> gl: for technologies that the ua does not support, it must
    provide a way for the user to render using other means.

    <AllanJ> ... for technologies that the ua does support, it may
    provide a way for the user to render using other means.

    <greg> 1.4.3 Alternative handlers for rendered technologies: The
    user has the ability to select content elements and have them
    rendered in alternative viewers. (AA)

    <greg> I guess we'll stick with "1.4.3 Alternative content handlers"

3.11

    <AllanJ> focus definitions:
    [41]http://www.w3.org/2002/09/wbs/36791/DefinitionOfFocus/results

      [41] http://www.w3.org/2002/09/wbs/36791/DefinitionOfFocus/results

    Question: Since the SC are so familiar and the intent is similar,
    how should we approach it? Repeat the same paragraph each time, or
    put the paragraph in once and link to it?

    consensus: link to it. Call it the general intent.

    <AllanJ> focus stuff happened between 4/8/10 and 4/21/a0

    GL: The focus definition needs indenting to make it easier to read.

    KP: 3.11.1 is supposed to be input focus.

    GL: I think it means keyboard input focus.

    <greg> * Input focus (active/inactive)

    <greg> o Keyboard focus (active/inactive)

    <greg> + Cursor (active/inactive) “Visual indicator showing where
    keyboard input will occur”

    <greg> # Focus cursor (active/inactive)

    <greg> # Text cursor (active/inactive)

    <greg> o Pointing device focus (active/inactive)

    <greg> + Pointer

    <AllanJ> Jeanne +1

    <AllanJ> Kelly +1

    <AllanJ> Gregg +1

    <AllanJ> Kim +1

    Jim +1

    <kford> 3.11.1 Content Focus: At least one content focus is provided
    for each viewport (including frames), where enabled elements are
    part of the rendered content. (Level A)

    <kford> Example:

    <kford> A user launches a web browser and navigates to a web page.
    The user starts pressing the tab key and focus begins moving through
    the links on the webpage.

    <kford> 3.11.2s

    <kford> 3.11.2 skipped

    <kford> 3.11.3 User Interface Focus: A user interface focus is
    provided. (Level A)

    <kford> Example:

    <kford> A user agent has several menus, toolbars and other controls.
    As the user presses a key to move to each item on one of the
    toolbars, the fact that this toolbar item is the active control is
    made clear through a focus rectangle. When the user switches to a
    menu, highlighting indicates the active menu element.

    <kford> 3.11.4 Extensions Focusable: The user interface focus can
    navigate within extensions to the user interface. (Level A)

    <kford> Example:

    <kford> A developer creates an extension to a user agent that allows
    the user to add notes about each web page being visited. A user can
    press a key to move focus to the user interface of this extension
    and interact with the funtionality offered by the extension.
    Similarly, the user presses another key to move focus back to the
    main viewpoert forthe user agent.

    <kford> 3.11.5 Hand-Off Focus: The user agent programmatically
    notifies any nested user agent(s) (e.g., plug-ins) when focus moves
    to them. (Level A)

    <kford> Example:

    <kford> A browser plug-in is installed to play a popular media
    format. When the user tabs to the controls for the plug-in, the user
    agent notifies the plug-in to handle keyboard interaction.

    <kford> That's all forme.

3.1.4 Rendering Alternative (Enhanced): Provide the user with the
global option to configure a cascade of types of alternatives to render
by default, in case a preferred type is unavailable. If the alternative
content has a different height or width, then the user agent will
reflow the viewport. (Level AA)

    <AllanJ> • Intent of Success Criterion 3.1.4:

    <AllanJ> For a give piece of non-text content the author may have
    provide one or several alternatives. For example, an image may have
    different versions based on resolution, ‘alt text’ (@alt) or a link
    to a long description (@longdesc). A video may have bandwidth
    alternatives, caption files in different languages, audio
    descriptions in different languages. There may be others. The user
    is able to...

    <AllanJ> ...choose which item(s) to render by default, and specify
    the order of the cascade of alternatives to be rendered if the
    author did not provide a type of alternative.

    <AllanJ> • Examples of Success Criterion 3.1.4:

    <AllanJ> Mary has a learning disability. She finds looking at images
    on a webpage very distracting. Mary would like to see all images
    rendered in the following order. First, for images with long
    descriptions have the long description rendered in place of the
    image. If the long description does not exit, she wants the ‘alt
    text’ to be rendered. If neither is available, Mary wants the file
    name...

    <AllanJ> ...rendered.

    <AllanJ> Added functionality would allow Mary to right click
    (context menu) on an image to list and select the rendering of the
    available alternatives (thumbnail, original size, full screen, low
    resolution, high resolution, alt text, long description, file name)

    <AllanJ> @@where do we put the ability for the user to individually
    pick an image and have the image displayed. It should not have to be
    an all or nothing.

    <AllanJ> Juan is hard of hearing. He wants to always see video on
    the page. Also, Juan would like the Spanish language track used if
    available, along with Spanish captions as a default. If these are
    not available, he wants to see the video with English audio and
    captions. If no captions are available Juan wants the the video and
    English audio.

    <AllanJ> Added functionality would allow Juan to right click
    (context menu) on an video to list and select the rendering of the
    available alternatives (still image, caption languages, audio
    languages, audio-description languages)

3.11 Additions

    <greg> General Intent of Guideline 3.11:

    <greg> Understanding and controlling focus is key to successful
    interaction with a user agent and its content. The overall purpose
    of Guideline 3.11 is to ensure that the user can reliably identify
    the focus location, and use it to navigate through and manipulate
    both the content and user interfaces of the user agent, its plug-ins
    and extensions.

    <greg> 3.11.1 Content Focus: At least one cursor is provided for
    each viewport (including frames), where enabled elements are part of
    the rendered content. (Level A)

    <greg> Intent:

    <greg> • Users need to be able to tell where the keyboard focus is
    in order to navigate or manipulate content; without it, a user
    cannot be sure what effect their next keystroke will have. Cursors
    are the visual indication of this location, and their locations are
    also conveyed to assistive technology for users not relying on sight
    (see success criterion _._._). When the sighted user expects a...

    <greg> ...cursor and does not see one, they can assume that it's in
    a portion of the content that has scrolled outside the visible
    portion of the viewport.

3.1.3.1

3.13.1

    <Kim> 3.13.1 Users who use screen readers need to be able to easily
    discover information about a link in order to properly navigate Web
    content.

    <Kim> Example:

    <Kim> Robert, who uses a screen reader, needs to know whether a
    given link will automatically open in a new page. The browser
    indicates this information so he can discover it before he makes a
    decision to click on a link.

    <Kim> 3.13 Users who use screen readers need to be able to easily
    discover information about a link, including the title of the link,
    whether or not that link is a webpage, PDF etc. and whether the link
    goes to a new page or a different location in the current page, in
    order to navigate Web content more quickly and easily.

    <Kim> Example:

    <Kim> Robert, who uses a screen reader, needs to know whether a
    given link will open a new page or jump to a different place on the
    same page. The browser indicates this information so he can discover
    it before he makes a decision to click on a link.

    <scribe> ACTION: Jeanne to copy proposals 3.1.4, 3.11 general
    intent, 3.11.1 specific intent, 3.11.1,4 & 5 Examples, and 3.13.1
    from minutes of 02-08-2010. Put in the Guidelines Master and the
    Survey for 5 August. [recorded in
    [42]http://www.w3.org/2010/08/02-ua-minutes.html#action01]

    <trackbot> Created ACTION-418 - Copy proposals 3.1.4, 3.11 general
    intent, 3.11.1 specific intent, 3.11.1,4 & 5 Examples, and 3.13.1
    from minutes of 02-08-2010. Put in the Guidelines Master and the
    Survey for 5 August. [on Jeanne Spellman - due 2010-08-09].

Summary of Action Items

    [NEW] ACTION: Jeanne to copy proposals 3.1.4, 3.11 general intent,
    3.11.1 specific intent, 3.11.1,4 & 5 Examples, and 3.13.1 from
    minutes of 02-08-2010. Put in the Guidelines Master and the Survey
    for 5 August. [recorded in
    [43]http://www.w3.org/2010/08/02-ua-minutes.html#action01]

    [End of minutes]
Received on Monday, 2 August 2010 22:13:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 2 August 2010 22:13:08 GMT