govuk_publishing_components 30.4.1 → 30.5.2

data/node_modules/axe-core/doc/rule-development.md

@@ -1,123 +0,0 @@
-# Developing Axe-core Rules
-
-Before you start writing axe-core rules, be sure to create a proposal for them in a github issue. Read [Proposing Axe-core rules](./rule-proposal.md) for details.
-
-A rule is a JSON Object that defines a test for axe-core to run. At a high level, think of a rule as doing two things. First it finds all elements that it should test, and after that it runs a number of checks to see if those selected elements pass or fail the rule.
-
-## Rule Select and Matches
-
-Each rule has a 'selector' and optionally a 'matches' property. The selector is a CSS selector. Each element matching this selector will be tested by the rule, unless the matches function says otherwise. The `matches` property is a reference to a function that returns a boolean, which indicates if the element should be tested.
-
-The last thing that may influence if an element is selected for testing in the rule is it's visibility. By default, hidden elements are ignored by the rule, unless the `excludeHidden` is set to 'false'.
-
-## Using Checks in Rules
-
-The actual testing of elements in axe-core is done by checks. A rule has one or more checks which end up generating a result. There are three properties with which to define a rule's checks. Each of them deals differently:
-
-- **All**: Takes an array of check names, **all** of which has to return true for the rule to pass.
-- **none**: Takes an array of check names, **none** of which can to return true for the rule to pass.
-- **any**: Takes an array of check names, **at least one** of which has to return true for the rule to pass.
-
-## Rule Properties
-
-| Prop. Name           | Description                                                         |
-| -------------------- | ------------------------------------------------------------------- |
-| id                   | Unique identifier for the rule                                      |
-| selector             | CSS Selector that matches elements to test                          |
-| matches              | Function to further filter the outcome of the selector              |
-| excludeHidden        | Should hidden elements be excluded                                  |
-| all                  | Checks that must all return true                                    |
-| any                  | Checks of which at least one must return true                       |
-| none                 | Checks that must all return false                                   |
-| pageLevel            | Should the rule only run on the main window                         |
-| enabled              | Does the rule run by default                                        |
-| tags                 | Grouping for the rule, such as wcag2a, best-practice                |
-| metadata.description | Description of what a rule does                                     |
-| metadata.help        | Short description of a violation, used in the axe extension sidebar |
-
-## Check Properties
-
-| Prop. Name                   | Description                                    |
-| ---------------------------- | ---------------------------------------------- |
-| id                           | Unique identifier for the check                |
-| evaluate                     | Evaluating function, returning a boolean value |
-| options                      | Configurable value for the check               |
-| after                        | Cleanup function, run after check is done      |
-| metadata impact              | "minor", "serious", "critical"                 |
-| metadata.messages.pass       | Describes why the check passed                 |
-| metadata.messages.fail       | Describes why the check failed                 |
-| metadata.messages.incomplete | Describes why the check didn’t complete        |
-
-Incomplete results occur when axe-core can’t produce a clear pass or fail result,
-giving users the opportunity to review it manually. Incomplete messages can take
-the form of a string, or an object with arbitrary keys matching the data returned
-from the check.
-
-A pass message is required, while fail and incomplete are dependent on the check result.
-
-### Incomplete message string
-
-As one example, the audio and video caption checks return an incomplete string:
-
-```js
-messages: {
-  pass: 'Why the check passed',
-  fail: 'Why the check failed',
-  incomplete: 'Why the check returned undefined'
-}
-```
-
-### Incomplete message object with missingData
-
-As another example, the color-contrast check returns missingData to aid in
-remediation. Here’s the message format:
-
-```js
-messages: {
-  pass: 'Why the check passed',
-  fail: 'Why the check failed',
-  incomplete: {
-    bgImage: 'The background color could not be determined due to a background image',
-    default: 'fallback string'
-  }
-}
-```
-
-To wire up an incomplete message with a specific reason it returned undefined,
-the check needs matching data. Otherwise, it will fall back to the `default` message.
-Reasons are arbitrary for the check (such as 'bgImage') but they must match the
-data returned:
-
-```js
-this.data({
-	missingData: 'bgImage'
-});
-```
-
-# Hierarchical rules
-
-Axe-core handles shadow DOM and cross-domain iframe rules very well - as long as you take care in the design and implementation of your rule. Any rule that evaluates the DOM hierarchy needs to think about what happens across shadow DOM boundaries and iframe boundaries.
-
-The rule callbacks all receive both a `node` and a `virtualNode` argument (in addition to the `options` argument). `node` points to the DOM Node that is to be evaluated, whereas `virtualNode` points to the node in the flattened tree (the hierarchy that shadow DOM creates that is used for parent child relationships across shadow DOM boundaries).
-
-If your rule looks at any hierarchical context (parents or children) then you need to operate on the `virtualNode` for those operations. Calls to `isHidden` and the accessible name calculation calls will all evaluate the hierarchy. The commons and utils functions will all fetch the `virtualNode` from the flattened tree if you use the `node` implementation (and then simply call the virtualNode one) and are there for backwards compatibility. This backwards compatibility comes at a performance cost that can be avoided by simply using the `virtualNode` to start with. We will ask you to change this during PR review, so you might as well just start out by using the `virtualNode`.
-
-## iframes
-
-Rules that evaluate the structure and/or the number of elements on the entire page (for example the heading nesting rule, or the landmark rules) will need to do this evaluation across iframe boundaries. What this means is that the check function instead of determining pass/fail/incomplete, performs a data gathering function. This data is then passed up the iframe hierarchy to the top window where it is passed into the `after` function, which does the evaluation of the gathered data and determines pass/fail.
-
-## Rules of Thumb for Rule Code Reviewers
-
-Rules of thumb for determining whether `virtualNode` should be used - if any of the answers to the following questions is yes, then it should use shadow DOM and `virtualNode`:
-
-1. Is it using the non-virtualNode version of a function that wraps the flattened tree lookup?
-2. Is it evaluating the DOM hierarchy?
-
-Rules that do this MUST have shadow DOM test cases that show passes and fails across the shadow DOM boundary.
-
-Rules of thumb for determining whether an `after` function is required - if any of the answers to the following questions is yes:
-
-1. Does the rule evaluate number of things on a page?
-2. Does the rule evaluate hierarchy of things across a whole page?
-
-Rules that use an `after` function MUST have iframe test cases that assert correct data passing between iframes and handle all the relevant cases across iframes.

data/node_modules/axe-core/doc/rule-proposal.md

@@ -1,106 +0,0 @@
-# Proposing Axe-core Rules
-
-This document outlines the process of proposing a rule. For a technical description on how to build a rule, read [Developing Axe-core Rules](./rule-development.md)
-
-Before you start coding a new rule for axe-core, you _must_ create a Github issue to document the rule you want to create. There are many considerations to writing a good rule. It must have no false positives, which is difficult, because there are always many many edge cases to consider. Additionally, a known problem of accessibility testing, is that not all testers hold the same interpretation of the accessibility guidelines. All rules _must_ be consistent with the interpretation of Deque Systems, the developer behind Axe-core.
-
-In addition to giving the axe-core development team an opportunity to provide feedback on the proposed rule, the Github Issue will serve as documentation of that rule for the future.
-
-## WCAG interpretation
-
-Please read our [principles for deciding on rules](./accessibility-supported.md).
-
-## Rules Format
-
-All Github issues that propose a rule must be tagged as _rule_, and must use the following format:
-
-### Intro
-
-In one sentence, describe what the rule does.
-
-Example: "Ensures ARIA attributes are allowed for an element's role"\
-
-#### Rule help
-
-In one sentence, describe how to resolve the issue.
-
-Example: "Elements must only use allowed ARIA attributes"
-
-#### Tags
-
-Indicate which tags the rule should use.
-
-Example: wcag2a, wcag211, cat.keyboard
-
-### Selector
-
-If possible using a CSS selector, otherwise describe in one sentence using plain language what elements the rule selects.
-
-Example 1: `input[type=checkbox][name]`
-
-Example 2: Select each node that has an attribute starting with `aria-`.
-
-### Checks:
-
-Make each check a subheading of `checks`. Give the check name in the heading, and indicate if the check type is `any`, `all` or `none`.
-
-In short sentences, using plain language, describe what conditions will lead to the check returning false, true or undefined. Keep the steps simple and short. You don't have to write out all the logic. Preferably not, just give the high level view of what the check does.
-
-**Example 1:**
-
-`###` aria/allow-attr (any)
-
-1. Look up the element role
-2. Look up a list of aria attributes allowed for that role
-3. Return false if the element has aria attributes not in the list
-4. Otherwise return true
-
-**Example 2:**
-
-`###` keyboard/focusable-no-name (none)
-
-1. If the element is not in the focus order, return false
-2. If the element has an accessible name, return false
-3. Otherwise return true
-
-## Best practices
-
-For rule design, consider the following as best practices:
-
-1. Rules should only have one `none` check so that the error message is specific
-2. Rules should not combine `any` and `none`, these should be broken out into separate rules
-3. Checks should each only test a single specific case (either a passing technique or a single failing test)
-
-## Template
-
-Use this template when creating the issue:
-
-```markdown
-# {{ Rule name }}
-
-{{ Rule description }}
-
-{{ Rule help }}
-
-**Tags:** {{ tag, tag, tag }}
-
-## Selector
-
-{{ selector }}
-
-## Checks
-
-### {{ Check name 1 }} ( any / all / none )
-
-1.
-
-### {{ Check name 2, optional }} ( any / all / none )
-
-1.
-```
-
-## W3C Standardized Rules
-
-Deque Systems is one of leading organizations in the development of standardized accessibility conformance testing rules. The above format is an adaptation of the [Accessibility Conformance Testing Rules Format](https://www.w3.org/TR/act-rules-format/).
-
-For details on how the above format maps to the ACT Rules format, see [act-rules-format.md](./act-rules-format.md).

data/node_modules/axe-core/lib/checks/aria/abstractrole.js

@@ -1,10 +0,0 @@
-const abstractRoles = axe.utils
-	.tokenList(virtualNode.attr('role'))
-	.filter(role => axe.commons.aria.getRoleType(role) === 'abstract');
-
-if (abstractRoles.length > 0) {
-	this.data(abstractRoles);
-	return true;
-}
-
-return false;

data/node_modules/axe-core/lib/checks/aria/abstractrole.json

@@ -1,14 +0,0 @@
-{
-	"id": "abstractrole",
-	"evaluate": "abstractrole.js",
-	"metadata": {
-		"impact": "serious",
-		"messages": {
-			"pass": "Abstract roles are not used",
-			"fail": {
-				"singular": "Abstract role cannot be directly used: ${data.values}",
-				"plural": "Abstract roles cannot be directly used: ${data.values}"
-			}
-		}
-	}
-}

data/node_modules/axe-core/lib/checks/aria/allowed-attr.js

@@ -1,39 +0,0 @@
-options = options || {};
-
-var invalid = [];
-
-var attr,
-	attrName,
-	allowed,
-	role = node.getAttribute('role'),
-	attrs = axe.utils.getNodeAttributes(node);
-
-if (!role) {
-	role = axe.commons.aria.implicitRole(node);
-}
-
-allowed = axe.commons.aria.allowedAttr(role);
-
-if (Array.isArray(options[role])) {
-	allowed = axe.utils.uniqueArray(options[role].concat(allowed));
-}
-
-if (role && allowed) {
-	for (var i = 0, l = attrs.length; i < l; i++) {
-		attr = attrs[i];
-		attrName = attr.name;
-		if (
-			axe.commons.aria.validateAttr(attrName) &&
-			!allowed.includes(attrName)
-		) {
-			invalid.push(attrName + '="' + attr.nodeValue + '"');
-		}
-	}
-}
-
-if (invalid.length) {
-	this.data(invalid);
-	return false;
-}
-
-return true;

data/node_modules/axe-core/lib/checks/aria/allowed-attr.json

@@ -1,14 +0,0 @@
-{
-	"id": "aria-allowed-attr",
-	"evaluate": "allowed-attr.js",
-	"metadata": {
-		"impact": "critical",
-		"messages": {
-			"pass": "ARIA attributes are used correctly for the defined role",
-			"fail": {
-				"singular": "ARIA attribute is not allowed: ${data.values}",
-				"plural": "ARIA attributes are not allowed: ${data.values}"
-			}
-		}
-	}
-}

data/node_modules/axe-core/lib/checks/aria/aria-allowed-role.js

@@ -1,28 +0,0 @@
-/**
- * Implements allowed roles defined at:
- * https://www.w3.org/TR/html-aria/#docconformance
- * https://www.w3.org/TR/SVG2/struct.html#implicit-aria-semantics
- */
-const { dom } = axe.commons;
-const { allowImplicit = true, ignoredTags = [] } = options || {};
-const tagName = node.nodeName.toUpperCase();
-
-// check if the element should be ignored, by an user setting
-if (ignoredTags.map(t => t.toUpperCase()).includes(tagName)) {
-	return true;
-}
-
-const unallowedRoles = axe.commons.aria.getElementUnallowedRoles(
-	node,
-	allowImplicit
-);
-
-if (unallowedRoles.length) {
-	this.data(unallowedRoles);
-	if (!dom.isVisible(node, true)) {
-		// flag hidden elements for review
-		return undefined;
-	}
-	return false;
-}
-return true;

data/node_modules/axe-core/lib/checks/aria/aria-allowed-role.json

@@ -1,22 +0,0 @@
-{
-	"id": "aria-allowed-role",
-	"evaluate": "aria-allowed-role.js",
-	"options": {
-		"allowImplicit": true,
-		"ignoredTags": []
-	},
-	"metadata": {
-		"impact": "minor",
-		"messages": {
-			"pass": "ARIA role is allowed for given element",
-			"fail": {
-				"singular": "ARIA role ${data.values} is not allowed for given element",
-				"plural": "ARIA roles ${data.values} are not allowed for given element"
-			},
-			"incomplete": {
-				"singular": "ARIA role ${data.values} must be removed when the element is made visible, as it is not allowed for the element",
-				"plural": "ARIA roles ${data.values} must be removed when the element is made visible, as they are not allowed for the element"
-			}
-		}
-	}
-}

data/node_modules/axe-core/lib/checks/aria/aria-hidden-body.js

@@ -1 +0,0 @@
-return node.getAttribute('aria-hidden') !== 'true';

data/node_modules/axe-core/lib/checks/aria/aria-hidden-body.json

@@ -1,11 +0,0 @@
-{
-	"id": "aria-hidden-body",
-	"evaluate": "aria-hidden-body.js",
-	"metadata": {
-		"impact": "critical",
-		"messages": {
-			"pass": "No aria-hidden attribute is present on document body",
-			"fail": "aria-hidden=true should not be present on the document body"
-		}
-	}
-}

data/node_modules/axe-core/lib/checks/aria/aria-roledescription.js

@@ -1,14 +0,0 @@
-options = options || {};
-
-const role = axe.commons.aria.getRole(node);
-const supportedRoles = options.supportedRoles || [];
-
-if (supportedRoles.includes(role)) {
-	return true;
-}
-
-if (role && role !== 'presentation' && role !== 'none') {
-	return undefined;
-}
-
-return false;

data/node_modules/axe-core/lib/checks/aria/aria-roledescription.json

@@ -1,23 +0,0 @@
-{
-	"id": "aria-roledescription",
-	"evaluate": "aria-roledescription.js",
-	"options": {
-		"supportedRoles": [
-			"button",
-			"img",
-			"checkbox",
-			"radio",
-			"combobox",
-			"menuitemcheckbox",
-			"menuitemradio"
-		]
-	},
-	"metadata": {
-		"impact": "serious",
-		"messages": {
-			"pass": "aria-roledescription used on a supported semantic role",
-			"incomplete": "Check that the aria-roledescription is announced by supported screen readers",
-			"fail": "Give the element a role that supports aria-roledescription"
-		}
-	}
-}

data/node_modules/axe-core/lib/checks/aria/errormessage.js

@@ -1,33 +0,0 @@
-const { aria, dom } = axe.commons;
-options = Array.isArray(options) ? options : [];
-
-const attr = node.getAttribute('aria-errormessage');
-const hasAttr = node.hasAttribute('aria-errormessage');
-
-const doc = dom.getRootNode(node);
-
-function validateAttrValue(attr) {
-	if (attr.trim() === '') {
-		return aria.lookupTable.attributes['aria-errormessage'].allowEmpty;
-	}
-	const idref = attr && doc.getElementById(attr);
-	if (idref) {
-		return (
-			idref.getAttribute('role') === 'alert' ||
-			idref.getAttribute('aria-live') === 'assertive' ||
-			axe.utils
-				.tokenList(node.getAttribute('aria-describedby') || '')
-				.indexOf(attr) > -1
-		);
-	}
-}
-
-// limit results to elements that actually have this attribute
-if (options.indexOf(attr) === -1 && hasAttr) {
-	if (!validateAttrValue(attr)) {
-		this.data(axe.utils.tokenList(attr));
-		return false;
-	}
-}
-
-return true;

data/node_modules/axe-core/lib/checks/aria/errormessage.json

@@ -1,14 +0,0 @@
-{
-	"id": "aria-errormessage",
-	"evaluate": "errormessage.js",
-	"metadata": {
-		"impact": "critical",
-		"messages": {
-			"pass": "Uses a supported aria-errormessage technique",
-			"fail": {
-				"singular": "aria-errormessage value `${data.values}` must use a technique to announce the message (e.g., aria-live, aria-describedby, role=alert, etc.)",
-				"plural": "aria-errormessage values `${data.values}` must use a technique to announce the message (e.g., aria-live, aria-describedby, role=alert, etc.)"
-			}
-		}
-	}
-}

data/node_modules/axe-core/lib/checks/aria/fallbackrole.js

@@ -1 +0,0 @@
-return axe.utils.tokenList(virtualNode.attr('role')).length > 1;

data/node_modules/axe-core/lib/checks/aria/fallbackrole.json

@@ -1,11 +0,0 @@
-{
-	"id": "fallbackrole",
-	"evaluate": "fallbackrole.js",
-	"metadata": {
-		"impact": "serious",
-		"messages": {
-			"pass": "Only one role value used",
-			"fail": "Use only one role value, since fallback roles are not supported in older browsers"
-		}
-	}
-}

data/node_modules/axe-core/lib/checks/aria/has-widget-role.js

@@ -1,6 +0,0 @@
-var role = node.getAttribute('role');
-if (role === null) {
-	return false;
-}
-var roleType = axe.commons.aria.getRoleType(role);
-return roleType === 'widget' || roleType === 'composite';

data/node_modules/axe-core/lib/checks/aria/has-widget-role.json

@@ -1,12 +0,0 @@
-{
-	"id": "has-widget-role",
-	"evaluate": "has-widget-role.js",
-	"options": [],
-	"metadata": {
-		"impact": "minor",
-		"messages": {
-			"pass": "Element has a widget role.",
-			"fail": "Element does not have a widget role."
-		}
-	}
-}

data/node_modules/axe-core/lib/checks/aria/implicit-role-fallback.js

@@ -1,6 +0,0 @@
-var role = node.getAttribute('role');
-if (role === null || !axe.commons.aria.isValidRole(role)) {
-	return true;
-}
-var roleType = axe.commons.aria.getRoleType(role);
-return axe.commons.aria.implicitRole(node) === roleType;

data/node_modules/axe-core/lib/checks/aria/implicit-role-fallback.json

@@ -1,12 +0,0 @@
-{
-	"id": "implicit-role-fallback",
-	"evaluate": "implicit-role-fallback.js",
-	"deprecated": true,
-	"metadata": {
-		"impact": "moderate",
-		"messages": {
-			"pass": "Element’s implicit ARIA role is an appropriate fallback",
-			"fail": "Element’s implicit ARIA role is not a good fallback for the (unsupported) role"
-		}
-	}
-}

data/node_modules/axe-core/lib/checks/aria/invalidrole.js

@@ -1,17 +0,0 @@
-const { tokenList } = axe.utils;
-const { aria } = axe.commons;
-
-const allRoles = tokenList(virtualNode.attr('role'));
-const allInvalid = allRoles.every(
-	role => !aria.isValidRole(role, { allowAbstract: true })
-);
-
-/**
- * Only fail when all the roles are invalid
- */
-if (allInvalid) {
-	this.data(allRoles);
-	return true;
-}
-
-return false;

data/node_modules/axe-core/lib/checks/aria/invalidrole.json

@@ -1,14 +0,0 @@
-{
-	"id": "invalidrole",
-	"evaluate": "invalidrole.js",
-	"metadata": {
-		"impact": "critical",
-		"messages": {
-			"pass": "ARIA role is valid",
-			"fail": {
-				"singular": "Role must be one of the valid ARIA roles: ${data.values}",
-				"plural": "Roles must be one of the valid ARIA roles: ${data.values}"
-			}
-		}
-	}
-}

data/node_modules/axe-core/lib/checks/aria/no-implicit-explicit-label.js

@@ -1,21 +0,0 @@
-const { aria, text } = axe.commons;
-
-const role = aria.getRole(node, { noImplicit: true });
-this.data(role);
-
-const labelText = text.sanitize(text.labelText(virtualNode)).toLowerCase();
-const accText = text.sanitize(text.accessibleText(node)).toLowerCase();
-
-if (!accText && !labelText) {
-	return false;
-}
-
-if (!accText && labelText) {
-	return undefined;
-}
-
-if (!accText.includes(labelText)) {
-	return undefined;
-}
-
-return false;

data/node_modules/axe-core/lib/checks/aria/no-implicit-explicit-label.json

@@ -1,11 +0,0 @@
-{
-	"id": "no-implicit-explicit-label",
-	"evaluate": "no-implicit-explicit-label.js",
-	"metadata": {
-		"impact": "moderate",
-		"messages": {
-			"pass": "There is no mismatch between a <label> and accessible name",
-			"incomplete": "Check that the <label> does not need be part of the ARIA ${data} field's name"
-		}
-	}
-}

data/node_modules/axe-core/lib/checks/aria/required-attr.js

@@ -1,53 +0,0 @@
-options = options || {};
-
-const missing = [];
-const {
-	isNativeTextbox,
-	isNativeSelect,
-	isAriaTextbox,
-	isAriaListbox,
-	isAriaCombobox,
-	isAriaRange
-} = axe.commons.forms;
-
-// aria-valuenow should fail if element does not have a value property
-// @see https://github.com/dequelabs/axe-core/issues/1501
-const preChecks = {
-	'aria-valuenow': function() {
-		return !(
-			isNativeTextbox(node) ||
-			isNativeSelect(node) ||
-			isAriaTextbox(node) ||
-			isAriaListbox(node) ||
-			isAriaCombobox(node) ||
-			(isAriaRange(node) && node.hasAttribute('aria-valuenow'))
-		);
-	}
-};
-
-if (node.hasAttributes()) {
-	const role = node.getAttribute('role');
-	let required = axe.commons.aria.requiredAttr(role);
-
-	if (Array.isArray(options[role])) {
-		required = axe.utils.uniqueArray(options[role], required);
-	}
-	if (role && required) {
-		for (let i = 0, l = required.length; i < l; i++) {
-			const attr = required[i];
-			if (
-				!node.getAttribute(attr) &&
-				(preChecks[attr] ? preChecks[attr]() : true)
-			) {
-				missing.push(attr);
-			}
-		}
-	}
-}
-
-if (missing.length) {
-	this.data(missing);
-	return false;
-}
-
-return true;

data/node_modules/axe-core/lib/checks/aria/required-attr.json

@@ -1,14 +0,0 @@
-{
-	"id": "aria-required-attr",
-	"evaluate": "required-attr.js",
-	"metadata": {
-		"impact": "critical",
-		"messages": {
-			"pass": "All required ARIA attributes are present",
-			"fail": {
-				"singular": "Required ARIA attribute not present: ${data.values}",
-				"plural": "Required ARIA attributes not present: ${data.values}"
-			}
-		}
-	}
-}