Renamed a number of rules that were equivalent to existing rules in the eslint-plugin-jsx-a11y library for consistency between the two libs

Author: Erin Doyle

docs/rules/valid-aria-role.md docs/rules/aria-role.mddocs/rules/valid-aria-role.md renamed to docs/rules/aria-role.md

@@ -1,4 +1,4 @@
-# valid-aria-role
+# aria-role
 
 The ARIA roles model requires that elements with a role attribute use a valid,
 non-abstract ARIA role. Each non-abstract ARIA role is mapped on to a known set
@@ -16,7 +16,7 @@ on additional required attributes, on the
 
 ## Passes
 
-```js
+```jsx harmony
 // passes when there is a role and it is valid
 <div role="button"></div>
 
@@ -26,7 +26,7 @@ on additional required attributes, on the
 
 ## Fails
 
-```js
+```jsx harmony
 // fails when there is an invalid `role`
 <div role="foo"></div>
 ```

…ules/no-unsupported-elements-use-aria.md docs/rules/aria-unsupported-elements.mddocs/rules/no-unsupported-elements-use-aria.md renamed to docs/rules/aria-unsupported-elements.md docs/rules/no-unsupported-elements-use-aria.md renamed to docs/rules/aria-unsupported-elements.md

@@ -1,4 +1,4 @@
-# no-unsupported-elements-use-aria
+# aria-unsupported-elements
 
 
 Certain reserved DOM elements do not support ARIA roles, states and properties.
@@ -14,8 +14,8 @@ This is often because they are not visible, for example `meta`, `html`, `script`
 ## Passes
 
 These elements are passed by this rule
-```js
-// no problem when the reserver element is not given an illegal prop
+```jsx harmony
+// no problem when the reserved element is not given an illegal prop
 <meta/>
 
 // no problem when an illegal props is given to a non-reserved elemeent
@@ -25,11 +25,11 @@ These elements are passed by this rule
 ## Fails
 
 These elements are *not* passed by this rule
-```js
+```jsx harmony
 // warns when the element should not be given any ARIA attributes
 <meta aria-hidden="false"/>
 ```
 
 ## See also
 
- - Google Audit defs [AX_ARIA_12](https://github.com/GoogleChrome/accessibility-developer-tools/wiki/Audit-defs#ax_aria_12)
+ - Google Audit defs [AX_ARIA_12](https://github.com/GoogleChrome/accessibility-developer-tools/wiki/Audit-defs#ax_aria_12)

docs/rules/hidden-uses-tabindex.md

@@ -12,7 +12,7 @@ in a hidden tab stop for screen reader users.
 
 ## Passes
 
-```js
+```jsx harmony
 // passes when an interactive element is aria-hidden and has tabindex="-1"
 <input aria-hidden="true" tabindex="-1"/>
 
@@ -25,7 +25,7 @@ in a hidden tab stop for screen reader users.
 
 ## Fails
 
-```js
+```jsx harmony
 // fails when an interactive element is hidden but has no tabindex
 <input aria-hidden="true"/>
 

docs/rules/redundant-alt.md docs/rules/img-redundant-alt.mddocs/rules/redundant-alt.md renamed to docs/rules/img-redundant-alt.md

@@ -1,4 +1,4 @@
-# redundant-alt
+# img-redundant-alt
 
 Enforce img alt attribute does not contain the word image, picture, or photo.
 Screenreaders already announce `img` elements as an image. There is no need to use
@@ -13,7 +13,7 @@ This rule takes the following options:
 
 ## Passes
 
-```js
+```jsx harmony
 // passes when the `alt` does not contain redundant words
 <img src="foo" alt="nice"/>
 
@@ -27,7 +27,7 @@ This rule takes the following options:
 
 ## Fails
 
-```js
+```jsx harmony
 // fails when is a redundant alt message
 <img src="foo" alt="bar image foo"/>
 

docs/rules/onclick-uses-tabindex.md docs/rules/interactive-supports-focus.mddocs/rules/onclick-uses-tabindex.md renamed to docs/rules/interactive-supports-focus.md

@@ -1,4 +1,4 @@
-# onclick-uses-tabindex
+# interactive-supports-focus
 
 Enforce that elements that have an `onClick` handler also have
 a `tabIndex` property.  If not, they will not be navigable by
@@ -11,22 +11,22 @@ keyboard users.
 
 ## Passes
 
-```js
+```jsx harmony
 // passes when when there is an `onClick` with a `tabIndex`
-<span tabindex="0"></span>
+<span onClick={someFunction} tabindex="0"></span>
 
 // passes when the element is hidden from aria
-<span aria-hidden="true"></span>
+<span onClick={someFunction} aria-hidden="true"></span>
 
 // passes when the element is interactive
-<button></button>
+<button onClick={someFunction}></button>
 ```
 
 ## Fails
 
-```js
+```jsx harmony
 // fails when there is an `onClick` with no `tabIndex`
-<span></span>
+<span onClick={someFunction}></span>
 ```
 
 ## See also

docs/rules/label-uses-for.md docs/rules/label-has-for.mddocs/rules/label-uses-for.md renamed to docs/rules/label-has-for.md

@@ -1,4 +1,4 @@
-# label-uses-for
+# label-has-for
 
 Enforce label tags have `htmlFor` attribute. Form controls using a `label` to
 identify them must have only one label that is programmatically associated with
@@ -11,7 +11,7 @@ the control using: `<label htmlFor={/* ID or name of control*/}>...</label>`.
 
 ## Passes
 
-```js
+```jsx harmony
 // passes when the label is hidden
 <label aria-hidden="true"></label>
 
@@ -24,7 +24,7 @@ the control using: `<label htmlFor={/* ID or name of control*/}>...</label>`.
 
 ## Fails
 
-```js
+```jsx harmony
 // fails when a label is not hidden and has no `htmlFor`
 <label></label>
 ```

…/rules/mouse-events-map-to-key-events.md …cs/rules/mouse-events-have-key-events.mddocs/rules/mouse-events-map-to-key-events.md renamed to docs/rules/mouse-events-have-key-events.md docs/rules/mouse-events-map-to-key-events.md renamed to docs/rules/mouse-events-have-key-events.md

@@ -1,4 +1,4 @@
-# mouse-events-map-to-key-events
+# mouse-events-have-key-events
 
 Enforce `onMouseOver`/`onMouseOut` are accompanied by
 `onFocus`/`onBlur`. Coding for the keyboard is important for users with
@@ -12,25 +12,25 @@ users.
 
 ## Passes
 
-```js
+```jsx harmony
 // passes when there is no `onMouseOver` or `onMouseOut`
 <div></div>
 
-// passes when there is `onMouseOver` but and `onFocus`
-<div></div>
+// passes when there is `onMouseOver` and `onFocus`
+<div onMouseOver={someFunction} onFocus={someFunction}></div>
 
-// passes when there is `onMouseOut` but and `onBlur`
-<div></div>
+// passes when there is `onMouseOut` and `onBlur`
+<div onMouseOut={someFunction} onBlur={someFunction}></div>
 ```
 
 ## Fails
 
-```js
+```jsx harmony
 // fails when there is `onMouseOver` but no `onFocus`
-<div></div>
+<div onMouseOver={someFunction}></div>
 
 // fails when there is `onMouseOut` but no `onBlur`
-<div></div>
+<div onMouseOut={someFunction}></div>
 ```
 
 ## See also

docs/rules/use-onblur-not-onchange.md docs/rules/no-onchange.mddocs/rules/use-onblur-not-onchange.md renamed to docs/rules/no-onchange.md

@@ -1,4 +1,4 @@
-# use-onblur-not-onchange
+# no-onchange
 
 Enforce usage of onBlur over onChange for accessibility. onBlur must be used
 instead of onChange, unless absolutely necessary and it causes no negative
@@ -11,25 +11,28 @@ consequences for keyboard only or screen reader users.
 
 ## Passes
 
-```js
+```jsx harmony
 // passes when there is no `onChange` prop
 <input/>
 
 // passes when the element is aria-hidden
-<input aria-hidden="true"/>
+<input onChange={fn} aria-hidden="true"/>
 
 // passes when the element is aria-disabled
-<input aria-disabled="true"/>
+<input onChange={fn} aria-disabled="true"/>
 
 // passes when the element is aria-readonly
-<input aria-readonly="true"/>
+<input onChange={fn} aria-readonly="true"/>
+
+// passes when there is an `onChange` prop and an `onBlur` prop
+<input onChange={fn} onBlur={fn}/>
 ```
 
 ## Fails
 
-```js
-// fails when the `onChange` prop is present
-<input/>
+```jsx harmony
+// fails when the `onChange` prop is present without an `onBlur` prop
+<input onChange={fn}/>
 ```
 
 ## See also