Web Accessibility

Ebase enables the creation of forms and web applications that meet the Web Content Accessibility Guidelines (WCAG) 1.0 produced by the World Wide Web Consortium, W3C under their Web Accessibility Initiative (WAI). A detailed description of the items contained within these guidelines and how these are met by Ebase is given in How Ebase meets the WCAG 1.0 Guidelines.

The objective of the WAI work undertaken by W3C is to ensure that, as far as possible, the advantages and facilities offered by the web are available to everyone and that certain groups are not disadvantaged. In particular, the following:

People who cannot see, hear, move, or may not be able to process some types of information easily or at all
People who may have difficulty reading or comprehending text
People who may not have or be able to use a keyboard or mouse
People who may have a text-only screen, a small screen, or a slow Internet connection
People who may not speak or understand fluently the language in which the document is written
People who may be in a situation where their eyes, ears, or hands are busy or interfered with (e.g., driving to work, working in a loud environment, etc.)
People who may have an early version of a browser, a different browser entirely, a voice browser, or a different operating system

More information on the general background and objectives of WAI can be found at the W3C WAI site.

It is important to understand that while Ebase enables the creation of accessible forms and web applications, it does not automatically guarantee this. In addition, the Ebase user needs to understand the underlying principles and guidelines to ensure that these are followed.

Ebase Support for Web Accessibility

How Ebase meets the WCAG 1.0 Guidelines

Describes in detail how Ebase meets the checkpoints in the WCAG guideline.

Ebase Designer Considerations

Describes in detail all accessibility considerations that Ebase user need to understand.

Options and Attributes

Describes the global options available.

Support for Browser Clients without JavaScript

Describes Ebase support for client browsers that do not support JavaScript.

Metadata Support

Describes the Ebase generic support for metadata.

Included Content

Describes all considerations for the creation of added additional content - e.g. HTML or JSP files

Web Accessibility References

The following are links to external sites containing accessibility information and are provided with no guarantees as to the accuracy of the advice provided.

W3C Web Accessibility Initiative

http://www.w3.org/wai

Syntax Checker

W3C HTML and CSS syntax checker: http://validator.w3.org/