24713 2014-02-18 20:21:01 +0000 some <th> elements and most elements with tabindex="" should probably count as interactive 2014-02-20 23:38:35 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#interactive-content P3 normal Unsorted 24750 1 contributor ian ian mike contributor oldest_to_newest 100817 0 contributor 2014-02-18 20:21:01 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#interactive-content Complete: http://www.whatwg.org/c#interactive-content Referrer: Comment: some <th> elements and most elements with tabindex="" should probably count as interactive Posted from: 2620:0:1000:167c:b1bc:1289:55f0:5f5e by ian@hixie.ch User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1809.0 Safari/537.36 100819 1 ian 2014-02-18 21:12:40 +0000 While I'm at it, elements that would otherwise not be focusable but are because of an explicit tabindex="" attribute should probably be ok in <canvas> and hit regions, since they're basically just buttons at that point. (Without such a change, making tabindex="" set an element to interactive would mean it was no longer allowed in <canvas>.)