Fix the Pagination double live-region announcement that competes with the page status

[mikewheeleer]

Resolve duplicate polite announcements between Pagination and the marketplace

Description

components/Pagination.jsx renders a visible count with aria-live="polite" aria-atomic="true", while app/invest/page.js also pushes "Showing N of M" into its own sr-only role="status" region via getPaginationAnnouncement. After "Load more", both regions announce the same change, producing a double announcement. This issue removes the redundancy so screen-reader users hear the update once.

Requirements and context

• Repository scope: Liquifact/Liquifact-frontend only.
• Choose a single source for the count announcement: either keep the Pagination live region and stop pushing the duplicate string into the page status, or make Pagination's count non-live and let the page status own the announcement.
• Keep the visible count for sighted users in either case.
• Preserve focus restoration to the "Load more" button after each load.
• Document the chosen single-announcement pattern.

Suggested execution

• Fork the repo and create a branch
• git checkout -b a11y/invest-14-pagination-single-announce
• Implement changes
  • Write code in: update components/Pagination.jsx and/or app/invest/page.js.
  • Write comprehensive tests in: create components/Pagination.test.tsx — assert exactly one live region announces the count change.
  • Add documentation: note the pattern in docs/accessibility.md.
  • Add comments explaining the single-announcer decision.
  • Validate a11y with jest-axe on the paginated list.
• Test and commit

Test and commit

• Run npm run lint, npm test, and npm run build.
• Cover edge cases: load-more, last page, and single-item list.
• Include the full npm test output.

Example commit message

fix: remove duplicate pagination live-region announcement

Guidelines

• Minimum 95 percent test coverage for impacted modules.
• Clear, reviewer-focused documentation.
• Timeframe: 96 hours.

Community & contribution rewards

• 💬 Join the Liquifact community on Discord for questions, reviews, and faster merges: https://discord.gg/JrGPH4V3
• ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — if this issue and the maintainers helped you ship, we'd be grateful for a 5-star rating. Clear questions in Discord and tidy, well-tested PRs are the fastest path to a merge and a reward.

[CleanDev-Fix]

Hi, I would like to work on this.

My planned approach:

1. Review Fix the Pagination double live-region announcement that competes with the page status against the existing repo patterns and acceptance criteria.
2. Implement the smallest focused change needed for JavaScript implementation without broad refactors.
3. Verify with the package test/build command documented by the repo and include the results in the PR.

One trade-off I will keep in mind: I will avoid expanding the scope beyond this issue unless you prefer a broader fix.

Does this approach line up with what you want for this issue?

[spiffamani]

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

I'm a full-stack Software Engineer with 3 years of experience
I'd love to take this on — thanks for considering me

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