From 22f64f7c4c54c5062eb31e123c8f9bcd954aafbb Mon Sep 17 00:00:00 2001 From: Dina Rosvoll <35217511+dinarosv@users.noreply.github.com> Date: Fri, 14 Jan 2022 11:30:42 +0100 Subject: [PATCH] Update packages/dnb-design-system-portal/src/docs/quickguide-designer/accessibility/checklist.md Co-authored-by: Thayanan Tharmapalan --- .../src/docs/quickguide-designer/accessibility/checklist.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/dnb-design-system-portal/src/docs/quickguide-designer/accessibility/checklist.md b/packages/dnb-design-system-portal/src/docs/quickguide-designer/accessibility/checklist.md index 7772ab05767..5d5827d4c6d 100644 --- a/packages/dnb-design-system-portal/src/docs/quickguide-designer/accessibility/checklist.md +++ b/packages/dnb-design-system-portal/src/docs/quickguide-designer/accessibility/checklist.md @@ -10,5 +10,5 @@ Building an accessible interface starts at the UX stage of design. Much of the D - [ ] **Accessible for keyboard users**: Plan how you would like a keyboard navigator to access interface laments/areas. What will the order of tabbing be? - [ ] **Skip to content**: Should you provide a ’skip to content’ feature to allow users to get to the main content quickly - [ ] **Responsive page**: Plan how the interface will respond to different screen sizes. The layout may have to change - how will this affect accessibility? -- [ ] **Zoom the interface**: Some users zoom their browser to increase the size. How will elements behave in these scenarios? Will they overlap. What happens to wide horizontal components such as navigation or tab sets? +- [ ] **Zoom the interface**: Some users zoom their browser to increase the size. How will elements behave in these scenarios? Will they overlap? What happens to wide horizontal components such as navigation or tab sets? - [ ] **Fluid design**: As opposed to using fixed breakpoints, fluid design allows the content to reflow in the same order as screen readers render content to users who are blind or visually impaired.