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

Showing content from https://a11ysupport.io/tests/tech__aria__aria-errormessage-with-aria-invalid-true below:

Test: aria-errormessage attribute with aria-invalid="true"

This expectation is applied to the input[type="text"] element. Expectations and results might differ when the the feature is applied to different roles.

Users need to know that the error message exists when the input is in an aria-invalid="true" state

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

• Result: (pass)
  • Test Case: Use Down arrow (Read next item) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: "Input with aria-invalid="true" Edit Has Error invalid entry"
• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: "Input with aria-invalid="true", edit, invalid entry, has error, example error text, type in text"

• Result: (pass)
  • Test Case: Use Down arrow (Read next item) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: "blank, Input with aria-invalid="true" Edit Has Error invalid entry"
• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: Input with aria-invalid="true" Edit invalid entry Has Error example error text Type in text.

• Result: (fail)
  • Test Case: Use Down arrow (Read next item) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: "Input with aria-invalid="true" Edit invalid entry"
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.
• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: "Input with aria-invalid="true" Edit invalid entry"
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use Down arrow (Jump to next item (scan mode)) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: "Input with aria-invalid="true", edit, invalid, scan off"
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.
• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: "Input with aria-invalid="true", edit, invalid"
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use down arrow (Read next item) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: "Input with aria-invalid="true" edit invalid entry"
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.
• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: "Input with aria-invalid="true", edit, invalid entry, blank"
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use down arrow (Read next item) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: "Input with aria-invalid="true", edit, invalid entry"
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.
• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: "Input with aria-invalid="true", edit, invalid entry, blank"
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use down arrow (Read next item) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: "Input with aria-invalid="true", edit, invalid entry has auto complete"
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.
• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: "Input with aria-invalid="true", edit, invalid entry has auto complete, blank"
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (pass)
  • Test Case: Use down arrow (Read next item) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: "Input with aria-invalid="true", entry, invalid entry, example error text"
• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: "Input with aria-invalid="true", entry, invalid entry, example error texte"

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

• Result: (pass)
  • Test Case: Use Swipe Right (Next item) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: "Input with aria-invalid="true", text field, invalid date, example error text, double tap to edit"

• Result: (fail)
  • Test Case: Use VO + Right arrow (Read next item) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: "Input with aria-invalid="true", invalid data, edit text"
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.
• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `*[aria-errormessage][aria-invalid=true]`
    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-errormessage][aria-invalid=true]
       • 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: "Input with aria-invalid="true", invalid data, edit text"
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

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