[wp-trac] [WordPress Trac] #26504: Semantic elements for non-link links

[WordPress Trac]

#26504: Semantic elements for non-link links
----------------------------+--------------------------------
 Reporter:  GaryJ           |       Owner:
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Administration  |     Version:  3.8
 Severity:  normal          |  Resolution:  invalid
 Keywords:  close           |     Focuses:  ui, accessibility
----------------------------+--------------------------------

Comment (by joedolson):

 Some notes from the February 25th accessibility team meeting discussing
 this ticket
 (https://wordpress.slack.com/archives/accessibility/p1424892308002647)

 How to address whether a button or link should be changed:

 Anchors with null or meaningless HREF values: href='#', no href,
 href='#something' where #something does not exist
         - Should be a button

 Anchors with meaningful on-page HREF values href='#something' where
 #something does exist
         - Could be a either a button or an anchor

 Anchors with meaningful off-page HREF values that are renderable (but
 actual behavior is AJAX)
         - Could be a link when JS not available, should be a button the
 rest of the time.

 Anchors with meaningful off-page HREF values that are *not* renderable
         - Should always be a button, but perhaps the target should be made
 renderable

 Buttons that direct to new locations on the same page
         - Could be either a button or a link.

 Buttons that direct to new locations on different pages.
         - Should be a link.

 With the 'either/or' cases, each button or link will need individual
 consideration, depending on the context of the control. If it could be an
 anchor, but is in the middle of a whole bunch of buttons, then it would
 probably be better UX to leave it as a button, for example.

 For HTML, we'll be using the classes .button-link for buttons that should
 look like links.

 To organize the work, we'll be creating new tickets. Each new ticket will
 pertain to a specific file that displays buttons or links that need to be
 changed. When creating patches, be sure to address both the file that
 displays the button or link and any JS files that manage the behavior of
 the control.

 Name tickets with something consistent and meaningful, such as the file
 name and location of the file being worked on.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/26504#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform