Avoid aria tags. The spec is unworkable (see this document) the browsers made by the disability industry extract vast quantities of money from disabled people with little effectiveness because they try and boil the ocean which unsurprisingly is ineffective.

Support efforts for computer vision based browsers, MCP and APIs.

▲

jraph 4 hours ago | parent | next [-]

> MCP

Respectfully screw making users rely on AI for accessibility. Just make the damn page accessible already. Actually, more like make sure you don't break the accessibility that's there by default with correctly written plain HTML.

▲

nailer an hour ago | parent [-]

> Respectfully screw making users rely on AI for accessibility.

Why? It's the right tool for the job.

> Just make the damn page accessible already.

Oh so just modify every website and expect the disabled people to wait while this happens?

This disabled web browser industry doesn't care about disabled people. Their solutions don't work, disabled browsers are expensive because government grants are given to purchase them.

▲

jakelazaroff 43 minutes ago | parent | next [-]

> Why? It's the right tool for the job.

No, it's not. Why should disabled users be forced to indirectly interact with a webpage via a non-deterministic agent, rather than directly interact with one that's specifically designed to accommodate them?

	▲	nailer 32 minutes ago \| parent [-]
		> rather than directly interact with one that's specifically designed to accommodate them? Because a world where that happens consistently doesn't exist, it hasn't existed for the last 20 years we've been using ARIA tags, and won't ever exist.

▲

jraph 40 minutes ago | parent | prev [-]

For a user running into broken pages, sure, you have to compose with what you have.

As a developer, however, get your shit fixed! And that fixing doesn't involve any MCP. Don't expect visitors to run AI...

▲

RobMurray 2 hours ago | parent | prev | next [-]

To hell with using vision based AI for web accessibility. it really isn't that hard to get right. Semantic html is already accessible. ARIA can help when devs want to use the wrong elements for some reason or for custom controls.

▲

nailer an hour ago | parent [-]

> it really isn't that hard to get right.

Yes you just need every website to use it, rather than fixing the client. Which is the 'boil the ocean' strategy mentioned in the comment you're replying to.

> ARIA can help when devs want to use the wrong elements for some reason or for custom controls.

But it can't. See this article.

	▲	RobMurray 3 minutes ago \| parent \| next [-]
		I did read the article. Why do you need to label a div? It's just a container, not a semantic element. If you really want to use a div for something semantic you can set role and aria-label. That is done all the time and works with screen readers.
	▲	rhdunn 6 minutes ago \| parent \| prev [-]
		See https://www.w3.org/WAI/ARIA/apg/patterns/ for a guide on how to create accessible markup for custom controls and the associated examples. See specifically https://www.w3.org/WAI/ARIA/apg/practices/names-and-descript... for details on naming. That has extensive notes and details for labeling elements correctly. See https://getbootstrap.com/docs/5.0/components/ for bootstrap markup on creating accessible components. There are plenty of other resources.

▲

ramblurr 5 hours ago | parent | prev [-]

What document?

Do you have any sources to back these claims up?

	▲	nailer an hour ago \| parent [-]
		> What document? https://news.ycombinator.com/item?id=48237159 > Do you have any sources to back these claims up? Yes, asides from the article, check the prices of browsers from the disability industry and consider for yourself whether it's logically easier to fix every website or make a client that can adapt existing webpages.