Yeah, I'm not really sure how to feel about the way they plan to handle it.
"Happy it exists at all" resonates. Most accessibility users find something inaccessible, sigh, and move on. Most of the time there is nothing we can do, and most of the time the complaint platform itself is inaccessible. We're taught not to complain.
But... The idea of a NO_GRAPHICS env var? I don't particularly like that. Its a hidden, unstandardised, global. To discover it exists, I have to first use the software in its inaccessible form - where I'd find it inaccessible, sigh, and move onto something else.
Again, the problem is discovery - if this is an optout, and the system that tells you is the same thing that you need to change to be able to use it in the first place, the audience just feels the usual crush and moves on.
Comments
While this is using ariadne for rendering, for annotate-snippets (the renderer for rustc) there is active work for a screen reader mode. This is being tracked at https://github.com/rust-lang/annotate-snippets-rs/issues/351
Yeah, I'm not really sure how to feel about the way they plan to handle it.
"Happy it exists at all" resonates. Most accessibility users find something inaccessible, sigh, and move on. Most of the time there is nothing we can do, and most of the time the complaint platform itself is inaccessible. We're taught not to complain.
But... The idea of a NO_GRAPHICS env var? I don't particularly like that. Its a hidden, unstandardised, global. To discover it exists, I have to first use the software in its inaccessible form - where I'd find it inaccessible, sigh, and move onto something else.
Most of these global env vars started somewhere.
That said, at least for cargo, there will also be a `term` config field for it.
Again, the problem is discovery - if this is an optout, and the system that tells you is the same thing that you need to change to be able to use it in the first place, the audience just feels the usual crush and moves on.