Accessibility – what is it good for? | Marco’s accessibility blog
This blog post is by no means about diminishing the accomplishments the #accessibility community has made. But we need to go beyond that! We need to leave our comfortable niche and turn the accessibility extra way into the #standards way. Make people use headings, correct form element labeling, and other stuff just because it is the right thing to do that benefits everyone, not because “it’s an accessibility requirement”. Accessibility needs to finally shake off the smell of being an unloved burden to meet some government criteria. Every book any web dev buys must simply state as a #best_practice, without mentioning accessibility at all, that for labeling an input one uses the label element, and that the for attribute of that label element needs to point to the id of the input to be labeled. As a test case, state that this way, a user can also click on the label to get the cursor right. Don’t bother people with screen readers at all. They don’t need to know for these things.
We must get to a point where teachers give their students lesser grade if they deliver semantically incorrect work. An excuse like “but it works” should not be enough to get a good grade.
Cent fois oui, on en est déjà bien là quand je participe à des formations.
Voir aussi, un commentaire de Kevin Potts :
The main problem, having been invested in the accessibility community since 2003, is that accessibility is seen as a checklist. Legislature such as Section 508 promotes this way of thinking — “make sure you check 0ff this, this, this and this and boom your site is accessible”. Checklists are easy to reference. Developers love them because lints and validators can be written against them.
The reality is that accessibility is a philosophy. It is a mindset. A strategy. A tenant. This is the brilliance of WCAG2.0 that most from the sidelines fail to grasp. It uses words like “perceivable” and “understandable” — abstractions that try to convey that accessibility is foundational, not something that cannot be tacked onto the end of a project.
2.10 : The (Second Phase of the) Revolution Has Begun
This aesthetically pleasing browser has begun a revolution in the way we experience knowledge. In the world of the Web, knowledge is not something you produce, but something you participate in. A document isn’t a self-sufficient individual creation, but a perspective, or collection of perspectives, on the entire Web.
This may sound abstract, but with Mosaic on your screen, it is suddenly, strikingly concrete. All the documents in the Web are within reach. What path will you take to get to them? What path will you mark for others to take?
C’est génial, l’enthousiasme de cet article. Ils ne disent même pas encore « bookmarks », ils disent « hotlist ». Tout l’usage restait à inventer, mais l’auteur (et Marc Andreesen) voyaient loin et ils avaient raison, la prophétie s’est réalisée.
Un régal de lire ça 18 ans après.
(via https://billshackleton.wordpress.com/2012/07/13/farewell-to-web-accessibility-part-2-roots dont nous reparlerons)
Universally Designed » Considering the Case for Creating an International Society of Accessibility Professionals
ATIA/AIA, IBM, Adobe – these are entities with deep pockets and a vested interest in seeing something like this move forward, and I am sure that they are willing to make investments to a point. But as one who has worked in this space for over a decade, I (we) well know that for the most part those who are currently working in the field of “web accessibility” are, for the most part, independent consultants, smaller development firms, or inside actors at a larger establishment who’ve embraced the role of advocate and agent provocateur where they work, often not because it’s part of their job description, but because they have come to our cause and profession for other reasons. Very few however actually have the privileged of being professionally focused exclusively on web accessibility: it’s part of what they do, and they do it for all the right reasons, but sometimes that alone doesn’t pay the bills. (I’ve personally been lucky and persistent, but I remember the early days, and the struggle to stay afloat while trying to focus on this industry: I also worked as a waiter and bar-tender to make ends meet.)
The Only Thing Constant is Change « Unrepentant
I arrived, a web-accessibility specialist, to set up a program that had a title and a blank sheet of paper attached to the title. The job? Figure it out and get it done. Learn the art of herding cats, and establish web accessibility as a thing on campus. Be an evangelist, a technologist, a salesman, a politician. Make it happen. I was surrounded by a group of supportive if sometimes skeptical technology people, who were always gracious in their generosity of time to me, and for the most part openly receptive to what I was trying to do. They remain so even today, and I look back on the many successes we’ve accomplished together, and the path forward we have charted together too, and I wish you all continued success.
When we use common image replacement techniques, including the smart ones, the user agent doesn’t know what’s the relation between the text content and a #CSS #pseudo-element or background. This is not even a “CSS is for decoration” issue. It’s a “your code lacks semantic information” issue
Why Web Accessibility Matters | Below The Fold
As a design agency, we come across a lot of business owners who think that in order for a site to be accessible it has to look dull as well. They feel they have to sacrifice one for the other. We disagree, as long as your site takes into the consideration accessibility guidelines then there is no limit to what you can produce from a design perspective.
C’est vrai que c’est un argument qu’on entend encore souvent, en partie à cause du fait que tous les évangélistes de l’accessibilité ont un blog mais tous ne sont pas designers. :)
WebAIM: WebAIM: Web Accessibility for Designers
Yes, yes, and yes.