User Agent Accessibility Guidelines Working Group Teleconference -- 10 May 2012

<trackbot> Date: 10 May 2012

<JAllan> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0040.html,

<JAllan> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0042.html

Glossary - Viewports

<Jan> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0064.html

<scribe> Scribe: kford

Jan going to go over glossary definitions.

Jan reads his changes.

<jeanne> +1 very good

<sharper> +1

JA: I like any objections or comments.

None heard.

<JAllan> VIEW: A user interface function that lets users interact with web content. UAAG 2.0 recognizes a variety of approaches to presenting the content in a view, such as:

<JAllan> 1. rendered views: Views in which content is presented such that it is rendered, played or executed. There are several sub-types:

<JAllan> a) In conventionally rendered views the content is rendered, played or executed according to the web content technology specification. This is the default view of most user agents.

<JAllan> b) In unconventionally rendered views the content is rendered quite differently than specified in the technology specification (e.g., rendering an audio file as a graphical wavefront); or

<JAllan> 2. source views: Views in which the web content is presented without being rendered, played or executed. The source view may be plain text (i.e., "View Source") or it may include some other organization (e.g., presenting the markup in a tree).

<JAllan> 3. outline views: Views in which only a subset of the rendered content is presented, usually composed of labels or placeholders for important structural elements. The important structural elements will depend on the web content technology, but may include headings, table captions, and content sections.

<JAllan> Note: Views can be visual, audio, or tactile.

<JAllan> VIEWPORT (ONSCREEN VIEWPORT)

<JAllan> The part of an onscreen view that the user agent is currently presenting onscreen to the user, such that the user can attend to any part of it without further action (e.g. scrolling). There may be multiple viewports on to the same view (e.g. when a split-screen is used to present the top and bottom of a document simultaneously) and viewports may be nested (e.g. a scrolling frame located...

<JAllan> ...within a larger document). When the viewport is smaller in extent than the content it is presenting, user agents typically provide mechanisms to bring the occluded content into the viewport (e.g., scrollbars).

Resolved: Accept viewport definitions above.

Resolution: Accept viewport definition from above.

<JAllan> close Action-727

<trackbot> ACTION-727 Write glossary item for top-level viewport (that it is the top rendered content viewport) closed

Action-722 Access to Relationships

Access to relationships

<JAllan> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0029.html

<JAllan> 1.10.3 Configure Elements for Outline View: The user can configure the

<JAllan> set of important elements for the outline view, including by element

<JAllan> type (e.g. headers). (Level AAA) [Under GL 1.10 Alternative View]

<JAllan> 2.5.7 Configure Elements for Structural Navigation: The user can

<JAllan> configure the sets of important elements (including element types) for

<JAllan> structured navigation and hierarchical/outline view. (Level AAA)

<JAllan> [Under GL 2.5 Structural Navigation]

<JAllan> Proposal: remove 1.10.3, merge IER for 1.10.3 and 2.5.7

<Jan> What are "decentralised extended elements"?

<Jan> Also, I agree with folding 1.10.3 into 2.5.7.

<JAllan> Intent of Success Criterion 2.5.7 :

<JAllan> Sometimes authors will visually convey relationships between elements

<JAllan> by spatially grouping them, by giving them the same coloration or

<JAllan> background, and so forth. Users may not be able to perceive those

<JAllan> attributes, such as when using a screen reader, or when strong

<JAllan> magnification makes it difficult to make a mental model of the screen

<JAllan> layout. In those cases the user agent can assist by providing a view

<JAllan> of the data that groups elements that that user agent perceives as

<JAllan> implying relationships.

<JAllan> Often the user agent will choose by default the elements it considers

<JAllan> important for structured navigation, however these may not be relevant

<JAllan> in all circumstances. It may be that the user wishes to navigate via

<JAllan> informal mechanisms such as microformats, decentralised extended

<JAllan> elements, or via a particular styling which is used to convey a

<JAllan> structure in the visual navigation, but which does not exist in the

<JAllan> element hierarchy.

<JAllan> Examples of Success Criterion 2.5.7 :

<JAllan> Fred is blind and wishes to navigate through the menu structure

<JAllan> using the Tab key, however the menu is a set of nested list elements

<JAllan> with a particular HTML class attribute denoting the menu-submenu

<JAllan> relationship. Because Fred's user agent allows him to configure

<JAllan> important elements he can explicitly include the class name as an

<JAllan> important element for navigation. He then assigns a keyboard shortcut

<JAllan> to navigate to the next element with the same class name as the

<JAllan> element that has the focus.

<JAllan> Jane uses a mobile device (and is often situationally impaired) and

<JAllan> often encounters tables laid out using floating DIV elements with

<JAllan> specific class names denoting the visual styling. In this case Jane

<JAllan> cannot use the cursor keys to move around these tabular layouts having

<JAllan> instead to use the tab key to move sequentially left-to-right

<JAllan> top-to-bottom. Jane's browser allows her to configure important

<JAllan> elements and so she can pick out the classes associated with thes

<JAllan> element, and therefore use the cursor key to move logically through

<JAllan> columns or rows.

<JAllan> Resolution: use the following for IER for 2.5.7, delete all of 1.10.3