Important: This website does not attempt to establish a standard for how assistive technologies must behave. Read the FAQ for more information. Additionally, this is a work in progress. Please submit feedback or suggestions.

Test: aria-errormessage attribute with aria-invalid="true"

Screen Reader support level: partial (15/22)

Voice Control support level: unknown

About this test

Tests the aria-errormessage attribute with aria-invalid="true". The error message must be conveyed.

Submit new test results

Age of results

Results in this test range from 10 months ago to 5 years ago. See detailed information about test dates and versions for more information.

Caution

Failing or partial results may be out of date. The oldest result is from 10 months ago. Consider running this test and contributing results.

Test HTML

Open the test case HTML file

<!DOCTYPE html>
<html lang="en">
<head>
    <title>aria-errormessage examples</title>
</head>
<body>
<h1>aria-errormessage Examples</h1>

<!-- Initial valid state -->
<label for="invalid-false">Input with aria-invalid="false"</label>
<input id="invalid-false" type="text" aria-errormessage="invalid-false-msg" value="" aria-invalid="false">
<div id="invalid-false-msg" style="visibility:hidden">example error text</div>

<!-- User has input an invalid value -->
<label for="invalid-true">Input with aria-invalid="true"</label>
<input id="invalid-true" type="text" aria-errormessage="invalid-true-msg" aria-invalid="true" value="" >
<div id="invalid-true-msg">example error text</div>

<h2>Reference input with aria-invalid="true" but no aria-errormessage</h2>
<p>It may not always be clear if aria-invalid="true" is being conveyed" or if aria-errormessage is being conveyed, or both. So the following is used as a reference.</p>
<label for="reference-input">Reference input</label>
<input id="reference-input" type="text" aria-invalid="true" value="">

</body>
</html>

Summary of Screen Reader support by expectation

aria-errormessage attribute
Expectation	JAWS			Narrator	NVDA			Orca	TalkBack	VoiceOver (iOS)	VoiceOver (macOS)
Expectation	Chrome	Edge	Firefox	Edge	Chrome	Edge	Firefox	Firefox	Chrome	Safari	Safari
MUST NOT convey the error when the error message is NOT pertinent applied to: input[type="text"] element	supported	supported	supported	supported	supported	supported	supported	supported	supported	supported	supported
MUST convey that the referenced error message is pertinent applied to: input[type="text"] element	supported	supported	none	none	none	none	none	supported	none	supported	none

* means that some support is hidden behind settings

Summary of Voice Control support by expectation

aria-errormessage attribute
Expectation	Dragon Naturally Speaking	Voice Access (Android)	Voice Control (iOS)	Voice Control (MacOS)	Windows Speech Recognition		Windows Voice Access
Expectation	Chrome	Chrome	Safari	Safari	Edge	Chrome	Edge	Chrome
Not applicable

* means that some support is hidden behind settings

Detailed support results by expectation

Expectation for the aria-errormessage attribute: convey the error when the error message is NOT pertinent - applied to the input[type="text"] element

This expectation is applied to the input[type="text"] element. Expectations and results might differ when the the feature is applied to different roles.

This expectation is from the aria-errormessage attribute feature.

Rationale:

Users should not be made aware of the error message when the input is not in an error state

Strength of this expectation for different types of assistive technologies:

Screen Readers: MUST NOT
Voice Control: NA

Examples:

when an input has an error message but also has aria-invalid="false", the error message will not be conveyed because it is not pertinent

Grading method:

Just one of the listed commands must pass for the expectation to pass.

AT	Browser	Has Support	Output
Dragon Naturally Speaking	Chrome	not applicable	-
JAWS	Chrome	yes	Result: (pass) Test Case: Use Down arrow (Read next item) to navigate forward to `[aria-errormessage]:not([aria-invalid=true])` Launch JAWS and Chrome. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage]:not([aria-invalid=true])` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Down arrow` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false" Edit" Result: (pass) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage]:not([aria-invalid=true])` Launch JAWS and Chrome. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage]:not([aria-invalid=true])` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false", edit, type in text"
JAWS	Edge	yes	Result: (pass) Test Case: Use Down arrow (Read next item) to navigate forward to `[aria-errormessage]:not([aria-invalid=true])` Launch JAWS and Edge. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage]:not([aria-invalid=true])` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Down arrow` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "blank, Input with aria-invalid="false" Edit Result: (pass) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage]:not([aria-invalid=true])` Launch JAWS and Edge. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage]:not([aria-invalid=true])` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false" Edit type in text"
JAWS	Firefox	yes	Result: (pass) Test Case: Use Down arrow (Read next item) to navigate forward to `[aria-errormessage]:not([aria-invalid=true])` Launch JAWS and Firefox. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage]:not([aria-invalid=true])` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Down arrow` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false" Edit" Result: (pass) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage]:not([aria-invalid=true])` Launch JAWS and Firefox. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage]:not([aria-invalid=true])` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false", edit type in text"
Narrator	Edge	yes	Result: (pass) Test Case: Use Down arrow (Jump to next item (scan mode)) to navigate forward to `[aria-errormessage]:not([aria-invalid=true])` Launch Narrator and Edge. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage]:not([aria-invalid=true])` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Down arrow` (Jump to next item (scan mode)) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false", edit, scan off" Result: (pass) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage]:not([aria-invalid=true])` Launch Narrator and Edge. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage]:not([aria-invalid=true])` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false", edit"
NVDA	Chrome	yes	Result: (pass) Test Case: Use down arrow (Read next item) to navigate forward to `[aria-errormessage][aria-invalid=false]` Launch NVDA and Chrome. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=false]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `down arrow` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false", edit" Result: (pass) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage][aria-invalid=false]` Launch NVDA and Chrome. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=false]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false", edit, blank"
NVDA	Edge	yes	Result: (pass) Test Case: Use down arrow (Read next item) to navigate forward to `[aria-errormessage][aria-invalid=false]` Launch NVDA and Edge. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=false]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `down arrow` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false", edit" Result: (pass) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage][aria-invalid=false]` Launch NVDA and Edge. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=false]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false", edit, blank"
NVDA	Firefox	yes	Result: (pass) Test Case: Use down arrow (Read next item) to navigate forward to `[aria-errormessage]:not([aria-invalid=true])` Launch NVDA and Firefox. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage]:not([aria-invalid=true])` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `down arrow` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false", entry" Result: (pass) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage]:not([aria-invalid=true])` Launch NVDA and Firefox. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage]:not([aria-invalid=true])` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false", edit has autocomplete blank "
Orca	Firefox	yes	Result: (pass) Test Case: Use down arrow (Read next item) to navigate forward to `[aria-errormessage]:not([aria-invalid=true])` Launch Orca and Firefox. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage]:not([aria-invalid=true])` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `down arrow` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false", entry" Result: (pass) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage]:not([aria-invalid=true])` Launch Orca and Firefox. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage]:not([aria-invalid=true])` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false", entry"
TalkBack	Chrome	yes	Result: (pass) Test Case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `[aria-errormessage]:not([aria-invalid=true])` Launch TalkBack and Chrome. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage]:not([aria-invalid=true])` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Swipe right (or alt+right arrow)` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Edit box, input with aria-invalid="false""
Voice Access (Android)	Chrome	not applicable	-
Voice Control (iOS)	Safari	not applicable	-
Voice Control (MacOS)	Safari	not applicable	-
VoiceOver (iOS)	Safari	yes	Result: (pass) Test Case: Use Swipe Right (Next item) to navigate forward to `[aria-errormessage]:not([aria-invalid=true])` Launch VoiceOver (iOS) and Safari. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage]:not([aria-invalid=true])` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Swipe Right` (Next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false", text field, double tap to edit"
VoiceOver (macOS)	Safari	yes	Result: (pass) Test Case: Use VO + Right arrow (Read next item) to navigate forward to `[aria-errormessage]:not([aria-invalid=true])` Launch VoiceOver (macOS) and Safari. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage]:not([aria-invalid=true])` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `VO + Right arrow` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false", edit text" Result: (pass) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage]:not([aria-invalid=true])` Launch VoiceOver (macOS) and Safari. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage]:not([aria-invalid=true])` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false", edit text"
Windows Speech Recognition	Edge	not applicable	-
Windows Speech Recognition	Chrome	not applicable	-
Windows Voice Access	Edge	not applicable	-
Windows Voice Access	Chrome	not applicable	-
Windows Keyboard	Chrome	not applicable	-
Windows Keyboard	Firefox	not applicable	-
Windows Keyboard	Edge	not applicable	-
Mac Keyboard	Chrome	not applicable	-
Mac Keyboard	Safari	not applicable	-
iOS Keyboard	Safari	not applicable	-
Android Keyboard	Chrome	not applicable	-

Extended Support for: aria-errormessage attribute: convey the error when the error message is NOT pertinent

These are less common combinations

AT	Browser	Has Support	Output
Dragon Naturally Speaking	IE	not applicable	-
Dragon Naturally Speaking	Firefox	not applicable	-
JAWS 2019.1907.42	IE 11	none	Result: (fail) Test Case: Use Down arrow (Read next item) to navigate forward to `[aria-errormessage]:not([aria-invalid=true])` Launch JAWS and IE. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage]:not([aria-invalid=true])` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Down arrow` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "edit, Input with aria-invalid="false", edit, has error, example error text, type in text" Result: (fail) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage]:not([aria-invalid=true])` Launch JAWS and IE. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage]:not([aria-invalid=true])` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="false", edit, has error, example error text, type in text"
Narrator	Firefox	unknown	-
Narrator	Chrome	unknown	-
Narrator	IE	unknown	-
NVDA	IE	unknown	-
TalkBack	Firefox	unknown	-
Voice Access (Android)	Firefox	not applicable	-
VoiceOver (iOS)	Chrome	unknown	-
VoiceOver (macOS)	Chrome	unknown	-
VoiceOver (macOS)	Firefox	unknown	-
Orca	Chrome	unknown	-
Voice Control (MacOS)	Chrome	not applicable	-
Voice Control (MacOS)	Firefox	not applicable	-
Mac Keyboard	Firefox	not applicable	-
Android Keyboard	Firefox	not applicable	-

Expectation for the aria-errormessage attribute: convey that the referenced error message is pertinent - applied to the input[type="text"] element

This expectation is applied to the input[type="text"] element. Expectations and results might differ when the the feature is applied to different roles.

This expectation is from the aria-errormessage attribute feature.

Rationale:

Users need to know that the error message exists when the input is in an aria-invalid="true" state

Strength of this expectation for different types of assistive technologies:

Screen Readers: MUST
Voice Control: NA

Examples:

screen readers might convey the accessible name of the referenced ID
screen readers might announce that an error message is present and provide a shortcut to jump to the error message

Grading method:

Just one of the listed commands must pass for the expectation to pass.

AT	Browser	Has Support	Output
Dragon Naturally Speaking	Chrome	not applicable	-
JAWS	Chrome	yes	Result: (pass) Test Case: Use Down arrow (Read next item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch JAWS and Chrome. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Down arrow` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="true" Edit Has Error invalid entry" Result: (pass) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch JAWS and Chrome. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="true", edit, invalid entry, has error, example error text, type in text"
JAWS	Edge	yes	Result: (pass) Test Case: Use Down arrow (Read next item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch JAWS and Edge. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Down arrow` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "blank, Input with aria-invalid="true" Edit Has Error invalid entry" Result: (pass) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch JAWS and Edge. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: Input with aria-invalid="true" Edit invalid entry Has Error example error text Type in text.
JAWS	Firefox	none	Result: (fail) Test Case: Use Down arrow (Read next item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch JAWS and Firefox. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Down arrow` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="true" Edit invalid entry" Grading note: This command may be expected to fail. This result simply indicates that it did not yield support. Result: (fail) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch JAWS and Firefox. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="true" Edit invalid entry" Grading note: This command may be expected to fail. This result simply indicates that it did not yield support. Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue.
Narrator	Edge	none	Result: (fail) Test Case: Use Down arrow (Jump to next item (scan mode)) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch Narrator and Edge. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Down arrow` (Jump to next item (scan mode)) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="true", edit, invalid, scan off" Grading note: This command may be expected to fail. This result simply indicates that it did not yield support. Result: (fail) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch Narrator and Edge. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="true", edit, invalid" Grading note: This command may be expected to fail. This result simply indicates that it did not yield support. Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue.
NVDA	Chrome	none	Result: (fail) Test Case: Use down arrow (Read next item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch NVDA and Chrome. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `down arrow` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="true" edit invalid entry" Grading note: This command may be expected to fail. This result simply indicates that it did not yield support. Result: (fail) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch NVDA and Chrome. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="true", edit, invalid entry, blank" Grading note: This command may be expected to fail. This result simply indicates that it did not yield support. Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue.
NVDA	Edge	none	Result: (fail) Test Case: Use down arrow (Read next item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch NVDA and Edge. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `down arrow` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="true", edit, invalid entry" Grading note: This command may be expected to fail. This result simply indicates that it did not yield support. Result: (fail) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch NVDA and Edge. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="true", edit, invalid entry, blank" Grading note: This command may be expected to fail. This result simply indicates that it did not yield support. Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue.
NVDA	Firefox	none	Result: (fail) Test Case: Use down arrow (Read next item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch NVDA and Firefox. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `down arrow` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="true", edit, invalid entry has auto complete" Grading note: This command may be expected to fail. This result simply indicates that it did not yield support. Result: (fail) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch NVDA and Firefox. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="true", edit, invalid entry has auto complete, blank" Grading note: This command may be expected to fail. This result simply indicates that it did not yield support. Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue.
Orca	Firefox	yes	Result: (pass) Test Case: Use down arrow (Read next item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch Orca and Firefox. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `down arrow` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="true", entry, invalid entry, example error text" Result: (pass) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch Orca and Firefox. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="true", entry, invalid entry, example error texte"
TalkBack	Chrome	none	Result: (fail) Test Case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch TalkBack and Chrome. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Swipe right (or alt+right arrow)` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Edit box, input with aria-invalid="true"" Grading note: This command may be expected to fail. This result simply indicates that it did not yield support. Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue.
Voice Access (Android)	Chrome	not applicable	-
Voice Control (iOS)	Safari	not applicable	-
Voice Control (MacOS)	Safari	not applicable	-
VoiceOver (iOS)	Safari	yes	Result: (pass) Test Case: Use Swipe Right (Next item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch VoiceOver (iOS) and Safari. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Swipe Right` (Next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="true", text field, invalid date, example error text, double tap to edit"
VoiceOver (macOS)	Safari	none	Result: (fail) Test Case: Use VO + Right arrow (Read next item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch VoiceOver (macOS) and Safari. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `VO + Right arrow` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="true", invalid data, edit text" Grading note: This command may be expected to fail. This result simply indicates that it did not yield support. Result: (fail) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch VoiceOver (macOS) and Safari. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="true", invalid data, edit text" Grading note: This command may be expected to fail. This result simply indicates that it did not yield support. Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue.
Windows Speech Recognition	Edge	not applicable	-
Windows Speech Recognition	Chrome	not applicable	-
Windows Voice Access	Edge	not applicable	-
Windows Voice Access	Chrome	not applicable	-
Windows Keyboard	Chrome	not applicable	-
Windows Keyboard	Firefox	not applicable	-
Windows Keyboard	Edge	not applicable	-
Mac Keyboard	Chrome	not applicable	-
Mac Keyboard	Safari	not applicable	-
iOS Keyboard	Safari	not applicable	-
Android Keyboard	Chrome	not applicable	-

Extended Support for: aria-errormessage attribute: convey that the referenced error message is pertinent

These are less common combinations

AT	Browser	Has Support	Output
Dragon Naturally Speaking	IE	not applicable	-
Dragon Naturally Speaking	Firefox	not applicable	-
JAWS 2019.1907.42	IE 11	yes	Result: (pass) Test Case: Use Down arrow (Read next item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch JAWS and IE. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Down arrow` (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "blank, edit, Input with aria-invalid="true", invalid entry, has error, example error text, type in text" Result: (pass) Test Case: Use Tab (Read next focusable item) to navigate forward to `[aria-errormessage][aria-invalid=true]` Launch JAWS and IE. Navigate to the test page. Find the target element(s) that you will test against. Identify all elements that match this selector:`[aria-errormessage][aria-invalid=true]` If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are met Virtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: `Tab` (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output: "Input with aria-invalid="true", edit, invalid entry, has error, example error text, type in text"
Narrator	Firefox	unknown	-
Narrator	Chrome	unknown	-
Narrator	IE	unknown	-
NVDA	IE	unknown	-
TalkBack	Firefox	unknown	-
Voice Access (Android)	Firefox	not applicable	-
VoiceOver (iOS)	Chrome	unknown	-
VoiceOver (macOS)	Chrome	unknown	-
VoiceOver (macOS)	Firefox	unknown	-
Orca	Chrome	unknown	-
Voice Control (MacOS)	Chrome	not applicable	-
Voice Control (MacOS)	Firefox	not applicable	-
Mac Keyboard	Firefox	not applicable	-
Android Keyboard	Firefox	not applicable	-

Dates and Versions of tested combinations

AT	AT Version	Browser	Browser version	OS version	Date tested
JAWS	2023.2306.38	Chrome	114	Windows 11 version 22h2	2023-06-20
JAWS	2023.2306.38	Edge	114	Windows 11 version 22h2	2023-06-20
JAWS	2023.2306.38	Firefox	114	Windows 11 version 22h2	2023-06-20
Narrator	Windows 11 version 22h2	Edge	114	Windows 11 version 22h2	2023-06-20
NVDA	2023.1	Chrome	114	Windows 11 version 22h2	2023-06-20
NVDA	2023.1	Edge	114	Windows 11 version 22h2	2023-06-20
NVDA	2023.1	Firefox	114	Windows 11 version 22h2	2023-06-20
Orca	3.31.4	Firefox	69	Ubuntu 19.04	2019-09-16
TalkBack	14	Chrome	114	13	2023-06-20
VoiceOver (iOS)	16.5	Safari	16.5	16.5	2023-06-20
VoiceOver (macOS)	13.4	Safari	16.5	13.4	2023-06-20

History

2019-04-09 Test created
2019-08-02 Updated results
2019-09-16 Add orca results
2021-07-23 Added Narrator results for NVDA and JAWS, updated NVDA+Chrome results.
2023-06-20 Updated all results

Test: aria-errormessage attribute with aria-invalid="true"

On this page

About this test

Age of results

Caution

Test HTML

Summary of Screen Reader support by expectation

Summary of Voice Control support by expectation

Detailed support results by expectation

Expectation for the aria-errormessage attribute: convey the error when the error message is NOT pertinent - applied to the input[type="text"] element

Rationale:

Strength of this expectation for different types of assistive technologies:

Examples:

Grading method:

Extended Support for: aria-errormessage attribute: convey the error when the error message is NOT pertinent

Expectation for the aria-errormessage attribute: convey that the referenced error message is pertinent - applied to the input[type="text"] element

Rationale:

Strength of this expectation for different types of assistive technologies:

Examples:

Grading method:

Extended Support for: aria-errormessage attribute: convey that the referenced error message is pertinent

Dates and Versions of tested combinations

History

Feedback and Contribute

Other

Test: aria-errormessage attribute with aria-invalid="true"

On this page

About this test

Age of results

Caution

Test HTML

Summary of Screen Reader support by expectation

Summary of Voice Control support by expectation

Detailed support results by expectation

Expectation for the aria-errormessage attribute: convey the error when the error message is NOT pertinent - applied to the input[type="text"] element

Rationale:

Strength of this expectation for different types of assistive technologies:

Examples:

Grading method:

Extended Support for: aria-errormessage attribute: convey the error when the error message is NOT pertinent

Expectation for the aria-errormessage attribute: convey that the referenced error message is pertinent - applied to the input[type="text"] element

Rationale:

Strength of this expectation for different types of assistive technologies:

Examples:

Grading method:

Extended Support for: aria-errormessage attribute: convey that the referenced error message is pertinent

Dates and Versions of tested combinations

History

Related Features

Feedback and Contribute

Other