Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Focus not always visible on JupyterLab initial page #167

Closed
2 of 3 tasks
Tracked by #6
gabalafou opened this issue Nov 7, 2022 · 7 comments
Closed
2 of 3 tasks
Tracked by #6

Focus not always visible on JupyterLab initial page #167

gabalafou opened this issue Nov 7, 2022 · 7 comments
Assignees
Labels
area: codebase 💻 Item related to codebase and software development work area: testing ☑️ Testing related issues or tasks area: WCAG compliance ♿️ This item related to WCAG standards and their compliance

Comments

@gabalafou
Copy link
Contributor

gabalafou commented Nov 7, 2022

Description

On the initial page in JupyterLab, some elements that receive focus by pressing the tab key do not have a visible focus indicator, which is a violation of WCAG 2.4.7.

This issue is about fixing those focus indicators for the initial page in JupyterLab.

Value / benefit

Understanding WCAG 2.4.7 explains why.

Implementation details

No response

TODO

  1. area: testing ☑️ type: task ✅
  2. gabalafou

Updates

No response

@gabalafou gabalafou added status: needs triage 🚦 Someone needs to have a look at this issue and triage type: bug 🐛 Something isn't working labels Nov 7, 2022
@gabalafou gabalafou changed the title Make focus visible on JupyterLab initial page Focus not always visible on JupyterLab initial page Nov 7, 2022
@trallard trallard added this to the Sprint 4 - Europa 🌕 milestone Nov 14, 2022
@gabalafou
Copy link
Contributor Author

@gabalafou
Copy link
Contributor Author

Update on this issue.

This issue stalled on the test-writing sub-task because I couldn't make the test that I wrote pass. I believe that Mark's PR fixed the issue, but I need to go back and try testing it.

@trallard
Copy link
Member

trallard commented Mar 14, 2023

@gabalafou can you remind me what we said about this particular issue, will you be working on it? are we pausing this?

@gabalafou
Copy link
Contributor Author

gabalafou commented Mar 14, 2023

This issue has 2 parts:

  1. fix
  2. regression test

The first part is done. The second part is still outstanding, and I plan to work on it in the upcoming weeks as part of my focus on accessibility testing in order to both integrate accessibility regression testing with general JupyterLab testing and to get ready for my talk at JupyterCon.

@gabalafou
Copy link
Contributor Author

gabalafou commented Mar 14, 2023

By the way, this is the PR that does the "fix" part of this issue (it just doesn't have a regression test yet):

@trallard
Copy link
Member

Regression tests added - need more things fixed

@gabalafou
Copy link
Contributor Author

I'm going to mark this as closed, even though there are some things that are still in progress:

I'm going to mark it as closed because the bulk of the work that I can do for this issue is already done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: codebase 💻 Item related to codebase and software development work area: testing ☑️ Testing related issues or tasks area: WCAG compliance ♿️ This item related to WCAG standards and their compliance
Projects
Status: Done 💪🏾
Development

No branches or pull requests

2 participants