Closed ancorgs closed 2 days ago
We have been trying to shape this new page for a couple of days now. Having other things to do in the middle, of course. Despite all the things I have said "offline", I still having doubts on how to proceed. I have slightly written the rationale at https://trello.com/c/nOUYvYIY/3873-8-first-prototype-of-the-new-ui#comment-672c738f86a51a5abbd1c842 (private link). Summarizing it a bit for a broader audience: it's so challenging to come up with a proposal that put a11y on the front mainly because of time. Somehow I feel we're in a hurry because a lot of things has changed in the backend that now needs a front-end for the users interact with.
That said, a proposal I had in mind still not convincing me, although I like it more than the @ancorgs versions above. It basically needs a lot of more tests and work to ensure it worth it in terms of a11y, reason while I fear we will go an step backward and work in the mode we were working: a11y later. I guess it is a matter of gathering more and more knowledge, working on it.
If the menu shown in the screenshots above were accessible, even the "Change device" button could be moved to the "More actions", renaming the latest to something more general.
But most probably we will go for the @ancorgs proposal for the initial version because I myself have doubts about the accessibility of the above research.
Closed in favor of #1742
Completely temporal, just in case it's useful for someone.
There must be better options than a raw ExpandableSection.