The document is a presentation by Meri Williams on baking accessibility into agile processes. Some key points discussed include defining team values to include inclusivity and accessibility, arranging work as deliberate practice to improve accessibility skills, and defining what "done" means to ensure it incorporates accessibility testing and inclusive design. Anti-patterns that were discussed include rushing accessibility testing to the end or treating it as an optional extra cost. The overall message is that accessibility should be integrated into normal development practices and valued as highly as other quality attributes.
13. WE KNOW ABOUT ACCESSIBILITY,
RIGHT?
Meri Williams, ChromeRose @Geek_Manager
14. • Progressive
enhancement
• Graceful degradation
• Offline-first
• Mobile-first
• *-first
• Contrast analyzer
• Accessibility audits
Best
Good
Practices
Meri Williams, ChromeRose @Geek_Manager
15. IT’S NOT JUST ABOUT DESIGN AND
TECH, IT’S ABOUT CONTENT TOO
Meri Williams, ChromeRose @Geek_Manager
16. “One measure of literacy is the percentage of adults who
perform at four achievement levels: Below Basic, Basic,
Intermediate, and Proficient.
13 percent of adults were at or above Proficient (indicating
they possess the skills necessary to perform complex and
challenging literacy activities) in 2003.
Twenty-two percent of adults were Below Basic (indicating
they possess no more than the most simple and concrete
literacy skills)”
Source: http://nces.ed.gov/fastfacts/display.asp?id=69
Meri Williams, ChromeRose @Geek_Manager
35. WE’RE GOOD AT WHAT WE PRACTISE,
PROVIDING WE CAN LEARN FROM IT
Meri Williams, ChromeRose @Geek_Manager
36. DELIBERATE PRACTICE
• You must be motivated to attend to the task and exert effort to improve
your performance.
• The design of the task should take into account your pre-existing
knowledge so that the task can be correctly understood after a brief
period of instruction.
• You should receive immediate informative feedback and knowledge of
results of your performance.
• You should repeatedly perform the same or similar tasks.
Meri Williams, ChromeRose @Geek_Manager
37. MODELS OF DELIBERATE PRACTICE
• Sports Model – analogous to conditioning
• Chess Model – what did the grand master do?
• Music Model – chunking & mental rehearsal
Meri Williams, ChromeRose @Geek_Manager
38. IS THE WORK DESIGNED IN A WAY THAT
MAKES IT EFFECTIVE DELIBERATE
PRACTICE?
Meri Williams, ChromeRose @Geek_Manager
40. PRO TIP: REMEMBER TO TALK ABOUT WHETHER YOU’RE
HOLDING TO YOUR TEAM VALUES IN YOUR RETROS
https://www.flickr.com/photos/psd/8002453131
Meri Williams, ChromeRose @Geek_Manager
41. AS AN ASIDE…
DO RETROSPECTIVES RATHER THAN
POST MORTEMS
FOR A POST MORTEM,
FIRST SOMETHING HAS TO DIE
Meri Williams, ChromeRose @Geek_Manager
49. WE ARE PROFESSIONALS, DAMMIT
YOU WOULDN’T CHARGE EXTRA FOR
TESTING, WOULD YOU?
WHY MAKE ACCESSIBILITY AN
OPTIONAL, ADDED EXTRA?!
Meri Williams, ChromeRose @Geek_Manager
51. Bake Good Practices In
• Articulate team values
• Value inclusivity & accessibility
• Arrange your work as deliberate practice
• Do accessibility testing katas
• Define “done” appropriately & inclusively
• Remember skills take time to become automatic
Meri Williams, ChromeRose @Geek_Manager
52. BE
AWESOME
BE
INCLUSIVE
Meri Williams, ChromeRose @Geek_Manager
Editor's Notes
But of course you’d say that Meri – you’re a diversity statistic!
Yes, I am in the minority in some ways, and that makes me very aware of being different. But I think this is a positive – it helps me to have empathy for people.
But of course you’d say that Meri – you’re a diversity statistic!
Yes, I am in the minority in some ways, and that makes me very aware of being different. But I think this is a positive – it helps me to have empathy for people.
The average reading level of the average American is 7-8th grade: i.e. 14 year old
We’d love to believe that our users are hanging out, doing extreme sports in between ice sculpting, but able to 100% focus on our website or app when they’re using it.
NICE DREAM.
So how do we bake it in?
For instance, if you as a team adopt the boyscout rule (i.e. always leave it looking better than you found it) then it wouldn’t be OK for someone to check in code that doesn’t have tests, just because they found it that way (they’d be expected to improve it)
There was a great article recently from Ron Jeffries about why refactoring shouldn’t be written up as separate stories – rather integrate dealing with technical debt into stories that touch those areas, else you will always end up deprioritising technical debt / refactoring stories and so digging yourself deeper into the hole.