101–110 of 944 posts
Earlier quoted context omitted.
I find it ironic that in order for your comment to be accessible the reader must lookup “a11y” to find that it means “accessibility”.
First time hearing the term a11y for me too. I hope to never come across it again.
You know what's an accessibility problem for a lot of people over 40? White text on a dark background. I don't think I'll ever get tired of hearing people advocate for making web pages readable for people my age. Yeah, opening up the inspector and updating the author's CSS made it readable for me, but made the shell script unreadable.
For me, the solution to this is:
https://addons.mozilla.org/en-US/firefox/addon/font-contrast...
Forces the text to black at least. Pretty reliable. Sometimes needs overrides which are easy to do.
Large, visible, and provides room for metadata like selected lines, errors, etc. I want them practically everywhere, even when they don't seem to make sense - widescreen monitors mean there's more than enough wasted horizonal space, it wasn't doing anything useful anyway.
Earlier quoted context omitted.
A gesture is an action . It's good, and it works as intended. A scrollbar is (also) an indication , glanceable, not requiring any action. If someone among your friends and family has an iOS device, remember how many times you had to show them that certain screens can be scrolled down? Oh, not just down, but also to the right? There used to be a few perfectly aligned views that had no indication whatsoever that there'…
I know what a gesture is. > If someone among your friends and family has an iOS device, remember how many times you had to show them that certain screens can be scrolled down? I don't know, zero? Maybe let's say once to be charitable. This is not a real problem faced by most people. IMO, this is just people being used to doing it another way.
In my perfect world, the scroll bar would appear if you hover in the right spot for long enough. And if you drag it and release, it would stick around until 1.) you move the cursor >0 pixels and 2.) a reasonable timeout passes, or it's obvious you've moving your cursor away from the scroll bar.
I'll note that Slack's desktop app _just works_ the way I wish scroll bars would work (it just appears and stays if your cursor is in the content area), though I think it's because they implement them manually.
Once again I have to give firefox credit for giving users the tools in about:config to disable this. It's cute fluff at best and annoying/abusive at worst. The browser's UI should more or less be fully off the table when it comes to what a website can change, and that includes scrollbars.
Earlier quoted context omitted.
I find it ironic that in order for your comment to be accessible the reader must lookup “a11y” to find that it means “accessibility”.
duuuuuude for real a11y? what kind of weird lingo flex is that?
edit: I will say this is a bad example because looking it up there is 40+ words that fit this description so maybe I am biased by experience. i18n works better but I think my point is no longer correct.
Earlier quoted context omitted.
> so fuck me, I guess Obviously not, but you also shouldn't expect the whole world to be designed around your needs. If you have difficulty using the expected input method, you should use alternatives with the same functionality, not expect others to redesign their apps in your preferred way.
That's the wrong mentality tbh Design for the best accessibility first and foremost, then try and make things look "prettier". Disabilities can affect anyone at any time and shouldn't be an afterthought.
Most of the terrible designs and accessibility problems stem from software going out its way to write custom controls or force controls to look and behave in a non-default way. It's not an afterthought--people are deliberately adding code to make their software worse.