chore(docs): switching from HTTP to HTTPS

Author: rodneyrehm

CHANGELOG.md

@@ -1,23 +1,23 @@
 
 # ally.js goals
 
-The ultimate goal is to make the development of apps adhering to [WAI-ARIA](http://www.w3.org/TR/wai-aria/) a breeze. The ultimatest™ goal is to make this library obsolete by lobbying the W3C and browser vendors into supporting the basic tools provided by ally.js. (One may dream…)
+The ultimate goal is to make the development of apps adhering to [WAI-ARIA](https://www.w3.org/TR/wai-aria/) a breeze. The ultimatest™ goal is to make this library obsolete by lobbying the W3C and browser vendors into supporting the basic tools provided by ally.js. (One may dream…)
 
-Applications have to deal with quite a number of different issues to get to a state we may call "accessible." There's the issue of *maintaining the focus*, a subset of providing *keyboard navigation*. Then there's [WAI-ARIA](http://www.w3.org/TR/wai-aria/), which helps the browser provide the operating system's Accessibility Infrastructure with the necessary details.
+Applications have to deal with quite a number of different issues to get to a state we may call "accessible." There's the issue of *maintaining the focus*, a subset of providing *keyboard navigation*. Then there's [WAI-ARIA](https://www.w3.org/TR/wai-aria/), which helps the browser provide the operating system's Accessibility Infrastructure with the necessary details.
 
-Documents like [WAI-ARIA Authoring Practices](http://www.w3.org/WAI/PF/aria-practices/) try to explain what needs to be done, but even though the documents have been "dumbed down", they're still too convoluted to allow quickly understanding things. With `ally.js` we want to take that *document* and turn it into generic, reusable *JavaScript*.
+Documents like [WAI-ARIA Authoring Practices](https://www.w3.org/WAI/PF/aria-practices/) try to explain what needs to be done, but even though the documents have been "dumbed down", they're still too convoluted to allow quickly understanding things. With `ally.js` we want to take that *document* and turn it into generic, reusable *JavaScript*.
 
 It does not make sense to implement the same things over and over again, which is why `ally.js` is designed in a way that exposes every function individually (i.e. it is "modular"), to allow simple integration in other libraries. The modularity is paramount for preventing application and library authors from copy-pasting code, or worse, rolling their own flawed implementations. While ally.js is not perfect (it's software, it's written by me, …), I want to make this *the place we focus our efforts* - much like has happened for the DOM by way of jQuery.
 
 With ally.js v1.0.0 I've laid the foundation for a library solving the "stupid problems" (like "what is focusable?") so developers won't have to anymore. Here are the topics I'd cover next (not necessarily in that order) and would love your support:
 
 * [x] simplify managing focus
 * [x] simplify basic keyboard interaction (`enter`, `escape`, `space`)
-* [ ] implement a DOM based interface to simplify handling [WAI-ARIA state attributes](http://www.w3.org/TR/wai-aria/states_and_properties) (along the lines of [IBM-Watson/a11y.js](https://github.com/IBM-Watson/a11y.js))
+* [ ] implement a DOM based interface to simplify handling [WAI-ARIA state attributes](https://www.w3.org/TR/wai-aria/states_and_properties) (along the lines of [IBM-Watson/a11y.js](https://github.com/IBM-Watson/a11y.js))
   * easily creating unique-IDs for linking elements e.g. `<label for="uniq-123">…</label><input id="uniq-123">`
   * toggling states
   * easy support for multiple-id-values, e.g. `aria-labeledby="id-1 id-2 id-3"` possibly via [DOMTokenList](https://dom.spec.whatwg.org/#interface-domtokenlist), e.g. via [tokenlist](https://github.com/rodneyrehm/tokenlist)
-* [ ] implement a keyboard command abstraction that maps the keyboard interactions suggested by [WAI-ARIA Authoring Practices](http://www.w3.org/WAI/PF/aria-practices/) (e.g. [Listbox](http://www.w3.org/WAI/PF/aria-practices/#Listbox)) to [Indie UI Event Triggers](https://w3c.github.io/indie-ui/indie-ui-events.html#triggers)
+* [ ] implement a keyboard command abstraction that maps the keyboard interactions suggested by [WAI-ARIA Authoring Practices](https://www.w3.org/WAI/PF/aria-practices/) (e.g. [Listbox](https://www.w3.org/WAI/PF/aria-practices/#Listbox)) to [Indie UI Event Triggers](https://w3c.github.io/indie-ui/indie-ui-events.html#triggers)
 * [ ] implement the corresponding [Indie UI Event Actions](https://w3c.github.io/indie-ui/indie-ui-events.html#actions) against DOM elements depending on their `role="…"` attribute
 
 ---

GOALS.md

@@ -22,9 +22,9 @@ ally.js is a JavaScript library simplifying certain accessibility features, func
 
 ## Requirements
 
-* [ES5](http://kangax.github.io/compat-table/es5/)
+* [ES5](https://kangax.github.io/compat-table/es5/)
 * [ES6 Array.prototype.findIndex](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/findIndex)
-* [CSSOM CSS.escape](https://developer.mozilla.org/en-US/docs/Web/API/CSS.escape) ([spec](http://dev.w3.org/csswg/cssom/#the-css.escape%28%29-method))
+* [CSSOM CSS.escape](https://developer.mozilla.org/en-US/docs/Web/API/CSS.escape) ([spec](https://dev.w3.org/csswg/cssom/#the-css.escape%28%29-method))
 * [Element.classList](https://developer.mozilla.org/en/docs/Web/API/Element/classList)
 
 
@@ -38,7 +38,7 @@ ally.js is a JavaScript library simplifying certain accessibility features, func
 
 ## Resources
 
-* [Website](http://allyjs.io/)
+* [Website](https://allyjs.io/)
 * [Documentation](docs/README.md)
 * [CONTRIBUTING.md](CONTRIBUTING.md) explaining how to author, test, document and build ally.js
 * [CHANGELOG.md](CHANGELOG.md) detailing what changed over time
@@ -47,14 +47,14 @@ ally.js is a JavaScript library simplifying certain accessibility features, func
 
 ## Supported by
 
-* [BrowserStack](http://browserstack.com) and [SauceLabs](http://saucelabs.com/) provide VMs for automated testing - free for open source projects.
+* [BrowserStack](https://browserstack.com) and [SauceLabs](https://saucelabs.com/) provide VMs for automated testing - free for open source projects.
 * [Code Climate](https://codeclimate.com/github/medialize/ally.js) and [Coveralls](https://coveralls.io/github/medialize/ally.js/) provide us with automated code analysis and coverage reports - free for open source projects.
 * [Travis CI](https://travis-ci.org/medialize/ally.js) provides a build server - free for open source projects.
 
 
 ## License
 
-ally.js is published under the [MIT License](http://opensource.org/licenses/mit-license).
+ally.js is published under the [MIT License](https://opensource.org/licenses/mit-license).
 
 
 [npm-image]: https://img.shields.io/npm/v/ally.js.svg

README.md

@@ -67,7 +67,7 @@ generateTableDocument({
   targetFile: path.resolve(targetDirectory, 'focusable.html'),
   title: 'Focusable Elements - Browser Compatibility Table',
   introduction: `<p>The following tables show which elements individual browsers consider focusable or tabbable (keyboard focusable).
-    The tables are based on the <a href="http://allyjs.io/tests/focusable/test.html">focusable test document</a>.</p>
+    The tables are based on the <a href="https://allyjs.io/tests/focusable/test.html">focusable test document</a>.</p>
     <p>Note that touch devices (without a physical keyboard) only show elements as tabbable (keyboard focusable),
     that can be navigated to through the on-screen keyboard (or "virtual keyboard").</p>`,
   skipExpected: false,
@@ -159,7 +159,7 @@ generateTableDocument({
   targetFile: path.resolve(targetDirectory, 'focusable.jquery.html'),
   title: 'Focusable Elements - jQuery UI Compatibility Table',
   introduction: `<p>The following tables show the differences between what browsers consider <a href="./focusable.html">focusable</a>
-    and what <a href="http://api.jqueryui.com/focusable-selector/">jQuery UI</a> identifies.</p>
+    and what <a href="https://api.jqueryui.com/focusable-selector/">jQuery UI</a> identifies.</p>
     <p>Note that touch devices (without a physical keyboard) only show elements as tabbable (keyboard focusable),
     that can be navigated to through the on-screen keyboard (or "virtual keyboard").</p>`,
   skipExpected: true,

build/data-tables/focusable-tables.js

@@ -51,7 +51,7 @@
     table:not(#sticky-table-header) + table thead {
       /*
         visually hide consecutive headers
-        see http://w3c.github.io/wai-tutorials/forms/labels/#note-on-hiding-elements
+        see https://w3c.github.io/wai-tutorials/forms/labels/#note-on-hiding-elements
       */
       position: absolute;
       width: 1px;

build/data-tables/templates/document.hbs

@@ -120,7 +120,7 @@ <h1 id="supported-by">Supported by</h1>
         <section>
           <ul>
             <li>
-              <a href="http://browserstack.com">BrowserStack</a> and <a href="http://saucelabs.com/">SauceLabs</a>
+              <a href="https://browserstack.com">BrowserStack</a> and <a href="https://saucelabs.com">SauceLabs</a>
               provide VMs for automated testing - <em>free for open source projects.</em>
             </li>
             <li>

build/metalsmith/index.html

@@ -17,7 +17,7 @@ const injectExamples = require('./plugins/inject-examples');
 const absoluteUrl = require('./plugins/absolute-url');
 
 const WEBSITE_ROOT = '/medialize/ally.js/';
-const WEBSITE_CANONICAL = 'http://allyjs.io/';
+const WEBSITE_CANONICAL = 'https://allyjs.io/';
 
 function getRedirectionMap() {
   // make sure legacy links are forwarded

build/metalsmith/metalsmith.js

@@ -1,5 +1,5 @@
 <footer>
-  <p>ally.js is published under the <a href="http://opensource.org/licenses/mit-license">MIT License</a>.</p>
+  <p>ally.js is published under the <a href="https://opensource.org/licenses/mit-license">MIT License</a>.</p>
   <p><a href="{{websiteRoot}}legal.html">Legal</a>, <a href="https://github.com/medialize/ally.js">Github</a>, <a href="https://twitter.com/allyjs_io">@allyjs_io</a>.</p>
   <p>Created By <a href="https://twitter.com/rodneyrehm">Rodney Rehm</a>.</p>
 </footer>

build/metalsmith/partials/site-footer.html

@@ -14,7 +14,7 @@
     absoluteUrl({ property: "websiteRoot", define: "/hello/world" })
 
     convert all URLs beginning with websiteRoot to relative URLs
-    absoluteUrl({ resolve: "/hello/world", canonical: "http://example.org/" })
+    absoluteUrl({ resolve: "/hello/world", canonical: "https://example.org/" })
 */
 
 // inspired by

build/metalsmith/plugins/absolute-url.js

@@ -26,4 +26,4 @@ layout: index.html
 
 ## License
 
-ally.js is published under the [MIT License](http://opensource.org/licenses/mit-license).
+ally.js is published under the [MIT License](https://opensource.org/licenses/mit-license).

docs/README.md

@@ -39,7 +39,7 @@ Many components work on the DOM. Components ingest elements identified by variou
 * array of [`HTMLElement`](https://developer.mozilla.org/en/docs/Web/API/HTMLElement)
 * [`NodeList`](https://developer.mozilla.org/en/docs/Web/API/NodeList)
 * [`HTMLCollection`](https://developer.mozilla.org/en/docs/Web/API/HTMLCollection)
-* [`jQuery`](http://api.jquery.com/jQuery/) instance
+* [`jQuery`](https://api.jquery.com/jQuery/) instance
 
 
 ## Focus identification exceptions

docs/api/concepts.md

@@ -10,7 +10,7 @@ Shifts focus away from an element if it currently has focus.
 
 ## Description
 
-The [`blur()`](https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/blur) method is available on all [`HTMLElement`](https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement). But this is not necessarily true for [`SVGElement`](https://developer.mozilla.org/en-US/docs/Web/API/SVGElement). Only Blink and WebKit expose the `blur()` method on SVG elements, Gecko, Trident and Edge do not. This will likely change once [SVG 2](http://www.w3.org/TR/SVG2/interact.html#Focus) is a thing. Until then `ally.element.blur()` tries to apply `HTMLElement.prototoype.blur` to `SVGElement`s. This only works for Internet Explorer 9 - 11, as Gecko and Edge actively prevent this.
+The [`blur()`](https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/blur) method is available on all [`HTMLElement`](https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement). But this is not necessarily true for [`SVGElement`](https://developer.mozilla.org/en-US/docs/Web/API/SVGElement). Only Blink and WebKit expose the `blur()` method on SVG elements, Gecko, Trident and Edge do not. This will likely change once [SVG 2](https://www.w3.org/TR/SVG2/interact.html#Focus) is a thing. Until then `ally.element.blur()` tries to apply `HTMLElement.prototoype.blur` to `SVGElement`s. This only works for Internet Explorer 9 - 11, as Gecko and Edge actively prevent this.
 
 According to [jQuery Bug 9420](https://bugs.jqueryui.com/ticket/9420) calling `blur()` on the `body` element may make the browser window lose focus. `ally.element.blur()` guards against this.
 

docs/api/element/blur.md

@@ -76,8 +76,8 @@ var isDisabled = ally.element.disabled(element);
 * [`ally.is.disabled`](../is/disabled.md) is able to identify elements disabled by [`ally.element.disabled`](#ally.element.disabled)
 * [`ally.maintain.disabled`](../maintain/disabled.md) is a [service](../concepts.md#Service) finding focusable elements and disabling them within the DOM
 
-* [HTML5: Disabled Elements](http://www.w3.org/TR/html5/disabled-elements.html#disabled-elements)
-* [WICG: Adding a [disabled] attribute to `<a>`s](http://discourse.wicg.io/t/adding-a-disabled-attribute-to-a-s/1116)
+* [HTML5: Disabled Elements](https://www.w3.org/TR/html5/disabled-elements.html#disabled-elements)
+* [WICG: Adding a [disabled] attribute to `<a>`s](https://discourse.wicg.io/t/adding-a-disabled-attribute-to-a-s/1116)
 
 
 ## Contributing

docs/api/element/disabled.md

@@ -18,7 +18,7 @@ The [`Element.focus()`](https://developer.mozilla.org/en-US/docs/Web/API/HTMLEle
 </a>
 ```
 
-While `focus()` is available on `HTMLElement`, this is not necessarily true for [`SVGElement`](https://developer.mozilla.org/en-US/docs/Web/API/SVGElement). Only Blink and WebKit expose the `focus()` method on SVG elements, Gecko, Trident and Edge do not. This will likely change once [SVG 2](http://www.w3.org/TR/SVG2/interact.html#Focus) is a thing. Until then `ally.element.focus()` tries to apply `HTMLElement.prototoype.focus` to `SVGElement`s. This only works for Internet Explorer 9 - 11, as Gecko and Edge actively prevent this.
+While `focus()` is available on `HTMLElement`, this is not necessarily true for [`SVGElement`](https://developer.mozilla.org/en-US/docs/Web/API/SVGElement). Only Blink and WebKit expose the `focus()` method on SVG elements, Gecko, Trident and Edge do not. This will likely change once [SVG 2](https://www.w3.org/TR/SVG2/interact.html#Focus) is a thing. Until then `ally.element.focus()` tries to apply `HTMLElement.prototoype.focus` to `SVGElement`s. This only works for Internet Explorer 9 - 11, as Gecko and Edge actively prevent this.
 
 Browsers [scroll the focused element into view](https://github.com/whatwg/html/issues/94), if it isn't already. However, this may interfere with widgets revealing content in an animated fashion. As there is no way to focus an element *without* the browser scrolling the element into view, `ally.element.focus()` provides the option `undoScrolling` to revert all scroll containers of the focused element to their state before the element got focus.
 

docs/api/element/focus.md

@@ -12,7 +12,7 @@ Observes changes to `document.activeElement` regardless of focus/blur events and
 
 The property `document.activeElement` is visited on every [animation frame](https://developer.mozilla.org/en-US/docs/Web/API/window.requestAnimationFrame).
 
-This event should not be abused because `FocusEvent`s do not bubble and are therefore unaccessible to [event delegation](http://davidwalsh.name/event-delegate), as the handling of `focus` and `blur` events *can* be delegated when using the [capture phase](http://www.quirksmode.org/js/events_order.html):
+This event should not be abused because `FocusEvent`s do not bubble and are therefore unaccessible to [event delegation](https://davidwalsh.name/event-delegate), as the handling of `focus` and `blur` events *can* be delegated when using the [capture phase](http://www.quirksmode.org/js/events_order.html):
 
 ```js
 document.addEventListener('focus', function(event) {

docs/api/event/active-element.md

@@ -23,7 +23,7 @@ Considering the following markup, clicking on one of the `<span>` elements would
   }
 </style>
 
-<a href="http://example.org/" class="fancy-link">
+<a href="https://example.org/" class="fancy-link">
   <span>Hello</span>
   <span>World</span>
 </a>

docs/api/fix/pointer-focus-children.md

@@ -11,7 +11,7 @@ This *Browser Bug Workaround* targets an issue in Safari and Firefox **on Mac OS
 ## Description
 
 > In Firefox for Mac, Chrome and Safari, some types of form field don’t take the focus at all when clicked with the mouse; this behavior is limited to fields which have no typed input, such as radios, checkboxes, buttons, color-pickers and sliders.
-> -- [When Do Elements Take the Focus?](http://www.sitepoint.com/when-do-elements-take-the-focus/)
+> -- [When Do Elements Take the Focus?](https://www.sitepoint.com/when-do-elements-take-the-focus/)
 
 
 ## Usage

docs/api/fix/pointer-focus-input.md

@@ -14,7 +14,7 @@ Considering the following markup, clicking on the `<a>` element would focus the
 
 ```html
 <div tabindex="-1">
-  <a href="http://example.org/">Hello World</a>
+  <a href="https://example.org/">Hello World</a>
 </div>
 ```
 

docs/api/fix/pointer-focus-parent.md

@@ -10,7 +10,7 @@ Identifies the parent elements
 
 ## Description
 
-Like [`jQuery.parents()`](http://api.jquery.com/parents/), except [`ally.get.parents`](#ally.get.parents) doesn't have a filter arguments.
+Like [`jQuery.parents()`](https://api.jquery.com/parents/), except [`ally.get.parents`](#ally.get.parents) doesn't have a filter arguments.
 
 The returned list is sorted as follows `[element, element.parent, element.parent.parent, …]`
 

docs/api/get/parents.md

@@ -53,7 +53,7 @@ Boolean, `true` if the element is disabled.
 
 * [`ally.element.disabled`](../element/disabled.md) can disable *any* interactive element
 
-* [HTML5: Disabled Elements](http://www.w3.org/TR/html5/disabled-elements.html#disabled-elements)
+* [HTML5: Disabled Elements](https://www.w3.org/TR/html5/disabled-elements.html#disabled-elements)
 
 
 ## Contributing

docs/api/is/disabled.md

@@ -52,9 +52,9 @@ Boolean, `true` if the element is a valid area.
 
 ## Related resources
 
-* [HTML5: The Map Element](http://www.w3.org/TR/html5/embedded-content-0.html#the-map-element)
-* [HTML5: The Area Element](http://www.w3.org/TR/html5/embedded-content-0.html#the-area-element)
-* [HTML5: Image Maps](http://www.w3.org/TR/html5/embedded-content-0.html#image-maps)
+* [HTML5: The Map Element](https://www.w3.org/TR/html5/embedded-content-0.html#the-map-element)
+* [HTML5: The Area Element](https://www.w3.org/TR/html5/embedded-content-0.html#the-area-element)
+* [HTML5: Image Maps](https://www.w3.org/TR/html5/embedded-content-0.html#image-maps)
 
 
 ## Contributing

docs/api/is/valid-area.md

@@ -46,7 +46,7 @@ Boolean, `true` if the element is has a valid tabindex attribute specified.
 
 ## Related resources
 
-* [HTML5: The `tabindex` attribute](http://www.w3.org/TR/html5/editing.html#sequential-focus-navigation-and-the-tabindex-attribute)
+* [HTML5: The `tabindex` attribute](https://www.w3.org/TR/html5/editing.html#sequential-focus-navigation-and-the-tabindex-attribute)
 
 
 ## Contributing