Change Details

With new DOM structure enabled in {T261802} and with feedback provided by AFB {T263834} it's time to revisit heading order. Citing from AFB's report: > New DOM structure: > https://en.wikipedia.org/w/index.php?useskinversion=2 > > - The new DOM structure for the main page has a strange heading layout which may confuse a screen reader user. > -- Page starts with level 3 heading which contains a search field. followed by level 2 heading with the 'Navigation Menu' and then the 'main landmark From today's featured article' as a level 2 heading. AFB's suggestions: > 1. The Search field doesn't have to be wrapped within heading because the screen reader user can easily get to it using the landmark keyboard shortcut by pressing letter 'd' on the keyboard. > 2. Similarly, the items within the 'Navigation menu' heading are also part of the landmark region which can easily be navigated by screen reader user. > 3. Either bring the 'Navigation menu' heading further down in the page after the level 1 heading or remove the level 2 heading 'Navigation menu' completely and leave the 'Namespaces and Views' navigation landmark region items at the top without the heading.

With new DOM structure enabled in {T261802} and with feedback provided by AFB {T263834} it's time to revisit heading order. Citing from AFB's report: > New DOM structure: > https://en.wikipedia.org/w/index.php?useskinversion=2 > > - The new DOM structure for the main page has a strange heading layout which may confuse a screen reader user. > -- Page starts with level 3 heading which contains a search field. followed by level 2 heading with the 'Navigation Menu' and then the 'main landmark From today's featured article' as a level 2 heading. AFB's suggestions: > 1. The Search field doesn't have to be wrapped within heading because the screen reader user can easily get to it using the landmark keyboard shortcut by pressing letter 'd' on the keyboard. > 2. Similarly, the items within the 'Navigation menu' heading are also part of the landmark region which can easily be navigated by screen reader user. > 3. Either bring the 'Navigation menu' heading further down in the page after the level 1 heading or remove the level 2 heading 'Navigation menu' completely and leave the 'Namespaces and Views' navigation landmark region items at the top without the heading. Further explanation of [[ https://webaim.org/techniques/semanticstructure/#headings | why semantic heading structure is important to screenreaders ]].

With new DOM structure enabled in {T261802} and with feedback provided by AFB {T263834} it's time to revisit heading order. Citing from AFB's report: > New DOM structure: > https://en.wikipedia.org/w/index.php?useskinversion=2 > > - The new DOM structure for the main page has a strange heading layout which may confuse a screen reader user. > -- Page starts with level 3 heading which contains a search field. followed by level 2 heading with the 'Navigation Menu' and then the 'main landmark From today's featured article' as a level 2 heading. AFB's suggestions: > 1. The Search field doesn't have to be wrapped within heading because the screen reader user can easily get to it using the landmark keyboard shortcut by pressing letter 'd' on the keyboard. > 2. Similarly, the items within the 'Navigation menu' heading are also part of the landmark region which can easily be navigated by screen reader user. > 3. Either bring the 'Navigation menu' heading further down in the page after the level 1 heading or remove the level 2 heading 'Navigation menu' completely and leave the 'Namespaces and Views' navigation landmark region items at the top without the heading. Further explanation of [[ https://webaim.org/techniques/semanticstructure/#headings | why semantic heading structure is important to screenreaders ]].