Aria list

With a default "undefined" value indicating the state or property is not relevant.ID referenceReference to the ID of another element in the same documentID reference listA list of one or more ID references.integerA numerical value without a fractional component.numberAny real numerical value.stringUnconstrained value type.tokenOne of a limited set of allowed values.Widget attributesaria-autocompleteIndicates whether user input completion suggestions are provided.Values: ValueConditioninlineThe system provides text after the caret as a suggestion for how to complete the field.listA list of choices appears from which the user can choose, but the edit box retains focus.bothA list of choices appears and the currently selected suggestion also appears inline.noneNo input completion suggestions are provided.aria-checked - (state)Indicates the current "checked" state of checkboxes, radio buttons, and other widgets. See related aria-pressed and aria-selected.Values: ValueConditiontrueThe element is selected.falseThe element is not selected.mixedThe element indicates both selected and unselected states.aria-current - (state)Indicates the element that represents the current item within a container or set of related elements. The aria-current attribute is used when an element within a set of related elements is visually styled to indicate it is the current item in the set.Values: ValueConditionpageRepresents the current page within a set of pages.stepRepresents the current step within a process.locationRepresents the current location within an environment or context.dateRepresents the current date within a collection of dates.timeRepresents the current time within a set of times.trueRepresents the current item within a set.false(default) Does not represent the current item within a set.aria-disabled - (state)Indicates that the element is perceivable but disabled, so it is not editable or otherwise operable. See related aria-hidden and aria-readonly.Values: aria-expanded - (state)Indicates whether the element, or another grouping element it controls, is currently expanded or collapsed.Values: aria-haspopupIndicates that the element has a popup context menu or sub-level menu.Values: aria-hidden - (state)Indicates that the element and all of its descendants are not visible or perceivable to any user as implemented by the author. See related aria-disabled.Values: aria-invalid - (state)Indicates the entered value does not conform to the format expected by the application.Values: ValueConditiontrueThe element is selected.falseThe element is not selected.grammarA grammatical error has been detected.spellingA spelling error has been detected.aria-labelDefines a string value that labels the current element. See related aria-labelledby.Values: aria-levelDefines the hierarchical level of an element within a structure.Values: aria-multilineIndicates whether a text box accepts multiple lines of input or only a single line.Values: aria-multiselectableIndicates that the user may select more than one item from the current selectable descendants.Values: aria-orientationIndicates whether the element and orientation is horizontal or vertical.Values: ValueConditionverticalThe element is oriented vertically.horizontal(default)The element is not selected.grammarThe element is oriented horizontally.aria-pressed - (state)Indicates the current "pressed" state of toggle buttons. See related aria-checked and aria-selected.Values: aria-readonlyIndicates that the element is not editable, but is otherwise operable.

Error: No matching rule for axe/html/4.9/aria-prohibited-attrr Need accessibility training? Deque University offers an extensive curriculum of self-guided online courses for every skillset and experience level. Sign up for the axe newsletter Stay up to date on axe features, updates, and events. Newsletter Sign-up These are automated accessibility checks. Manual checks are also required. Learn how through our accessibility curriculum. See the list of axe html versions Table of Contents WCAG 2.0 Level A & AA Rules WCAG 2.1 Level A & AA Rules WCAG 2.2 Level A & AA Rules Best Practices Rules WCAG 2.x level AAA rules Experimental Rules Deprecated Rules WCAG 2.0 Level A & AA Rules Rule ID Description Impact Tags Issue Type ACT Rules area-alt Ensures elements of image maps have alternate text Critical cat.text-alternatives, wcag2a, wcag244, wcag412, section508, section508.22.a, TTv5, TT6.a, EN-301-549, EN-9.2.4.4, EN-9.4.1.2, ACT failure, needs review c487ae aria-allowed-attr Ensures an element's role supports its ARIA attributes Critical cat.aria, wcag2a, wcag412, EN-301-549, EN-9.4.1.2 failure, needs review 5c01ea aria-braille-equivalent Ensure aria-braillelabel and aria-brailleroledescription have a non-braille equivalent Serious cat.aria, wcag2a, wcag412, EN-301-549, EN-9.4.1.2 needs review aria-command-name Ensures every ARIA button, link and menuitem has an accessible name Serious cat.aria, wcag2a, wcag412, TTv5, TT6.a, EN-301-549, EN-9.4.1.2, ACT failure, needs review 97a4e1 aria-conditional-attr Ensures ARIA attributes are used as described in the specification of the element's role Serious cat.aria, wcag2a, wcag412, EN-301-549, EN-9.4.1.2 failure 5c01ea aria-deprecated-role Ensures elements do not use deprecated roles Minor cat.aria, wcag2a, wcag412, EN-301-549, EN-9.4.1.2 failure 674b10 aria-hidden-body Ensures aria-hidden="true" is not present on the document body. Critical cat.aria, wcag2a, wcag131, wcag412, EN-301-549, EN-9.1.3.1, EN-9.4.1.2 failure aria-hidden-focus Ensures aria-hidden elements are not focusable nor contain focusable elements Serious cat.name-role-value, wcag2a, wcag412, TTv5, TT6.a, EN-301-549, EN-9.4.1.2 failure, needs review 6cfa84 aria-input-field-name Ensures every ARIA input field has an accessible name Serious cat.aria, wcag2a, wcag412,

How to Fix the Problem Ensure the value inside each attribute is spelled correctly and corresponds to a valid value. For example, aria-hidden="true" would pass, but aria-hidden="rtue" would fail, as would aria-hidden="pizza". As another example, the checkbox role only has three possible values: true, false, or mixed. Using any value other than one of those three will prevent the checkbox from being functional. Note: Particular caution must be used when specifying values for ARIA attributes, as factors such as the distinction between states and properties, role inheritance, undefined and default values can be confusing. Value Types It is useful to take into consideration the following allowed state or property value types: true/false Value representing either true or false, with a default "false" value. tristate Value representing true or false, with an intermediate "mixed" value. Default value is "false" unless otherwise specified. true/false/undefined Value representing true or false, with a default "undefined" value indicating the state or property is not relevant. ID reference Reference to the ID of another element in the same document ID reference list A list of one or more ID references. integer A numerical value without a fractional component. number Any real numerical value. string Unconstrained value type. token One of a limited set of allowed values. token list A list of one or more tokens. Undefined Value: The "undefined" value, when allowed on a state or property, is an explicit indication that the state or property is not set. The value is used on states and properties that support tokens, and the "undefined" value is a string that is one of the allowed tokens. It is also used on some states and properties that accept true/false values, when "undefined" has a different meaning than "false". These are generic types for states and properties, but do not define specific representation. See State and Property Attribute Processing for details on how these values are expressed and handled in host languages. Default Value and Implicit Value for Role: Many states and properties have default values. Occasionally, the default value when used on a given role should be different from the usual default. Roles that require a state or property to have a non-standard default value indicate this in the "Implicit Value for Role". This is expressed in the form "state or property name is new default value". Roles that define this have the new default value for the state or property if the author does not provide an explicit value. State and Property Values Reference: For complete information about allowed values, refer to the table of characteristics for each individual attribute at W3C WAI-ARIA 1.1 Supported States and Properties. Why it Matters ARIA attributes (i.e. starting with aria-) must

Error: No matching rule for axe/html/4.8/a Learn Web Accessibility Subscribe to our extensive curriculum of online self-paced courses Sign up for the axe newsletter Stay up to date on axe features, updates, and events. Newsletter Sign-up These are automated accessibility checks. Manual checks are also required. Learn how through our accessibility curriculum. See the list of axe html versions Table of Contents WCAG 2.0 Level A & AA Rules WCAG 2.1 Level A & AA Rules WCAG 2.2 Level A & AA Rules Best Practices Rules WCAG 2.x level AAA rules Experimental Rules Deprecated Rules WCAG 2.0 Level A & AA Rules Rule ID Description Impact Tags Issue Type ACT Rules area-alt Ensures elements of image maps have alternate text Critical cat.text-alternatives, wcag2a, wcag244, wcag412, section508, section508.22.a, TTv5, TT6.a, EN-301-549, EN-9.2.4.4, EN-9.4.1.2, ACT failure, needs review c487ae aria-allowed-attr Ensures an element's role supports its ARIA attributes Critical cat.aria, wcag2a, wcag412, EN-301-549, EN-9.4.1.2 failure, needs review 5c01ea aria-braille-equivalent Ensure aria-braillelabel and aria-brailleroledescription have a non-braille equivalent Serious cat.aria, wcag2a, wcag412, EN-301-549, EN-9.4.1.2 needs review aria-command-name Ensures every ARIA button, link and menuitem has an accessible name Serious cat.aria, wcag2a, wcag412, TTv5, TT6.a, EN-301-549, EN-9.4.1.2, ACT failure, needs review 97a4e1 aria-conditional-attr Ensures ARIA attributes are used as described in the specification of the element's role Serious cat.aria, wcag2a, wcag412, EN-301-549, EN-9.4.1.2 failure 5c01ea aria-deprecated-role Ensures elements do not use deprecated roles Minor cat.aria, wcag2a, wcag412, EN-301-549, EN-9.4.1.2 failure 674b10 aria-hidden-body Ensures aria-hidden="true" is not present on the document body. Critical cat.aria, wcag2a, wcag412, EN-301-549, EN-9.4.1.2 failure aria-hidden-focus Ensures aria-hidden elements are not focusable nor contain focusable elements Serious cat.name-role-value, wcag2a, wcag412, TTv5, TT6.a, EN-301-549, EN-9.4.1.2 failure, needs review 6cfa84 aria-input-field-name Ensures every ARIA input field has an accessible name Serious cat.aria, wcag2a, wcag412, TTv5, TT5.c, EN-301-549, EN-9.4.1.2, ACT failure, needs review e086e5 aria-meter-name Ensures every ARIA meter node has an accessible name Serious cat.aria, wcag2a, wcag111, EN-301-549, EN-9.1.1.1 failure, needs review aria-progressbar-name Ensures every ARIA progressbar node has an accessible name Serious cat.aria, wcag2a, wcag111, EN-301-549, EN-9.1.1.1 failure, needs review aria-prohibited-attr Ensures ARIA attributes are not prohibited for an element's role Serious

Cat.aria, wcag2a, wcag412, EN-301-549, EN-9.4.1.2 failure, needs review 5c01ea aria-required-attr Ensures elements with ARIA roles have all required ARIA attributes Critical cat.aria, wcag2a, wcag412, EN-301-549, EN-9.4.1.2 failure 4e8ab6 aria-required-children Ensures elements with an ARIA role that require child roles contain them Critical cat.aria, wcag2a, wcag131, EN-301-549, EN-9.1.3.1 failure, needs review bc4a75, ff89c9 aria-required-parent Ensures elements with an ARIA role that require parent roles are contained by them Critical cat.aria, wcag2a, wcag131, EN-301-549, EN-9.1.3.1 failure ff89c9 aria-roles Ensures all elements with a role attribute use a valid value Critical cat.aria, wcag2a, wcag412, EN-301-549, EN-9.4.1.2 failure 674b10 aria-toggle-field-name Ensures every ARIA toggle field has an accessible name Serious cat.aria, wcag2a, wcag412, TTv5, TT5.c, EN-301-549, EN-9.4.1.2, ACT failure, needs review e086e5 aria-tooltip-name Ensures every ARIA tooltip node has an accessible name Serious cat.aria, wcag2a, wcag412, EN-301-549, EN-9.4.1.2 failure, needs review aria-valid-attr-value Ensures all ARIA attributes have valid values Critical cat.aria, wcag2a, wcag412, EN-301-549, EN-9.4.1.2 failure, needs review 6a7281 aria-valid-attr Ensures attributes that begin with aria- are valid ARIA attributes Critical cat.aria, wcag2a, wcag412, EN-301-549, EN-9.4.1.2 failure 5f99a7 blink Ensures elements are not used Serious cat.time-and-media, wcag2a, wcag222, section508, section508.22.j, TTv5, TT2.b, EN-301-549, EN-9.2.2.2 failure button-name Ensures buttons have discernible text Critical cat.name-role-value, wcag2a, wcag412, section508, section508.22.a, TTv5, TT6.a, EN-301-549, EN-9.4.1.2, ACT failure, needs review 97a4e1, m6b1q3 bypass Ensures each page has at least one mechanism for a user to bypass navigation and jump straight to the content Serious cat.keyboard, wcag2a, wcag241, section508, section508.22.o, TTv5, TT9.a, EN-301-549, EN-9.2.4.1 needs review cf77f2, 047fe0, b40fd1, 3e12e1, ye5d6e color-contrast Ensures the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds Serious cat.color, wcag2aa, wcag143, TTv5, TT13.c, EN-301-549, EN-9.1.4.3, ACT failure, needs review afw4f7, 09o5cg definition-list Ensures elements are structured correctly Serious cat.structure, wcag2a, wcag131, EN-301-549, EN-9.1.3.1 failure dlitem Ensures and elements are contained by a Serious cat.structure, wcag2a, wcag131, EN-301-549, EN-9.1.3.1 failure document-title Ensures each HTML document contains a non-empty element Serious cat.text-alternatives, wcag2a, wcag242, TTv5, TT12.a, EN-301-549, EN-9.2.4.2, ACT failure 2779a5 duplicate-id-aria Ensures every id attribute value used in ARIA and in labels is unique Critical cat.parsing, wcag2a, wcag412, EN-301-549, EN-9.4.1.2

Skip to content When there are set of elements, one among them is active, we have been communicating this state today with one or other techniques to assistive technology users. Techniques that we have been following:Using off screen techniquesUsing title techniquesRemoving href attribute or providing role=”presentation” if they are actionable elementsThese are the hacking techniques to convey the current state of the element to the assistive technology users.aria 1.1 introduced aria-current attribute to convey the current state of the element programmatically. We don’t need to use hacking techniques any more. Aria-current is enumerated type and accepts list of token values. They are,Aria-current=page, represents the current page within the set of the pages. For ex: in the pagination, we can set this attribute to the page which is currently activearia-current=”step”, represents the current step within the process. For ex: in the ecommerse websites, we have checkout process. Typically, checkout process consists of few steps such as billing information, shipping information, payment method, conformation and so on.. we can set aria-current=”step= to the step that is currently active.Aria-current=”location”, represents the current location within the context or environment. For ex: in the flow chart, we can set this attribute to the location that is currently active.Aria-current=”date”, represents the current date within the collection of dates. For ex: in the calendar, we can set this attribute to the date that is currently activearia-current=”time”, represents the current time within the set of times.aria-current=”true”, represents the current item within the setAria-current=”false”, does not represent the current item within the set.Notes for assistive technology vendorsAny other values apart from the mentioned values should be treated as aria-current=”true” by assistive technologies.If the attribute is not present or its value is an empty string or undefined, aria-current state MUST NOT be exposed by user agents or assistive technologies.Author notesAuthor should not use Aria-current and aria-selected interchangeably as they are not one and the same and they are different. In few cases, author might have to use both aria-current and aria-selected. For ex:, in the tree view, aria-current is to be used for the currently active page and aria-select to be used for the item that user is navigated to..Authors SHOULD only mark one element in a set of elements as current with aria-current. Post navigation