anchor tags have no link content or id, buttons would be better
See original GitHub issueFor accessibility reasons, anchor tags should have valid link content/text or at the very least, an id
attribute.
I think an id
would maybe be the easiest to add, maybe with the prefix from the instance of the editor itself so you can ensure a unique value if multiple editors are on a page.
Ideally, you would replace them all with button
elements, which would probably be more semantically correct. See the recommendation regarding accessibility in the MDN docs
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Stop using anchors as buttons! | Ancestry Corporate
Simply use an id attribute on the containing element of the region you want "linkable." Don't use an empty <a name="my-section"></a> element. Are...
Read more >Anchors vs Buttons - bitsofcode
Because no link is related to the element, only the default user-action pseudo-classes ( :hover , :active and :focus ) are available to...
Read more >Should you use a button tag or an anchor tag for clickable ...
The main reason is that it provides better accessibility without extra ... Anchors are also ideal for linking to other content in the...
Read more >Valid to use <a> (anchor tag) without href attribute? [duplicate]
Yes, it is valid to use the anchor tag without a href attribute. If the ...
Read more ><a>: The Anchor element - HTML: HyperText Markup Language
Content within each <a> should indicate the link's destination. If the href attribute is present, pressing the enter key while focused on the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @RIP21. PR for this project is at #43
Merged! #43