RetroSearch Browse

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

Showing content from https://a11ysupport.io/tests/techariaaria-details below:

Test: aria-details test | Accessibility Support

Test: aria-details test

Screen Reader support level: partial (7/11)

Voice Control support level: unknown

On this page

About this test

A sample of aria-details functionality

Submit new test results Age of results

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

Caution

Failing or partial results may be out of date. The oldest result is from 3 years ago. Consider running this test and contributing results.

Test HTMLOpen the test case HTML file

<!DOCTYPE html>
<html lang="en">
<head>
    <title>aria-details examples</title>
</head>
<body>
<h1>aria-details examples</h1>

<img src="pythagorean.jpg" alt="Cats" aria-details="details">

<p>Some unrelated text</p>

<p id="details">Cats have 4 legs, one tail, and are <a href="https://en.wikipedia.org/wiki/Cat">full of awesome</a>.</p>

<p>Further text</p>

</body>
</html>

Summary of Screen Reader support by expectation

* means that some support is hidden behind settings

Summary of Voice Control support by expectation aria-details attribute 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 aria-details attribute 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 aria-details attribute: convey the boundaries of the details - applied to the img element

This expectation is applied to the img element. Expectations and results might differ when the the feature is applied to different roles.

This expectation is from the aria-details attribute feature.

Rationale:

A screen reader user may find it helpful to know exactly where the details start and end.

Strength of this expectation for different types of assistive technologies:

Screen Readers: MAY
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 `#details`
  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:#details
    - 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: "Entering details"
Result: (pass)
- Test Case: Use Down arrow (Read next item) to navigate forward to `#details`
  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:#details
    - 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: "Entering details"

JAWS Edge yes

Result: (pass)
- Test Case: Use Down arrow (Read next item) to navigate forward to `#details`
  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:#details
    - 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: "Entering details"
Result: (pass)
- Test Case: Use Down arrow (Read next item) to navigate forward to `#details`
  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:#details
    - 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: "Entering details"

JAWS Firefox yes

Result: (pass)
- Test Case: Use Down arrow (Read next item) to navigate forward to `#details`
  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:#details
    - 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: "Entering details"
Result: (pass)
- Test Case: Use Down arrow (Read next item) to navigate forward to `#details`
  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:#details
    - 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: "Entering details"

Narrator Edge none

Result: (fail)
- Test Case: Use Down arrow (Jump to next item (scan mode)) to navigate forward to `#details`
  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:#details
    - 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: (does not convey boundaries)
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue. NVDA Chrome none

Result: (fail)
- Test Case: Use down arrow (Read next item) to navigate forward to `#details`
  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:#details
    - 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: "Cats have 4 legs, one tail, and are link full of awesome."
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue. NVDA Edge none

Result: (fail)
- Test Case: Use down arrow (Read next item) to navigate forward to `#details`
  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:#details
    - 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: "Cats have 4 legs, one tail, and are link full of awesome."
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue. NVDA Firefox none

Result: (fail)
- Test Case: Use down arrow (Read next item) to navigate forward to `#details`
  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:#details
    - 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: "Cats have 4 legs, one tail, and are link full of awesome."
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue. Orca Firefox yes

Result: (pass)
- Test Case: Use down arrow (Read next item) to navigate forward to `#details`
  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:#details
    - 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: "Cats have 4 legs, one tail, and are, details for cats, full of awesome, link."
- Command Notes: The text "details for cats" was inserted mid sentence. This could potentially negatively affect meaning.

TalkBack Chrome none

Result: (fail)
- Test Case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `#details`
  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:#details
    - 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: "Cats have 4 legs, one tail, and are full of awesome." (i.e. TalkBack read the text content itself)
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue. Voice Access (Android) Chrome not applicable - Voice Control (iOS) Safari not applicable - Voice Control (MacOS) Safari not applicable - VoiceOver (iOS) Safari none

Result: (fail)
- Test Case: Use Swipe Right (Next item) to navigate forward to `#details`
  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:#details
    - 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: "Cats have 4 legs, one tail, and are full of awesome."
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Result: (fail)
- Test Case: Use VO + Right arrow (Read next item) to navigate forward to `#details`
  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:#details
    - 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: "Cats have 4 legs, one tail, and are full of awesome., details for Cats"
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue. 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: aria-details attribute: convey the boundaries of the details

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.134 yes

Result: (pass)
- Test Case: Use Down arrow (Read next item) to navigate forward to `#details`
  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:#details
    - 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: "Entering details"
Result: (pass)
- Test Case: Use Down arrow (Read next item) to navigate forward to `#details`
  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:#details
    - 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: "Entering details"

This expectation is applied to the img element. Expectations and results might differ when the the feature is applied to different roles.

This expectation is from the aria-details attribute 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 `*[aria-details]`
  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:*[aria-details]
    - 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: "Cats, graphic, has details."

JAWS Edge yes

Result: (pass)
- Test Case: Use Down arrow (Read next item) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: "Cats, graphic, has details."

JAWS Firefox yes

Result: (pass)
- Test Case: Use Down arrow (Read next item) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: "Cats, has details."

Narrator Edge none

Result: (fail)
- Test Case: Use Down arrow (Jump to next item (scan mode)) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: "Cats, graphic"
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue. NVDA Chrome yes

Result: (pass)
- Test Case: Use down arrow (Read next item) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: "Graphic, has details, Cats"

NVDA Edge yes

Result: (pass)
- Test Case: Use down arrow (Read next item) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: "Graphic, has details, Cats"

NVDA Firefox yes

Result: (pass)
- Test Case: Use down arrow (Read next item) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: "Graphic, has details, Cats"

Orca Firefox yes

Result: (pass)
- Test Case: Use down arrow (Read next item) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: "Cats, has details in paragraph"

TalkBack Chrome none

Result: (fail)
- Test Case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: "Cats, graphic"
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue. Voice Access (Android) Chrome not applicable - Voice Control (iOS) Safari not applicable - Voice Control (MacOS) Safari not applicable - VoiceOver (iOS) Safari none

Result: (fail)
- Test Case: Use Swipe Right (Next item) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: "Cats, image"
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Result: (fail)
- Test Case: Use VO + Right arrow (Read next item) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: "Cats, image, has details in paragraph"
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue. 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: aria-details attribute: convey the presence of aria-details

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.134 yes

Result: (pass)
- Test Case: Use Down arrow (Read next item) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: "Graphic, unavailable, Cats, has details."

This expectation is applied to the img element. Expectations and results might differ when the the feature is applied to different roles.

This expectation is from the aria-details attribute feature.

Rationale:

If the details are not adjacent to the element with aria-details, it might be helpful to jump directly to the reference or have it conveyed.

Strength of this expectation for different types of assistive technologies:

Screen Readers: SHOULD
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 none

Result: (fail)
- Test Case: Use equals sign (Follow the element referenced by aria-flowto) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: equals sign (Follow the element referenced by aria-flowto)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: "no more flows found" (does not let user navigate to the referenced element)
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue. JAWS Edge none

Result: (fail)
- Test Case: Use equals sign (Follow the element referenced by aria-flowto) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: equals sign (Follow the element referenced by aria-flowto)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: "no more flows found" (does not let user navigate to the referenced element)
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue. JAWS Firefox none

Result: (fail)
- Test Case: Use equals sign (Follow the element referenced by aria-flowto) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: equals sign (Follow the element referenced by aria-flowto)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: (does not let user navigate to the referenced element)
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue. Narrator Edge none

Result: (fail)
- Test Case: Use Down arrow (Jump to next item (scan mode)) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: "Cats, graphic"
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue. NVDA Chrome yes

Result: (pass)
- Test Case: Use NVDA + d (Read details) on the target of `*[aria-details]`
  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:*[aria-details]
    - 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: target
    - Keyboard focus is: target
    - Mode is: auto (do not explicitly change the mode)
  5. Issue the command: NVDA + d (Read details)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: "Cats have 4 legs, one tail, and are full of awesome."

NVDA Edge yes

Result: (pass)
- Test Case: Use NVDA + d (Read details) on the target of `*[aria-details]`
  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:*[aria-details]
    - 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: target
    - Keyboard focus is: target
    - Mode is: auto (do not explicitly change the mode)
  5. Issue the command: NVDA + d (Read details)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: "Cats have 4 legs, one tail, and are full of awesome."

NVDA Firefox yes

Result: (pass)
- Test Case: Use NVDA + d (Read details) on the target of `*[aria-details]`
  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:*[aria-details]
    - 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: target
    - Keyboard focus is: target
    - Mode is: auto (do not explicitly change the mode)
  5. Issue the command: NVDA + d (Read details)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: "Cats have 4 legs, one tail, and are full of awesome."

Orca Firefox yes

Result: (pass)
- Test Case: Use key pad enter (Where Am I) on the target of `*[aria-details]`
  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:*[aria-details]
    - 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: target
    - Keyboard focus is: target
    - Mode is: auto (do not explicitly change the mode)
  5. Issue the command: key pad enter (Where Am I)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: "Cats, paragraph, Cats have 4 legs, one tail, and are full of awesome."

TalkBack Chrome none

Result: (fail)
- Test Case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: "Cats, graphic"
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue. Voice Access (Android) Chrome not applicable - Voice Control (iOS) Safari not applicable - Voice Control (MacOS) Safari not applicable - VoiceOver (iOS) Safari none

Result: (fail)
- Test Case: Use Swipe Right (Next item) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: "Cats, image"
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Result: (fail)
- Test Case: Use VO + Right arrow (Read next item) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: "Cats, image, has details in paragraph"
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Grading Note: There is no known/documented support. There may still be support for this expectation, but it is undocumented. If this is the case, please report this issue. 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: aria-details attribute: convey the referenced content (jump or convey)

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.134 none

Result: (fail)
- Test Case: Use Down arrow (Read next item) to navigate forward to `*[aria-details]`
  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:*[aria-details]
    - 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: "Graphic, unavailable, Cats, has details."

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 105 Windows 11 version 21H2 2022-09-16 JAWS 2021.2107.12 Edge 105 Windows 11 version 21H2 2022-09-16 JAWS 2022.2207.25 Firefox 104 Windows 11 version 21H2 2022-09-16 Narrator Windows 11 version 21H2 Edge 105 Windows 11 version 21H2 2022-09-16 NVDA 2022.2.2 Chrome 105 Windows 11 version 21H2 2022-09-16 NVDA 2022.2.2 Edge 105 Windows 11 version 21H2 2022-09-16 NVDA 2022.2.2 Firefox 104 Windows 11 version 21H2 2022-09-16 Orca 42.0 Firefox 104 Ubuntu 22.04 2022-09-16 TalkBack 12.5 Chrome 105 12 2022-09-16 VoiceOver (iOS) 16.0 Safari 16.0 16.0 2022-09-16 VoiceOver (macOS) 12.6 Safari 16.0 12.6 2022-09-16 History

2019-05-19 Test created
2019-09-16 Added orca results
2021-07-23 Added Narrator results for NVDA and JAWS, updated NVDA+Chrome results.
2022-09-16 Update all results, NVDA and Orca now have more robust results.

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

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

Showing content from https://a11ysupport.io/tests/tech__aria__aria-details below:

Test: aria-details test | Accessibility Support

Showing content from https://a11ysupport.io/tests/techariaaria-details below: