[community] Guidance/resources re: designers providing accessibility requirements to engineers?

Joe Murray joe.murray at jmaconsulting.biz
Tue Nov 20 18:05:21 UTC 2018

At a high level they'll understand if you say the product needs to be WCAG
2.0 AA compliant, or WCAG 2.1 AAA with respect to some specific features.
You're likely to want to be much more specific about your interaction

The engineers will need not just a visual design but a full description of
the interaction design. Here's a simple one:

Here's a more interesting one that indicates how a menu should respond to
keyboard actions:
and https://www.w3.org/WAI/tutorials/menus/application-menus/#submenu-items

Note that there are often allowable variations for something like an
accessible menu in terms of some of the details. Providing references can
help, like to one of the many examples out on the web like


Joe Murray, PhD
President, JMA Consulting
joe.murray at jmaconsulting.biz
skype JosephPMurray twitter JoeMurray

On Tue, Nov 20, 2018 at 12:47 PM Kate McGee <kate at lumenlearning.com> wrote:

> Hey there,
> I'm looking for guidance, resources, etc. on best practises for providing
> requirements/documentation to engineers on expected accessibility UX. I'm
> a UX
> designer and I'm familiar with providing specification via tools like
> InVision
> or Zeplin for UX/UI. I'm not sure if that's a good option for
> accessibility UX
> as well or if there's any guidance from the community on how to best
> provide the
> expected UX to an engineer (for example when a user is navigating via
> keyboard
> only)?
> Thanks for the help!
> Kate McGeeSenior Product DesignerLumen Learning
> ________________________________________
> Inclusive Design Community (community at lists.idrc.ocadu.ca)
> To manage your subscription, please visit:
> https://lists.idrc.ocadu.ca/mailman/listinfo/community

More information about the community mailing list