[accesswatch]

Closes #246.

On github.com the branch field both filters existing branches and names a new one. So a screen reader user hears that no branches match, and then has to press Tab past the Tags tab to reach Create branch. @DebeeArmstrong described this exactly.

This updates every place that teaches the step:

• the Challenge 4 issue template (in learning-room/ and at the root)
• the challenge hub (docs/CHALLENGES.md)
• the reference solution
• the Day 1 agenda

The HTML was rebuilt with npm run build:html. validate:authoritative-sources and test:automation (93 tests) pass.

It combines the three contributor pull requests for this issue: #256 and #257 by @abinyads-dev, and #258 by @Valeriia458. Those two updated different files, one the hub and one the template, and the hub version had list formatting that would not render. This keeps their wording and applies it everywhere.

---

Generated by Claude Code

[github-actions]

Learning Room Validation Report

Great work. Your changes look good.

Resources

• Markdown Guide
• Accessibility Standards
• Open Source Culture

[github-actions]

Hi! I am Gandalf, your workshop agent. I bring a little magic to make this interaction clear, helpful, and fun. Here is my review of your pull request:

Report Status

Validation Needs Attention [ACTION REQUIRED]

Required Checks

• Issue Reference

• PR Description

• File Location
  Changes should be in learning-room/ directory only
  Student contributions should modify files in learning-room/docs/ only. Other directories are workshop infrastructure.

Learning Resources

Based on your changes, these guides might help:

---

Automated validation by Learning Room Bot. Gandalf generated this review. Last updated: 2026-10-28T21:15:43.674Z
Questions? Check PR Guidelines or mention @Facilitator

[github-actions]

Progress Update

Great work, @accesswatch!

Current Level: Explorer
Merged PRs: 26
Next Level: Contributor (NaN more merged PRs)

Available Challenges:

• 01 Scavenger Hunt
• 02 First Issue
• 03 Join Conversation

Keep going!

[github-actions]

Skill Unlocked: Contributor

Congratulations @accesswatch! You've completed a general challenge.

Your Progress

This PR demonstrated:

What's Next?

Check your profile for the next available challenge, or explore:

• Learning Path Tracker
• Available Challenges

Keep up the amazing work!

---

Progress tracked by Learning Room Skills Engine

[github-actions]

Peer Review Assigned

Hi @accesswatch! Your PR has been automatically paired with @taylorarndt for peer review.

For @taylorarndt:

This is a great opportunity to practice code review skills! Here's what to look for:

Content Quality:

• Does the change accomplish what the issue describes?
• Is the writing clear and helpful?
• Are there any typos or grammar issues?

Accessibility:

• Proper heading hierarchy (H1 → H2 → H3, no skips)?
• Descriptive link text (not "click here")?
• Alt text on images?
• [TODO] markers removed?

Documentation:

• Code blocks are properly formatted?
• Tables have headers?
• References/links work correctly?

Review Guidelines:

• Be kind and constructive
• Suggest improvements, don't just point out problems
• Ask questions if something is unclear
• Approve when ready or request changes with explanation

Resources:

• How to Review PRs
• Writing Good Review Comments

---

Pairing by Learning Room Grouping Engine