-
Accordions create extra work
Accordions can either hide information that needs to be split over pages for easier reading, or unnecessarily hide key information that can be written concisely.
-
Do not forget unique text for repeated actions such as ‘Change’
Patterns that use link titles with the same name need extra attention to make sure they are still unique for screen readers.
-
Avoid tabs for complex content
The primary use case for tabs is when one set of information is far more important than others and does not need to be compared.
-
Do not use a question as a heading unless a user can answer it on the page
If you put a question in a form page, it needs to have a way for a user to answer it.
-
Make sure that answers are connected to a question
Input fields separated too far from the initial question cause barriers for users who struggled to remember the question.
-
Do not split up expected form groupings
Some groupings like username and password are so commonly expected that both people and browsers can struggle if they are changed.