Ethin Probst
Ethin Probst
I mean they aren't rendered as, e.g., a table.
@wmat The benefit would be that people with screen readers, like myself, would be able to understand the tables. As it currently stands, the figures just say "graphic diagram" when...
An alternative would be to include the SVG directly without base64-encoding it and to instead include accessible SVG attributes.
You can find more info about accessible SVGs [here](https://css-tricks.com/accessible-svgs), but in general a table is better and makes interpreting the data much simpler.
@nick-knight SVGs have accessibility things that WaveDrom could implement as well, including ARIA support. The problem is that to use ARIA properly, one must implement the behaviors that an ARIA...
Okay, so I have an update on this. To my surprise, AI's image descriptions (at least chatGPT's) are actually quite useful in hacking around this issue. Obviously, this is not...
> I think that's one of the main issues with supporting #![no_std]. It means that the project can never, EVER, rely on the standard library. That's a pretty severe limitation...
Any update on this?
@bjorn3 They could easily just use a trait for host operations. Then they could define operations for when libstd is included and just use that, and when your in `no_std`,...
Update: yes, the first answer is a bit useful, but as noted in the issue, it doesn't yet support JSON targets, and that's what I'm using.