Re: FW: OASIS Dockbook

[Norman Walsh <ndw@nwalsh.com>]

/ Andi Snow-Weaver <andisnow@us.ibm.com> was heard to say:
| Hi Norm,
|
| I'm glad to know that you did think about accessibility when developing it.
|
| Thanks for contacting me. I haven't reviewed this standard so it's hard for
| me to provide much helpful information. For a document format, here are
| some of the things to think about with regard to accessibility:
|
| - any non-text content (images, audio, video, etc.) must have a way to
| attach a text alternative to it. The text alternative is for users who
| can't see or hear.

Check.

| - the ability to provide semantic structure in the document is important -
| headings, lists, tables, etc.

Check.

| - the ability to define relationships between related components that can
| be programmatically determined is important. For example:
| --- identifying the row and column headers in simple tables (<th> elements
| in HTML)
| --- associating headers with cells in complex tables (id and headers
| attributes in HTML)
| --- identifying labels for form controls (<label> element in HTML)

Check.

| The ODF Accessibility subcommittee added 11 or 12 things to ODF 1.1 to
| correct accessibility deficiencies in ODF 1.0.

If you find anything that you think is missing, please let us know.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com>      | If you are hankering after
http://www.oasis-open.org/docbook/ | certainty, you are better advised
Chair, DocBook Technical Committee | to seek it in religion: the
                                   | stock-in-trade of science is not
                                   | certainty but doubt.--K.C. Cole

PGP signature