OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office-accessibility message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [office-accessibility] Agenda: ODF Accessibility Subteam Meeting February 15, 2007


regrets for me tomorrow, but I second question #1

On 2/14/07, Janina Sajka <janina@rednote.net> wrote:
> Can I suggest two additional items of some urgency?
>
> 1.)     Our member status with Oasis.
> 2.)     Whether or not to hold an F2F around CSUN?
>
>
> Did we already deal with 2?
>
> Janina
>
> Richard Schwerdtfeger writes:
> >
> >
> > Greetings,
> >
> > Connection info:
> >
> > Thursday 9Nov; 8am PT / 10am CST/ 11am ET / 4pm GMT / 5pm CET
> >
> > Toll-free dial-in: 1-877-421-0019
> > Toll/International dial-in: 1-770-615-1380
> > Tie-line dial-in: 421-0019
> > Participant passcode: 710374
> >
> > IRC: http://irc.oasis-open.org
> > channel: "&office-accessibility"
> >
> >
> > I would like to propose for our agenda:
> >
> > 1. Roll call
> >
> > 2. ODF 1.1 Daisy Converter status - Dave Pawson
> >
> > 3. ODF 1.2 Current State, Future Planning
> >
> > This is very early but I would like the group to take a look at these and
> > see if there are any read flags.
> >
> > Here is the list of agreed to and proposed changes to ODF:
> > http://wiki.oasis-open.org/office/OpenDocument_v1%2e2_Action_Items
> > Here is the current draft:
> > http://lists.oasis-open.org/archives/office/200701/msg00016.html
> >
> >
> > 4. ODF Accessibility Guidelines Review by Becky Gibson - IBM:
> > Current draft:
> > http://www.oasis-open.org/apps/org/workgroup/office-accessibility/download.php/21789/ODF_Accessibility_Guidelines_16_11Jan07.odt
> >
> > Becky's comments:
> >
> > I would suggest rearranging the sections on physical impairments with and
> > without speech recognition.  I would put the section with speech
> > recognition before the one without speech recognition since you refer to
> > speech recognition in the section without. I had to re-read the start of
> > the section WITH speech recognition to figure out what was being referred
> > to.  For people who don't know about speech recognition it would be better
> > to put that section first before you refer to speech recognition.
> >
> > Section 2.3.2 - it seems odd that Windows / MSAA is not included in the
> > list of  Accessibility Frameworks - especially since you refer to MSAA in
> > the section 2.3.4!.  I realize that MSAA may not be a recommended framework
> > but it should at least be defined and explained - perhaps in a subsection
> > or something.
> >
> > In section 2.4 I would include the version of Firefox (1.5 or later).
> >
> > It seems odd that you are suddenly talking about XML in section 3.1. While
> > I realize that ODF is based on XML, it seems odd to not discuss that.
> > Perhaps it is assumed that the audience of this document is intimately
> > familiar with the ODF specification and format?
> >
> > There seems to be a fair amount of repetition in section 3.2 - the examples
> > in 3.2.5 overlap with previous sections. Section 3.2.1 is about more than
> > just imagemaps.   I think these sections need to be reworked and
> > consolidated.
> >
> > The table example is 3.27 (or maybe it is 3.3 - the section has both
> > labels) is disorienting for a visual user!  I don't get what is attempting
> > to be explained here.
> >
> > Section 4.4 intro - you might want to define DAISY. I see that DAISY is
> > included in the glossary but when reading the document I had no idea that
> > DAISY was included in the document -there should be some kind of link or
> > association between the terms use in the document and the glossary entry
> > for that term.
> >
> >  I'm also not sure what the tables in this section are trying to convey?
> > Some columns have no data - is they because there is no equivalent?  Needs
> > a better explanation.  This entire section seems to focus mostly on
> > conversion to HTML.  Perhaps the sections can be better broken up to better
> > refer to the conversion being undertaken - it seems to be a bit jumbled
> > together.
> >
> > 5. Suann Nichols review - IBM
> >
> > (See attached file: ODF GL Feedback.odt)
> >
> >
> > Rich Schwerdtfeger
> > Distinguished Engineer, SWG Accessibility Architect/Strategist
> > Chair, IBM Accessibility Architecture Review  Board
> > blog: http://www.ibm.com/developerworks/blogs/page/schwer
>
>
> --
>
> Janina Sajka                            Phone: +1.202.595.7777
> Partner, Capital Accessibility LLC      http://CapitalAccessibility.Com
>
> Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada--Go to http://ScreenlessPhone.Com to learn more.
>
> Chair, Accessibility Workgroup          Free Standards Group (FSG)
> janina@freestandards.org                http://a11y.org
>


-- 
dc
-----
David Clark
Database Developer
Institute for Community Inclusion (http://www.communityinclusion.org/)
david.clark@umb.edu
(617)  287-4318


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]