mins 070405

["Dave Pawson" <dave.pawson@gmail.com>]

Attached, html format.

Great meeting.

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk

Title: OASIS ODF Accessibility SC Meeting

OASIS ODF Accessibility SC Meeting

Date: 2007-04-05T15:04:09.0Z
Time: 1500Z
Venue: Telcon
Date: 2007-04-05T15:04:04.0Z

Version: 1

Attendees

• Dave Pawson
• Chieko Asakawa - late joining
• Rich Schwerdtfeger - chair
• Janina Sajka
• Mike Paciello
• Hironobu Takagi
• Tatsuya Ishihara
• Pete Brunet

Apologies

• David Clark
• Malte Timmerman
• Peter Korn

Scribe(s): Dave Pawson

Agenda

Item. Roll Call

Item. Outstanding actions

Item. Should there be a note in our Guidelines document emphasizing how authors should properly use structural markup?

Item. Should the group do a "ODF Authoring Guidelines" Document for ODF 1.2?

Item. Outstanding issues for the ODF Application Accessibility Guidelines before sending to Mac

Item. Should we talk with Kurzweil or Freedom Scientific reqarding ODF 1.2 features we should add for Learning and Cognitive Disabilities (thinking of Kurzweil 3000 and WYNN)?

Item. Presentations - (Chieko/Hiro) How should we incorporate information from business presentation research to assist PWDs?

1  Roll Call, previous minutes

DISCUSSION: Review & approve previous minutes.

• Deferred to next meeting - approval of CSUN minutes.

2  Structured documents in ODF

DISCUSSION: RS. Should there be a note in our guidelines.

• DP. Goal is generation of structured documents in XML.
• RS. Possibly in section 3. Need for authors to follow guidelines and properly provide structural information.
• JS. yes, need correct structure to provide good accessibility. We expect to provide thorough guidance in future editions. Could be pointers.
• DP. Suggest note in this version, more later.
• MP. Have to add a note for this document if we commit to an authoring guidelines. More info the better. Major issue is lack of real awareness on part of authors and publishers. Generally not public enough. Not pervasive enough. Create a small bookshelf.
• DP. Could also apply to Word. Is anyone else working in this area. E.g CNIB. We might work together.
• RS. Implementation should be specific to ODF.
• JS. We are putting responsibility on end user. Should this be an implementor issue? Author should still be in charge, but implementers can help.
• MP. Could use prompting notion, implicit or part of the application. If an author turns it on, could be very easy! Or validation afterwards. App should support A11y prompting in UI. Control of that is up to the author. If available, then control is up to user.
• JS. Agree.
• RS. Should we extend to how the author does this, or say that authoring tools should check for inconsistancies.
• DP. how to get this to implementors.
• RS. Structural testing won't be in for 1.2
• MP. From implementors its just work flow
• RS. They need our leadership to show what the workflow should look like.

Action item: Draft outline of workflow

Who? MP

Due date: When possible.

3  Should the group do a "ODF Authoring Guidelines" Document for ODF 1.2?

DISCUSSION: RS. Are we OK for a committment.

• PB. More we have for authors the better.
• RS, DP, yes.
• JS. Authoring guidelines 2.0 could be substantial.
• MP. We should take an approach similar to TITAC, plain language by tech writers, communicators. To make a better document. Michelle Budris is a tech writer, there's a great resource. There are others also. Time will be the challenge.
• RS. An informative document.

4  Outstanding issues, Accessibility Guidelines

DISCUSSION: RS. Status? Authoring tool structure is outstanding? Just DP RS inputs to be added.

5  Should we talk with Kurzweil or Freedom Scientific reqarding ODF 1.2

DISCUSSION: RS. FS have a product, what you need now. For people with learning difficulties. Kurzweil has a product. What could a document provide that make life easier.

• RS. E.g. personal bookmarks and common landmarks for navigational purposes.
• MP. Already supports bookmarks, but little on their use. Didn't address it as a navigational aid. Lots of school teachers need to deal with this. use cases wern't quite clear, we asked for these to develop a solution.
• RS. Good if we talk to these two companies.
• All. Agreed. We need input from these companies on what makes it easier. Action RS.

Action item: Obtain input from these two companies

Who? RS

Due date: Next week.

6  Presentations - (Chieko/Hiro)

DISCUSSION: Hiro joined. RS. Look at MP minutes please,

• RS. What are next steps re presentations.
• HT. Will sent presentation to list. We need to think about author work load. Considering feasible method of adding meta data. Would like to use existing tags, e.g. object. Can update proposal in a few weeks. Focussing on metadata for connectors. Also for formal vector graphics.
• HT. Will check soon.
• MP. CSUN minutes update to reflect comments.
• RS. I'm out next week. Back Thursday, HT may set up agenda. Assume PK back next week.

Action item: Talk to Jon Garnder, what can we do to content to help people who are blind

Who? JS

Due date: Next week.

Action item: Send proposal to group

Who? HT

Due date: April 25th.

The Oasis irc server is irc.oasis-open.org, channel &office-accessibility

Summary of Actions

MP

Action item: Draft outline of workflow

Due date: When possible.

RS

Action item: Obtain input from these two companies

Due date: Next week.

JS

Action item: Talk to Jon Garnder, what can we do to content to help people who are blind

Due date: Next week.

HT

Action item: Send proposal to group

Due date: April 25th.