[uxcolumbo]

Exactly.

It's unfortunate that accessibility is usually treated as an add-on in a lot of 'UX' project. Focus is heavily on visual design.

Accessibility needs to be considered from the start when designing new apps.

Making things accessible means making it easier for all users.

Which apps / sites have you stopped using because of poor UX choices.

And what are those things that made you stop using those sites?

[JohnFen]

> Which apps have you stopped using because the UX choices.

The biggest example for me is Firefox. FF's UX has always been horrible, but until the revamp, it was always possible to configure it to be OK without a great deal of effort. After the revamp, the UX is still horrible (although in different ways), but the ability to configure the bad parts away has been seriously reduced.

> And what are those things that made you stop using those sites?

Overreliance on Javascript, hidden functionality, and (related) the lack of discoverability top my list of peeves. Also, with websites, being too aggressive with enforcing a particular layout, color scheme, fonts, etc.

[ris58h]

> FF's UX has always been horrible

I've used it for years. It can browse sites, manage tabs and so on. Even synchronization between devices works fine. There are some issues but I wouldn't call it horrible. Could you elaborate more?

[kaba0]

> After the revamp, the UX is still horrible (although in different ways), but the ability to configure the bad parts away has been seriously reduced.

It has become HTML-rendered, if anything, shouldn’t it be more configurable?

[JohnFen]

It depends on how you mean. If you're a web dev, and/or willing to mess with CSS, then perhaps it's more configurable? But there is significant friction in doing so, even if you do know how to work at that level. In terms of what normal users can realistically do, the browser is much less configurable.

Also, that pretty much only affects the look, it doesn't affect how the browser behaves.