Skip to content

a11y: key={index} undermines screen-reader stability across list mutations #455

Description

@nanaf6203-bit

Summary

Several files use key={index} on lists where stable ids exist (see issue #7); this is also an a11y concern for screen reader announcements because React reconciliation cycles can jumble element ids.

Affected area

Same as #7.

Steps to reproduce

Filter a list, observe that screen reader announces cleared content in unexpected orders.

Expected behaviour

Use stable identifiers.

Acceptance criteria

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Stellar WaveIssues in the Stellar wave programaccessibilityAccessibility (a11y) issuepriority/p3P3 — nice to have

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions