RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://a11ysupport.io/tests/aria_alertdialog_document_mode below:

Test: ARIA alertdialog role must use document mode

Screen Reader support level: supported

Voice Control support level: unknown

On this page

About this test

This test ensures the alertdialog role does not invoke application mode in screen readers. The default mode (document) must be used. ARIA 1.0 had language for the alertdialog role that could suggest that application mode must be invoked. However, that language was clarified in aria 1.1.

Submit new test results Age of results

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

Test HTMLOpen the test case HTML file

<!DOCTYPE html>
<html lang="en">
<head>
    <title>ARIA alertdialog role document mode test</title>
</head>
<body>
<button>Go to Dialog</button>
<div role="alertdialog" aria-label="test">
    <h1 tabindex="-1">Test Dialog</h1>
    <p>paragraph before</p>
    <p id="target">target</p>
    <p>paragraph after</p>
</div>

<script>
    /** It is necessary to send focus to an element inside of the dialog in order for some screen readers (NVDA) to read its contents. **/
    document.querySelector('button').addEventListener("click", function(){
        document.querySelector('h1').focus();
    });
</script>
</body>
</html>

Summary of Screen Reader support by expectation

* means that some support is hidden behind settings

Summary of Voice Control support by expectation alertdialog role Expectation Dragon Naturally Speaking Voice Access (Android) Voice Control (iOS) Voice Control (MacOS) Windows Speech Recognition Windows Voice Access Chrome Chrome Safari Safari Edge Chrome Edge Chrome Not applicable

* means that some support is hidden behind settings

Summary of Keyboard support by expectation alertdialog role Expectation Windows Keyboard Mac Keyboard iOS Keyboard Android Keyboard Chrome Firefox Edge Chrome Safari Safari Chrome Not applicable

* means that some support is hidden behind settings

Detailed support results by expectation Expectation for the alertdialog role: NOT automatically switch away from reading mode

This expectation is from the alertdialog role feature.

Strength of this expectation for different types of assistive technologies:

Screen Readers: MUST
Voice Control: NA

Grading method:

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

AT Browser Has Support Output Dragon Naturally Speaking Chrome not applicable - JAWS Chrome yes

Result: (pass)
- Test Case: Use Down arrow (Read next item) to navigate forward to `*[role="alertdialog"]`
  1. Launch JAWS and Chrome.
  2. Navigate to the test page.
  3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="alertdialog"]
    - If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
  4. Position and configure the screen reader so that the following conditions are met
    - Virtual focus is: before target
    - Keyboard focus is: before target
    - Mode is: auto (do not explicitly change the mode)
  5. Issue the command: Down arrow (Read next item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: target

JAWS Edge yes

Result: (pass)
- Test Case: Use Down arrow (Read next item) to navigate forward to `*[role="alertdialog"]`
  1. Launch JAWS and Edge.
  2. Navigate to the test page.
  3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="alertdialog"]
    - If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
  4. Position and configure the screen reader so that the following conditions are met
    - Virtual focus is: before target
    - Keyboard focus is: before target
    - Mode is: auto (do not explicitly change the mode)
  5. Issue the command: Down arrow (Read next item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: target

JAWS Firefox yes

Result: (pass)
- Test Case: Use Down arrow (Read next item) to navigate forward to `*[role="alertdialog"]`
  1. Launch JAWS and Firefox.
  2. Navigate to the test page.
  3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="alertdialog"]
    - If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
  4. Position and configure the screen reader so that the following conditions are met
    - Virtual focus is: before target
    - Keyboard focus is: before target
    - Mode is: auto (do not explicitly change the mode)
  5. Issue the command: Down arrow (Read next item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: target

Narrator Edge yes

Result: (pass)
- Test Case: Use Down arrow (Jump to next item (scan mode)) to navigate forward to `*[role="alertdialog"]`
  1. Launch Narrator and Edge.
  2. Navigate to the test page.
  3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="alertdialog"]
    - If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
  4. Position and configure the screen reader so that the following conditions are met
    - Virtual focus is: before target
    - Keyboard focus is: before target
    - Mode is: auto (do not explicitly change the mode)
  5. Issue the command: Down arrow (Jump to next item (scan mode))
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: target

NVDA Chrome yes

Result: (pass)
- Test Case: Use down arrow (Read next item) to navigate forward to `*[role="alertdialog"]`
  1. Launch NVDA and Chrome.
  2. Navigate to the test page.
  3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="alertdialog"]
    - If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
  4. Position and configure the screen reader so that the following conditions are met
    - Virtual focus is: before target
    - Keyboard focus is: before target
    - Mode is: auto (do not explicitly change the mode)
  5. Issue the command: down arrow (Read next item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: target

NVDA Edge yes

Result: (pass)
- Test Case: Use down arrow (Read next item) to navigate forward to `*[role="alertdialog"]`
  1. Launch NVDA and Edge.
  2. Navigate to the test page.
  3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="alertdialog"]
    - If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
  4. Position and configure the screen reader so that the following conditions are met
    - Virtual focus is: before target
    - Keyboard focus is: before target
    - Mode is: auto (do not explicitly change the mode)
  5. Issue the command: down arrow (Read next item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: target

NVDA Firefox yes

Result: (pass)
- Test Case: Use down arrow (Read next item) to navigate forward to `*[role="alertdialog"]`
  1. Launch NVDA and Firefox.
  2. Navigate to the test page.
  3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="alertdialog"]
    - If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
  4. Position and configure the screen reader so that the following conditions are met
    - Virtual focus is: before target
    - Keyboard focus is: before target
    - Mode is: auto (do not explicitly change the mode)
  5. Issue the command: down arrow (Read next item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: target

Notes: An element in the dialog had to receive focus before the contents of the dialog would be read by NVDA. Orca Firefox yes

Result: (pass)
- Test Case: Use down arrow (Read next item) to navigate forward to `*[role="alertdialog"]`
  1. Launch Orca and Firefox.
  2. Navigate to the test page.
  3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="alertdialog"]
    - If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
  4. Position and configure the screen reader so that the following conditions are met
    - Virtual focus is: before target
    - Keyboard focus is: before target
    - Mode is: auto (do not explicitly change the mode)
  5. Issue the command: down arrow (Read next item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: "target"

TalkBack Chrome yes

Result: (pass)
- Test Case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `*[role="alertdialog"]`
  1. Launch TalkBack and Chrome.
  2. Navigate to the test page.
  3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="alertdialog"]
    - If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
  4. Position and configure the screen reader so that the following conditions are met
    - Virtual focus is: before target
    - Keyboard focus is: before target
    - Mode is: auto (do not explicitly change the mode)
  5. Issue the command: Swipe right (or alt+right arrow) (Read next item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: target

Voice Access (Android) Chrome not applicable - Voice Control (iOS) Safari not applicable - Voice Control (MacOS) Safari not applicable - VoiceOver (iOS) Safari yes

Result: (pass)
- Test Case: Use Swipe Right (Next item) to navigate forward to `*[role="alertdialog"]`
  1. Launch VoiceOver (iOS) and Safari.
  2. Navigate to the test page.
  3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="alertdialog"]
    - If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
  4. Position and configure the screen reader so that the following conditions are met
    - Virtual focus is: before target
    - Keyboard focus is: before target
    - Mode is: auto (do not explicitly change the mode)
  5. Issue the command: Swipe Right (Next item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: target

VoiceOver (macOS) Safari yes

Result: (pass)
- Test Case: Use VO + Right arrow (Read next item) to navigate forward to `*[role="alertdialog"]`
  1. Launch VoiceOver (macOS) and Safari.
  2. Navigate to the test page.
  3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="alertdialog"]
    - If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
  4. Position and configure the screen reader so that the following conditions are met
    - Virtual focus is: before target
    - Keyboard focus is: before target
    - Mode is: auto (do not explicitly change the mode)
  5. Issue the command: VO + Right arrow (Read next item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: target

Windows Speech Recognition Edge not applicable - Windows Speech Recognition Chrome not applicable - Windows Voice Access Edge not applicable - Windows Voice Access Chrome not applicable - Windows Keyboard Chrome not applicable - Windows Keyboard Firefox not applicable - Windows Keyboard Edge not applicable - Mac Keyboard Chrome not applicable - Mac Keyboard Safari not applicable - iOS Keyboard Safari not applicable - Android Keyboard Chrome not applicable - Extended Support for: alertdialog role: NOT automatically switch away from reading mode

These are less common combinations

AT Browser Has Support Output Dragon Naturally Speaking IE not applicable - Dragon Naturally Speaking Firefox not applicable - JAWS 2018.1811.2 IE 11.253 yes

Result: (pass)
- Test Case: Use Down arrow (Read next item) to navigate forward to `*[role="alertdialog"]`
  1. Launch JAWS and IE.
  2. Navigate to the test page.
  3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="alertdialog"]
    - If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
  4. Position and configure the screen reader so that the following conditions are met
    - Virtual focus is: before target
    - Keyboard focus is: before target
    - Mode is: auto (do not explicitly change the mode)
  5. Issue the command: Down arrow (Read next item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: target

Narrator Firefox unknown - Narrator Chrome unknown - Narrator IE unknown - NVDA IE unknown - TalkBack Firefox unknown - Voice Access (Android) Firefox not applicable - VoiceOver (iOS) Chrome unknown - VoiceOver (macOS) Chrome unknown - VoiceOver (macOS) Firefox unknown - Orca Chrome unknown - Voice Control (MacOS) Chrome not applicable - Voice Control (MacOS) Firefox not applicable - Mac Keyboard Firefox not applicable - Android Keyboard Firefox not applicable - Back to top Dates and Versions of tested combinations AT AT Version Browser Browser version OS version Date tested JAWS 2021.2107.12 Chrome 92 Windows 10 version 21h1 2021-08-07 JAWS 2021.2107.12 Edge 92 Windows 10 version 21h1 2021-08-07 JAWS 2018.1811.2 Firefox 66 Windows 10 version 1809 2019-05-19 Narrator Windows 10 version 1809 Edge 44.17763 Windows 10 version 1809 2018-01-18 NVDA 2024.4 Chrome 129 Windows 11 version 23h2 2024-12-06 NVDA 2021.1 Edge 92 Windows 10 version 21h1 2021-08-07 NVDA 2018.4.1 Firefox 64.0.2 Windows 10 version 1809 2019-01-19 Orca 3.31.4 Firefox 69 Ubuntu 19.04 2019-09-13 TalkBack 7.2 Chrome 67 8.1 2018-07-21 VoiceOver (iOS) 12.1.2 Safari 12.1.2 12.1.2 2018-01-18 VoiceOver (macOS) 10.14.2 Safari 12.0.2 10.14.2 2018-10-26 History

2019-01-18 Test created
2019-09-13 Orca results and missing information added
2021-08-07 Added Narrator results for NVDA and JAWS, updated NVDA+Chrome results.
2024-12-08 Updated results for NVDA+Chrome. No changes. Thanks @SimoAccessiWay!

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4