Great to know there are frameworks like this that don't push the whole app on my browser, potentially crashing it. I posted a rant about the same topic some time ago.
I think that Hey might be pushing it a little too far though. Lots of accessibility issues, and while some of them can be fixed easily, fixing the rest without adding a sprinkle of JS will be impossible without the platform giving us a better higher level widgets to work with.
, curious about what kind of accessibility issues the Hey approach would introduce? Normally, accessibility should be more related to html not JS right?
True. However, I think it's a good sign that we're atleast putting some effort in this direction to solve the js bloat problem which is another big accessibility issue. I hope to see frameworks like these mature and become more capable.
Hi, can you be more specific about the accessibility issues and how more JS would solve them?
Oh, I just read this thread that explains it well, interesting, thanks! twitter.com/devongovett/status/127...
I still think these issues should be solved in the HTML standards so that good accessibility is not dependant on JS.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.