Accessibility Minutes 2015 05 15

From MemberWiki

Jump to: navigation, search


  • Jon Gunderson (University of Illinois) - Chair
  • Mike Scott (State of Illinois)
  • Ann Abbott (IBM)
  • Marc Johlic (IBM)
  • Nicholas Hoyt (University of Illinois) (scribe)


  1. Current OAA rule mapping to WCAG 2.0 Level A and AA requirements for ruleset running on development server
  2. Update on state of library
    • Updated role restriction rules to only fail and updated messaging to use “Overriding or defining element semantics”
    • Fixed bug in TABLE 2 rule related to headers in complex and simple tables
  3. Data table headers rule issue, example data table where we fail the data table: Should we pass this table?
  4. Do we have all the rules we need for version 1.0?
  5. Testing of rules and rule messaging


1. Mapping of rules to WCAG Success Criteria


Consensus: Change IMAGE 6 to require that alternative text must be descriptive, and one of the techniques is that decorative images should have 'null' alt text.


AA: What about Image 5? role=presentation on small/decorative image

MS: Would Image 5 give an error if you have alt="" but do not have role=presentation?


JG: There are a few rules (4) that are not in a ruleset.

AA: Are they being counted?

JG: Yes, but taking them out will not affect the coverage of SCs.

JG: Maybe we can have a deprecated category so that we can track rules that are no longer being included in at least one ruleset.

AA: My concern is that it could mislead someone re. compliance with Section 508.

JG: At some point we will need rule(s) for SVG images.

NH: Do both of our rulesets cover all SCs in WCAG 2.0 (A and AA)?

JG: Will create new view for ruleset by SC.

AA: Offer to run tests on the rules we have.

NH: We could run through the SCs and look at the rules that map to it, to verify we aren't missing any rules.

JG: I have about 100 test pages that are built with QUnit.

JG: We have been revising the messaging for the role restriction rules, which now need to be retested.

JG: Looking at the rule summaries: are we missing and rules, or do we have any rules that should not be there.

3. Data table headers rule issue, example data table where we fail the data table:



JG: Our rule says that a table with headers with row spans must have headers attribute

MS: Was testing these tables recently: I feel we need to stick with requiring HEADERS attribute for complex tables (tables with colspan or rowspan)

MJ: Agree that this lines up with my experience.

MS: Problem seems to be with scope=rowgroup, no ATs are able to handle this.

JG: I will update the ruleset tables to provide view that indicates SC mapping, also including whether rule is required or recommended.

JG: Next week, will continue going through this SC table.

Personal tools