Replies: 2 comments 1 reply
-
ah yes We want our UIs to evolve - but change is disruptive (even debilitating) for elders. But we can't still be supporting the interface for DOS Windows 3.2 XP etc. and delaying the day when they have to deal with a changed UI only makes it more likely that the UI change to that version will be even more drastic. Do you have a suggested solution to it? The only one i know of is the Info-Bot/IUIG approach |
Beta Was this translation helpful? Give feedback.
-
This is a great point. Making ever-changing technology predictable isn't always clear-cut, and this is where user research becomes essential to reducing cognitive burden. This aligns with WCAG 3.0's shift towards measurable outcomes and the real-world user experience. Perhaps the guidance could focus on tracking metrics like:
These feedback loops should be standard practice. They provide the objective perspectives needed to identify major roadblocks that internal teams, with their inherent biases, will inevitably miss. While this research is ideally integrated into the design phase, establishing a feedback loop at any stage would be a crucial step forward. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I think in real-world use, UI updates can also pose significant challenges for users, especially those with disabilities or older adults. Changes in the interface cause confusion and increase the cognitive burden, making it harder for users to navigate and interact with services. I suggest that guidelines also address the frequency and manner of UI updates. Even when updates are necessary, they should be designed to remain predictable and familiar so that users can anticipate changes and adapt without undue difficulty.
I know it is somewhat different from the existing guidelines, but I believe that many considerations are also needed from the perspective of maintenance.
Beta Was this translation helpful? Give feedback.
All reactions