Create draft keyboard navigation event content #8
Conversation
| 7. | ||
| 8. | ||
| 9. | ||
| 10. |
There was a problem hiding this comment.
This sign in area seems like a branch conflict nightmare waiting to happen. I would like to find a way for participants to voluntarily sign in and get clear credit for their work whether or not they get to writing a full review for commit, so this is the placeholder.
There was a problem hiding this comment.
This remains a problem in the latest commit.
|
|
||
| | Area | Able to navigate to the area (yes/no/not applicable) | Able to navigate fully within the area (yes/no/not applicable) | Able to navigate out of the area (yes/no/not applicable) | | ||
| |---|---|---|---| | ||
| | Menu bar | a | b | c | |
There was a problem hiding this comment.
Oops, these are web app related! Would it make sense to have them be more general by using HTML sections?
At best, these sections match the website architecture. At worst, the sections provide a mental model for talking about poor or non-HTML implementations that has been heavily tested.
There was a problem hiding this comment.
I've retemplated this to sort of match the patterns of HTML sections in How to Section Your HTML and HTML Standard for Sectioning content.
|
I'm going to merge this since I haven't gotten further feedback. I'm expecting many changes will need to be made as this event starts getting tested. Onwards! |
The long-awaited second event type is being prototyped! 🎉
This PR introduces some (very) draft resources for testing out an event for reviewing keyboard navigation and contributing a review document to identify issues. This could be run on a whole interface, on a PR (with permission), probably even on desktop apps.
While it doesn't directly fix all the issues, this lack of review knowledge in the broader community has meant that lots of work passes through review missing some foundational accessibility needs. The tests listed in
review-template.mdmay be helpful for reviewers even outside of event contexts. 🌻This PR:
workshop-resources/keyboard-navigationREADME.mdto describe keyboard navigation events and index the resourcesagenda-template.mdas an incomplete event agendareview-template.mdto provide the main content and document participants will contribute to during the eventPhew. 😅 There's a lot in these three files, but the
review-template.mdis the only entirely new piece of content. The rest are based on the image description event resources.