Accessibility Minutes 2011 05 16

From MemberWiki

Jump to: navigation, search

Contents

Present

  • Richard Schwerdtfeger (IBM - Co-Chair)
  • Jon Gunderson (University of Illinois - Co-Chair)
  • Marc Johlic (IBM)
  • Ann Abbott (IBM)
  • David Todd (IBM)
  • Nicholas Hoyt (University of Illinois)
  • Aurelien Levy (Temesis)

Caching

DOM element base class

Jon: /member/wiki/Accessibility_DOM_Elements_Cache#Table_Cache_.28under_development.29

Jon: Been working on cache this week documenting the properties. Will add methods also.

Jon: DOM element base class: provides node, id value, position in class, tag name, role (may skip if presentational or hidden) plus 4 arrays.

Aurelien: http://www.w3.org/TR/EARL10-Schema/#OutcomeValue

Jon: have you worked a lot with earl?

Aurelien: knows of 1 French tool that uses.

Jon: would you like to work on translating our format to earl? Seems overly complicated and used for document format.

Aurelien: correct and allows comparison of results between tools.

Jon: have not discussed results objects yet. Needs investigation and not ready for earl at this point.

Aurelien: seems similar to what OAA has.

Nick: has looked at earl but seems complicated.

Jon: potential violation = CannotTell

Jon: near future OAA discussion = running the rules

Jon: lightweight option = JSON or XML format

Rich: who has implemented earl anywhere today?

Aurelien: we use and know 1 tool that does

Jon: if someone needs, they can implement

Jon: would like to spend our time on rules and get out the door. Doesn't see using earl at this time.

Rich: doesn't see earl getting any adoption worldwide.

Nick: rule_not_supported s/b rules_not_supported

Jon: yes, thank you

Links element cache

Jon: Link Elements Cache

(see table at last URL posted for properties, type & description)

Aurelien: did you consider 'title'?

Jon: could use title attribute to help understand difference of links

Rich: title would map to accessible name, if any

Ann: doesn't title map to tooltip, and JAWS will announce tooltip

Jon: JAWS will if configured to

Ann: if considered a sufficient technique, should be included

Jon: would never write a rule to allow sentence to pass

Aurelien: many EU countries allow title for link object

Jon: will add

Jon: if anyone wishes to write rule for context from sentences, they are welcome to, but won't write it.

Cache inspector

Jon: http://code.google.com/p/oaa-accessibility-cache-inspector/

Above is link to testing tool to write cache.

Jon: no XPI package, but can check out code and point FF to it.

David: can you get to all those elements from DOM Element base?

Jon: http://code.google.com/p/oaa-accessibility-cache-inspector/source/browse/trunk/chrome/content/oaa/scripts/cache.js

Jon: function traverses DOM once to cache all needed to run rules

Other cache concerns

Rich: what triggers a re-calc?

Jon: tool would based on time (every so many seconds) or if node doesn't exist in cache

Rich: or focus change event

Rich: or live region adds/removes

Jon: hopes rules run in 2-3 seconds at most

Rich: what about mutation events?

Jon: faster it is, easier to update

Jon: when busy goes to not busy, do refresh

David: do we need to cache divs & spans?

Jon: will cache things that have role values and have to add cache details for forms and color contrast

Jon: only care about divs that have roles

Jon: will have widget cache

Jon: landmark and widget cache are tree caches to have parent info

Jon: rest have only document order info

Jon: plans to work on those this week

Aurelien: useful to add tab order?

Jon: would ever have rule for tab order?

Jon: will add tab index

Call ended 1:03pm Central--AnnAbbott 19:23, 16 May 2011 (UTC)

Personal tools