The Linux Foundation

 
Accessibility/IAccessible2/Agenda/20070904

From The Linux Foundation

Agenda for 2007/09/04

  1. Introductions if needed
  2. LF: Open A11y news - Janina
  3. Version 2 of text attributes
    • Please review version 2 of the attribute spec. There may be some attributes that can be eliminated thus cutting down on the workload for implementers.
    • The suggestions to date are:
      • Remove line-height-at-least.
      • Remove num-format, num-prefix, and num-suffix and replace with a new attribute named "prefix" where the value is the actual number (with any leading or trailing punctuation such as a trailing period and/or leading and/or trailing parens), or a bullet character, or the word "graphic".
  4. Addition of IAText::defaultAttributes - raised by Aaron
    • The question is: For the next release of IA2 should IAText::attributes be deprecated in favor of IAText::defaultAttributes and IAText::changedAttributes?
    • Aaron said he will talk to the ATVs. 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.
    • Initial 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 provide further status during the meeting.
  5. IA2 has text events for both updated and changed - raised by Aaron
    • One of these is a duplicate. The Notes 8 team used UPDATED. BTW, Notes 8 only fires UPDATED. They do not ever fire INSERTED or REMOVED. JAWS doesn't use any of the text events and so the Notes 8 team only implemented the UPDATED event.
    • FF will use note use UPDATED but when there is a modification/replace will instead generate both REMOVED and INSERTED events. This is to be compatible with Linux AT-SPI.
    • Proposal is to document the following:
      • Text deleted - fire REMOVED
      • Text inserted - fire INSERTED
      • Text replaced - fire REMOVED and INSERTED *or* UPDATED
      • Unknown type of text change - fire UPDATED
    • Is this acceptable?
  6. Inspect tool - Mike Squillace
  7. Firefox - Aaron Leventhal

No progress on the following

  1. IDL submission to BZR.
    • There have been no changes since the March 26 version.
    • Prior to publishing it on the main page the 3/26 version is available via bug 111.
  2. Eclipse - Barry Feigenbaum
    • Check back in August
  3. Python wrappers
    • Waiting for IBM legal approval to release as BSD.
  4. Documentation of memory management issues for [out] parameters - the following need to be understood and documented.
    • Here is a rough first draft:
      • BSTRs need to be SysFreeString'd at end of life; ditto for when they are in structs or arrays.
      • COM interfaces need to be AddRef'd when used and Release'd at end of life.
      • Single longs, HWNDs, booleans, and structs are allocated by the caller and passed by reference. The marshaller does all the memory management. (I don't believe there are any structs with BSTRs or interface pointers.)
      • Arrays of longs - the server allocates the top level array and anything it points to; nothing needs to be free'd by the client. The marshalling code handles freeing anything on the client side.
      • TBD: How are VARIANTs handled? Like interfaces? These methods return VARIANTs: IAHyperlink::anchor/anchorTarget, IAValue::current/maximum/minimumValue
      • TBD: Are arrays of IUnknowns, e.g. IARelation::targets, correctly specified as **IUnknown?
      • This Don Box article can be used for understanding: http://www.microsoft.com/msj/1196/activex1196.aspx
  5. Wikipedia
    • Please contribute and/or review.
  6. Developer Guide
  7. Oleacc.idl
    • No new status on when it will be back in the SDK.
  8. BZR patch submission process
  9. Enter defects into Bugzilla

Other Topics

  1. What else needs to be discussed?
  2. What IA2 information do you need?
  3. What IA2 issues need resolution soon? Target date?
  4. What would you like to see done?
    • FAQ
    • Others?

[Article] [Discussion] [View source] [History]