Too narrow, hidden, minimal feedback…

  • Windex007@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    for whatever reason

    Flashy sleek shit gets invested in.

    Outside of business specifically oriented towards people with accessibility issues, the energy just doesn’t translate into VC.

    Companies who do try to shoehorn it in when products are more mature usually have:

    1. A codebase with a frustrating amount of refactoring in order to retroactively get things in line.

    2. Development inertia where it’s seen as a low value activity among developers and product owners

    3. Lack of clear guidance/tools/processes to QA new work

    4. Lack of will to retroactively identify the breadth and scope of changes you even want to make

    There is no mystery. It’s not going to get you sexy VC money at the beginning, and then it’s bizarrely more work than you’d think once your project is sufficiently large.

    • Alatain@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      That doesn’t explain why already established products are ditching things like plainly visible scroll bars in products like Microsoft word and other content viewers.

    • Emerald@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 months ago

      This. And it doesn’t only apply to companies. I have a personal blog with a couple accessibility issues that I haven’t bothered to fix because I’ve built a lot of my CSS around my bad HTML. Part of the issue is that I built my site as a school project for a web design class I was taking, so code quality wasn’t great. One day I might redesign it better, but I don’t have the energy for now.