584121 - (console-a11y) [meta] Web Console should be keyboard accessible.

Status: RESOLVED INCOMPLETE

(DevTools :: Console, defect, P5)

Description

[David Bolter [:davidb] (NeedInfo me for attention)]

Spun off 583816 comment 6.

We need to provide keyboard access to the toolbar.

Comment 1

[David Bolter [:davidb] (NeedInfo me for attention)]

I asked Gijs how keyboarding works on Chatzilla, with tab completion of nicks etc.

The strategy CZ uses is that if the user hits tab repeatedly, detect this and tell them that f6 is used to cycle in/out of the input box (but in user facing wordsmithy).

Comment 2

[Kevin Dangoor]

This bug has a nice, general summary, so I'm bundling up other keyboard accessibility bugs as blockers for this one. We should look to take care of this in beta 5.

Comment 3

[Zhenshuo Fang (:fang) - Firefox UX Team]

Not sure this needs ui-wanted. Deleted for now but can be added later.

Comment 4

[Mihai Sucan [:msucan]]

Should we continue to keep this bug open?

Is it possible to somehow get a keyboard accessibility evaluation of some sorts for the web console? Maybe with some filed bug reports as needed. We have recently made some changes - added shortcuts for common operations, added accesskeys and made all links in the output focusable by Tab.

Thank you!

Comment 5

[David Bolter [:davidb] (NeedInfo me for attention)]

Thanks!

One thing I'm curious about... bringing up the web console via keyboard routes focus to the input line nicely. If I travel away using F6 I don't seem to be able to return using F6. A workaround seems to be closing and reopening the web console.

I think we could close this one as fixed (thanks) and reopen one for the F6 issue if you agree? (I might be missing something)

Comment 6

[Joe Walker [:jwalker]]

Let's remember the work we're doing to replace the JS input in the web console with something more JSTerm like.

Comment 7

[Mihai Sucan [:msucan]]

(In reply to David Bolter [:davidb] from comment #5)
> Thanks!
> 
> One thing I'm curious about... bringing up the web console via keyboard
> routes focus to the input line nicely. If I travel away using F6 I don't
> seem to be able to return using F6. A workaround seems to be closing and
> reopening the web console.
> 
> I think we could close this one as fixed (thanks) and reopen one for the F6
> issue if you agree? (I might be missing something)

Sounds good to me. Thank you!

Comment 8

[Mihai Sucan [:msucan]]

Here's the bug for focusing the web console input: Bug 612253.