[PointerReaper]

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.