Test cases for Dragon Naturally Speaking + Chrome Test case: Use "Click <text>" (Activate item by name) Launch Dragon Naturally Speaking and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Issue the command: "Click <text>" (Activate item by name) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes Test case: Use Click <role> (Click Type) Launch Dragon Naturally Speaking and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Issue the command: Click <role> (Click Type) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes Test cases for Dragon Naturally Speaking + IE The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Dragon Naturally Speaking + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for JAWS + Chrome Test case: Use Down arrow (Read next item) to navigate forward to `details` 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:detailsIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting details element, MUST convey its role Examples:
A screen reader might announce the role as "group" or "details" A screen reader might consider the group as presentational and not convey a group role Resultunknown pass fail partial
Notes details element, MUST convey the name of the group if the group role is conveyed Resultunknown pass fail partial
Notes details element, MUST convey the boundaries of the details element if the group role is conveyed 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 `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `summary` 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:summaryIf 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 summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) to navigate forward to `summary` 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:summaryIf 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: Enter or Space (Activate Button) 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 summary element, MUST convey when the expanded state is changed Examples:
A screen reader might announce the new new state value, either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use b (Next button) to navigate forward to `summary` 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:summaryIf 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: b (Next button) 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 summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use f (Next form field) to navigate forward to `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: f (Next form field) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Down arrow (Read next item) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting h1, h2, h3, h4, h5, and h6 elements, MUST convey its role, level, and name Examples:
When applied to a heading, the heading might be announced as something like "<name> heading level <level>" Resultunknown pass fail partial
Notes Test case: Use h (Next heading) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If 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: h (Next heading) 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 h1, h2, h3, h4, h5, and h6 elements, SHOULD provide shortcuts to jump to headings Resultunknown pass fail partial
Notes Test cases for JAWS + Edge Test case: Use Down arrow (Read next item) to navigate forward to `details` 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:detailsIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting details element, MUST convey its role Examples:
A screen reader might announce the role as "group" or "details" A screen reader might consider the group as presentational and not convey a group role Resultunknown pass fail partial
Notes details element, MUST convey the name of the group if the group role is conveyed Resultunknown pass fail partial
Notes details element, MUST convey the boundaries of the details element if the group role is conveyed 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 `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `summary` 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:summaryIf 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 summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) to navigate forward to `summary` 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:summaryIf 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: Enter or Space (Activate Button) 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 summary element, MUST convey when the expanded state is changed Examples:
A screen reader might announce the new new state value, either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use b (Next button) to navigate forward to `summary` 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:summaryIf 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: b (Next button) 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 summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use f (Next form field) to navigate forward to `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: f (Next form field) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Down arrow (Read next item) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting h1, h2, h3, h4, h5, and h6 elements, MUST convey its role, level, and name Examples:
When applied to a heading, the heading might be announced as something like "<name> heading level <level>" Resultunknown pass fail partial
Notes Test case: Use h (Next heading) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If 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: h (Next heading) 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 h1, h2, h3, h4, h5, and h6 elements, SHOULD provide shortcuts to jump to headings Resultunknown pass fail partial
Notes Test cases for JAWS + Firefox Test case: Use Down arrow (Read next item) to navigate forward to `details` 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:detailsIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting details element, MUST convey its role Examples:
A screen reader might announce the role as "group" or "details" A screen reader might consider the group as presentational and not convey a group role Resultunknown pass fail partial
Notes details element, MUST convey the name of the group if the group role is conveyed Resultunknown pass fail partial
Notes details element, MUST convey the boundaries of the details element if the group role is conveyed 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 `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `summary` 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:summaryIf 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 summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) to navigate forward to `summary` 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:summaryIf 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: Enter or Space (Activate Button) 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 summary element, MUST convey when the expanded state is changed Examples:
A screen reader might announce the new new state value, either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use b (Next button) to navigate forward to `summary` 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:summaryIf 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: b (Next button) 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 summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use f (Next form field) to navigate forward to `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: f (Next form field) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Down arrow (Read next item) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting h1, h2, h3, h4, h5, and h6 elements, MUST convey its role, level, and name Examples:
When applied to a heading, the heading might be announced as something like "<name> heading level <level>" Resultunknown pass fail partial
Notes Test case: Use h (Next heading) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If 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: h (Next heading) 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 h1, h2, h3, h4, h5, and h6 elements, SHOULD provide shortcuts to jump to headings Resultunknown pass fail partial
Notes Test cases for JAWS + IE Test case: Use Down arrow (Read next item) to navigate forward to `details` Launch JAWS and IE. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:detailsIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting details element, MUST convey its role Examples:
A screen reader might announce the role as "group" or "details" A screen reader might consider the group as presentational and not convey a group role Resultunknown pass fail partial
Notes details element, MUST convey the name of the group if the group role is conveyed Resultunknown pass fail partial
Notes details element, MUST convey the boundaries of the details element if the group role is conveyed 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 `summary` Launch JAWS and IE. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `summary` Launch JAWS and IE. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf 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 summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) to navigate forward to `summary` Launch JAWS and IE. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf 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: Enter or Space (Activate Button) 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 summary element, MUST convey when the expanded state is changed Examples:
A screen reader might announce the new new state value, either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use b (Next button) to navigate forward to `summary` Launch JAWS and IE. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf 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: b (Next button) 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 summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use f (Next form field) to navigate forward to `summary` Launch JAWS and IE. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: f (Next form field) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Down arrow (Read next item) to navigate forward to `h1, h2, h3, h4, h5, h6` Launch JAWS and IE. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:h1, h2, h3, h4, h5, h6If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting h1, h2, h3, h4, h5, and h6 elements, MUST convey its role, level, and name Examples:
When applied to a heading, the heading might be announced as something like "<name> heading level <level>" Resultunknown pass fail partial
Notes Test case: Use h (Next heading) to navigate forward to `h1, h2, h3, h4, h5, h6` Launch JAWS and IE. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:h1, h2, h3, h4, h5, h6If 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: h (Next heading) 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 h1, h2, h3, h4, h5, and h6 elements, SHOULD provide shortcuts to jump to headings Resultunknown pass fail partial
Notes Test cases for Narrator + Edge Test case: Use Down arrow (Jump to next item (scan mode)) to navigate forward to `details` 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:detailsIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Down arrow (Jump to next item (scan mode)) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting details element, MUST convey its role Examples:
A screen reader might announce the role as "group" or "details" A screen reader might consider the group as presentational and not convey a group role Resultunknown pass fail partial
Notes details element, MUST convey the name of the group if the group role is conveyed Resultunknown pass fail partial
Notes details element, MUST convey the boundaries of the details element if the group role is conveyed 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 (Jump to next item (scan mode)) to navigate forward to `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Down arrow (Jump to next item (scan mode)) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `summary` 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:summaryIf 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 summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Enter or Space Bar (Activate Item (primary action)) to navigate forward to `summary` 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:summaryIf 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: Enter or Space Bar (Activate Item (primary action)) 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 summary element, MUST convey when the expanded state is changed Examples:
A screen reader might announce the new new state value, either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use b (Next button) to navigate forward to `summary` 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:summaryIf 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: b (Next button) 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 summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use f (Next form field) to navigate forward to `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: f (Next form field) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Down arrow (Jump to next item (scan mode)) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Down arrow (Jump to next item (scan mode)) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting h1, h2, h3, h4, h5, and h6 elements, MUST convey its role, level, and name Examples:
When applied to a heading, the heading might be announced as something like "<name> heading level <level>" Resultunknown pass fail partial
Notes Test case: Use h (Next heading) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If 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: h (Next heading) 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 h1, h2, h3, h4, h5, and h6 elements, SHOULD provide shortcuts to jump to headings Resultunknown pass fail partial
Notes Test cases for Narrator + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Narrator + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Narrator + IE The test has not been configured for this combination. Please open a GitHub issue.
Test cases for NVDA + Chrome Test case: Use down arrow (Read next item) to navigate forward to `details` 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:detailsIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting details element, MUST convey its role Examples:
A screen reader might announce the role as "group" or "details" A screen reader might consider the group as presentational and not convey a group role Resultunknown pass fail partial
Notes details element, MUST convey the name of the group if the group role is conveyed Resultunknown pass fail partial
Notes details element, MUST convey the boundaries of the details element if the group role is conveyed 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 `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `summary` 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:summaryIf 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 summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) to navigate forward to `summary` 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:summaryIf 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: Enter or Space (Activate Button) 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 summary element, MUST convey when the expanded state is changed Examples:
A screen reader might announce the new new state value, either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use b (Next button) to navigate forward to `summary` 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:summaryIf 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: b (Next button) 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 summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use f (Next form field) to navigate forward to `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: f (Next form field) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use down arrow (Read next item) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting h1, h2, h3, h4, h5, and h6 elements, MUST convey its role, level, and name Examples:
When applied to a heading, the heading might be announced as something like "<name> heading level <level>" Resultunknown pass fail partial
Notes Test case: Use h (Next heading) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If 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: h (Next heading) 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 h1, h2, h3, h4, h5, and h6 elements, SHOULD provide shortcuts to jump to headings Resultunknown pass fail partial
Notes Test cases for NVDA + Edge Test case: Use down arrow (Read next item) to navigate forward to `details` 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:detailsIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting details element, MUST convey its role Examples:
A screen reader might announce the role as "group" or "details" A screen reader might consider the group as presentational and not convey a group role Resultunknown pass fail partial
Notes details element, MUST convey the name of the group if the group role is conveyed Resultunknown pass fail partial
Notes details element, MUST convey the boundaries of the details element if the group role is conveyed 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 `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `summary` 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:summaryIf 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 summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) to navigate forward to `summary` 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:summaryIf 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: Enter or Space (Activate Button) 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 summary element, MUST convey when the expanded state is changed Examples:
A screen reader might announce the new new state value, either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use b (Next button) to navigate forward to `summary` 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:summaryIf 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: b (Next button) 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 summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use f (Next form field) to navigate forward to `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: f (Next form field) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use down arrow (Read next item) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting h1, h2, h3, h4, h5, and h6 elements, MUST convey its role, level, and name Examples:
When applied to a heading, the heading might be announced as something like "<name> heading level <level>" Resultunknown pass fail partial
Notes Test case: Use h (Next heading) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If 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: h (Next heading) 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 h1, h2, h3, h4, h5, and h6 elements, SHOULD provide shortcuts to jump to headings Resultunknown pass fail partial
Notes Test cases for NVDA + Firefox Test case: Use down arrow (Read next item) to navigate forward to `details` 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:detailsIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting details element, MUST convey its role Examples:
A screen reader might announce the role as "group" or "details" A screen reader might consider the group as presentational and not convey a group role Resultunknown pass fail partial
Notes details element, MUST convey the name of the group if the group role is conveyed Resultunknown pass fail partial
Notes details element, MUST convey the boundaries of the details element if the group role is conveyed 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 `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `summary` 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:summaryIf 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 summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) to navigate forward to `summary` 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:summaryIf 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: Enter or Space (Activate Button) 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 summary element, MUST convey when the expanded state is changed Examples:
A screen reader might announce the new new state value, either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use b (Next button) to navigate forward to `summary` 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:summaryIf 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: b (Next button) 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 summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use f (Next form field) to navigate forward to `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: f (Next form field) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use down arrow (Read next item) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting h1, h2, h3, h4, h5, and h6 elements, MUST convey its role, level, and name Examples:
When applied to a heading, the heading might be announced as something like "<name> heading level <level>" Resultunknown pass fail partial
Notes Test case: Use h (Next heading) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If 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: h (Next heading) 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 h1, h2, h3, h4, h5, and h6 elements, SHOULD provide shortcuts to jump to headings Resultunknown pass fail partial
Notes Test cases for NVDA + IE The test has not been configured for this combination. Please open a GitHub issue.
Test cases for TalkBack + Chrome Test case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `details` 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:detailsIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Swipe right (or alt+right arrow) (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting details element, MUST convey its role Examples:
A screen reader might announce the role as "group" or "details" A screen reader might consider the group as presentational and not convey a group role Resultunknown pass fail partial
Notes details element, MUST convey the name of the group if the group role is conveyed Resultunknown pass fail partial
Notes details element, MUST convey the boundaries of the details element if the group role is conveyed 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 right (or alt+right arrow) (Read next item) to navigate forward to `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Swipe right (or alt+right arrow) (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use double tap (or alt+enter) (Activate button) to navigate forward to `summary` 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:summaryIf 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: double tap (or alt+enter) (Activate button) 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 summary element, MUST convey when the expanded state is changed Examples:
A screen reader might announce the new new state value, either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Swipe down (alt+c) (next control (correct reading control must be selected)) to navigate forward to `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Swipe down (alt+c) (next control (correct reading control must be selected)) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, 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 `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Swipe right (or alt+right arrow) (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting h1, h2, h3, h4, h5, and h6 elements, MUST convey its role, level, and name Examples:
When applied to a heading, the heading might be announced as something like "<name> heading level <level>" Resultunknown pass fail partial
Notes Test case: Use Swipe down (alt+H) (next heading (correct reading control must be selected)) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Swipe down (alt+H) (next heading (correct reading control must be selected)) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting h1, h2, h3, h4, h5, and h6 elements, SHOULD provide shortcuts to jump to headings Resultunknown pass fail partial
Notes Test cases for TalkBack + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Access (Android) + Chrome Test case: Use "Tap <text>" or just "<text>" (Activate item by name) Launch Voice Access (Android) and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Issue the command: "Tap <text>" or just "<text>" (Activate item by name) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes Test case: Use "Show numbers" (Turn on the numbers overlay) Launch Voice Access (Android) and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Issue the command: "Show numbers" (Turn on the numbers overlay) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes Test cases for Voice Access (Android) + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for VoiceOver (iOS) + Safari Test case: Use Swipe Right (Next item) to navigate forward to `details` 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:detailsIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Swipe Right (Next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting details element, MUST convey its role Examples:
A screen reader might announce the role as "group" or "details" A screen reader might consider the group as presentational and not convey a group role Resultunknown pass fail partial
Notes details element, MUST convey the name of the group if the group role is conveyed Resultunknown pass fail partial
Notes details element, MUST convey the boundaries of the details element if the group role is conveyed 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 Right (Next item) to navigate forward to `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Swipe Right (Next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes summary element, MUST convey when the expanded state is changed Examples:
A screen reader might announce the new new state value, either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Swipe down (next form control (correct item type must be selected)) to navigate forward to `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Swipe down (next form control (correct item type must be selected)) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use Swipe Right (Next item) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Swipe Right (Next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting h1, h2, h3, h4, h5, and h6 elements, MUST convey its role, level, and name Examples:
When applied to a heading, the heading might be announced as something like "<name> heading level <level>" Resultunknown pass fail partial
Notes Test case: Use Swipe down (next heading (correct item type must be selected)) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If 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 heading (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 h1, h2, h3, h4, h5, and h6 elements, SHOULD provide shortcuts to jump to headings Resultunknown pass fail partial
Notes Test cases for VoiceOver (iOS) + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for VoiceOver (macOS) + Safari Test case: Use VO + Right arrow (Read next item) to navigate forward to `details` 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:detailsIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: VO + Right arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting details element, MUST convey its role Examples:
A screen reader might announce the role as "group" or "details" A screen reader might consider the group as presentational and not convey a group role Resultunknown pass fail partial
Notes details element, MUST convey the name of the group if the group role is conveyed Resultunknown pass fail partial
Notes details element, MUST convey the boundaries of the details element if the group role is conveyed 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 `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: VO + Right arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `summary` 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:summaryIf 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 summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use VO + space (Activate Button) to navigate forward to `summary` 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:summaryIf 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 + space (Activate Button) 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 summary element, MUST convey when the expanded state is changed Examples:
A screen reader might announce the new new state value, either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use VO + Command + J (Next Form Control) to navigate forward to `summary` 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:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: VO + Command + J (Next Form Control) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use VO + Right arrow (Read next item) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: VO + Right arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting h1, h2, h3, h4, h5, and h6 elements, MUST convey its role, level, and name Examples:
When applied to a heading, the heading might be announced as something like "<name> heading level <level>" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If 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 h1, h2, h3, h4, h5, and h6 elements, MUST convey its role, level, and name Examples:
When applied to a heading, the heading might be announced as something like "<name> heading level <level>" Resultunknown pass fail partial
Notes Test case: Use VO + Command + H (Next Heading) to navigate forward to `h1, h2, h3, h4, h5, h6` 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:h1, h2, h3, h4, h5, h6If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: VO + Command + H (Next Heading) 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 h1, h2, h3, h4, h5, and h6 elements, SHOULD provide shortcuts to jump to headings Resultunknown pass fail partial
Notes Test cases for VoiceOver (macOS) + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for VoiceOver (macOS) + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Orca + Firefox Test case: Use down arrow (Read next item) to navigate forward to `details` Launch Orca and Firefox. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:detailsIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting details element, MUST convey its role Examples:
A screen reader might announce the role as "group" or "details" A screen reader might consider the group as presentational and not convey a group role Resultunknown pass fail partial
Notes details element, MUST convey the name of the group if the group role is conveyed Resultunknown pass fail partial
Notes details element, MUST convey the boundaries of the details element if the group role is conveyed 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 `summary` Launch Orca and Firefox. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `summary` Launch Orca and Firefox. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf 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 summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes summary element, MUST convey the expanded state Examples:
A screen reader might announce either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) to navigate forward to `summary` Launch Orca and Firefox. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf 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: Enter or Space (Activate Button) 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 summary element, MUST convey when the expanded state is changed Examples:
A screen reader might announce the new new state value, either "expanded" or "collapsed" Resultunknown pass fail partial
Notes Test case: Use b (Next button) to navigate forward to `summary` Launch Orca and Firefox. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf 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: b (Next button) 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 summary element, SHOULD provide shortcuts to jump to this role Resultunknown pass fail partial
Notes Test case: Use down arrow (Read next item) to navigate forward to `h1, h2, h3, h4, h5, h6` Launch Orca and Firefox. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:h1, h2, h3, h4, h5, h6If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: down arrow (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting h1, h2, h3, h4, h5, and h6 elements, MUST convey its role, level, and name Examples:
When applied to a heading, the heading might be announced as something like "<name> heading level <level>" Resultunknown pass fail partial
Notes Test case: Use h (Next heading) to navigate forward to `h1, h2, h3, h4, h5, h6` Launch Orca and Firefox. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:h1, h2, h3, h4, h5, h6If 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: h (Next heading) 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 h1, h2, h3, h4, h5, and h6 elements, SHOULD provide shortcuts to jump to headings Resultunknown pass fail partial
Notes Test cases for Orca + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Control (iOS) + Safari Test case: Use "Tap <text>" (Activate item by name) Launch Voice Control (iOS) and Safari. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Issue the command: "Tap <text>" (Activate item by name) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes Test cases for Voice Control (MacOS) + Safari Test case: Use "Click <text>" (Activate item by name) Launch Voice Control (MacOS) and Safari. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Issue the command: "Click <text>" (Activate item by name) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes Test case: Use "Show numbers" (Turn on the numbers overlay) Launch Voice Control (MacOS) and Safari. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Issue the command: "Show numbers" (Turn on the numbers overlay) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes Test cases for Voice Control (MacOS) + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Control (MacOS) + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Speech Recognition + Edge Test case: Use "Click <text>" (Activate item by name) Launch Windows Speech Recognition and Edge. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Issue the command: "Click <text>" (Activate item by name) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes Test case: Use "Show numbers" (Turn on the numbers overlay) Launch Windows Speech Recognition and Edge. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Issue the command: "Show numbers" (Turn on the numbers overlay) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes Test cases for Windows Speech Recognition + Chrome Test case: Use "Click <text>" (Activate item by name) Launch Windows Speech Recognition and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Issue the command: "Click <text>" (Activate item by name) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its name Examples:
A screen reader might announce something like "<role>, <name>" Voice control software might allow the user to say something like "click <name>" Resultunknown pass fail partial
Notes Test case: Use "Show numbers" (Turn on the numbers overlay) Launch Windows Speech Recognition and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:summaryIf multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue. Issue the command: "Show numbers" (Turn on the numbers overlay) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting summary element, MUST convey its role Examples:
A screen reader might announce something like "button", "details", or "summary" Voice control software might allow the user to say something like "click button" Resultunknown pass fail partial
Notes Test cases for Windows Voice Access + Edge The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Voice Access + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Keyboard + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Keyboard + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Keyboard + Edge The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Mac Keyboard + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Mac Keyboard + Safari The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Mac Keyboard + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for iOS Keyboard + Safari The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Android Keyboard + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Android Keyboard + Firefox The test has not been configured for this combination. Please open a GitHub issue.