Accessibility, Inclusiveness, and WCAG
Accessibility affects all users, not just those with stereotypical disabilities. The extra work that may be required to ensure good accessibility in DNB applications and services will be worth it.
Remember - test for accessibility early in the design process.
WCAG (Web Content and Accessibility Guide)
The four main tenets of the WCAG 2.1 are:
Perceivable content must be readable.
Make sure there is enough contrast between background and text colors.
Larger text is generally more readable. Make sure text can easily be resized.
Images should have alt text.
For video, provide transcripts and captions for visual-heavy videos.
Do's / Don'ts
Don't use font sizes below 14px (0.875 em).
Avoid fixed pixel sizes - use relative sizing.
Never put the important text as part of an image.
All users should be able to get to all the pages and forms.
Users should be able to interact with what they need to:
- all other navigating and information retrieval
Keyboard navigation covers many use cases and contexts. Users who cannot see the position of the cursor on the screen, or who do not possess fine motor skills in their hands, often rely on the keyboard.
Keyboard shortcuts can increase task efficiency.
See 'Focus management' below for more on this topic.
Forms, navigation, and other essential components and actions should work on older browsers and devices. Styling comes second to content and accessibility.
The contents' intended meaning is easily understandable.
Use simple, honest, direct language.
This especially applies to the use of icons and symbols. What may be obvious to a designer or a user in one culture may not be so to another.
Back up icons and symbols with clear labels, captions, or subtitles.
Make content accessible from a wide variety of devices.
Semantic markup makes robust content that's accessible. Pay attention to the following:
- Semantic HTML tags
- Proper use of aria tags
- Logically ordering DOM elements
- Server-side rendering to ensure it's delivered properly
Responsive Design ensures that content can be viewed on a wide spectrum of display sizes. Responsive components and layout design should be planned from the beginning and not applied as an afterthought. Build prototypes early in code or design and begin testing their breakpoints sooner rather than later.
Where should the focus start on the first page init?
If there is a Skip-Link then this should focus first since the point of having it is to avoid having to go through blocks of material that are repeated on multiple pages. The order in which tabbed focus occurs is up to the UX designer if the Skip-Link link is bypassed. For example: Tab 1: Skip-Link Enter: Focus is applied to the main content
There are no fixed rules for the order of what becomes focusable after the Skip-Link link. It can be based on context for example:
If on index
- Tab 1: Skip-Link
- Tab 2: First link in the main menu or main menu button or search field
If not on index
- Tab 1: Skip-Link
- Tab 2: Logo with link to the homepage
- Tab 3: First link in the main menu or main menu button or search field
Or, it can be based on user needs. For example, it may be more beneficial for a search field to be in focus rather than the main menu.
Is a Skip Link required?
Again, this is dependent on both content, context, and user needs which ultimately affect the user experience. If there are blocks of repeating content on multiple pages then it may improve user experience to add a Skip-Link. It is not a requirement to have a Skip-Link but an asset.
Accessibility checklist for designers
Check out the Accessibility checklist for designers for the most important features in accessibility.