I do personally want to make sure the content on this website is consumable by people with disabilities and/or with poor internet connection and browser speed. However, at the same time, I want to add any feature that I feel would improve the website experience, for everyone else. This is how I reach a middle ground between both sides:
Bare bone website version§
Consumable content with everything blocked§
First, icons on this website are managed with an icon font. I’ve watched Seren Davies’ talk, but I’ve found working with SVGs noticeably increases workload on my end.
However, I’ve still implemented those icons with accessibility in mind:
- Navigation is done with text entries in the sidebar, not icons.
- Buttons for other functionalities use text to reference their action, rather than (only) an “image”, most of the time. The only mission-critical one that isn’t represented with text is the sidebar folding and expanding button, right next to “Home”. But it is mapped to the standard up and down pointing triangle characters, so it should still be useable.
- Icons that aren’t decorative are “mapped” to their closest standard Unicode symbol, so even without the font, their purpose should be fairly understandable. Furthermore, I make sure those Unicode symbols have been standardised since at least 1999.
- My font has only the icons I use, and compared to the SVG equivalent setup, it takes up roughly a third of the size.