Accessibility Minutes 2014 01 27

From MemberWiki

Jump to: navigation, search

Contents

Present

  • Ann Abbott (IBM)
  • Marc Johlic (IBM)
  • Jon Gunderson (University of Illinois)
  • Nicholas Hoyt (University of Illinois)
  • Mark Novak

Minutes

Remaining WCAG 2.0 success criteria needing rules

1.3.3 Sensory Characteristics (done)

1.4.1 Use of Color (done)

1.4.2 Audio Control (done)

1.4.4 Resize Text (done)

1.4.5 Images of Text (done)

2.2.1 Timing Adjustable (done)

2.2.2 Pause, Skip, Hide (done)

2.3.1 Three Flashes or Below Threshold (done)

3.2.2 On Input

  • http://www.w3.org/WAI/WCAG20/quickref/#qr-consistent-behavior-unpredictable-change
  • Rule Category: Keyboard
  • Consensus on rule category
  • 2 rules
    1. Does form include submit button (element)(Done)
    2. Selecting a radio checkbox cause change in context (Done)
    3. When any form control looses focus it does not automatically submit a form
    4. When any widget looses focus or has a change of state it does not automatically change context

3.3.1 Error Identification (done)

3.3.3 Error Suggestion

3.3.4 Error Prevention (Legal, Financial, Data)

  • AA: we need to include rules for:
  1. Situation A: If an application causes a legal transaction to occur, such as making a purchase or submitting an income tax return
  2. Situation B: If an action causes information to be deleted
  3. Situation C: If the Web page includes a testing application

Landmark Rules

2.1 Current Landmark Rules

  • Landmark Rule 1: No more than one main landmark that identifies the main content.
    • for a DOM, sub doms can have their own main landmarks
  • Landmark Rule 2: All rendered content must be placed inside of container elements with ARIA landmark roles.
  • Landmark Rule 3: Page must have navigation landmark
  • Landmark Rule 4: Website branding content (e.g. typically at the top of a web page) must use banner landmark.
  • Landmark Rule 5: No more than one banner landmark
  • Landmark Rule 6: Use contentinfo landmark
  • Landmark Rule 7: No more than one contentinfo landmark
  • Landmark Rule 8: Headings nested in landmarks
  • Landmark Rule 9: banner landmark must be a top-level landmark
  • Landmark Rule 10: navigation landmark can only contain region landmarks

2.2 Landmark Restriction Rules

  • Landmark Rule 11: main landmark must be a top-level landmark
    • exception is for iframes and frames
  • Landmark Rule 12: contentinfo landmark must be a top-level landmark (required)
  • Landmark Rule 13: complementary landmark a descendant of a main landmark or a top-level landmark (update, required)
  • Landmark Rule 14: search landmark can contain only region landmarks (required)
  • Landmark Rule 15: form landmark can contain only region landmarks (required)

2.3 Accessible Name Rules

  • Landmark Rule 16: region landmark must have an accessible name (required)
  • Landmark Rule 17: Landmarks must have unique accessible names (required)

2.4 ARIA Role Restriction Rules (required)

  • Role Rule 1: 'main' element can only have 'main' or 'presentation' landmark
  • Role Rule 2: 'nav' element can only have 'navigation' or 'presentation' landmark
  • Role Rule 3: 'footer' element can only have 'contentinfo' or 'presentation' landmark
  • Role Rule 4: 'header' element can only have 'banner' or 'presentation' landmark
  • Role Rule 5: 'aside' element can only have 'complementary', 'note', 'search' or' presentation' landmark
  • Role Rule 6: 'article' element can only have 'application', 'document' or 'main' landmark
  • Role Rule 7: 'section' element can only have 'region', 'alert', 'alertdialog', 'application', 'contentinfo', 'dialog', 'document', 'log', 'main', 'marquee', 'presentation', 'search' or 'status'
  • Role Rule 8: 'ul' or 'ol' element can only have 'directory', 'listbox', 'menu', 'menubar', 'presentation', 'tablist', 'toolbar' or 'tree' roles.
  • Role Rule 9: 'li' element can only have 'listitem', 'menuitem', 'menuitemcheckbox', 'menuitemradio', 'option', 'tab', 'treeitem' or 'presentation' roles.
  • Role Rule 10: 'hr' element can only have 'separator' or 'presentation' roles.
  • Role Rule 11: 'body' element can only have 'document' or 'separator' roles.
Personal tools