has come and gone. Below is a curated list of slide decks, reviews, photos, and more. Also check out my CSUN Assistive Technology Conference CSUN17 preview. Slides etc. from presentations
Feel free to cite more in the comments.
Other reviews, etc.
More awesome stuff
WCAG 2.1 First public working draft. Also see Quick Guide to WCAG 2.1 First Public Working Draft by David MacDonald
Va11yS, or Verified Accessibility Samples, is a repository of live working code samples that designers and developers can easily access to test with different assistive technologies and tools.
OATMEAL – An accessibility testing methodology for the web, by eBay. Stands for Open Accessibility Testing Methods for Experts And Layfolk—nice!
Mind Your Lang by Adrian Roselli from role=drinks event. Photos
Terry Thompson speaking on audio description at CSUN17
Denis Boudreau fills the Deque Suite at CSUN17
Karaoke at CSUN17, Makoto and Matt lead C-S-U-N (to the tune of YMCA)
CSUN17 Flickr album by Dennis Lembree
Unfortunately, several shiny HTML5 features (such as the video element), ended up implemented to different levels by browsers, without good accessibility, and without an interface that satisfied designers (a nearly impossible task). This includes the
Recently on Twitter, there was some discussion about accessible date picker widgets. Jason Kiss (@JKiss) did some analysis and gave feedback.
I felt compelled to list the examples of accessible date pickers mentioned in the Twitter thread, so here they are. Know any other good ones?
PS: In the tweet thread, props to @handcoding, @pauljadam, and @backflip.
Some great accessibility events coming up!
Did I miss anything? Please add in comments.
Update Sep 24: added Ottawa and Chicago events
Experts say don’t do infinite scrolling, or be
extremely careful in doing so. I completely agree. Infinite scrolling creates accessibility and usability problems. Below are checkpoints, issues and suggestions from a few resources.
Here’s a great list of checkpoints from the article
So You Think You’ve Built a Good Infinite Scroll by Adrian Roselli (@aardrian):
Can the user hit “back” and return to the exact same place?
Does the page have a footer?
Can a keyboard user access all other content on the page?
Can you share a URL to a specific place on the page?
Can a user easily jump ahead a few “pages” to quickly get to content much further down the list?
Does the memory footprint of the page dramatically increase after just a couple new “pages?”
Is there a way to disable automatic infinite scrolling and lean on standard paging?
Have you conducted any user tests?
Are you satisfying a use case that has come from research or user request?
Do you have any analytics/tracking to measure success?
In the article
Infinite Scrolling: Let’s Get To The Bottom Of This, Smashing Magazine makes some great points including the following.
Fails: temptation, optimism, exhaustion, pogo-sticking, loss of control, distracting, unreachable
Users want immediate access to exclusive data.
Users want to feel in control.
Users often look for landmarks when scrolling.
Consider conventional pagination or a hybrid solution.
Provide interesting content without an ambiguous interface.
Users often expect a footer.
An infinite list is still a list.
Effects are nice to have but not a must.
In the Simply Accessible article
Automatic infinite scrolling & accessibility, Derek Featherstone (@Feather) says:
Just don’t implement infinite scrolling.
Replace automatic infinite scrolling with a “Load more results…” button or link that explicitly invites the user to add more. Once they do a few times, prompt them to ask if they’d like to turn auto-loading of more results on.
No, really, just don’t implement infinite scrolling.