Test cases for Dragon Naturally Speaking + Chrome The test has not been configured for this combination. Please open a GitHub issue.
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 r (Next region) to navigate forward to `role="main"` 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:role="main"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: r (Next region) 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Ctrl + Insert + r (List regions) to navigate forward to `role="main"` 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:role="main"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: Ctrl + Insert + r (List regions) 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `role="main" > button` 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:role="main" > buttonIf 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use Shift + Tab (Read previous focusable item) to navigate backwards to `role="main" > button` 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:role="main" > buttonIf 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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: Shift + Tab (Read previous 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use Down arrow (Read next item) to navigate forward to the start of `role="main"` 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:role="main"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: start of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use Up arrow (Read previous item) to navigate backwards to the end of `role="main"` 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:role="main"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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: Up arrow (Read previous item) After issuing the command, virtual focus should be: end of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test cases for JAWS + Edge Test case: Use r (Next region) to navigate forward to `role="main"` 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:role="main"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: r (Next region) 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Ctrl + Insert + r (List regions) to navigate forward to `role="main"` 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:role="main"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: Ctrl + Insert + r (List regions) 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `role="main" > button` 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:role="main" > buttonIf 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use Shift + Tab (Read previous focusable item) to navigate backwards to `role="main" > button` 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:role="main" > buttonIf 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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: Shift + Tab (Read previous 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use Down arrow (Read next item) to navigate forward to the start of `role="main"` 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:role="main"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: start of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use Up arrow (Read previous item) to navigate backwards to the end of `role="main"` 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:role="main"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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: Up arrow (Read previous item) After issuing the command, virtual focus should be: end of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test cases for JAWS + Firefox Test case: Use r (Next region) to navigate forward to `role="main"` 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:role="main"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: r (Next region) 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Ctrl + Insert + r (List regions) to navigate forward to `role="main"` 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:role="main"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: Ctrl + Insert + r (List regions) 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `role="main" > button` 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:role="main" > buttonIf 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use Shift + Tab (Read previous focusable item) to navigate backwards to `role="main" > button` 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:role="main" > buttonIf 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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: Shift + Tab (Read previous 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use Down arrow (Read next item) to navigate forward to the start of `role="main"` 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:role="main"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: start of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use Up arrow (Read previous item) to navigate backwards to the end of `role="main"` 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:role="main"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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: Up arrow (Read previous item) After issuing the command, virtual focus should be: end of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test cases for JAWS + IE The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Narrator + Edge Test case: Use d (Next landmark) to navigate forward to `role="main"` 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:role="main"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: d (Next landmark) 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Narrator + N (Move to main landmark) to navigate forward to `role="main"` 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:role="main"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: Narrator + N (Move to main landmark) 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Narrator + F5 (List landmarks) to navigate forward to `role="main"` 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:role="main"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: Narrator + F5 (List landmarks) 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `role="main" > button` 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:role="main" > buttonIf 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 main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `role="main" > button` 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:role="main" > buttonIf 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes Test case: Use Shift + Tab (Read previous focusable item) to navigate backwards to `role="main" > button` 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:role="main" > buttonIf 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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: Shift + Tab (Read previous 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 main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use Shift + Tab (Read previous focusable item) to navigate backwards to `role="main" > button` 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:role="main" > buttonIf 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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: Shift + Tab (Read previous 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes Test case: Use Down arrow (Jump to next item (scan mode)) to navigate forward to the start of `role="main"` 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:role="main"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: start of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use Up arrow (Jump to previous item (scan mode)) to navigate backwards to the end of `role="main"` 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:role="main"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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: Up arrow (Jump to previous item (scan mode)) After issuing the command, virtual focus should be: end of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line 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 d (Next landmark) to navigate forward to `role="main"` 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:role="main"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: d (Next landmark) 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use NVDA + F7 (Open Elements List) to navigate forward to `role="main"` 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:role="main"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: NVDA + F7 (Open Elements List) 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `role="main" > button` 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:role="main" > buttonIf 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use Shift + Tab (Read previous focusable item) to navigate backwards to `role="main" > button` 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:role="main" > buttonIf 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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: Shift + Tab (Read previous 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use down arrow (Read next item) to navigate forward to the start of `role="main"` 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:role="main"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: start of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use up arrow (Read previous item) to navigate backwards to the end of `role="main"` 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:role="main"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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: up arrow (Read previous item) After issuing the command, virtual focus should be: end of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test cases for NVDA + Edge Test case: Use d (Next landmark) to navigate forward to `role="main"` 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:role="main"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: d (Next landmark) 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use NVDA + F7 (Open Elements List) to navigate forward to `role="main"` 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:role="main"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: NVDA + F7 (Open Elements List) 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `role="main" > button` 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:role="main" > buttonIf 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use Shift + Tab (Read previous focusable item) to navigate backwards to `role="main" > button` 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:role="main" > buttonIf 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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: Shift + Tab (Read previous 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use down arrow (Read next item) to navigate forward to the start of `role="main"` 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:role="main"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: start of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use up arrow (Read previous item) to navigate backwards to the end of `role="main"` 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:role="main"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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: up arrow (Read previous item) After issuing the command, virtual focus should be: end of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test cases for NVDA + Firefox Test case: Use d (Next landmark) to navigate forward to `role="main"` 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:role="main"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: d (Next landmark) 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use NVDA + F7 (Open Elements List) to navigate forward to `role="main"` 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:role="main"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: NVDA + F7 (Open Elements List) 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `role="main" > button` 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:role="main" > buttonIf 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use Shift + Tab (Read previous focusable item) to navigate backwards to `role="main" > button` 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:role="main" > buttonIf 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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: Shift + Tab (Read previous 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use down arrow (Read next item) to navigate forward to the start of `role="main"` 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:role="main"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: start of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use up arrow (Read previous item) to navigate backwards to the end of `role="main"` 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:role="main"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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: up arrow (Read previous item) After issuing the command, virtual focus should be: end of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line 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 down after changing the reading control to 'landmarks' (alt+D) (Next landmark) to navigate forward to `role="main"` 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:role="main"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 after changing the reading control to 'landmarks' (alt+D) (Next landmark) 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to the start of `role="main"` 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:role="main"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: start of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use Swipe left (or alt+left arrow) (Read previous item) to navigate backwards to the end of `role="main"` 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:role="main"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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: Swipe left (or alt+left arrow) (Read previous item) After issuing the command, virtual focus should be: end of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line 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 The test has not been configured for this combination. Please open a GitHub issue.
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 down (next landmark (correct item type must be selected)) to navigate forward to `role="main"` 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:role="main"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 landmark (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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Swipe Right (Next item) to navigate forward to the start of `role="main"` 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:role="main"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: start of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use Swipe Left (Previous item) to navigate backwards to the end of `role="main"` 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:role="main"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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: Swipe Left (Previous item) After issuing the command, virtual focus should be: end of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line 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 + U (Open Rotor) to navigate forward to `role="main"` 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:role="main"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 + U (Open Rotor) 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `role="main" > button` 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:role="main" > buttonIf 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use Shift + Tab (Read previous focusable item) to navigate backwards to `role="main" > button` 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:role="main" > buttonIf 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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: Shift + Tab (Read previous 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 main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use VO + Right arrow (Read next item) to navigate forward to the start of `role="main"` 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:role="main"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: start of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line Resultunknown pass fail partial
Notes Test case: Use VO + Left Arrow (Read previous item) to navigate backwards to the end of `role="main"` 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:role="main"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: after target Keyboard focus is: after target Mode is: auto (do not explicitly change the mode) Issue the command: VO + Left Arrow (Read previous item) After issuing the command, virtual focus should be: end of target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting main role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes main role, MUST convey its name Resultunknown pass fail partial
Notes main role, MUST convey the boundaries of the element Examples:
A screen reader might announce the role of the element when entering and say something like "leaving" when exiting. A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example). A screen reader might announce position in set information such as "1 of 6". A screen reader might not convey boundaries if the content fits on a single line 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 The test has not been configured for this combination. Please open a GitHub issue.
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 The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Control (MacOS) + Safari The test has not been configured for this combination. Please open a GitHub issue.
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 The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Speech Recognition + Chrome The test has not been configured for this combination. Please open a GitHub issue.
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.