Note by @fastfinge

@ander_dapo It depends on my settings. I can have it skip all emoji, read them, skip if there are more than three, etc. The problem with government right now is that the closed source big tech products generally include enough absolute minimum accessibility to comply with the law, and the open source products do not. So if you’re a sales person for big tech, you have a huge advantage. You can bully government into buying your product, because it’s the only way they can avoid a lawsuit. So it’s a chicken and egg problem: governments don’t use open source tech because it’s not accessible, and it’s not accessible because governments don’t use it. I think the only way out of this is to get government to adopt open formats, open API’s, and open data. Then one employee could use the accessible solution, and the other could use the inaccessible open source solution. And everything would be compatible. And of course, governments won’t want to buy two software packages that do the same thing, so they’ll then start funding open source accessibility. Europe is slowly making progress in this way with Office products. First, they required Microsoft to fully support the ODF, Open Document FOrmat. Then, they started moving to LibreOffice, but employees who couldn’t work with it could stick with Microsoft Offfice and just save as ODF. Then LibreOffice started having more and more accessibility features. Now, slowly, blind folks are starting to begin dipping our toes into LibreOffice. Right now, complex features like track changes are still more accessible in Microsoft Word, so blind users can still go back to Word for complicated requirements. But for simpler documents, LibreOffice is fine these days. And we can test it out without giving up word entirely, so we’ll know when it becomes good enough.