8 min read
Accessibility identifiers that survive redesigns
How to name and maintain accessibility identifiers so UI tests and automation keep working through visual redesigns and component refactors.
Read the essayEnteror double click opens it
Topics
In this essay
- 1. Separate identifiers from accessibility labels
- 2. Name product actions, not screen furniture
- 3. Keep identifiers close to the component boundary
- 4. Treat lists as identity problems
- 5. Build a small UI test vocabulary
- 6. Version identifiers deliberately during redesigns
- 7. Audit identifiers like public API
- 8. Make identifiers part of the design system contract
- 9. Prefer boring names that stay true