I’m designing an accessibility workshop with a working title of ‘Do your own Accessibility Audit’
I’m hoping to help people get into accessibility testing while adding real value to their companies by offering a basic accessibility audit in house rather than spend thousands on very detailed external services. Starting with a unique quiz to introduce a lot of the principles of accessibility the attendees would practice on their own systems (if available) and practice hands on auditing and testing in the class room. By the end they will have enough knowledge to complete the audit they have already begun.
I have a couple of questions I’m hoping people will help me answer.
Would this be of interest?
What would you like to see covered?
While mainly web focused, would you like some mobile/app coverage?
Any help would be greatly appreciated. Thanks, Ady
How much of an understanding of accessibility would you expect from the attendees?
How long are you planning for the workshop? Is it a one hour event? Or more of a half-day exercise?
Once the audit is complete, then what?
As it feels like the audit is the start of something, rather than the end.
Perhaps give examples of where something fails an audit, and what can be done to demonstrate it? Maybe take it even further and show an improved version of the site after the failed audit, and what was done to make it pass, along with showing it passing?
Could it also cover how to sell the result of the audit? As initially the audit may be shown to stakeholders and they may feel that the failure isn’t that big. Others can still use it, it makes them money, etc. Helping people point out the impact, whether it be legal, commercial, financial, etc., they could take the audit result and use it to fuel the necessary changes.
Love the questions Lee, thanks. This is exactly what I want.
I’m not expecting any understanding of accessibility from the attendees. Obviously, some understanding is useful but my experience is that lots of testers see accessibility as a specialism that takes a lot of time and effort to understand and from an audit perspective that’s just not true.
I’m looking at a half-day workshop covering all the knowledge needed for a basic accessibility audit.
As testers, we provide value through information. We don’t always have the authority to decide what is prioritised but offering information from an accessibility audit, albeit a basic one, has to be better than nothing at all.
Basic accessibility audits generally don’t give the behind the scenes coding examples of how to fix things but I’ll definitely have examples of what can be done instead.
There will be some aspect of that in the workshop. I do cover that in my Accessibility, Assumptions and Arguments talk I’ve given a few times so I’ve examples and ideas to share.
Thanks again and keep them coming if anything isn’t clear
This is a great idea. I think you’ll get good interest from testers who want to broaden their scope.
At least a reminder that influencing the design early is better than correction after an audit. So if there is an opportunity to avoid an accessibility issue, take it.
Thanks @hattori and your point is a great one which I make in my talks and in general. I’ll be sure to include references to inclusive design in the course as any bug you can avoid is better than correction no matter the type.
I love that it will be a hands-on session. I’m not an a11y expert but I’ve found learning and practicing it makes me a better tester overall - just as making an app more accessible helps everyone and not only people with various impediments. And that’s what I’d like to see an emphasis on - it’s not just an “extra” for a few people. I personally would love to learn mobile app aspects.
Fantastic idea, I would love to attend the workshop. I’ve been involved in testing our application for accessibility, and one of my struggles is using accessibility tools as a user that doesn’t have accessibilities needs.
I’ve conducted an accessibility usability testing for one of our clients, and it was frustrating, most users for this particular client have some accessibility needs, and I really felt like we were (are) failing to support them. So participating in a workshop and learning how to test better and help the team to develop the application to be inclusive would be an achievement.
