Jump to: navigation, search

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

< WTP
(Web Checklist)
(Software checklist)
 
(16 intermediate revisions by 2 users not shown)
Line 27: Line 27:
 
*[https://bugs.eclipse.org/bugs/show_bug.cgi?id=306104 Bug 306104] - [acc] Web Page Editor preference page does not use any mnemonics
 
*[https://bugs.eclipse.org/bugs/show_bug.cgi?id=306104 Bug 306104] - [acc] Web Page Editor preference page does not use any mnemonics
 
*[https://bugs.eclipse.org/bugs/show_bug.cgi?id=306103 Bug 306103] - [acc] Faces Config Editor preference page does not use any mnemonics
 
*[https://bugs.eclipse.org/bugs/show_bug.cgi?id=306103 Bug 306103] - [acc] Faces Config Editor preference page does not use any mnemonics
 +
* <span style="color:#f00"><b>P2</b> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=191496 Bug 191496] - [hotbug_request] Unable to use palette on nav rule faces config editor without mouse (Notes: One can however edit the faces-config.xml file entirely using the keyboard to create a navigation rule)</span>
 +
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=191495 Bug 191495] -  Unable to tab to palettte on nav rule page of config editor
 +
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=268871 Bug 268871] - Improvements to tab order in faces-config editor
 +
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=191494 Bug 191494] - Unable to switch pages in faces config editor without mouse
 +
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=268435 Bug 268435] - Tab names on faces-config editor aren't read by screen reader
 
|-
 
|-
 
| scope="row" | 1.2  
 
| scope="row" | 1.2  
Line 44: Line 49:
 
| scope="row" | 2.1  
 
| scope="row" | 2.1  
 
| Provide a visual focus indicator ...
 
| Provide a visual focus indicator ...
| Yes
+
| No
| &nbsp;
+
|  
 +
* <span style="color:red"><b>P2</b> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=268407 Bug 268407] - [hotbug_request] Focus not set properly after activating faces-config editor with the keyboard</span>
 +
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=268874 Bug 268874] - Focus improvements to ManagedBean tab of faces-config editor 
 
|-
 
|-
 
| scope="row" | 2.2  
 
| scope="row" | 2.2  
 
| Provide semantic information about user interface objects ...
 
| Provide semantic information about user interface objects ...
| Yes
+
| No
| &nbsp;
+
|
 +
* <span style="color:red"><b>P2</b> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=268426 Bug 268426] - [hotbug_request] Objects on Navigation Rule tab of faces-config editor aren't accessible</span>
 
|-
 
|-
 
| 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
+
| No
| &nbsp;
+
|  
 +
* <span style="color:red"><b>P2</b> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=268443 Bug 268443] -  [hotbug_request] FacesConfig Editor preferences page needs more info for screen readers</span>
 +
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=268435 Bug 268435] - Tab names on faces-config editor aren't read by screen reader
 
|-
 
|-
 
| scope="row" | 2.4  
 
| scope="row" | 2.4  
Line 245: Line 255:
 
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.
 
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.
  
 +
'''Note for readers and future efforts: the evaluation done here is oriented towards the Eclipse website, which is not the purpose of this form. This is good information (and should be accessible) but here we are documenting compliance to deliverables that adopters might re-use).'''
  
 
<table border="1" cellpadding="1" cellspacing="1">
 
<table border="1" cellpadding="1" cellspacing="1">
Line 900: Line 911:
 
<p>No</p>
 
<p>No</p>
 
</td>
 
</td>
<td>
+
<td><p>
 
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=306260 Bug 306260] -  [acc] [web] JSF tutorial contains invalid HTML (which may lead to accessibility problems)  
 
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=306260 Bug 306260] -  [acc] [web] JSF tutorial contains invalid HTML (which may lead to accessibility problems)  
 
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=306262 Bug 306262] -  [acc] [web] JSF Tools home page does not validate against HTML standards for valid markup
 
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=306262 Bug 306262] -  [acc] [web] JSF Tools home page does not validate against HTML standards for valid markup

Latest revision as of 09:32, 8 April 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
  • P2 Bug 191496 - [hotbug_request] Unable to use palette on nav rule faces config editor without mouse (Notes: One can however edit the faces-config.xml file entirely using the keyboard to create a navigation rule)
  • Bug 191495 - Unable to tab to palettte on nav rule page of config editor
  • Bug 268871 - Improvements to tab order in faces-config editor
  • Bug 191494 - Unable to switch pages in faces config editor without mouse
  • Bug 268435 - Tab names on faces-config editor aren't read by screen reader
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 ... No
  • P2 Bug 268407 - [hotbug_request] Focus not set properly after activating faces-config editor with the keyboard
  • Bug 268874 - Focus improvements to ManagedBean tab of faces-config editor
2.2 Provide semantic information about user interface objects ... No
  • P2 Bug 268426 - [hotbug_request] Objects on Navigation Rule tab of faces-config editor aren't accessible
2.3 Associate labels with controls, objects, icons and images ... No
  • P2 Bug 268443 - [hotbug_request] FacesConfig Editor preferences page needs more info for screen readers
  • Bug 268435 - Tab names on faces-config editor aren't read by screen reader
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.

Note for readers and future efforts: the evaluation done here is oriented towards the Eclipse website, which is not the purpose of this form. This is good information (and should be accessible) but here we are documenting compliance to deliverables that adopters might re-use).

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

Yes

Bug 306294 - [acc] No table of contents or equivalent in JSF tutorial and other documentation page. This does not seem to apply directly to the website per se

2.4b

Removed: ...

 

 

2.4c

Frames. ...

N/A

No frames are used

2.4d

Page titles....

Yes

 

2.4e

Focus order....

Yes

 

2.4f

Link purpose....

No

Bug 306299 - [web] In JSF Tools home page, "Project Wiki" and "Project Plan" point to the same page

 3.1

Readable: ...

3.1a

Language of page. ...

No

Bug 306109 - [acc] [doc] Define language for HTML pages in website and documentation

 3.2

Predictable. ...

3.2a

On focus. ...

Yes

 

3.2b

On input....

N/A

 

 3.3

Input Assistance: ...

3.3a

Error identification. ...

N/A

 

3.3b

Labels or instructions. ...

N/A

 

 4.1

Compatible: ...

4.1a

Parsing. ...

No

  • Bug 306260 - [acc] [web] JSF tutorial contains invalid HTML (which may lead to accessibility problems)
  • Bug 306262 - [acc] [web] JSF Tools home page does not validate against HTML standards for valid markup

4.1b

Name, role, value. ...

N/A

 

 4.2

Ensure that content is accessible ...

4.2a

Text-only page. ...

N/A

 

4.2b

Accessibility-supported technologies only. ...

Yes