28555 2015-04-24 15:20:33 +0000 Your use of "Example" and "Note" in the CSS rather than HTML, when it carries substantial heading-type semantics, is kind of double standards ain't it? 2017-06-11 01:15:23 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other All RESOLVED WONTFIX https://html.spec.whatwg.org/#the-ins-element tools P3 normal Unsorted 1 contributor ian ian mike contributor oldest_to_newest 119886 0 contributor 2015-04-24 15:20:33 +0000 Specification: https://html.spec.whatwg.org/multipage/semantics.html Multipage: https://html.spec.whatwg.org/multipage/#the-ins-element Complete: https://html.spec.whatwg.org/#the-ins-element Referrer: https://html.spec.whatwg.org/multipage/links.html Comment: Your use of "Example" and "Note" in the CSS rather than HTML, when it carries substantial heading-type semantics, is kind of double standards ain't it? Posted from: 213.122.174.85 User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.90 Safari/537.36 119892 1 ian 2015-04-24 19:25:21 +0000 Yes. The intent is for the toolchain to address this but I haven't gotten to it yet. 128633 2 mike 2017-06-11 01:15:23 +0000 I’m not sure what the original intent might have been here but we don’t currently have any plans to add h1-h6 heading elements to Notes and Examples in the HTML output of the spec. The semantics (such as they are) are captured with class=note and class=example attributes+values already, which is identical to how Bikeshed marks them up. Notes and Examples should arguably have headings in order to make it easier for screen-reader users to navigate through them. But we’ve never actually gotten a feature request for that use case so I’m not sure it’s a real problem/priority in practice for actual users. So I’m resolving this wontfix here, but if anybody following this wants to start fresh discussion on it, let’s do that over at https://github.com/whatwg/html/issues