20648 2013-01-11 16:25:38 +0000 It is not always appropriate to place a heading in a NAV. However, if we leave it out most screenreaders will announe something like "Unnamed navigation". One solution is to put in a heading, but hide [...] 2013-04-12 23:16:38 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#headings-and-sections P3 normal Unsorted 1 contributor ian ian mike contributor oldest_to_newest 81247 0 contributor 2013-01-11 16:25:38 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/sections.html Multipage: http://www.whatwg.org/C#headings-and-sections Complete: http://www.whatwg.org/c#headings-and-sections Comment: It is not always appropriate to place a heading in a NAV. However, if we leave it out most screenreaders will announe something like "Unnamed navigation". One solution is to put in a heading, but hide it with css, which is not very elegant (you cannot do this with display: none since that would hide it from screenreaders again). SO would it be an option to have the outliner refer to the title attribute when there is no heading? Posted from: 88.244.26.47 User agent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.52 Safari/537.17 84100 1 ian 2013-03-07 23:31:18 +0000 Why would screenreaders announce "unnamed navigation"? That's silly. They should just say nothing, or maybe say "Navigation" or some such. "Unnamed" is just bad UI. I recommend filing bugs against the screen readers that do this.