@leaverou @font.awesome Hey, this is exciting! While...

@leaverou @font.awesome Hey, this is exciting!

While you're there, do you think you can improve accessibility for people who have web fonts disabled, e.g., via Apple’s Lockdown mode? My web-browsing experience all too often looks like this… 🙏

A screenshot of Lea’s blog at lea.verou.me indicating some square placeholders where FontAwesome icons would appear if the user was not blocking web fonts.

Like 17 September at 0:22 | Wall-to-wall | Open on mastodon.social

2 comments

Lea Verou

@com @font.awesome My blog actually uses Bootstrap Icons since it was done before I switched to FA. I should redo that part now!

What would be the ideal experience for you? What would you prefer to happen in that case?

17 September at 2:15 | Open on front-end.social

Quinn Comendant

@leaverou @font.awesome The general trend in web dev has been to move to SVG-based icons, which are supported universally. FontAwesome has SVG support now, but many sites still use the font version, including parts of the FontAwesome website itself (screenshot).

Ideally, users would be nudged away from using the font version. From skimming your blog post, it seems you might be in a role that could push for adoption of accessible icons?

A screenshot of fontawesome.com/search with placeholder squares where icons should appear.

17 September at 2:42 | Open on mastodon.social