Inconsistency
Priority: 3
Introduction
An important inclusive design principle, is “Be consistent”. Interfaces that fail to do so present unnecessary burdens of comprehension to users — especially those who consume HTML semantics, such as screen reader users. In particular, inconsistent navigation schema and page structure can make the user feel disoriented and unsure.
It is appreciated that a consistent experience can be difficult to achieve when managing three separate projects, built on separate technologies, and it is noted that a design system is currently being developed to help diminish the issue.
WCAG criteria
- 3.2.3 Consistent Navigation (level AA)
- 3.2.4 Consistent Identification (level AA)
Scope of the issue
Navigation
The main navigation differs across the three properties. The Marketing site offers a number of options (pictured), the Join site excludes navigation altogether, and the Account dashboard (also pictured) offers just three navigation options: “Community”, “Help”, and “Sign out”.
Note that, while these sites are built and managed separately, users do not necessarily access them separately or consider them autonomous. The severity of this issue of consistency depends on user journeys and behavior.
In general, every landmark region except the <main>
(or role="main"
) region is expected to have consistent content between pages. The <main>
region defines the unique content of the page.
Forms
There is a lot of inconsistency between the sites regarding the way form elements, labels, and errors are marked up and presented visually.
Fixing the issue
Navigation
It is recommended that the same (complete) Marketing site navigation is used for each of the three sites, with the exception that “Sign out” is not pertinent except to logged in users of the Account dashboard. The visual design (colors, layout, and font size) should also be consistent.
Forms
See Missing and placeholder labels and Form errors for recommendations on form design and error reporting. Use the same behavior and visual design for labels, placeholders, individual error messages, and generic error notification live regions.