Test cases for Dragon Naturally Speaking + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Dragon Naturally Speaking + IE The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Dragon Naturally Speaking + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for JAWS + Chrome Test case: Use Down arrow (Read next item) to navigate forward to `#target-1` 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:#target-1If multiple elements match the selector, repeat this test for all 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 tooltip role, MUST convey its role, applied to div element Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes tooltip role, MUST convey its name, applied to div element Resultunknown pass fail partial
Notes tooltip role, MUST convey boundaries, applied to div element Examples:
Screen readers might announce the starting boundary by conveying the role. Screen readers might announce the ending boundary by conveying something like "leaving tooltip". Resultunknown pass fail partial
Notes tooltip role, SHOULD expose the semantics of content if accessed directly, applied to div element Resultunknown pass fail partial
Notes Test cases for JAWS + Edge Test case: Use Down arrow (Read next item) to navigate forward to `#target-1` 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:#target-1If multiple elements match the selector, repeat this test for all 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 tooltip role, MUST convey its role, applied to div element Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes tooltip role, MUST convey its name, applied to div element Resultunknown pass fail partial
Notes tooltip role, MUST convey boundaries, applied to div element Examples:
Screen readers might announce the starting boundary by conveying the role. Screen readers might announce the ending boundary by conveying something like "leaving tooltip". Resultunknown pass fail partial
Notes tooltip role, SHOULD expose the semantics of content if accessed directly, applied to div element Resultunknown pass fail partial
Notes Test cases for JAWS + Firefox Test case: Use Down arrow (Read next item) to navigate forward to `#target-1` 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:#target-1If multiple elements match the selector, repeat this test for all 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 tooltip role, MUST convey its role, applied to div element Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes tooltip role, MUST convey its name, applied to div element Resultunknown pass fail partial
Notes tooltip role, MUST convey boundaries, applied to div element Examples:
Screen readers might announce the starting boundary by conveying the role. Screen readers might announce the ending boundary by conveying something like "leaving tooltip". Resultunknown pass fail partial
Notes tooltip role, SHOULD expose the semantics of content if accessed directly, applied to div element Resultunknown pass fail partial
Notes Test cases for JAWS + IE The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Narrator + Edge Test case: Use Down arrow (Jump to next item (scan mode)) to navigate forward to `#target-1` 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:#target-1If multiple elements match the selector, repeat this test for all 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 tooltip role, MUST convey its role, applied to div element Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes tooltip role, MUST convey its name, applied to div element Resultunknown pass fail partial
Notes tooltip role, MUST convey boundaries, applied to div element Examples:
Screen readers might announce the starting boundary by conveying the role. Screen readers might announce the ending boundary by conveying something like "leaving tooltip". Resultunknown pass fail partial
Notes tooltip role, SHOULD expose the semantics of content if accessed directly, applied to div element 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 `#target-1` 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:#target-1If multiple elements match the selector, repeat this test for all 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 tooltip role, MUST convey its role, applied to div element Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes tooltip role, MUST convey its name, applied to div element Resultunknown pass fail partial
Notes tooltip role, MUST convey boundaries, applied to div element Examples:
Screen readers might announce the starting boundary by conveying the role. Screen readers might announce the ending boundary by conveying something like "leaving tooltip". Resultunknown pass fail partial
Notes tooltip role, SHOULD expose the semantics of content if accessed directly, applied to div element Resultunknown pass fail partial
Notes Test cases for NVDA + Edge Test case: Use down arrow (Read next item) to navigate forward to `#target-1` 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:#target-1If multiple elements match the selector, repeat this test for all 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 tooltip role, MUST convey its role, applied to div element Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes tooltip role, MUST convey its name, applied to div element Resultunknown pass fail partial
Notes tooltip role, MUST convey boundaries, applied to div element Examples:
Screen readers might announce the starting boundary by conveying the role. Screen readers might announce the ending boundary by conveying something like "leaving tooltip". Resultunknown pass fail partial
Notes tooltip role, SHOULD expose the semantics of content if accessed directly, applied to div element Resultunknown pass fail partial
Notes Test cases for NVDA + Firefox Test case: Use down arrow (Read next item) to navigate forward to `#target-1` 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:#target-1If multiple elements match the selector, repeat this test for all 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 tooltip role, MUST convey its role, applied to div element Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes tooltip role, MUST convey its name, applied to div element Resultunknown pass fail partial
Notes tooltip role, MUST convey boundaries, applied to div element Examples:
Screen readers might announce the starting boundary by conveying the role. Screen readers might announce the ending boundary by conveying something like "leaving tooltip". Resultunknown pass fail partial
Notes tooltip role, SHOULD expose the semantics of content if accessed directly, applied to div element 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 `#target-1` 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:#target-1If multiple elements match the selector, repeat this test for all 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 tooltip role, MUST convey its role, applied to div element Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes tooltip role, MUST convey its name, applied to div element Resultunknown pass fail partial
Notes tooltip role, MUST convey boundaries, applied to div element Examples:
Screen readers might announce the starting boundary by conveying the role. Screen readers might announce the ending boundary by conveying something like "leaving tooltip". Resultunknown pass fail partial
Notes tooltip role, SHOULD expose the semantics of content if accessed directly, applied to div element Resultunknown pass fail partial
Notes Test cases for TalkBack + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Access (Android) + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Access (Android) + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for VoiceOver (iOS) + Safari Test case: Use Swipe Right (Next item) to navigate forward to `#target-1` 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:#target-1If multiple elements match the selector, repeat this test for all 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 tooltip role, MUST convey its role, applied to div element Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes tooltip role, MUST convey its name, applied to div element Resultunknown pass fail partial
Notes tooltip role, MUST convey boundaries, applied to div element Examples:
Screen readers might announce the starting boundary by conveying the role. Screen readers might announce the ending boundary by conveying something like "leaving tooltip". Resultunknown pass fail partial
Notes tooltip role, SHOULD expose the semantics of content if accessed directly, applied to div element 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 `#target-1` 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:#target-1If multiple elements match the selector, repeat this test for all 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 tooltip role, MUST convey its role, applied to div element Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes tooltip role, MUST convey its name, applied to div element Resultunknown pass fail partial
Notes tooltip role, MUST convey boundaries, applied to div element Examples:
Screen readers might announce the starting boundary by conveying the role. Screen readers might announce the ending boundary by conveying something like "leaving tooltip". Resultunknown pass fail partial
Notes tooltip role, SHOULD expose the semantics of content if accessed directly, applied to div element Resultunknown pass fail partial
Notes Test case: Use VO + Right arrow (Read next item) to navigate forward to `#target-1` 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:#target-1If multiple elements match the selector, repeat this test for all 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 tooltip role, MUST convey boundaries, applied to div element Examples:
Screen readers might announce the starting boundary by conveying the role. Screen readers might announce the ending boundary by conveying something like "leaving tooltip". 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 `#target-1` 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:#target-1If multiple elements match the selector, repeat this test for all 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 tooltip role, MUST convey its role, applied to div element Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes tooltip role, MUST convey its name, applied to div element Resultunknown pass fail partial
Notes tooltip role, MUST convey boundaries, applied to div element Examples:
Screen readers might announce the starting boundary by conveying the role. Screen readers might announce the ending boundary by conveying something like "leaving tooltip". Resultunknown pass fail partial
Notes tooltip role, SHOULD expose the semantics of content if accessed directly, applied to div element 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 The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Control (MacOS) + Safari The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Control (MacOS) + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Control (MacOS) + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Speech Recognition + Edge The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Speech Recognition + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Voice Access + Edge The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Voice Access + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Keyboard + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Keyboard + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Keyboard + Edge The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Mac Keyboard + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Mac Keyboard + Safari The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Mac Keyboard + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for iOS Keyboard + Safari The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Android Keyboard + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Android Keyboard + Firefox The test has not been configured for this combination. Please open a GitHub issue.