Live data from Hacker News

The easiest way to keep your web apps accessible: Just use text

blog.logrocket.com

41–50 of 271 posts

Re: The easiest way to keep your web apps accessible: Just use text

#41

Earlier quoted context omitted.

> I really wish "reading mode" was a prominent feature in desktop browsers. What do you mean here by "prominent"?

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.

You can enable reader mode by default on Safari. It's in Preferences -> Websites -> Reader.

Re: The easiest way to keep your web apps accessible: Just use text

#42

Reading 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…

> but we have so many weird little needs to introduce elements just for styling purposes.

I think this is the number one reason why I prefer mobile dev over front-end web dev.

Re: The easiest way to keep your web apps accessible: Just use text

#43
I'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.).

Re: The easiest way to keep your web apps accessible: Just use text

#44
post #33

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.

I'm in favor of this. My eyes aren't particularly bad, but I have to use reading glasses in order to read most computer text, and some can get really difficult. Larger fonts are better even for my bad-like-most-other-people-my-age eyes. The tiny text I would have found fine 20 years ago is painful now.

There's an easy fix for folks like yourself: most (all?) modern browsers support setting a minimum font size. Jack that up way into the double digits, and stop justifying ridiculously large font sizes for everyone.

Re: The easiest way to keep your web apps accessible: Just use text

#45

Posted on Medium with a massive pointless image at the top and page loaded asynchronously using JS.

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.

[deleted]

Re: The easiest way to keep your web apps accessible: Just use text

#46
post #41

Earlier 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.

You can enable reader mode by default on Safari. It's in Preferences -> Websites -> Reader.

No way. That’s incredible.

Edit: Awww, so close. Sadly, I can see Safari still loads all the crap. So I'd still have to disable/enable JS manually, and have other blocking in place for the extraneous requests that don't belong in a reader view. Maybe one day.

Re: The easiest way to keep your web apps accessible: Just use text

#47

Reading 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…

> input button is hidden using CSS tricks because the actual button can't be styled.

Buttons can be styled.

Re: The easiest way to keep your web apps accessible: Just use text

#48

Reading 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…

> input button is hidden using CSS tricks because the actual button can't be styled. Buttons can be styled.

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.

Re: The easiest way to keep your web apps accessible: Just use text

#49

Earlier quoted context omitted.

> I really wish "reading mode" was a prominent feature in desktop browsers. What do you mean here by "prominent"?

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.

NoScript
Post reply on HN