Live data from Hacker News

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

blog.logrocket.com

161–170 of 271 posts

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

#161

Earlier quoted context omitted.

You could use a custom domain with Medium to get the UI with your blog

Except sadly not anymore, even if you pay: https://help.medium.com/hc/en-us/articles/115003053487-Custo...

I say it's great. Hopefully more people concerned with owning their content will move to a static blog generator or even WordPress.

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

#163
post #131
post #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.).

So how do you handle something like filters on a product listing? Make every filter option its own link?

they're not links, as they don't link off to other pages - they'd be buttons, with event handlers attached.

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

#165
post #148

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

You realize you don't need input field for file input in any of the modern browsers. Just capture the click event and create input field temporarily. let i = document.createElement('input'); i.type = 'file'; // other attributes if you like i.onselect = ev => { // ev.files contains selected files }; i.click(); i.remove(); No stupid styling hacks needed. At most you may need tabIndex on the or that represents the butto…

[deleted]

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

#166
post #125

Earlier quoted context omitted.

I've been doing this internet thing for nearly 25 years now. I'm not ignorant of all the things I can do on the "modern" internet or browsers. I'm not waiting around passively for someone to deliver experiences I want--I build software, ffs. I made a simple statement about what I wish browsers did by default . That means no extensions. That means that--unless I'm going to fork a browser to build it myself--building y…

Please accept my apologies. I fully understood your comment, your point, and your desire. I was attempting to encourage you (and anyone less experienced reading along at home) to push the world that exists in the direction of the world you want, rather than imply any ignorance on your part. It's far, far too easy for people to treat technology as artifacts handed down from the gods that can only be passively accepted…

> It's far, far too easy for people to treat technology as artifacts handed down from the gods that can only be passively accepted.

Too true. I usually phrase the same sentiment as bemoaning how people treat tech as if it's some magical black box into which they cannot peer & tinker.

Of course, I feel that same way about other things, such as automobile engines. I know it isn't a magical black box, but it may as well be.

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

#167

Ironically, this article was posted on Medium, whose apps are notoriously inaccessible. Despite being a reading-focused app, it does not let you change the text size or spacing in any way. And on iOS, it also ignores the user's systemwide dynamic text setting.

Not to mention the persistent sharing dickbars and make you read through a mail slot.

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

#168
The easiest way to keep your apps accessible is not making them web apps. Instead of relying on an entirely redundant abstraction layer/OS built on top of your existing one just write native applications.

But if you have to do it in a browsers then at least make it so the actual content (text/images) do not require JS to load and display.

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

#169

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…

Just thought I'd let you know, Great Big Story is running a development build of react. You save some of bundle size and performance by switching to a production build.

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

#170

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.

This is why I disable custom fonts and limit the range in size from 9-13 everywhere. I have a mono and a regular font allowed. I've been doing that for at least a decade.
Post reply on HN