Test cases for Dragon Naturally Speaking + Chrome Test case: Use "Click <text>" (Activate item by name) Launch Dragon Naturally Speaking and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:input[type="number"]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. Issue the command: "Click <text>" (Activate item by name) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes Test case: Use Click <role> (Click Type) Launch Dragon Naturally Speaking and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:input[type="number"]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. Issue the command: Click <role> (Click Type) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes Test case: Use "press <key>" (press a keyboard command) Launch Dragon Naturally Speaking and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:input[type="number"]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. Issue the command: "press <key>" (press a keyboard command) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MAY allow incrementing and decrementing the value Examples:
Desktop screen readers might allow users to adjust the value by pressing up and down arrows Mobile screen readers might allow users to adjust the value by swiping up or down Voice control software might allow someone to say something like "increment <name>" Resultunknown pass fail partial
Notes Test case: Use "{speak text to type}" (dictate) Launch Dragon Naturally Speaking and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:input[type="number"]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. Issue the command: "{speak text to type}" (dictate) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST allow data entry Examples:
Voice control software might allow someone to dictate data into a field once it is focused. Resultunknown pass fail partial
Notes Test cases for Dragon Naturally Speaking + IE The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Dragon Naturally Speaking + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for JAWS + Chrome Test case: Use Down arrow (Read next item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use f (Next form field) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: f (Next form field) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Insert + F3 (Open element list) 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:input[type="number"]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 metMode is: auto (do not explicitly change the mode) Issue the command: Insert + F3 (Open element list) After issuing the command, virtual focus should be: na Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use <enter text> (enter text) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <enter text> (enter text) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey changes in value Examples:
When the user enter texts, the screen reader will announce it back to them. Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <keyboard command> (Keyboard command while in forms or application mode) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MAY allow incrementing and decrementing the value Examples:
Desktop screen readers might allow users to adjust the value by pressing up and down arrows Mobile screen readers might allow users to adjust the value by swiping up or down Voice control software might allow someone to say something like "increment <name>" Resultunknown pass fail partial
Notes Test case: Enter invalid text into the number input 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:input[type="number"]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. set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the number input Using the command: "Tab" (Read next focusable item) Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target issue commandsummary: type "two" Using the command: "<enter text>" (enter text) Observe: the input should be rejected and the screen reader should have conveyed that the input was rejected. Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey when input is rejected Examples:
the behavior might be implied if the control is conveyed as something like "number", "spinbox", "spin button", or "incrementable" some AT/browser combinations will allow invalid input but convey the field as invalid screen readers might announce an earcon when the user tries to enter data beyond the maximum length. screen readers might imply that the input was rejected by not announcing anything when a user tries to enter data (usually the keypress is echoed) Resultunknown pass fail partial
Notes Test cases for JAWS + Edge Test case: Use Down arrow (Read next item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use f (Next form field) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: f (Next form field) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Insert + F3 (Open element list) 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:input[type="number"]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 metMode is: auto (do not explicitly change the mode) Issue the command: Insert + F3 (Open element list) After issuing the command, virtual focus should be: na Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use <enter text> (enter text) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <enter text> (enter text) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey changes in value Examples:
When the user enter texts, the screen reader will announce it back to them. Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <keyboard command> (Keyboard command while in forms or application mode) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MAY allow incrementing and decrementing the value Examples:
Desktop screen readers might allow users to adjust the value by pressing up and down arrows Mobile screen readers might allow users to adjust the value by swiping up or down Voice control software might allow someone to say something like "increment <name>" Resultunknown pass fail partial
Notes Test case: Enter invalid text into the number input 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:input[type="number"]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. set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the number input Using the command: "Tab" (Read next focusable item) Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target issue commandsummary: type "two" Using the command: "<enter text>" (enter text) Observe: the input should be rejected and the screen reader should have conveyed that the input was rejected. Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey when input is rejected Examples:
the behavior might be implied if the control is conveyed as something like "number", "spinbox", "spin button", or "incrementable" some AT/browser combinations will allow invalid input but convey the field as invalid screen readers might announce an earcon when the user tries to enter data beyond the maximum length. screen readers might imply that the input was rejected by not announcing anything when a user tries to enter data (usually the keypress is echoed) Resultunknown pass fail partial
Notes Test cases for JAWS + Firefox Test case: Use Down arrow (Read next item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use f (Next form field) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: f (Next form field) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Insert + F3 (Open element list) 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:input[type="number"]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 metMode is: auto (do not explicitly change the mode) Issue the command: Insert + F3 (Open element list) After issuing the command, virtual focus should be: na Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use <enter text> (enter text) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <enter text> (enter text) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey changes in value Examples:
When the user enter texts, the screen reader will announce it back to them. Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <keyboard command> (Keyboard command while in forms or application mode) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MAY allow incrementing and decrementing the value Examples:
Desktop screen readers might allow users to adjust the value by pressing up and down arrows Mobile screen readers might allow users to adjust the value by swiping up or down Voice control software might allow someone to say something like "increment <name>" Resultunknown pass fail partial
Notes Test case: Enter invalid text into the number input 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:input[type="number"]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. set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the number input Using the command: "Tab" (Read next focusable item) Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target issue commandsummary: type "two" Using the command: "<enter text>" (enter text) Observe: the input should be rejected and the screen reader should have conveyed that the input was rejected. Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey when input is rejected Examples:
the behavior might be implied if the control is conveyed as something like "number", "spinbox", "spin button", or "incrementable" some AT/browser combinations will allow invalid input but convey the field as invalid screen readers might announce an earcon when the user tries to enter data beyond the maximum length. screen readers might imply that the input was rejected by not announcing anything when a user tries to enter data (usually the keypress is echoed) Resultunknown pass fail partial
Notes Test cases for JAWS + IE Test case: Use Down arrow (Read next item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use f (Next form field) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: f (Next form field) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Insert + F3 (Open element list) 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:input[type="number"]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 metMode is: auto (do not explicitly change the mode) Issue the command: Insert + F3 (Open element list) After issuing the command, virtual focus should be: na Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use <enter text> (enter text) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <enter text> (enter text) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey changes in value Examples:
When the user enter texts, the screen reader will announce it back to them. Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <keyboard command> (Keyboard command while in forms or application mode) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MAY allow incrementing and decrementing the value Examples:
Desktop screen readers might allow users to adjust the value by pressing up and down arrows Mobile screen readers might allow users to adjust the value by swiping up or down Voice control software might allow someone to say something like "increment <name>" Resultunknown pass fail partial
Notes Test case: Enter invalid text into the number input 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:input[type="number"]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. set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the number input Using the command: "Tab" (Read next focusable item) Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target issue commandsummary: type "two" Using the command: "<enter text>" (enter text) Observe: the input should be rejected and the screen reader should have conveyed that the input was rejected. Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey when input is rejected Examples:
the behavior might be implied if the control is conveyed as something like "number", "spinbox", "spin button", or "incrementable" some AT/browser combinations will allow invalid input but convey the field as invalid screen readers might announce an earcon when the user tries to enter data beyond the maximum length. screen readers might imply that the input was rejected by not announcing anything when a user tries to enter data (usually the keypress is echoed) Resultunknown pass fail partial
Notes Test cases for Narrator + Edge Test case: Use Down arrow (Jump to next item (scan mode)) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use f (Next form field) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: f (Next form field) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use <enter text> (enter text) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <enter text> (enter text) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey changes in value Examples:
When the user enter texts, the screen reader will announce it back to them. Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <keyboard command> (Keyboard command while in forms or application mode) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MAY allow incrementing and decrementing the value Examples:
Desktop screen readers might allow users to adjust the value by pressing up and down arrows Mobile screen readers might allow users to adjust the value by swiping up or down Voice control software might allow someone to say something like "increment <name>" Resultunknown pass fail partial
Notes Test case: Enter invalid text into the number input 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:input[type="number"]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. set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the number input Using the command: "Tab" (Read next focusable item) Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target issue commandsummary: type "two" Using the command: "<enter text>" (enter text) Observe: the input should be rejected and the screen reader should have conveyed that the input was rejected. Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey when input is rejected Examples:
the behavior might be implied if the control is conveyed as something like "number", "spinbox", "spin button", or "incrementable" some AT/browser combinations will allow invalid input but convey the field as invalid screen readers might announce an earcon when the user tries to enter data beyond the maximum length. screen readers might imply that the input was rejected by not announcing anything when a user tries to enter data (usually the keypress is echoed) Resultunknown pass fail partial
Notes Test cases for Narrator + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Narrator + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Narrator + IE The test has not been configured for this combination. Please open a GitHub issue.
Test cases for NVDA + Chrome Test case: Use down arrow (Read next item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use f (Next form field) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: f (Next form field) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use NVDA + F7 (Open Elements List) 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:input[type="number"]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 metMode is: auto (do not explicitly change the mode) Issue the command: NVDA + F7 (Open Elements List) After issuing the command, virtual focus should be: na Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use <enter text> (enter text) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <enter text> (enter text) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey changes in value Examples:
When the user enter texts, the screen reader will announce it back to them. Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <keyboard command> (Keyboard command while in forms or application mode) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MAY allow incrementing and decrementing the value Examples:
Desktop screen readers might allow users to adjust the value by pressing up and down arrows Mobile screen readers might allow users to adjust the value by swiping up or down Voice control software might allow someone to say something like "increment <name>" Resultunknown pass fail partial
Notes Test case: Enter invalid text into the number input 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:input[type="number"]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. set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the number input Using the command: "Tab" (Read next focusable item) Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target issue commandsummary: type "two" Using the command: "<enter text>" (enter text) Observe: the input should be rejected and the screen reader should have conveyed that the input was rejected. Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey when input is rejected Examples:
the behavior might be implied if the control is conveyed as something like "number", "spinbox", "spin button", or "incrementable" some AT/browser combinations will allow invalid input but convey the field as invalid screen readers might announce an earcon when the user tries to enter data beyond the maximum length. screen readers might imply that the input was rejected by not announcing anything when a user tries to enter data (usually the keypress is echoed) Resultunknown pass fail partial
Notes Test cases for NVDA + Edge Test case: Use down arrow (Read next item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use f (Next form field) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: f (Next form field) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use NVDA + F7 (Open Elements List) 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:input[type="number"]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 metMode is: auto (do not explicitly change the mode) Issue the command: NVDA + F7 (Open Elements List) After issuing the command, virtual focus should be: na Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use <enter text> (enter text) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <enter text> (enter text) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey changes in value Examples:
When the user enter texts, the screen reader will announce it back to them. Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <keyboard command> (Keyboard command while in forms or application mode) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MAY allow incrementing and decrementing the value Examples:
Desktop screen readers might allow users to adjust the value by pressing up and down arrows Mobile screen readers might allow users to adjust the value by swiping up or down Voice control software might allow someone to say something like "increment <name>" Resultunknown pass fail partial
Notes Test case: Enter invalid text into the number input 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:input[type="number"]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. set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the number input Using the command: "Tab" (Read next focusable item) Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target issue commandsummary: type "two" Using the command: "<enter text>" (enter text) Observe: the input should be rejected and the screen reader should have conveyed that the input was rejected. Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey when input is rejected Examples:
the behavior might be implied if the control is conveyed as something like "number", "spinbox", "spin button", or "incrementable" some AT/browser combinations will allow invalid input but convey the field as invalid screen readers might announce an earcon when the user tries to enter data beyond the maximum length. screen readers might imply that the input was rejected by not announcing anything when a user tries to enter data (usually the keypress is echoed) Resultunknown pass fail partial
Notes Test cases for NVDA + Firefox Test case: Use down arrow (Read next item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use f (Next form field) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: f (Next form field) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use NVDA + F7 (Open Elements List) 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:input[type="number"]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 metMode is: auto (do not explicitly change the mode) Issue the command: NVDA + F7 (Open Elements List) After issuing the command, virtual focus should be: na Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use <enter text> (enter text) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <enter text> (enter text) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey changes in value Examples:
When the user enter texts, the screen reader will announce it back to them. Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <keyboard command> (Keyboard command while in forms or application mode) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MAY allow incrementing and decrementing the value Examples:
Desktop screen readers might allow users to adjust the value by pressing up and down arrows Mobile screen readers might allow users to adjust the value by swiping up or down Voice control software might allow someone to say something like "increment <name>" Resultunknown pass fail partial
Notes Test case: Enter invalid text into the number input 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:input[type="number"]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. set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the number input Using the command: "Tab" (Read next focusable item) Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target issue commandsummary: type "two" Using the command: "<enter text>" (enter text) Observe: the input should be rejected and the screen reader should have conveyed that the input was rejected. Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey when input is rejected Examples:
the behavior might be implied if the control is conveyed as something like "number", "spinbox", "spin button", or "incrementable" some AT/browser combinations will allow invalid input but convey the field as invalid screen readers might announce an earcon when the user tries to enter data beyond the maximum length. screen readers might imply that the input was rejected by not announcing anything when a user tries to enter data (usually the keypress is echoed) Resultunknown pass fail partial
Notes Test cases for NVDA + IE The test has not been configured for this combination. Please open a GitHub issue.
Test cases for TalkBack + Chrome Test case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use Swipe down (alt+c) (next control (correct reading control must be selected)) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Swipe down (alt+c) (next control (correct reading control must be selected)) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use <enter text> (enter text) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <enter text> (enter text) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey changes in value Examples:
When the user enter texts, the screen reader will announce it back to them. Resultunknown pass fail partial
Notes Test case: Enter invalid text into the number input 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:input[type="number"]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. set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the number input Using the command: "Swipe right (or alt+right arrow)" (Read next item) Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target issue commandsummary: type "two" Using the command: "<enter text>" (enter text) Observe: the input should be rejected and the screen reader should have conveyed that the input was rejected. Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey when input is rejected Examples:
the behavior might be implied if the control is conveyed as something like "number", "spinbox", "spin button", or "incrementable" some AT/browser combinations will allow invalid input but convey the field as invalid screen readers might announce an earcon when the user tries to enter data beyond the maximum length. screen readers might imply that the input was rejected by not announcing anything when a user tries to enter data (usually the keypress is echoed) Resultunknown pass fail partial
Notes Test cases for TalkBack + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Access (Android) + Chrome Test case: Use "Tap <text>" or just "<text>" (Activate item by name) Launch Voice Access (Android) and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:input[type="number"]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. Issue the command: "Tap <text>" or just "<text>" (Activate item by name) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes Test case: Use "Show numbers" (Turn on the numbers overlay) Launch Voice Access (Android) and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:input[type="number"]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. Issue the command: "Show numbers" (Turn on the numbers overlay) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes Test case: Use "{speak text to type}" (dictate) Launch Voice Access (Android) and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:input[type="number"]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. Issue the command: "{speak text to type}" (dictate) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST allow data entry Examples:
Voice control software might allow someone to dictate data into a field once it is focused. Resultunknown pass fail partial
Notes Test cases for Voice Access (Android) + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for VoiceOver (iOS) + Safari Test case: Use Swipe Right (Next item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use Swipe down (next form control (correct item type must be selected)) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Swipe down (next form control (correct item type must be selected)) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use <enter text> (enter text) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <enter text> (enter text) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey changes in value Examples:
When the user enter texts, the screen reader will announce it back to them. Resultunknown pass fail partial
Notes Test case: Enter invalid text into the number input 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:input[type="number"]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. set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the number input Using the command: "Swipe Right" (Next item) Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target issue commandsummary: type "two" Using the command: "<enter text>" (enter text) Observe: the input should be rejected and the screen reader should have conveyed that the input was rejected. Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey when input is rejected Examples:
the behavior might be implied if the control is conveyed as something like "number", "spinbox", "spin button", or "incrementable" some AT/browser combinations will allow invalid input but convey the field as invalid screen readers might announce an earcon when the user tries to enter data beyond the maximum length. screen readers might imply that the input was rejected by not announcing anything when a user tries to enter data (usually the keypress is echoed) Resultunknown pass fail partial
Notes Test cases for VoiceOver (iOS) + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for VoiceOver (macOS) + Safari Test case: Use VO + Right arrow (Read next item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use VO + Command + J (Next Form Control) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: VO + Command + J (Next Form Control) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use VO + U (Open Rotor) 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:input[type="number"]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 metMode is: auto (do not explicitly change the mode) Issue the command: VO + U (Open Rotor) After issuing the command, virtual focus should be: na Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use <enter text> (enter text) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <enter text> (enter text) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey changes in value Examples:
When the user enter texts, the screen reader will announce it back to them. Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <keyboard command> (Keyboard command while in forms or application mode) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MAY allow incrementing and decrementing the value Examples:
Desktop screen readers might allow users to adjust the value by pressing up and down arrows Mobile screen readers might allow users to adjust the value by swiping up or down Voice control software might allow someone to say something like "increment <name>" Resultunknown pass fail partial
Notes Test case: Enter invalid text into the number input 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:input[type="number"]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. set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the number input Using the command: "Tab" (Read next focusable item) Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target issue commandsummary: type "two" Using the command: "<enter text>" (enter text) Observe: the input should be rejected and the screen reader should have conveyed that the input was rejected. Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey when input is rejected Examples:
the behavior might be implied if the control is conveyed as something like "number", "spinbox", "spin button", or "incrementable" some AT/browser combinations will allow invalid input but convey the field as invalid screen readers might announce an earcon when the user tries to enter data beyond the maximum length. screen readers might imply that the input was rejected by not announcing anything when a user tries to enter data (usually the keypress is echoed) Resultunknown pass fail partial
Notes Test cases for VoiceOver (macOS) + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for VoiceOver (macOS) + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Orca + Firefox Test case: Use down arrow (Read next item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual 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 Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes Test case: Use e (Next edit field) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: e (Next edit field) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use alt + shift + f (Open list of form fields) to navigate forward to `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: alt + shift + f (Open list of form fields) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes input[type="number"] element, MUST convey the current value Resultunknown pass fail partial
Notes input[type="number"] element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use <enter text> (enter text) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <enter text> (enter text) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey changes in value Examples:
When the user enter texts, the screen reader will announce it back to them. Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) on the target of `input[type="number"]` 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:input[type="number"]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 metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: <keyboard command> (Keyboard command while in forms or application mode) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MAY allow incrementing and decrementing the value Examples:
Desktop screen readers might allow users to adjust the value by pressing up and down arrows Mobile screen readers might allow users to adjust the value by swiping up or down Voice control software might allow someone to say something like "increment <name>" Resultunknown pass fail partial
Notes Test case: Enter invalid text into the number input 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:input[type="number"]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. set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the number input Using the command: "Tab" (Read next focusable item) Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target issue commandsummary: type "two" Using the command: "<enter text>" (enter text) Observe: the input should be rejected and the screen reader should have conveyed that the input was rejected. Ensure AT location after executing the commandTarget: `input[type="number"]` keyboard focus location: target virtual cursor location: target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey when input is rejected Examples:
the behavior might be implied if the control is conveyed as something like "number", "spinbox", "spin button", or "incrementable" some AT/browser combinations will allow invalid input but convey the field as invalid screen readers might announce an earcon when the user tries to enter data beyond the maximum length. screen readers might imply that the input was rejected by not announcing anything when a user tries to enter data (usually the keypress is echoed) Resultunknown pass fail partial
Notes Test cases for Orca + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Control (iOS) + Safari Test case: Use "Tap <text>" (Activate item by name) Launch Voice Control (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:input[type="number"]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. Issue the command: "Tap <text>" (Activate item by name) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes Test case: Use "{speak text to type}" (dictate) Launch Voice Control (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:input[type="number"]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. Issue the command: "{speak text to type}" (dictate) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST allow data entry Examples:
Voice control software might allow someone to dictate data into a field once it is focused. Resultunknown pass fail partial
Notes Test cases for Voice Control (MacOS) + Safari Test case: Use "Click <text>" (Activate item by name) Launch Voice Control (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:input[type="number"]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. Issue the command: "Click <text>" (Activate item by name) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes Test case: Use "Show numbers" (Turn on the numbers overlay) Launch Voice Control (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:input[type="number"]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. Issue the command: "Show numbers" (Turn on the numbers overlay) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes Test case: Use "{speak text to type}" (dictate) Launch Voice Control (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:input[type="number"]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. Issue the command: "{speak text to type}" (dictate) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST allow data entry Examples:
Voice control software might allow someone to dictate data into a field once it is focused. Resultunknown pass fail partial
Notes Test cases for Voice Control (MacOS) + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Control (MacOS) + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Speech Recognition + Edge Test case: Use "Click <text>" (Activate item by name) Launch Windows Speech Recognition and Edge. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:input[type="number"]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. Issue the command: "Click <text>" (Activate item by name) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes Test case: Use "Show numbers" (Turn on the numbers overlay) Launch Windows Speech Recognition and Edge. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:input[type="number"]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. Issue the command: "Show numbers" (Turn on the numbers overlay) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes Test cases for Windows Speech Recognition + Chrome Test case: Use "Click <text>" (Activate item by name) Launch Windows Speech Recognition and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:input[type="number"]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. Issue the command: "Click <text>" (Activate item by name) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its name Examples:
A screen reader will announce the name (label). Voice control software will let the user say something like "click <name>" to activate the control. Resultunknown pass fail partial
Notes Test case: Use "Show numbers" (Turn on the numbers overlay) Launch Windows Speech Recognition and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:input[type="number"]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. Issue the command: "Show numbers" (Turn on the numbers overlay) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST convey its role Examples:
A screen reader might be announce the role as "number", "text input", "edit", "edit text", "spinbox", "spin button", "incrementable" etc. Voice control software will let the user say something like "click edit" to focus a the input or flag the role with a number. Resultunknown pass fail partial
Notes Test case: Use "{speak text to type}" (dictate) Launch Windows Speech Recognition and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:input[type="number"]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. Issue the command: "{speak text to type}" (dictate) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting input[type="number"] element, MUST allow data entry Examples:
Voice control software might allow someone to dictate data into a field once it is focused. Resultunknown pass fail partial
Notes Test cases for Windows Voice Access + Edge The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Voice Access + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Keyboard + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Keyboard + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Keyboard + Edge The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Mac Keyboard + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Mac Keyboard + Safari The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Mac Keyboard + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for iOS Keyboard + Safari The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Android Keyboard + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Android Keyboard + Firefox The test has not been configured for this combination. Please open a GitHub issue.