Accessibility Minutes 2013 06 17

From MemberWiki

Jump to: navigation, search


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


NH: Sent email with latest updates to AInspector Sidebar prototype.

NH: AInspector Sidebar 1.0 will also add the Element Results panel.

MS: Need reevaluate button when page changes w/o reload (e.g. ajax).

MS: Have an internal URL that starts out as login page, then when you log in, the evaluation does not update. This also happens in Firebug.

MS: All of the content changes are the result of JavaScript (rather than page load).

JG: Will meet with MS and NH to look into this further.

JG: Update on AInspector Firebug: Prasanna finished her last version last week. It will also be available at Mozilla Add-ons site.

JG: Need to decide on rulesets for 1.0, and test features as well.

AA: Will we have release of 1.0 tools before we have rulesets complete?

NH: I agree that this would cause too much confusion.

JG: Could renumber the OAA Evaluation Library versions, e.g. 0.x

JG: Would like to have a comparison between current OAA rulest and IBM rules in RPT.

AA: Link to IBM rules:>

JG: Will have student do gap analysis.

AA: Some of the requirements in checklist are 508, some are WCAG (or both),

AA: US Section 508:

JG: Any news on 508 refresh?

MJ: We're hearing next draft due in August.

AA: And that there are massive changes for software requirements, not many changes for web requirements.

NH: Need to clarify what our goals are re. ruleset completeness (version 1.0).

NH: We have talked about mapping to all A and AA WCAG success criteria.

AA: And also that the strict ruleset maps to IBM requirements.

NH: Group on campus has proposed that we only include ARIA structure rules initially.

JG: What does each ruleset assume in terms of developer skills and knowledge?

JG: How we position/describe rulesets will make a difference.

JG: Also want to emphasize in our coding practices documentation that there is often not just one way to implement accessibility for a particular situation.

JG: Part of what our tools will help to do is quantify what accessibility means.

Personal tools