Apparently the issue with Exo 2 is an upstream issue in Exo 2 that mostly affects macOS Browsers: https://github.com/NDISCOVER/Exo-2.0/issues/11 https://github.

Apparently the issue with Exo 2 is an upstream issue in Exo 2 that mostly affects macOS Browsers: https://github.com/NDISCOVER/Exo-2.0/issues/11 https://github.com/NDISCOVER/Exo-2.0/issues/11 (Possibly Google Fonts is serving different CSS specific to macOS user agents as a current workaround.) Fontsource (which is similar to this tool but packaged as npm packages and I found mentioned in another thread here) is similarly aware of the issue and suggests the current macOS workaround is to enable it as a Variable Font with slightly different CSS: https://github.com/fontsource/fontsource/issues/243 https://github.com/fontsource/fontsource/issues/243 (They don't enable fonts as variable fonts in their default CSS because of different browser issues with variable fonts.)