Accessibility Minutes 2012 04 16

From MemberWiki

Jump to: navigation, search



  • Jon Gunderson (University of Illinois - Co-Chair)
  • Ann Abbott (IBM)
  • Marc Johlic (IBM)
  • Prasanna Bale (University of Illinois)
  • Nicholas Hoyt (University of Illinois) - Scribe


Landmark Rules and article role vs. article tag

JG: Is it a rule at IBM that all renderable content must be in a landmark? Ann: Yes

Ann: Can use role=region with an ARIA label when one of the predefined landmarks doesn't fit.

Jon: 1st item on the agenda: comments or updates to conceptual model

Ann: Re. article tags, what info are you looking for?

Jon: Common use cases

Jon: Lots of confusion re. how to use ARIA roles vs. certain new HTML 5 tags.

Jon: Primary intended use is for logs, where each response is considered an article.

Nick: What is the definition of article? Difference between ARIA and HTML 5?

Ann: Related to discussion: a section of the page that refers to the composition that forms and independent part of a document, page or site.


Jon: The article element represents a self-contained composition in a document, page, application, or site and that is, in principle, independently distributable or reusable, e.g. in syndication. This could be a forum post, a magazine or newspaper article, a blog entry, a user-submitted comment, an interactive widget or gadget, or any other independent item of content.

Jon: When article elements are nested, the inner article elements represent articles that are in principle related to the contents of the outer article. For instance, a blog entry on a site that accepts user-submitted comments could represent the comments as article elements nested within the article element for the blog entry.

Jon: Author information associated with an article element (q.v. the address element) does not apply to nested article elements.

Ann: IE shows article role as a landmark; Firefox does not.

Ann: Could have been article tag that appeared in IE.

Jon: This will be source of confusion: ARIA "article" has an analogue in HTML 5.

Ann: From Freedom Scientific: IE was showing it as a landmark when seeing an HTML 5 article tag.

Conceptual Model

Nick: Two changes in CM: (1) added rule mapping object and (2) purpose property for accessibility rule.

Nick: Note: Change external requirement id to plural "ids" to accommodate a primary reference and list of related references.

Widget Rules

Jon: Widget rules

Jon: /member/wiki/WCAG_2.0_Principle_3_Understandable_Rules#Requirement_3.3.2_Labels_or_Instructions

Jon: WIDGET 1 rule: Widgets must have labels

Nick: What are the techniques for adding labels to widgets?

Jon: A lot of different combinations.

Jon: 4 ways to label a widget: (1) child or descendant text content (default label) examples: checkbox, radio button, list item, menu item, tree item

Jon: (2) aria-label; (3) aria-labeledby (4) title attribute (not recommended)

Jon: Only certain types of widgets can use child or desc. technique.

Jon: In ARIA spec, for every role, whether it's a landmark, a widget, a section or a live region (two aria roles for that: status and alert), or something like a document role

Jon: Role application and role document

Jon: Techniques preferences: 1st is child or descendant text content; 2nd is aria-labeledby (since it reuses content that is already there); 3rd is aria-label (often used when you want to have a different label or one that is not rendered; 4th is title attribute

Ann: title creates tooltips, but is device or browser dependent

Ann: Values of the title attribute may be rendered by user agents in a variety of ways. For instance, visual browsers frequently display the title as a "tool tip" (a short message that appears when the pointing device pauses over an object).

Jon: Are there any mentions of widget labeling in WCAG techniques?

Nick: Need to define what we mean by widget.


Nick: Seems to be more closely mapped to WCAG 4.1.2

Jon: A lot of nesting requirements for widgets, e.g. certain roles can't be children of other roles

Jon: Also ARIA states and properties that are required; problems when they're missing.

Jon: /member/wiki/WCAG_2.0_Principle_4_Robust_Rules

Marc: Would 4.1.1 also apply?

Ann: I would say it all goes under 4.1.2.

Jon: Should we use a different ID for these rules than WIDGET?

Jon: What is the rule category label?

Ann: 10. Design Patterns

Ann: For these widgets and structures, this document describes the keyboard interaction and identifies the relevant WAI-ARIA roles, states, and properties.


Nick: What we're talking about are elements that use ARIA widget roles.

Jon: Widgets use structural roles, e.g. group but some widget roles have implied structure.

Jon: Restrictions on what can be child of group or other roles.

Personal tools