WAI-ARIA tablist plugin based on AcceDe Web accessibility guidelines
npm install @accede-web/tablistWAI-ARIA tab plugin without dependencies.
Basic HTML structure with roles tablist, tab, and tabpanel.
#### HTML structure
``html
---
---
---
---
An
aria-disabled attribute set to true on a tab will disable the tab and the associated tabpanel making them unfocusable and unselectable.If you wish to open one specific tab when the script starts, just add the
data-open attribute with the value of true on the desired tab:`html
- Tab 1
- Tab 2
- Tab 3
- Tab 4
`$3
At least a CSS selector for panels to be hidden when not selected:
`css
[role=tabpanel][aria-hidden=true] {
display: none;
}
`The selector can be anything you want, like a class, as the script allows callback when opening or closing a panel; you can add your own class using the callbacks.
$3
The script itself, either from npm:
`bash
$ npm install @accede-web/tablist
`and later in your code:
`js
var Tablist = require( '@accede-web/tablist' );// or
import Tablist from @accede-web/tablist
`or downloaded from Github and added to the page (minified and non minified versions available in the
dist folder)`html
`Using the later, the script will be available on
window under the namespace Tablist.Now to kick off the script:
`js
// get the tablist element
var list = document.querySelector( '[role="tablist"]' );// create the tablist instance
var tablist = new window.Tablist( list );
// optionnaly add callbacks to on show and hide a tab
tablist.on( 'show', function( tab, tabPanel ){
…
});
tablist.on( 'hide', function( tab, tabPanel ){
…
});
// start the plugin
tablist.mount();
`Parameters
The script takes one parameter:
* the
tablist DOM elementAs the script takes only one
tablist element as parameter you have to loop over each tablist to kick off the script on each of them.`js
var lists = document.querySelectorAll( '[role="tablist"]' );Array.prototype.forEach.call( lists, function( list ) {
new window.Tablist( list ).mount();
});
`Methods
The
Tablist constructor returns 4 methods:*
mount() - bind all events and apply required attributes
* unmount() - unbind keyboard and mouse events
* on( event, callback ) - bind a callback to either the show or hide event triggered when changing tab. Both tab and tabPanel HTMLElement are passed on the callback
* off( event, callback ) - unbind a callback to either the show or hide event triggered when changing tabProperties
To know which
tab and tabPanel is open use tablist.current. It will return an array containing tab and tabPanel`js
// ES6 destructuring array
const { tab, tabPanel } = tablist.current;tab; // return the
tab
tabPanel; // return the tabPanel// ES5
var elements = tablist.current;
elements.tab; // return the
tab
elements.tabPanel; // return the tabPanel
`Keyboard Interaction
The keyboard interactions are based on Atalan's AcceDe Web guidelines (in French) and the WAI-AIRA 1.0 Authoring Practices
*
Tab - only the active tab is in the tab order. The user reaches the tabbed panel component by pressing the tab key until the active tab title receives focus.
* Left Arrow - with focus on a tab, pressing the left arrow will move focus to the previous tab in the tab list and activate that tab. Pressing the left arrow when the focus is on the first tab in the tab list will move focus and activate the last tab in the list.
* Right Arrow - with focus on a tab, pressing the right arrow will move focus to the next tab in the tab list and activate that tab. Pressing the right arrow when the focus is on the last tab in the tab list will move focus to and activate the first tab in the list.
* Up arrow - behaves the same as left arrow in order to support vertical tabs.
* Down arrow - behaves the same as right arrow in order to support vertical tabs.
* Home - with focus on a tab, pressing the Home key will move the focus to the first tab
* End - with focus on a tab, pressing the End key will move the focus to the last tab
* Control+Up Arrow - with focus anywhere within the tab panel, pressing Control+Up Arrow will move focus to the tab for that panel. This is not standard behavior.
* Control+PageUp - When focus is inside of a tab panel, pressing Control+PageUp moves focus to the tab of the previous tab in the tab list and activates that tab. When focus is in the first tab panel in the tab list, pressing Control+PageUp will move focus to the last tab in the tab list and activate that tab.
* Control+PageDown When focus is inside of a tab panel, pressing Control+PageDown moves focus to the tab of the next tab in the tab list and activates that tab. When focus is in the last tab panel in the tab list, pressing Control+PageUpwill move focus to the first tab in the tab list and activate that tab.
Compatibilty
This plugin is tested against the following browsers:
* Internet Explorer 9 and higher
* Microsoft Edge
* Chrome
* Firefox
* Safari
Testing
Install the project dependencies:
`bash
$ npm install
`Run the automated test cases:
`bash
$ npm test
``