Because the stakes are high enough that 5% validates the engineering effort.
.
> 2) If 9+ is 30%, why quibble over the extra 5%
Same answer.
.
> 5) The distinction between the two is two independent implementations.
I didn't know that. Thank you for the information. :)
.
> 8 #1) Colourblindness (8% of Caucasian Men)
Jesus, really?
Luckily, my sites tend to be monochrome, so I get trapdoored on this.
.
> 8 #2) Dyslexia
I wouldn't even know where to begin making a website be dyslexia-sensitive. I don't know anyone affected and don't even know what's important there. Is there a resource about this?
.
> 9) The non-presence of ARIA does not make a site inaccessible.
In a question about why we invest no effort in accessibility, it is germane to point out the level of effort you have placed into accessibility.
And, respectfully, that markup.
.
> Unfortunately, you are presenting the opposite side of the problem.
I'm just explaining why it isn't gotten right.
.
> So you have a little more knowledge about accessibility issues than the OP - but not enough to pass a quick scrutiny.
Yeah, that was my point. My belief is that this limitation that you have correctly observed in me is the defacto case for nearly all web developers. I think it's just something most of us don't know.
Like, write a poignant guide or a learn you some consideration or something. Give people something to read, rather than to point out that they haven't read anything, you know what I mean?
.
> Perhaps, what is needed is for you and I to stop being part of the problem of disseminating half-truths
I don't believe that I have done this. I did make an error in naming the kind of recommendation though.
.
> spend that time quietly doing our jobs properly
I think that I actually do this. The world is full of a lot of hard, unfair choices, many of them outside my hands. I do my best to support as many people as I can within my time and budget constraints.
Perhaps we disagree on the choices, however.
.
> Invest the time to teach someone else how to build accessible websites
Yes, that was my point. Easy to say; too hard, apparently, for either of us to do.
Because the stakes are high enough that 5% validates the engineering effort.
.
> 2) If 9+ is 30%, why quibble over the extra 5%
Same answer.
.
> 5) The distinction between the two is two independent implementations.
I didn't know that. Thank you for the information. :)
.
> 8 #1) Colourblindness (8% of Caucasian Men)
Jesus, really?
Luckily, my sites tend to be monochrome, so I get trapdoored on this.
.
> 8 #2) Dyslexia
I wouldn't even know where to begin making a website be dyslexia-sensitive. I don't know anyone affected and don't even know what's important there. Is there a resource about this?
.
> 9) The non-presence of ARIA does not make a site inaccessible.
In a question about why we invest no effort in accessibility, it is germane to point out the level of effort you have placed into accessibility.
And, respectfully, that markup.
.
> Unfortunately, you are presenting the opposite side of the problem.
I'm just explaining why it isn't gotten right.
.
> So you have a little more knowledge about accessibility issues than the OP - but not enough to pass a quick scrutiny.
Yeah, that was my point. My belief is that this limitation that you have correctly observed in me is the defacto case for nearly all web developers. I think it's just something most of us don't know.
Like, write a poignant guide or a learn you some consideration or something. Give people something to read, rather than to point out that they haven't read anything, you know what I mean?
.
> Perhaps, what is needed is for you and I to stop being part of the problem of disseminating half-truths
I don't believe that I have done this. I did make an error in naming the kind of recommendation though.
.
> spend that time quietly doing our jobs properly
I think that I actually do this. The world is full of a lot of hard, unfair choices, many of them outside my hands. I do my best to support as many people as I can within my time and budget constraints.
Perhaps we disagree on the choices, however.
.
> Invest the time to teach someone else how to build accessible websites
Yes, that was my point. Easy to say; too hard, apparently, for either of us to do.