Posts Tagged ‘Usability’

Learned Pattern Recognition

Tuesday, August 23rd, 2011

I was having an interesting conversation with Alex Jones the other day, remarking about the usability studies by Peter Steen Høgenhaug around the ‘link’ iconography in CMS software. Alex touched on this in his blog with Usability of the Link Icon and earlier with Replacing the Save Icon. It’s interesting when we encounter patterns in systems that other designs tend to perpetuate and we create learned patterns that users who interact with our systems get used to over time.

As Alex points out, Høgenhaug did test with users unfamiliar with the CMS software and were not used to patterns in those systems even though many systems use very, very similar iconography. It would be interesting to see that case applied to frequent users (a simple pattern learned once, to be sure).

I’m a big fan of re-evaluating systems on a regular basis because I think it keeps UX professionals fresh. I’m always worried that too often, as technology changes, as systems become more complex and evolved, we rely on older iconography, older user patterns, and the ‘traditional’ ways of thinking. I feel that we should be looking deeply at the user base to come up with new and innovative methods to teach users new structures rather than relying on old habits and patterns. Saving to a disk may no longer be a useful user action, versions could be closer to the path you want users to take. Sharing, Tweeting, Manipulation – new and interesting actions have cropped up for users. It’s up to designers to take a step back and look at how these actions are taken in the system and craft designs which encourage these actions but are not confusing.

Live Blog from John Slatin Access U 2009

Tuesday, May 12th, 2009

Live Blogging from @pat_ramsey ‘s talk on “Accessibility and Social Media”.

SMS is primary social tool in Sub Sahara Africa – only data the infrastructure will support.

Problems: When there’s no way to skip repetitive content, no text equivilents for images when the sites are super image heavy, when you can’t identify inputs and controls – the rush makes accessibility fall by the wayside!

Problems arise when users who don’t know about accessibility can create content without the tools available for accessibility information. 15 year olds on YouTube don’t know about captions on their home movies – how to handle the user-generated content question?

How to make Web content accessible to peopele with disabilities. Education is key!

Text alternatives are important to image heavy sites: Thumbnails in discussion threads, avatars in forums, images in user galleries.

CAPTCHA: The questionable best way to handle bots. Turing Test Alternatives are better “Is fire hot or cold?”. What about audio files? They are, by definition, hard to hear! Look at Blogger’s audio CAPTCHA.

Don’t make it harder for your users to sign up than it is for bots and phishers! This should make you think long and hard about access barriers.

LABEL YOUR FORMS! The and attributes are important for those hitting your form in JAWS form mode.

Facebook Mobile: m.facebook.com, simpler, easier and faster loading. Much easier for screen reader use. beware – login and other forms still not labeled!

Twitter: “what are you doing?” is labeled correctly, most images have alt text. Skip nav is enabled. Use greasemonkey scripts to enhance accessibility. There is a third party accessible alternative.

WordPress: problems are two fold: admin interface and published interface. Templating on the front end works great for the 6 files (wrap your content in an accessible package). With admin panel – edits are lost on upgrade! Look at /wp-admin/ folder to see the admin template files. Login form in properly labeled for accessibility. Admin section has problems, but know issues are getting better. Alt+Z drops right to content editor! Those need to be told to users!

Developers know things can be better. WAI-ARIA used to send info back to blind twitterers about how many characters were left in their tweets (TPG Notifier).

“Great kid, now don’t get cocky” – There is a need to get content from developers about what does and doesn’t work. Open source can help with all this. Rather than feel overwhelmed, try to submit patches, find the accessibility hooks, share findings, communicate! WordPress IRC is always open, Facebook loves feedback!