[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [office-accessibility] OASIS ODF Accessibility meeting,Monday June 2nd, 7am PT / 9am CT / 10am ET / 4pm CET / 11pm Japan time
Damn - almost missed it because I am just busy with some bug fixes ;) And my XChat also doesn't work anymore since switching to 64 bit Windows :( Can someone please send me the phone details? Malte. Peter Korn wrote, On 02.06.08 07:38: > Dear colleagues, > > As agreed at our last meeting, our next meeting is set for tomorrow - > Monday June 2nd, at 7am PT / 9am CT / 10am ET / 4pm CET / 11pm Japan > time. Please use our usual (and unpublished) dial-in, and our usual IRC > channel: &office-accessibility and irc.oasis-open.org > > Attached, and at > http://lists.oasis-open.org/archives/office-accessibility/200805/msg00023.html > please find the minutes from our last meeting, on Friday May 23rd. > > I believe we have a short agenda for this meeting - mostly a question as > to whether recent information provided by TC members mean we have enough > to begin our review, and a walk-through of the open action items (which > overwhelmingly belong to Rich!). > > > Agenda > -------- > 0. Approval of the minutes (see attached and URL above) > > 1. Is the ODF v1.2 draft ready for our review? Note that Michael Brauer > recently posted the v7 schemas, and Patrick Durusau just today posted > ODF v1.2 v7-03-0531. > - See: v7-02 at: > http://www.oasis-open.org/committees/download.php/28121/OpenDocument-v1.2-v7-02.odt > - See Patrick's v7-03-0531 message: > http://lists.oasis-open.org/archives/office/200806/msg00000.html > - See Michael's v7 schemas message: > http://lists.oasis-open.org/archives/office/200805/msg00129.html & > - See Michael's message on schemas: > http://lists.oasis-open.org/archives/office/200805/msg00134.html > > 2. Action items (from before) > a. Janina 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 revision of the > accessibility guidelines to allow control of the animation rate of > images in a presentation > > d. Hiro to provide wording in the to address 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 > connections. > > f. Rich Schwerdtfeger to answer questions: 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". > [From Tatsuya: look at ODF v1.1 spec. 15.4.23 Language; Use the > fo:language, fo:language-asian and fo:language-complex properties to > specify the language of the text. See §7.9.2 of [XSL] for details. Some > applications ignore these properties if they are not specified together > with the corresponding fo:country property.] > > g. Rich Schwerdtfeger: 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. > > h. Rich Schwerdtfeger: address question/ research on Accessibility of > Animations > - Animations that are defined and controlled by ODF (eg. Fly right, fly > left) > - Embedded content that contains animations > > i. Rich Schwerdtfeger: Research Tasks > - Plugins that support captions > - OS Matrix on Descriptive Video > > j. Rich Schwerdtfeger: Modify Hiro's proposal to put into merge > document. Notes from previous meeting: > Hiro - Write proposed modification to 8.1.1 to add caption-id for table, > and 9.2.15.2 to include tables - <ref > name="common-draw-caption-id-attlist"/> [note that Hiro is providing > more information related to table headers (from > http://www.oasis-open.org/apps/org/workgroup/office-accessibility/email/archives/200711/msg00007.html) > > > > Regards, > > Peter Korn > Accessibility Architect, > Sun Microsystems, Inc. > > > ------------------------------------------------------------------------ > > Subject: > [office-accessibility] OASIS ODF accessibility meeting minutes - 23May08 > From: > Peter Korn <Peter.Korn@sun.com> > Date: > Thu, 29 May 2008 17:35:04 -0700 > To: > office-accessibility@lists.oasis-open.org > > To: > office-accessibility@lists.oasis-open.org > > > Dear colleagues, > > Here are the minutes I took from our OASIS ODF accessibility meeting on > 23May08. > > Please note that our next meeting is set for this coming Monday June > 2nd, at 7am PT / 9am CT / 10am ET / 4pm CET / 11pm Japan time. Rich - I > believe the deal was I'd wake up early for these meetings, and you'd be > responsible for being coherent and running them! > > > Attendees > --------- > Tatsuya > Janina > Pete Brunet > Peter Korn > Rich > Hiro > > 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 > * Unanimous consent to minutes sent by Mike Paciello at > http://lists.oasis-open.org/archives/office-accessibility/200805/msg00022.html > > 1. Confirm with IBM Japan, all, that this as our most-of-the-time new > meeting time > * Tatsuya requests on behalf of the rest of IBM Japan that we start > one hour earlier: at 11:00am PT / > * Confirmations from Janina, Peter, Pete, Rich, Tatsuya, and Hiro > that 7am PT / 9am CT / 10am ET / 11pm Japan works for them - except the > 2nd Monday of every month for Rich is a conflict > * Action: get confirmation from others > > 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 > * IBM Japan reports that, so long as we are meeting one hour earlier > (at 11pm their time), we don't need to meet at a better time for Japan > one week a month. > > 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) > * Report of vote: 11 ayes, no nays; we are a committee specification > * See: > http://docs.oasis-open.org/office/office-accessibility/v1.0/cs01/ODF_Accessibility_Guidelines-v1.0.pdf > and > http://docs.oasis-open.org/office/office-accessibility/v1.0/cs01/ODF_Accessibility_Guidelines-v1.0.odt > and > http://docs.oasis-open.org/office/office-accessibility/v1.0/cs01/ODF_Accessibility_Guidelines-v1.0.html > > 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 > * Rich: this specification seems not quite ready for review -> the > schema isn't in sync with the rest of the document (Michael Brauer had > suggested we provide schema changes). > * AI for Rich: to work with the TC to determine when we will have a > draft that is ready for our review > > 5. ODF Accessibility Guidelines v1.1 for ODF v1.2 > - Seeking a new owner/maintainer for the document (instead of me)... > * No volunteers; Peter remains stuck with it > > - 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 > * "3.13.2" is a red herring. Janina's new 2.6 is what was sought, > and is done. > Janina 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. > * This remains an open AI for Janina > > 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. > * This remains an open AI for Peter > > c. Rich Schwerdtfeger to: add wording to the next revision of the > accessibility guidelines to allow control of the animation rate of > images in a presentation > * This remains an open AI for Rich > > d. Hiro to provide wording in the to address 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 > connections. > * This remains an open AI for Hiro; will check this also against the > latest ODF v1.2 spec. > > > 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.? > -> Not a spec. issue, and if a bug, it appears fixed. See Section 4.1 > of the ODF v1.1 spec. The element is <text:h>, and the heading level is > indicated by the attribute "text:outline-level" which is set to equal > the heading level (e.g. "1", "2"). > > * 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". > * This remains an open AI for Rich > [From Tatsuya: look at ODF v1.1 spec. 15.4.23 Language; Use the > fo:language, fo:language-asian and fo:language-complex properties to > specify the language of the text. See §7.9.2 of [XSL] for details. Some > applications ignore these properties if they are not specified together > with the corresponding fo:country property.] > > - 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. > * This remains an open AI for Rich > > - Accessibility of Animations > - Animations that are defined and controlled by ODF (eg. Fly > right, fly left) > - Embedded content that contains animations > * This remains an open AI for Rich > - Research Tasks > - Plugins that support captions > - OS Matrix on Descriptive Video > * This remains an open AI for Rich > > - Modify Hiro's proposal to put into merge document. Notes from > previous meeting: > Hiro - Write proposed modification to 8.1.1 to add caption-id for table, > and 9.2.15.2 to include tables - <ref > name="common-draw-caption-id-attlist"/> [note that Hiro is providing > more information related to table headers (from > http://www.oasis-open.org/apps/org/workgroup/office-accessibility/email/archives/200711/msg00007.html) > * This remains an open AI for Rich > > > Regards, > > Peter Korn > Accessibility Architect, > Sun Microsystems, Inc. > > > ------------------------------------------------------------------------ > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. You may a link to this group and all your TCs in OASIS > at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]