Test cases for Dragon Naturally Speaking + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Dragon Naturally Speaking + IE The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Dragon Naturally Speaking + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for JAWS + Chrome Test case: open the dialog using Activate Button (Enter or Space) Launch JAWS and Chrome. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandUsing the command: "Enter or Space" (Activate Button) Observe: dialog will open and focus will be moved to the target Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes dialog role, MUST convey the name of the dialog Resultunknown pass fail partial
Notes aria-modal attribute, MUST convey the presence of aria-modal=true, applied to dialog role Examples:
Screen readers might convey the modal state when entering the modal Screen readers might imply the modal state by restricting reading and navigation to the modal content Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Read previous item (Up arrow) Launch JAWS and Chrome. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "Up arrow" (Read previous item) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey the boundaries of the dialog Examples:
Screen readers might announce something like "entering dialog" or "leaving dialog". Screen readers might imply the boundary by obscuring outside content when aria-modal=true is also present. Resultunknown pass fail partial
Notes aria-modal attribute, SHOULD limit reading to children of aria-modal=true, applied to dialog role Resultunknown pass fail partial
Notes Test case: Open the element list while the modal is open using Open element list (Insert + F3) Launch JAWS and Chrome. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[aria-modal=true]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[aria-modal=true]` keyboard focus location: within target virtual cursor location: within target set mode to browse issue commandsummary: attempt to navigate to content behind the modal via the element list Using the command: "Insert + F3" (Open element list) is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Previous unvisited link (shift+u) Launch JAWS and Chrome. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "shift+u" (Previous unvisited link) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test cases for JAWS + Edge Test case: open the dialog using Activate Button (Enter or Space) Launch JAWS and Edge. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandUsing the command: "Enter or Space" (Activate Button) Observe: dialog will open and focus will be moved to the target Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes dialog role, MUST convey the name of the dialog Resultunknown pass fail partial
Notes aria-modal attribute, MUST convey the presence of aria-modal=true, applied to dialog role Examples:
Screen readers might convey the modal state when entering the modal Screen readers might imply the modal state by restricting reading and navigation to the modal content Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Read previous item (Up arrow) Launch JAWS and Edge. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "Up arrow" (Read previous item) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey the boundaries of the dialog Examples:
Screen readers might announce something like "entering dialog" or "leaving dialog". Screen readers might imply the boundary by obscuring outside content when aria-modal=true is also present. Resultunknown pass fail partial
Notes aria-modal attribute, SHOULD limit reading to children of aria-modal=true, applied to dialog role Resultunknown pass fail partial
Notes Test case: Open the element list while the modal is open using Open element list (Insert + F3) Launch JAWS and Edge. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[aria-modal=true]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[aria-modal=true]` keyboard focus location: within target virtual cursor location: within target set mode to browse issue commandsummary: attempt to navigate to content behind the modal via the element list Using the command: "Insert + F3" (Open element list) is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Previous unvisited link (shift+u) Launch JAWS and Edge. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "shift+u" (Previous unvisited link) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test cases for JAWS + Firefox Test case: open the dialog using Activate Button (Enter or Space) Launch JAWS and Firefox. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandUsing the command: "Enter or Space" (Activate Button) Observe: dialog will open and focus will be moved to the target Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes dialog role, MUST convey the name of the dialog Resultunknown pass fail partial
Notes aria-modal attribute, MUST convey the presence of aria-modal=true, applied to dialog role Examples:
Screen readers might convey the modal state when entering the modal Screen readers might imply the modal state by restricting reading and navigation to the modal content Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Read previous item (Up arrow) Launch JAWS and Firefox. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "Up arrow" (Read previous item) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey the boundaries of the dialog Examples:
Screen readers might announce something like "entering dialog" or "leaving dialog". Screen readers might imply the boundary by obscuring outside content when aria-modal=true is also present. Resultunknown pass fail partial
Notes aria-modal attribute, SHOULD limit reading to children of aria-modal=true, applied to dialog role Resultunknown pass fail partial
Notes Test case: Open the element list while the modal is open using Open element list (Insert + F3) Launch JAWS and Firefox. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[aria-modal=true]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[aria-modal=true]` keyboard focus location: within target virtual cursor location: within target set mode to browse issue commandsummary: attempt to navigate to content behind the modal via the element list Using the command: "Insert + F3" (Open element list) is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Previous unvisited link (shift+u) Launch JAWS and Firefox. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "shift+u" (Previous unvisited link) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test cases for JAWS + IE Test case: open the dialog using Activate Button (Enter or Space) Launch JAWS and IE. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandUsing the command: "Enter or Space" (Activate Button) Observe: dialog will open and focus will be moved to the target Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes dialog role, MUST convey the name of the dialog Resultunknown pass fail partial
Notes aria-modal attribute, MUST convey the presence of aria-modal=true, applied to dialog role Examples:
Screen readers might convey the modal state when entering the modal Screen readers might imply the modal state by restricting reading and navigation to the modal content Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Read previous item (Up arrow) Launch JAWS and IE. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "Up arrow" (Read previous item) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey the boundaries of the dialog Examples:
Screen readers might announce something like "entering dialog" or "leaving dialog". Screen readers might imply the boundary by obscuring outside content when aria-modal=true is also present. Resultunknown pass fail partial
Notes aria-modal attribute, SHOULD limit reading to children of aria-modal=true, applied to dialog role Resultunknown pass fail partial
Notes Test case: Open the element list while the modal is open using Open element list (Insert + F3) Launch JAWS and IE. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[aria-modal=true]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[aria-modal=true]` keyboard focus location: within target virtual cursor location: within target set mode to browse issue commandsummary: attempt to navigate to content behind the modal via the element list Using the command: "Insert + F3" (Open element list) is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Previous unvisited link (shift+u) Launch JAWS and IE. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "shift+u" (Previous unvisited link) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test cases for Narrator + Edge Test case: open the dialog using Activate Item (primary action) (Enter or Space Bar) Launch Narrator and Edge. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandUsing the command: "Enter or Space Bar" (Activate Item (primary action)) Observe: dialog will open and focus will be moved to the target Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes dialog role, MUST convey the name of the dialog Resultunknown pass fail partial
Notes aria-modal attribute, MUST convey the presence of aria-modal=true, applied to dialog role Examples:
Screen readers might convey the modal state when entering the modal Screen readers might imply the modal state by restricting reading and navigation to the modal content Resultunknown pass fail partial
Notes Test case: navigate forward into open dialog using Jump to next item (scan mode) (Down arrow) Launch Narrator and Edge. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space Bar" (Activate Item (primary action)) Ensure AT location after executing the commandTarget: `*[role="dialog"]` keyboard focus location: within target virtual cursor location: within target set mode to browse issue commandsummary: navigate backwards out of the open dialog Using the command: "Up arrow" (Jump to previous item (scan mode)) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog"]` keyboard focus location: before target virtual cursor location: before target issue commandsummary: navigate forwards into the open dialog Using the command: "Down arrow" (Jump to next item (scan mode)) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog"]` keyboard focus location: within target virtual cursor location: within target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey the boundaries of the dialog Examples:
Screen readers might announce something like "entering dialog" or "leaving dialog". Screen readers might imply the boundary by obscuring outside content when aria-modal=true is also present. Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Jump to previous item (scan mode) (Up arrow) Launch Narrator and Edge. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space Bar" (Activate Item (primary action)) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "Up arrow" (Jump to previous item (scan mode)) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey the boundaries of the dialog Examples:
Screen readers might announce something like "entering dialog" or "leaving dialog". Screen readers might imply the boundary by obscuring outside content when aria-modal=true is also present. Resultunknown pass fail partial
Notes aria-modal attribute, SHOULD limit reading to children of aria-modal=true, applied to dialog role Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Previous heading (shift + h) Launch Narrator and Edge. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space Bar" (Activate Item (primary action)) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "shift + h" (Previous heading) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test cases for Narrator + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Narrator + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Narrator + IE The test has not been configured for this combination. Please open a GitHub issue.
Test cases for NVDA + Chrome Test case: open the dialog using Activate Button (Enter or Space) Launch NVDA and Chrome. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandUsing the command: "Enter or Space" (Activate Button) Observe: dialog will open and focus will be moved to the target Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes dialog role, MUST convey the name of the dialog Resultunknown pass fail partial
Notes aria-modal attribute, MUST convey the presence of aria-modal=true, applied to dialog role Examples:
Screen readers might convey the modal state when entering the modal Screen readers might imply the modal state by restricting reading and navigation to the modal content Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Read previous item (up arrow) Launch NVDA and Chrome. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "up arrow" (Read previous item) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey the boundaries of the dialog Examples:
Screen readers might announce something like "entering dialog" or "leaving dialog". Screen readers might imply the boundary by obscuring outside content when aria-modal=true is also present. Resultunknown pass fail partial
Notes aria-modal attribute, SHOULD limit reading to children of aria-modal=true, applied to dialog role Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using previous form field (shift + f) Launch NVDA and Chrome. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "shift + f" (previous form field) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Previous link (shift+ k) Launch NVDA and Chrome. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "shift+ k" (Previous link) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test case: Open the element list while the modal is open using Open Elements List (NVDA + F7) Launch NVDA and Chrome. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[aria-modal=true]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[aria-modal=true]` keyboard focus location: within target virtual cursor location: within target set mode to browse issue commandsummary: attempt to navigate to content behind the modal via the element list Using the command: "NVDA + F7" (Open Elements List) is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test cases for NVDA + Edge Test case: open the dialog using Activate Button (Enter or Space) Launch NVDA and Edge. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandUsing the command: "Enter or Space" (Activate Button) Observe: dialog will open and focus will be moved to the target Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes dialog role, MUST convey the name of the dialog Resultunknown pass fail partial
Notes aria-modal attribute, MUST convey the presence of aria-modal=true, applied to dialog role Examples:
Screen readers might convey the modal state when entering the modal Screen readers might imply the modal state by restricting reading and navigation to the modal content Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Read previous item (up arrow) Launch NVDA and Edge. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "up arrow" (Read previous item) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey the boundaries of the dialog Examples:
Screen readers might announce something like "entering dialog" or "leaving dialog". Screen readers might imply the boundary by obscuring outside content when aria-modal=true is also present. Resultunknown pass fail partial
Notes aria-modal attribute, SHOULD limit reading to children of aria-modal=true, applied to dialog role Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using previous form field (shift + f) Launch NVDA and Edge. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "shift + f" (previous form field) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Previous link (shift+ k) Launch NVDA and Edge. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "shift+ k" (Previous link) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test case: Open the element list while the modal is open using Open Elements List (NVDA + F7) Launch NVDA and Edge. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[aria-modal=true]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[aria-modal=true]` keyboard focus location: within target virtual cursor location: within target set mode to browse issue commandsummary: attempt to navigate to content behind the modal via the element list Using the command: "NVDA + F7" (Open Elements List) is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test cases for NVDA + Firefox Test case: open the dialog using Activate Button (Enter or Space) Launch NVDA and Firefox. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandUsing the command: "Enter or Space" (Activate Button) Observe: dialog will open and focus will be moved to the target Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes dialog role, MUST convey the name of the dialog Resultunknown pass fail partial
Notes aria-modal attribute, MUST convey the presence of aria-modal=true, applied to dialog role Examples:
Screen readers might convey the modal state when entering the modal Screen readers might imply the modal state by restricting reading and navigation to the modal content Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Read previous item (up arrow) Launch NVDA and Firefox. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "up arrow" (Read previous item) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey the boundaries of the dialog Examples:
Screen readers might announce something like "entering dialog" or "leaving dialog". Screen readers might imply the boundary by obscuring outside content when aria-modal=true is also present. Resultunknown pass fail partial
Notes aria-modal attribute, SHOULD limit reading to children of aria-modal=true, applied to dialog role Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using previous form field (shift + f) Launch NVDA and Firefox. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "shift + f" (previous form field) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Previous link (shift+ k) Launch NVDA and Firefox. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "shift+ k" (Previous link) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test case: Open the element list while the modal is open using Open Elements List (NVDA + F7) Launch NVDA and Firefox. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[aria-modal=true]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[aria-modal=true]` keyboard focus location: within target virtual cursor location: within target set mode to browse issue commandsummary: attempt to navigate to content behind the modal via the element list Using the command: "NVDA + F7" (Open Elements List) is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test cases for NVDA + IE The test has not been configured for this combination. Please open a GitHub issue.
Test cases for TalkBack + Chrome Test case: open the dialog using Activate button (double tap (or alt+enter)) Launch TalkBack and Chrome. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "Swipe right (or alt+right arrow)" (Read next item) Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandUsing the command: "double tap (or alt+enter)" (Activate button) Observe: dialog will open and focus will be moved to the target Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes dialog role, MUST convey the name of the dialog Resultunknown pass fail partial
Notes aria-modal attribute, MUST convey the presence of aria-modal=true, applied to dialog role Examples:
Screen readers might convey the modal state when entering the modal Screen readers might imply the modal state by restricting reading and navigation to the modal content Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Read previous item (Swipe left (or alt+left arrow)) Launch TalkBack and Chrome. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "Swipe right (or alt+right arrow)" (Read next item) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "double tap (or alt+enter)" (Activate button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "Swipe left (or alt+left arrow)" (Read previous item) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey the boundaries of the dialog Examples:
Screen readers might announce something like "entering dialog" or "leaving dialog". Screen readers might imply the boundary by obscuring outside content when aria-modal=true is also present. Resultunknown pass fail partial
Notes aria-modal attribute, SHOULD limit reading to children of aria-modal=true, applied to dialog role Resultunknown pass fail partial
Notes Test case: navigate forward into open dialog using Read next item (Swipe right (or alt+right arrow)) Launch TalkBack and Chrome. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "Swipe right (or alt+right arrow)" (Read next item) Ensure AT location after executing the commandTarget: `*[role="dialog"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "double tap (or alt+enter)" (Activate button) Ensure AT location after executing the commandTarget: `*[role="dialog"]` keyboard focus location: within target virtual cursor location: within target set mode to browse issue commandsummary: navigate backwards out of the open dialog Using the command: "Swipe left (or alt+left arrow)" (Read previous item) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog"]` keyboard focus location: before target virtual cursor location: before target issue commandsummary: navigate forwards into the open dialog Using the command: "Swipe right (or alt+right arrow)" (Read next item) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog"]` keyboard focus location: within target virtual cursor location: within target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey the boundaries of the dialog Examples:
Screen readers might announce something like "entering dialog" or "leaving dialog". Screen readers might imply the boundary by obscuring outside content when aria-modal=true is also present. Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using previous link (correct reading control must be selected) (Swipe up (alt+shift+L)) Launch TalkBack and Chrome. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "Swipe right (or alt+right arrow)" (Read next item) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "double tap (or alt+enter)" (Activate button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "Swipe up (alt+shift+L)" (previous link (correct reading control must be selected)) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test cases for TalkBack + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Access (Android) + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Access (Android) + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for VoiceOver (iOS) + Safari Test case: open the dialog using Activate Button (Double tap) Launch VoiceOver (iOS) and Safari. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "Swipe Right" (Next item) Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandUsing the command: "Double tap" (Activate Button) Observe: dialog will open and focus will be moved to the target Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes dialog role, MUST convey the name of the dialog Resultunknown pass fail partial
Notes aria-modal attribute, MUST convey the presence of aria-modal=true, applied to dialog role Examples:
Screen readers might convey the modal state when entering the modal Screen readers might imply the modal state by restricting reading and navigation to the modal content Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Previous item (Swipe Left) Launch VoiceOver (iOS) and Safari. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "Swipe Right" (Next item) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Double tap" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "Swipe Left" (Previous item) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey the boundaries of the dialog Examples:
Screen readers might announce something like "entering dialog" or "leaving dialog". Screen readers might imply the boundary by obscuring outside content when aria-modal=true is also present. Resultunknown pass fail partial
Notes aria-modal attribute, SHOULD limit reading to children of aria-modal=true, applied to dialog role Resultunknown pass fail partial
Notes Test case: attempt to navigate forwards to content behind the open modal using Next item (Swipe Right) Launch VoiceOver (iOS) and Safari. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "Swipe Right" (Next item) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Double tap" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate forwards past the end of the dialog Using the command: "Swipe Right" (Next item) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: after target virtual cursor location: after target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey the boundaries of the dialog Examples:
Screen readers might announce something like "entering dialog" or "leaving dialog". Screen readers might imply the boundary by obscuring outside content when aria-modal=true is also present. Resultunknown pass fail partial
Notes aria-modal attribute, SHOULD limit reading to children of aria-modal=true, applied to dialog role Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using previous link (correct item type must be selected) (Swipe up) Launch VoiceOver (iOS) and Safari. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "Swipe Right" (Next item) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Double tap" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "Swipe up" (previous link (correct item type must be selected)) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test cases for VoiceOver (iOS) + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for VoiceOver (macOS) + Safari Test case: open the dialog using Activate Button (VO + space) Launch VoiceOver (macOS) and Safari. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "next_button" Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandUsing the command: "VO + space" (Activate Button) Observe: dialog will open and focus will be moved to the target Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes dialog role, MUST convey the name of the dialog Resultunknown pass fail partial
Notes aria-modal attribute, MUST convey the presence of aria-modal=true, applied to dialog role Examples:
Screen readers might convey the modal state when entering the modal Screen readers might imply the modal state by restricting reading and navigation to the modal content Resultunknown pass fail partial
Notes Test case: navigate to modal container using Exit an object (such as an iframe) (VO + Shift + Up Arrow) Launch VoiceOver (macOS) and Safari. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "next_button" Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "VO + space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: navigate to the modal container Using the command: "VO + Shift + Up Arrow" (Exit an object (such as an iframe)) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: target virtual cursor location: target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes dialog role, MUST convey the name of the dialog Resultunknown pass fail partial
Notes dialog role, MUST convey the boundaries of the dialog Examples:
Screen readers might announce something like "entering dialog" or "leaving dialog". Screen readers might imply the boundary by obscuring outside content when aria-modal=true is also present. Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Read previous item (VO + Left Arrow) Launch VoiceOver (macOS) and Safari. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "next_button" Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "VO + space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: navigate to the dialog container Using the command: "VO + Shift + Up Arrow" (Exit an object (such as an iframe)) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: target virtual cursor location: target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "VO + Left Arrow" (Read previous item) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD limit reading to children of aria-modal=true, applied to dialog role Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Previous Heading (VO + Shift + Command + H) Launch VoiceOver (macOS) and Safari. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "next_button" Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "VO + space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: navigate to the dialog container Using the command: "VO + Shift + Up Arrow" (Exit an object (such as an iframe)) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: target virtual cursor location: target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "VO + Shift + Command + H" (Previous Heading) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test case: Open the element list while the modal is open using Open Rotor (VO + U) Launch VoiceOver (macOS) and Safari. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "next_button" Ensure AT location after executing the commandTarget: `*[aria-modal=true]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "VO + space" (Activate Button) Ensure AT location after executing the commandTarget: `*[aria-modal=true]` keyboard focus location: within target virtual cursor location: within target set mode to browse issue commandsummary: attempt to navigate to content behind the modal via the element list Using the command: "VO + U" (Open Rotor) is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test cases for VoiceOver (macOS) + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for VoiceOver (macOS) + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Orca + Firefox Test case: open the dialog using Activate Button (Enter or Space) Launch Orca and Firefox. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandUsing the command: "Enter or Space" (Activate Button) Observe: dialog will open and focus will be moved to the target Ensure AT location after executing the commandTarget: `*[role="dialog" aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey its role Examples:
A screen reader might announce an element as something like "<name>, <role>" A screen reader might imply the role by the presence of certain context roles Voice Control software might let the user say something like "click, <role>". Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers. Resultunknown pass fail partial
Notes dialog role, MUST convey the name of the dialog Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Read previous item (up arrow) Launch Orca and Firefox. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "up arrow" (Read previous item) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting dialog role, MUST convey the boundaries of the dialog Examples:
Screen readers might announce something like "entering dialog" or "leaving dialog". Screen readers might imply the boundary by obscuring outside content when aria-modal=true is also present. Resultunknown pass fail partial
Notes aria-modal attribute, MUST convey the presence of aria-modal=true, applied to dialog role Examples:
Screen readers might convey the modal state when entering the modal Screen readers might imply the modal state by restricting reading and navigation to the modal content Resultunknown pass fail partial
Notes aria-modal attribute, SHOULD limit reading to children of aria-modal=true, applied to dialog role Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using previous form field (shift + tab) Launch Orca and Firefox. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "shift + tab" (previous form field) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test case: attempt to navigate backwards to content behind the open modal using Previous link (shift+ k) Launch Orca and Firefox. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: within target virtual cursor location: within target issue commandsummary: attempt to navigate backwards past the start of the dialog Using the command: "shift+ k" (Previous link) You may need to issue this command multiple times Ensure AT location after executing the commandTarget: `*[role="dialog" *[aria-modal="true"]` keyboard focus location: before target virtual cursor location: before target is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes aria-modal attribute, MUST convey the presence of aria-modal=true, applied to dialog role Examples:
Screen readers might convey the modal state when entering the modal Screen readers might imply the modal state by restricting reading and navigation to the modal content Resultunknown pass fail partial
Notes aria-modal attribute, SHOULD limit reading to children of aria-modal=true, applied to dialog role Resultunknown pass fail partial
Notes Test case: Open the element list while the modal is open using Open a list of links (alt + shift+ k) Launch Orca and Firefox. Navigate to the test page . set mode to auto (do not explicitly change the mode) issue commandsummary: navigate forward to the button to open the dialog Using the command: "b" (Next button) Ensure AT location after executing the commandTarget: `*[aria-modal=true]` keyboard focus location: button virtual cursor location: button issue commandsummary: dialog will open and focus will be moved to the target Using the command: "Enter or Space" (Activate Button) Ensure AT location after executing the commandTarget: `*[aria-modal=true]` keyboard focus location: within target virtual cursor location: within target set mode to browse issue commandsummary: attempt to navigate to content behind the modal via the element list Using the command: "alt + shift+ k" (Open a list of links) is the expectation met? Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-modal attribute, SHOULD remove outside content from navigational shortcuts when aria-modal=true, applied to dialog role Examples:
Screen readers must not allow allow users to jump to the next element type if that element is outside of the modal Screen readers must not include outside content in the list of elements Resultunknown pass fail partial
Notes Test cases for Orca + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Control (iOS) + Safari The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Control (MacOS) + Safari The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Control (MacOS) + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Control (MacOS) + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Speech Recognition + Edge The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Speech Recognition + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Voice Access + Edge The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Voice Access + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Keyboard + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Keyboard + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Keyboard + Edge The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Mac Keyboard + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Mac Keyboard + Safari The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Mac Keyboard + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for iOS Keyboard + Safari The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Android Keyboard + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Android Keyboard + Firefox The test has not been configured for this combination. Please open a GitHub issue.