And I was saying that I don't believe this is true. And the internet proves it. In abundance.
I'm sorry but it doesn't. The Internet proves that not many people are interested in building standards compliant websites. It doesn't prove that people with a basic knowledge are not capable of doing it.
However you should be standards compliant. Even one WAI priority 1 issue makes a site very difficult to navigate using a screen reader or text only browser. However you don't need to go nuts and start ripping your site apart to try and fix it. Look at your demographic and the people who are going to use it and then try as hard as possible not to exclude anyone.
However why?
A common misconception between many people is that you need a standards compliant website to be accessible, this is not true at all. You can have an accessible website without being standards compliant.
It's an interesting point you make about "not to exclude anyone" - Accessiblity is about "access for all" - now go explain to people who use old computers, with old browsers why they won't have access to your website.
WAI 1 is way too restrictive and WAI 2 are proof of that. WCAG 2 will be more like section 508 which is a more practical and common sense approach. No longer will it revolve around code, but whether it actually works or not.
I think we're going to have to agree to disagree here. If you understand the issue then you should be doing it. It doesn't take long if you have the knowledge.
It still takes longer than doing it the old fashioned way.
We have to stop treating the internet as a place full of perfect people. It isn't. We have to be more inclusive, and try to reach as many people as we can with our content. I feel that in Ireland we have a very inclusve culture and society.
For example, we have better public transport access for wheelchair users than any other city I've been in. Every single new building has ramps or lifts etc. So I feel that we shouldn't ignore various groups on the internet because the time it would take to complete it.
Yet again getting confused with accessibility and the latest coding standards. I will say it again... a site does not have to be coded in the latest coding standards to be accessible.
Oh I would disagree that "every single new building" has accessible options. I'll give you an example, a wheelchair ramp at the back of a building is NOT accesssible. Yes you may be able to get in in a wheelchair, but because it's at the back of the building, it is excluding wheelchair users.
So this is kind of similar to web accessibility. Just because WAI WCAG 1.0 says it's accessible doesn't mean it is. And it definitely doesn't mean it's accessible if it is coded to the latest coding standards.