Accessible modal windows
•
18 likes•9,292 views
The document discusses guidelines for making modal windows accessible. A modal window forces user interaction before allowing interaction with the main page. Key guidelines include: allowing full keyboard and screen reader navigation within the modal; informing users and screen readers when a modal opens through focus, labels, roles and descriptions; preventing interaction outside the modal; and ensuring screen readers can operate in "read" and "form" modes within modals as needed.
Report
Share
More Related Content
What's hot
What's hot (20)
Similar to Accessible modal windows
Similar to Accessible modal windows (20)
More from Russ Weakley
More from Russ Weakley (20)
Recently uploaded
Recently uploaded (20)
Accessible modal windows
- 2. What is a modal window?
- 3. A modal window is a window that forces the user to interact with it before they can go back to using the parent page.
- 4. Generally, modal windows are designed to sit over the top of the parent page. In some cases, the parent page is greyed out so that users can visually focus on the modal dialog only.
- 6. Different types of modal window
- 7. Modal windows can be used for all sorts of different roles such as:
- 8. Modal alerts
- 10. Modal lightboxes
- 11. Modeless windows
- 12. Modal windows should not be mistaken for modeless windows.
- 13. Modeless windows are secondary windows that stay active on the user's screen until dismissed. Modeless windows can be minimised or hidden behind other windows.
- 14. Unlike a modal window, a modeless window will allow the user to continue working with the application while the modeless window is still open.
- 15. What makes an accessible modal window?
- 16. Keyboard only
- 17. Users must be able to navigate through the modal window as needed using keyboard-only.
- 18. Users should be able to close the modal window using keyboard- only.
- 19. Users should not be able to TAB outside of the modal window until the modal window has been closed.
- 20. There should be no hidden keystrokes as users move through the modal window.
- 21. Screen reader
- 22. All relevant components should be identified to screen reader users as they are accessed.
- 23. Screen readers should be notified of changes as they occur.
- 24. Focus should be placed on relevant areas as changes occur.
- 25. General user
- 26. The process should be easy to understand for any type of user - keyboard only user, screen reader user, general user.
- 27. Informing users before modal window spawning
- 28. If a modal window spawns from a focusable element, screen reader users should be given additional information to let them know what will happen.
- 29. This can be done using a range of different methods, depending on the element that is used.
- 30. Hyperlinks
- 31. For hyperlinks, we could add additional information using the “title”, aria-labelledby, or “aria- label” attributes. Or we could place the addition information inside the link and then hide it.
- 32. <!-- title attribute -->! <a href="#id-name" ! ! title="Added info">! ! Add bank account! </a>!
- 33. <!-- aria-label attribute -->! <a href="#id-name" ! ! aria-label="Add bank account - Added info">! ! Add bank account! </a>!
- 34. <!-- aria-labelledby attribute -->! <a href="#id-name" ! ! aria-labelledby="info1">! ! Add bank account! </a>! <p id="info1" class="hidden">! ! Added info! </p>!
- 35. <!-- hidden info -->! <a href="#id-name">! ! Add bank account! ! <span class="hidden">Added info</span>! </a>!
- 36. Buttons
- 37. For <button> elements, we could use any of these same techniques.
- 38. <!-- title attribute -->! <button id="id-name" ! ! title="Added info">! ! Add bank account! </button>!
- 39. <!-- aria-label attribute -->! <button id="id-name" ! ! aria-label="Add bank account - Added info">! ! Add bank account! </button>!
- 40. <!-- aria-labelledby attribute -->! <button id="id-name" ! ! aria-labelledby="info1">! ! Add bank account! </button>! <p id="info1" class="hidden">! ! Added info! </p>!
- 41. <!-- hidden info -->! <button id="id-name">! ! Add bank account! ! <span class="hidden">Added info</span>! </button>!
- 42. Inputs
- 43. For <input> elements, we could use any of these same techniques - except the hidden method as we cannot place HTML markup inside input elements.
- 44. Images
- 45. For <img> elements, we could use any of the above techniques or even add info into the “alt” attribute.
- 46. <!-- alt attribute -->! <a href="#id-name">! ! <img src="a.gif" ! ! alt="Add bank account - Added info">! </a>!
- 48. 1. Hiding the modal window
- 49. Initially, we need to hide the modal dialog content so that is not seen by sighted users or heard by screen reader users.
- 50. <!-- hiding modal window -->! <div! ! style="display:none">! ! ...! </div>!
- 51. 2. Showing the modal window
- 52. When a user triggers the modal window, we need to use JavaScript to switch the values within these two attributes.
- 53. The “display” value needs to change from “none” to “block”.
- 54. <!-- aria-hidden -->! <div! ! style="display:block">! ! ...! </div>!
- 55. When the modal window becomes active, the rest of the page - everything apart from the modal window container, could then be set with aria-hidden=“true”.
- 56. <!-- all other content -->! <div! ! aria-hidden="true">! ! ...! </div>! ! <!-- modal window -->! <div! ! style="display:block">! ! ...! </div>! !
- 57. Notifying screen readers when arriving at modal window
- 58. When a modal window is spawned, we need to provide a range of information to screen reader users.
- 59. 1. Setting focus on the modal window
- 60. The first thing we need to do when a modal window spawns is set the initial focus to the modal window element itself.
- 61. Initial focus
- 62. This is important because we are going to give the window a label as well as potentially adding additional descriptive information.
- 63. If we set focus on an element inside the window, such as the first form control, the label and additional information will not be heard by screen reader users.
- 64. Initial focus
- 66. We need to inform screen reader users that this modal window is a “modal dialog”. We can do this by adding role=“dialog”.
- 67. <!-- adding aria role -->! <div! ! style="display:block"! ! aria-hidden="false"! ! role="dialog">! ! ...! </div>
- 68. 3. Adding a label
- 69. We need to provide a label for the modal dialog, so screen reader users know its purpose.
- 70. We can do this by linking the modal dialog container to the primary <hn> element using “aria-labeledby”.
- 71. <!-- adding aria labelledby -->! <div! ! style="display:block"! ! aria-hidden="false"! ! role="dialog"! ! aria-labelledby="modal-label">! ! <h1 id="modal-label">! ! ! Choose account! ! </h1>! </div>!
- 72. Now the heading will be announced to screen reader users when the modal dialog is spawned.
- 73. 4. Adding optional additional information
- 74. In some circumstances, such as complex modal dialogs, we may need to provide a more detailed description of the purpose of the modal dialog.
- 75. We can provide additional information by linking the modal dialog container to some descriptive content using “aria- describedby”.
- 76. <!-- adding aria labelledby -->! <div! ! style="display:block"! ! aria-hidden="false"! ! role="dialog"! ! aria-labelledby="modal-label"! ! aria-describedby="modal-description">! ! <h1 id="modal-label">! ! ! Choose account! ! </h1>! ! <p id="modal-description">! ! ! Description here! ! </p>! </div>!
- 77. Ideally, this content should be hidden or placed at the end of the modal dialog content, after all other content in the source.
- 78. Otherwise it can be read-aloud twice in quick succession by screen readers, which can be confusing for some users.
- 79. 5. Working with older Assistive Technologies?
- 80. What about older assistive technologies that may not support some of the more advanced ARIA attributes?
- 81. If this is an issue, other simpler options may need to be considered.
- 82. One simple option would be to provide a special focusable element, such as a link, that comes before all others.
- 83. This could be presented as a simple “Information” icon that sits in the top left corner of the window.
- 85. We could then add a description of the modal window to this link.
- 86. <!-- help info -->! <a href="#id-name">! ! <img src="a.gif" alt="Help">! ! <span class="tooltip">Added info</span>! </a>! !
- 87. This method could be useful for both screen reader users and general users, as the information could be made visible as a tooltip on focus.
- 89. Actions outside the modal window
- 90. Users should not be able to mouse-click on any focusable element outside the modal window while it is open.
- 91. CLICK
- 92. Users should not be able to use TAB keystrokes to focus on any focusable element outside the modal window while it is open.
- 93. TAB
- 95. Mouse
- 96. Users should be able to mouse- click to enable any focusable element inside the modal window while it is open.
- 97. CLICK
- 98. CLICK
- 99. CLICK
- 100. CLICK
- 101. CLICK
- 102. CLICK
- 103. CLICK
- 104. TAB keystroke
- 105. Users should be able to use TAB keystrokes to navigate to any focusable element inside the modal window while it is open.
- 106. TAB
- 107. TAB
- 108. TAB
- 109. TAB
- 110. TAB
- 111. TAB
- 112. TAB
- 113. SHIFT + TAB keystroke
- 114. Users should be able to use SHIFT + TAB keystrokes to navigate backwards to any focusable element inside the modal window while it is open.
- 115. SHIFT + TAB
- 116. SHIFT + TAB
- 117. SHIFT + TAB
- 118. SHIFT + TAB
- 119. SHIFT + TAB
- 120. SHIFT + TAB
- 121. SHIFT + TAB
- 123. Users should be able to use ENTER or SPACE keystrokes on relevant elements while inside the modal window - especially if they are button elements.
- 124. ENTER
- 125. ENTER
- 126. SPACE
- 127. SPACE
- 128. ARROW keystrokes
- 129. When inside form controls, ARROW keys are generally used to allow users to navigate user- entered text within the form control.
- 130. An example might be a user entering data into a <textarea> element. The user can navigate within their entered text using ARROW keys to move to previous and next characters, next line etc.
- 131. However, some form controls use ARROW keys to allow users to choose options within a set of choices.
- 132. For example, radio buttons and select menus allow users to navigate through choices using ARROW keys.
- 133. So, users should be able to use ARROW keystrokes to change radio button options.
- 134. TAB
- 135. ARROW
- 136. Users should be able to use ARROW keystrokes to change select menu options.
- 137. Option 1 - apples ARROW
- 138. Option 2 - pears ARROW
- 139. Option 3 - bananas ARROW
- 140. ESC keystroke
- 141. Users should be able to use the ESC key to close modal.
- 142. ESC
- 143. Modal windows and screen reader “read” mode
- 144. Screen readers generally operate in one of two modes: ‘read’ mode and ‘form’ mode.
- 145. In “read” mode, users can read and navigate the page. Users cannot interact with form controls
- 146. In “form” mode, users can interact with form controls. Users cannot read and navigate the page.
- 147. In some cases, modal windows may include important content that is not form-related. In these cases, screen reader users need to be able to operate in “read” mode.
- 148. This means that screen reader users must be able to navigate though content using all of the standard “read” mode keys.
- 149. In these cases, we could wrap a new element around all the content within the window and set it with role=“document”.
- 150. The “document” role informs screen readers of the need to augment browser keyboard support so that users can navigate and read any content within the “document” region.
- 151. <!-- adding aria role -->! <div! ! style="display:block"! ! aria-hidden="false"! ! role="dialog"! ! aria-labelledby="modal-label"! ! aria-describedby="modal-description">! ! <div role="document">! ! ! <h1 id="modal-label">! ! ! ! Choose account! ! ! </h1>! ! ! <p id="modal-description">! ! ! ! Description here! ! ! </p>! ! </div>!
- 152. Adding meaning to important actions
- 153. For some important actions inside the modal window, screen reader users should be given additional information to let them know what will happen.
- 154. Submit
- 155. As screen reader users are submitting form data, they should be informed that:
- 156. 1. they will be taken back to the parent page.
- 157. 2. where this data will be submitted when they return to the parent page.
- 158. ENTER “Submit and return to bank balance information. Your data will be added to the Balance table”
- 159. Close window
- 160. As screen reader users focus on the “Close” function, they should be informed that closing will take them back to the parent page.
- 161. ENTER “Leave form and return to bank balance information”
- 162. A question on tab order
- 163. Is it better to present to “Close” button before any form controls in tab order, or after any form controls.
- 164. A lot will depend on the complexity and amount of content inside the modal window.
- 165. Simple modal windows
- 166. For simple modal windows, it may be easier to place the “Close” button last in tab order.
- 167. 1
- 168. 2
- 169. 3
- 171. For complex modal windows, where users may want to go back to the parent page quickly without having to TAB through the whole window, it may be better to place the “Close” button first in tab order.
- 172. 1
- 173. 2
- 174. 3
- 175. 4
- 176. 5
- 177. 6
- 178. On sites where there are numerous different modal dialogs, the most important thing is consistency. Decided on a method and use it for all modal windows so that it becomes predictable.
- 180. When the modal window is closed, if users are being taken back to the parent page:
- 181. 1. Focus should be placed on the relevant component of the parent page. The most common practice is to move focus back to the element that invoked the dialog.
- 182. The user should not be thrown back to the top of the parent page unless there is a good reason!
- 183. 2. The user should be informed where they are and what change has occurred.
- 184. ENTER
- 185. Lorem ipsum dolor sit amet consect etuer adipi scing elit sed diam nonummy nibh euismod tinunt ut laoreet dolore magna aliquam erat volut. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip vel eum iriure dolor in hendrerit in vulputate. Accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat. Heading here Another thing here Add your bank balance Another heading $1,200.34 Focus “Bank balance $1200.34 added to bank information table”
- 186. Thanks to…
- 187. A huge thanks to Roger Hudson, Steve Faulkner and James Edwards for their advice and feedback on these slides.
- 188. Russ Weakley Max Design ! Site: maxdesign.com.au Twitter: twitter.com/russmaxdesign Slideshare: slideshare.net/maxdesign Linkedin: linkedin.com/in/russweakley