Portal v6.1.5 Accessibility features

 

+

Search Tips   |   Advanced Search

 

Accessibility features help users who have a physical disability, such as restricted mobility or limited vision, to use software products successfully.

WebSphere Portal v6.1 5...

• Supports installation through a command line interface known as console mode. This is the accessible equivalent of installing by using the graphical user interface.

• Supports interfaces commonly used by screen readers and screen magnifiers (Windows only)

• Supports use of screen-reader software and digital speech synthesizers to hear what is displayed on the screen.

• Can be operated using only the keyboard

• Allows the user to request more time to complete timed responses

• Supports customization of display attributes such as color, contrast, and font size

• Communicates all information independently of color

• Supports the attachment of alternative input and output devices

• Supports alternatives to audio information

• Supports adjustable volume control

• Does not flash the screen at rates that could induce epileptic seizures

• Provides documentation in an accessible format

• For best results when using a screen reader to view WebSphere Portal, use Freedom Scientific JAWS 10 or higher and Firefox 3 or higher.

The documentation includes the following features to aid accessibility:

• All documentation is available in HTML formats to give the maximum opportunity for users to apply screen-reader software technology.

• All images in the documentation are provided with alternative text so that users with vision impairments can understand the contents of the images.

When appropriate, the documentation for specific product features contains additional information about accessibility.

See the IBM Human Ability and Accessibility Center for more information about the commitment that IBM has to accessibility:

Section 508 Standards

Items from Section 508 of the Rehabilitation Act Amendments of 1998...

1. Scripting Languages

   If pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.

2. Color

   Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. Use bold or italics instead.

3. Multimedia

   Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

   Elements in a page that need textual representation...

   • Flash animations
   • Movie clips
   • Power Point slides
   • Other video or audio media

4. Row and Column Headers

   Row and column headers shall be identified for data tables. HTML defines a special tag for table row and column headers. Use the TH tag for any cell that is a row header.

5. Table Data Cells

   Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. Explicitly define which header each cell goes with. Not requried for simple tabular data.

6. Style Sheets

   Documents shall be organized so they are readable without requiring an associated style sheet. Pages have to be readable if someone chooses not to use the style sheet. You can turnoff style sheets in any browser to get an idea of what your pages look like without style sheets.

7. Server Side Image Maps

   Redundant text links shall be provided for each active region of a server-side image map.

   Use client-side image maps is possible. For Server-Side image maps, include a text link to every possible url the server-side image map might take the user.

8. Client Side Image Maps

   Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.

9. Frames

   Frames shall be titled with text that facilitates frame identification and navigation.

10. Screen Flicker

    Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.

    Verify animated graphics do not create a blinking or flickering effect.

    Graphics cannot "blink" in excess of twice per second.

11. Text Only Version

    A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.

12. Applet Links

    When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through.

    If a page requires a plug-in, link to to the download for that plug-in on every page that uses it. The plug-in itself must comply with other "non-web" software accessibility standards.

    The content you make for that plug-in must also be compliant when used in a compliant plug-in.

13. Electronic Forms

    When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.

    The user should be able to tab through the items in a logical order.

    If your form uses the "label tag", associate these to a text reader.

14. Repetitive Links

    A method shall be provided that permits users to skip repetitive navigation links.

    Provide anchor links to make pages more accessible when rendered in a "text only" view. You can attach these anchor links to "spacer" or "invisible" images with proper alt text, so that users that get a text only view know what the links are for and users that don't need them won't see them.

15. Redirects

    When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

    Meta and JavaScript redirects should be greater than ten seconds, or more, if there is a lot of text to read.

    The user needs time to react and should have a choice to go "back".

16. General - Text Equivalencies

    A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).

    Many images in a web page's design might be strictly structural in nature that can have empty "alt" text All images in a site must have an alt attribute, even if it's blank.

    If an image that does need alt text (a photo for example) would require an especially long text to describe it, you can create a "D- link".

Parent topic:

Product overview

Related concepts

Accessibility and keyboard shortcuts in the information center