Following is a quick tip from the AD208 : End-to-End Quality Processes for Top Notch XPages Apps session from IBM Connect 2014. In the tip, speakers Martin Donnelly, Brian Gleeson, and Padraic Edwards cover XPages accessibility for the latest WCAG 2.0 and Section 508 standards, including why you should care about it, tools to get started, and guidelines and best practices.
2. 22
IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole
discretion.
Information regarding potential future products is intended to outline our general product direction and it should not be relied
on in making a purchasing decision.
The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver
any material, code or functionality. Information about potential future products may not be incorporated into any contract.
The development, release, and timing of any future features or functionality described for our products remains at our sole
discretion
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The
actual throughput or performance that any user will experience will vary depending upon many factors, including
considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage
configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve
results similar to those stated here.
Please Note
3. 2828
XPages Accessibility
Why should we worry about accessibility?
Millions of people worldwide live & work with a disability
IBM requirement
Extend market reach
Requirement for Government services
Promotes good Design Practices
Promotes better usability
6. 31 Lower images sourced from: www.colourblindawareness.org
Colour blindness example
7. 3232
XPages Accessibility
A brief overview
■ XPages must be compliant to WCAG 2.0 level A and level AA, and US Section 508
standards
■ XPages is the recommended accessible solution for IBM Domino Web Apps
■ There is no single solution but rather choose an accessible path
■ Make use of the tools, techniques and documentation available
– A good starting point - http://www.w3.org/WAI/
XPage Web Apps
IBM Web Accessibility Checklist
http://goo.gl/YLPqm0
XPages in the Client (XPinC) Apps
IBM Software Accessibility Checklist
http://goo.gl/xDCrQF
8. 3333
XPages Accessibility
Supported Environments
■ In v9.0.1, the accessible path supported by XPages is:
– Microsoft Windows 7
– Mozilla Firefox 25
– JAWS 14
– English was chosen test language
– Theme: “OneUI v2.1 Blue”
9. 3434
XPages Accessibility
■ WAI-ARIA standard
– Accessible Rich Internet Applications
– http://www.w3.org/WAI/intro/aria.php
■ Supplements HTML content
■ Increases accessibility of webpages
■ Some XPages controls are accessible “out-of-the-box”
■ Accessibility specific properties in IBM Domino Designer ®
– e.g. 'role', 'title', 'description' properties
– 'attrs' property for adding additional aria attributes
11. 3636
XPages Accessibility
IBM Accessibility Verification Testing (AVT)
■ AVT1 - Automated Test Tools
– Firefox plugin: Rational Policy Tester (RPT)
including Dynamic Assessment Tool
■ AVT2 - Manual Tests
– Keyboard Navigation
– Focus & Sequence
– Visual formatting
● Colour contrast
● High contrast
● Large font
– Alternative content for
audio/video
– Error handling
■ AVT3 - JAWS
– Screen Reader tool
12. 3737
XPages Accessibility
Guidelines & Best practices
■ Accessibility should begin at the 'Design' phase
– Design your apps with accessibility in mind
– Keep things simple & avoid over-complicating design
■ Use Accessible Controls where possible
– See Control Reference sections of the Help User Guide to help choose
controls
– In 9.0.1, new accessibility properties have been added to some controls
■ Error Pages
– Provide customized accessible XPage error pages
13. 3838
XPages Accessibility
Guidelines & Best practices (cont.)
Using Events in your application
– Any mouse event must have a matching keyboard event
Using Access Keys in your application
– Set accesskeys in IBM Domino Designer ®
– Make the bindings unique and intuitive
Using Partial Update
– Ensure that the updated area/control is further down the page
Login Pages
– Enable SSO on the Domino Server for accessible user
authentication