- From: Léonie Watson <lwatson@paciellogroup.com>
- Date: Tue, 1 Dec 2015 08:42:40 -0000
- To: "'Cynthia Shelly'" <cyns@microsoft.com>, <info@3zero.co.uk>, <public-html@w3.org>
> From: Cynthia Shelly [mailto:cyns@microsoft.com] > Sent: 30 November 2015 18:08 "> So, then why have it at all? Shouldn't be expose the role when it exists?" Good question. I think (as a screen reader user) it is useful to be able to identify the header (and footer) for the page. Together with elements like main, nav and aside, they help create a simple map of the page that was previously unavailable before ARIA/HTML5. Identifying the header or footer for sectioning content seems less useful to me. As discrete chunks of content, the header or footer of sectioning content is often not as semantically important as their page counterparts, and exposing them would rapidly increase the verbosity of the content. I think this would also reduce the efficacy of the mapping mentioned above, because the available information would be too granular to be really usable. That said, I expect these elements are useful outside of this context. Having an element as a styling hook instead of class names is often preferable; in digital publishing eBook applications may derive additional use from them; search engines may also obtain data using them perhaps. Léonie. -- Senior accessibility engineer @LeonieWatson @PacielloGroup
Received on Tuesday, 1 December 2015 08:43:04 UTC