Important: This website does not attempt to establish a standard for how assistive technologies must behave. Read the FAQ for more information. Additionally, this is a work in progress. Please submit feedback or suggestions.

Run Test: aria-sort test

Current support: undefined

Tests the aria-sort attribute.

Go back to the test details page

Step 1: What are you testing with?

Select your testing combination.

Note: your selection will be saved until you change it or clear your browser cache.

Make sure everything is up to date

Always make sure that your OS, Browser, and Assistive technology are up to date with the latest production versions before submitting test results. Also make sure that your assistive technology is set to factory defaults.

Please be sure to read the full instructions before completing the test.

Step 2: Run test cases and submit your findings

Launch the chosen assistive technology that you want to test with.
Ensure that your OS, AT, and Browser are all up to date.
Navigate to the test page iframe (after these instructions) or open the test page.
For each test case, locate the target element(s) and test whether or not the expectations are met

Note: Screen readers will usually announce an element in the format: "<role>, <accessible name>, <other states and properties>, <accessible description>". The order in which the name, role, and properties are announced might differ between screen readers. The exact vocabulary used will also differ.

Technology information

The selected AT/Browser combo is:

Use the "what are you testing with?" form to change your combination.

AT Version (required)

OS Version (required)

Browser Version (required)

Test cases for JAWS + Chrome

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-1[aria-sort="ascending"]`

Launch JAWS and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-1[aria-sort="ascending"] button`

Launch JAWS and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-2[aria-sort="descending"]`

Launch JAWS and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-2[aria-sort="descending"] button`

Launch JAWS and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-3[aria-sort="none"]`

Launch JAWS and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-3[aria-sort="none"] button`

Launch JAWS and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-4[aria-sort="other"]`

Launch JAWS and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-4[aria-sort="other"] button`

Launch JAWS and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Enter or Space (Activate Button) on the target of `#target-1[aria-sort="ascending"]`

Launch JAWS and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
Position and configure the screen reader so that the following conditions are met
- Virtual focus is: target
- Keyboard focus is: target
- Mode is: auto (do not explicitly change the mode)
Issue the command: Enter or Space (Activate Button)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey changes to the sort value, applied to th element

Examples:

Screen readers will convey the new sort value after activating a button to change the sort direction.

Result

Notes

Test cases for JAWS + Firefox

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-1[aria-sort="ascending"]`

Launch JAWS and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-1[aria-sort="ascending"] button`

Launch JAWS and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-2[aria-sort="descending"]`

Launch JAWS and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-2[aria-sort="descending"] button`

Launch JAWS and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-3[aria-sort="none"]`

Launch JAWS and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-3[aria-sort="none"] button`

Launch JAWS and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-4[aria-sort="other"]`

Launch JAWS and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-4[aria-sort="other"] button`

Launch JAWS and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Enter or Space (Activate Button) on the target of `#target-1[aria-sort="ascending"]`

Launch JAWS and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
Position and configure the screen reader so that the following conditions are met
- Virtual focus is: target
- Keyboard focus is: target
- Mode is: auto (do not explicitly change the mode)
Issue the command: Enter or Space (Activate Button)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey changes to the sort value, applied to th element

Examples:

Screen readers will convey the new sort value after activating a button to change the sort direction.

Result

Notes

Test cases for JAWS + IE

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-1[aria-sort="ascending"]`

Launch JAWS and IE.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-1[aria-sort="ascending"] button`

Launch JAWS and IE.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-2[aria-sort="descending"]`

Launch JAWS and IE.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-2[aria-sort="descending"] button`

Launch JAWS and IE.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-3[aria-sort="none"]`

Launch JAWS and IE.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-3[aria-sort="none"] button`

Launch JAWS and IE.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-4[aria-sort="other"]`

Launch JAWS and IE.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-4[aria-sort="other"] button`

Launch JAWS and IE.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Enter or Space (Activate Button) on the target of `#target-1[aria-sort="ascending"]`

Launch JAWS and IE.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
Position and configure the screen reader so that the following conditions are met
- Virtual focus is: target
- Keyboard focus is: target
- Mode is: auto (do not explicitly change the mode)
Issue the command: Enter or Space (Activate Button)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey changes to the sort value, applied to th element

Examples:

Screen readers will convey the new sort value after activating a button to change the sort direction.

Result

Notes

Test cases for Narrator + Edge

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-1[aria-sort="ascending"]`

Launch Narrator and Edge.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-1[aria-sort="ascending"] button`

Launch Narrator and Edge.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-2[aria-sort="descending"]`

Launch Narrator and Edge.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-2[aria-sort="descending"] button`

Launch Narrator and Edge.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-3[aria-sort="none"]`

Launch Narrator and Edge.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-3[aria-sort="none"] button`

Launch Narrator and Edge.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-4[aria-sort="other"]`

Launch Narrator and Edge.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-4[aria-sort="other"] button`

Launch Narrator and Edge.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Enter or Space Bar (Activate Item (primary action)) on the target of `#target-1[aria-sort="ascending"]`

Launch Narrator and Edge.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
Position and configure the screen reader so that the following conditions are met
- Virtual focus is: target
- Keyboard focus is: target
- Mode is: auto (do not explicitly change the mode)
Issue the command: Enter or Space Bar (Activate Item (primary action))
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey changes to the sort value, applied to th element

Examples:

Screen readers will convey the new sort value after activating a button to change the sort direction.

Result

Notes

Test cases for NVDA + Chrome

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-1[aria-sort="ascending"]`

Launch NVDA and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-1[aria-sort="ascending"] button`

Launch NVDA and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-2[aria-sort="descending"]`

Launch NVDA and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-2[aria-sort="descending"] button`

Launch NVDA and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-3[aria-sort="none"]`

Launch NVDA and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-3[aria-sort="none"] button`

Launch NVDA and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-4[aria-sort="other"]`

Launch NVDA and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-4[aria-sort="other"] button`

Launch NVDA and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Enter or Space (Activate Button) on the target of `#target-1[aria-sort="ascending"]`

Launch NVDA and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
Position and configure the screen reader so that the following conditions are met
- Virtual focus is: target
- Keyboard focus is: target
- Mode is: auto (do not explicitly change the mode)
Issue the command: Enter or Space (Activate Button)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey changes to the sort value, applied to th element

Examples:

Screen readers will convey the new sort value after activating a button to change the sort direction.

Result

Notes

Test cases for NVDA + Edge

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-1[aria-sort="ascending"]`

Launch NVDA and Edge.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-1[aria-sort="ascending"] button`

Launch NVDA and Edge.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-2[aria-sort="descending"]`

Launch NVDA and Edge.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-2[aria-sort="descending"] button`

Launch NVDA and Edge.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-3[aria-sort="none"]`

Launch NVDA and Edge.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-3[aria-sort="none"] button`

Launch NVDA and Edge.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-4[aria-sort="other"]`

Launch NVDA and Edge.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-4[aria-sort="other"] button`

Launch NVDA and Edge.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Enter or Space (Activate Button) on the target of `#target-1[aria-sort="ascending"]`

Launch NVDA and Edge.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
Position and configure the screen reader so that the following conditions are met
- Virtual focus is: target
- Keyboard focus is: target
- Mode is: auto (do not explicitly change the mode)
Issue the command: Enter or Space (Activate Button)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey changes to the sort value, applied to th element

Examples:

Screen readers will convey the new sort value after activating a button to change the sort direction.

Result

Notes

Test cases for NVDA + Firefox

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-1[aria-sort="ascending"]`

Launch NVDA and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-1[aria-sort="ascending"] button`

Launch NVDA and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-2[aria-sort="descending"]`

Launch NVDA and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-2[aria-sort="descending"] button`

Launch NVDA and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-3[aria-sort="none"]`

Launch NVDA and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-3[aria-sort="none"] button`

Launch NVDA and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use Control + Alt + Right arrow (Move to next column) to navigate forward to `#target-4[aria-sort="other"]`

Launch NVDA and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"]
- 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.
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)
Issue the command: Control + Alt + Right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-4[aria-sort="other"] button`

Launch NVDA and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Enter or Space (Activate Button) on the target of `#target-1[aria-sort="ascending"]`

Launch NVDA and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
Position and configure the screen reader so that the following conditions are met
- Virtual focus is: target
- Keyboard focus is: target
- Mode is: auto (do not explicitly change the mode)
Issue the command: Enter or Space (Activate Button)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey changes to the sort value, applied to th element

Examples:

Screen readers will convey the new sort value after activating a button to change the sort direction.

Result

Notes

Test cases for TalkBack + Chrome

Test case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `#target-1[aria-sort="ascending"]`

Launch TalkBack and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
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)
Issue the command: Swipe right (or alt+right arrow) (Read next item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `#target-2[aria-sort="descending"]`

Launch TalkBack and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"]
- 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.
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)
Issue the command: Swipe right (or alt+right arrow) (Read next item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `#target-3[aria-sort="none"]`

Launch TalkBack and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"]
- 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.
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)
Issue the command: Swipe right (or alt+right arrow) (Read next item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `#target-4[aria-sort="other"]`

Launch TalkBack and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"]
- 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.
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)
Issue the command: Swipe right (or alt+right arrow) (Read next item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use double tap (or alt+enter) (Activate button) on the target of `#target-1[aria-sort="ascending"]`

Launch TalkBack and Chrome.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
Position and configure the screen reader so that the following conditions are met
- Virtual focus is: target
- Keyboard focus is: target
- Mode is: auto (do not explicitly change the mode)
Issue the command: double tap (or alt+enter) (Activate button)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey changes to the sort value, applied to th element

Examples:

Screen readers will convey the new sort value after activating a button to change the sort direction.

Result

Notes

Test cases for VoiceOver (iOS) + Safari

Test case: Use Swipe Right (Next item) to navigate forward to `#target-1[aria-sort="ascending"]`

Launch VoiceOver (iOS) and Safari.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
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)
Issue the command: Swipe Right (Next item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Swipe Right (Next item) to navigate forward to `#target-2[aria-sort="descending"]`

Launch VoiceOver (iOS) and Safari.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"]
- 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.
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)
Issue the command: Swipe Right (Next item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Swipe Right (Next item) to navigate forward to `#target-3[aria-sort="none"]`

Launch VoiceOver (iOS) and Safari.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"]
- 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.
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)
Issue the command: Swipe Right (Next item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use Swipe Right (Next item) to navigate forward to `#target-4[aria-sort="other"]`

Launch VoiceOver (iOS) and Safari.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"]
- 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.
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)
Issue the command: Swipe Right (Next item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Double tap (Activate Button) on the target of `#target-1[aria-sort="ascending"]`

Launch VoiceOver (iOS) and Safari.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
Position and configure the screen reader so that the following conditions are met
- Virtual focus is: target
- Keyboard focus is: target
- Mode is: auto (do not explicitly change the mode)
Issue the command: Double tap (Activate Button)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey changes to the sort value, applied to th element

Examples:

Screen readers will convey the new sort value after activating a button to change the sort direction.

Result

Notes

Test cases for VoiceOver (macOS) + Safari

Test case: Use VO + Right Arrow (Move to Next Column) to navigate forward to `#target-1[aria-sort="ascending"]`

Launch VoiceOver (macOS) and Safari.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
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)
Issue the command: VO + Right Arrow (Move to Next Column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-1[aria-sort="ascending"] button`

Launch VoiceOver (macOS) and Safari.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use VO + Right Arrow (Move to Next Column) to navigate forward to `#target-2[aria-sort="descending"]`

Launch VoiceOver (macOS) and Safari.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"]
- 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.
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)
Issue the command: VO + Right Arrow (Move to Next Column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-2[aria-sort="descending"] button`

Launch VoiceOver (macOS) and Safari.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use VO + Right Arrow (Move to Next Column) to navigate forward to `#target-3[aria-sort="none"]`

Launch VoiceOver (macOS) and Safari.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"]
- 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.
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)
Issue the command: VO + Right Arrow (Move to Next Column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-3[aria-sort="none"] button`

Launch VoiceOver (macOS) and Safari.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use VO + Right Arrow (Move to Next Column) to navigate forward to `#target-4[aria-sort="other"]`

Launch VoiceOver (macOS) and Safari.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"]
- 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.
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)
Issue the command: VO + Right Arrow (Move to Next Column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-4[aria-sort="other"] button`

Launch VoiceOver (macOS) and Safari.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use VO + space (Activate Button) on the target of `#target-1[aria-sort="ascending"]`

Launch VoiceOver (macOS) and Safari.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
Position and configure the screen reader so that the following conditions are met
- Virtual focus is: target
- Keyboard focus is: target
- Mode is: auto (do not explicitly change the mode)
Issue the command: VO + space (Activate Button)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey changes to the sort value, applied to th element

Examples:

Screen readers will convey the new sort value after activating a button to change the sort direction.

Result

Notes

Test cases for Orca + Firefox

Test case: Use alt + shift + right arrow (Move to next column) to navigate forward to `#target-1[aria-sort="ascending"]`

Launch Orca and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
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)
Issue the command: alt + shift + right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-1[aria-sort="ascending"] button`

Launch Orca and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'ascending' value, applied to th element

Examples:

Screen readers will convey the 'ascending' value as something like "sorted ascending" or "sort up" when navigating to the header or one of its cells.

Result

Notes

Test case: Use alt + shift + right arrow (Move to next column) to navigate forward to `#target-2[aria-sort="descending"]`

Launch Orca and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"]
- 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.
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)
Issue the command: alt + shift + right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-2[aria-sort="descending"] button`

Launch Orca and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-2[aria-sort="descending"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'descending' value, applied to th element

Examples:

Screen readers will convey the 'descending' value as something like "sorted descending" or "sort down" when navigating to the header or one of its cells.

Result

Notes

Test case: Use alt + shift + right arrow (Move to next column) to navigate forward to `#target-3[aria-sort="none"]`

Launch Orca and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"]
- 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.
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)
Issue the command: alt + shift + right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-3[aria-sort="none"] button`

Launch Orca and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-3[aria-sort="none"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'none' value either by omitting any sort information or by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers will convey the 'none' value by omitting any sort announcements when navigating to the header or one of its cells.

Result

Notes

aria-sort attribute, SHOULD convey the 'none' value by indicating that the header is unsorted but sortable, applied to th element

Examples:

Screen readers may convey the 'none' value by indicating that the header is sortable but omitting a current sort direction.

Result

Notes

Test case: Use alt + shift + right arrow (Move to next column) to navigate forward to `#target-4[aria-sort="other"]`

Launch Orca and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"]
- 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.
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)
Issue the command: alt + shift + right arrow (Move to next column)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Tab (Read next focusable item) to navigate forward to `#target-4[aria-sort="other"] button`

Launch Orca and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-4[aria-sort="other"] button
- If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
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)
Issue the command: Tab (Read next focusable item)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey the 'other' value, applied to th element

Examples:

Screen readers will convey the 'other' value as something like "sorted" or "sorted other" when navigating to the header or one of its cells.

Result

Notes

Test case: Use Enter or Space (Activate Button) on the target of `#target-1[aria-sort="ascending"]`

Launch Orca and Firefox.
Navigate to the test page.
Find the target element(s) that you will test against. Identify all elements that match this selector:#target-1[aria-sort="ascending"]
- 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.
Position and configure the screen reader so that the following conditions are met
- Virtual focus is: target
- Keyboard focus is: target
- Mode is: auto (do not explicitly change the mode)
Issue the command: Enter or Space (Activate Button)
- After issuing the command, virtual focus should be: target
Record results for the relevant expectations

OutputNotesIf support is hidden behind non-default settings, briefly describe that setting

aria-sort attribute, MUST convey changes to the sort value, applied to th element

Examples:

Screen readers will convey the new sort value after activating a button to change the sort direction.

Result

Notes

Run Test: aria-sort test

Step 1: What are you testing with?

Make sure everything is up to date

Step 2: Run test cases and submit your findings

Test cases for Dragon Naturally Speaking + Chrome

Test cases for Dragon Naturally Speaking + IE

Test cases for Dragon Naturally Speaking + Firefox

Test cases for JAWS + Chrome

Test cases for JAWS + Edge

Test cases for JAWS + Firefox

Test cases for JAWS + IE

Test cases for Narrator + Edge

Test cases for Narrator + Firefox

Test cases for Narrator + Chrome

Test cases for Narrator + IE

Test cases for NVDA + Chrome

Test cases for NVDA + Edge

Test cases for NVDA + Firefox

Test cases for NVDA + IE

Test cases for TalkBack + Chrome

Test cases for TalkBack + Firefox

Test cases for Voice Access (Android) + Chrome

Test cases for Voice Access (Android) + Firefox

Test cases for VoiceOver (iOS) + Safari

Test cases for VoiceOver (iOS) + Chrome

Test cases for VoiceOver (macOS) + Safari

Test cases for VoiceOver (macOS) + Chrome

Test cases for VoiceOver (macOS) + Firefox

Test cases for Orca + Firefox

Test cases for Orca + Chrome

Test cases for Voice Control (iOS) + Safari

Test cases for Voice Control (MacOS) + Safari

Test cases for Voice Control (MacOS) + Chrome

Test cases for Voice Control (MacOS) + Firefox

Test cases for Windows Speech Recognition + Edge

Test cases for Windows Speech Recognition + Chrome

Test cases for Windows Voice Access + Edge

Test cases for Windows Voice Access + Chrome

Test cases for Windows Keyboard + Chrome

Test cases for Windows Keyboard + Firefox

Test cases for Windows Keyboard + Edge

Test cases for Mac Keyboard + Chrome

Test cases for Mac Keyboard + Safari

Test cases for Mac Keyboard + Firefox

Test cases for iOS Keyboard + Safari

Test cases for Android Keyboard + Chrome

Test cases for Android Keyboard + Firefox

Copy/paste this into a github issue

Related Features

Is something not right?