Re: Alternative for the widget access in a dashboard

Hello Mario,

Screenshot images can tell only part of the story. It’s hard to draw conclusions about accessibility or user experience just by looking at the screenshots. How are these elements are marked up?

It’s not entirely clear to me why certain content or elements are hidden or restricted for some users, or might require additional clicks or keyboard actions to gain access. What sort of reasoning was used to drive these design decisions?

Also, I don’t quite understand what you mean by "A keyboard User has no access to the content of each widget”, unless you only mean initially.

Peter
On Jul 20, 2021, 2:15 AM -0500, Batusic, Mario <mario.batusic@fabasoft.com>, wrote:
Hello dear experts,
In our Fabasoft Cloud Web-Apps we try to reduce navigation efforts for keyboard users in the app dashboards. In the window area of a dashboard we implement currently an ARIA listbox with widget headings as options.
<image001.png>
A keyboard User has no access to the content of each widget. He/she can only navigate with arrow keys to each widget header and open it with enter key. The content on the top level are only restricted lists. After opening a widget the user gets full functional access to the complete list.
<image002.png>
Is this an allowed partial alternative? There are no unavailable functionalities for a keyboard user. The only difference to the possibilities of a mouse user is a keypress more (enter). A mouse user has also to open the widget if the list has more than 6 entries.

Thanks in advance.

Ciao     Mario