Keyboard navigation documentation fixes

[isabela-pf]

This is a running PR of fixes to the keyboard navigation workshop documentation. As we test the events and/or get feedback, I'll add commits.

This can be merged whenever the fixes need to go live.

🌻

[isabela-pf]

Feedback from the first event #10

• Need to add space for general notes or things that could impact all tests.
• Having common language to reference could also be helpful.
• Maybe this should be on hackmd instead; leverage real RTC?
• Add table of contents to top maybe? To help guide?
• Review might be better split by view (ie. what is open, where) or UI region rather than test running over all of it.
• Maybe add takeaways as an area to fill out per section. I did this manually post-event for the issue it created to make it action-focused. I'm torn because part of me thought it was good I really had to read and synthesize all the feedback because as the person opening this issue I think I need be aware what I'm posting. It also slowed down the transition though, which could become a big problem as we run more events.

Good things!

• Binder made it easy!
• Table placeholders were helpful!

[isabela-pf]

I want to give this self-review with fresh eyes, so I'm moving it out of draft for later.

[isabela-pf]

I think this is good enough pass. I'll pat myself on the back and schedule another prototype meeting to keep trying out this work.