I’ve literally had to screenshot things so I could see them on my phone.
Please stop disabling zoom
171–180 of 309 posts
Re: Please stop disabling zoom
#172Thank you! As a visually impaired user, disabling zoom is just incredibly stupid, except for a few edge cases such as games. As per theories in this thread why this meta tag is so popular. I know a few UX designers who explicitly asked the web developers (also me) to disable zoom so that there precious design could not be broken by users. I simply refuse to do so.
Doing God's work.
Re: Please stop disabling zoom
#173Earlier quoted context omitted.
It seems to me you can build quite complex things that will be accessible by default with the web platform. IF don't fight it and if you respect semantics and progressive enhancement / beautiful degradation. You get so much by default: legible colors and font sizes, tabbed page navigation, alt texts, clickable labels, zoomable interface... When you embrace the platform and its spirit, you get accessible results quite…
I'm just trying to step back and look at things objectively. Instead of saying "arg developers are just stupid" I'm trying to analyze why these mistakes are made so frequently (even at big corporations with lots of funding). There are native UI frameworks where this is not nearly as big of an issue. Too much freedom perhaps? Should you even be able to give a div an onclick handler? What about inputs? Why do developer…
> Because core functionality is terrible and needs to be augmented with richer functionality
Well, yes, I agree with both of these points. I think I get your point in the end, and your examples are convincing.
I'd say the web platform is accessible by default but this is easy to break inadvertently and maybe not the ideal platform to build applications because despite its strong accessibility features, it's lacking for what we want to do with it today.
HTML being a format to write documents first and not applications probably does not help neither.
Re: Please stop disabling zoom
#174Earlier quoted context omitted.
For presentations, I've observed that constraints on number of slides encourage people to try to stuff a bunch of information at small font sizes on a single slide, often big blocks of text. And they are laying it out on a high dpi screen that ultimately gets scaled down when presenting (especially with screen sharing). They'll have two data points in a small font and massive amount of empty space on the slide. Very…
I went through a phase of making sales presentations aimed at C-levels at big co's and was trained to pack the information on two slides into one slide and then consolidate two of those slides into one slide... And do it all without big blocks of texts or small fonts but rather well-planned complex diagrams that would draw people in and provide a great foil for spoken explanation, answering questions, etc. In the han…
If you want to understand without attending a presentation then what you want is a paper, or book. Those are very different formats.
Re: Please stop disabling zoom
#175It’s not just accessibility. I’ve last track of the number of times I’ve seen a mobile website with a table that extends past the right side of the viewport and zoom disabled. You can’t scroll, and you can’t zoom, so you can’t read the table.
Unfortunately people see accessibility as a burden that a small minority puts on the rest of us, but really it is something that benefits everyone. For instance, normally sighted people or even people with "normal" nearsightedness, farsightedness, or presbyopia benefit from adequate contrast. Text "size" is another thing because people should be able to control it, particularly given the wide range of different devic…
Re: Please stop disabling zoom
#176Earlier quoted context omitted.
A simple rule: Minimum font size >= Age of oldest attendee
What about giving websites and web apps the ability to detect the font size preference of the user to automatically adjust the font size? Just like native apps do...?
Re: Please stop disabling zoom
#177I disable it because there are bugs on mobile browsers where inputs can automatically hijack zoom and the default behavior really messes up the workflow. But yea you have to reimplement or replace it with a flow for your use case.
Re: Please stop disabling zoom
#178It’s not just accessibility. I’ve last track of the number of times I’ve seen a mobile website with a table that extends past the right side of the viewport and zoom disabled. You can’t scroll, and you can’t zoom, so you can’t read the table.
Maybe this is a good place to ask since there's a lot of web devs here: What is SO effing hard about drawing within the screen on web?! I can't tell you the number of times I've seen this issue. Just the other day I saw reddit's sign up form is totally broken on iOS, you have to swap between landscape/portrait multiple times and hope whatever garbage layout engine it uses redraws the button inside the screen.
But, as you've noticed, with more complex UI (especially modals and toolbars fixed to the screen) it becomes more important that things are built to fit horizontally and vertically. It's not necessarily hard but it does take more thought to work out how things will shrink, grow, scroll, etc.
Re: Please stop disabling zoom
#179Earlier quoted context omitted.
For presentations, I've observed that constraints on number of slides encourage people to try to stuff a bunch of information at small font sizes on a single slide, often big blocks of text. And they are laying it out on a high dpi screen that ultimately gets scaled down when presenting (especially with screen sharing). They'll have two data points in a small font and massive amount of empty space on the slide. Very…
I went through a phase of making sales presentations aimed at C-levels at big co's and was trained to pack the information on two slides into one slide and then consolidate two of those slides into one slide... And do it all without big blocks of texts or small fonts but rather well-planned complex diagrams that would draw people in and provide a great foil for spoken explanation, answering questions, etc. In the han…
Manager wanted to add a ton of content that they felt would be helpful. I said sure, and added it to an appendix with arrows, callouts, additional definitions, etc.
I then presented it to the CxO group -- we only discussed that first slide. I emailed the deck, and got comments back saying that the appendix was confusing but they loved how simple and clear the single non-appendix slide was.
I've always tried to follow the 4x4 rule: no more than 4 lines, and no more than 4 words per line. I've found icons and occasionally diagrams can be helpful in explaining more abstract concepts. Also, slide notes are used liberally.
One place I worked was veeery similar to what you describe here. PPT was considered docs of record since no one wanted to make formal memos and have those enter the control system. My approach had friction, since I would be extremely concise and direct people to the slide notes if they had questions. In this org, people were notorious for lifting slides from others decks for their own presentations (hence I would distribute as PDF to discourage this) since people would not field questions those slides might raise.