Open isabela-pf opened 1 year ago
Hello everyone, many thanks for @isabela-pf for providing the keyboard navigation review of Notebook 7!
I am happy to announce that we have received a development grant from @InseeFr for 8 weeks of work to address the keyboard navigation issues of the Jupyter notebook!
Hopefully, we will be able to resolve most (or all) of the issues that were discovered by Isabela as part of this review. On a separate note, we are aware of the work that @gabalafou has already done on fixing the tab traps in the JupyterLab repository at https://github.com/jupyterlab/jupyterlab/pull/14115. If this PR has not been merged when we start working on this assignment, it will definitely be a priority to help get this work integrated in JupyterLab (review, debugging, etc).
Upon finishing this assignment, we would love to connect with you on the possibility of writing a joint blog post showing progress on these subjects, the multi-stakeholder effort on accessibility, and crediting the audit done by Isabela.
@SylvainCorlay wonderful news! Does the 8 weeks mean that there's a specific start date or deadline on the work or a specific timeframe in which it has to be done? Just wondering in terms of planning.
@SylvainCorlay wonderful news! Does the 8 weeks mean that there's a specific start date or deadline on the work or a specific timeframe in which it has to be done? Just wondering in terms of planning.
We have to spend this budget before the end of December.
EDIT: but I think we will start earlier.
table
practices. there is a recommendation in https://github.com/jupyter/notebook/issues/6800 to make the file browser a table. implementing the recommendation tab patterns then table patterns would sort out of a lot of inconsistencies.Thanks @isabela-pf for reporting this.
- The full order of the content isn't clear because of limited visible focus styling.
- [ ] There are unknown focus areas where the user needs to use the tab key multiple times in a row to continue to the next section without visual feedback where they are. We're not sure if this will be solved by visible focus styling or if they content order is jumping somewhere we don't expect.
Is this still the case ? On my side the focus can be seen every time, in the file browser or the Notebook view. Nevertheless, focusing styles differ according to the elements involved (black outlines, blue outlines, grayed background, blue background). Is this the issue here or are there some items without focus at all ?
- Leaving the active file editor with a keyboard must be done with the
esc
key. This isn't standard keyboard navigation behavior.- Notebook editor (like other file editors) and consoles must be exited with the
esc
key. This isn't standard keyboard navigation behavior.
Do you know if there are suggestions about this when using inline editors ? I think the standard navigation keys are tab
, arrows, enter
and space
, but all of them have a function in an editor.
- JupyterLab cannot switch between split areas Keyboard shortcuts for navigating panes jupyterlab/jupyterlab#4407
Does it also concern Notebook 7 or only Jupyterlab ? Don't know if we can split the main area in Notebook, and if it is expected.
- "If I hide the header (command palette, untoggle "Show Header"), I still tab through the hidden element?"
I can't reproduce it, on my side there is no "unknow" tab, even when the header is hidden.
I can't reproduce it, on my side there is no "unknow" tab, even when the header is hidden.
the tab order doesn't take me to any hidden elements either. maybe something got fixed?
Does it also concern Notebook 7 or only Jupyterlab ? Don't know if we can split the main area in Notebook, and if it is expected.
there is a splitter region in the current notebook main area for extensions. the ARIA authoring practice guide has recommendations for implementing a window splitter. the one splitter in notebook is probably requires different considerations than window splitters in lab.
Do you know if there are suggestions about this when using inline editors ? I think the standard navigation keys are
tab
, arrows,enter
andspace
, but all of them have a function in an editor.
lots of scope creep can happen at the intersection of authoring (ATAG) and WCAG. some inline widgets with features like autocomplete recommend esc implementations. the closest APG pattern would be to think about the notebook or file editor interfaces as part of a complex grid layout interface. in this pattern, Escape: restores grid navigation. If content was being edited, it may also undo edits.
so for terminal, file editor, and notebook cells we should restore grid navigation.
2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A)
Is this still the case ? On my side the focus can be seen every time, in the file browser or the Notebook view.
i was able to find focus each time, too. maybe its all good at the moment.
Nevertheless, focusing styles differ according to the elements involved (black outlines, blue outlines, grayed background, blue background). Is this the issue here or are there some items without focus at all ?
the inconsistent focus is confusing when navigating around the headers. this is likely a big meta issue. theres a lot of different focus treatments across the interface. testing for focus is likely something we could do though. this would be a good piece of automation. sara soueidan's focus indicators post is always worth mentioning when discussing focus
As a part of reviewing the prerelease of Notebook 7 for accessibility issues, we teamed up to run some manual keyboard navigation tests on this Notebook 7 binder.
Many thanks to @ohrely, @gabalafou, @krassowski, @vidartf, @steff456, and @afshin for authoring this review!
Please note that this format of reporting the full review via issue is new and possibly a little messy. Please let me know if there's anything that would make it easier to understand or manage. Thanks!
Takeaways
Based on the full review, I'm going to briefly issues that stood out.
Content order
In the file browser
Areas to navigate
lm-mod-active
class on last active item"esc
key. This isn't standard keyboard navigation behavior.Keyboard/tab traps
esc
key. This isn't standard keyboard navigation behavior.Skip links
Focus
Mixed input
In the file browser
Keyboard shortcuts
Full review
This is the full list of prompts and responses from our review session.