Accessibility Minutes 2011 12 05

From MemberWiki

Jump to: navigation, search



  • Jon Gunderson (University of Illinois - Co-Chair)
  • Ann Abbott (IBM)
  • David Todd (IBM)
  • Marc Johlic (IBM)
  • Nicholas Hoyt (University of Illinois)
  • Philip Ackermann (Fraunhofer Institute for Applied Information Technology) scribe
  • Prasanna Bale (University of Illinois)
  • Richard Schwerdtfeger (IBM - Co-Chair)


Link to agenda:


Requirement 2.4.5 Multiple Ways


Ann: Multiple ways require at least two ways

Jon: Include three ways, and pass if there are two of three ways

Everybody agrees

Jon: I think different smaller rules are better maintainable than one large rule

Jon: algorithm for G125, G64, G161, G185 would be the same at the moment

Jon: don't think we need an algorithm for H59

Jon: agree with Nick that complicated rules rather confuse developers

Jon: Add transitional LANDMARK_7 which looks only for searchbox?

Ann: think that every test (also searchbox-test) would require manual evaluation

Requirement 2.4.6 Headings and Labels


Nick: When and how do we add HTML5 to our rules?

Jon: I assume that HTML5 elements are mapped to landmarks (for example "nav")

Rich: it's required for browsers in HTML5 to create a table of contents

Rich: this could result in restructuring headings (for example h4 could become h2, if there are only h1 and h4 in a heading hierarchy)

Jon: HEADING 8 recommendation?

Everybody agrees

Jon: LANDMARK_3 sibling landmarks have the same parent

Nick: what's the same parent, is it the parent landmark?

Nick: what's the level?

Ann: landmarks of same type should be unique no matter where they are in the document

Ann: no matter what the level

Nick: I agree and also think that it's difficult to define what the level actually is

Jon: agreed

Jon: LANDMARK_4 similar to HEADING_3, should be a manual evaluation

Jon: CONTROL_10: what about HTML5 elements like "date"?

Ann: think that we should not include HTML5 at the moment

Nick: there are cases where you repeat labels for form elements, for example different address forms on one page

Nick: and how is an "accessible label" defined?

Jon: I think for every occurrence of "accessible name" or "accessible label" add a reference to the algorithm that is used to generate that name/label

Jon: I will add a section like "accessible name calculation"

Jon: CONTROL_11 recommendation?

Everybody agrees

Personal tools