--- tags: docs sprint --- # Notebook 7 keyboard navigation review An event for the [prerelease of Notebook 7](https://github.com/jupyter/notebook/releases/tag/v7.0.0a6)! ## Intro Event time: Wednesday, October 12 at 10:15am Pacific ([check the time in your timezone](https://arewemeetingyet.com/Los%20Angeles/2022-10-12/10:15/Notebook%207%20keyboard%20navigation%20review)) [Join on google meet]( https://meet.google.com/ipj-yffz-oyo) at the time of the event. Welcome! Thank you for taking the time to learn a few ways to make open source-—or any digital space—-more accessible by testing keyboard accessibility. We are all learning, so please don't hesitate to ask questions. ## Agenda - 0 minutes-20: Welcome, keyboard navigation information, and goals for the event - 20–30: Questions - 30–50: Work time! - 50–60: Review contributions upon request and answer final questions ## Resources Needed for the event: - [The collaborative event PR](https://github.com/isabela-pf/a11y-events/pull/10) - [What to review (Notebook 7 gist)](https://gist.github.com/jtpio/d368ab89cee5123ecee60683115e15f3) - [Keyboard navigation - what to press](https://github.com/isabela-pf/a11y-events/tree/main/workshop-resources/keyboard-navigation/what-to-press.md) Extra information: - [Keyboard Accessibility - WebAIM](https://webaim.org/techniques/keyboard/) - [Browsing with a keyboard - Tetralogical blog](https://tetralogical.com/blog/2021/10/26/browsing-with-a-keyboard/) - [Quick accessibility tests anyone can do - Tetralogical blog](https://tetralogical.com/blog/2022/01/18/quick-accessibility-tests-anyone-can-do/) ## How to participate 1. Go to [our working PR](https://github.com/isabela-pf/a11y-events/pull/10) and review the types of keyboard navigation review listed. 2. Comment on the PR which section of review you plan to work on. You can work as a team if desired! 3. Using the steps listed in your section of the working PR and the Resources section of this agenda, review the interface. 4. Take note of what happens when completing review steps, making sure you can reproduce the review as needed. Mark down any questions you have as well! 5. Make sure to note fill out all areas in your section, even if you need to mark them as n/a or not completable. While you can always add more information, these are the foundation. 6. Submit your review notes on the PR via single-comment [GitHub suggestions](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request). Add review on the line of the "Result" prompt, into a table cell, or in the "Notes" prompt at the end of each section. **Note:** If you think anything is missing, please tell Isabela and she can add it. 7. Repeat steps 2 through 6 as much as you'd like. Be sure to coordinate with others to cover as much as we can. 8. **Optional:** If you have time, you can team up with other participants and give feedback on each others' review. 9. You did it! Great work! ## Review checklist These are a few of the main things we need to make sure our reviews are trackable and reproducible. The review has - [ ] All requested information has been added or marked "n/a" - [ ] There is enough information that someone could recreate the review task (it's reproducible) - [ ] If an area could not be completed, it is marked "could not be completed" with additional notes as needed - [ ] The review is added as a [GitHub suggestion](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request) (so reviewers get credit) ## Questions We'll try and answer questions during the event, but often people have questions that will require a little research or we just plain run out of time. Feel free to leave questions so we can get back to them post-event. - [Your questions here! Adding your name is optional.]