Re: [Libreoffice] [PATCH] vcl: Printing UI "page range" autofocus

Hi,

At 06:50 22-10-2011, Maxim Iorsh wrote:

> When the user selects "Pages" radio button in the Range section, it is very
> reasonable to expect that she would now want to specify the range. Thus moving
> the focus automatically to the page range edit box would save the user a mouse
> click.

Unrequested focus changes that are not announced in advance are not 
good practice for accessibility reasons.

1. When a screen reader user (typically a blind user) encounters a 
set of radio buttons, the only way to find out what the buttons are, 
is going through them with the up/down arrow. If the focus changes to 
the page range input field when she puts the focus on the Pages radio 
button, the label for the radio button will either not be read by the 
screen reader or the labels for the radio button and the edit field 
will be run together, which might lead to confusion.

2. Keyboard users (not only blind users) move through dialogs like 
the Print dialog with the Tab key and the Shift+Tab key. The latter 
is for navigating backwards. With this patch, what happens when the 
user presses Shift+Tab from the Page Range field in order to move 
back to the radio buttons? Does the focus immediately get pushed back 
to the edit field, making backwards navigation impossible?

Best regards,

Christophe



> Code is contributed under the LGPLv3+ / MPL.
>
> Signed-off-by: Maxim Iorsh <iorsh@users.sourceforge.net>
> ---
>  vcl/source/window/printdlg.cxx |   21 +++++++++++++++++++++
>  1 files changed, 21 insertions(+), 0 deletions(-)



--
Christophe Strobbe
K.U.Leuven - Dept. of Electrical Engineering - SCD
Research Group on Document Architectures
Kasteelpark Arenberg 10 bus 2442
B-3001 Leuven-Heverlee
BELGIUM
tel: +32 16 32 85 51
http://www.docarch.be/
Twitter: @RabelaisA11y
---
Open source for accessibility: results from the AEGIS project 
www.aegis-project.eu
---
Please don't invite me to Facebook, Quechup or other "social 
networks". You may have agreed to their "privacy policy", but I haven't.