Hacker News Reader

...rule one of accessibility is let the user configure how they access your content, and you just chose to override that. So that's a pretty weak excuse.

They can still disable custom fonts in their browser if they care. I have them disabled in Chrome.

Why "must"? What group is being excluded by this?

Dyslexics

> For example, most people don't consider that the W and the M in your font must look distinctly different, and not just vertical mirrors of each other.

Why isn't relying on default fonts provided by the user's system good enough for that?

I don't know what specific problem the parent is pointing to, but generally, users don't set up defaults, so you're really using the defaults of the vendor of whatever system the user uses. That may or may not be useful.

Tool customization may be where the users and power users are separated - but it's hard to tell who is who when you're just looking at an HTTP request.