furthermore if javascript breaks and no one notices—maybe just delete the javascript
11 replies
@zachleat I think it would be interesting if we forced developers to develop the site without JavaScript if they use frameworks with SSR. In my experience, CSR does make websites feel nice to use. It's a balance I guess.
Im considering modifying https://github.com/fireship-io/flamethrower for my 11ty site@eb ah hmm—what’s the accessibility story of that component?
@zachleat of flamethrower? I doubt there's any. It just hijacks standard links, fetches the body of the page they point to, and hotswaps that in. This should be good for performance because
1. Progressive Enhancement
2. On each click, the browser no longer needs to parse and rerun JavaScript, fonts, and styles@eb sure, yeah—but does it announce page changes to screen readers? That’s the #1 accessibility issue with SPA—each plugin has had to solve this problem independently afaik
@eb I only ask because I don’t see it mentioned on the readme or in the issue tracker
@zachleat that's an interesting point. Two questions I have:
1. This issue must have been solved in the accessibility tools by this point? Like half the web is SPAified, not to mention the other terrible practices
2. Is there some way a router *could* help screen readers out?@eb to the second point: yeah, for sure. I do think it is a “solved” problem but it doesn’t seem to be solved by this component.
to the first point: I don’t think so 😅
@zachleat Oh! How could I modify the component to address this issue? Do you have any resources?
@eb I know Marcy Sutton Todd did some great work on Gatsby’s implementation awhile back, I think there are a few resources, maybe here https://www.gatsbyjs.com/contributors/marcy-sutton or on her web site?