Skip to main content

Pass-thru HTML

Lotus Notes checkpoint 6.4

HTML added to Domino applications must follow the Web Accessibility Checklist guidelines.

Rationale

Techniques

Testing

 

Rationale

HTML content can be added to Domino application by importing, pasting or entering the HTML directly on the page or form. The HTML content must follow the applicable standards in the IBM Web Accessibility Checklist to ensure the code is accessible.

This checkpoint only applies to applications that will be deployed on the Web.

Back to top

Development techniques

The following techniques are the minimum required to meet Checkpoint 6.4 from the Lotus Notes Application Accessibility Checklist:

  • Multimedia. Audio content must be accessible to someone who is deaf or hard of hearing. Videos without descriptions are not accessible to the blind. For additional information on making multimedia content accessible, see the Multimedia checkpoint from the Web Accessibility Checklist.
    • Provide captions or transcripts of important audio content.
    • Provide transcripts or audio descriptions of important video content.
  • Do not use the <blink> or <marquee> elements to create blinking or flashing content. Flashing information may cause photosensitive epilepsy seizures in susceptible individuals. For additional information on blinking content, see the Blinking, Moving, or Flickering Content checkpoint from the Web Accessibility Checklist.
  • When a timed response is required, alert the user and give sufficient time to indicate more time is required. For additional information on making timed responses accessible, see the Timed Response checkpoint from the Web Accessibility Checklist.
  • When pass-thru HTML is used to add images in a Domino application, provide alternate text for the image. In the following example, the new.gif graphic is added to a view column if the document was created in the last five days. To make the image accessible, alt text is provided so a screen reader can speak the information to someone who is blind. When the image is encountered, the screen reader will say "new" since that is the alt text for the image.

    @If (@NOW > @ADJUST(@CREATED; 0;0;5;0;0;0); ""; "[<img src=new.gif alt="new">]")

Back to top


Testing techniques

Test the application to ensure that it complies with accessibility requirements.

Techniques

The following techniques are required to verify this checkpoint:
  Action Result
1. If the application includes multimedia content, follow the test techniques defined in the Multimedia checkpoint on the Web Accessibility Checklist. Pass:

  • Audio content is accessible to someone who is deaf or hard of hearing through an alternative format.
  • Video content is accessible to someone who is blind or visually impaired through an alternative format.

Fail:
  • Alternate accessible formats are not provided for audio content.
  • Alternate accessible formats are not provided for video content.
2. If the application includes blinking or flashing content, follow the test techniques defined in the Blinking, Moving, or Flickering Content checkpoint on the Web Accessibility Checklist. Pass:
The site does not include blinking or flashing content or the time interval of the blinking or flickering content is less than 2 Hz or greater than 55 Hz.

Fail:

The site includes blinking or flickering content between 2 Hz and 55 Hz.
3. If the application includes timed instructions, follow the test techniques defined in the Timed Responses checkpoint on the Web Accessibility Checklist. Pass:

The user is notified before instructions time out and given the opportunity to indicate more time is needed to complete the process.

Fail:
  • The user is not notified before instructions time out, so the information displayed on the screen is lost.
  • The user is notified before the instructions time out, but not given an option to request more time to complete the operation.

Back to top


©2001, 2008 IBM Corporation

Last updated February 08, 2008.

Previous

Checklist

Next