Accessibility Minutes 2012 09 24

From MemberWiki

Jump to: navigation, search



  • Ann Abbott (IBM)
  • Marc Johlic (IBM)
  • Jon Gunderson (University of Illinois - Co-Chair)
  • Prasanna Bale (University of Illinois)
  • Nicholas Hoyt (University of Illinois) - Scribe


Cache Inspector Prototype

JG: 1st agenda item: new version of OAA Cache Inspector with 3 new link rules

JG: latest version of Cache Inspector has new feature for exporting in CSV format

AA: link exists in HTML version of report to .csv version of report

Draft Rule Categories


JG: In another working group we've been talking about Rule Categories; would like this group's feedback

JG: Let's go through the categories and see if names and types of rules make sense>

MJ: The categories look good on first read-through

AA: Question about Styles label -- would Presentation be a better heading?

AA: If Styles points mainly to CSS, then Styles seems better than Presentation.

JG: Don't have any rules currently for abbreviations and acronyms

AA: What about languages?

JG: We need to think about any inline language markup and what we want to recommend/promote

JG: Could be page-level rule for language, likewise for abbrev and acronym

JG: For example, if there are no abbrev or acronym tags on page, could have a manual check to verify that there are no abbrevs or acronyms

AA: Question about tables: should all tables be addressed, i.e. change Data Tables to Tables?

JG: We plan to start using the draft rule categories in our tools to see how users react and to get further feedback

Link Purpose Rules (WCAG 2.4.4)

JG: /member/wiki/WCAG_2.0_Principle_2_Operable_Rules#Requirement_2.4.4_Link_Purpose_.28In_Context.29

JG: three rules in 2.4.4 Link Purpose (In Context)

JG: LINK 1: Links with hrefs pointing to different locations should have a unique accessible name or description.

JG: Looking into ARIA role=link specification

JG: If two elements have role=link, if they go to different targets, should have unique accessible name

JG: LINK 2: Also includes role=link?


JG: aria-labelledby or aria-label

JG: aria-labelledby or aria-label or described-by will modify the accessible name

JG: correction: aria-described-by

JG: correction: aria-described-by affects the accessible description, but not accessible name

AA: LINK 2 should have same Recommended and Required properties as LINK 1

JG: LINK 3: If using this with Firefox tools, we get dimensions in pixels

JG: We need to see if pixel density information is available in JavaScript

JG: Does WCAG address specific size (rendered) in any way?

Personal tools