1

How often do you design with keyboard accessibility in mind? How often is it implemented in the final product?

  • Do you mean the "need" for the keyboard in building the product?! – Khalil Hanna May 13 '19 at 11:14
  • 1
    I mean considering the use of a product using just the keyboard. – Ren May 13 '19 at 18:00
  • 1
    Can you explain specifically what problem you're trying to solve? – 習約塔 May 14 '19 at 3:51
1

Design no, implementation yes. Well structured HTML laid out in a logical fashion should cover a lot of the basics with regards to keyboard navigation. It maybe necessary to add a few tabIndex to elements to let the user tab to certain sections of a webpage, but there is no way/need to show this on a mockup.

| improve this answer | |
  • How do you communicate this to the developers? – Ren May 13 '19 at 17:34
  • 3
    If something which isn't normally keyboard operable is intended to be keyboard operable, then that must be conveyed to the developer, with an explanation of why. This is easy to show this on a mockup; just include a note which says so, and point to whatever it is. Don't forget to explain what it should do when activated. – andrewmacpherson May 14 '19 at 6:42

Not the answer you're looking for? Browse other questions tagged or ask your own question.