Ticket #7163 (open feature)
Investigate viability of using <a tabindex=0> instead of <a href="#">, etc.
| Reported by: | ajpiano | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | none |
| Component: | [meta] ui.a11y | Version: | 1.8.10 |
| Keywords: | Cc: | ||
| Blocking: | Blocked by: |
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."
Change History
comment:4 Changed 6 months ago by joern.zaefferer
Scott, any reason to keep this open? As far as I can tell there isn't.
comment:5 Changed 6 months ago by scott.gonzalez
The ticket description gives the reason this is open. Why do you think it shouldn't be open?
comment:6 in reply to: ↑ 1 Changed 6 months ago by mikesherov
- Status changed from new to open
Replying to 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.
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.