Accessibility Minutes 2013 07 22

From MemberWiki

Jump to: navigation, search


  • Jon Gunderson (University of Illinois)
  • Mike Scott (Illinois Dept. of Human Services) (scribe)
  • Nick Hoyt (University of Illinois)
  • Rich Schwerdtfeger (IBM)
  • Ann Abbott (IBM)


Removed AAA rules, including 7:1 color contrast and video rules

Updated prototype Coding Practices site

Rules for focus:

SC 2.4.3 (Level A) Focus has meaningful order

If 1 or fewer focusable elements, rule doesn't apply

If no tabindex set, should it apply?

Mike: yes

Ann: yes

IITAA 13.3 Avoid changing focus unexpectedly

WCAG 2.0 3.2.1 On focus: When any component receives focus, it does not initiate a change of context (Level A)

IBM 2.1d, 2.4e, 2.4.7, 3.2a

WCAG 2.0 2.1.2 No Keyboard Trap

Two rules?

1. Check order after page loads

2. Check order if/when page is changed dynamically

Or one big manual check?

Focus visible could be checked at the same time

Can one manual check test multiple rules?

Concept of "related" rules/checks -- one procedure could check all related rules

Don't want an explosion of manual checks

But rules need to be kept simple/focused

Jon will come up with some ideas for next week

2.4.4 Link Purpose (in Context)

2.4.9 Link Purpose (Link Only) - Level AAA

Rule checks whether link accessible name is unique

Does it map to 2.4.4 (A) or 2.4.9 -- if 2.4.9 (AAA), do we keep it?

Personal tools