Re: Alternative for the widget access in a dashboard

Also from me: no offense intended - maybe it sounded harsh but I’m no native speaker and try to keep things as short as possible.

Everything else private and in German.

😉

--
Mit freundlichen Grüßen

Marc Haunschild
https://Accessibility.Consulting


Am 21.07.2021 um 07:54 schrieb Batusic, Mario <mario.batusic@fabasoft.com>:


Hello Marc,

Thanks for the answer. And no offense.

Ciao     Mario

Von: Marc Haunschild <haunschild@mhis.onmicrosoft.de>
Gesendet: Dienstag, 20. Juli 2021 16:12
An: Batusic, Mario <mario.batusic@fabasoft.com>
Cc: WAI IG <w3c-wai-ig@w3.org>
Betreff: Re: Alternative for the widget access in a dashboard

Hi Mario,

I was completely serious, when I said that the described behavior is not violating any success criterion.

And I also said, that you might end up with problems for people with disabilities, if you make many questionable decisions.

I made not a single conclusion. I just pointed out, that it looks like it was not designed with accessibility in mind. I’m happy to be wrong!

BTW: the issues I’ve been mentioning about poor contrast and bypassing blocks of course is not a problem for Screenreader users. You have way more possibilities to bypass blocks, than the rest of us (moving to main content, using headings to navigate to, skipping lists and so on…).

But again: I’m happy if you say that the app was designed with accessibility in mind.

I will check it - we are using it ourselves and I have to make an audit soon.

--
Mit freundlichen Grüßen

Marc Haunschild
https://Accessibility.Consulting



Am 20.07.2021 um 13:39 schrieb Batusic, Mario <mario.batusic@fabasoft.com<mailto:mario.batusic@fabasoft.com>>:

Hi Marc,

@all:  I appologize for putting graphics in my mail. I am myself blind and don’t like this kid of actions. But at the time I have not yet a test system open for external users to offer the real Web situation.

@Marc:  Thanks for answering the questions that I didn’t pose. 😊 Please make no conclusions about Accessibility of a system only having seen a screenshot. Fabasoft Cloud is highly accessible. I work with it with ease daily.

But please, maybe somebody else gives me a serious answer.

Mario

Von: Marc Haunschild <haunschild@mhis.onmicrosoft.de<mailto:haunschild@mhis.onmicrosoft.de>>
Gesendet: Dienstag, 20. Juli 2021 10:34
An: Batusic, Mario <mario.batusic@fabasoft.com<mailto:mario.batusic@fabasoft.com>>
Cc: WAI IG <w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>>
Betreff: Re: Alternative for the widget access in a dashboard

Hi Mario,

It’s bad UX to make SR users click twice. You know it, that's because you're asking. ;-)

Why not think about making it good? - If you make many decisions like this you might end up wit a product that is passing each SC but still is not usable for many people.

If everything else is perfect, then ok, but I don’t think the table in the second screenshot is accessible.

Also I see at least four navigations on the second pic - have you thought of how to bypass them?

Actually that piece of software does not look like it was designed with accessibility in mind...

Besides there are very competent people on this list that cannot see your images. So maybe you won’t get some of the best answers because you have published non text content without text alternative right here.

Have a nice day,

Marc


Am 20.07.2021 um 09:10 schrieb Batusic, Mario <mario.batusic@fabasoft.com<mailto:mario.batusic@fabasoft.com>>:

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