github / github/erblint-github

Idea: Introduce new rule against use of `target="_blank"` on links

Aberta
#26 0 comentários 0 reações 0 responsáveis Ver no GitHub
good first issue needs-discussion
Linguagem predominante
Ruby
Estrelas
66
Forks
9
Merge médio
9h 26min
PRs com merge (30d)
2

Descrição

`target="_blank"` is frequently used on external links. However, this can be disorienting for many groups of users who don't expect to be in a new window. Using `target="_blank"` requires extra considerations which can be tricky to enforce, so it may be best to avoid them altogether.

From @jscholes in [Slack thread](https://github.slack.com/archives/C0FSWLQ0Y/p1647548349260269):

> TL;DR: don't force links to open in a new tab/window. When you force it, users can not opt out in any browser I know of. However, when you give them the choice from the start, users can make their own decision as to: current window, new tab, or new entire window.
> If links are forced to open in a new tab/window, you have to surface that fact upfront, with "(opens in new tab)" and icons everywhere. Personally, while I see the utility of this, it makes many websites cluttered and a nightmare to read, particularly when you have new-opener links in the middle of text paragraphs. And, can all be avoided by just not doing it in the first place.

#### Resources

- [Link Targets and 3.2.5](https://adrianroselli.com/2020/02/link-targets-and-3-2-5.html)
- [G201: Giving users advanced warning when opening a new window](https://www.w3.org/TR/WCAG20-TECHS/G201.html)
- [Links and new windows](https://accessibility.oit.ncsu.edu/it-accessibility-at-nc-state/developers/accessibility-handbook/mouse-and-keyboard-events/links/links-and-new-windows/)

Guia de contribuição

Abrir o guia de contribuição

Direção de pesquisa

No implementation files, tests, or entry points are named. Start with the linked accessibility guidance to clarify the intended scope; done means the project has a rule that consistently flags target="_blank" links.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Stack de tecnologia
html, ruby
Domínio
accessibility, tooling
Tipo de issue
Funcionalidade
Dificuldade
3/5
Tempo estimado
1-2 dias
Status de atividade
Estagnada
Clareza
Razoavelmente clara
Facilidade para iniciantes
35/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.