Unreadable pages in lynx and other non-css browsers

[keiyakins]

Using CSS for content is unacceptable in any circumstance. It creates unreadable pages in non-graphical browsers, when users turn off stylesheets (in 'reader mode' for instance), and destroys accessibility with screen readers and the like.

[AlexandreArpin]

Thank you for your feedback!

Do you have any alternatives or suggestions as to how you would approach solving this issue without impacting traditional graphic users?

[keiyakins]

Honestly? <img> with alt attributes. Using background images for foreground elements is inherently going to cause problems.

Failing that, have the text representation (W, U, Q, etc) as text inside and just hidden by the CSS, so at least that's there.

[AlexandreArpin]

How does FontAwesome (the inspiration for this project) handles this? The Alt Attribute and Text representation would probably be left to the implentor.

Some symbols had text representation before and I remember it caused a handful of problems with the scaling of things.

This project is also a proof of concept for handling this sort of things, If you feel like sending a pull request with this issue fixed i'll gladly review it, otherwise, it'll probably stay as it is.

[AckerApple]

I don't use these symbols for documentation or screen readers @keiyakins. I use it to make art on the web with scalable vector art (fonts).

[keiyakins]

FontAwesome doesn't. This is somewhat acceptable as its icons are usually used as bullets, so they're not actually content, just styling. This is not true of mana costs and the like.