RetroSearch Browse

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

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

Test: CSS generated content for button name

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

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

AT Browser Has Support Output Dragon Naturally Speaking Chrome none

Result: (fail)
- 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:#target
    - 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: command was not recognized
- Command Notes: said "click submit order"
- 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 Chrome none

Result: (fail)
- Test Case: Use Tab (Read next focusable item) to navigate forward to `#target`
  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:#target
    - 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: "unlabeled 3 button"
- 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 Tab (Read next focusable item) to navigate forward to `#target`
  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:#target
    - 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: "unlabeled 3 button"
- 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 yes

Result: (pass)
- Test Case: Use Tab (Read next focusable item) to navigate forward to `#target`
  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:#target
    - 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: "submit order button"

Narrator Edge none

Result: (fail)
- Test Case: Use Tab (Read next focusable item) to navigate forward to `#target`
  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:#target
    - 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: "button"
- 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 Tab (Read next focusable item) to navigate forward to `#target`
  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:#target
    - 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: "submit order button"

NVDA Edge yes

Result: (pass)
- Test Case: Use Tab (Read next focusable item) to navigate forward to `#target`
  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:#target
    - 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: "submit order button"

NVDA Firefox yes

Result: (pass)
- Test Case: Use Tab (Read next focusable item) to navigate forward to `#target`
  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:#target
    - 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: "submit order, button"

Orca Firefox yes

Result: (pass)
- Test Case: Use Tab (Read next focusable item) to navigate forward to `#target`
  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:#target
    - 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: "submit order, push button"

TalkBack Chrome yes

Result: (pass)
- Test Case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `#target`
  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:#target
    - 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: "submit order, button"

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:#target
    - 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: button was activated
- Command Notes: said "tap submit order".

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:#target
    - 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: button was activated
- Command Notes: said "tap submit order"

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:#target
    - 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: button was activated
- Command Notes: said "click submit order"

VoiceOver (iOS) Safari yes

Result: (pass)
- Test Case: Use Swipe Right (Next item) to navigate forward to `#target`
  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:#target
    - 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: "submit order, button"

VoiceOver (macOS) Safari yes

Result: (pass)
- Test Case: Use Tab (Read next focusable item) to navigate forward to `#target`
  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:#target
    - 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: "submit order, button"

Windows Speech Recognition Edge unknown - Windows Speech Recognition Chrome none

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:#target
    - 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: button was not recognized
- Command Notes: said "click submit order"
- 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__css__css_generated_content_button below:

Test: CSS generated content for button name

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