Accessibility Minutes 2011 11 14

From MemberWiki

Jump to: navigation, search


  • Ann Abbott (IBM)
  • Jon Gunderson (University of Illinois - Co-Chair)
  • Marc Johlic (IBM)
  • Philip Ackermann (Fraunhofer Institute for Applied Information Technology)
  • Prasanna Bale (University of Illinois) (Scribe)
  • Rich Schwerdtfeger (IBM - Co-Chair)


JG: /member/wiki/Accessibility_Ruleset_Rule_and_NLS_Format_2.0#Rule_Files_and_SVN_Repository


JG: Due to the performance issues in version1.0 we abandoned the version 1.0 and using the version 2.0 which is situated at the repository

JG: version 2.0 improves the performance by calling the dom only once

AA: /member/wiki/Accessibility#Minutes

JG: /member/wiki/WCAG_2.0_Principle_2_Operable_Rules#Requirement_2.4.2_Page_Titled

   TITLE 1: The page must contain exactly one title element and it must contain content.

JG: agreed up on Violation for Trasitional as well for ARIA

   TITLE 2: If a page contains both MAIN landmarks and H1 elements, each H1 element should be a label for a MAIN landmark

JG: /member/wiki/WCAG_2.0_Principle_2_Operable_Rules#Requirement_2.4.1_Bypass_Blocks

AA: Was there more than one H1 on a page?

JG: Yes

JG: Does this seem ok with Title2 and Landmark1?

RS: feel its not mandatory

PB: If there are more than one H1 and MAIN landmark on page, which H1 has to be associated with MAIN?

JG: MAIN landmarks can reference H1 elements in other landmarks and considered as error if MAIN landmark references H1 element in other MAIN (documented on the wiki)

   TITLE 3: The words in the content of the first H1 element (document order) on the page should be a subset of the words in the content of the TITLE element

JG: Does Title3 seems right?

AA: Yes

   TITLE 4(EN): Title content should be concise and descriptive (more than one word, but less than 100 characters) (English only)

JG: TITLE 4 is Recommendation

   TITLE 5: The title element content of the page should be unique within a website and identify the content of the web page

JG: TITLE 5 is a manual check

JG: Manual evaluation makes more sense than potential violation

PA: agrees on manual evaluation

MJ: Yes. as potential violation will not give much feedback to the users.

JG: Group agrees on Manual Evaluation

Requirement 2.4.3 Focus Order

    FOCUS ORDER 1: If a page contains more than one link, form control, object or widget verify the focus order is meaningful

JG: Changed from Potential violation to Manual Evaluation

Requirement 2.4.4 Link Purpose (In Context)

    Link 1: The accessible text of a link, including the content referenced using aria-describedby, for links with different HREFs in the same landmark should be the unique

JG: using aria-describedby would pass the rule

PB: consensus is recommendation

    Link 2: The accessible text of a link, including the content referenced using aria-describedby, for links with same HREF should be the same

rather than continuing the discussion on Link2 will discuss on coding rules...

Personal tools