Link a11y considerations
- Dominant language
- TypeScript
- Stars
- 19
- Forks
- 3
- Avg merge
- 46m
- Merged PRs (30d)
- 13
Description
If you guys could just skim through this article very quickly https://codersblock.com/blog/external-links-new-tabs-and-accessibility/
I think we could get 2 things for us:
1. `screen-reader-only`-like class for `target='_blank'` links
2. Should we somehow enforce the visual indication when `target='_blank'`? e.g. through TS? I think it would be in-sync with the general idea of restricting developers to enforce good a11y principles.
WDYT @utkukaratas @aigoncharov @jankoritak @danad02 @jozefhruska ?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the linked article and reviewing the design system's existing handling of links with target='_blank'. Define the intended screen-reader-only treatment and whether visual-indication enforcement belongs in TypeScript; done means both decisions are documented and implemented with appropriate coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- accessibility, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100