RetroSearch Browse

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

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

Test: HTML inert attribute test

The inert attribute will prevent all click events for mouse users and hide content from assistive technologies, so all functionality should be removed for assistive technologies. This includes removing the inert content from the tab order, and preventing any interactions with inert content.

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:[inert] button
    - 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: unknown
- Command Notes: said "click inert button"
Result: (pass)
- Test Case: Use Click <role> (Click Type)
  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:[inert] button
    - 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 <role> (Click Type)
  5. Record results for the relevant expectations
- Output: all inert content was skipped

JAWS Chrome yes

Result: (pass)
- Test Case: unknown
  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:[inert] *
    - 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: after target
  6. Record results for the relevant expectations
- Output: "tab stop after button"
- Command Notes: all inert content was skipped

JAWS Edge yes

Result: (pass)
- Test Case: unknown
  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:[inert] *
    - 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: after target
  6. Record results for the relevant expectations
- Output: "tab stop after button"
- Command Notes: all inert content was skipped

JAWS Firefox yes

Result: (pass)
- Test Case: unknown
  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:[inert] *
    - 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: after target
  6. Record results for the relevant expectations
- Output: "tab stop after button"
- Command Notes: all inert content was skipped

Narrator Edge yes

Result: (pass)
- Test Case: unknown
  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:[inert] *
    - 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: after target
  6. Record results for the relevant expectations
- Output: "tab stop after, button"
- Command Notes: all inert content was skipped

NVDA Chrome yes

Result: (pass)
- Test Case: unknown
  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:[inert] *
    - 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: after target
  6. Record results for the relevant expectations
- Output: "tab stop after button"
- Command Notes: all inert content was skipped

NVDA Edge yes

Result: (pass)
- Test Case: unknown
  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:[inert] *
    - 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: after target
  6. Record results for the relevant expectations
- Output: "tab stop after button"
- Command Notes: all inert content was skipped

NVDA Firefox yes

Result: (pass)
- Test Case: unknown
  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:[inert] *
    - 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: after target
  6. Record results for the relevant expectations
- Output: "tab stop after button"
- Command Notes: all inert content was skipped

Orca Firefox yes

Result: (pass)
- Test Case: unknown
  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:[inert] *
    - 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: after target
  6. Record results for the relevant expectations
- Output: "tab stop after, push button"
- Command Notes: inert content was skipped

TalkBack Chrome yes

Result: (pass)
- Test Case: unknown
  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:[inert] *
    - 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 (Move to next focusable item)
    - After issuing the command, virtual focus should be: after target
  6. Record results for the relevant expectations
- Output: "tab stop after, button"
- Command Notes: all inert content was skipped

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:[inert] button
    - 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: command was not recognized
- Command Notes: Said "tap inert button".
Result: (pass)
- Test Case: Use "Show numbers" (Turn on the numbers overlay)
  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:[inert] button
    - 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: "Show numbers" (Turn on the numbers overlay)
  5. Record results for the relevant expectations
- Output: inert content was not numbered

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:[inert] button
    - 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: command was not recognized
- Command Notes: said "tap inert button"
Result: (pass)
- Test Case: Use "Show names" (Turn on the names overlay)
  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:[inert] button
    - 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: "Show names" (Turn on the names overlay)
  5. Record results for the relevant expectations
- Output: inert content was skipped
Result: (pass)
- Test Case: Use "Show numbers" (Turn on the numbers overlay)
  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:[inert] button
    - 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: "Show numbers" (Turn on the numbers overlay)
  5. Record results for the relevant expectations
- Output: inert content was skipped

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:[inert] button
    - 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 inert button"
Result: (pass)
- Test Case: Use "Show numbers" (Turn on the numbers overlay)
  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:[inert] button
    - 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: "Show numbers" (Turn on the numbers overlay)
  5. Record results for the relevant expectations
- Output: all inert content was skipped

VoiceOver (iOS) Safari yes

Result: (pass)
- Test Case: unknown
  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:[inert] *
    - 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 (Move to next focusable item)
    - After issuing the command, virtual focus should be: after target
  6. Record results for the relevant expectations
- Output: "tab stop after, button"
- Command Notes: all inert content was skipped

VoiceOver (macOS) Safari yes

Result: (pass)
- Test Case: unknown
  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:[inert] *
    - 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: after target
  6. Record results for the relevant expectations
- Output: "tab stop after, button"
- Command Notes: all inert content was skipped

Windows Speech Recognition Edge yes

Result: (pass)
- 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:[inert] button
    - 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 "tap inert button".
Result: (pass)
- Test Case: Use "Show numbers" (Turn on the numbers overlay)
  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:[inert] button
    - 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: "Show numbers" (Turn on the numbers overlay)
  5. Record results for the relevant expectations
- Output: all inert content was skipped

Windows Speech Recognition Chrome yes

Result: (pass)
- 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:[inert] button
    - 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 "tap inert button".
Result: (pass)
- Test Case: Use "Show numbers" (Turn on the numbers overlay)
  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:[inert] button
    - 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: "Show numbers" (Turn on the numbers overlay)
  5. Record results for the relevant expectations
- Output: all inert content was skipped

Windows Voice Access Edge yes

Result: (pass)
- Test Case: Use "Click <text>" (Activate item by name)
  1. Launch Windows Voice Access 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:[inert] button
    - 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 "tap inert button".
Result: (pass)
- Test Case: Use "Show numbers" (Turn on the numbers overlay)
  1. Launch Windows Voice Access 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:[inert] button
    - 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: "Show numbers" (Turn on the numbers overlay)
  5. Record results for the relevant expectations
- Output: inert content was not numbered

Windows Voice Access Chrome yes

Result: (pass)
- Test Case: Use "Click <text>" (Activate item by name)
  1. Launch Windows Voice Access 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:[inert] button
    - 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 "tap inert button".
Result: (pass)
- Test Case: Use "Show numbers" (Turn on the numbers overlay)
  1. Launch Windows Voice Access 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:[inert] button
    - 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: "Show numbers" (Turn on the numbers overlay)
  5. Record results for the relevant expectations
- Output: inert content was not numbered

Windows Keyboard Chrome yes

Result: (pass)
- Test Case: Use Tab (Navigate to the next focusable item)
  1. Launch Windows Keyboard 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:[inert] button
    - 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: Tab (Navigate to the next focusable item)
  5. Record results for the relevant expectations
- Output: inert contents were skipped

Windows Keyboard Firefox yes

Result: (pass)
- Test Case: Use Tab (Navigate to the next focusable item)
  1. Launch Windows Keyboard 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:[inert] button
    - 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: Tab (Navigate to the next focusable item)
  5. Record results for the relevant expectations
- Output: inert contents were skipped

Windows Keyboard Edge yes

Result: (pass)
- Test Case: Use Tab (Navigate to the next focusable item)
  1. Launch Windows Keyboard 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:[inert] button
    - 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: Tab (Navigate to the next focusable item)
  5. Record results for the relevant expectations
- Output: inert contents were skipped

Mac Keyboard Chrome yes

Result: (pass)
- Test Case: Use Tab (Navigate to the next focusable item)
  1. Launch Mac Keyboard 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:[inert] button
    - 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: Tab (Navigate to the next focusable item)
  5. Record results for the relevant expectations
- Output: inert contents were skipped

Mac Keyboard Safari yes

Result: (pass)
- Test Case: Use Tab (Navigate to the next focusable item)
  1. Launch Mac Keyboard 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:[inert] button
    - 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: Tab (Navigate to the next focusable item)
  5. Record results for the relevant expectations
- Output: inert contents were skipped

iOS Keyboard Safari yes

Result: (pass)
- Test Case: Use Tab (Navigate to the next focusable item)
  1. Launch iOS Keyboard 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:[inert] button
    - 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: Tab (Navigate to the next focusable item)
  5. Record results for the relevant expectations
- Output: inert contents were skipped

Android Keyboard Chrome yes

Result: (pass)
- Test Case: Use Tab (Navigate to the next focusable item)
  1. Launch Android Keyboard 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:[inert] button
    - 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: Tab (Navigate to the next focusable item)
  5. Record results for the relevant expectations
- Output: inert contents were skipped

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

Test: HTML inert attribute test

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