This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29250 - 4.3.6. Headings with built-in tabstop [w/o tabindex=0 attribute]
Summary: 4.3.6. Headings with built-in tabstop [w/o tabindex=0 attribute]
Status: RESOLVED WONTFIX
Alias: None
Product: HTML.next
Classification: Unclassified
Component: default (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-28 20:39 UTC by Devarshi Pant
Modified: 2016-04-28 15:01 UTC (History)
3 users (show)

See Also:


Attachments

Description Devarshi Pant 2015-10-28 20:39:17 UTC
URL: https://html.spec.whatwg.org/multipage/semantics.html#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements

I have seen many applications (internally) where headings have tabindices of "0," which in turn have helped sighted keyboard only users when they tab through webpages. Now, some may disagree - but I would like to get a feel for whether this is something HTML.n can implement.  Reiterating it -- would it help to make headings receive keyboard focus by default?

thanks,
Devarshi
Comment 1 Charles McCathieNevile 2016-04-28 15:01:43 UTC
No, we won't do this. In cases where it makes sense people can continue to use tabindex=0 but otherwise making all headings interactive just clutters up user navigation.