Earlier quoted context omitted.
For some reason, font sizes have shot through the roof in the past few years. Medium is one of the biggest offenders. You get maybe 2-3 paragraphs per page now, when entire articles would fit on a single screen page with normal-sized fonts.
Not to mention the absurd margins that are nearly the width of the text itself.
The easiest way to keep your web apps accessible: Just use text
71–80 of 271 posts
Re: The easiest way to keep your web apps accessible: Just use text
#72Earlier quoted context omitted.
I wish I could set reader mode as the default experience. Then, I’d click on something to load the full experience when I know/think it’s needed (and perhaps have my browser remember that choice). Currently, I can only enable reader mode after my browser has loaded all the shit I don’t want loaded.
https://addons.mozilla.org/en-US/firefox/addon/automatic-rea...
Yeah, I know there are extensions for this. I was talking about what I wish for--browsers blocking all the extraneous requests by default and just showing me the page content alone in reader view without downloading all the additional crap.
Re: The easiest way to keep your web apps accessible: Just use text
#73I'm still looking for "just use links". So many frontends I see use fancy onclicks to emulate links (including updating window.location). However they are either not links or are void links. This breaks all sorts of useful things (copy link location, open in new tab &c.).
I agree for cases where the text is supposed to behave like a hyperlink - it should be one.
But in cases where its behaviour is that of a button (even a button which has the appearance of blue text - think iOS) then onclick is a good choice. Especially for contexts where “open in new tab” makes no sense.
I can’t see any valid reason for using a void link - worst of both worlds?
Re: The easiest way to keep your web apps accessible: Just use text
#74Earlier quoted context omitted.
I didn't know Medium did "white label" blogs on non-medium.com domains, but that's what this is. The irony is that people go to medium because it's kind of .. expected somehow? And looks more authoritative?
People use Medium because it's the easiest way to write some plain text and have what you wrote look decent in the browser. That's all it comes down to.
Really? I always figured that plain text looked pretty damn awesome in a browser. Example: https://motherfuckingwebsite.com/
I'm honestly curious how Medium is an improvement over that. Are you referring to the technical challenges of hosting content, perhaps?
Re: The easiest way to keep your web apps accessible: Just use text
#75Reading this article made me realize what it is that's broken about the concept of semantic markup and why websites even today are div soup. It's the same reason why divs won in the first place. You can't dictate the shape of a document to people and it be anything other than a kludge. Take the site I work on, Great Big Story[1]. We have sections and headers, but our content isn't defined by text, it's defined by gra…
The whole debate between semantic markup and visual styling in CSS looks to me to be a massive exercise in people yelling past each other and needlessly making all life difficult. I've ranted about this before, but worse is that everyone insists on trying to go with the default flow of elements as much as they can. Example I used last time was that it is actually easy to layout things and have them look pretty solid…
I like absolute positioning but it's really hard to learn how to use fluently. New devs need to be educated on the concepts otherwise you get a total mess.
Flex and grid are more intuitive so they're easier for juniors to train up on.
Re: The easiest way to keep your web apps accessible: Just use text
#76Earlier quoted context omitted.
https://addons.mozilla.org/en-US/firefox/addon/automatic-rea...
Yeah, I know there are extensions for this. I was talking about what I wish for--browsers blocking all the extraneous requests by default and just showing me the page content alone in reader view without downloading all the additional crap.
It's worth considering that one of the many, many wonderful things about the modern internet and modern browsers is that you don't have to sit and wait passively for someone to deliver the experience you want to you. You have everything you need to make Firefox or Chromium do it for you!
Then you can share it with others, and they can have the automagic, fresh-from-the-box, on-by-default experience you would like.
Re: The easiest way to keep your web apps accessible: Just use text
#77Also please don't use bad fonts. Someone posted the following article the other day and the font drove me so nuts that I had to resort editing the CSS code to make it readable. https://blog.bugsnag.com/bug-day-race-condition-therac-25/ I really wish "reading mode" was a prominent feature in desktop browsers.
It's a button in the title bar in Firefox and Safari. I haven't used it but Edge seems to also have a reader mode. By "desktop browsers", do you just mean Chrome?
/picardface
Yes, I am using Chrome on Windows. Thank you for the Firefox suggestion! I didn't realize it was built in now and you can use a serif font. I guess it's back to Firefox!
Re: The easiest way to keep your web apps accessible: Just use text
#78Earlier quoted context omitted.
Not the file input button, unless things have changed in the last year since I had to build one. Other buttons, sure, but not on file inputs.
Heaven forbid your buttons look like buttons.
The point being that the file input button doesn’t look like any other button on their website. But hey, why solve a problem when you can force the entire world to accommodate it?
Why does there even have to be a button? I want an API not a button...
Re: The easiest way to keep your web apps accessible: Just use text
#79https://motherfuckingwebsite.com/
Really disappointing with the google analytics javascript used on this site ironically not making it as simple as he claims it is.
Re: The easiest way to keep your web apps accessible: Just use text
#80Earlier quoted context omitted.
The whole debate between semantic markup and visual styling in CSS looks to me to be a massive exercise in people yelling past each other and needlessly making all life difficult. I've ranted about this before, but worse is that everyone insists on trying to go with the default flow of elements as much as they can. Example I used last time was that it is actually easy to layout things and have them look pretty solid…
I like absolute positioning but it's really hard to learn how to use fluently. New devs need to be educated on the concepts otherwise you get a total mess. Flex and grid are more intuitive so they're easier for juniors to train up on.
How is it hard to learn. Put someone in front of some graph paper and let them layout what they want the page to look like. Get someone a little more experienced to help them pick the points that can grow, and off you go.
Not to say that they can't do better with flex and grid. But it was like our entire industry didn't even bother trying to learn with the first tools that our industry made.