[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: 13July06 Draft ODF 1.1 spec. accessibility appendix
Greetings
Sorry for the delay. Below and attached is the draft accessibility
implementation appendix for the ODF 1.1 specification, coming out of our
con-call yesterday.
Let's please make this the bulk of our meeting next week Thursday.
Regards,
Peter
------------------------
Outline of the draft Accessibility implementation Appendix for the ODF
1.1. specification document
July 13, 2006
Section I: Background & Overview
*
Introduction
*
What is Accessibility?
<note applications of accessibility technology for folks w/out
disabilities>
[Rich: how far do we want to go with this?]
[David: length depends in part on TC feedback: how long can this
document be?]
*
Importance of the accessibility of the ODF application
*
Importance of ensuring authors encode accessibility information
into documents
*
(special commentary on alternate presentations of documents [e.g.
DAISY]?)
*
[Hiro: suggestion to consider the chart at
http://www.w3.org/WAI/guid-tech.html to show the relationship
between AT, players, authoring tools, etc.]
Section II: ODF application accessibility
*
<Reference Section 508 1194.21 guidelines> [Rich is concerned with
referencing only 508; either do all, or do not do 508] [Peter
prefers to reference lots; David prefers referencing none; Rich as
well – final decision on this was tabled for later discussion]
*
Keyboard navigation/mouseless
Refer to standard keyboard gestures on various desktops
Must always have visible indication of focus
Conventions for selection, caret navigation, etc.
*
Theme support (including OS fonts & colors)
*
Interoperability with AT [David Clark: this should be about
programmatic access; stay away from the “does it work with JAWS”]
*
Note: all of this applies to your help system as well!
*
Special issues for Web-based ODF applications
Section III: Document content accessibility
*
ALT text (in all of the various places they can go)
Include suggested UI for setting them
*
Importance of proper encoding of document structure (headings,
subheads, etc.)
*
Soft page break generation
*
Keyboard focus order for object contents (in slides, in graphics)
Section IV: Special issues when converting other formats to ODF
*
ALT text preservation (from MS-Office)
*
accessibility meta-data [Rich? What exactly do you mean by this?]
*
Preservation of structural semantics
*
Page breaks,
*
Headers
*
Heading levels
*
Forms elements
*
Table and and table structure: ( headers, rows, etc.)
Section V: Special issues for audio-based ODF applications
*
Desktop “self-voicing” setting
*
Ensure support for volume control [Rich?]
*
Ensure support for all speech capabilities of the TTS engine [Rich?]
Section VI: Glossary of terms
[From Cheiko's draft]
User agent
- any type of software tool, which reads or writes ODF files
Office editor
- a user agent with edit capability for "human" users
- an authoring tool
Office reader
- a user agent without edit capability for "human" users
Voice office editor
- a user agent with edit capability for non-visual access users
- an office editor
- an assistive technology
- an authoring tool
Voice office reader
- a user agent without edit capability for non-visual access users
- an office reader
- an assistive technology
Generator
- a user agent, which generates ODF files on client side or server side
- an authoring tool
Converter
- a user agent, which converts some types of documents into ODF files or
from ODF files to some types of documents
- an authoring tool
Accessibility checker (evaluation tool)
- a software tool, which checks accessibility of ODF files
- a user agent?
Screen reader
- a software to read aloud office editor or office reader screen for
non-visual access users
- not a user agent?
- an assistive technology
Draft accessibility appendix to ODF 1.1 13July06.odt
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]