7. Carrie had a motorcycle
accident and no longer has
use of her right arm; she
can use a mouse with her
left hand but finds it fiddly
and awkward.
image CC-BY-SA from patdavid on flickr
Personas
8. Combo BoxCombo Box
← / → move the caret within the edit field
Alt+↑/↓ opens / closes the list
↑/↓
moves focus up and down the list. As
focus moves inside the dropdown list,
the edit field is updated.
PgUp /
PgDown
selects the next/previous pages item
depending on the lists size.
w3.org/TR/wai-aria-practices/#combobox
Design keyboard interactions
11. tabIndex="0" element will be in the “natural” tab
order (defined by the DOM order)
tabIndex="-1" element will be programmatically
focusable, but not in the tab order.
* tabIndex > 0 element in a manual tab order
* Do not use in web components* Do not use in web components
Manage focus: tabIndex
15. Assistive technology
Do your custom elements provide semantic
information?
Role
State
Value
Name
Do all elements and images have meaningful
text alternatives?
19. Adding semantics: ARIA
<x-slider min="1" max="5" value="2.5">
</x-slider>
<!-- x-slider element template adds ARIA role and attributes which are visible in
light DOM -->
<x-slider role="slider" aria-valuemin="1" aria-valuemax="5" aria-valuenow="2.5">
</x-slider>
20. Text alternatives
•Ensure any information
communicated visually is also
available textually
•Provide alt text for all images
· alt="" will cause the image to be
skipped by the screen reader
25. Is the moving or flashing
content in your elements
stoppable and safe?
26. Six characteristics of
complete Web Components
1. available via keyboard
2. works with assistive technology
3. works without color
4. has sufficient contrast
5. works without sound
6. safe or stoppable moving/flashing content
27. Learn more
Accessible Web Components article
polymer-project.org/articles/
accessible-web-components.html