-
Icons are not being handled accessibly.
Icons are non-text content as per [WCAG 1.1.1.](https://www.w3.org/TR/WCAG22/#non-text-content)
The key technique is [H86](https://www.w3.org/WAI/WCAG22/Tech…
-
The current toolbar buttons (`A` (*activity*; blue), `S` (*solution*; green), `L` (*learner*, yellow), `T` (*tutor*, pink) are a bit cryptic:
- [x] add tooltips
- [ ] use vector graphics (origina…
-
I just created https://github.com/spl/font-awesome-type for Font Awesome icons. Since I've been using Bootstrap, I always found it quite annoying to use strings for the glyphs. So I think it would be …
-
We are using MudBlazor and the icons from that toolkit. Is it possible to use those icons instead of Font Awesome so that we don't have to include another icon package?
-
- [x] Update requirements doc
- [ ] Rewrite the icon component to use our icons instead of using Font Awesome icons
- [ ] Replace Font Awesome icons in existing components with our icons.
- [ ] Update…
-
-
Icon-Satz reduzieren, eventuell base64-kodiert direkt ins CSS schreiben.
Reduce the set of Icons. Maybe write them directly into the CSS in base64.
-
## Is your feature request related to a problem?
The current icons are very dated in their look and feel. We could present a far better-looking, modern, and usable user experience if we used a libra…
-
With 6.5.2 Font Awesome now has a [Bluesky Icon](https://fontawesome.com/icons/bluesky?f=brands&s=solid).
The website currently uses `fa-square` in place of this.
I tried to do this myself since #…
-