BIRT/FAQ/AccessibilityBIRT4.2.1

From Eclipsepedia

< BIRT‎ | FAQ
Revision as of 22:19, 27 September 2012 by Lchen.actuate.com (Talk | contribs)

Jump to: navigation, search

Contents

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
Bugs Comments
1.1 Provide keyboard equivalents ... Yes    
1.2 Do not interfere with keyboard accessibility features ... Yes    
2

Object information

Yes No
Planned
N/A
Bugs 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 ... Yes    
3 Sounds and multimedia Yes No
Planned
N/A
Bugs 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
Bugs Comments
4.1 Provide text through standard system function calls ... Yes    
4.2 Use color as an enhancement ... Yes    
4.3 Support system settings for high contrast ... Yes    
4.4 When color customization is supported, provide a variety of color selections ... Yes    
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. Yes    
5 Timing Yes No
Planned
N/A
Bugs 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, ... N/A    

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
Bugs 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:... Yes    
  1.6 Tables: ... Yes    
  1.7 Threshold violations: ... Yes    
  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-User Interface

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
Bugs Comments

 1.1

Text alternatives: ...

1.1a

Text alternatives. ...

yes

 

 

1.1b

Non-text content. ...

n/a

 

 

1.1c

Image maps. ...

yes

 

 

 1.2

Time-based media: ...

1.2a

Captions. ...

n/a

 

 

1.2b

Audio and video (prerecorded). ...

n/a

 

 

1.2c

Live multimedia. ...

n/a

 

 

 1.3

Adaptable: ...

1.3a

Information and relationships. ...

n/a

 

 

1.3b

Removed: ...

 

 

 

1.3c

Meaningful sequence. ...

n/a

 

 

1.3d

Forms. ...

yes

304325

 

1.3e

Tables....

n/a

 

 

1.3f

Cascading style sheets. ...

yes

 

 

1.3g

Sensory characteristics. ...

n/a

 

 

 1.4

Distinguishable: ...

1.4a

Use of color....

n/a

 

 

1.4b

Audio control. ...

n/a

 

 

 2.1

Keyboard Accessible: ...

2.1a

Keyboard. ...

yes

304453

 

2.1b

Scripts. ...

yes

 

 

2.1c

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

n/a

 

 

2.1d

No keyboard trap....

n/a

 

 

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

n/a

 

 

2.4b

Removed: ...

 

 

 

2.4c

Frames. ...

yes

 

 

2.4d

Page titles....

yes

 

 

2.4e

Focus order....

yes

304457

 

2.4f

Link purpose....

yes

 

 

 3.1

Readable: ...

3.1a

Language of page. ...

yes

 

 

 3.2

Predictable. ...

3.2a

On focus. ...

yes

 

 

3.2b

On input....

yes

 

 

 3.3

Input Assistance: ...

3.3a

Error identification. ...

n/a

 

 

3.3b

Labels or instructions. ...

yes

 

 

 4.1

Compatible: ...

4.1a

Parsing. ...

yes

 

 

4.1b

Name, role, value. ...

yes

 

 

 4.2

Ensure that content is accessible ...

4.2a

Text-only page. ...

yes

 

 

4.2b

Accessibility-supported technologies only. ...

n/a

 

 


Web Checklist-output

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
Bugs Comments

 1.1

Text alternatives: ...

1.1a

Text alternatives. ...

yes

 

 

1.1b

Non-text content. ...

n/a

 

 

1.1c

Image maps. ...

yes

 

 

 1.2

Time-based media: ...

1.2a

Captions. ...

n/a

 

 

1.2b

Audio and video (prerecorded). ...

n/a

 

 

1.2c

Live multimedia. ...

n/a

 

 

 1.3

Adaptable: ...

1.3a

Information and relationships. ...

yes

 

 

1.3b

Removed: ...

 

 

 

1.3c

Meaningful sequence. ...

n/a

 

 

1.3d

Forms. ...

n/a

 

 

1.3e

Tables....

yes

304320

 

1.3f

Cascading style sheets. ...

yes

 

 

1.3g

Sensory characteristics. ...

n/a

 

 

 1.4

Distinguishable: ...

1.4a

Use of color....

n/a

 

 

1.4b

Audio control. ...

n/a

 

 

 2.1

Keyboard Accessible: ...

2.1a

Keyboard. ...

n/a

 

 

2.1b

Scripts. ...

n/a

 

 

2.1c

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

n/a

 

 

2.1d

No keyboard trap....

n/a

 

 

 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

 

 

2.4b

Removed: ...

 

 

 

2.4c

Frames. ...

yes

 

 

2.4d

Page titles....

yes

 

 

2.4e

Focus order....

yes

 

 

2.4f

Link purpose....

yes

305450

 

 3.1

Readable: ...

3.1a

Language of page. ...

yes

 

 

 3.2

Predictable. ...

3.2a

On focus. ...

yes

 

 

3.2b

On input....

yes

 

 

 3.3

Input Assistance: ...

3.3a

Error identification. ...

yes

304463

 

3.3b

Labels or instructions. ...

yes

 

 

 4.1

Compatible: ...

4.1a

Parsing. ...

yes

 

 

4.1b

Name, role, value. ...

yes

 

 

 4.2

Ensure that content is accessible ...

4.2a

Text-only page. ...

yes

 

 

4.2b

Accessibility-supported technologies only. ...

n/a

 

 



Documentation for Web 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
Bugs Comments
1.1.1 Text Alternatives: Provide text alternatives for all non-text content so that it can be changed into other forms people need, such as large print, Braille, speech, symbols or simpler language.
  1.1.1a Text alternatives. All non-text content that is presented to the user has a text alternative Yes    
  1.1.1b Non-text content. A descriptive label is provided for time-based media, including live audio-only and live video-only content Yes    
  1.1.1c Image maps. N/A    
1.1.2 Time-based Media: Provide alternatives for time-based media.
  ... N/A    
1.1.3 Adaptable: Create content that can be presented in different ways without losing information or structure.
  1.1.3a Information and Relationships. Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. Yes    
  1.1.3a Information and Relationships. Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. Yes    
  1.1.3c Meaningful Sequence. Yes    
  1.1.3d Forms. Yes    
  1.1.3e Tables. Yes    
  1.1.3f Cascading style sheets. Yes    
  1.1.3g Sensory Characteristics. Yes    
1.1.4 Distinguishable: Make it easier for users to see and hear content including separating foreground from background .
  1.1.4a Use of Color. Color is not used as the only visual means. Yes    
  1.1.4b Audio Control. N/A    
1.2.1 Distinguishable: Make it easier for users to see and hear content including separating foreground from background .
  1.2.1a Keyboard. All functionality of the content is operable through a keyboard interface . Yes    
  1.2.1b Scripts. Scripts are keyboard accessible. N/A    
  1.2.1c Applets, plug-ins, and non-HTML content. N/A    
  1.2.1d No Keyboard Trap. Yes    
1.2.2 Enough Time. Provide users enough time to read and use content..
  ... N/A    
1.2.3 Seizures: Do not design content in a way that is known to cause seizures..
  ... N/A    
1.2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are..
  1.2.4a Navigational features. Yes    
  1.2.4b Skip to main content. Yes    
  1.2.4c Frames. Yes    
  1.2.4d Page Titles. Yes    
  1.2.4e Focus Order. Yes    
  1.2.4f Link Purpose. Yes    
1.3.1 Readable: Make text content readable and understandable..
  1.3.1a Language of Page. Yes    
1.3.2 Predictable. Make Web pages appear and operate in predictable ways..
  1.3.2a On Focus. When any component receives focus, it does not initiate a change of context. Yes    
  1.3.2b On Input. Changing the setting of any user interface component does not automatically cause a change of context. Yes    
1.3.3 Input Assistance: Help users avoid and correct mistakes..
  ... N/A    
1.4.1 Compatible: Maximize compatibility with current and future user agents..
  1.4.1a Parsing. Yes    
  1.4.1b Name, Role, Value. Yes    
1.4.2 Ensure that content is accessible or provide an accessible alternative..
  1.4.2a Text-only page. Yes    
  1.4.2b Accessibility-Supported Technologies Only. ????