Exactly, it sort of re-inforces my point that when I was designing that site I didn't really think about it.
I don't have to be an accessibility expert to discuss the fact that developers don't tend to create accessible sites!
I really liked the first font from a design standpoint and found it quite readable! It's ridiculous you're being attacked for voicing a very valid concern on your own blog, because of your preferred font choice. A lot of the comments both on your blog and on here seem to almost be mocking the idea that sites should be accessible, by making an unwarranted personal attack against you, when you clearly state you were never even introduced to accessibility programming through formal education, like lots and lots of developers weren't ( myself included ).
Forcing programmers to jump through extra hoops (trying /em to learn on their own, and making well-intentioned changes but not knowing if its right or enough or effective) is not the way to increase knowledge and uptake of accessibility-minded-design as the standard.
It would be nice if designers were still able to make stylistic choices with regards to fonts and website colors, that may be less readable for some, but have it degrade easily to something more readable with a simple command or click of a button. Besides some roundabout ways i can think of, or using readability, im not sure how to do that easily though.
That's an unfair criticism. The author (and I, and the rest of us) are not focussing our efforts logically. We can see browser stats in server logs, but measuring disabled or impaired visitors' traffic is easy to overlook - servers don't collect this data point.
She's now raised the issue for a wider audience and this could only be hypocrisy if she held herself up as an example of how to do things correctly. She isn't, and says so right at the top of the article.
> I'd like to start this post with a disclaimer: I don't know much about creating accessible websites.