Thanks for looking into this.
From my research there isn’t a WCAG Success Criterion that explicitly mandates moving focus to the first new item. A A11y expert I follow does recommend it though.
What I did find is recommendations to meet accessibility principles for dynamic content updates, particularly under Success Criterion 2.4.3 (Focus Order) and Success Criterion 4.1.2 (Name, Role, Value), as well as ARIA best practices for managing focus in dynamic interfaces.
Here are the relevant W3C resources and explanations (which Grok helped in summarizing):
- WCAG 2.1 Success Criterion 2.4.3: Focus Order
- Link: Understanding Success Criterion 2.4.3: Focus Order | WAI | W3C
- Relevance: This criterion requires that focusable components receive focus in an order that preserves meaning and operability. When new content is loaded (e.g., via a “Load More” button), moving focus to the first new item ensures that keyboard and screen reader users can immediately interact with the newly added content, maintaining a logical navigation flow. The W3C notes that dynamic updates should not disrupt the user’s ability to follow the content structure.
- W3C ARIA Authoring Practices - Managing Focus in Composites and Dynamic Content
- Link: ARIA Authoring Practices Guide | APG | WAI | W3C
- Relevance: The ARIA Authoring Practices Guide explicitly recommends managing focus when new content is added dynamically. Section 3.14, “Managing Focus in Composites,” suggests that after a dynamic update (like loading more content), focus should be moved to a logical location, such as the first item in the newly loaded content, to ensure screen reader and keyboard users can continue navigating effectively. This is particularly relevant for “Load More” buttons, as it helps users perceive and interact with the new content without needing to manually navigate to it.