Bug 402476 - 2 additional points for the "Accessibility features" help doc
Summary: 2 additional points for the "Accessibility features" help doc
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: User Assistance (show other bugs)
Version: 4.3   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 3.8.2+   Edit
Assignee: Carolyn MacLeod CLA
QA Contact:
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks: 376011
  Show dependency tree
 
Reported: 2013-03-05 15:01 EST by Carolyn MacLeod CLA
Modified: 2013-03-25 09:21 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carolyn MacLeod CLA 2013-03-05 15:01:26 EST
As a follow-on to bug 400997 comment 9, there are 2 more points I need to make on the "Navigating the user interface using the keyboard" help page, and then I think the doc will be complete:

1) Typing Enter when focus is on a page tab (i.e. editor or view tab) will move focus to the page tab's contents. (in SWT terms, if a CTabItem has focus, you can type Enter to move focus to the CTabItem's control). This is true whether you are in a view stack or an editor stack.

2) The sentence "Ctrl+PageUp and Ctrl+PageDown can be used for switching between the open editors" does not mention that Ctrl+PageUp and Ctrl+PageDown can be used for switching between views in a view stack.
Comment 2 Carolyn MacLeod CLA 2013-03-12 17:22:06 EDT
Dani, can you please review the words in this commit?
http://git.eclipse.org/c/platform/eclipse.platform.common.git/commit/?id=896bcf32d1e97096552199ffd4d4bd746ce98579

After bug 376011 was fixed, the old description of tab traversal did not match reality. So it is important to have the correct doc backported to 4.2.2+.

You can test out the current behavior in any very recent build, since about the beginning of March. (I know that you can see it in I20130306-2330).

Thanks!
Comment 3 Dani Megert CLA 2013-03-13 09:26:24 EDT
"While on an editor's or view's tab, the left or right arrow keys select
 a different editor or view, and the Enter key navigates directly into
 the selected editor or view."

I would rephrase this a bit:
When the focus is on an editor or view tab, pressing the left/right arrow key moves to the previous/next tab and pressing Enter moves the focus to the current selection in the editor or view.

"/" could also be replaced with "or".
Comment 4 Carolyn MacLeod CLA 2013-03-14 11:39:32 EDT
Thanks - I like your words. Done, and kept the slashes:
http://git.eclipse.org/c/platform/eclipse.platform.common.git/commit/?id=ce567c3435da1332266e3cb2bb03348efa7fd0b3
Comment 5 Carolyn MacLeod CLA 2013-03-19 15:27:15 EDT
Backported the patch from comment 1:
http://git.eclipse.org/c/platform/eclipse.platform.common.git/commit/?h=R4_2_maintenance&id=423202c8a1dd4016d5a7e266ea4f431666de480a

Dani, can you please verify that I did the right thing on line 117 of org.eclipse.platform.doc.user/contexts_AntUI.xml? There was an href conflict:
OLD:    <topic label="Configuring accessibility options for textual editors" href="PLUGINS_ROOT/org.eclipse.platform.doc.user/concepts/accessibility/text_editor.htm"/>

NEW:    <topic label="Accessibility features in textual editors" href="concepts/accessibility/text_editor.htm"/>

The old annotation was: Fixed bug 272167: [content assist] screen reader should read first proposal
Comment 7 Dani Megert CLA 2013-03-21 09:35:07 EDT
(In reply to comment #5)
> Backported the patch from comment 1:
> http://git.eclipse.org/c/platform/eclipse.platform.common.git/commit/
> ?h=R4_2_maintenance&id=423202c8a1dd4016d5a7e266ea4f431666de480a
> 
> Dani, can you please verify that I did the right thing on line 117 of

Looks good.
Comment 9 Dani Megert CLA 2013-03-25 06:43:58 EDT
I've update the bundle version in the manifest and the pom for both versions.
Comment 10 Carolyn MacLeod CLA 2013-03-25 09:21:12 EDT
Thank-you, Dani.