Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

From SVG to Canvas – A new way of building interactions

felt.com

Post reply on HN
Print view View original

51–60 of 97 posts

Re: From SVG to Canvas – A new way of building interactions

#51

Post by layer8 »

rikroots wrote: post #45
simlevesque wrote: post #17

ctrl+f "accessibility" in part 2: zero results ctrl+f "accessibility" in part 1: zero results Does anyone care about digital access to content for disabled people ? Or about the ADA ? Svg to canvas without any answer for accessibility is backwardness, plain and simple. You are letting down anyone who's deaf, blind or has trouble hearing or seeing, anyone who does not know how to read, has motor impairments, temporary…

I've never used the product, but I did see this snippet in the article, which gives me a flicker of hope that the product does address some accessibility concerns: > One particularly nice aspect of this system is that key presses follow the same flow as pointer events, which is not how things work in the DOM. In the DOM, you usually bind key handlers globally, and pointer events per element. But here, we get all the…

The quote doesn’t seem particularly related to accessibility. Having keyboard shortcuts doesn’t by itself imply accessibility.

Re: From SVG to Canvas – A new way of building interactions

#52

Post by layer8 »

vbezhenar wrote: post #38
simlevesque wrote: post #17

ctrl+f "accessibility" in part 2: zero results ctrl+f "accessibility" in part 1: zero results Does anyone care about digital access to content for disabled people ? Or about the ADA ? Svg to canvas without any answer for accessibility is backwardness, plain and simple. You are letting down anyone who's deaf, blind or has trouble hearing or seeing, anyone who does not know how to read, has motor impairments, temporary…

Unless they have a legal requirement to provide product for disabled people, why would they care? It's a huge investment for very little output, unless this product is specifically targeted.

Accessibility helps everyone, not just disabled people.

Re: From SVG to Canvas – A new way of building interactions

#53

Post by mhoad »

tadfisher wrote: post #28
simlevesque wrote: post #17

ctrl+f "accessibility" in part 2: zero results ctrl+f "accessibility" in part 1: zero results Does anyone care about digital access to content for disabled people ? Or about the ADA ? Svg to canvas without any answer for accessibility is backwardness, plain and simple. You are letting down anyone who's deaf, blind or has trouble hearing or seeing, anyone who does not know how to read, has motor impairments, temporary…

Genuinely asking, how do you make something like their map view accessible with so many objects and layers? I'd imagine you end up with a solution that exposes various content rectangles and ignores everything else, kind of how Google Maps does it.

This is a problem that turns up in Flutter when they compile for the web.

The long term answer is the Accessibility Object Model spec currently under development.

The current answer is to build a replica DOM structure for accessibility purposes.

Re: From SVG to Canvas – A new way of building interactions

#54

Post by bryanrasmussen »

marcus_holmes wrote: post #9

> These InteractionHandlers are just objects satisfying a specific TypeScript interface. They’re not coupled to React or hooks or anything like that, which feels quite freeing, honestly. There’s no worrying about stale closures or dependencies or hooks rules - it really is just TypeScript. This is a great example of "fighting the framework". React + SVG got them from nothing to a working product. But then they had to…

>And the more the framework does, the earlier the fight begins.

assuming that the more the framework does also means the less the framework allows you to do yourself. which is a pretty reasonable assumption of course.

Re: From SVG to Canvas – A new way of building interactions

#55

Post by bryanrasmussen »

vbezhenar wrote: post #38
simlevesque wrote: post #17

ctrl+f "accessibility" in part 2: zero results ctrl+f "accessibility" in part 1: zero results Does anyone care about digital access to content for disabled people ? Or about the ADA ? Svg to canvas without any answer for accessibility is backwardness, plain and simple. You are letting down anyone who's deaf, blind or has trouble hearing or seeing, anyone who does not know how to read, has motor impairments, temporary…

Unless they have a legal requirement to provide product for disabled people, why would they care? It's a huge investment for very little output, unless this product is specifically targeted.

This attitude is why sooner or later everyone ends up with legal requirements for disabled people.

Re: From SVG to Canvas – A new way of building interactions

#56

Post by mkl »

paulddraper wrote: post #29
thomasfromcdnjs wrote: post #4

I've built diagram like tools several times, constantly umming and ahing between Canvas and SVG. SVG seems to get you pretty far, but I always end up with Canvas in the long run. Fun fact: Google docs is actually a canvas.

You start with SVG Then you go to Canvas Then you go to WebGL Source: Early engineer at Lucidchart

Then you go to WebGPU, I expect.

Re: From SVG to Canvas – A new way of building interactions

#58

Post by [deleted] »

johncoltrane wrote: post #35
simlevesque wrote: post #17

ctrl+f "accessibility" in part 2: zero results ctrl+f "accessibility" in part 1: zero results Does anyone care about digital access to content for disabled people ? Or about the ADA ? Svg to canvas without any answer for accessibility is backwardness, plain and simple. You are letting down anyone who's deaf, blind or has trouble hearing or seeing, anyone who does not know how to read, has motor impairments, temporary…

[flagged]

[deleted]

Re: From SVG to Canvas – A new way of building interactions

#59

Post by ygra »

tadfisher wrote: post #28
simlevesque wrote: post #17

ctrl+f "accessibility" in part 2: zero results ctrl+f "accessibility" in part 1: zero results Does anyone care about digital access to content for disabled people ? Or about the ADA ? Svg to canvas without any answer for accessibility is backwardness, plain and simple. You are letting down anyone who's deaf, blind or has trouble hearing or seeing, anyone who does not know how to read, has motor impairments, temporary…

Genuinely asking, how do you make something like their map view accessible with so many objects and layers? I'd imagine you end up with a solution that exposes various content rectangles and ignores everything else, kind of how Google Maps does it.

Not all of accessibility is for those who cannot see (well). WCAG also has a bunch of guidelines for loss of dexterity and other ailments:

• keyboard support (being able to navigate to all controls as needed, not being stuck in a navigation island from which there is no escape with the keyboard, etc.)

• pointing device considerations (not requiring drag unless absolutely essential, no action on mouse-down, etc.)

• not requiring the simultaneous use of mouse and keyboard (e.g. via modifier keys)

• sufficient size for buttons and other pointer targets

• the ability to suppress animations, flashing images, etc.

• the ability to control colors and contrast of things on the screen

...

Of course, something like Photoshop, Illustrator, or the visual part of Google Maps is hard to use when you cannot see, but there are so many different disabilities that some or even most accessibility guidelines can apply to pretty much any software.

Re: From SVG to Canvas – A new way of building interactions

#60

Post by ygra »

paulddraper wrote: post #29
thomasfromcdnjs wrote: post #4

I've built diagram like tools several times, constantly umming and ahing between Canvas and SVG. SVG seems to get you pretty far, but I always end up with Canvas in the long run. Fun fact: Google docs is actually a canvas.

You start with SVG Then you go to Canvas Then you go to WebGL Source: Early engineer at Lucidchart

Similar journey here (yWorks, with a diagramming library, too). In our case the journey comes with drawbacks, though. Yes, WebGL allows for larger graphs, but it also does not support the flexibility (to customers) the other options offer.
Post reply on HN