Comment by gostsamo

4 days ago

so glad about the accessibility part. it is a struggle sometimes. also, as far as both chrome and ff converged on the same accessibility architecture, I hope that the project will be using it from the very start and will have tangible results soon.

6 comments

gostsamo

Reply
Muromec  4 days ago

It's mandated by law nowdays, so they just have to mention it (and do it) to tick all the boxes, especially if they take grants from EU.

  • gostsamo  4 days ago

    I don't know why it matters to you, but if the end product is accessible, I don't care if it is an EU directive or a german one. Keeping in mind where the team are coming from, there is a high chance that the implementation won't be checking boxes for grand reasons only.

    • Muromec  4 days ago

      I most certainly welcome laws like this, partly because I work in a place, where compliance always wins, and a11y being part of compliance makes it more of real requirement and less of "nice to have".

      That being said, I saw two approaches to this -- negative, when people get some kind of a tool and change things until the tool stops showing warning and positive, where accessibility is another part of UX and has to be designed with positive checks on what actually works.

      I sincerely hope that the team behind it is doing it the second way, but I'm not in their heads and don't know whether this text war written as part of government relations to get the moneys or they actually believe it. It's customary to praise Communist party, God allmighty without meaning any of it in some places too.