All content on the page/screen must be readable and understandable to users.
Readable
Present language selection upfront (A) (AA)
3.1.1 Language of Page 3.1.2 Language of Parts
If content of your product has option to support multiple languages, then make sure language selection is presented upfront, before user can continue interacting with the product.
Simplify content (AAA)
Use simple sentences and communicate in a conversational tone, friendly and polite. Don't confuse users with too much information and complicated words or descriptions. By using simple sentence formulation content is understood faster and more easily.
Predictable
Don't change context without user confirmation (A)
Context of the page/screen shouldn't be changed without user confirming it in some way. Before any change happens, there needs to be a clear question and an option user can choose from. If there is not a question in ask, then user needs to have a clear confirmation action, before any context changes.
Make navigation predictable and consistent (AA)
Ensure consistent navigation across all pages by placing menus, buttons, and repeated elements in the same order. This predictability is crucial for users, especially those with disabilities, who rely on spatial memory and visual cues to navigate. Avoid changing the layout or order of these elements unless the user initiates it. For example, keep "skip navigation" links or search bars in the same spot on every page to help users quickly find and use them. Consistency improves accessibility and overall user experience.
Stay consistent for improved accessibility (AA)
3.2.4. Consistent Identification
Start by creating a style guide with standardized labels and text alternatives for similar functions. Use clear, uniform language, such as "Download [Document Title]" for document icons. Regularly review your design elements to ensure consistency and conduct user testing with assistive technologies to catch any discrepancies. By maintaining a predictable experience, you'll improve accessibility and usability for all users, especially those relying on screen readers.
Keep help options consistent across your design (A)
Ensure that help options such as contact links, chatbots, or support pages are consistently positioned in your design. While not every page needs to have a help option, those that do must maintain a consistent order and location. For instance, a "Contact Us" link could always be placed in the footer, a help button in the main navigation, or you can have a sticky chatbot positioned in the lower right corner on all relevant pages.
Input assistance
Clearly identify errors (A) (AA)
3.3.1 Error Identification 3.3.3 Error Suggestion
Clearly indicate where and what type of error took place. Focus the element in question, provide an error text next to it and describe what the issue is.
Provide labels and cues to avoid mistakes (A)
Avoid user mistakes by adding simple instructions or cues so users understand what is asked of them. Also, don't avoid using labels, as they help users to clearly understand which form are they filling out.
Enable review and confirmation to prevent mistakes (AA)
When designing interfaces that involve the input of legal or financial information, it's crucial to implement measures that help prevent errors. Ensure that users are provided with clear instructions and validation messages throughout the data entry process. Offer confirmation dialogues before finalizing transactions to allow users to review their information.
Avoid redundant entries in multi-step processes (A)
When designing multi-step processes, avoid asking users to re-enter the same information within the same task or session. Instead, auto-fill information or provide options like checkboxes and drop-downs to reuse previously entered data. This reduces cognitive load and prevents users from making mistakes.
Provide accessible authentication options (AA)
5.3 Biometrics 3.3.8 Accessible Authentication (Minimum) (AA)
For authentication always provide alternative identification methods, both biometric (like fingerprints, face-ID etc) and non-biometric, to ensure accessibility for all users, especially those with disabilities. Be mindful that authentication should not require cognitive function tests, like recalling passwords, unless you offer alternatives. Consider integrating support for password managers and enabling copy-and-paste options to help reduce the cognitive load.