I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
I'm mostly thinking of the fact that you have to add extra markup and then hide it from screen readers. This means if you have something that's just an icon, you end up with two elements anyway. It's not that you can't fudge it to be accessible, it's that it makes extra hoops to jump through.
And if the font doesn't load properly, people get nonsense characters in their page.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'd advise against doing things like extracting the font urls from Google's entrypoints. What if they change over time?
I have my doubts as to the benefits of font awesome at all in the face of writing coherent, accessible web documents.
Good point, I added that warning.
Out of curiosity, what is it about font awesome that makes a web document inaccessible?
I'm mostly thinking of the fact that you have to add extra markup and then hide it from screen readers. This means if you have something that's just an icon, you end up with two elements anyway. It's not that you can't fudge it to be accessible, it's that it makes extra hoops to jump through.
And if the font doesn't load properly, people get nonsense characters in their page.