Re: [xwiki-devs] Are we really sure we want 2 H1 for page rendering?

any decision we make, we need to make sure that beside WCAG, the headers are also displayed visually corect by the {toc} macro and that they are semantically correct. If we are looking at Main - visually we have a separation between the content and the panels. Within the content - since we have the big title "Welcome to your wiki" - it would look normal that "Spaces", "Recent Changes" to be H2. This is done now visually through CSS, but for audio readers they are all H1. So no hierarchy is showed in audio mode. If we are going to change the "Spaces" in H2, we need to modify the {{ toc }} macro to include the page title, otherwise it's gonna start with a simple bullet. Regarding an algorithm to transform all H1 within the content in H2 - I disagree. The user may need to add a H1 to the page. It's his decision if we doesn't care about WCAG. Another thing is that the Main actually includes "Spaces", "Recent Changes", "Tags" - and they are original H1, being separated pages. On Thu, Nov 12, 2009 at 10:50, Vincent Massol <vincent(a)massol.net> wrote: