Accessibility Minutes 2013 09 16

From MemberWiki

Jump to: navigation, search



  • Jon Gunderson (University of Illinois)
  • Mark Novak (Paciello Group)
  • Mike Scott (Illinois Dept. of Human Services)
  • Nicholas Hoyt (University of Illinois) - scribe
  • Rich Schwerdtfeger (IBM)


Rule Scopes

JG: Would like to add website scope.

JG: Previously we have had rules with page and element scope.


JG: We now have three types of rules relative to scope that we've identified:

  1. element-level rules e.g. image, widget, form control
  2. page-level rules e.g. heading structure, presence of main landmark
  3. new: website-level rules, based on WCAG 2.4.5, 3.2.3 and 3.2.4, rules about a set of web pages

NH: Distinguishing between element- and page-level rules helps with visualizations.

JG: At the conceptual level, we think it will help developers to have website-level rules

MS: How have we categorized rules according to these three types?

JG: Am going through all of our current rules to determine whether correct scope is defined.

Rule Results for Different Types of Rules

From Agenda:

  1. Coding to standards or coding conflicts (fail/manual checks, no passes)
    1. No title element
    2. Both aria-required and required on element
    3. Empty label element
  2. Accessibility requirements (pass/fail/manual check)
    1. At least one main
    2. Image has alt attribute
    3. No label on form control
  3. Helps reduce passing counts and accessibility scoring inflation

JG: Coding to Standards

JG: You don't get a pass result for these types of rules, but you get a failure if you don't comply.

JG: This allows only the accessibility requirements rules contribute to pass percentage.

New rules for Navigation category

  • WCAG 2.4.5: More than one way: site map, inter page navigational links, website search feature
  • WCAG 3.2.3 :Consistent Navigation (same relative order)
  • WCAG 3.2.4: Consistent identification (same names)

JG: Navigation Rule 1

JG: At least two of the following features must be used to find content in a website

  1. website search feature
  2. list of links for navigation between pages
  3. breadcrumbs or sand trail
  4. dedicated page that serves as site map
  5. home page includes a list of links to all other pages in the website

JG: These are the five ways to comply with 2.4.5.

JG: The next two rules are for 3.2.3: Consistent Navigation (same relative order)

JG: Navigation Rule 2

JG: Consistent ordering of main, navigation, search, banner and contentinfo landmarks on each page of a website

JG: Navigation Rule 3:

JG: Consistent ordering of h1 and h2 elements that mark major sections on each page of a website (also for 3.2.3)

RS: Don't we need to go beyond the h2 level?

JG: h1 and h2 are the only heading elements for which we have rules that specifically address indicating main sections of pages.

RS: Could have additional regions on page.

JG: Developers could see this as a template rule: go through all of my templates to look at consistency.

JG: The "manual checking techniques" that we provide could discuss templates.

JG: WCAG How to Meet: labels for form controls, headings, landmarks, alt text on images

JG: These would be manual check rules.

JG: Do not have rules yet for 3.2.4


JG: Have updated link hrefs on downloads page for OAA Evaluation Library.

Personal tools