Accessibility: Understanding Why Screen Readers Announce Single Items as a List

This behavior fully meets WCAG 2.2 AA standards, specifically Success Criterion 1.3.1 Info and Relationships. There is no WCAG requirement that restricts a list to having more than one item. The underlying markup is technically valid HTML. Much like a real-world list that contains only one item, it remains a valid list structure.

Salesforce has evaluated this behavior and determined that maintaining the consistent list structure is the most accessible and performant approach for the following reasons:

• Consistent Mental Models: Screen reader users rely on familiar structures to navigate the platform. They expect record actions or specific link groups to be presented as a list. Removing the list structure dynamically would disrupt their memory of where elements are located on the page.
• Predictability and Parity: If Object A has one action configured and Object B has five actions, dynamically removing the list from Object A creates an inconsistent experience. Screen reader users navigating between these objects might think the action bar is broken or missing entirely on Object A.
• Page Performance: Implementing custom logic to constantly count items and dynamically rewrite the HTML structure to remove lists for single items would negatively impact page load times. Protecting page performance is critical for all users.