Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "WTP/Accessibility/Helios/webservices"

< WTP
(Software checklist)
(Software checklist)
Line 2: Line 2:
  
 
For JAX-WS Web Services Accessibility Checklists, see http://wiki.eclipse.org/WTP/Accessibility/Helios/webservices/jaxws
 
For JAX-WS Web Services Accessibility Checklists, see http://wiki.eclipse.org/WTP/Accessibility/Helios/webservices/jaxws
 +
 +
=Web Services=
 +
 +
This data is an unofficial, working copy for a sub-project. The rolled up version for Helios requirements will be a consolidated summary of the individual ones.
  
 
==Software checklist==  
 
==Software checklist==  

Revision as of 20:57, 16 March 2010

The following are the accessibility checklists for the WTP Web Services sub-project.

For JAX-WS Web Services Accessibility Checklists, see http://wiki.eclipse.org/WTP/Accessibility/Helios/webservices/jaxws

Web Services

This data is an unofficial, working copy for a sub-project. The rolled up version for Helios requirements will be a consolidated summary of the individual ones.

Software checklist

The full, original check list can be found at http://www-03.ibm.com/able/guidelines/software/accesssoftware.html. Please refer to it for full text and links.


1

Keyboard access

Yes No
Planned
N/A
Comments
1.1 Provide keyboard equivalents ... Yes Tested with keyboard. Bugs found:

Bug 306098

1.2 Do not interfere with keyboard accessibility features ... Yes No interference
2

Object information

Yes No
Planned
N/A
Comments
2.1 Provide a visual focus indicator ... Yes Standard SWT widgets used. Visual indicators present.

Tested with JAWS

2.2 Provide semantic information about user interface objects ... Yes Tested with JAWS
2.3 Associate labels with controls, objects, icons and images ... Yes Tested with JAWS
2.4 When electronic forms are used, the form shall allow people using assistive technology to access the information ... N/A Forms not used
3 Sounds and multimedia Yes No
Planned
N/A
Comments
3.1 Provide an option to display a visual cue for all audio alerts. N/A No audio alerts
3.2 Provide accessible alternatives to significant audio and video. N/A No audio or video
3.3 Provide an option to adjust the volume. N/A No audio
4 Display Yes No
Planned
N/A
Comments
4.1 Provide text through standard system function calls ... Yes WSDL - Images have hover over help
4.2 Use color as an enhancement ... Yes Color is used as an enhancement, not to identify information
4.3 Support system settings for high contrast ... Yes Can use high contrast for user control and content
4.4 When color customization is supported, provide a variety of color selections ... N/A No support for customized color
4.5 Inherit system settings for font, size, and color ... Yes SWT inherit color and fonts
4.6 Provide an option to display animation in a non-animated presentation mode. N/A No animation
5 Timing Yes No
Planned
N/A
Comments
5.1 Provide an option to adjust the response times on timed instructions ... N/A No timed instructions
5.2 Do not use flashing or blinking text, ... N/A No flashing or blinking items

Back to the top