Jump to: navigation, search

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

< WTP
(Web Checklist)
(Web Checklist)
Line 421: Line 421:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
  
Line 436: Line 436:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
Line 451: Line 451:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>No</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=306111 Bug 306111] - [acc] [doc] Use correct table headers in documentation tables</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 467: Line 467:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Used "Disable CSS" bookmarklet to verify this. [http://dorward.me.uk/software/disablecss/]</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 483: Line 483:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 508: Line 508:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
  
Line 523: Line 523:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
Line 549: Line 549:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
 
<td>
 
<td>
Line 564: Line 564:
  
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>No scripts have been used for any user functionality</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 579: Line 579:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
  
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>No such content</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 594: Line 594:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>Yes</p>
 
</td>
 
</td>
 
<td>
 
<td>
Line 621: Line 621:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
Line 636: Line 636:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
 
<td>
 
<td>
Line 662: Line 662:
 
</td>
 
</td>
 
<td>
 
<td>
<p>&nbsp;</p>
+
<p>N/A</p>
 
</td>
 
</td>
  

Revision as of 21:40, 17 March 2010

JavaServer Faces

[Instructions: WTP subprojects should copy this template to a wiki page, named similar to WTP/Accessibility/Helios/<subproject name>/, fill in their project name, remove these instructions in brackets, then fill in the checklist data.]

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 ... No Some support is provided (Keyboard shortcuts to change WPE layouts etc). Additional support is planned.
  • Bug 306104 - [acc] Web Page Editor preference page does not use any mnemonics
  • Bug 306103 - [acc] Faces Config Editor preference page does not use any mnemonics
1.2 Do not interfere with keyboard accessibility features ... No
  • Bug 305928 - [acc] [wpe] PageUp and PageDown do not work in WPE design pane
  • Bug 191544 - [WPE] Home and End keys do not work in Web Page Editor
2

Object information

Yes No
Planned
N/A
Comments
2.1 Provide a visual focus indicator ... Yes  
2.2 Provide semantic information about user interface objects ... Yes  
2.3 Associate labels with controls, objects, icons and images ... Yes  
2.4 When electronic forms are used, the form shall allow people using assistive technology to access the information ... Planned  
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  
3.2 Provide accessible alternatives to significant audio and video. N/A  
3.3 Provide an option to adjust the volume. N/A  
4 Display Yes No
Planned
N/A
Comments
4.1 Provide text through standard system function calls ... No  
4.2 Use color as an enhancement ... Yes  
4.3 Support system settings for high contrast ... No Bug 305924 - [acc] [wpe] WPE design pane widgets do not respect OS high-contrast color scheme
4.4 When color customization is supported, provide a variety of color selections ... N/A  
4.5 Inherit system settings for font, size, and color ... Yes  
4.6 Provide an option to display animation in a non-animated presentation mode. N/A  
5 Timing Yes No
Planned
N/A
Comments
5.1 Provide an option to adjust the response times on timed instructions ... N/A  
5.2 Do not use flashing or blinking text, ... Yes The <blink> tag when used in the WPE, does not blink in the design pane or the preview pane. This conforms to this accessibility guideline, and well as those of W3C's Web Content Accessibility guidelines http://www.w3.org/TR/WAI-WEBCONTENT/

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: ... No Bug 305964 - [acc] Images used for code listings in JSF tutorial
  1.2 Information and relationships: ... Yes Bug 306092 - [doc] [tutorial] Miscellaneous Corrections in JSF Tutorial
  1.3 Color and contrast: ... Yes  
  1.4 Meaningful sequence:... Yes  
  1.5 Forms:... Yes  
  1.6 Tables: ... No Bug 306111 - [acc] [doc] Use correct table headers in documentation tables
  1.7 Threshold violations: ... N/A  
  1.8 Navigation: ... Yes The few long documents that exist use headers of appropriate weights (h1, h2 etc.) etc.
  1.9 Language of page: ... Planned Bug 306109 - [acc] [doc] Define language for documentation pages
2. Document all accessibility features    
  2.1 Provide documentation on all accessibility ... N/A No custom keyboard shortcuts. Toolbar icons that have key shortcuts are documented in the toolbar item itself.

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. ...

No

Bug 306116 - [acc] [web] Alt text missing on many images in JSF tools website

1.1b

Non-text content. ...

No

Bug 305964 - [acc] Images used for code listings in JSF tutorial

1.1c

Image maps. ...

N/A

No image maps were found to be used.

 1.2

Time-based media: ...

1.2a

Captions. ...

Yes

 

1.2b

Audio and video (prerecorded). ...

N/A

 

1.2c

Live multimedia. ...

N/A

 

 1.3

Adaptable: ...

1.3a

Information and relationships. ...

No

  • Bug 306139 - [acc] Use <strong> instead of <b> in emphasised text in JSF Tools website and documentation for better semantics (for assistive technology)
  • Bug 306146 - [acc] Use captions for tables in JSF documentation and website
  • Bug 306246 - [acc] Use semantic markup for paragraphs, lists and headings in documentation and website

1.3b

Removed: ...

 

 

1.3c

Meaningful sequence. ...

Yes

 

1.3d

Forms. ...

N/A

 

1.3e

Tables....

No

Bug 306111 - [acc] [doc] Use correct table headers in documentation tables

1.3f

Cascading style sheets. ...

Yes

Used "Disable CSS" bookmarklet to verify this. [1]

1.3g

Sensory characteristics. ...

Yes

N/A

 1.4

Distinguishable: ...

1.4a

Use of color....

Yes

 

1.4b

Audio control. ...

N/A

 

 2.1

Keyboard Accessible: ...

2.1a

Keyboard. ...

Yes

 

2.1b

Scripts. ...

N/A

No scripts have been used for any user functionality

2.1c

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

N/A

No such content

2.1d

No keyboard trap....

Yes

 

 2.2

Enough Time. ...

2.2a

Adjust time response. ...

N/A

 

2.2b

Pause, stop, hide....

N/A

 

 2.3

Seizures: ...

2.3a

Flashing Content or below threshold. ...

N/A

 

 2.4

Navigable: ...

2.4a

Navigational features. ...

 

 

2.4b

Removed: ...

 

 

2.4c

Frames. ...

 

 

2.4d

Page titles....

 

 

2.4e

Focus order....

 

 

2.4f

Link purpose....

 

 

 3.1

Readable: ...

3.1a

Language of page. ...

 

 

 3.2

Predictable. ...

3.2a

On focus. ...

 

 

3.2b

On input....

 

 

 3.3

Input Assistance: ...

3.3a

Error identification. ...

 

 

3.3b

Labels or instructions. ...

 

 

 4.1

Compatible: ...

4.1a

Parsing. ...

 

 

4.1b

Name, role, value. ...

 

 

 4.2

Ensure that content is accessible ...

4.2a

Text-only page. ...

 

 

4.2b

Accessibility-supported technologies only. ...