(In reply to Alessandro Castellani (:aleca) from comment #21) > I like your proposed ordering FTR, I just proposed to keep the current default order (before this bug), because it looks carefully designed to be maximally intuitive and efficient. > My proposal was to optimize the row for screen readers and visually impaired users. [snip] > I think this is a unique scenario we should optimize for them, since any other user can update the order as they want. I have serious doubts on that approach, which (with all respect) seems upside-down: I think we must fix accessibility problems by making things accessible, not by rearranging everyone's UI to favor screenreaders and the small group of their users, and then expect the majority of regular users to customize their UI for a useful UX.
Bug 1612055 Comment 27 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Alessandro Castellani (:aleca) from comment #21) > I like your proposed ordering FTR, I just proposed to keep the current default order (before this bug occured), because it looks carefully designed to be maximally intuitive and efficient. > My proposal was to optimize the row for screen readers and visually impaired users. [snip] > I think this is a unique scenario we should optimize for them, since any other user can update the order as they want. I have serious doubts on that approach, which (with all respect) seems upside-down: I think we must fix accessibility problems by making things accessible, not by rearranging everyone's UI to favor screenreaders and the small group of their users, and then expect the majority of regular users to customize their UI for a useful UX.