Note to myself

After generating through yeoman, generally do
npm install and bower update before running any grunt tasks, otherwise it probably will come back with some error messages.

More details about this here: (this is for official backbone generator from Yeoman.io)
http://www.justinmccandless.com/blog/Getting+a+Yeoman+App+Working+on+a+New+Machine+after+Cloning
and here
https://github.com/gruntjs/grunt-contrib-compass/issues/194

Literally pulled hair out because of this stupid issue…

ScreenReader issues with AJAX and Role=”Status”

When focusing on element with role=”status” tag, before and after AJAX call with JavaScript, both JAWS and VoiceOver will finish reading the element with role=”status” tag.

Where mobile accessibility tools (VoiceOver on iOS devices, and Talkback on Android devices”) will cut off in middle while it’s reading element with role=”status”

Maybe this is reproducible with regular javascript focusing on element with timeout, instead of ajax call. need to investigate.

Also, there’s no way to detect if the user is using screen readers, so there’s need for detect each browser / OS as almost every screen reader / browser combination behave differently even if you follow WCAG2.0 AAA compliance.

There’s debate about to whether open up API or not: (well at least some surveys)
http://webaim.org/projects/screenreadersurvey5/#srdetection