Page MenuHomePhabricator

Challenge use of <a> instead of <button> elements in current library for button representing interface elements
Open, MediumPublic

Description

Challenge use of <a> (and probably <div>) instead of <button> in button resembling interface elements.

Main foundational principle for accessible and universal applicable design: use semantic HTML.

accessible = comprehensive

Event Timeline

Volker_E created this task.Apr 1 2016, 5:52 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 1 2016, 5:52 PM
Restricted Application added a project: UI-Standardization. · View Herald TranscriptMay 22 2016, 11:47 PM
Volker_E renamed this task from Challenge use of <a> instead of <button> to Challenge use of <a> instead of <button> elements in current library for button representing interface elements.Sep 21 2016, 7:36 PM

I did not know that this was the case. Do we have use cases for which we picked links over buttons in the first place?

@Prtksxna Not quite sure, if I understand your question. Please refine!
(ButtonElement has always visually appeared as button)

My question was, do we know why we are using <a>s instead of <button>s in the first place?

Volker_E triaged this task as Medium priority.Nov 16 2016, 6:28 PM
Aklapper removed Volker_E as the assignee of this task.Jun 19 2020, 4:23 PM

This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!

For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)