[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [office-accessibility] Agenda: OASIS ODF Accessibility SC CallMonday October 27th
Did some phone numbers change? Trying 0800-181-6323 from Germany => "number invalid" Malte. Richard Schwerdtfeger wrote, On 10/26/08 07:00 AM: > Dear Accessibility SC, > > I changed the time zone for CET. > > After a hiatus, we resume our schedule of meetings every other week of > the OASIS ODF Accessibility subcommittee, tomorrow/Monday October 27th, > at 7am PT / 9am CT / 10am ET / 3pm CET / 11pm Japan time. Please use our > usual (and unpublished) dial-in, and our usual IRC channel: > *&office-accessibility* at *irc.oasis-open.org * > > * > Suggested agenda:* > > 1. Approval of minutes from 6Oct08 meeting (attached, and also at: > _http://www.oasis-open.org/apps/org/workgroup/office-accessibility/email/archives/200810/msg00009.html_ > > 2. Determine if Janina still as trouble posting to the list. > > 3. Hiro to provide review of latest ODF 1.2 specification and also to > determine if there is a need to make use of its new metadata > > 4. Based on Hiro's review discuss way to submit change requirements to > the ODF 1.2 TC. > > 5. Discussion: Action plan for next rev. of ODF Accessibility Guidelines > based on Hiro's review > > 6. Action Items > > * Malte and Peter: Provide input on the above topic of integration of > the a11y guidelines into the suite of docs comprising the ODF 1.2 spec. > * Malte: Provide input on charts backed by disjoint cells: > > How does (or how will) OpenOffice provide access > to charts backed by disjoint cell ranges either > in a single or multiple tables? If this case be > done today, what are the examples?_ > __http://www.oasis-open.org/apps/org/workgroup/office/email/archives/200808/msg00054.html__ > __http://mediacast.sun.com/share/korn/chart-accessibility-challenge.ogg__ > __http://mediacast.sun.com/share/korn/chart-in-writer.behavior.ogg_ > > * Pete: Ask Symphony team about best practices for radio button groups > (see last action item above). Peter Korn to ask Orca team. > > What are the best practices for creating button groups? There are two > tags providing labeling: 1)form:frame and 2) form:fixed-text. In the > latter case, i.e. static text is labeling a group of buttons (rather > than the buttons being groups in a form:frame, would you be able to > implement an accessible hierarchy (including the proper relations) for a > button group? > > > 5. Other Action item from prior meeting > > * Janina to clarify text in section 3.4. Was this sent to Peter > * Janina to 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. > * Steve Noble to look at formulas specification identify data that would > update frequently, such as volatile formula information that would > require the Office application to inform the AT of updates sections. > Will complete by next meeting. Steve has moved on. Rich and Peter to > determine how to handle. > * Rich to provide base document for ODF 1.2 change specification > (starting with caption-id reference) to Mike Paciello. Mike is to own > the requirements document for ODF 1.2 which will be submitted to the ODF > TC. Rich is waiting on a decision as to where the ODF schema is to > reside (separate or within the base document). > > > > > Rich Schwerdtfeger > Distinguished Engineer, SWG Accessibility Architect/Strategist > blog: http://www.ibm.com/developerworks/blogs/page/schwer
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]