DS-077: Add VisuallyHidden and LiveRegion accessibility primitives

[IbrahimIjai]

Context

Shared components need consistent utilities for screen-reader-only labels and
non-disruptive status announcements. Ad hoc sr-only markup and live regions
are easy to misuse or duplicate.

Scope

• Add a VisuallyHidden primitive that can wrap text or semantic elements.
• Add a LiveRegion with polite, assertive, and off modes.
• Support atomic announcements and an optional visually rendered fallback.
• Document appropriate use and cases where visible text is still required.

Acceptance criteria

• Visually hidden content remains available to assistive technology and focusable when needed.
• LiveRegion renders the correct ARIA live, atomic, and role attributes.
• Repeated identical messages can be intentionally re-announced through a documented API.
• Neither primitive affects surrounding layout.
• Tests cover semantic attributes, focusable content, modes, and message updates.

Out of scope

• A global notification queue.
• Replacing visible labels with hidden labels by default.

[Paranoa-dev]

I’d like to take this on. I have experience building accessible React component libraries and implementing reusable WAI-ARIA primitives, including screen-reader utilities, live regions, focus management, and comprehensive component testing.

For this issue, I'll introduce two shared accessibility primitives: a flexible VisuallyHidden component that can wrap text or semantic elements without affecting layout, and a configurable LiveRegion component supporting polite, assertive, and off modes with proper aria-live, aria-atomic, and role behavior. I'll also support atomic announcements, an optional visually rendered fallback, and a documented mechanism for intentionally re-announcing identical messages when required.

I'll document appropriate usage patterns, including when visible labels should still be preferred over hidden ones, and ensure both primitives are easy to consume across the shared component library without encouraging accessibility anti-patterns.

Finally, I'll add comprehensive component tests covering semantic attributes, live region modes, focusable hidden content, layout invariants, repeated message announcements, and regression cases to ensure the primitives remain reliable and standards-compliant.

[Michael997glitch]

@Michael997glitch has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I’ve resolved similar problems in the past and am confident I can implement a clean, efficient fix quickly,if am given the opportunity.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Michael997glitch to this issue.

[samuelfrancis163-eng]

@samuelfrancis163-eng has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello, I'd like to work on this issue because i am confident i can deliver smoothly, Please assign issue to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @samuelfrancis163-eng to this issue.

[edrizxabdulganiyu-blip]

@edrizxabdulganiyu-blip has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello Maintainer, I’ve reviewed the issue description and I’m confident I can work on it effectively. Please assign it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @edrizxabdulganiyu-blip to this issue.

[darius-daniel]

@darius-daniel has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I'd like to work on this issue.

I'll add reusable "VisuallyHidden" and "LiveRegion" primitives that provide a consistent, accessible foundation for screen-reader-only content and status announcements across the component library. The implementation will support the required live region modes ("polite", "assertive", and "off"), atomic announcements, optional visible fallbacks, and a documented mechanism for intentionally re-announcing identical messages, all without affecting page layout. I'll also add comprehensive tests covering ARIA attributes, focusable hidden content, announcement behavior, message updates, and the supported modes, update the accessibility documentation with usage guidance and best practices, and verify the changes by running the project's linting, test suite, and build before submitting the PR.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @darius-daniel to this issue.

[MiaShayla]

@MiaShayla has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello, I explored the issue, understand the expected outcome, and have a solid implementation plan. I'd appreciate the opportunity to work on this and contribute a reliable solution.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @MiaShayla to this issue.

[Tobiloba0]

@Tobiloba0 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi maintainer, I would like to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Tobiloba0 to this issue.

[OkonkwoEmeka]

@OkonkwoEmeka has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

hi maintainer, please i’d love to work on this issue. i’m a professional frontend accessibility developer, and i can finish it properly and on time.

i understand the goal is to add reusable visuallyhidden and liveregion primitives so accessibility behavior is consistent across the interface. i’ll implement the aria/live-region modes, support repeated announcements, ensure no layout impact, and add tests for focus, attributes, and message updates.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @OkonkwoEmeka to this issue.

[Kenlachy]

@Kenlachy has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi maintainer, I’d love to work on this issue. I’ve reviewed the requirements and I’m ready to get started. Please consider assigning it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Kenlachy to this issue.

[barnabasolutayo-lgtm]

@barnabasolutayo-lgtm has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello maintainer. I can resolve this issue quickly. Please assign to me. Thank you

ℹ️ Repo Maintainers: To accept this application, review their application or assign @barnabasolutayo-lgtm to this issue.

[ironhood]

@ironhood has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello, I reviewed the issue requirements and identified the likely areas that need modification. I'd appreciate the opportunity to contribute and submit a well-tested solution.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ironhood to this issue.

[Adeyinka0123]

@Adeyinka0123 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi Maintainer, I've gone through the issue details and understand the requirements. I would love to work on this. Could you please assign it to me?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Adeyinka0123 to this issue.

[bashir347]

@bashir347 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

This is one of the issues to work on

ℹ️ Repo Maintainers: To accept this application, review their application or assign @bashir347 to this issue.

[0xsteins]

@0xsteins has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello, good day, Can I work on this sir?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @0xsteins to this issue.