office-accessibility message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [office-accessibility] ODF Accessibility SC Agenda April 10, 2008
- From: Hironobu Takagi <TAKAGIH@jp.ibm.com>
- To: office-accessibility@lists.oasis-open.org
- Date: Thu, 10 Apr 2008 00:14:05 -0500
regrets.
I and Chieko are on a trip, unfortunately.
We are really interested in the NCAM/AFB
announcement. I hope we can get together at the next call.
Thank you.
Hiro
---------------------
Hironobu Takagi, PhD.
Accessibility Research
Tokyo Research Laboratory, IBM Research
+81-46-215-4557
E-mail: takagih@jp.ibm.com
Richard Schwerdtfeger <schwer@us.ibm.com> wrote
on 2008/04/09 17:46:01:
> ODF Accessibility SC Agenda April 10, 2008
> Please note your open action items. We will discuss
these on the call.
>
> Thursday 8am PT / 10am CST/ 11am ET / 3pm GMT
>
> US: 1-877-421-0030
> Toll: 770-615-1247
>
> Toll Free Toll
>
> UK: 0808-234-1969 +44 2070260533
> IBM Tie-Line: 421-0030
> IBM ITN: 2-421-0030
> 2-421-0035 from Europe
> Vo/IP Using SIP or IAX: telecon@a11y.org
>
> 21192119 aka a11ya11y is the mod code
>
> pc is 2119674 aka a11yorg
>
>
> USA 877-421-0030; 770-615-1247
> Austria +43 179576264
> Belgium 0800-7-3026; +32 22006114
> Denmark 80-888377; +45 38323070
> Finland 0800-914-630; +358 972519061
> France 0800-902366; +33 157323040; +33 157323041
> Germany 0800-181-6323; +49 6951709081
> Ireland 1800-558728; +353 16569209
> Italy 800-788634; +39 0269430413
> Netherlands 0800-022-8558; +31 202008077
> Norway 800-18373; +47 24159528
> Spain 900-95-1089; +34 912754171
> Sweden 020-799414; +46 850163259
> Switzerland 0800-564-331; +41 446545620
> United Kingdom 0808-234-1969; +44 2070260533
>
>
> IRC: http://irc.oasis-open.org
> channel: "&office-accessibility"
>
> Agenda: April 10 ODF Accessibility SC Meeting
> It has been a while since we have had a meeting.
This meeting is
> largely to synch up and start scheduling and get commitments to
> finishing up accessibility work on ODF 1.2 and its corresponding guidelines
>
> 1. Assign scribe and role call
> 2. Approve February 14 Minutes: http://www.oasis-open.
> org/apps/org/workgroup/office-
> accessibility/email/archives/200802/msg00006.html
> 3. Rescheduling Meeting Time
> 4. Work Items for ODF 1.2 specfications.
>
> Reference Document: ODF 1.2 Draft 6 http://www.oasis-open.
> org/apps/org/workgroup/office/download.php/25268/OpenDocument-v1.2-draft6.odt
> - requirements to the TC
> Note the timeline
> ODF 1.2 technical drafting complete May 2008
> ODF 1.2 public review June-July 2008
> ODF 1.2 approved as OASIS Standard - Sept 2008
> ODF 1.2 approved as an ISO standard - Summer
2009
>
> * [unassigned] 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".
> * 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"/>
> * Hiro to provide more information related to table headers (from
> http://www.oasis-open.org/apps/org/workgroup/office-
> accessibility/email/archives/200711/msg00007.html)
> * 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.?
> The request to the main TC: please ensure that this heading
> information is available & stable & in a relatively-easy to
discern way
> * Assign team members to review updated draft when it comes out.
>
> 5. Work Items ODF Accessibility Guidelines 1.1
> * Peter to wrap up ODF 1.1 Accessibility guidlines
http://docs.
> oasis-open.org/office/office-accessibility/v1.
> 0/cd01/ODF_Accessibility_Guidelines-v1.0.odt
>
> 6. Work Items ODF Accessibility Guidelines 1.2
>
> * Rich to 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.
> * Pete Brunet: Provide guidelines as to how to supply tracking
> change information to ATs.
> -> Malte & Pete & others have been looking at how
to expose
> document revision information in platform a11y APIs, so they can be
> exposed via IAcc2 and ATK/AT-SPI. Are converging on a specification.
> Miscellaneous Action items
> -------------
> * [unassigned] Can OOo be a good codebase for Marc to start
from
> for the Icon (which is ARM based)
> * Results: PeteB to set up a meeting at CSUN around the revision
> API (already looking to set up an IAcc2 meeting & an OpenA11y
meeting at CSUN)
>
> (See attached file: ODF_Accessibility_Guidelines_v1.0-NEW.odt)(See
> attached file: ODF_Accessibility_Guidelines_v1.0-NEW.pdf)(See
> attached file: ODF_Accessibility_Guidelines_v1.0-NEW.zip)
>
>
> 4. ODF Accessibility Guidelines for ODF 1.2
> - See action items below
> - Should we provide any direction on animations?
> 5. ODF 1.2 Draft 6 http://www.oasis-open.
> org/apps/org/workgroup/office/download.php/25268/OpenDocument-v1.2-draft6.odt
> - requirements to the TC
>
> Action Items for ODF Accessibility Guidelines for 1.2
> Group Actions
> Modify next version of accessibility guidelines
to ensure
> applications respond to system font and color settings.
> Add wording to the next revison of the accessibilty
guidelines to
> allow control of the animation rate of
> images in a presentation
> Modify 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.
>
> Janina actions: create new wording for reload delay (section 3.13.2)
> which would allow user agents to control the reload delay and to state
the
> WCAG requirements for content refreshing to prevent seizures. We
> need wording to provide control over flashing Here are some related
links
> http://www.w3.org/TR/2007/WD-WCAG20-20070517/#general-thresholddef
> http://www.w3.org/TR/2006/WD-UNDERSTANDING-WCAG20-20060427/#seizure-
> does-not-violate
>
> Pete Brunet: Provide guidelines as to how to supply tracking change
> information to ATs.
>
> Hiro: 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.
>
>
> Rich Schwerdtfeger
> Distinguished Engineer, SWG Accessibility Architect/Strategist
> Chair, IBM Accessibility Architecture Review Board
> blog: http://www.ibm.com/developerworks/blogs/page/schwer[添付ファイ
> ル "ODF_Accessibility_Guidelines_v1.0-NEW.odt" は Hironobu
> Takagi/Japan/IBM が削除しました] [添付ファイル
> "ODF_Accessibility_Guidelines_v1.0-NEW.pdf" は Hironobu
> Takagi/Japan/IBM が削除しました] [添付ファイル
> "ODF_Accessibility_Guidelines_v1.0-NEW.zip" は Hironobu
> Takagi/Japan/IBM が削除しました]
> ---------------------------------------------------------------------
> 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]