Skip to main content

Search and Top Navigation

#7163 closed feature (fixed)

Opened March 18, 2011 02:21PM UTC

Closed March 07, 2014 02:22PM UTC

Investigate viability of using <a tabindex=0> instead of <a href="#">, etc.

Reported by: ajpiano Owned by:
Priority: minor Milestone: git
Component: [meta] ui.a11y Version: 1.8.10
Keywords: Cc:
Blocked by: Blocking:
Description

As I understand it, the main thing holding us back from increased use of the tabindex attribute for allowing focusability to arbitrary elements, and avoiding using href="#", is the fact that elements that are not natively tabbable without tabindex are not tabbable on Safari 3, which runs only on [relatively] older phones. If switching to tabindex can help, for instance, with suppressing the browser status bar when hovering over a dialog close button, and other problems, we should investigate whether the usage levels of Safari 3 at present truly merit keeping tabindex "tabled."

Attachments (0)
Change History (9)

Changed February 27, 2012 03:43PM UTC by jzaefferer comment:1

So we don't support Safari 3 anymore. I don't know which other components this affects, but Scott dropped the accordion anchors already. Would probably be more useful to have component-specific tickets.

Changed June 26, 2012 01:22AM UTC by scottgonzalez comment:2

type: enhancementfeature

Changed October 11, 2012 02:40PM UTC by scottgonzalez comment:3

milestone: 1.9.01.10.0

Changed November 04, 2012 05:37PM UTC by jzaefferer comment:4

Scott, any reason to keep this open? As far as I can tell there isn't.

Changed November 04, 2012 06:58PM UTC by scottgonzalez comment:5

The ticket description gives the reason this is open. Why do you think it shouldn't be open?

Changed November 04, 2012 07:02PM UTC by mikesherov comment:6

status: newopen

Replying to [comment:1 joern.zaefferer]:

So we don't support Safari 3 anymore. I don't know which other components this affects, but Scott dropped the accordion anchors already. Would probably be more useful to have component-specific tickets.

I think this is why. Either way, it shouldn't be "new", so I'm marking it as open.

Changed January 25, 2013 09:23PM UTC by tj.vantoll comment:7

milestone: 1.10.0none

Changed March 07, 2014 02:16PM UTC by tj.vantoll comment:8

I tested this out and

tabindex="0"
works fine in our supported browsers (IE 8+, Firefox, Chrome, Safari 5.1+, Opera, and Windows 8 touch devices). For the most part though, I think we should avoid
<a>
elements without
href
attributes anyways - since they're semantically meaningless they really should be
<span>
s or
<div>
s.

I switched the slider over for #9890, and dialog's close button now uses a button widget, so is there anyplace this issue is still relevant? Datepicker comes to mind, but we'll be addressing that in the rewrite. Spinner uses

<a>
elements, but they use
tabindex="-1"
and no
href
.

Changed March 07, 2014 02:22PM UTC by scottgonzalez comment:9

milestone: nonegit
resolution: → fixed
status: openclosed

A quick search seems to confirm that those are all the uses. I also never wanted to continue using anchors when we made this change.

Closing as fixed since this was just a meta ticket.