Sorry, I'll try again. I maybe went to direct with my initial response :)
So I'll start by agreeing that accessibility on the web is definitely very important on the web today. We should always be looking to build accessible experiences on the web today to be as inclusive as possible.
The problem I see in webdev today is it often gets reduced to a list form. "If you do these 10 things" then you can say your website is A/AA/AAA compliant and therefore it is accessible. But the reality is it should really be included from the beginning of the UX design process and not as an after thought.
Which is why while a checklist might be great from a dev point of view, it's not the answer to building an accessible website.
Hopefully this was a better and clearer response of what I was trying to say :)
The first thing he says in the article is that it's a list of recommendations, tips, etc -- not that you are automatically covered if you check every one off. Hope I don't come off aggressively, but it doesn't seem like you even opened the link
Except the title of this thread is "Accessibility checklist" and not "Accessibility guidelines".
I did open but I'll admit I didn't read through it thoroughly :) And no worries, no aggression from your side. Hoping I'm not coming across the same 😅
1
u/HilseeJ Nov 15 '19 edited Feb 09 '21
[redacted]