Be The Fireman and not The Cop
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Be The Fireman and not The Cop

on

  • 8,776 views

 

Statistics

Views

Total Views
8,776
Views on SlideShare
8,713
Embed Views
63

Actions

Likes
3
Downloads
15
Comments
0

3 Embeds 63

https://twitter.com 51
http://lanyrd.com 11
http://tweetedtimes.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-NonCommercial LicenseCC Attribution-NonCommercial License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • [twitter]Overcoming resistance: the key is good communication and good communicators.[/twitter]
  • [twitter]The Tipping Point by Malcolm Gladwell - http://john.foliot.ca/TippingPoint[/twitter]
  • [twitter]Bug tracking systems: http://www.thegeekstuff.com/2010/08/bug-tracking-system/[/twitter]
  • [twitter]Pro-tip: Provide detailed expectations of Outcomes, not process[/twitter]
  • [twitter]Related: Case Study: AT&T’s Role-Based Approach – Thursday @ 1:50 #Deque[/twitter]
  • [twitter]Pro-tip: Be specific in what you ask for, generous in what you accept[/twitter]
  • [twitter]Celebrate successes - Recognize efforts great and small[/twitter]
  • [twitter]Thanks for listening - Be the Fireman and not the Cop[/twitter]

Be The Fireman and not The Cop Presentation Transcript

  • 1. Laying the groundwork for online accessibilitysuccess in a large environment
  • 2. Current Problems• Lack of accessibility planning / pre-planning• Stakeholders already on the defensive• Tight deadlines• "How Much Does It Cost?" - No budget allotted• Content being developed for the web that was never designed with web accessibility in mind• Sum total = Resistance
  • 3. Resistance to changeResistance to change manifests in different ways: Confrontation Avoidance Rejection Insincerity (hand waving)
  • 4. Finding the champions It takes a Cultural shift. The key is goodcommunication andgood communicators.
  • 5. The Law of the Few• Connectors – Knows everyone, has done everything (institutional knowledge)• Mavens – Tech gurus. Follows web trends and tries new technology early (implementer)• Salesmen – Boosters, promoters, persuader, helper (enthusiasm)
  • 6. Communication Skills• Be Likable - Stay positive• Connect - Find mutual points of interest• Solve Problems / Build Trust - Teamwork starts with you• Create Positive Experiences - Make learning fun!• Build relationships – You can’t do it alone.• Identify and work with Connectors, Mavens and Salesmen in your organization.
  • 7. Establishing the systemsto get you thereTackling Technical Challenges Publishing & Tracking systems Drupal, CQ5, etc. Bugzilla, Mantis, Trak, etc. Frameworks jQuery, Dojo Consider custom tools Stanford’s Caption tool
  • 8. Establishing the systemsto get you thereTackling Technical Challenges Evaluation tools Deque Worldspace, SSB Bart AMP, IBM Rational Checker WAVE, eChecker
  • 9. Establishing the systemsto get you thereTackling Cultural challenges Goals and Expectations Provide detailed expectations of Outcomes, not process - encourage creativity Set realistic goals and expectations Lay out the efforts as challenges, not consequences Pursuit of Quality
  • 10. Establishing the systemsto get you thereTackling Cultural challenges Timeline/milestones Fostering empathy andunderstanding Brownbag events - invite actual users with disabilities
  • 11. Establishing the systemsto get you thereAddressing Financial challenges The hardest problem to solve today Honesty is important Scaled question - the longer you delay, the more it costs
  • 12. Establishing the systemsto get you thereTransition towards team based approach• Project Manager• Tech Team• Design, User Experience• Marketing/Content Dept.Identify bottlenecks for each group independentlyRoles based accessibility: http://www.w3.org/community/wai-engage/wiki/Accessibility_Responsibility_Breakdown
  • 13. Establishing the systemsto get you thereEstablish Training and internal resources Motivation (internal awards, recognition, etc.) Knowledge wiki or other Knowledge Base Consistency of implementation
  • 14. Legislation, Policy &Best PracticesAccessibility is a governance issue and a shared responsibilityAppeal to Pride versus Fear• Policy: work with existing standards - avoid re-inventing the wheel• Best Practices: document your internal interpretation and implementation - consistency trumps all• Legal threat is heavy-handed: use as last resort. (IANAL)
  • 15. Measuring success• Avoid checklist mentality• Avoid appearances of concessions and sacrifices• Avoid the Brick!!
  • 16. Measuring success • More than just QA Process: multiple rounds of testing for accessibility • Work with milestones: test early, test often • Be specific in what you ask for, generous in what you accept* * (Within reason)
  • 17. Measuring success Celebrate successes - Recognize efforts great and small
  • 18. Thank YouQuestions? Contact Me john@foliot.ca http://john.foliot.ca Be the Fireman and not the Cop: Laying the groundwork for online accessibility success in a large environment February, 2013