Important note: This Wiki page is edited by participants of the RDWG. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.

View source for Static Documents on the Web: Document Accessibility

← Static Documents on the Web: Document Accessibility

Jump to: navigation, search

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in one of the groups: Users, 106, 47076-chairs.

You can view and copy the source of this page.

[Brief synopsis of 1-2 sentences]

== Contacts ==
Page author(s): Klaus Miesenberger, Andrea Petz

Other contact(s): Shawn Henry

== Keywords ==
Guidelines, Static Documents, Structure & Design, File Formats

[[Category:Template]]

== Description ==
Many rules, guidelines and recommendations have been developed to help authoring and publishing information on the internet so that it can be read and used by the broadest audience possible. Following those rules and also everyday experiences, it becomes clear that often the information needed is too long or in an other way not adapted to be displayed on-line and needs publication via download. If those documents are not structured and design in an accessible manner, the effect of the whole website accessibility is subverted, leading to barriers and frustration.

== Background ==
A lot of research has been done concerning static document accessibility for including accessibility of widely used file formats (e.g. pdf, doc, odd, xls), providing specialised formats (e.g. DAISY)and conversion tools, over accessible adaptation of graphical contents to language adaptations (Easy-to-Read). Even if web accessibility guidelines are implemented on a page, documents and information available via download are not.
There are many reasons for this break in the eAccessibility chain. Web authors simply don't take care on this issues as document authors are other people. Often documents can not be changed nor copied due to IPR reasons. Very often the core information and final target a user is searching for on a web page is not accessible. Also basically accessible websites loose their benefit because of inaccessible documents are attached.
Many people are not aware of this problems and accessible templates (e.g. for creating accessible .pdf files that both, comply with IPR considerations and nevertheless are accessible for screenreaders).
Not only complicated documents, like .pdf forms to be filled in and saved / printed by users - often connected with watersigns and or digital signatures or certificate servers but also basic things are often an unsurmountable barrier for the user / client. Besides basic access to the content also the  complexity of design and language use often lead to serious usability/accessibility problems.

== Discussion ==
# Are available rules/guidelines for document accessibility sufficient?
# Are rules for accessible webdesign adaptable to accessible documents?
# What different filetypes are used to display further information to be downloaded and how is accessibility supported in design and editing tools?
# What filetypes would be best adapted / most accessible for the broadest possible user group?
# What filetypes would be best for information providers (IPR / Security, / Ease of design, use)?
# What basic rules make the difference in terms of document accessibility?
# Are there any "benchmarks" that have to be reached to make a document accessible for a most diverse range of providers AND user groups (like flexibility in display and style implemented via the usage of CSS on websites) e.g.
## Filetype (most flexible .html vs. IPR and CI implemented with not accessible, not extractable, graphical .pdf)?
## Structure (quick overview with clearly and consistenly implemented headings and paras)?
## Typesetting (in conjunction with clear and consistent structuring) and typography?
## Representation / Explanation of grahical contents (between superfluous statements and urgently needed additional information)
# What about "specific content" - e.g. maps / schedules / mathematical / statistical / language & linguistic / scientific information / music scores / documents?
# What about "specific structures" - e.g. maps / tables / dictionnaries?
# Progress and problems in including accessibility in document editors and design tools, including guidance: Is there a need or even a possibility to design / draft a template for content providers that solves all of the above issues?
# Availability and progress in conversion and repair tools?
# How to best promote and reach out for better document accessibility as an integral part of web accessibility: benefits, tools and legislation (e.g. NIMAS, ETIN)

Added by --[[User:Sharper|Simon Harper]] 17:47, 18 October 2012 (UTC)

https://www.w3.org/WAI/UA/tracker/actions/759 - 
ACTION-759: Forward a request to RDWG that they suggest that students looking for projects build an extention that allows people to put navigation marks in a page - 1.8.12
Forward a request to RDWG that they suggest that students looking for projects build an extention that allows people to put navigation marks in a page - 1.8.12


== References ==
# Abu Doush, I. et al. "Non-visual Navigation of Spreadsheet Tables", Springer LNCS 6179, p.108ff
# Ball, S. and Sewell, J. "Accessibility Standards Are not Always Enough: The Development of the Accessibility Passport", Springer LNCS 5105, p.264ff
# Contini, E. et al. "A Semi-Autmatic Support to Adapt E-Documents in an Accessible and Usable Format for Vision Impaired Users", Springer LNCS 5105, p.242ff
# Crombie, D. "Design for Adaptive Content Processing", Springer LNCS 6179, p. 1ff
# Crombie, D. "Accessible Content Processing", Springer LNCS 5105, p.234ff
# Darvishy, A. et al. "A Flexible Software Architecture Concept for the Creation of Accessible PDF Documents", Springer LNCS 6179, p.47ff
# Kopecek, I. et al. "Annotating and Describing Pictures", Springer LNCS 6179, p.108ff
# McMullen, D.; Fitzpatrick, D. "Generating Daisy Books from OpenOffice.org", Springer LNCS 6179, p.5ff
# Ruemer, R. et al. "New Production and Delivery Systems for Pupils with Disabilities in Austria as a Chance for Higher Quality Output", Springer LNCS 6179, p.43ff
# [http://www.icchp.org/programme2012/ ICCHP 2012 - actual papers and presentations, to be published in Springer LNCS 7382 and 7383, Last: May 2012.]
## [http://www.icchp.org/programme2012/thursday#track2 ICCHP 2012 - STS Access to Math and Science, Last: May 2012.]
## [http://www.icchp.org/programme2012/thursday#track1 ICCHP 2012 - STS PDF/UA - A new Era for Document Accessibility, Last: May 2012.]
## [http://www.icchp.org/programme2012/thursday#track1 ICCHP 2012 - Document and Media Accessibility, Last: May 2012.]
## [http://www.icchp.org/programme2012/thursday#track5 ICCHP 2012 - Track ULD: Universal Design of Documents Including Accessible Graphics in Tertiary Education, Last: May 2012.]
## [http://www.icchp.org/programme2012/wednesday#track5 ICCHP 2012 - STS Putting the Disabled Student in Charge - Alternative Approaches to Alternative Formats, Last: May 2012.]

Back to the [http://www.w3.org/WAI/RD/wiki/ list of topics].

Return to Static Documents on the Web: Document Accessibility.

Retrieved from "https://www.w3.org/WAI/RD/wiki/Static_Documents_on_the_Web:_Document_Accessibility"

View source for Static Documents on the Web: Document Accessibility

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Navigation

Tools