The original March 2026 article described a conversation with a team whose new landing page added steps before they could reach their work. That experience is a useful prompt for evaluation, but it does not establish how every legacy system or every user performs.
Count the work, not just the clicks
A short path can still be confusing or inaccessible. A longer path may include a necessary review, confirmation or permission check. Compare whether a person can complete the intended task accurately and recover from a mistake.
Bring representative tasks
- Find the approved procedure for a specific activity and identify its version.
- Complete an assigned training acknowledgement using the keyboard.
- Route a document to the appropriate reviewer and check who can see it.
- Correct an entry, explain the change and retrieve the resulting record.
Illustrative workflow: observe a task
Ask a first-time user and an experienced user to try the same task with representative permissions. Record completion time, unsuccessful attempts, requests for help and the point where each person hesitates. Include keyboard and assistive-technology use. Repeat after changes; do not convert one successful demonstration into a universal adoption claim.
Keep necessary controls
Remove redundant navigation where possible, while preserving checks that the process requires. A usability problem does not by itself prove that a product is unsupported, and fewer clicks do not prove compliance.
Reference and next step
W3C introduction to web accessibility ↗
Use the QMS software evaluation guide, estimate a plan or discuss your process with Qlutch.

