フォロー
Imagine there is an auto-carousel where each panel has alt text (in accordance with WCAG SC 1.1.1) and a pause button (in accordance with SC 2.2.2).
If the auto-carousel is coded as a live region, this could frustrate screen reader users, as the alt text of each panel would be read aloud frequently, even if they were focusing on other areas of the content. In an accessibility audit, can we classify this implementation as a "failure" from a WCAG perspective? If so, which success criteria could be used as the basis for this?
SC 2.2.2 (Pause, Stop, Hide) or SC 2.2.4 (Interruptions) might apply, but this implementation seems compliant with these SCs because it includes a pausing mechanism.
What about SC 4.1.3 (Status Messages)? I believe the alt text of the carousel panels does not constitute status messages. However, the "Understanding Success Criterion 4.1.3" document lists "Using role=alert or aria-live=assertive on content which is not important and time-sensitive (future link)" as a failure technique.