Skip to content

Commit 1313bd4

Browse files
committed
Call out example in wishcart screenshot
1 parent 3701d40 commit 1313bd4

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

learn-pr/cela-accessibility/develop-keyboard-accessible-products/includes/4-review-design-considerations.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,8 @@ Indicate the sequence in which interactive elements should receive focus when na
4949
1. Use the focus order indicators to show the intended ordering of elements when being navigated using a keyboard.
5050
1. Long lists of like elements should be by-passable. For instance, imagine a Teams meeting where user has to make a user as signer. Users can invoke the menu item of that user and using arrow key they can drill down on the required menu item.
5151

52+
In the next image, the focus order is from left to right along the top navigation menu. Users can navigate the search categories within the dropdown using the **down arrow** or skip it with **Tab**.
53+
5254
:::image type="complex" source="../media/focus-order-accessibility-annotation-wishcart-application.png" alt-text="Screenshot of WishCart application with focus order annotations." lightbox="../media/focus-order-accessibility-annotation-wishcart-application.png":::
5355
Image of WishCart application with wishcart, delivering to New Delhi, Search field, choose language for shopping, hello sign in accounts &lists, returns &orders and Cart defined as custom component, Search in all categories Drop-down list as parent component and ‘All categories’, ‘Devices’ & ‘fashion’ as its child components. Each section has numerical labels indicating the focus order.
5456
:::image-end:::

0 commit comments

Comments
 (0)