From The Linux Foundation
Revision as of 20:30, 18 September 2007 by Ptbrunet (Talk | contribs)

(diff) ←Older revision | view current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

IAccessible2 SIG Conference Call Minutes 2007/09/18

  1. Regrets
    • Barry Feigenbaum
  2. Attendees
    • Pete Brunet, Janina Sajka, Andres Gonzalez, Aaron Leventhal, Itoh-san (Takashi Itoh), Mick Curran
  3. OpenA11y news from Janina
    • Nominations and voting are complete.
      • Chair: Janina Sajka
      • Vice-chair: Gregory Rosmaita.
  4. CSUN 2008 - IA2 related activities?
    • Janina will chair a panel on the status of the LF Open A11y standards, i.e. the IA2, atk/at-spi, and keyboard specs. They should all have been submitted to ISO by the time of CSUN.
    • There will be a session on Expert Handlers which may cover IA2 to some extent.
    • IA2 may be mentioned in any FF3 based presentations.
    • Will there be anything related to IA2 in OpenOffice?
  5. Version 2 of the text attributes
    • Aaron is not sure if they will be able to implement this in FF3.
  6. Addition of IAText::defaultAttributes - raised by Aaron
    • No new status this week.
    • The question is: For the next release of IA2 should IAText::attributes be deprecated in favor of IAText::defaultAttributes and IAText::changedAttributes?
    • The use case for FF is a string of text with a link. In FF this will be a parent object with an embed character representing the link text and a child object holding the link text. The concept of default attributes could be helpful in this case, i.e. if the POR (Point of Regard) is in the link, a default attributes method could return the attributes of the parent affecting the child. However this could also be done by querying the parent object for the text attributes in effect at the point of the embed character. If this solution was acceptable the existing IA2 design would not have to be changed.
    • Prior discussion with ATs: Repeat the text attributes repeated on every node, because that's what Notes 8 does. However, it turns out that there are bigger issues than that, in terms of how FF is different from Notes 8:
      • Where focus is in an editable document
      • FF uses embedded object chars and a containment hierarchy, so that to get text for a line you need recursion.
    • Aaron will continue discussions with the AT vendors. He will target having more status in two weeks.
  7. Inspect tool - Mike Squillace:
    • No new status except that we're having a lot of trouble now that we're introducing multi-threaded contexts with COM - slowly working through issues.
    • Prior status
      • The next release of AccProbe will be as part of the Accessibility Tools Framework (AcTF), which has its Creation Review set for Sept. 17. After this review, we will (assuming successful at the review) begin committing code to AccProbe will be part of this initial commit. The next release will include enhanced Find functionality on the Explorer View, a highlighting rectangle, keyboard tracking (and possibly mouse/cursor tracking), and a User's Guide.
      • The limited release version, currently in use by the FF3 and dojo development teams, will be upgraded to r0.2 in mid September.
  8. Firefox Status - Aaron Leventhal
    • a dozen critical bugs, ARIA fixes, a desire to make it easier to use in html, i.e without using namespaces
  9. NVDA Status - Mick Curran
    • NVDA (Non-Visual Desktop Access) is an open source Win screen reader. Mick has been implementing IA2 in NVDA since May. It's been going pretty well so far, focusing on FF3. IAText caret support has been very helpful.
  10. Best practices for implementations - from Mick Curran
    • To help reduce the amount of special casing code by ATs there needs to be a best practices implementation document for application developers.
    • Having an OpenOffice and FF3 implementation will help as being models to base other implementations on.
    • We should discuss this more in future meetings.