Anne Gibson
@perpendicularme
Followers
437
Following
107
Media
203
Statuses
10K
/*-- insert cheeky statement here -- */ Interaction designer and information architect. Follow my personal tweets on @kirabug
Southeastern PA
Joined May 2011
Ok so I have to admit I am feeling a little smug and relieved that I made pdf copies of many of my livetweeted conferences ages ago so that if something happened to Twitter I would still have them. Are they accessible? Fuck no. But they’re a starting point.
0
0
1
You Should Write a Book by Katel LeDû and Lisa Maria Marquis
perpendicularangel.com
When I first started working in User Experience, my mentors explained to me that part of my responsibility as a designer was to pass on to others what I had learned. My team exemplified that ethic:…
0
0
0
My day has been constant interruptions, so I’m giving up on getting through the rest of the conference today… will catch up on the other sessions sometime later. #aeaot
0
0
0
The 8 steps, in summary: 1. Ask questions first 2. Content and functionality 3. Requirements and prioritization 4. Test concepts and designs 5. Document and annotate designs 6. Use accessible components 7. Test development iterations 8. Final review #aeaot
1
0
0
The more accessibility you do all along, the more efficient you’ll be. People can’t blame accessibility for making the process take longer because it’ll be built in Build it in, don’t bolt it on. #aeaot
1
0
0
3. Test for color and color contrast, linearization, and flow 4. Document / annotate designs with keyboard and focus path 5. Test keyboard and semantics during dev / before QA 6. Include 3 people with disabilities in a final review #aeaot
1
0
0
An MVP accessibility process: 1. Ask 3 question of 5 people with different disabilities 3 different times: before you start, during the process, and final review. 2. Review and answer your role based questions during the process. #aeaot
1
0
0
3 questions for design: 1. Which thing should be focusable and in what order for keyboard efficiency? 2. What is the name of each thing? 3. Is there a visible feedback mechanism for an interaction? #aeaot
1
0
0
5. Do we use plain language wherever possible? 3 questions for development: 1. Does the code reflect the visual relationships present in the design? 2. Is the code clean, semantic markup? 3. Does all functionality work efficiently with a keyboard? #aeaot
1
0
1
2. Do our headings set the right expectation for the content that follows each heading? 3. Do our calls to action map consistently well to the content that is presented next? 4. Do our text equivalents reflect the intent and function of their media? #aeaot
1
0
0
Step 8: final review. The 5 questions to answer should’ve been answered as early in the process as possible. 1. Do page titles accurately reflect the content or functionality of the page or screen? #aeaot
1
0
0
Accessibility evaluation tools: https://t.co/AYB4SFuLgx is a list by the W3C of tools - 157 of them - that they don’t comment on but help you find so you can choose what you need. #aeaot
1
0
0
Which screen reader should we check with? It doesn’t make sense to test everything manually with a screen reader. If automation hits heading structure, test that part with that. #aeaot
1
0
0
If we’re looking to test keyboard accessibility we should probably test with manual review. (It’s more complete than automated testing.) Images have alt text, probably automated testing. #aeaot
1
0
0
Can you test every requirement with every method? Possibly. Some will be automation, some will be manual review, one will show up with each of the other items. #aeaot
1
0
0
Conduct accessibility testing with the least complex tool available that requires the least learning with the most value. You can’t test everything with automation. You also need manual review, screen readers, magnification, voice control, and usability testing. #aeaot
1
0
0
1. does the code reflect the visual relationships/ 2. is the code clean semantic markup? 3. is it easy to use with a keyboard? #aeaot
1
0
0
6. Use accessible components. Put 40% of your tactical accessibility effort into a design system. 7. Test your development iterations. Shift accessibility left. Test during development. Put 30% of tactical accessibility effort into testing the process. #aeaot
1
0
0
MVP for documentation and annotation: 1. Linear order 2. Notable focus path changes 3. Labels / accessible names 4. Notable keystrokes 5. Type of control / component #aeaot 5. Heading and other semantics
1
0
0
Document the order between components and how the user should be able to navigate between areas. Document keystrokes that map to things. Figma has great accessibility annotation kits. #aeaot
1
0
0