• 0 Posts
  • 45 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle












  • JS has little to do with accessibility. Most web accessibility comes from the Dom and aria attributes as well as semantic tags. You can do all of that with wasm too.

    Are you asking about how it will work with wgpu based applications? This will work the same as it does on desktop applications. The program calls out to libraries that support talking to screen readers. I know rust the language with the best support for and ecosystem around wasm libraries like this already exist and ui frameworks like egui already have some support built in.





  • Ugh word does this. I didn’t realize until I wrote some documentation for a cli tool I made for a client and I wrote the documentation in word because they are fairly non technical so I wrote in the documentation sample arguments they can copy and paste and shipped it feeling good that it would work flawlessly because I tested the crap out of it. Or so I thought because they immediately hit back with it doesn’t work. I spent hours recreating their environment and watching it work no matter what I tried to get it to not work. Then I hopped on a call and had the client step by step show me what they did and they opened the word doc and copied the example commands, changed the arguments to be correct and run it. I followed along on my own machine and then I fucking saw what had happened. Fucking Microsoft Word replaced my " " with “ ” (straight quotes for smart quotes for those who cant see the difference). A quick patch of the cli to properly parse those and things were working again.