-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve page structure #4232
Comments
from #4194
|
Regions - there is some use of regions, but needs tidying upPages should be divided into regions whose purpose is clearly identified by use of an Aria landmark, e.g. navigation, ARIA11 Technique. Other regions can be identified via aria-lablelledby, ARIA13 Technique.
Banner has been defined for OLH and Clean. All three themes seem to have navigation defined. But other regions, most importantly 'main' cannot be found within the code. Some use of ARIA labelledby but not for regions. |
grouping roles to identify related form controls
|
Aim
The have well structured pages
Background
The structure of the pages are not consistent, most of this is about heading levels not being consistent, but regions and landmarks should also be reviewed.
Pages are formed from multiple templates being slotted together, so I propose the parent template pass the heading level to the child so that the heading structure will always be known at the parent level, rather than hard coded into any child templates.
This needs to be done across all themes.
Refer to #4194 for examples of page structure issues.
Consider:
WCAG 1.3.1 - Info and Relationships
Techniques to meet 1.3.1
WCAG 2.4.6 - Headings and Labels
Technique G130 - Providing Descriptive Headings
The text was updated successfully, but these errors were encountered: