[update] - Update docs for use-onblur-not-onchange (#32)

* [update] - Update docs for use-onblur-not-onchange

In meantime of discussion on #31, just update the docs to explain
motivation for lint rule.

* [new] - Add total downloads badge

Just for fun for me to see growth :)

Author: beefancohen

README.md

@@ -14,6 +14,10 @@
   <a href='https://coveralls.io/github/evcohen/eslint-plugin-jsx-a11y?branch=master'>
     <img src='https://coveralls.io/repos/github/evcohen/eslint-plugin-jsx-a11y/badge.svg?branch=master' alt='Coverage Status' />
   </a>
+  <a href='https://npmjs.org/package/eslint-plugin-jsx-a11y'>
+    <img src='https://img.shields.io/npm/dt/eslint-plugin-jsx-a11y.svg?maxAge=2592000'
+    alt='Total npm downloads' />
+  </a>
 </p>
 
 # eslint-plugin-jsx-a11y

docs/rules/use-onblur-not-onchange.md

@@ -1,6 +1,10 @@
 # use-onblur-not-onchange
 
-Enforce usage of onBlur over onChange for accessibility. onBlur must be used instead of onChange, unless absolutely necessary and it causes no negative consequences for keyboard only or screen reader users.
+Enforce usage of `onBlur` over/in parallel with `onChange` for accessibility. `onBlur` **should** be used instead of `onChange`, unless absolutely necessary and it causes no negative consequences for keyboard only or screen reader users. `onBlur` is a more declarative action by the user: for instance in a dropdown, using the arrow keys to toggle between options will trigger the `onChange` event in some browsers. Regardless, when a change of context results from an `onBlur` event or an `onChange` event, the user should be notified of the change unless it occurs below the currently focused element.
+
+#### References
+1. [onChange Event Accessibility Issues](http://cita.disability.uiuc.edu/html-best-practices/auto/onchange.php)
+2. [onChange Select Menu](http://www.themaninblue.com/writing/perspective/2004/10/19/)
 
 ## Rule details
 
@@ -15,4 +19,4 @@ This rule takes no arguments.
 ### Fail
 ```jsx
 <input onChange={updateModel} />
-```
+```