Earlier this week, I wrote about how I’m building a UI library for people who love HTML. I also published a YouTube video about it. I got a lot of excited responses and comments about it, but also a noteworthy handful asking something along the lines of this… People should not be prioritizing no-JS users. No one turns off JavaScript. Today, I wanted to talk about why that’s wrong, and why you should care about the no-JS experience.
  • masterspace@lemmy.caEnglish
    41·
    8 hours ago

    This is both factually incorrect, and ignores the original point.

    First of all, no you cannot just run an automatic WAI ARIA checker. That will highlight some surface level basic structural issues but in no way is adequate testing for a pleasant accessible UX.

    Secondly, modern frameworks like React and Angular have the same ARIA validation utilities. It does not matter whether components are loaded in dynamically by the framework as long as they’re defined in the codebase where linters and code analyzers can run.

    Thirdly, you’re ignoring the actual point that is being made. You know as well as I do, that virtually nowhere actually puts serious effort and usability testing into websites making sure their websites are accessible, and that directly impacts the lives of millions of people who are cut off from the world of technology because of a disability.

    Until you’re making all of your websites and apps accessible by second nature (i.e. until at a bare minimum you have your Web Accessibility Specialist certification), then focusing your time and efforts on catering to a niche ideological no JS crowd is quite frankly somewhat cruel and self serving.