[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: OASIS ODF SC meeting minutes, 11Oct07
Greetings, I just realized I never sent out the meetings of our last meeting (oops). They are attached below. We said that we would not meet until Hiro had completed his action item, which he promised to do in the month of October. Given that we haven't heard from him, I suggest we NOT meet tomorrow. Regards, Peter Korn Accessibility Architect, Sun Microsystems, Inc. ============================================================ Attendees ---------- Rich Schwerdtfeger Peter Korn Pete Brunet Janina Sajka Malte Timmermann Steve Nobel Dave Pawson Agenda: September 6 ODF Accessibility SC Meeting ------------------------------------------------------ 1. Assign scribe and role call -> done, Peter Korn 2. Approve September 27 Minutes. Janina to post. -> Approved 3. Review Open Action Items -> Done (see below) 4. Hiro's review progress of the ODF v1.2 Draft 6 http://www.oasis-open.org/apps/org/workgroup/office/download.php/25268/OpenDocument-v1.2-draft6.odt -> Skipping; no Hiro and his AI deadline hasn't passed yet 5. Animations - We should discuss animation accessibility soon in our SC - perhaps at our next meeting. Questions we should explore include ways to tag the animation with ALT text descriptions, suggested UI for authors to do this, guidelines for when animations should be so tagged (does every animation need a description? is there a way to indicate 'non-informational/decorative animations' as such, so the user knows they exist and knows they needn't care about http://lists.oasis-open.org/archives/office-accessibility/200709/msg00014.html <http://lists.oasis-open.org/archives/office-accessibility/200709/msg00015.html> -> Discussion led by Dave Pawson: under what circumstances does a blind user want to know about "decorative" animations? [CONCLUSION] -> Interstitial animations (between slide switching) is fine as is -> Objects on a slide that are animations are fine, so long as you can have ALT text on them & TAB to them -> Objects on a master slide that are animations are fine, again so long as you can have ALT text on them & TAB to them Previous Open Action Items ---------------------------- 1. Peter Korn to post final ODF 1.1 Accessibility Guidelines -> Almost there... 2. Dave Pawson: look at HTML example on slide #3 of Hiro, to see how we can encode the "San Jose" stuff in ODF (see Hiro's e-mail http://www.oasis-open.org/apps/group_public/email/office-accessibility/200708/msg00005.html <http://www.oasis-open.org/apps/group_public/email/office-accessibility/200708/msg00005.html> ) -> AI is done. See: http://lists.oasis-open.org/archives/office-accessibility/200708/msg00008.html 3. Rich: I will ask when 1.2 is coming out and how many more drafts we might expect. i.e. When we should do our review. action rich -- to contact Robert Weir -> No clear & final answer; more reviews to come, but not a lot of changes expected. -> Rich: doesn't see a lot of new work in these drafts for us to review -> Peter: feels an analysis of the metadata proposal being worth a review 4. Action Hiro: End of October is good. -> [action was actually for Hiro to do a review of draft #6 of the ODF v1.2 spec.; answer was "End of Oct. is good"] 5. (From August 23 meeting) - Group Actions # Modify next version of accessibility guidelines to ensure applications respond to system font and color settings. # Add wording to the next revision of the accessibility 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. -> Skipping these; waiting on the review action (#5) 6. (From August 23 meeting) - Janina to 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/2007/WD-WCAG20-20070517/#general-thresholddef> # http://www.w3.org/TR/2006/WD-UNDERSTANDING-WCAG20-20060427/#seizure-does-not-violate <http://www.w3.org/TR/2006/WD-UNDERSTANDING-WCAG20-20060427/#seizure-does-not-violate> -> Janina will have this done by next week 7. (From August 23 meeting) - Pete Brunet review review section 4.6 of the ODF 1.2 specification and see how an application should supply tracking change information to an AT. Write proposal on how this should be addressed in the accessibility guidelines -> Pete Brunet: Belief is that -> Active discussion in exposing this via accessibility APIs (in the IAccessible2 mailing list); no consensus yet on how to do this - more study needed -> Malte: OOo is not exposing changes information via attributes New Action Items ------------------ 1. Consider a formal comparison to OOXML on a11y in ~6 mos. from now Next meeting will be when Hiro is ready; that might be next week, might be after that.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]