Hacker News Reader

Comment by shakna | Hacker News Reader

As far as standards is concerned, that API is ARIA [0].

W3C already offers guides for accessibility and canvas. But no one who opts for canvas turns around and remembers to do their landmarks.

View on HN

> But no one who opts for canvas turns around and remembers to do their landmarks.

Not completely true. Flutter has been adding some accessibility for web canvas target. [1]

I think Avalonia is in in the make it work phase. Accessibility will probably be added in the make it right phase.

[1] https://docs.flutter.dev/ui/accessibility/web-accessibility

Then I’m showing my ignorance… how do you add ARIA landmarks to Canvas elements?

You would create transparent DOM elements in the right places with the right ARIA attributes and content, I suspect.

I guess that’s what I’d like to see a better API for, then. Mapping on click events for invisible elements feels like a hack.

It's HTML imagemaps from the 90s, when we could not style buttons and navbars where GIFs with links in the right places. Browsers still have the code to render them.

https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/...

https://caniuse.com/mdn-html_elements_map

OTH, we are still failing to provide a bare minimum for accessibility. Heck, we even needed a law (in the EU, that than needed to be translated to national law), so that companies providing crucial end user services would care about accessibility.

That's possible. But it is difficult to get right, and can have poor performance if you you have many such elements.

Reply on news.ycombinator.com