RetroSearch Browse

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

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

Test: HTML links example 5 - A link that wraps many elements

A screen reader user needs to know what to enter.

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

AT Browser Has Support Output Dragon Naturally Speaking Chrome yes

Result: (pass)
- Test Case: Use "Click <text>" (Activate item by name)
  1. Launch Dragon Naturally Speaking 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:a[href]
    - 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. Issue the command: "Click <text>" (Activate item by name)
  5. Record results for the relevant expectations
- Output: successfully activated

JAWS Chrome yes

Result: (pass)
- Test Case: Use Down arrow (Read next item) to navigate forward to `a[href]`
  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:a[href]
    - 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: "Heading level 3, link, tablet 9000!" (each down arrow press announces a line of text within the link along with the the link role)
Result: (pass)
- Test Case: Use Tab (Read next focusable item) to navigate forward to `a[href]`
  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:a[href]
    - 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: Tab (Read next focusable item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: "<all text in link>, heading level 3, link"

JAWS Edge yes

Result: (pass)
- Test Case: Use Down arrow (Read next item) to navigate forward to `a[href]`
  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:a[href]
    - 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: "Heading level 3, link, tablet 9000!" (each down arrow press announces a line of text within the link along with the the link role)
Result: (pass)
- Test Case: Use Tab (Read next focusable item) to navigate forward to `a[href]`
  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:a[href]
    - 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: Tab (Read next focusable item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: "<all text in link>, heading level 3, link"

JAWS Firefox yes

Result: (pass)
- Test Case: Use Down arrow (Read next item) to navigate forward to `a[href]`
  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:a[href]
    - 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: "Heading level 3, link, tablet 9000!" (each down arrow press announces a line of text within the link along with the the link role)
Result: (pass)
- Test Case: Use Tab (Read next focusable item) to navigate forward to `a[href]`
  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:a[href]
    - 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: Tab (Read next focusable item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: "<all text in link>, heading level 3, link"

Narrator Edge yes

Result: (pass)
- Test Case: Use Down arrow (Jump to next item (scan mode)) to navigate forward to `a[href]`
  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:a[href]
    - 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: "Link, tablet 9000!"
Result: (pass)
- Test Case: Use Tab (Read next focusable item) to navigate forward to `a[href]`
  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:a[href]
    - 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: Tab (Read next focusable item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: Link, tablet 9000! Turn all your widgets into mellbloms! Only $9.99 plus shipping and handling." (embedded semantics were not conveyed)

NVDA Chrome yes

Result: (pass)
- Test Case: Use down arrow (Read next item) to navigate forward to `a[href]`
  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:a[href]
    - 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: "link, Heading level 3, tablet 9000!" (each down arrow press announces a line of text within the link along with the the link role)
Result: (pass)
- Test Case: Use Tab (Read next focusable item) to navigate forward to `a[href]`
  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:a[href]
    - 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: Tab (Read next focusable item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: "tablet 9000! heading level 3, <rest of text>, link"

NVDA Edge yes

Result: (pass)
- Test Case: Use down arrow (Read next item) to navigate forward to `a[href]`
  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:a[href]
    - 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: "link, Heading level 3, tablet 9000!" (each down arrow press announces a line of text within the link along with the the link role)
Result: (pass)
- Test Case: Use Tab (Read next focusable item) to navigate forward to `a[href]`
  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:a[href]
    - 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: Tab (Read next focusable item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: "tablet 9000! heading level 3, <rest of text>, link"

NVDA Firefox yes

Result: (pass)
- Test Case: Use down arrow (Read next item) to navigate forward to `a[href]`
  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:a[href]
    - 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: "link, Heading level 3, tablet 9000!" (each down arrow press announces a line of text within the link along with the the link role)
Result: (pass)
- Test Case: Use Tab (Read next focusable item) to navigate forward to `a[href]`
  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:a[href]
    - 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: Tab (Read next focusable item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: "tablet 9000! heading level 3, <rest of text>, link"

Orca Firefox yes

Result: (pass)
- Test Case: Use down arrow (Read next item) to navigate forward to `a[href]`
  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:a[href]
    - 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: "tablet 9000!, heading level 3, link"
- Result Notes: each line is announced as a link
Result: (pass)
- Test Case: Use Tab (Read next focusable item) to navigate forward to `a[href]`
  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:a[href]
    - 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: Tab (Read next focusable item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: "tablet 9000! Turn all your widgets into mellbloms! Only $9.99 plus shipping and handling. link, tablet 9000!, heading level 3, link"

TalkBack Chrome yes

Result: (pass)
- Test Case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `a[href]`
  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:a[href]
    - 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: "tablet 9000! Turn all your widgets into mellbloms! Only $9.99 plus shipping and handling, link"

Notes: The entire content is announced as a link, and it is not possible to navigate content within the link. No semantics inside the link are conveyed. Voice Access (Android) Chrome yes

Result: (pass)
- Test Case: Use "Tap <text>" or just "<text>" (Activate item by name)
  1. Launch Voice Access (Android) 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:a[href]
    - 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. Issue the command: "Tap <text>" or just "<text>" (Activate item by name)
  5. Record results for the relevant expectations
- Output: link was activated
- Command Notes: said "tap tablet 9000"

Voice Control (iOS) Safari yes

Result: (pass)
- Test Case: Use "Tap <text>" (Activate item by name)
  1. Launch Voice Control (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:a[href]
    - 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. Issue the command: "Tap <text>" (Activate item by name)
  5. Record results for the relevant expectations
- Output: link was flagged for disambiguation
- Command Notes: said "tap tablet 9000"

Voice Control (MacOS) Safari yes

Result: (pass)
- Test Case: Use "Click <text>" (Activate item by name)
  1. Launch Voice Control (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:a[href]
    - 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. Issue the command: "Click <text>" (Activate item by name)
  5. Record results for the relevant expectations
- Output: link was clicked
- Command Notes: said "click tablet 9000"

VoiceOver (iOS) Safari yes

Result: (pass)
- Test Case: Use Swipe Right (Next item) to navigate forward to `a[href]`
  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:a[href]
    - 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: Each line is conveyed as its own link

VoiceOver (macOS) Safari yes

Result: (pass)
- Test Case: Use VO + Right arrow (Read next item) to navigate forward to `a[href]`
  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:a[href]
    - 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: "link, tablet 9000! Turn all your widgets into mellbloms! Only $9.99 plus shipping and handling."
Result: (pass)
- Test Case: Use Tab (Read next focusable item) to navigate forward to `a[href]`
  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:a[href]
    - 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: Tab (Read next focusable item)
    - After issuing the command, virtual focus should be: target
  6. Record results for the relevant expectations
- Output: "link, tablet 9000! Turn all your widgets into mellbloms! Only $9.99 plus shipping and handling."

Notes: The entire contents of the link are announced when navigating to the link. Users can navigate into the link contain and navigate object by object. Windows Speech Recognition Edge none

Result: (fail)
- Test Case: Use "Click <text>" (Activate item by name)
  1. Launch Windows Speech Recognition 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:a[href]
    - 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. Issue the command: "Click <text>" (Activate item by name)
  5. Record results for the relevant expectations
- Output: role was not activated
- Command Notes: said "click tablet 9000"
- Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

Result: (fail)
- Test Case: Use "Click <text>" (Activate item by name)
  1. Launch Windows Speech Recognition 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:a[href]
    - 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. Issue the command: "Click <text>" (Activate item by name)
  5. Record results for the relevant expectations
- Output: role was not activated
- Command Notes: said "click tablet 9000"
- 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 Voice Access Edge unknown - Windows Voice Access Chrome unknown - 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 -

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__html__links__example5 below:

Test: HTML links example 5 - A link that wraps many elements

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