This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 133436 - Current line number not read by screenreader
Summary: Current line number not read by screenreader
Status: RESOLVED WONTFIX
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: David Strupl
URL:
Keywords: A11Y
Depends on:
Blocks:
 
Reported: 2008-04-21 11:53 UTC by pacf1
Modified: 2010-09-28 15:00 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pacf1 2008-04-21 11:53:28 UTC
I didn't found out on which line I was. Number of line is for me quite important orientation point (for example when I 
know that error is somewhere aroud line 44).
Comment 1 Jaromir Uhrik 2008-05-12 16:54:25 UTC
This is true, it is not possible to read by a screenreader the line number in NetBeans IDE which is a bug.
Comment 2 Vitezslav Stejskal 2008-05-18 18:35:14 UTC
Do all these issues qualify as A11Y problems? If so, please use the keyword. Thanks
Comment 3 Max Sauer 2008-11-18 14:01:40 UTC
To solve this issue, gutter would have to become focusable, since screenreaders are focus-based (ie. read a11y names, descriptions, text while a 
component is focused, upon focus change). But such change will probably hinder normal development, I don't think anyone beside visually impaired people 
would like to have gutter focusable. Traversal would have to be defined in a proper way after this change also.

I don't think there is any support for getting JEditors current line currently, so the only way is probably through focusing gutter.
Comment 4 David Strupl 2010-09-28 15:00:08 UTC
As per Max's evaluation we will not change the gutter to be focusable.

The other solution would be if the currently focused JEditorPane would provide the info somehow to the screenreader.

I am marking this as wontfix.