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 "BIRT/FAQ/AccessibilityBIRT4.2.1"

< BIRT‎ | FAQ
(→‎Documentation for Web Checklist)
(→‎Documentation for Web Checklist)
Line 372: Line 372:
 
<td>1.3.1a Language of Page. </td>
 
<td>1.3.1a Language of Page. </td>
 
<td>Yes</td>
 
<td>Yes</td>
 +
<td>&nbsp;</td>
 +
<td>&nbsp;</td>
 +
</tr>
 +
 +
<tr>
 +
<th scope="row"><strong>1.3.2</strong></th>
 +
<td colspan="4"><strong><span id="checkpoint1">Predictable. Make Web pages appear and operate in predictable ways.</span>.</strong></td>
 +
</tr>
 +
<tr>
 +
<th scope="row">&nbsp;</th>
 +
<td>1.3.2a On Focus. When any component receives focus, it does not initiate a change of context.</td>
 +
<td>Yes</td>
 +
<td>&nbsp;</td>
 +
<td>&nbsp;</td>
 +
</tr>
 +
<tr>
 +
<th scope="row">&nbsp;</th>
 +
<td>1.3.2b On Input. Changing the setting of any user interface component does not automatically cause a change of context.</td>
 +
<td>Yes</td>
 +
<td>&nbsp;</td>
 +
<td>&nbsp;</td>
 +
</tr>
 +
 +
 +
<tr>
 +
<th scope="row"><strong>1.3.3</strong></th>
 +
<td colspan="4"><strong><span id="checkpoint1">Input Assistance: Help users avoid and correct mistakes.</strong></td>
 +
</tr>
 +
<tr>
 +
<th scope="row">&nbsp;</th>
 +
<td>...</td>
 +
<td>N/A</td>
 +
<td>&nbsp;</td>
 +
<td>&nbsp;</td>
 +
</tr>
 +
 +
 +
<tr>
 +
<th scope="row"><strong>1.4.1</strong></th>
 +
<td colspan="4"><strong><span id="checkpoint1">Compatible: Maximize compatibility with current and future user agents.</strong></td>
 +
</tr>
 +
<tr>
 +
<th scope="row">&nbsp;</th>
 +
<td>1.4.1a Parsing. </td>
 +
<td>Yes</td>
 +
<td>&nbsp;</td>
 +
<td>&nbsp;</td>
 +
</tr>
 +
<tr>
 +
<th scope="row">&nbsp;</th>
 +
<td>1.4.1b Name, Role, Value. </td>
 +
<td>Yes</td>
 +
<td>&nbsp;</td>
 +
<td>&nbsp;</td>
 +
</tr>
 +
 +
 +
<tr>
 +
<th scope="row"><strong>1.4.2</strong></th>
 +
<td colspan="4"><strong><span id="checkpoint1">Ensure that content is accessible or provide an accessible alternative..</strong></td>
 +
</tr>
 +
<tr>
 +
<th scope="row">&nbsp;</th>
 +
<td>1.4.2a Text-only page. </td>
 +
<td>Yes</td>
 +
<td>&nbsp;</td>
 +
<td>&nbsp;</td>
 +
</tr>
 +
<tr>
 +
<th scope="row">&nbsp;</th>
 +
<td>1.4.2b Accessibility-Supported Technologies Only. </td>
 +
<td>????</td>
 
<td>&nbsp;</td>
 
<td>&nbsp;</td>
 
<td>&nbsp;</td>
 
<td>&nbsp;</td>

Revision as of 02:57, 27 September 2012

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  


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.</strong></td>

</tr>

  ...</td> N/A</td>  </td>  </td>

</tr>


1.4.1 Compatible: Maximize compatibility with current and future user agents.</strong></td>

</tr>

  1.4.1a Parsing. </td> Yes</td>  </td>  </td>

</tr>

  1.4.1b Name, Role, Value. </td> Yes</td>  </td>  </td>

</tr>


1.4.2 Ensure that content is accessible or provide an accessible alternative..</strong></td>

</tr>

  1.4.2a Text-only page. </td> Yes</td>  </td>  </td>

</tr>

  1.4.2b Accessibility-Supported Technologies Only. </td> ????</td>  </td>  </td>

</tr>

</table>

Retrieved from "https://wiki.eclipse.org/index.php?title=BIRT/FAQ/AccessibilityBIRT4.2.1&oldid=316494"

Back to the top