Earlier quoted context omitted.
duuuuuude for real a11y? what kind of weird lingo flex is that?
It's a longstanding abbreviation for "accessibility", along the same lines of i18n being an abbreviation for internationalisation. There's the first letter, and the last letter, and between them a count of the number of letters elidded.
Scrollbars are becoming a problem
621–630 of 944 posts
Re: Scrollbars are becoming a problem
#622Earlier quoted context omitted.
Windows 2000 was the last truly great Windows for me. It was the last Windows version that had a working "Find in File Contents" feature without having to install grepwin.
I won't argue against Windows 2000's usability. But I will say that to me, as someone who first started using computers in the XP era, any Windows earlier than Windows 7 looks so god damn ugly to me, and Windows 2000 even more so than XP. Interestingly though, I don't have the same impression when looking at the old Apple OSes. To me, Mac OS 9 looks old, but not ugly.
For me, I grew up on Amiga Workbench 2.0 and MS-DOS, so Windows NT/2000 felt like a good evolution from it's User Interface. Very functional, for sure.
100% agree on Classic MacOS. As outdated as the tech was, it was beautiful because it was elegant without being distracting.
Re: Scrollbars are becoming a problem
#623Re: Scrollbars are becoming a problem
#624Re: Scrollbars are becoming a problem
#625I agree the scrollbar is dying and becoming unusable. A scroll bar needs to be: - Wide, clearly visible and easy to hit. - Proportional sized, indicating how much of the document is currently in view. - Movable parts should have features indicating friction, as opposed to slippy-ness. - With arrow buttons, placed together instead of at opposing ends. - It should change colors to indicate hover and mouse press. Of the…
All of this, with the addition that you should have the option of panning in both dimensions from a single toolbar widget if the document supports it. I've seen that implemented but never with the arrow buttons together rather than at opposite ends. > - Wide, clearly visible and easy to hit. Way back in the day, there used to be a field of study called Human Computer Interaction, where people would learn about things…
Which, despite the name, is not a law and should not be called such. I've had so many people claim that I'm wrong for disliking the global menu in MacOS because "Fitt's Law" says it's better. And yet, it's still less usable for me despite the claim that this "law" makes or what Apple's defenders say.
If people's subjective preference can be contrary to what Fitt observed, then it's not a law. A law is something that is true for everyone, it is not a matter of opinion. I have no doubt that this is a useful maxim, but it's not a law and I really wish it wasn't named so poorly.
Re: Scrollbars are becoming a problem
#626Glancing to the side and seeing both how much scrolling there is (by the size of the scrollbar grab target[1]) and how much space I have to go (by the position of the scrollbar grab target is something I use all the freaking time.
1: This is a relatively modern feature. The first decade or so of me using scrollbars they were a fixed size)
Re: Scrollbars are becoming a problem
#627Earlier quoted context omitted.
All of azure’s a web UI is a disaster. Breadcrumbs that aren’t really breadcrumbs. “X” that sometimes means back and sometimes means several steps back. … and the browser back button sometimes does what you expect, and sometimes not. “X” stacked directly under one of the aforementioned “X”s, which means close, but the other “X” is back, all on a flat ui with the same background and no border. And yeah, the log analyt…
I still prefer it over AWS, which has separate portals for each product in each region. All of which show random internal identifiers instead of human-readable text. None of which support a folder structure, a technology invented before the advent of computers.
Re: Scrollbars are becoming a problem
#628Looking from web browser perspective, scrollbar should be part of browser UI ("chrome" if you will), but not webpage. Sure, some designers love that they can customize colors of scrollbar and change its width, but it's a huge accessibility problem, even for people without disabilities. And when clicking on scrollbar counts as interaction with website and starts autoplaying video somewhere in the background, you know…
The other half of the issue is that native scrollbars, especially on Windows, are a huge eyesore in those scenarios because they disrupt the layout or conflict heavily with the app or site's branding in some way. Take any eyesore in real life and it produces the same psychological effect — scrollbars too often feel like they don't belong.
Of course, many here (and myself) would argue that usability is far more important than branding.
I think a happy medium would be to enforce a certain size and stay with fundamental usability principles, while allowing customization of colors / arrow images at most, probably.
A good, usability-focused designer alongside their engineers would keep these things in mind, ideally, but alas — a great many experiences are driven by amateur-level professionals who are still learning about these blind spots, and favor aesthetics over functionality.
Re: Scrollbars are becoming a problem
#629Only 50? I can finally have something useful to fill that massive blank space between my content and the edge of the page.
Re: Scrollbars are becoming a problem
#630Earlier quoted context omitted.
It seems like most people who scroll use touch, wheel, or other non-scroll-bar interfaces, and the scroll bars are just a visual indicator of document size and position while navigating it. I know I do— and have for 20 years unless I was using a shitty laptop without a scrolling input method. Maybe unless I'm scrolling through literally millions of lines of text, which is infrequent enough that I'd prefer to have the…
> Phone and tablet usage has outpaced regular computer usage for quite some time, and that informs users interaction style. "Informs"?!? Deforms! WTF does phone usage have to do with sabotaging the UI on a computer???