Becky Gibson

Apologies for the delay in responding. We don't have any specific examples from other Web API specifications but the APA working group agreed upon the following suggestion for an accessibility...

Currently testing 2E456D and 406098 as foreground and background for ballard and Vancouver. This puts them at a ratio 0f 4.67. Using DADFE1 in place of 406098 increases the ration...

Here are the Web Content Accessibility Guidelines (WCAG) 2.1: https://www.w3.org/TR/WCAG21/. The specific success criterion is: https://www.w3.org/TR/WCAG21/#focus-visible. The keyboard only user needs to know where focus is located. The arrows don't...

So, this should be relatively easy to fix. When the menu is not visible on the screen, set the < nav class="slide-menu slide-menu--left active"> to display:none.This will prevent the tab...

Okay, perhaps not so easy to fix. I added display:none via the developer tools and was still seeing focus getting trapped in the menu area. But, that is a start....

Thanks for your comment. We agree that providing one or more accessible routes through a process is important. We discussed this briefly and agreed that it was beyond the scope...