Live data from Hacker News

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

blog.logrocket.com

201–210 of 271 posts

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

#201
post #187
post #155

Earlier quoted context omitted.

Why does Medium need an app in the first place? Is a web browser not a good enough app for reading content on the internet?

Apps often are a solution for business problems rather than users. In mediums case, the app solves the ad blocking and retention problem.

As far as I am aware of, Medium is not supported by ads, and its popularity depends on the web.

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

#202
post #50

My biggest pet peeve is when sites use js to try to "help" me scroll. What. The. Hell. is wrong with developers who think their users' browsers can't scroll? Am I the only one?

Often the blame will lie with someone else - the designer or the PM. Some webdevs are to blame, but many of us would prefer to work on tasks OTHER than arguing with the browser over how it should do it's job.

The most common source of blame for scrolljackers are wordpress template writers. There was a huge surge in developing them a few years ago that happen to coincide with popularity in scroll-jackers actually being considered good. Mostly because of the Windows crowd not actually having a great scrolling experience like Mac. Now windows scrolling is 95% on par with the mac, but alas, the scrolljacking stays with us until people migrate off wordpress or people are interested in developing for wordpress again.

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

#203

> You use ALT text by adding the alt attribute with a value of the text equivalent of your image, like so: > https://example.com/image.png” alt=“developer in an office working feverishly to hit a deadline on a software project” /> Is this actually a good idea? This sounds like a typical "hero" or "teaser" image, to capture the reader's attention or interest. I don't think the alt tag does that in a comparable way, fo…

The W3C's Web Content Accessibility Guidelines (the gold standard for web accessibility and the usual legal requirement) only requires that images of text have "text alternatives" - it doesn't require the alt attribute specifically. Your solution to just use text alongside the image should be fine in most cases.

The only practical difference is that with alt text, the blind person is aware that there's a graphic on the page. With alt="" they have no idea the image exists. Does that matter? Maybe in some contexts - you have to use your best judgment on a case-by-case basis.

It also doesn't require alt text for images that are purely decorative and not necessary to understand the content, though this is a bit subjective. Could a blind reader still imagine the idea of a developer in an office working feverishly to hit a deadline, and would that add to their experience of the article enough to be worth including? Again, there are no hard and fast rules here so you just have to use your best judgment.

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

#204

Earlier quoted context omitted.

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

Is that a problem with the file input button, or with every other button on your website? The file input button does seem to be a barely remembered feature by browser builders. It's weirdly specific, doesn't work the same way on phones, and probably only hangs around because there isn't a decent alternative.

IIRC correctly, the File Input button was deliberately excluded from CSS styling, as it was felt that it would be abused to 'steal' data from clients, if the user wasn't aware it was file upload...

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

#205

So much unnecessary reading to figure out what this is. I gave up.

I'm not sure that this comment is serious, but I think it illustrates exactly why text isn't more prominent in modern websites.

I noticed a similar comment here the other day:

https://news.ycombinator.com/item?id=17721496

Blogs are such a waste. I dont need to hear your life story and opinions. Post the situation, the plan, and details/documentation.

I do not have the time to read a literal 6,000 words.

I for one, do enjoy reading a long article and if I'm busy I will bookmark it/add to reading list for later. Everything doesn't need to be crammed into 280 characters or less. Maybe I'm just old fashioned and should embrace our race to the future presented in the movie Idiocracy?

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

#206
post #153
post #133

Earlier quoted context omitted.

Ha! I should have said the technique works. I'd obviously want to lay things out a little smaller on phone screens. Though, for that particular use, is just punt and say not supported on smaller screens. Note, I couldn't just do an image because of the animation nonsense I was playing with. Edit: though, oddly, I think you are really complaining about some of the styling I inherited from org. I can possibly fix that…

Sure, max-width will restore reflow, but now your code listings and images break out of their container: https://i.imgur.com/utCVxg1.png My point is that absolute positioning/pixel perfect designs are easy because they solve a simplified project "How to have my content look correct at a fixed size". But it breaks down once that fixed size is no longer reasonable for the target device.

Right, I agreed that what I did would not scale down to small screens. Nor will it work if you ever try and display on an apple watch or some such. The max-width would have just given you flowing text. I fully expect the visualization to be broken on small sizes.

I contend that is just not a requirement for most things. This particular endeavor mine, included.

So, what point are you arguing against? If it was that I pitched this strongly as a panacea. I definitely concede it is not one. But I also don't believe in panaceas.

If if it is that there is an easier way to get that layout such that I can play with it in silly animations without absolute positioning, I'm game to see it.

Edit: I should say thanks for getting me to look at my own site again in a long time. The code block would need the same width->max-width flip. Though, I question on why anyone would look at that page... well, ever, first. But in general even on a small screen. Not sure what I want code blocks to do there. Will take another look sometime hopefully this weekend. :)

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

#207
post #52
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 that's why that happens. Why on earth would you break one of the most foundational aspects of HTML that way?

Off the top of my head, for one, because my HTML sits on top of a REST API and links can't hit a DELETE endpoint.

I've no idea what people expect right clicking a delete link to open in a new tab to do?

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

#208
post #52

Earlier quoted context omitted.

So that's why that happens. Why on earth would you break one of the most foundational aspects of HTML that way?

Off the top of my head, for one, because my HTML sits on top of a REST API and links can't hit a DELETE endpoint. I've no idea what people expect right clicking a delete link to open in a new tab to do?

> I've no idea what people expect right clicking a delete link to open in a new tab to do?

I expect it to issue the delete, and then dump the response to the delete into a new tab rather than navigating away from the page that hosts the delete link.

There might be ten other delete links on the original page, and I don't want to delete-back-delete-back-delete-back, when I can just open all of them in a new tab, then go through the tabs to look for errors.

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

#209
post #52

Earlier quoted context omitted.

So that's why that happens. Why on earth would you break one of the most foundational aspects of HTML that way?

Off the top of my head, for one, because my HTML sits on top of a REST API and links can't hit a DELETE endpoint. I've no idea what people expect right clicking a delete link to open in a new tab to do?

Yes, but application developers have long faked it using GET .../thing?op=DELETE

When you get sick of faking it you look into why there is no way to get browser to send real DELETEs and PUTs and w3c verbiage says "because application developers don't seem to need it" ... because they fake it ... because they have to fake it ... because browser don't do it ... because devs don't need it ...

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

#210
post #208

Earlier quoted context omitted.

Off the top of my head, for one, because my HTML sits on top of a REST API and links can't hit a DELETE endpoint. I've no idea what people expect right clicking a delete link to open in a new tab to do?

> I've no idea what people expect right clicking a delete link to open in a new tab to do? I expect it to issue the delete, and then dump the response to the delete into a new tab rather than navigating away from the page that hosts the delete link. There might be ten other delete links on the original page, and I don't want to delete-back-delete-back-delete-back, when I can just open all of them in a new tab, then g…

That sounds like the right behaviour to me, although there is an arguably nasty non-idempotence. Click it the first time and you get a DELETE response. Click it the second time and you get a 404.
Post reply on HN