It was amazing to see that summit organizers took as much care as they could to make the event accessible. Speakers have described everything that they have shown visually and closed captions were provided live.
Ari Stile kicked off the event with a welcome note and housekeeping tips. She admired Adobe Connect as the platform has become much responsive than ever before but suggested audience to use wired connection better quality. Other option is to turn off the video; they keep running cameras because some people might love lip reading (either by choice or by necessary – again inclusion here!).
First talk was by Robert – a Project Manager and title of the talk is “PM Led Accessibility”; it was very insightful to hear how Project managers / product owners can create a great impact. He began explaining about typical roles of a PM that includes, managing timelines, deliverable, taks, communication, risk mitigation, resourcing, requirements, scoping etc.,
So whose responsibility is accessibility? Can PM take this responsibility; the answer is Yes! and how that can be done; by having little learning about accessibility, having empathetic mindset, have understanding about accessibility requirements and roles of resources. It’s important to include discussion about accessibility in Project meetings, let me know about risk if product does not comply with accessibility standards. Even if product does not have an accessibility requirement, it’s still be a risk from legal prospective. It’s obvious that as the progress, there will be resistance or setbacks about accessibility but being firm is important. Ask coworkers how the product would work for diverse users like people who are blind, hard of hearing, cognitive disabilities, elderly etc.,
It’s also important to educate resources about the impact accessibility creates. Showcase examples like how product having low color contrast would impact users when viewing on a mobile device in a sun light environment etc.,
Robert has recommended one should read book “Reimagine Empathy” by Paul Parkins (unfortunately, I couldn’t find this book online; if anyone does, please leave the link in comments section please…).
If you are new to accessibility, that’s Okay, ask for help. There are a lot of wonderful people and forums like WebAIM who would be happy to help. It’s good to seek help rather than spending your time. Of course, research is good too!
Let us, however, agree that accessibility is not single line item and all stakeholders has to put in efforts as per their roles and responsibilities. For instance, designers should design products keeping inclusion in mind, developers should code keeping semantics and standards in mind. QA folks should include accessibility into their test plans. Accessibility should be discussed in product / project status meetings. Communication plays a key role to achieve goals.
Some resources that Robert has mentioned in his presentation:
- Web Content Accessibility Guidelines 2.0
- A customize-able quick reference to WCAG 2.0
- Vox Product Accessibility Guidelines – this includes a checklist but Robert also remindseveryone that accessibility should not be treaed as checklist wise activity
Then Robert discusses about significant risks with accessibility problems. Includes litigations happening in all industries, people demanding rightfully equal access, law suits etc.,
Accessibility of a project can be achieved by raising awareness among all stakeholders, reporting accessibility progress, knowing when to ask for help, as needed, bring in accessibility consultants on board, etc.,
Robert has also recommended people reading Developing a Web Accessibility Business Case for you, Accessibility Business Case by Karl Groves and Website of Lainey Feingold – an advocate who does a fantastic work in the area of accessibility advocacy and structured negotiations that could lead to win-win situation.
Then Robert focuses on a few tips how to get the accessibility work done. Well, PMs has great power; they can dictate! But a constructive discussion brings the success. When providing a feedback about accessibility, start conversation with positive notes and say something like “Hey buddy, you are great; you love code, how about adding that love to accessibility too?”. Make sure to bring back the focus as you notice. Recall project requirements so that it stays on everyone’s thinking. At times, you may need to esclate too. If situation minor, just mark in tracking system but if issue is major, call all stakeholders for a discussion.
When there was a question about what Robert would advice to deal with B2B companies, he says that though B2B companies doesn’t directly deal with consumers, we never know if business that company is dealing with may have people with disabilities in stakeholders. Today given that technology does a great job and make things possible, anyone can take up any job… I agree with Robert.
That concludes session of Robert; Next post will be about Paul Adam’s Presentation titled “Reports that designers and developers love”. Stay tuned!
Disclaimer: These are not exact words that Robert have used.