Make lyric lines accessible (#32514 & 19510) [4.7.1]#33436
Make lyric lines accessible (#32514 & 19510) [4.7.1]#33436mathesoncalum wants to merge 3 commits into
Conversation
|
@coderabbitai full review |
✅ Actions performedFull review triggered. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughChordRest navigation between articulations and lyrics is refactored to explicitly handle 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
0b6c55a to
51d9342
Compare
Resolves: #32514
Resolves: #19510
This PR includes lyric lines in the alt+direction navigation chain (ace2e5d) and ensures that the screen reader reads the type name out (0b6c55a). The video below demos the navigation order, which is as follows when starting on a note:
1st verse lyrics -> 1st verse lyrics line -> 2nd verse lyrics -> 2nd verse lyrics line (etc.) -> next note
lyrlinedemo.mov