Reassigned to ES.

Broken!

In OOo 1.1 you could use Shift-F5

Breaks keyboard access, P2, Target 2.2

Assigning to Oliver

It is not broken.
issue 33307 assigned the function "to next frame" from Shift+F5 to Shift+F4

Well that's great to know. Thanks.

Where are all these keyboard shortcuts defined so that a mere mortal
like myself can know what they are without having to file a "bug" in
order to find out?

AFAIK there's no complete list of all shortcuts available.
You can either have a look at Tools/Configure in your OOo to see which key is
linked to which command or you can take a look at the code. For the Writer it's
in
http://sw.openoffice.org/source/browse/sw/sw/uiconfig/swriter/accelerator/en-US/default.xml
(use the download link of the top revision)

I just tried Shift-F4 as you suggested on the sample document:
http://bugzilla.gnome.org/attachment.cgi?id=74579&action=view
Firstly there is no indication for a blind person when you need
to hit Shift-F4. Even doing it visually, it doesn't allow me to
navigate the forms. Down arrow just moved the form done. Tab
allows me to jump from one form to another.

Reopening the bug. Please explain how to navigate all the fields
in each form.

Thanks.

Jumping to the first control works using Ctrl+F5, after that travelling works
with Tab
BTW: The referred document has a very strange tab order.

Sorry to reopen this yet again, but we are still unable to navigate the
test document in Orca using the keyboard. See comment #7 in the corresponding
Orca bug:

http://bugzilla.gnome.org/show_bug.cgi?id=361737#c7

Could you please describe:

1/ when to know when to type Shift-F5 to get to the form.
2/ how to get to each of the fields within the form after you've
   typed Shift-F5.

Thanks.

>1/ when to know when to type Shift-F5 to get to the form.
It's Ctrl+F5. 
What do you mean with "how to know when"? The user should know that the document
contains form controls that have to be filled. 

>2/ how to get to each of the fields within the form after you've
   typed Shift-F5.
After typing Ctrl+F5 the tabulator key allows travelling between the controls.

> What do you mean with "how to know when"? The user should 
> know that the document contains form controls that have to 
> be filled.

We are talking about a blind user here, who is trying to
navigate an unknown OOo Writer document with the help of
the Orca screen reader. Now that we know there is a
keyboard shortcut to get into the form, I've adjusted the
summary of the bug to better reflect the real problem.

> After typing Ctrl+F5 the tabulator key allows travelling
> between the controls.

My experience with OOo v2.1, was that the Tab key moved you to
the next form, not the next field within the form.

AFAIK the Tab-Key handling hasn't changed since 2.1

I change the target to 2.x because this is not broken.
mt added to help finding a solution of the problem.

Not a defect, changed to Enhancement

added myself to cc

target 2.4; mt and os are going to discuss the matter soon

We can compare what happens here with the accessibilty of a Browser and the
accessibilty of the web-page displayed in this browser. If the page is not
accessible, the browser cannot stand for the missing features of the page...

In the linked sample, I'd say the creator of document is to blame for the lack
of accessibilty, not OOo.

First, this is not a "normal" read-only document but a document containing a
form *in active mode* (in this case, there is no cursor focus in this document).

To make this document accessible (see my attachement below) some simple
manipulations should have been made:
(for the following explanations, please switch on the "Form Design" and "Form
Controls" ON under "View - Toolbars")

1) Automatic control focus - to set the cursor in the form automatically when
opening the document:
-> In the Form Design toolbar, click on "Automatic control focus"

2) Tab order - As OS said, the tab order is weird:
-> In the Form Design toolbar, click on "Activation Order", then on "Automatic sort"

Now, it would be also nice to give the controls a pertinent name.

Finally, it is not possible to set the cursor in the text in the background of a
form when this form is active. So, in order to be able to read the title and
"Notes for Guidance", this text should have ben inserted into a text box, just
like the "Policy" at the end of the document.

Considering all this, I'll close the issue as invalid.

Created attachment 48181 [details]
Accessible sample

.

closed