IBM Skip to main contentUnited States
   Home  |  Products & services  |  Support & downloads  |  My account
. Go to Select a country
     
  Accessibility Center  
  Product Solutions  
  Resources  
  Events  
  Guidelines  
  · Software  
  · Web  
  · Java™  
  · Lotus Notes  
  · Hardware  
  · Peripherals  
  Law & disabilities  
  Site map  
  Information for  
    Persons with disabilities  
    Employers / HR  
    Institutions / schools  
    Service providers  
    Developers  
     
  Order accessibility products  
Lotus Notes Accessibility Guidelines

Lotus Notes Application Accessibility

Use this checklist for:

  • Notes 4.x, R5 or Notes 6 applications that will be deployed on the Notes Client
  • Notes 4.x, R5 or Notes 6 applications that will be deployed on the Notes Client or the Web

Understanding Accessibility

If you are new to accessibility, review "Understanding Accessibility" before completing the checklist.

Lotus Notes Application Accessibility Checklist

Techniques pages, accessed via the link in each checkpoint, may contain more recent updates than the checklist itself. Be sure to review the techniques pages for the latest accessibility guidance. For convenience in completing the Notes accessibility checklist, save this page and edit the HTML file.


Lotus Notes Application Accessibility Checklist - Version 3.2

1 Navigation. Yes No
Planned
N/A
Comments
1.1 Provide keyboard equivalents for all navigator actions.    
1.2 Provide methods for skipping over navigation links to get to the main content of the Web page.    
1.3 Provide a title for each frame.    
2 Buttons. Yes No
Planned
N/A
Comments
2.1 Include all action buttons in the appropriate menu.    
2.2 Provide text labels for all buttons.    
3 Graphics, Image maps and Links. Yes No
Planned
N/A
Comments
3.1 Provide alternate text for important graphics.    
3.2 Provide alternate text for image maps and image map hotspots.    
3.3 Make text pop-ups directly accessible or provide an alternative.    
4 Views. Yes No
Planned
N/A
Comments
4.1 Include views in the View menu if the application uses navigators.    
4.2 Use color as an enhancement, not as the only way to convey information or indicate an action.    
4.3 Provide a visible selector for embedded outlines and views.    
5 Forms. Yes No
Planned
N/A
Comments
5.1 Include forms in the appropriate action menu.    
5.2 Associate labels with editable fields on forms using field help or HTML TITLE.    
5.3 Provide a descriptive title for each form and page.    
5.4 Avoid the use of animated tables.    
5.5 Use the TH element to mark up table heading cells on Web pages. Use the headers attribute on cells of complex data tables on Web pages.    
5.6 Avoid the use of rich text lite fields.    
6 Applets, JavaScript and Style Sheets Yes No
Planned
N/A
Comments
6.1 Provide alternate content for Java applets which are not accessible.    
6.2 Provide content for JavaScript which is keyboard accessible. If the content is not accessible, provide an alternative.    
6.3 Web pages must be readable without requiring style sheets.    
6.4 When HTML content is added to Domino applications, follow the IBM Web Accessibility Checklist guidelines.    
7 Documentation. Yes No
Planned
N/A
Comments
7.1 Provide documentation on all accessibility features including keyboard access.    
8 Verify Accessibility. Yes No
Planned
N/A
Comments
8.1 Test for accessibility using available tools.    

©2001, 2003 IBM Corporation

References

 

  About IBM  |  Privacy  |  Legal  |  Contact