From The Linux Foundation
Revision as of 23:24, 19 May 2008 by Ptbrunet (Talk | contribs)

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

Agenda for 2008/05/20

  1. Introductions if needed
  2. Prior minutes
    • Corrections? Approval?
  3. LF: Open A11y news - Janina
  4. AccProbe inspect tool - Mike Squillace
  5. Firefox - Marco Zehe
  6. IA2 1.0.2 readiness for review.
    • The spec has been posted for review. Please see the links at the top of the IA2 home page.
    • The current review/release plan for IA2 version 1.0.2 follows:
      • 2 week review within the Linux Foundation's IA2 and Open A11y communities from 5/19 through 5/30
      • 4 week review by the entire world wide accessibility community from 6/2 through 6/27
      • Submit to the Linux Foundation Board of Directors for approval on 6/30.
  7. IA2 text attributes specification.
    • This spec is ready. The Firefox team has requested that we wait until there is at least one implementation to ensure it is correct. Agreed?
  8. IA2 object attributes specification.
    • This spec has just been started. The Symphony and FF3 object attributes will reviewed. The common attributes will become part of the IA2 object attributes spec and the spec will reference the FF3 and Symphony specific specifications. (The Symphony object attributes are not documented on any Symphony web site, but they'll soon be documented on the IA2 site.)
  9. Interop with UIA - Other than the last bullet under Issue 114 there has been no change from the last meeting.
    • This is the current status of the seven IA2 issues Calvin Gaisford opened on the behalf of AIA:
      • Issue 112: Commentary was added to the IDL.
      • Issue 113: This will probably remain as is.
      • Issue 114: An email was sent on May 16 to Norm Hodne at Microsoft asking if Microsoft could create the interface and attach it to bug 114. That should resolve the legal concern regarding the addition of get_objectForChild and get_IAccessiblePair to the IAccessible2 set of interfaces. It would then be clear that the content was directly from and approved by Microsoft and thus it would be clear that the content was not in violation of any Microsoft licenses, copyrights, or promises. See the bug log for the full text of the email.
      • Issue 115: Input is needed from Microsoft. This would probably be a version 2 issue.
      • Issue 116: Commentary was added to the IDL.
      • Issue 117: Input is needed from Microsoft. This would probably either be a version 2 issue or remain as is.
      • Issue 118: Commentary was added to the IDL.
    • Inter-organizational cooperation - How would Open A11y collaborate with AIA (Accessibility Interoperability Alliance)?
      • UIA and UIA Express are now being developed within the AIA.
      • IA2 and ATK/AT-SPI are being developed within the Linux Foundation Open Accessibility workgroup.
  10. Proposal for access to misspellings, grammar errors, and "smart tags"
    • Oliver-Rainer Wittmann from Sun sent email describing an interface proposal for access to misspelling, grammar errors and "smart tags".
    • Pete is checking with Xing Li. This may have already been solved with IAHyperlink and IAAction.
  11. IA2 proxy DLL and the USB key fob problem
    • Currently can't run NVDA and FF3 on USB stick.
    • See this post to the IA2 list for more detail.
    • Marco opened a bug against FF3.
    • Symphony has already removed installation of the DLL as per the prior agreement but can add it back in around the August time frame.
  12. Access to document revisions - from the ODF AccSC
    • This was reviewed and approved by Li Yuan the committer for ATK/AT-SPI. He has asked for someone to develop a patch.

enum IA2RevisionType {
  IA2_REVTYPE_FORMAT_CHANGE  // The revision is due to any change in formatting attributes. 

typedef struct {
    enum IA2RevisionType type;  
    BSTR time;  ///< ISO 8601 format:  YYYY-MM-DDThh:mm:ss (eg 1997-07-16T19:20:21)
    BSTR author;
    BSTR comments;
} IA2RevisionInformation;

// Note: an object that implements IARevisionText must also implement IAText
// returns the number of segments available for the
// block of text represented by the IARevisionText object.
// this number is 1 based
get_segmentCount( long* count );
// returns a specific segment based on the index passed in
// the index is 0 based.
// no two indexes should return the same segment.
// any index >= 0, and less than the segment count should return a valid segment
// any index outside those bounds should set HRESULT to S_FALSE and return NULL
get_segment( long index,  IARevisionSegment** seg );
// returns a segment whose boundaries encompass the offset provided
// if there are no segments that correspond to the given offset, an error is produced
// offsets correspond identically to those used by IAText and IAHyperlink
get_segmentAtOffset( long offset, IARevisionSegment** seg );

// returns the bounding offsets of the segment within the IARevisionText/IAText object.
// the end offset is one past the last character in the revision text
get_bounds( long* start, long* end );

// returns a struct containing date/time, author, and comments
get_attributes( IA2RevisionAttributes *attributes );
// returns a set of name value pairs describing additional application
// specific attributes in the format "name:value;name:value"
get_extraAttributes( BSTR* extraAttributes );

No progress on the following

  1. Eclipse
  2. Move latest frozen 3/26/2007 1.0.1 IDL to BZR
  3. Wikipedia
  4. Developer Guide - Best practices document. We should start an outline for a best practices document. For starters it should define the following:
    • What events should be fired for each role and in what order.
    • What object hierarchy should be used. There are two today, a flat hierarchy as used in Symphony and a deeper hierarchy as used in Firefox. These two should be documented and in order to cut down on the proliferation of designs, future applications should attempt to use one or the other.
  5. Oleacc.idl
    • No new status on when it will be back in the SDK.
  6. FAQ