[Docs] HTTP => HTTPS

Author: Schweinepriester

README.md

@@ -41,7 +41,7 @@ Ryan Florence built out this awesome runtime-analysis tool called [react-a11y](h
 
 **If you are installing this plugin via `eslint-config-airbnb`, please follow [these instructions](https://github.com/airbnb/javascript/tree/HEAD/packages/eslint-config-airbnb#eslint-config-airbnb-1).**
 
-You'll first need to install [ESLint](http://eslint.org):
+You'll first need to install [ESLint](https://eslint.org):
 
 ```sh
 # npm

docs/rules/accessible-emoji.md

@@ -23,4 +23,4 @@ This rule takes no arguments.
 - [WCAG 1.1.1](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content.html)
 
 ### Resources
-- [Léonie Watson, Accessible Emoji](http://tink.uk/accessible-emoji/)
+- [Léonie Watson, Accessible Emoji](https://tink.uk/accessible-emoji/)

docs/rules/anchor-is-valid.md

@@ -261,6 +261,6 @@ Invalid `href` attribute:
 
 ### Resources
 
-- [WebAIM - Introduction to Links and Hypertext](http://webaim.org/techniques/hypertext/)
+- [WebAIM - Introduction to Links and Hypertext](https://webaim.org/techniques/hypertext/)
 - [Links vs. Buttons in Modern Web Applications](https://marcysutton.com/links-vs-buttons-in-modern-web-applications/)
 - [Using ARIA - Notes on ARIA use in HTML](https://www.w3.org/TR/using-aria/#NOTES)

docs/rules/no-access-key.md

@@ -3,7 +3,7 @@
 Enforce no accessKey prop on element. Access keys are HTML attributes that allow web developers to assign keyboard shortcuts to elements. Inconsistencies between keyboard shortcuts and keyboard commands used by screenreaders and keyboard-only users create accessibility complications so to avoid complications, access keys should not be used.
 
 ### References
-1. [WebAIM](http://webaim.org/techniques/keyboard/accesskey#spec)
+1. [WebAIM](https://webaim.org/techniques/keyboard/accesskey#spec)
 
 ## Rule details
 
@@ -23,4 +23,4 @@ This rule takes no arguments.
 General best practice (reference resources)
 
 ### Resources
-- [WebAIM, Keyboard Accessibility: Accesskey](http://webaim.org/techniques/keyboard/accesskey#spec)
+- [WebAIM, Keyboard Accessibility: Accesskey](https://webaim.org/techniques/keyboard/accesskey#spec)

docs/rules/no-noninteractive-element-interactions.md

@@ -57,7 +57,7 @@ Headers often double as expand/collapse controls for the content they headline.
 
 ### Case: This element is a table cell
 
-Table cells (and tables in general) are meant to contain data. ARIA provides us with a construct called a [Grid](http://w3c.github.io/aria-practices/#grid) that is essentially a 2 dimensional logical container for content and interactive elements.
+Table cells (and tables in general) are meant to contain data. ARIA provides us with a construct called a [Grid](https://w3c.github.io/aria-practices/#grid) that is essentially a 2 dimensional logical container for content and interactive elements.
 
 You have two options in this case.
 

docs/rules/no-onchange.md

@@ -28,5 +28,5 @@ This rule takes no arguments.
 - [WCAG 3.2.2](https://www.w3.org/WAI/WCAG21/Understanding/on-input)
 
 ### Resources
-- [onChange Event Accessibility Issues](http://cita.disability.uiuc.edu/html-best-practices/auto/onchange.php)
-- [onChange Select Menu](http://www.themaninblue.com/writing/perspective/2004/10/19/)
+- [onChange Event Accessibility Issues](https://web.archive.org/web/20191207202425/http://cita.disability.uiuc.edu/html-best-practices/auto/onchange.php)
+- [onChange Select Menu](https://www.themaninblue.com/writing/perspective/2004/10/19/)