 |
|
|
|
But better text can be shown : load/save : content ? From ? |
 |
Your link refers to a custom solution implementing G1 technique I would say can be sufficient for passing the requirement 2.4.1. The only "extensible" menu is the "question list" / "page list" menu. Other menus can also be deactivated. Thank you for caring. |
|
|
Oh you're right : no menu, no shirtcut link ;) I'm unsure on the good landmark : we need it too. But sometime : no footer |
|
|
About https://www.w3.org/WAI/WCAG22/Techniques/general/G124.html We really have a main content. You mean someting like adding a link at top to each question ? |
|
|
Screen readers reads from top of page to end of page. Usually pages have: main content, header, navigation menu, sidebar, footer. In this situation, technique G124 is useful to go straight to content, avoiding boring lists. In a "pages of questions" situation, but in general, the obstacle between top of page (<body>) and the main content (<h1>) is the header content, and header navigation menu. So that make me think G124 is useful to bring impaired user to each parts of page (header, main, footer). But G1 is also ok to skip the boring navigation menu and go straight to main content. I guess G1 is sufficient implementation for Vanilla simple theme. (don't know for fruity theme, didn't tested). LS Administrators are able to write custom child themes based on core Vanilla, so I guess is a good choice to preset the theme for passing 2.4.1 requirement also in complex situation with footer or sidebars. Must be said I guess the better choice for themers is to have a G124 ready made solution. For example:
|
|
|
Skip to question + Skip to navigation can be interesting. |
- Anonymous
