PointerReaper

Lots when you consider that almost everyone on every platform has a PDF reader to work with that signature, whereas not many people have GPG or GPG tools that are friendly to the non-technical users.

You might consider some people won't be able to use this calendar as-is; it isn't accessible. Consider http://www.456bereastreet.com/archive/201302/making_elements... and perhaps change the spans to native HTML elements with visual and keyboard focus. Thanks for sharing!

Still not seeing any technical details about if this is a native implementation of Android or virtualized with QNX. One of the key issues with their past approach was lack of any accessibility at the system API level. I wonder if they will be blocking or interfering with native Android app accessibility.

Do you think teams will be able to leverage the same spatial visual information to provide or pair with technologies for spatial audio?

A lot of the game libraries assume and need 3d rendering in order to provide proper sound blocking (from objects) and in scene spatial depth. Having that concept considered in these experiments would perhaps provide for novel and consistent ways for people who are blind or low vision to gain awareness of the scenes (if audio can be attached by design or even by user preference) and augment or improve usability (end-user enjoyment?) if provided.

I hope they find a way to add this to a portable device for end users. Here in DC I've suspected the air in the metro stations (underground train) is many times worse than the above ground sampling.

Just wondering if this library provided keyboard access only manipulation, would you have expected it to provide mouse events?

I'm biased on the keyboarding should be required perspective: I deal with accessibility day in and day out, and a library such as this had to be ripped out and removed from the organization, simply because junior developers would prototype and ship without thinking about that required use-case of keyboard access.

Open access is a recurring problem, addressed to some degree with presidential orders. You might be interested in FASTR (Fair Access to Science and Technology Research Act): https://plus.google.com/u/0/+PeterSuber/posts/G2uebVhVtBv

In my line of accessibility work, I find QA fills the role of testing to educate. If the engineers don't have the experience, looping issues into the backlog, gives them the experience to train up the skill set. They might have had verified experience before hiring, but getting team collaboration helps mature new people or smooth out the rough skill sets of a dev who might be awesome in one particular area but meh in others.

I suspect this could be the case for any subject matter expert where the skill set is viewed as fringe or not expecting the team will be required to have that exact knowledge before hire.

I'm not confused as to why, but there is pretty good summaries out there: http://josefprusa.cz/open-hardware-meaning/ - all comes down to trying to market to, and mangle the definition of open source hardware IMHO.

I wish they would have better explored "2. People Have Limitations" via mental models and not been biased by "(as humans are 90% visual creatures)." Designing for and separating visuals from content can strengthen not only the user experience, but make accessibility elegant, instead of simply possible.

The most frugal approach might be to consider a trackball, followed by a full computer drawing table (e.g., http://goo.gl/qlHnlz or equivalent). Depends on the nature of her tremor or shake. Alternatively, get her a gaming mouse and turn the dpi sensitivity all the way up such that any movement is translated into minute screen movements.

There are dedicated hardware vendors, found on rehab sites such as http://www.rehabmart.com/product/adapted-wireless-computer-m... that you might consider browsing. I had a link to a product that seems to have gone out of business - it was an adapter that autoaveraged input coordinates to tone down tremors.

Finally, keeping all the keyboard shortcuts handy - http://community.linuxmint.com/tutorial/view/45 or https://support.google.com/chromebook/answer/183101?hl=en might help her.

Best of luck!

Based on end-user experience during accessibility testing, I'm pretty sure they do detect the presence of tools such as AdBlock, test to see if certain elements were successfully provided before continuing with a specific set of ads, and also make some assumptions about providing "errors" to end users that only people with something like AdBlock or NoScript _should_ see.

It would be interesting to see the same sort of diagram and discussion in the linked article that includes what happens when end users are using the AdBlock or Hosts block techniques.

Good work!

Could be better, as no accessibility for people with disabilities referenced at a technical conformance level: this needs to be a part of the guidelines.

Keyboard access (e.g., http://www.linuxfoundation.org/collaborate/workgroups/access...) should be a part of the overall guidelines, even without annotation to support of accessibility. This should include visual focus, as well as well defined default keyboard shortcuts, where supported by the operating system, window manager, or application conventions.

At a deeper level, concepts of textual representation of the user interface via Name, Role, State, etc. need to be conveyed. Language used in this guide that is heavily visual centric should be considered and revised if it leads end developers to ONLY think of visual situations, or encourages them to ignore accessibility.

How do you expect people to do this from a keyboard?

I really wonder about the utility of something like this tool. I enjoy and encourage building new things "just because" but I can help but think the point to PDFs is to have complete visual control of layout and formatting while providing the textual and tagging information layers is critical to transform and adapt the information for artificial intelligent agents and people with disabilities that rely upon assistive technologies such as screen readers.

OMG! I can improve the audio 200% by simply setting: pactl set-sink-volume alsa_output.pci-0000_00_1b.0.analog-stereo 200%

Teh sound is so much more sound-ier! Way much more cranked up than the lame defaults! http://goo.gl/TJLTMF

http://amara.readthedocs.org/en/latest/index.html (Amara: Create Captions and Subtitles) might be of interest to you.

For the small startup Mike Monteiro: F*ck You, Pay Me ; https://www.youtube.com/watch?v=jVkLVRt6c1U

It is certainly not backwards compatibility. Every internal review of Microsoft systems within the government indicates they upgrade whenever possible, even to the detriment of keeping versions that "just work". That is one of the frustrating things about succcesses in deployment of open source: a mindset that still wants to put out the latest version due to features and "coolness" instead of patching and keeping stability that would ultimately save money.

One of the biggest reasons isn't just the licensing and individual system, but the supporting systems and processes: certification and accreditation processes for security, ability to only pay for one year at a time due to legalities of budget constraints, and items such as mandated ediscovery systems that are tied to the OS and systems architecture they are designed for using. It takes a great deal of experience, planning, and foresight to decouple services and make removal and swap out of key pieces open and even possible to change out. Add to that active defaults by vendors that encourages lock-in as well as the failure to draw in expertise that would survive in such an environment, equates to mediocrity in IT.