Jump to: navigation, search

Platform Accessibility Status

Revision as of 13:37, 9 May 2007 by Tod creasey.ca.ibm.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

<html>

<head>

<title>Eclipse 3.3 Accessibility Status</title></head>

<body>

Accessibility Status for Eclipse SDK 3.3

Last update: May 9, 2006

  • <a href="#software">Software</a>
  • <a href="#doc">Documentation</a>
  • The numbers in the Failures column indicate problem reports in the Eclipse Bugzilla database (<a href="http://bugs.eclipse.org/bugs/">http://bugs.eclipse.org/bugs</a>).
    The bug database has other PRs marked with the keyword "accessibility", however these are minor and are not an issue in meeting the checklist requirements.

    <a name="software"></a>

     

    IBM Software Accessibility Checklist - Version 3.5.1
    (from <a href="http://www-306.ibm.com/able/guidelines/software/accesssoftware.html">http://www-306.ibm.com/able/guidelines/software/accesssoftware.html</a>)

       </td>
     </tr>
    
    <b>

    1</font></b></td>

    <b>
         <p>Keyboard access</b></td>
    
    <b>
         <p ALIGN="CENTER">Yes
    No
    Planned
    N/A</p>
    </b> </td>
         <p ALIGN="left"><b>Comments </b></td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">1.1</b></td>
    
         <p>Provide keyboard
         equivalents for
         all actions.</td>
    
         <p align="center">Yes</td>
    
    <p><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=56338">56338</a>,
           <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=66297">66297</a>, 
           <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=87015">87015</a>, 
           <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110216">110216</a>, 
           <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=136698">136698</a>,(UI) 
       </td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">1.2</b></td>
    
    <p>
         Do not interfere with keyboard
         accessibility features
         built into the operating system.</td>
    
         <p>Yes </td>
    
    </td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">2</b></td>
    
    <b>
         <p>Object Information</b></td>
    
         <p ALIGN="CENTER"><b>
         Yes
    No
    Planned
    N/A
    </b></td>
    <b>Comments</b></td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">2.1</b></td>
    
    <p>
         Provide a visual
         focus indicator
         that moves among interactive objects as the input focus changes. This
         focus indicator must be programmatically exposed to assistive technology.</td>
    
         <p>Yes </td>
    
    <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89820">89820</a>,

    <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=159201">159201</a> (SWT)</td>

     </tr>
    
    <b>
         <p ALIGN="CENTER">2.2</b></td>
    
    <p>
         Provide semantic information
         about user interface objects.
         When an image represents a program element, the information conveyed by
         the image must also be available in text.</td>
    
         <p>Yes</td>
    
    <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=128436">128436</a>
         (SWT)</td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">2.3</b></td>
    
    <p>
         Associate labels
         with controls, objects, icons and images. If an image is used to identify
         programmatic elements, the meaning of the image must be consistent
         throughout the application.</td>
    
         <p> Yes</td>
    
     </td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">2.4</b></td>
    
    <p>
        When electronic forms
         are used, the form shall allow people using assistive technology to access
         the information, field elements and functionality required for completion
         and submission of the form, including all directions and cues.</td>
    
         <p> Yes</td>
    
    </td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">3</b></td>
    
    <b>
         <p>Sounds and Multimedia</b></td>
    
         <p ALIGN="CENTER"><b>
         Yes
    No
    Planned
    N/A
    </b></td>
    <b>Comments </b></td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">3.1</b></td>
    
    <p>
         Provide an option to display a visual
         cue for all audio alerts.</td>
    
         <p>N/A </td>
    
    Occasional use of system beep, which is handled by OS.</td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">3.2</b></td>
    
    <p>
         Provide accessible alternatives to significant audio
         and video.</td>
    
         <p>N/A </td>
    
    </td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">3.3</b></td>
    
    <p>
         Provide an option to <u>adjust
         the volume</u>.</td>
    
         <p>N/A </td>
    
    </td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">4</b></td>
    
    <b>
         <p>Display</b></td>
    
         <p ALIGN="CENTER"><b>
         Yes
    No
    Planned
    N/A
    </b></td>
    <b>Comments </b></td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">4.1</b></td>
    
    <p>
         Provide <u>text</u>
         through standard system function calls or through an API (application
         programming interface) which supports interaction with assistive
         technology.</td>
    
         <p align="center"> Yes</td>
    
    <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=100034">100034</a>
         (UI)</td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">4.2</b></td>
    
    <p>
         Use <u>color</u>
         as an enhancement, not as the only way to convey information or indicate
         an action.</td>
    
         <p> Yes</td>
    
    Breakpoints use color to show their state: blue for enabled,
         clear for disabled.  But this state is accessible via the breakpoint
         properties dialog.</td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">4.3</b></td>
    
    <p>
        Support system settings for <u>high
         contrast</u> for all
         user interface controls and client area content.</td>
    
         <p> Yes</td>
    
    <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=144530">144530</a>
         (UA)</td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">4.4</b></td>
    
    <p>
         When color customization is supported, provide a <u>variety</u>
         of color selections capable of producing a range of contrast levels.</td>
    
         <p> Yes</td>
    
    <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=181592">181592</a>
         (SWT)</td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">4.5</b></td>
    
    <p>
         Inherit <u>system
         settings for font, size, and color</u>
         for all user interface controls.</td>
    
         <p>Yes </td>
    
    <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=145565">145565</a>
         (Update)</td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">4.6</b></td>
    
    <p>
         Provide an option to display <u>animation</u>
         in a non-animated presentation mode.</td>
    
         <p>N/A </td>
    
    </td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">5</b></td>
    
    <b>
         <p>Timing</b></td>
    
         <p ALIGN="CENTER"><b>
         Yes
    No
    Planned
    N/A
    </b></td>
    <b>Comments </b></td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">5.1</b></td>
    
    <p>
         Provide an option to adjust the <u>response
         times</u> on timed
         instructions or allow the instructions to persist.</td>
    
         <p>Yes </td>
    
    Cell editors in the Tasks view have timed interaction, but
         the Task Properties dialog is an accessible alternative.</td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">5.2</b></td>
    
    <p>
         Avoid the use of <u>blinking
         text, objects or other elements.</u></td>
    
         <p> Yes</td>
    
    </td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">6</b></td>
    
    <b>
         <p>Verify Accessibility</b></td>
    
         <p ALIGN="CENTER"><b>
         Yes
    No
    Planned
    N/A
    </b></td>
    <b>Comments </b></td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">6.1</b></td>
    
    <p><u>
         Test</u> for
         accessibility using available tools.</td>
    
         <p> Yes</td>
    
    <p>Tested with MSAA tools and JAWS on Windows.
       </td>
     </tr>
    

    </table>

    <a name="doc"></a>

        IBM Documentation Accessibility Checklist - Version 1.5 
    (from <a href="http://www-306.ibm.com/able/guidelines/documentation/accessdoc.html">http://www-306.ibm.com/able/guidelines/documentation/accessdoc.html</a>)

    1</font></b></td>

    <b>
         Documentation
         <p></b></td>
    
    <b>
         <p ALIGN="CENTER">Yes
    No
    Planned
    N/A</p>
    </b> </td>
         <p ALIGN="left"><b>Comments </b></td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">1.1</b></td>
    
    <p>
        Provide documentation
         in an accessible format.
         Check using accessibility compliance tools.</td>
    
    <p align="center">
         Yes </td>
    
    <p><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=76381">76381</a> (SWT),
           <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=93206">93206</a> 
    
    (UA)

       </td>
     </tr>
    
    <b>

    1.2</font></b></td>

    <p>
         Provide documentation
         on all accessibility features
         including keyboard access.</td>
    
         <p>Yes </td>
    
    </td>
     </tr>
    
    <b>
         <p ALIGN="CENTER">6.1</b></td>
    
    <p>
         Test for
         accessibility using available tools.</td>
    
         <p> Yes</td>
    
    <p>Tested with MSAA tools and JAWS on Windows.
       </td>
     </tr>
    

    </table> </body>

    </html>