News for hackers. Stuff that matters.
Re:The unreasonable effectiveness of simple HTML by ogre_codes on Wednesday January 27, 2021 @12:56PM (#25931398)
This is a fantastic article, it does miss one very key point about bog-standard HTML which is worth mentioning though.

The standard widgets are all accessible, people with screen readers, limited mobility, poor vision, etc, all rely on pages being written so the devices they use to read the web can function properly. People who choose to eschew these standard components very frequently end up with a site which is unusable for disabled people.

Very few people have the skill to turn a div into an effective button, yet over and over I see web sites with rows of buttons which are in fact just divs with javascript behind them.

Making your site accessible isn't just a good practice, in the US, it is the law. Courts have ruled that the ADA applies to web sites along with any other type of business. A small sample of sites where people thought they could smash together super-fancy sites without concern for basic needs of users: https://www.atilus.com/top-10-ada-lawsuits/

Re:The unreasonable effectiveness of simple HTML by lastofthemojito on Wednesday January 27, 2021 @02:56PM (#25933099)
One of the great things about accessibility is that it often doesn't just benefit people with disabilities.

My wife and I have watched a lot of TV in the past year with the volume down and captioning on, while we enjoy some down time while our baby is sleeping.

A ramped entrance to a building allows wheelchair-bound folks access, but it also helps able-bodied people using delivery dollies.

Making simple, lightweight web pages makes them accessible to those with older browsers and devices, but it also saves power consumption, time, and frustration for folks on M1 MacBook Pros.

Re:The unreasonable effectiveness of simple HTML by acdha on Wednesday January 27, 2021 @03:34PM (#25933570)
> One of the great things about accessibility is that it often doesn't just benefit people with disabilities.

I really love how Microsoft's design team has pushed this with their “Inclusive Design” concept[1] and highlighting how any sort of disability can be situational (holding a baby), temporary (broken arm), or permanent (missing arm) but we often only think of those in the last context despite there being orders of magnitude more people in the first two categories. Parenting is really good for showing this out since you get the need to be quiet, be able to do something using only one hand (or none), navigate sidewalks with a stroller, trying to do anything while sleep deprived, etc.

There's a great chart on page 42 (“Persona Spectrum”) of this PDF which I try to get every team I work on to go through which really gets people to think about what this means:

https://download.microsoft.com/download/b/0/d/b0d4bf87-09ce-...

1. https://www.microsoft.com/design/inclusive/

Re:The unreasonable effectiveness of simple HTML by einpoklum on Thursday January 28, 2021 @01:06PM (#25946024)
1. With due respect to various useful elements of design in Microsoft's work - this booklet reads like "We design for black people! We design for LGBT people! We design for disabled people! Look at us, we're so morally and politically superior!"

2. Microsoft makes software which costs a lot of money (for most people in the world); often a lot of money. One of the main problems people with disabilities have is low income and lots of expenses.

3. Microsoft makes software which hogs resources and thus runs poorly, or not at all, on older or simpler, low-power devices. This also not very accessible. So it might have a perfect UI experience - on the computer people don't have. Admittedly, though, this is not as bad of a problem in the past few years.

4. I wonder how actually accessible MS apps and Windows actually are. Considering how they've botched a lot of their designs in recent years even for normies (Metro; Ribbons).

Re:The unreasonable effectiveness of simple HTML by acdha on Thursday January 28, 2021 @02:55PM (#25948069)
It's disturbing that you find trying to be inclusive offensive because you perceive them as political opponents. I mean, who cares what people's political leanings are if they are making things better for people who haven't been well-served historically?

Similarly, while Microsoft software isn't free nothing in computing is and it seems like an odd angle to criticize an effort to help make their products better based on decisions made by other people in different parts of a huge company, or to criticize them for things in the past which they've since corrected.

Re:The unreasonable effectiveness of simple HTML by einpoklum on Thursday January 28, 2021 @06:16PM (#25950917)
> nothing in computing is free...

Luckily, that is not the case:

https://en.wikipedia.org/wiki/Free_software

I suggest you take a bit of time to read some Free Software philosophy. Consider starting with "Why software should be free", by Richard Stallman:

https://www.gnu.org/philosophy/shouldbefree.html

Re:The unreasonable effectiveness of simple HTML by acdha on Thursday January 28, 2021 @10:06PM (#25953261)
Haha, that lazy troll takes me right back to Slashdot before the turn of the century. On the off chance that you actually believe what you're doing is useful, here's why this form of advocacy has singularly failed to attract converts (speaking as someone who's been using and contributing to open source software since the early 1990s): open source software is only free if your time and expertise are free.

That free software has to run on non-free hardware (even if the oft-heralded RISC-V revolution happens, someone has to manufacture the device) and most people do not have the skills or time to assemble the hardware or maintain an OS. That means that we're all making tradeoffs of what things we buy and what we do ourselves, and for the vast majority of computer users, even open source developers, that involves outsourcing that work to a handful of companies (or, maybe, a hardware company and Debian). Most computer users consider that a good deal: they spend time on things they like and pay a rather small amount of money relative to the utility they get from a transformative device like a general purpose computer. This means that for most people the decisions which matter the most are made by Microsoft, Apple, or Google — and that anyone who cares should applaud them improving accessibility because it will affect daily life for billions of people.

This is especially true for accessibility, where people develop deep habits around things like screen readers and quality matters a great deal. I happen to work with a number of visually impaired users and have not heard good things about the Linux screen readers compared to their Windows or iOS counterparts, and that means that in the context of this thread it's really not useful to snark about the moral superiority of free software.

Re:The unreasonable effectiveness of simple HTML by sls on Saturday January 30, 2021 @09:59AM (#25969578)
I rarely bother to address this argument:

> open source software is only free if your time and expertise are free

but since you seem to actually be trying to discuss this in a thoughtful way, please note that we're not given a choice between free software that takes time and expertise to use and maintain vs closed software that takes no time or expertise to maintain. To mimic your original phrase, Windows 10 Pro is only $199 if your time and expertise is free. Going further, in my experience it's often been the case that the free software takes less time and less expertise to use and maintain.

Also, it's worth mentioning that you are conflating two different things, open source software and free software, a distinction that often doesn't matter but is central when the point at hand is the ethics of free-as-in-freedom software vs non-free software, a distinction the term open source was deliberately created to elide. You are also conflating free-as-in-freedom with free-as-in-beer by opposing the "software is only freedom-free" with "your time and expertise are free-as-in-beer free".

Finally it's not clear to me why you went on to address the pragmatics of non-free hardware or the fact that human effort is necessary to build computers, maintain distros, write kernels etc. Is there a claim that it's unethical to try to run free software on the hardware that you have, or that free(dom) software must always be provide without cost on hardware that is both free(dom) and without cost? If not, then computer users can still spend a small amount of money, relative to utility, to buy a computer that runs free(dom) software.

I'm not disputing your claims that accessibility software on Windows or iOS is better than that on Linux, because I don't know the space. It's an unrelated argument, afaict. To illustrate this, simply imagine that some government or corporation had decided to make high-quality accessibility software available under a free license. (I am reminded of Intel's work supporting Dr. Hawking.) You wouldn't conclude from this that all your previous thoughts about free and open source software vs closed/commerical software were wrong, I assume.

Re:The unreasonable effectiveness of simple HTML by pvorb on Wednesday January 27, 2021 @04:51PM (#25934497)
I fully agree with all of your points.

I just wanted to point out the irony that the manual and other documentation for this "inclusive design" toolkit come as PDFs – the worst choice you can make if you strive for accessibility.

Re:The unreasonable effectiveness of simple HTML by scrollaway on Wednesday January 27, 2021 @07:02PM (#25935995)
PDFs can be accessible, and many of them are! Everyone who works with PDF needs to know about PDF/A:

https://en.wikipedia.org/wiki/PDF/A

PDF/A is a small family of sub-formats to PDFs which amount to the accessible subset of PDF + some requirements.

PDF/A and PDF/UA are mandated by a variety of governments for PDF distribution. They're very suitable to archival and are accessible (screenreaders can work with them, their text can be cleanly copied, etc).

Re:The unreasonable effectiveness of simple HTML by pvorb on Thursday January 28, 2021 @12:47AM (#25938675)
That might be true, but these ones are not. I can't efficiently read them on my smartphone and have to scroll around a lot. They also show two pages on one, probably to be better printable for some marketing material, but I would never want to print a PDF that's mostly black, because that would overwhelm my printer. I'm also not near a printer right now. This is clearly inaccessible to me.

HTML, on the other side, can be easily made readable on any device. Even if the author didn't care, through readable mode in my browser.

Re:The unreasonable effectiveness of simple HTML by auggierose on Thursday January 28, 2021 @06:39AM (#25940667)
PDFs are often the BEST way to read something. I prefer PDF text books over any other format, because (not very good) computer algorithms laying out text is inferior to proper professional layout.

Why would you read PDFs on a smart phone anyway?

Re:The unreasonable effectiveness of simple HTML by brigandish on Thursday January 28, 2021 @07:53AM (#25941161)
> Why would you read PDFs on a smart phone anyway?

Is there another option here?

Re:The unreasonable effectiveness of simple HTML by auggierose on Thursday January 28, 2021 @09:10AM (#25941935)
Yeah, read it on a large tablet, or on a large computer display.
Re:The unreasonable effectiveness of simple HTML by falcolas on Thursday January 28, 2021 @10:35AM (#25943426)
Ironic to read this comment in an article of someone reading a web page on a PSP.
Re:The unreasonable effectiveness of simple HTML by corty on Thursday January 28, 2021 @04:13AM (#25939847)
PDF/A isn't necessarily accessible. First, PDF is very hard to impossible to scale for people who need big writing, due to reflowing being unavailable or not working properly. Text in PDF/A can still be a big image, e.g. in a scan for archival purposes, if you are "lucky" there is an OCR overlay, but then your screenreader reads OCR'd text which is hit-or-miss. And text ordering is supposed to be "reading order" in PDF/A, but many tools, especially DTP tools make a mess of it and jumble up the (screenreader-visible) order of text in textboxes, columns and sometimes even paragraphs.

IME PDF/A is better than nothing, but far worse than plain HTML for accessibility..

Re:The unreasonable effectiveness of simple HTML by scrollaway on Thursday January 28, 2021 @11:36AM (#25944481)
There is no OCR overlay in /A, what are you talking about? It should be the original text.

If it's scanned copies then all it is is a bunch of images, not A compliant.

Re:The unreasonable effectiveness of simple HTML by corty on Thursday January 28, 2021 @12:43PM (#25945504)
Scanned images are totally PDF/A-compliant. The standard is just about reproducible archiving, nothing else. Bitmaps are perfectly reproducible and pass every compliance check. That PDF/A is more accessible than any old PDF is just a side-effect.
Re:The unreasonable effectiveness of simple HTML by qwantim1 on Wednesday January 27, 2021 @08:46PM (#25937038)
PDFs are fine but their time will come to an end for one big reason: they were invented to reproduce defined-size paper forms.
Re:The unreasonable effectiveness of simple HTML by ocdtrekkie on Wednesday January 27, 2021 @11:10PM (#25938039)
This is their strength: You know a PDF will not shift its presentation due to device changes. PDFs from when the PDF was created still work right today. And they still look the same.
Re:The unreasonable effectiveness of simple HTML by labawi on Wednesday January 27, 2021 @05:11PM (#25934778)
I may be missing something obvious, but why is pdf such a bad choice?

As long as it has actual text and is reasonably typeset (selecting text in this pdf seems to work properly), I don't see what's wrong. I'd take it any day over webpages with random floating content that you have to click through and use a modern browser with javascript without blockers/filters for the content to even render, in small text on 20% of the page, with low contrast and somehow broken zoom.

Re:The unreasonable effectiveness of simple HTML by lucasmullens on Wednesday January 27, 2021 @05:45PM (#25935195)
I would assume PDFs don't typically work well with screen readers, which is what a large part of web accessibility is designed for.
Re:The unreasonable effectiveness of simple HTML by viraptor on Wednesday January 27, 2021 @09:42PM (#25937481)
As long as they're produced in a reasonable way, they work just fine. The option was even included natively in adobe reader 9 https://www.montgomeryschoolsmd.org/departments/hiat/tech_qu...

Where it breaks down is some badly designed OCR systems which place the letters independently rather than in lines/blocks. But that's starting from a document which was not accessible in the first place, so not a huge issue.

Re:The unreasonable effectiveness of simple HTML by colejohnson66 on Wednesday January 27, 2021 @06:56PM (#25935924)
As PDF is essentially saying, “put this thing here”, you’d think it wouldn’t. But it does. You can embed the source text for screen readers. It’s also how copying text from PDFs works.
Re:The unreasonable effectiveness of simple HTML by pvorb on Friday January 29, 2021 @06:56PM (#25964471)
The whole topic of this thread is reading web pages on a PSP. There's a whole universe of devices that perfectly render good old server-side HTML with CSS styling, but can't display a PDF for reasons. Or if they can, it will be annoying because it won't fit on the screen and be readable at the same time. That's its unique selling point as well as its biggest drawback.

I have to admit that many modern SPAs also won't rendet on many devices, though.

Re:The unreasonable effectiveness of simple HTML by Stevie300 on Wednesday January 27, 2021 @09:25PM (#25937329)
What sort of file types are preferable? I'm not very familiar with accessible tech.
Re:The unreasonable effectiveness of simple HTML by pvorb on Tuesday February 02, 2021 @05:32PM (#26007906)
HTML, as demonstrated by the article, is accessible by default.
Re:The unreasonable effectiveness of simple HTML by scooble on Wednesday January 27, 2021 @04:55PM (#25934549)
To add to this, a perspective I've heard working in the disability sphere is 'everybody is disabled eventually' - be that through injury, illness, or even just old age.

This really challenges the view that thinking about disabled users is catering to the needs of a small group of the population. Whereas in fact it is bringing benefits to the majority of the population (at some point in their lives).

Re:The unreasonable effectiveness of simple HTML by AtlasBarfed on Wednesday January 27, 2021 @05:43PM (#25935162)
The culture of distraction distracts everyone from realizing they'll die.

Disability is just the fine print.

I remember walking around in a city after a parent died, and the world seemed like an illusion.

Re:The unreasonable effectiveness of simple HTML by ogre_codes on Wednesday January 27, 2021 @07:19PM (#25936239)
It's weird, sometimes I do something and I realize that if things had been slightly different it might have killed me.

Then I wonder if in a parallel universe I'm already dead.

Then I realize that if there are parallel universes there are probable countless times where I'm already dead.

Re:The unreasonable effectiveness of simple HTML by blackbrokkoli on Thursday January 28, 2021 @05:51AM (#25940404)
Does not even have to be that grim/profound.

Ever used your phone in the blazing sun, or rain? Had a partly shattered screen or tried to do something on the stone-age library computer? Searched for something with really slow or shaky connection? Tried to explain where to click via phone?

Suddenly all those accessibility features and "fail gracefully" come in really handy.

Re:The unreasonable effectiveness of simple HTML by myfonj on Thursday January 28, 2021 @06:12AM (#25940537)
It's often put as "temporarily abled" or "able-bodied".

    "We're all just temporarily abled."
is quite famous quote, as far as I traced attributed to Cindy Li.
Re:The unreasonable effectiveness of simple HTML by bonestamp2 on Wednesday January 27, 2021 @03:28PM (#25933499)
> watched a lot of TV in the past year with the volume down and captioning onf

I like how Apple TV now lets you pair two bluetooth headsets. My wife and I can watch shows without waking the baby. Combine that with the visual sound indicator on the baby monitor, and headphones with transparency mode, we can see when the baby is making noise and hear other environmental noises too. It's a nice combination of accessibility features that make a clever setup for hearing the TV. I can't wait until Apple TV supports spatial audio... then we'll have "surround sound" in our headphones too!

Re:The unreasonable effectiveness of simple HTML by ogre_codes on Wednesday January 27, 2021 @03:10PM (#25933268)
Yes, absolutely.

I use closed caption when possible because often I don't quite hear things right and can't make out words. I could turn up the TV, but this means I can enjoy it at the same volume as everyone.

Re:The unreasonable effectiveness of simple HTML by zzo38computer on Tuesday February 02, 2021 @11:55PM (#26010731)
I also use captions (even when the TV isn't muted). If someone else in the room is speaking so something on the TV is missed, it will be shown on the captions. Sometimes there might be some word or name I don't know and will want to look it up, and the caption will have the spelling (if the caption writer has spelled it correctly, which sometimes they don't, unfortunately). It could also be used for transcripts and caption scrollback, if those features were implemented, although unfortunately it isn't.
Re:The unreasonable effectiveness of simple HTML by eins1234 on Wednesday January 27, 2021 @06:03PM (#25935379)
Another great example of this is effective keyboard navigation is both an accessibility feature and something you can sell as a feature for power users who like to get things done as quickly and effortlessly as possible.
Re:The unreasonable effectiveness of simple HTML by m463 on Thursday January 28, 2021 @12:17PM (#25945116)
Like the apple face tracking mouse pointer, where you raise your eyebrows to click.

https://youtu.be/wAVij3tTAxE

Re:The unreasonable effectiveness of simple HTML by ehnto on Thursday January 28, 2021 @12:55AM (#25938714)
I use a tool called Vimium so I don't need my mouse to navigate websites, and it really quickly highlights websites that have accessibility problems. Even before this though, my preference was websites that use standard elements, as so frequently people can't write robust code and boutique buttons, drop downs or other widgets break.
Re:The unreasonable effectiveness of simple HTML by analog31 on Thursday January 28, 2021 @12:00AM (#25938402)
Indeed, I'm a double bassist, and accessible buildings are a huge blessing, especially when loading out at 2 AM after playing for 4 hours straight. Not to mention, they've probably saved me thousands of dollars in repairs.
Re:The unreasonable effectiveness of simple HTML by thewakalix on Wednesday January 27, 2021 @06:21PM (#25935561)
This is commonly termed the "curb cut effect".
Re:The unreasonable effectiveness of simple HTML by m463 on Thursday January 28, 2021 @12:13PM (#25945059)
The troublesome grey area is the part where people do it for control.

There is also sort of "exclusive design" that is practiced. You know - where you can't get comfortable on a park bench because you might sleep on it, or a ramp or stairs are built to exclude skateboards.

Same thing happens with websites, to "control" adblockers or "reader mode" and other nonsense.

Re:The unreasonable effectiveness of simple HTML by dmhmr on Wednesday January 27, 2021 @03:08PM (#25933234)
I might be misinterpreting your last sentence regarding M1 MacBook Pros. Are you saying they are underpowered for surfing the internet?
Re:The unreasonable effectiveness of simple HTML by lastofthemojito on Wednesday January 27, 2021 @03:19PM (#25933381)
The M1 MacBook Pro is at the other end of the spectrum from the outdated/underpowered device that requires a lightweight web page. But the user of such a fast machine still benefits from lightweight web pages (faster loading times, less CPU usage, etc).
Re:The unreasonable effectiveness of simple HTML by jaywalk on Wednesday January 27, 2021 @03:19PM (#25933383)
What he's saying is that this stuff has benefits even for people using modern, powerful machines like the M1 MacBook Pro.
Re:The unreasonable effectiveness of simple HTML by hsitz on Thursday January 28, 2021 @11:36AM (#25944475)
> . . .also saves power consumption, time, and frustration for folks on M1 MacBook Pros.

Did you mean to say ". . . for folks /not/ on M1 Macbook Pros"?

Re:The unreasonable effectiveness of simple HTML by recursive on Wednesday January 27, 2021 @01:18PM (#25931721)
> Making your site accessible isn't just a good practice, in the US, it is the law. Courts have rules that the ADA applies to web sites along with any other type of business.

This seems to imply that web sites are businesses. If my hobby sites are subject to this, I'm going to be in trouble.

Re:The unreasonable effectiveness of simple HTML by jcranmer on Wednesday January 27, 2021 @01:23PM (#25931801)
If you're not selling anything, then you're not engaged in commerce and you wouldn't qualify as a "public accommodation" and the law doesn't kick in for you.

(Complete list of public accommodation is 24 USC §12181(7)--https://www.law.cornell.edu/uscode/text/42/12181).

Re:The unreasonable effectiveness of simple HTML by ogre_codes on Wednesday January 27, 2021 @01:56PM (#25932267)
Right at the top of that page:

> The term “commerce” means travel, trade, traffic, commerce, transportation, or communication

It is pretty funny that their definition of commerce includes commerce, but seems like communication is on the list as well.

Re:The unreasonable effectiveness of simple HTML by slavik81 on Wednesday January 27, 2021 @11:02PM (#25937989)
Seems to be a common thing. One of my favourites from The Canadian Customs Tariff Schedule, Ch. 71 § 4.B:

> The expression "platinum" means platinum, iridium, osmium, palladium, rhodium and ruthenium

Re:The unreasonable effectiveness of simple HTML by unicornporn on Wednesday January 27, 2021 @02:51PM (#25933024)
Re:The unreasonable effectiveness of simple HTML by cptskippy on Wednesday January 27, 2021 @01:39PM (#25932017)
Non-profits don't necessarily sell anything but they've been sued by the ADA for violating the laws on accessibility.
Re:The unreasonable effectiveness of simple HTML by jcranmer on Wednesday January 27, 2021 @02:09PM (#25932445)
"Sell anything" is probably a bit too restrictive, but summarizing case law on what counts as "affecting commerce" is difficult. In general, you need something that looks like a service or good being provided (even if no money is actually paid for it). Something like Youtube would absolutely fall under the ADA--it's clearly analogous to a movie theater.
Re:The unreasonable effectiveness of simple HTML by aksss on Wednesday January 27, 2021 @11:56PM (#25938377)
Let’s just be honest - anyone can sue anybody, but you’re probably not going to have problems under the ADA unless you become visible for some reason (success, expressing the wrong thoughts loudly, service necessity for a community, etc).
Re:The unreasonable effectiveness of simple HTML by wikibob on Wednesday January 27, 2021 @01:41PM (#25932056)
ADA is the American disabilities act, it can’t sue anyone.
Re:The unreasonable effectiveness of simple HTML by cptskippy on Wednesday January 27, 2021 @01:53PM (#25932229)
Sorry, I meant American Association of People with Disabilities (AAPD). We got sued under the ADA by the AAPD.
Re:The unreasonable effectiveness of simple HTML by andi999 on Wednesday January 27, 2021 @02:33PM (#25932772)
Today I learned Ikea is non-profit....
Re:The unreasonable effectiveness of simple HTML by ogre_codes on Wednesday January 27, 2021 @01:23PM (#25931800)
One of the big linked sites was Beyonce's web site.

How big an issue this is depends largely on how big your hobby site is.

Update: I think this might even be wrong, its likely personal sites are fine. It's still good practice though!

Re:The unreasonable effectiveness of simple HTML by recursive on Wednesday January 27, 2021 @01:24PM (#25931815)
The size of any of my sites is well below 1 milli-Beyonce.
Re:The unreasonable effectiveness of simple HTML by bachmeier on Wednesday January 27, 2021 @01:40PM (#25932039)
Unless there's a law I haven't heard of (definitely a possibility) it would be necessary to classify it as a commerce site for the law to apply.
Re:The unreasonable effectiveness of simple HTML by jcranmer on Wednesday January 27, 2021 @01:58PM (#25932288)
Taking a quick look at the site, Beyoncé has a store page on it, which would be sufficient to classify it.
Re:The unreasonable effectiveness of simple HTML by ogre_codes on Wednesday January 27, 2021 @02:50PM (#25933007)
With regards to the ADA, commerce means more than just "Selling stuff" so I'd be careful making assumptions about that.
Re:The unreasonable effectiveness of simple HTML by bluefirebrand on Wednesday January 27, 2021 @04:09PM (#25933989)
Selling stuff is probably sufficient but not necessary to qualify as commerce.
Re:The unreasonable effectiveness of simple HTML by elliekelly on Wednesday January 27, 2021 @01:13PM (#25931645)
> Very few people have the skill to turn a div into an effective button, yet over and over I see web sites with rows of buttons which are in fact just divs with javascript behind them.

What was the catalyst behind this trend? I just don’t understand the reason behind it. Hasn’t <button> been around forever? Was there some limitation on the button tag that made the div tag more desirable?

Re:The unreasonable effectiveness of simple HTML by aidos on Wednesday January 27, 2021 @02:35PM (#25932810)
You’ll find it’s because until “recently” (depending on how long you’ve been in this game, cough some of us since before css was even a thing) buttons weren’t stylable like they are now.

There’s no good reason to just not use buttons these days, but for a long time that wasn’t the case (cross platform).

Re:The unreasonable effectiveness of simple HTML by tyingq on Wednesday January 27, 2021 @04:54PM (#25934536)
<div> is also substantially older than both <button> and <input type="button">. The only button like thing before HTML4 was <input TYPE=SUBMIT>.

And, as you mention, the default styling was typically "make it look like the button in the underlying OS".

So there was a lot of inertia from existing code, examples, and docs that predated buttons. And a (misinformed) avoidence of it when it did appear because of styling.

Re:The unreasonable effectiveness of simple HTML by ogre_codes on Wednesday January 27, 2021 @06:39PM (#25935724)
The button html element is old enough to vote.

Since it's introduction, jQuery was born and died. Backbone was created and became obsolete. React took over the internet. Webpack, babel, and node were invented.

With all that change, I think it's safe to say web technologies are adopted or not based on inertia.

I think you are being over-generous.

Re:The unreasonable effectiveness of simple HTML by tyingq on Wednesday January 27, 2021 @06:50PM (#25935847)
Perhaps. I happen to be in a space with lots of "old enough to vote" code still running.

On the other hand, the Compose "button" in gmail is ... a <div>:

<div class="T-I T-I-KE L3" style="user-select: none" role="button" tabindex="0" jscontroller="eIu7Db" jsaction="click:dlrqf; clickmod:dlrqf" jslog="20510; u014N:cOuCgd,Kr2w4b" gh="cm">Compose</div>

Re:The unreasonable effectiveness of simple HTML by ogre_codes on Wednesday January 27, 2021 @07:32PM (#25936403)
Maybe came across more crossly than I intended... I have a blog I started in the 90s so I hear you.

FWIW, my issue with using divs is not that they should never be used as buttons. It's that few people who use them that way go to the effort of doing it correctly. It's absolutely possible to do it right and have a functioning/ accessible js button.

Either go the full way and do it right—with accessibility—or just style the standard components. In most cases the latter is the easiest way to go if you care about getting it right.

Re:The unreasonable effectiveness of simple HTML by ogre_codes on Wednesday January 27, 2021 @01:48PM (#25932160)
I suspect a lot has to do with the fact that it's easier to slap together a quick list/ menu thing than it is to make a select box look the way a designer wants it to. Similarly with calendar components, radio buttons, etc.
Re:The unreasonable effectiveness of simple HTML by K0nserv on Wednesday January 27, 2021 @02:12PM (#25932483)
What has happened in that scenario is that the designer has failed in their job. Unfortunately it’s up to engineers to catch this, which they often don’t
Re:The unreasonable effectiveness of simple HTML by ogre_codes on Wednesday January 27, 2021 @02:48PM (#25932987)
Designers don't really know or understand the limits of how you can style a select box. Nor should they need to. A good team will work together around the limits.

Also, FWIW some of the problem is with the browser makers (still!!). CSS still has a lot of browser specific quirks when working with some components.

Re:The unreasonable effectiveness of simple HTML by ryandrake on Wednesday January 27, 2021 @03:18PM (#25933361)
> Designers don't really know or understand the limits of how you can style a select box. Nor should they need to.

Designers absolutely need to be aware of and work within their platform's constraints, like a painter needs to understand and work with the physical characteristics of their canvas. It's this kind of mentality that results in visual specs that read "Make the window look exactly, to the pixel, like this Photoshop image!"

Re:The unreasonable effectiveness of simple HTML by K0nserv on Wednesday January 27, 2021 @02:58PM (#25933118)
I'm sure the designers who work on GDS[0] and its design system do. You are probably right that most don't, they should in my opinion. Of course you are also right that good teams will work together on this. I think the best designers have an understanding of HTML/CSS or the native toolkits if they work on Android/iOS. They know when the user experience will be signficantly improved by a custom component and work with their team to make it accessible and good in those case. They also know when not to reinvent a select to make it look slightly better.

This subthread is about why divs are used for buttons and why developers reimplement existing HTML components poorly. Good designers help their teams avoid this, good engineers work with their designers to avoid it.

0: https://www.gov.uk/government/organisations/government-digit...

Re:The unreasonable effectiveness of simple HTML by zepto on Wednesday January 27, 2021 @05:32PM (#25935032)
“ Nor should they need to.”

It’s funny - I’d expect an interior designer to know something about the limitations of the materials they work with.

Why don’t we expect this of digital designers?

Re:The unreasonable effectiveness of simple HTML by ogre_codes on Wednesday January 27, 2021 @10:43PM (#25937875)
Interior designers know their limits too. For example a good one won't try to move walls without consulting an engineer.

I think that's somewhat like what the relationship between designers and developers should be.

Re:The unreasonable effectiveness of simple HTML by zepto on Thursday January 28, 2021 @11:14AM (#25944157)
Perhaps so - but not understanding styling options for a component seems like the wrong limit.
Re:The unreasonable effectiveness of simple HTML by kortilla on Wednesday January 27, 2021 @02:33PM (#25932768)
If the site looks correct visually, the designer has actually completed their job. You’ll find that very few businesses care how a page is implemented and happily pay for shit html if it looks right.
Re:The unreasonable effectiveness of simple HTML by K0nserv on Wednesday January 27, 2021 @02:34PM (#25932798)
That might be the way many companies work, doesn’t mean it’s correct. Design is more than how things look, in fact how things look is secondary.
Re:The unreasonable effectiveness of simple HTML by kortilla on Wednesday January 27, 2021 @09:56PM (#25937577)
But that’s what a designer’s “job” is when they work for a company.
Re:The unreasonable effectiveness of simple HTML by berkes on Wednesday January 27, 2021 @03:39PM (#25933607)
This painfully reminds me of ages ago, pre-ie6 even, when we would get html-tables, spacergifs and whatnots, blurped out by ancient Dreamweaver, Paint Shop Pro slices and such.

It looked good. But hardly worked.

Apparently the web hasn't really changed in that part: we're still churning out HTML that hardly works, but "looks good".

Re:The unreasonable effectiveness of simple HTML by inopinatus on Wednesday January 27, 2021 @09:17PM (#25937281)
Ironically, it's because of the ARIA Authoring Practices guidelines[1], which include exactly this sort of nonsense[2].

[1] https://www.w3.org/TR/wai-aria-practices/

[2] https://www.w3.org/TR/wai-aria-practices/#examples

Re:The unreasonable effectiveness of simple HTML by ogre_codes on Wednesday January 27, 2021 @10:40PM (#25937846)
I was listening to a podcast and they were talking about using semantic HTML instead of piles of divs. One of the things they mentioned was that a survey of public web sites showed that the presence of ARIA in html was usually a sign that a site would have poor usability. Mostly because it's a sign that the site has abandoned standard HTML and went their own way and tried to patch things up by smearing aria properties everywhere.
Re:The unreasonable effectiveness of simple HTML by TheCoelacanth on Thursday January 28, 2021 @09:47AM (#25942487)
That seems like a misinterpretation of ARIA guidelines. I'm pretty sure the guidelines are meant as "if you are going to use a div as a button, do this", not "do this instead of using a button".
Re:The unreasonable effectiveness of simple HTML by inopinatus on Thursday January 28, 2021 @10:40AM (#25943530)
Quite so.
Re:The unreasonable effectiveness of simple HTML by recursive on Wednesday January 27, 2021 @01:23PM (#25931807)
My guess is that some learn react et al without ever really learning HTML first.
Re:The unreasonable effectiveness of simple HTML by pferde on Wednesday January 27, 2021 @03:40PM (#25933632)
That's entirely possible. I've seen a React tutorial that shows a simple example HTML snippet, and comments on it with "We’ll get to the funny XML-like tags soon."
Re:The unreasonable effectiveness of simple HTML by recursive on Wednesday January 27, 2021 @03:54PM (#25933785)
And then there's jsx, which is different from html in some important ways, and generally a little closer to xml.
Re:The unreasonable effectiveness of simple HTML by kodt on Wednesday January 27, 2021 @01:49PM (#25932174)
Perhaps because buttons have some default styles attached and people just decided to use a div.
Re:The unreasonable effectiveness of simple HTML by grishka on Wednesday January 27, 2021 @02:07PM (#25932424)
That's what a CSS reset is for.
Re:The unreasonable effectiveness of simple HTML by moring on Thursday January 28, 2021 @02:10AM (#25939075)
HTML buttons have special behaviour in CSS (not even styles, but differences in the rules how they work) that cannot be reset using a CSS reset. I actually tried to make a button fit into the reset of the UI until I gave up and used a div.
Re:The unreasonable effectiveness of simple HTML by FrontAid on Thursday January 28, 2021 @03:25AM (#25939524)
Like what? I can't think of any "special behaviour" that I would not want to have in a button and that cannot be changed by CSS.
Re:The unreasonable effectiveness of simple HTML by moring on Thursday January 28, 2021 @04:06AM (#25939804)
Vertical alignment.

"button are special element and their content is always vertically aligned by default. Even all the propertise are the same, if you don't center the text in the link, you won't get the same visual"

https://stackoverflow.com/questions/64766922/what-can-make-t...

Re:The unreasonable effectiveness of simple HTML by codazoda on Wednesday January 27, 2021 @02:50PM (#25933017)
> Very few people have the skill to turn a div into an effective button, yet over and over I see web sites with rows of buttons which are in fact just divs with javascript behind them.

I created a minimalist CSS framework called Neat CSS (https://neat.joeldare.com). I use anchors instead of buttons and explain why in the quote below. I'd love feedback on the accessibility of that alternative.

It's best to use semantic web tags whenever possible. Buttons are a unique case where you're typically linking somewhere, but the button tag doesn't currently support the href attribute. So, buttons are anchor tags with a class of button.

Re:The unreasonable effectiveness of simple HTML by ogre_codes on Wednesday January 27, 2021 @02:58PM (#25933116)
FWIW, I'm not an expert on this so take what I say with a grain of salt.

An anchor tag that links to another page but looks like a button is probably fine. So long as you can access them via the keyboard (tabbing to it) and they have a distinct appearance when focused so if you are tabbing through you can see whats active (this is different from the hover attribute).

Re:The unreasonable effectiveness of simple HTML by wizzwizz4 on Wednesday January 27, 2021 @02:52PM (#25933042)
Conceptually, those are links, not buttons. Buttons are for forms and JavaScript and such.
Re:The unreasonable effectiveness of simple HTML by codazoda on Wednesday January 27, 2021 @03:13PM (#25933314)
Fair. I would typically us a form tag with an input tag inside it for forms. Sounds like the button tag can be styled a little more because it allows i, em, br, img, and similar tags inside it, while an input does not. They are interchangable in the case of a form (based on your style need).
Re:The unreasonable effectiveness of simple HTML by petepete on Thursday January 28, 2021 @03:22AM (#25939505)
There are more ways to interact with a link than a button.

You can drag it to your tab bar, bookmarks or desktop, middle click to open in a new tab, copy the target URL etc.

With a button you can push it.

Re:The unreasonable effectiveness of simple HTML by reificator on Wednesday January 27, 2021 @02:24PM (#25932656)
While I agree with your message of "make things accessible" I think you're pointing the finger the wrong way.

> This is a fantastic article, it does miss one very key point about bog-standard HTML which is worth mentioning though.

> The standard widgets are all accessible, people with screen readers, limited mobility, poor vision, etc, all rely on pages being written so the devices they use to read the web can function properly. People who choose to eschew these standard components very frequently end up with a site which is unusable for disabled people.

> Very few people have the skill to turn a div into an effective button, yet over and over I see web sites with rows of buttons which are in fact just divs with javascript behind them.

Using a div as a button is not "bog-standard" HTML or a "standard component". Use a button and be done with it.

Using React or whatever does not prevent you from doing this, and in fact makes it less obvious to anyone doing a cursory review. I've not seen any difference overall in the amount of people knowingly using divs as buttons with plain HTML vs whatever framework, but I have seen an increase in unknowingly doing so by importing a calendar widget or similar without reviewing it.

Re:The unreasonable effectiveness of simple HTML by ogre_codes on Wednesday January 27, 2021 @02:42PM (#25932910)
> Using a div as a button is not "bog-standard" HTML or a "standard component". Use a button and be done with it.

Fully agree. In fact that is exactly point I was trying to make.

Re:The unreasonable effectiveness of simple HTML by madeofpalk on Wednesday January 27, 2021 @03:42PM (#25933655)
FWIW, using React or whatever makes it more obvious that you're making these mistakes because your event handlers are attached right on the "HTML" element. It makes it easy to spot because you see

    <div className="button" onClick={handler}>
and it immedaitely sticks out as a mistake. Because its easier to statically understand these mistakes, theres even tooling to automate detecting some of them as you type https://www.npmjs.com/package/eslint-plugin-jsx-a11y
Re:The unreasonable effectiveness of simple HTML by reificator on Wednesday January 27, 2021 @04:52PM (#25934508)
> FWIW, using React or whatever makes it more obvious that you're making these mistakes because your event handlers are attached right on the "HTML" element. It makes it easy to spot because you see

> <div className="button" onClick={handler}>

> and it immedaitely sticks out as a mistake. Because its easier to statically understand these mistakes, theres even tooling to automate detecting some of them as you type https://www.npmjs.com/package/eslint-plugin-jsx-a11y

I'm not sure how you got that out of

> I have seen an increase in unknowingly doing so by importing a calendar widget or similar without reviewing it.

I'm referring to:

    <div class="div-button" onclick="clickHandler()" />
VS:

    <SomeGreatNpmWidget onClick={clickHandler} />
The point of using components is so that you don't have to look under the covers to understand them at a high level, but that also means if you don't look you don't see how they're breaking accessibility.
Re:The unreasonable effectiveness of simple HTML by madeofpalk on Wednesday January 27, 2021 @06:19PM (#25935537)
Got it from the first part

> Using React or whatever does not prevent you from doing this, and in fact makes it less obvious to anyone doing a cursory review

Sure. From that level it might not be apparent, but within that component the mistake would be immediately obvious, on a cursory glance. Again, I don’t think React or whatever makes this less obvious.

But really, this just isn’t a problem I’ve seen in practice. Because of good tooling, and the ease of doing things the right way, I think the majority do it well. Those that don’t were going to fuck it up regardless of the framework or paradigm.

Re:The unreasonable effectiveness of simple HTML by Aeolun on Wednesday January 27, 2021 @05:13PM (#25934797)
Depends on how far you are linting it? If you lint your node_packages folder you may still catch these.
Re:The unreasonable effectiveness of simple HTML by ori_b on Wednesday January 27, 2021 @10:10PM (#25937667)
When was the last time you removed a dependency due to lint errors? How about your coworkers?
Re:The unreasonable effectiveness of simple HTML by Aeolun on Thursday January 28, 2021 @06:38PM (#25951120)
If my point was to have accessible code, then I think I would care about not using components that are inaccessible.
Re:The unreasonable effectiveness of simple HTML by ori_b on Saturday January 30, 2021 @12:48PM (#25971157)
Yes, it's certainly cheaper to ignore usability.
Re:The unreasonable effectiveness of simple HTML by benbristow on Wednesday January 27, 2021 @03:06PM (#25933210)
> Very few people have the skill to turn a div into an effective button, yet over and over I see web sites with rows of buttons which are in fact just divs with javascript behind them.

You can add role="button" and a modern browser will treat it just like a normal button and all the accessibility that comes with it.

Re:The unreasonable effectiveness of simple HTML by darekkay on Wednesday January 27, 2021 @04:08PM (#25933977)
I wish this would be the case. The button will not be focusable, so we need to add tabindex="0". A disabled div with role="button" is not handled as disabled, so we need to take care of that. Keyboard space/enter will not be triggered on "click" event, unlike real buttons, hence excluding keyboard users. You can check my playground [1] - I'm using it to demo why one should prefer native over custom components.

[1] https://darekkay.github.io/presentations/accessible-web/reso...

Re:The unreasonable effectiveness of simple HTML by vxNsr on Wednesday January 27, 2021 @04:27PM (#25934193)
That's kind of missing the point though, most bad browsers the author mentions don't do modern web very well. They're likely using an older renderer and are missing many features.
Re:The unreasonable effectiveness of simple HTML by GrumpyNl on Wednesday January 27, 2021 @04:05PM (#25933940)
its about simple html and older devices, so just plain button will do the job.
Re:The unreasonable effectiveness of simple HTML by pier25 on Wednesday January 27, 2021 @08:49PM (#25937066)
It would be great if browsers implemented other common elements such as sortable data tables, carousels, etc.

https://open-ui.org/

Re:The unreasonable effectiveness of simple HTML by deergomoo on Thursday January 28, 2021 @03:16AM (#25939466)
This is the issue. People (especially on HN) complain about people building un-semantic, inaccessible websites that don't work with JS disabled—and I agree this sucks—but HTML is so limited your only choice is to build the niceties yourself or skip them altogether. Sure, in some circumstances you can progressively enhance (sortable table for example), but many cases having a HTML fallback that still does what you need it to is a ton of extra work.

HTML covers text, painfully basic tables, semantic rectangles (<nav>, <aside>, etc.), form inputs, and embedded media. Basically, anything you could build with a word processor. Outside of that, you're on your own.

JavaScript and CSS are continually improving and are so much more capable than they were even five years ago, but it feels like HTML is just stagnating. Why can't we have new elements every year, with behaviour? Stuff that works just fine out of the box, but can be easily tweaked with CSS or a little sprinkling of JS. The amount of developer time and bandwidth we could save not having to re-invent the wheel for every little thing.

Re:The unreasonable effectiveness of simple HTML by gcblkjaidfj on Wednesday January 27, 2021 @08:59PM (#25937141)
You have a great point. Browser UI elements are stuck in time and all the attention now is directed to things that Google can make money from (e.g. DRM, sandbox for rich apps/extensions, webrtc for their video call products, etc)

but your cited site is not a good advocacy of that. Not even the most exalted UI framework fix the most obvious problems with those either. e.g. tables still won't hold the header and first column(s) while scrolling.

Most of the these elements does not help consuming information, like carousels. And any true UX designer abhor them all for the fallacy they are.

Re:The unreasonable effectiveness of simple HTML by kuschku on Thursday January 28, 2021 @04:52AM (#25940055)
> e.g. tables still won't hold the header and first column(s) while scrolling.

https://caniuse.com/css-sticky

position:sticky works on tables.

Re:The unreasonable effectiveness of simple HTML by gcblkjaidfj on Thursday January 28, 2021 @05:42PM (#25950559)
It's all red :( No support anywhere but Firefox. In fact, I will now use this URL as my main argument in support of firefox!

even the grand-parent, javascript infused solutions, only two out of 20 support this extremely basic and obvious use case.

Web UI standards are a joke. Everyone involved only cares about rich ads and accordions/carrousels which are lame ways to shove lots of content in a badly designed space.

Re:The unreasonable effectiveness of simple HTML by kuschku on Thursday January 28, 2021 @07:27PM (#25951757)
Why? The yellow/striped fields mean it's still supported (as long as you add it to th instead of thead/tr):
Re:The unreasonable effectiveness of simple HTML by pbronez on Wednesday January 27, 2021 @01:31PM (#25931925)
Are there any automated ways to assess a web product against the Web Content Accessibility Guidelines (WCAG)? This should really be part of the CI/CD process.
Re:The unreasonable effectiveness of simple HTML by ratww on Wednesday January 27, 2021 @01:41PM (#25932064)
There's a Firefox/Chrome extension called Axe that's pretty good. We use at my company it to make our products accessible and it helped us tremendously.

[1] https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/

[2] https://chrome.google.com/webstore/detail/axe-web-accessibil...

Re:The unreasonable effectiveness of simple HTML by bramd on Wednesday January 27, 2021 @02:15PM (#25932538)
The engine behind that add-on, Axe core, can be called from JS and there are some open source tools around to integrate it in your CI. I would say Axe is kind of the gold standard at this time when it comes to automated accessibility testing. Not because it catches the highest number of issues, but if it flags something you can be pretty sure it's a real issue and not a false positive.
Re:The unreasonable effectiveness of simple HTML by ahuth on Wednesday January 27, 2021 @03:33PM (#25933550)
Shameless plug: at work we created axe-storybook-testing [1], which can be used to run accessibility tests against Storybook stories [2] on CI.

1. https://github.com/chanzuckerberg/axe-storybook-testing 2. https://storybook.js.org/docs/react/get-started/whats-a-stor...

Re:The unreasonable effectiveness of simple HTML by Aeolun on Wednesday January 27, 2021 @05:53PM (#25935278)
Oh, this sounds interesting. I’ll have a look.
Re:The unreasonable effectiveness of simple HTML by tingletech on Wednesday January 27, 2021 @01:44PM (#25932101)
our web team wanted this in the CI/CD https://allyjs.io

edit: actually it's spelled https://pa11y.org

Re:The unreasonable effectiveness of simple HTML by cptskippy on Wednesday January 27, 2021 @01:51PM (#25932205)
Yes, there are a lot of tools. None are great and are mostly for compliance.

Products like Siteimprove are targeted at Enterprise (e.g. demos with sales weasels, unpublished pricing, etc). They mostly suck but check an auditing and compliance box.

Re:The unreasonable effectiveness of simple HTML by hanniabu on Wednesday January 27, 2021 @02:12PM (#25932493)
Would be nice to have an html builder that follows all these best practices. That would also make it nice and easy to apply different crowdsourced themes.
Re:The unreasonable effectiveness of simple HTML by 908B64B197 on Wednesday January 27, 2021 @06:23PM (#25935577)
That was the original idea behind HTML.

It might not get rendered the same everywhere depending on the device receiving it.

If the goal was to send pixel perfect pages, the web would have settled on postscript + hyperlinks.

Re:The unreasonable effectiveness of simple HTML by arcturus17 on Wednesday January 27, 2021 @01:09PM (#25931594)
> Making your site accessible isn't just a good practice, in the US, it is the law

> Courts have rules that the ADA applies to web sites along with any other type of business

For a business like a coffee shop I'd imagine that accessibility is codified in law through things like building regulations (ie, you must have n disabled parking spots per square foot, a disabled toilet, etc)

Is there an equivalent legally codified and enforceable standard for the web?

Re:The unreasonable effectiveness of simple HTML by ogre_codes on Wednesday January 27, 2021 @01:21PM (#25931767)
> Is there an equivalent legally codified and enforceable standard for the web?

More or less yes. The link I posted has a few good resources, but generally speaking sites need to work with a screen reader and they need to be accessible via the keyboard (which by extension enables other accessibility devices).

This site has some more guidelines. https://www.essentialaccessibility.com/blog/ada-guidelines

Generally speaking, if you start with existing components that do the thing you want done, you have a huge leg up. If you try to reinvent the wheel, you are likely in for a lot of trouble. The more complex the control, the harder it is to roll your own. Calendar controls and Selects are particularly tough to get right.

UPDATE: Also, the wc3 has some good guidelines which should cover your ass.

https://www.w3.org/TR/WCAG21/

Re:The unreasonable effectiveness of simple HTML by udia on Wednesday January 27, 2021 @01:20PM (#25931761)
I have had a lot of success with this course (Web Accessibility, by Google): https://www.udacity.com/course/web-accessibility--ud891

> In this course you’ll get hands-on experience making web applications accessible. You’ll understand when and why users need accessibility. Then you’ll dive into the "how": making a page work properly with screen readers, and managing input focus (e.g. the highlight you see when tabbing through a form.) You’ll understand what "semantics" and "semantic markup" mean for web pages and add ARIA markup to enable navigating the interface with a range of assistive devices. Finally, you’ll learn styling techniques that help users with partial vision navigate your pages easily and reliably.

Re:The unreasonable effectiveness of simple HTML by rstupek on Wednesday January 27, 2021 @01:19PM (#25931737)
There is not a codified standard however that doesn't stop websites from being sued
Re:The unreasonable effectiveness of simple HTML by ogre_codes on Wednesday January 27, 2021 @01:27PM (#25931850)
If you comply with the WCAG 2.1, you have a pretty good legal defense. While it isn't "Law", it is the most widely known published standard and likely to be added to the law soon.

https://www.w3.org/TR/WCAG21/

Re:The unreasonable effectiveness of simple HTML by trissylegs on Thursday January 28, 2021 @12:14AM (#25938476)
> Very few people have the skill to turn a div into an effective button, yet over and over I see web sites with rows of buttons which are in fact just divs with javascript behind them.

Gahhh. I use either an <a> or a <button> and put style on it. Has all the same visual appeal of the equivalent div. But it already is a button.

Re:The unreasonable effectiveness of simple HTML by DCoder on Thursday January 28, 2021 @12:59AM (#25938741)
> use either an <a> or a <button>

Generally, it should be noted that an <a> tag is only appropriate if it makes sense to right-click this element and get options to "open in new tab" or "add to bookmarks". All the stupid "buttons" implemented as <a href="#"> + e.preventDefault() need to die.

Re:The unreasonable effectiveness of simple HTML by trissylegs on Sunday January 31, 2021 @10:39PM (#25985276)
Yea I use <a> if it's a navigation button for react-router. But it still shows up like a URL because we're using the Browser history (it just updates the URL and renders the new page, each route has a URL and resource id's are in the url). As opening the URL directly should work (if authenticated) it makes sense to use <a> tags.
Re:The unreasonable effectiveness of simple HTML by analog31 on Wednesday January 27, 2021 @11:58PM (#25938390)
I remember learning about HTML for the first time, maybe in Byte Magazine. It was before I actually had a computer with a browser. But the article talked about a benefit of HTML, which was that the tags could be interpreted by custom browsers for accessibility, including for the blind or sight-impaired. It seemed like a pretty cool idea to me.

Later on, when people started treating web design as a general purpose graphical and GUI framework, many of the accessibility benefits probably vanished.

Re:The unreasonable effectiveness of simple HTML by DCoder on Thursday January 28, 2021 @01:35AM (#25938908)
Yeah, nowadays most of the sites are suffering from div-ititis that has no semantics, massive blackholes of JavaScript that have to be loaded and processed before you can even see plain text, and CSS class names that are randomly hashed with each deployment in the name of modularity.

General accessibility be damned.

<noscript> fallback messages be damned. (Except when snitching on your page views to Google Analytics, that's too important to be neglected! I wonder if GA has any default marker to let their customers distinguish these views from normal ones, or if that's still left to each customer to implement manually.)

UI customizations in the form of browser extensions and styles be damned.

Ad blocking be damned.

Re:The unreasonable effectiveness of simple HTML by rkangel on Thursday January 28, 2021 @09:15AM (#25941999)
Designing for people with disabilities usually increases the overall UX for everyone. I see it a bit like resistance training for fitness - you train in a 'more difficult than normal' scenario, and then when you return to normal it feels much easier.