Web Accessibility - Included
Content
Documentation home
General
accessibility considerations. 1
Accessing Ebase presentation attributes. 1
See also: Web
Accessibility Home
This page documents all the accessibility issues relating to
HTML content that is included with an
Ebase Xi form - normally this content is included by specifying top, left,
right, bottom JSPs or using an Include Control or an
HTML Control, and the content is either in JSP or HTML format.
The following is a selection
of the main checkpoints from the W3C WCAG
1.0 guidelines that are applicable to all included HTML content. These apply
to HTML pages in general and are not specific to Ebase Xi. The numbers in
parentheses refer to the WCAG 1.0 guideline number. Items required to achieve
the W3C AA accessibility are marked as mandatory.
- Provide a text equivalent for every
non-text element. Mostly this entails adding an alternate text for all
images - this is a mandatory requirement (1.1)
- Ensure that all information conveyed
with color is also available without color.
This is a mandatory requirement (2.1)
- Ensure that foreground
and background color combinations provide
sufficient contrast when viewed by someone having color
deficits or when viewed on a black and white screen. This is a mandatory
requirement. (2.2)
- When an appropriate markup language
exists, use markup rather than images to convey information. This could be
alternatively phrased as: do not use
images that just contain text. This is a mandatory requirement. (3.1)
- Ensure that all HTML conforms to the
HTML Standard. This is a mandatory requirement. (3.2)
- Normally always use style
sheets to control layout and presentation, but also have the ability to
display without style sheets if they are not supported by the client
browser. This is a mandatory requirement. (3.3 and 6.1)
- Use relative rather than absolute
units in markup language attribute values and style sheet property values.
Use 'em' or '%'. This is a
mandatory requirement. (3.4)
- If there are any clickable links or
buttons, ensure these can be activated with the keyboard alone - i.e. not
using the mouse. This is a mandatory requirement. (9.2)
- Clearly identify the target of each
link. This is a mandatory requirement. (13.1)
- Use the clearest and simplest
language appropriate for a site's content. This is a mandatory
requirement. (14.1)
- Supplement text with graphic
or auditory presentations where they will facilitate comprehension of the
page (14.2)
- Create a style of
presentation that is consistent across pages (14.3)
See the W3C WCAG 1.0
guidelines for a more complete list.