Bug 86268 - [About] About dialog plug-ins and features tables do not meet accessibility requirements
Summary: [About] About dialog plug-ins and features tables do not meet accessibility r...
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: 3.4 M7   Edit
Assignee: Boris Bokowski CLA
QA Contact:
URL:
Whiteboard:
Keywords: accessibility, helpwanted
Depends on: 38662
Blocks:
  Show dependency tree
 
Reported: 2005-02-23 10:10 EST by Jennifer Calder CLA
Modified: 2008-04-29 13:11 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jennifer Calder CLA 2005-02-23 10:10:31 EST 
1. Choose Help > About Eclipse Platform
2. Choose Feature Details or Plug-in Details

In the resulting tables, if the columns are shorter than their content, Jaws 
will read a truncated version of the content (it will read only what can be 
seen on the screen). There is no method for resizing the column without using 
the mouse. In other views that use this table, the problem also exists, 
however, properties for cell contents can be achieved using the keyboard and, 
in the resulting properties dialog, the full cell contents can be read by the 
screen reader.
Comment 1 Tod Creasey CLA 2005-02-23 11:18:58 EST 
This is a general issue with tables. This is an OS limitation IIRC.
Comment 2 Nick Edgar CLA 2005-02-23 11:28:25 EST 
I seem to remember something about Jaws doing screen scraping when it should be
using the MSAA API.  The MSAA API provides the full strings, but screen scraping
only yields the truncated string.
Comment 3 Jennifer Calder CLA 2005-02-23 13:26:52 EST 
To Tod's comment: Agreed - but, with other tables (at least those that I've 
played with - I'll use the Problems and Error Log views as examples), the user 
can read those cell contents by accessing a properties dialog. I'm not 
suggesting that the properties dialog is the best way out - I, personally, 
think it's ugly.. but, at least in those views, it is possible to read those 
cell contents.
Comment 4 Jennifer Calder CLA 2005-03-02 11:27:48 EST 
Actually, I think that this could be closed as a duplicate of bug 38662. If 
you agree, then please feel free to go ahead and do this.
Comment 5 Nick Edgar CLA 2005-03-07 14:20:01 EST 
I'll leave this one open for the concrete accessibility issues with the About
dialogs.  Bug 38662 only covers resizing.  What is needed is an accessible
alternative to reading the entire entry (row) in the table.  A properties dialog
is just one option.
Comment 6 Nick Edgar CLA 2006-03-15 11:56:09 EST 
Reassigning bugs in component areas that are changing ownership.
Comment 7 Boris Bokowski CLA 2007-01-02 11:10:24 EST 
Reassigning bugs to reflect changes in ownership.
Comment 8 Kim Horne CLA 2007-06-21 16:21:00 EDT 
a properties dialog would be nice.
Comment 9 Boris Bokowski CLA 2008-04-23 17:23:52 EDT 
Fix released to HEAD. I added another button "Columns..." to the two dialogs. Clicking it opens a new dialog with which column sizes can be edited.
Comment 10 Boris Bokowski CLA 2008-04-29 13:11:34 EDT 
Verified using I20080429-0100 on Windows XP.