Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 65968

Summary:	[Webapp] Access
Product:	[Eclipse Project] Platform	Reporter:	Isaac Porat <isaac.porat>
Component:	User Assistance	Assignee:	platform-ua-inbox <platform-ua-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	Keywords:	accessibility
Version:	3.2
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Isaac Porat

2004-06-07 10:21:19 EDT

For a blind user the help system is difficult to navigate because the user, 
using a screen reader, needs to go through all the links to get to the 
content.  It would be very helpful if a link at the top of the page would skip 
all navigations and go directly to the content and if any of the links could 
take the user not just to the relevant page but to the content part of the page.

Thank you for your consideration.

Comment 1 Konrad Kolosowski

2004-06-07 10:56:50 EDT

It is not necessary to go through all the links.  On Windows, for example, 
user can press Ctrl+Tab to navigate to the next frame (toolbar or view etc.), 
and not go throgh all links inside frames.  As documented in bug 56956, in 
3.0M9, there is even another shortcut, that eliminates a need for multiple 
Ctrl+Tab to get to the content frame. ALT+K will get user there.

"link at the top of the page would skip all navigations and go directly to the 
content" - could you provide more details, a graphics mockup of proposed 
desing?
"not just to the relevant page but to the content part of the page" - what 
exactly is the difference between the two?  Help does not have much control on 
the design of the content.

Thanks.

Comment 2 Konrad Kolosowski

2004-06-09 12:47:02 EDT

Post 3.0.

Comment 3 Chris Goldthorpe

2006-10-30 12:18:42 EST

We are going to be improving the accessibility of the help system in Eclipse 3.3, including better support for screenreaders. I'll add updates as our plans become more detailed.

Comment 4 Lars Vogel

2019-09-06 03:33:07 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it and remove the stalebug whiteboard tag. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.