Ticket #6623 (closed Bug: wontfix)

Opened 4 years ago

Last modified 16 months ago

Colors dialog: up/down arrow keys not working as expected

Reported by: wwalc Owned by:
Priority: Normal Milestone:
Component: Accessibility Version: 3.0
Keywords: Discussion Cc:

Description

In the first colors dialog that appears straight after pressing "Text Color" or "Background Color" button, the up/down keyboard arrow keys doesn't work as expected - pressing the down key moves to the next color on the right side instead to the next color in the line below.

It looks like it never worked properly.

Change History

comment:1 Changed 4 years ago by garry.yao

  • Component changed from General to Accessibility

This's an a11y v.s. u7y problem, as for disabled people, the color panels are presented as list.

comment:2 Changed 4 years ago by fredck

Based on that we should guarantee the list navigation to be in line with accessibility standards. If the arrow keys are not used for that, we can consider having them used for visual navigation.

comment:3 Changed 4 years ago by garry.yao

  • Keywords Discussion added

@Fred, I don't understand how to tackle both in an acceptable way

comment:4 Changed 17 months ago by Reinmar

I also don't have an idea how could this work. If person using screen reader will press down key (instead of right) he will jump to the next line, unless we'd discover what this person really meant (is he using screen reader or not).

comment:5 Changed 17 months ago by Reinmar

  • Status changed from new to pending

comment:6 Changed 16 months ago by j.swiderski

At first this doesn't sound very professional but if there is no other way, perhaps we could provide two sets of keys like in computer game ;)

Visually impaired could use arrows while other users W, A, S, D :). Of course some explanation in docs why arrows work differently

This's an a11y v.s. u7y problem, as for disabled people, the color panels are presented as list.

should be provided.

I don't think anyone will agree but this way we can have both and many users are familiar with using WASD for "navigation".

comment:7 Changed 16 months ago by Reinmar

Come on... I would never thought about using WSAD :P Never, ever :D

comment:8 Changed 16 months ago by j.swiderski

That is why you should read docs to know this or perhaps dialog could provide such hint.

I knew you won't agree thus I have proposed this as "if there is no other way" :P

Last edited 16 months ago by j.swiderski (previous) (diff)

comment:9 Changed 16 months ago by wwalc

There is no point in adding shortcuts that noone will use. As a user I'd not use anything else than arrow keys to cycle through colors. It's possible to change colors using arrow keys already, so unlike e.g. with magicline, there is no need to introduce another hard-to-guess shortcut.

comment:10 Changed 16 months ago by Reinmar

  • Status changed from pending to closed
  • Resolution set to wontfix

I agree. Closed.

Note: See TracTickets for help on using tickets.
© 2003 – 2012 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy