Special OASIS ODF Accessibility SC meeting, Friday May 23,8am PT / 11am ET / 3pm UTC / 4pm BST / 5pm CET / midnight Japan

Dear all,

Due to e-mail problems, my announcement & agenda for what I'd hoped
would be a resumption of our regular meetings at the mostly-ratified
new time of Mondays (8am PT / 11am ET / 3pm UTC / 4pmBST / 5pm CET /
midnight Japan) didn't make it to the list.

I believe the e-mail problems are resolved, but not in time to meet
today.  Next week Monday is the Memorial Day holiday in the U.S., and
Rich and I would prefer to not wait another two weeks to meet.  So we
would like to call a special meeting this coming Friday, to hopefully
address a few items (see agenda below).

Please RSVP to me/Rich and let us know whether you can attend.

Friday May 23, 8am PT / 11am ET / 3pm UTC / 4pm BST / 5pm CET /
midnight Japan

IRC: http://irc.oasis-open.org

channel: "&office-accessibility"

Phone numbers are the "usual" toll-free numbers we have been using for
some time now, courtesy IBM.  By request, I am not publishing them
where they might be archived.

=======================

Agenda:

 0. Approval of the minutes

  - I am not finding our previous minutes.  Only two messages from Mike
Paciello, at:
http://lists.oasis-open.org/archives/office-accessibility/200805/msg00001.html
and
http://lists.oasis-open.org/archives/office-accessibility/200805/msg00005.html

 1. Confirm with IBM Japan, all, that this as our most-of-the-time new
meeting time

 2. Conform with IBM Japan, all, which week of the month (and perhaps
day of the week) we will use an alternate time, and exactly what that
time is

 3. Status of the vote for making our ODF Guidelines document a formal
Committee Specification (see the vote at:
http://www.oasis-open.org/apps/org/workgroup/office/ballot.php?id=1459)

 4. ODF v1.2 draft 

  -Latest: v7-02: http://www.oasis-open.org/committees/download.php/28121/OpenDocument-v1.2-v7-02.odt

  - We have two concerns as stated by Pete Brunet about tables - see:
http://lists.oasis-open.org/archives/office-accessibility/200805/msg00017.html

  - We had the plan from our last meeting (April 28) to assign sections
of this specification for review, but are missing that report from the
minutes.  In the absence of that info, we will need to regenerate it

 5. ODF Accessibility Guidelines v1.1 for ODF v1.2

  - Seeking a new owner/maintainer for the document (instead of me)...

  - Summary of planned additions/changes:

   a. Janina's new section 2.6, 2.6.1, and 2.6.2;

      also add guidelines to address reload delay section 3.13.2 which
would allow user agents to control the reload delay, as per
http://www.oasis-open.org/apps/org/workgroup/office-accessibility/email/archives/200804/msg00034.html

     Janinan to modify the accessibility guidelines to state how common
field attributes (section 6.7 of the ODF 1.2 spec.) should be supplied
to the AT. The field attributes would indicate whether something were a
boolean, gregorian date, etc.

   b. Peter Korn to: provide provide guidelines as to how to provide
tracking information to ATs; and modify guidelines to ensure
applications respond to system font and color settings.

   c.  Rich Schwerdtfeger to: add wording to the next revison of the
accessibilty guidelines to allow control of the animation rate of
images in a presentation

   d. Hiro to provide wording in the to adress dynamic, asynchronous
updates There are several topics in the specs related to
“asynchronous automatic update� of contents or values. Automatic
updates should be carefully presented to assistive technologies through
accessibility APIs. Documents are becoming more dynamic- async updates
- some examples: linked tables, database ranges, scritping, text
sections, DDE connecdtions. 

 6. Previous action items:

 * Peter actions:

    - Check to see if this is a bug in OpenOffice: Address David's
concern that headings were made available in an easy to discern way.
... H2s followed by H1s etc. He obtained that structure from an
additional file.  Came back in an OOo update, and that information was
no longer available.  Was Dave relying on optional attributes that are
no longer there, or did OOo break the spec.? 

* Rich actions:

    -  How does ODF do language tagging of a range of text?  Font
attributes?  And how best to tag a string as "Grade 2 English
Braille", vs. "music Braille in German". 

    - Find deadlines for ODF 1.2; also to verify whether TC would like
to see our 1.2 guidelines doc delivered at same time (in same "bundle")
as 1.2 spec.