[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Agenda ODF Accessibility Subteam meeting
Greetings,
I believe that everyone in the U.S. and Western Europe went through a
time change this past weekend - all an hour later than before - making
the subject line times accurate.
Connection info:
Thursday 9Nov; 8am PT / 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. Approval of Minutes November 9 meeting (attached).
3. IBM and FSG Announce of IAccessible2
http://www.freestandards.org/en/Accessibility/IAccessible2
3. ODF Accessibility Guidelines Work assingments
Comments from Mak (attached), Becky Gibsion and SuAnn Nichols (attached),
Comments from Rich, Dave Pawson, and Dave Clark below
4. Daisy Implementation Status (Yes these are old) - Dave Pawson
=======================================
Rich's comments
Some comments on Mak's comments.
I believe the wording Mak suggests is a good idea in order to address a broader audience.
Section 1.2.2.3 - It is a caret and not a cursor. On most systems the cursor is the mouse pointer.
Section 1.2.2.4 -
People with minor physical impairments have a variety of issues that prevent them from using the full keyboard or mouse easily. In order to support such users, complete ODF application usage and document manipulation should be possible ?? user friendly ?? without using the mouse.
Suggested rewording to reflect WCAG 2.0:
People with minor physical impairments have a variety of issues that prevent them from using the full keyboard or mouse easily. In order to support such users, all functionality of the content is operable in a non-time-dependent manner through a keyboard interface, except where the task requires analog, time-dependent input.
Section 1.2.2.5
Suggest rewording: Advanced on-screen keyboard software can actually extract the menu structure of the ODF application, the toolbar elements, and even the 'manipulable user?? user friendly?? interface elements' and place them on the software “keyboard” where the user can choose them.
To: Advanced on-screen keyboard software can actually provide remote access to accessible menus, toolbar elements, and other UI componentry on the software “keyboard” where the user can choose them.
I don't understand what Mak means by ?? “randomly” can be an appropriate word??
Section 1.2.2.6
Here is a reference for ASR: http://www.netac.rit.edu/publication/asr.html
Section 2.1
Common keystrokes Windows XP: http://www.rnib.org.uk/xpedio/groups/public/documents/PublicWebsite/public_rnib003585.hcsp
common keystrokes Macintosh: http://docs.info.apple.com/article.html?artnum=75459
There should be one on the Gnome site - Can't find it.
Section 2.3
Ineroperaability is a commonly used term.
Author of this section should fill in the API piece.
This bug showed up again in open office 3.2.5 A few examples
Section 4.2.2
Figure X Visual Rendering of an ODF list
Section 4.2.3
The standard landmark of contentinfo - Do not accept Mak's deletion of info as it is incorrect.
Section 4.2.4
Addressing Mak's comment about meta data. No additional meta data is required as the element presentation:notes constitutes the landmark
Mak introduces a Section 5.3.x but there is not section 5.3
5.3.1 Soft Page Breaks and Hard Page Numbering
===========================
Dave Pawson Comment
> Section 1.2.2.4 -
>
> People with minor physical impairments have a variety of issues that prevent them from using the full keyboard or mouse easily. In order to support such users, complete ODF application usage and document manipulation should be possible ?? user friendly ?? without using the mouse.
>
> Suggested rewording to reflect WCAG 2.0:
>
> People with minor physical impairments have a variety of issues that prevent them from using the full keyboard or mouse easily. In order to support such users, all functionality of the content is operable in a non-time-dependent manner through a keyboard interface, except where the task requires analog, time-dependent input.
dp. This isn't good English Rich? Content doesn't have functionality,
applications do?
How about
People with minor physical impairments have a variety of issues that
prevent them from using the full keyboard and or mouse easily. In
order to support such users, all the functionality of the application
should be operable in a non-time-dependent manner through a keyboard
interface, except where the task requires analog, time-dependent
input.
==========================
Dave Clark Comments
After reading the first 10-15 pages of Mak's edits, it occurs to me
that our glossary needs some more basic concepts that we al take for
granted, like:
caption vs subtitles -- never occurred to me that these may be
conflated by some.
caret/cursor/insertion point
compatibility vs interoperability
============================
(See attached file: 061109.html) (See attached file: ODF_Accessibility_Guidelines_mak_rev_30 Nov_06.odt)(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
OASIS ODF Accessibility SC MeetingAttendees
Apologies
AgendaItem. Roll Call Item. Review & approve previous minutes Item. Outstanding actions Item. Guidelines document: what remains before we post it, give it to our volunteer editor? Item. RNIB conversion of ODF 1.1 to DAISY 1 Roll CallDISCUSSION: Review & approve previous minutes.
Action item: Seek earlier time on list Who? RSDue date: Next week. 2 Daisy Conversion statusDISCUSSION: RS. IBM have submitted certification.
3 User variables on diskDISCUSSION: DP. Explained the iteroperability issues.
The Oasis irc server is irc.oasis-open.org, channel &office-accessibility Summary of Actions
|
ODF_Accessibility_Guidelines_mak_rev_30 Nov_06.odt
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Date: 2006-11-09T15:55:09.0Z
Time: 1600Z
Venue: Telcon
Date: 2006-11-09T15:55:14.0Z
Version: 1