The trend to use LARGE BIG SCREAMING FONTS
-
I've been noticing more and more that websites are setting their font size to something a blind man could read. Particularly sites with API documentation, but not exclusively. I find myself setting the zoom factor in Chrome to 75% or even less, simply so these pages don't SCREAM at me, like that.
Latest Articles:
Client-Side TypeScript without ASP.NET, Angular, etc.Because actual responsive designs are hard. Much easier to just design for a small phone, and apply a fixed scaling factor on anything larger. :rolleyes:
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
-
I've been noticing more and more that websites are setting their font size to something a blind man could read. Particularly sites with API documentation, but not exclusively. I find myself setting the zoom factor in Chrome to 75% or even less, simply so these pages don't SCREAM at me, like that.
Latest Articles:
Client-Side TypeScript without ASP.NET, Angular, etc. -
Marc Clifton wrote:
I've been noticing more and more that websites are setting their font size to something a blind man could read.
Without providing alt-text's for them images, causing blind man not to be able to place an order.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
https://www.cnbc.com/2019/10/07/dominos-supreme-court.html "
Quote:
The case was originally brought by a blind man named Guillermo Robles, who sued the pizza chain after he was unable to order food on Domino’s website and mobile app despite using screen-reading software.
" So I'm wondering why he didn't call the order in. I don't want to seem unsympathetic to the disabled but this requirement seems a bit much. :confused:
-
https://www.cnbc.com/2019/10/07/dominos-supreme-court.html "
Quote:
The case was originally brought by a blind man named Guillermo Robles, who sued the pizza chain after he was unable to order food on Domino’s website and mobile app despite using screen-reading software.
" So I'm wondering why he didn't call the order in. I don't want to seem unsympathetic to the disabled but this requirement seems a bit much. :confused:
MKJCP wrote:
So I'm wondering why he didn't call the order in.
Maybe he has a thick Scottisch accent? Doesn't change the fact that most websites provide this simple to add "feature" that has been around since the img-tag. Why can't Dominoes?
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
MKJCP wrote:
So I'm wondering why he didn't call the order in.
Maybe he has a thick Scottisch accent? Doesn't change the fact that most websites provide this simple to add "feature" that has been around since the img-tag. Why can't Dominoes?
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
Ah, I didn't know it was a simple and common fix. I don't do any web stuff (except for my very simple and non-compliant personal site). I assumed it was a substantial task as it seems all I hear from folks at work and on CP is how difficult everything webbish seems to be. Thanks for the enlightenment.
-
Ah, I didn't know it was a simple and common fix. I don't do any web stuff (except for my very simple and non-compliant personal site). I assumed it was a substantial task as it seems all I hear from folks at work and on CP is how difficult everything webbish seems to be. Thanks for the enlightenment.
MKJCP wrote:
Ah, I didn't know it was a simple and common fix.
There just needs to be an alt-text for each image; the screenreader software will then "read" those tags out loud. Most websites do that already.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
What ticks me off even worse is the really small gray text that is intended to be seen as secondary info, but that is so freakin small, I have to bring the site's scale up to 120% to read it. CP. Just sayin...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Count me in. Even if the typeface is large enough by itself, web fashion of today is to use fonts made up of hairlines only. Single pixel width, or thereabouts. Sometimes medium or light grey as well. I think the designers might use the term "elegance" in describing the style. They definitely should not use the term "readability". In theory this should create no problems with web pages ... if what we were told 20 years ago had been true. It was said that the "cascading" nature of CSS allows you to define the typeface and size at the top level, and it would sift through the layers, adjusting whatever you wanted to adjust. We were told that the same page could be viewed using one CSS for large, high contrast text, another CSS for poor resolution screens, hence different fonts and other layout, yet another CSS for users with a braille terminal. This was a blatant lie. In the very first years, I tried to make alternate CSSes. Essentially it might affect websites that didn't use CSS at all (they did exist, 20 years ago!). For very simple, almost pure text pages, you might be able to affect some text, but often just part of it. I never saw a web site providing a "If you can't read this text because it is too small, click on it to enlarge font size" that could be scaled up by adding a local CSS. I never saw a single demo of a CSS that would give a braille reader access to the web page text, or a reduced-vision person higher contrast and larger typefaces, not even in the early days when absolute measures were considered inappropriate. Today, most websites set both typeface and size explicitlty, very close to the actual graphics, and in absolute values rather than relative. Changing a default has no effect whatsoever. I don't even know if today's browsers have facilities for inserting CSS files or set defaults. Why should they, when 99,99% of page elements will ignore it anyway? In theory I can, for each and every web page, pick up the specific CSS of that web page and edit it. Although there in theory is no difference between theory and practice, in pratice there is. The onlyu workable solution would be one a single "private" CSS, setting defaults for all web pages. Our only rescue is the zoom function. But that cannot change a light grey hairline font to a solid black font of a fatter design. To make the text readable I have to zoom up far more than I would do with a proper typface choice. I suspect that there is some way of setting up a global (on my machine) font substitution tab
-
I've been noticing more and more that websites are setting their font size to something a blind man could read. Particularly sites with API documentation, but not exclusively. I find myself setting the zoom factor in Chrome to 75% or even less, simply so these pages don't SCREAM at me, like that.
Latest Articles:
Client-Side TypeScript without ASP.NET, Angular, etc. -
Well, that's an interesting aspect and reason to go for the louder fonts, however, not many visually impaired users gonna use the development related websites. Also, most of the site developers might not be aware of the ADA.
You can have all the tools in the world but if you don't genuinely believe in yourself, it's useless.
-
Gandalf_TheWhite wrote:
not many visually impaired users gonna use the development related websites
Um, I beg your pardon? ;P
If you think 'goto' is evil, try writing an Assembly program without JMP.
How did you miss 'Not Many' & 'Development Related websites' If it otherwise please share the data.
You can have all the tools in the world but if you don't genuinely believe in yourself, it's useless.
-
I've been noticing more and more that websites are setting their font size to something a blind man could read. Particularly sites with API documentation, but not exclusively. I find myself setting the zoom factor in Chrome to 75% or even less, simply so these pages don't SCREAM at me, like that.
Latest Articles:
Client-Side TypeScript without ASP.NET, Angular, etc.I totally blame high resolution phones and tablets for this. When you have a page that's perfectly reasonable on, say, a 24" 1080p monitor, it's rather unreadable on a 6" phone at the same resolution. Since so many lemmings nowadays are glued to their phones, what's now appropriate for a phone turns into a huge waste of space on a monitor.
