Progress formatter accessibility: screen‑reader compatibility unclear

Goal

Ensure that the RSpec progress formatter provides output that is fully interpretable by screen readers, and that the HTML formatter supplies appropriate ARIA labels for accessibility.

Constraints

RSpec’s progress formatter is text‑based and may lack explicit semantic markers; the HTML formatter may not include ARIA roles by default. Random test ordering can make reproducibility of accessibility audits difficult if the seed is not persisted.

Unresolved Questions

• Does the default progress formatter emit enough semantic cues for screen readers to distinguish test successes, failures, and errors?
• Should the HTML formatter automatically embed ARIA roles and labels for test result elements to satisfy WCAG guidelines?
• What configuration options can be used to persist the random seed across test runs to guarantee deterministic ordering for accessibility assessment?