4 ms·

> a fully native framework that eschews the DOM by compiling directly onto a canvas Wouldn't that essentially be the death of accessibility on the web, though?

by olah_1 7y ago

adev_ 7y ago
> Wouldn't that essentially be the death of accessibility on the web, though? It does. And would condemn us to live again usability nightmare of the flash epoch. People are confusing two things here: There is no need of replacing the DOM. There is a need to replace (modernize) the API controling the DOM.
satvikpendem 7y ago
I see this concern a lot with Flutter or similar WASM -> canvas frameworks, and I think it's unfounded. Just because it's a canvas doesn't mean there's no accessibility. Indeed, even desktop apps are canvas like in that one cannot view the source and they can render using similar frameworks like Skia, or even Skia itself, yet they still have accessibility. Flutter's developers have specifically included accessibility settings that devs should use, such as Semantics widgets, just like aria labels for the web. Flutter also constructs a separate semantic DOM like tree that screen readers hook into. So there are both built in things and things that devs can use to make their projects more accessible. This video shows more about it: https://www.youtube.com/watch?v=bWbBgbmAdQs https://www.youtube.com/watch?v=bWbBgbmAdQs https://flutter.dev/docs/development/accessibility-and-localization/accessibility https://flutter.dev/docs/development/accessibility-and-local... https://api.flutter.dev/flutter/widgets/Semantics-class.html https://api.flutter.dev/flutter/widgets/Semantics-class.html
- olah_1 7y ago
  My comment was less about possibility and more about willingness. But it looks like many are taking accessibility as a first-class concern, which is great to see.
- deleted 7y ago
  [deleted]

4 ms·

> a fully native framework that eschews the DOM by compiling directly onto a canvas Wouldn't that essentially be the death of accessibility on the web, though?

by olah_1 7y ago

> a fully native framework that eschews the DOM by compiling directly onto a canvas Wouldn't that essentially be the death of accessibility on the web, though?

adev_ 7y ago
> Wouldn't that essentially be the death of accessibility on the web, though? It does. And would condemn us to live again usability nightmare of the flash epoch. People are confusing two things here: There is no need of replacing the DOM. There is a need to replace (modernize) the API controling the DOM.
satvikpendem 7y ago
I see this concern a lot with Flutter or similar WASM -> canvas frameworks, and I think it's unfounded. Just because it's a canvas doesn't mean there's no accessibility. Indeed, even desktop apps are canvas like in that one cannot view the source and they can render using similar frameworks like Skia, or even Skia itself, yet they still have accessibility. Flutter's developers have specifically included accessibility settings that devs should use, such as Semantics widgets, just like aria labels for the web. Flutter also constructs a separate semantic DOM like tree that screen readers hook into. So there are both built in things and things that devs can use to make their projects more accessible. This video shows more about it: https://www.youtube.com/watch?v=bWbBgbmAdQs https://www.youtube.com/watch?v=bWbBgbmAdQs https://flutter.dev/docs/development/accessibility-and-localization/accessibility https://flutter.dev/docs/development/accessibility-and-local... https://api.flutter.dev/flutter/widgets/Semantics-class.html https://api.flutter.dev/flutter/widgets/Semantics-class.html
- olah_1 7y ago
  My comment was less about possibility and more about willingness. But it looks like many are taking accessibility as a first-class concern, which is great to see.
- deleted 7y ago
  [deleted]