Jump to: navigation, search

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

< WTP
(Software checklist)
(Web Checklist)
 
(18 intermediate revisions by the same user not shown)
Line 43: Line 43:
 
| Yes
 
| Yes
 
| Standard SWT widgets used.  Visual indicators present.
 
| Standard SWT widgets used.  Visual indicators present.
Tested with JAWS
+
Tested with screen reader
 
|-
 
|-
 
| scope="row" | 2.2  
 
| scope="row" | 2.2  
 
| Provide semantic information about user interface objects ...
 
| Provide semantic information about user interface objects ...
 
| Yes  
 
| Yes  
| Tested with JAWS
+
| Tested with screen reader
 
|-
 
|-
 
| scope="row" | 2.3  
 
| scope="row" | 2.3  
 
| Associate labels with controls, objects, icons and images ...
 
| Associate labels with controls, objects, icons and images ...
 
| Yes  
 
| Yes  
| Tested with JAWS
+
| Tested with screen reader
 
|-
 
|-
 
| scope="row" | 2.4  
 
| scope="row" | 2.4  
Line 131: Line 131:
 
|}
 
|}
  
 +
 +
 +
== Documentation Checklist  ==
 +
 +
The full, original check list can be found at http://www-03.ibm.com/able/guidelines/documentation/accessdoc.html. Please refer to it for full text and links.
 +
 +
{| cellspacing="1" cellpadding="1" border="1" summary="Table with three columns and 4 rows. The first row contains the column headers. The first column contains the row headers."
 +
|-
 +
! scope="col" | &nbsp;
 +
! scope="col" | Checkpoint
 +
! scope="col" | Yes/No<br>
 +
Planned<br> N/A
 +
 +
! scope="col" | Comments
 +
|-
 +
! scope="row" | '''1.'''
 +
| '''Provide <span id="checkpoint1">documentation in an accessible format</span>.'''
 +
| &nbsp;
 +
| &nbsp;
 +
|-
 +
! scope="row" | &nbsp;
 +
| 1.1 Non-text Content: ...
 +
| Yes
 +
| &nbsp;
 +
|-
 +
! scope="row" | &nbsp;
 +
| 1.2 Information and relationships: ...
 +
| Yes
 +
| &nbsp;
 +
|-
 +
! scope="row" | &nbsp;
 +
| 1.3 Color and contrast: ...
 +
| Yes
 +
| &nbsp;
 +
|-
 +
! scope="row" | &nbsp;
 +
| 1.4 Meaningful sequence:...
 +
| Yes
 +
| &nbsp;
 +
|-
 +
! scope="row" | &nbsp;
 +
| 1.5 Forms:...
 +
| N/A
 +
| &nbsp;
 +
|-
 +
! scope="row" | &nbsp;
 +
| 1.6 Tables: ...
 +
| Yes
 +
| &nbsp;
 +
|-
 +
! scope="row" | &nbsp;
 +
| 1.7 Threshold violations: ...
 +
| N/A
 +
| &nbsp;
 +
|-
 +
! scope="row" | &nbsp;
 +
| 1.8 Navigation: ...
 +
| Yes
 +
| &nbsp;
 +
|-
 +
! scope="row" | &nbsp;
 +
| 1.9 Language of page: ...
 +
| Yes
 +
| &nbsp;
 +
|-
 +
! scope="row" | '''2.'''
 +
| '''<span id="checkpoint2">Document all accessibility features </span>'''
 +
| &nbsp;
 +
| &nbsp;
 +
|-
 +
! scope="row" | &nbsp;
 +
| 2.1 Provide documentation on all accessibility ...
 +
| Yes
 +
| &nbsp;
 +
|}
  
 
== Web Checklist==
 
== Web Checklist==
Line 163: Line 238:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Images have ALT text
 +
Web Service Explorer, sample JSPs, and Web Services Wizard tested
 +
</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 179: Line 256:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 194: Line 271:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>ALT text is used in image maps.
 +
Sample JSPs are programmatically determined.
 +
</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 220: Line 299:
  
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>No multimedia</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 234: Line 313:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
  
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>No Video</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 250: Line 329:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>No Live multimedia</p>
 
</td>
 
</td>
  
Line 277: Line 356:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>HTML table markup is used but we don’t show the border.  It is there for  formatting purposes</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 292: Line 371:
  
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Color is not used to distinguish things from each other</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 307: Line 386:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
  
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 322: Line 401:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>No Forms</p>
 
</td>
 
</td>
  
Line 337: Line 416:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Correct HTML Table markup is used, but we don’t show the border.  It is there for formatting purposes</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 353: Line 432:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Relevant text is still displayed properly</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 369: Line 448:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>No sensory characteristics used.</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 394: Line 473:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
  
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Color not used to convey information</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 409: Line 488:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>No audio</p>
 
</td>
 
</td>
  
Line 435: Line 514:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Controls are accessible using tab and enter key (Preferences, Web Services wizard)</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 450: Line 529:
  
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Controls are accessible using tab and enter key.</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 465: Line 544:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
  
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 507: Line 586:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 522: Line 601:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 548: Line 627:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
  
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 575: Line 654:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Similar elements are grouped together</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 590: Line 669:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 605: Line 684:
  
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 619: Line 698:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
  
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Sample JSPs have <Title></Title> tags</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 634: Line 713:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Able to navigate Sample JSPs and its frames and read results.  Tested with screen reader.</p>
 
</td>
 
</td>
  
Line 649: Line 728:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Tested with screen reader.  Links in JSPs are self explanatory, as they are the actual names of the methods.</p>
 
</td>
 
</td>
  
Line 676: Line 755:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Pass</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 701: Line 780:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
  
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Context does not change on focus, only on activation</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 716: Line 795:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
  
Line 743: Line 822:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 759: Line 838:
  
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 784: Line 863:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 800: Line 879:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 826: Line 905:
  
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 841: Line 920:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
  
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
</tr>
 
</tr>

Latest revision as of 10:41, 30 March 2010

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.

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

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 screen reader

2.2 Provide semantic information about user interface objects ... Yes Tested with screen reader
2.3 Associate labels with controls, objects, icons and images ... Yes Tested with screen reader
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


Documentation Checklist

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

  Checkpoint Yes/No

Planned
N/A

Comments
1. Provide documentation in an accessible format.    
  1.1 Non-text Content: ... Yes  
  1.2 Information and relationships: ... Yes  
  1.3 Color and contrast: ... Yes  
  1.4 Meaningful sequence:... Yes  
  1.5 Forms:... N/A  
  1.6 Tables: ... Yes  
  1.7 Threshold violations: ... N/A  
  1.8 Navigation: ... Yes  
  1.9 Language of page: ... Yes  
2. Document all accessibility features    
  2.1 Provide documentation on all accessibility ... Yes  

Web Checklist

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

# Section title Yes No

Planned

N/A
Comments

 1.1

Text alternatives: ...

1.1a

Text alternatives. ...

Yes

Images have ALT text Web Service Explorer, sample JSPs, and Web Services Wizard tested

1.1b

Non-text content. ...

N/A

N/A

1.1c

Image maps. ...

Yes

ALT text is used in image maps. Sample JSPs are programmatically determined.

 1.2

Time-based media: ...

1.2a

Captions. ...

N/A

No multimedia

1.2b

Audio and video (prerecorded). ...

N/A

No Video

1.2c

Live multimedia. ...

N/A

No Live multimedia

 1.3

Adaptable: ...

1.3a

Information and relationships. ...

Yes

HTML table markup is used but we don’t show the border. It is there for formatting purposes

1.3b

Removed: ...

N/A

Color is not used to distinguish things from each other

1.3c

Meaningful sequence. ...

N/A

N/A

1.3d

Forms. ...

N/A

No Forms

1.3e

Tables....

Yes

Correct HTML Table markup is used, but we don’t show the border. It is there for formatting purposes

1.3f

Cascading style sheets. ...

Yes

Relevant text is still displayed properly

1.3g

Sensory characteristics. ...

N/A

No sensory characteristics used.

 1.4

Distinguishable: ...

1.4a

Use of color....

Yes

Color not used to convey information

1.4b

Audio control. ...

N/A

No audio

 2.1

Keyboard Accessible: ...

2.1a

Keyboard. ...

Yes

Controls are accessible using tab and enter key (Preferences, Web Services wizard)

2.1b

Scripts. ...

Yes

Controls are accessible using tab and enter key.

2.1c

Applets, plug-ins, and non-HTML content. ...

N/A

N/A

2.1d

No keyboard trap....

 

 

 2.2

Enough Time. ...

2.2a

Adjust time response. ...

N/A

N/A

2.2b

Pause, stop, hide....

N/A

N/A

 2.3

Seizures: ...

2.3a

Flashing Content or below threshold. ...

N/A

N/A

 2.4

Navigable: ...

2.4a

Navigational features. ...

Yes

Similar elements are grouped together

2.4b

Removed: ...

N/A

N/A

2.4c

Frames. ...

Yes

Yes

2.4d

Page titles....

Yes

Sample JSPs have <Title></Title> tags

2.4e

Focus order....

Yes

Able to navigate Sample JSPs and its frames and read results. Tested with screen reader.

2.4f

Link purpose....

Yes

Tested with screen reader. Links in JSPs are self explanatory, as they are the actual names of the methods.

 3.1

Readable: ...

3.1a

Language of page. ...

Yes

Pass

 3.2

Predictable. ...

3.2a

On focus. ...

Yes

Context does not change on focus, only on activation

3.2b

On input....

N/A

N/A

 3.3

Input Assistance: ...

3.3a

Error identification. ...

N/A

N/A

3.3b

Labels or instructions. ...

N/A

N/A

 4.1

Compatible: ...

4.1a

Parsing. ...

N/A

N/A

4.1b

Name, role, value. ...

N/A

N/A

 4.2

Ensure that content is accessible ...

4.2a

Text-only page. ...

N/A

N/A

4.2b

Accessibility-supported technologies only. ...

N/A

N/A