Mostly marketing and informational websites for the public. Businesses, tourism spots, local charities and nonprofits, etc. Nothing that’s going to change the world but hopefully makes somebody’s day a little easier when they need to look something up.
It doesn’t have to not include JavaScript, that would be quite difficult and unreasonable. Accessible sites are not about limiting functionality but providing the same functionality.
I haven’t gone fully down the rabbit hole on this but my understanding is even something like Nuxt if you follow best practices will deliver HTML that can be interacted with and serve individual pages.
That said, screen readers and other support shouldn’t require running without any JavaScript. Having used them to test sites that might be the smart approach but they actually have a lot of tools for announcing dynamic website changes that are built into ARIA properties at the HTML level so very flexible. There are of course also JavaScript APIs for announcing changes.
They just require additional effort and forethought to implement and can be buggy if you do really weird things.
I think we’re on the same page here. Your reply seems to me to argue against the people who are completely against JavaScript and who treat its very presence like a complete site-breaking bug. I am not of their opinion either. But I do sympathize with the sentiment that it is being used for evil.
That’s excellent.
And what do you make that doesn’t include JavaScript? Like what kind of software/website/content? If you don’t mind sharing, of course.
Mostly marketing and informational websites for the public. Businesses, tourism spots, local charities and nonprofits, etc. Nothing that’s going to change the world but hopefully makes somebody’s day a little easier when they need to look something up.
Good stuff!
It doesn’t have to not include JavaScript, that would be quite difficult and unreasonable. Accessible sites are not about limiting functionality but providing the same functionality.
I haven’t gone fully down the rabbit hole on this but my understanding is even something like Nuxt if you follow best practices will deliver HTML that can be interacted with and serve individual pages.
That said, screen readers and other support shouldn’t require running without any JavaScript. Having used them to test sites that might be the smart approach but they actually have a lot of tools for announcing dynamic website changes that are built into ARIA properties at the HTML level so very flexible. There are of course also JavaScript APIs for announcing changes.
They just require additional effort and forethought to implement and can be buggy if you do really weird things.
I think we’re on the same page here. Your reply seems to me to argue against the people who are completely against JavaScript and who treat its very presence like a complete site-breaking bug. I am not of their opinion either. But I do sympathize with the sentiment that it is being used for evil.
Yeah, I don’t think that’s what the screenshot shows though since there’s no content at all 😅
Not even a noscript tag at all or anything, yeah. Very bad.