How well do screen readers parse other compiler errors?
This isn’t me trying to be snarky, I actually have no idea! Reading a C++ template error is hard enough as a sighted person
This isn’t me trying to be snarky, I actually have no idea! Reading a C++ template error is hard enough as a sighted person
You can see an example of the output here: https://godbolt.org/z/aan6Kfxds (that's the first example from the article, with -fdiagnostics-format=sarif-stderr added to the command-line options)
That doesn't cover the diagrams though (which I currently serialize in SARIF form by making a placeholder Markdown text containing "code" containing the diagram).
I experimented with SVG output for the diagrams, but didn't get this in good enough shape for GCC 14.
I've got a few ideas for more general UX improvements with how we do diagnostics, which I'll try in GCC 15 once we're finished focusing on GCC 14 bugfixing.
An advice to anyone out there making software: give a screen reader a whirl! Take it as a learning experience!
I like to ask this question on posts about new libraries or developer tools, because most developers don't consider the accessibility of the features they're building.