Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Move delay option to before feed content to support keyboard users #877
For a keyboard-only user, there is no way to get to the
A screen reader user can jump to just form controls, but each example in the feed has a form control (the
Steps to Reproduce
As noted on the documentation page, this example is an early draft that still needs work.
The design of the display page is not complete. It needs content both before and after the feed to illustrate how to nest feeds in a page.
There is a keyboard feature for moving past the feed. On this example, it is ctrl+end. See the example documentation page. One problem, of course, is that there is nothing present in the experience that helps the user know that.
Before we decide whether to move the delay selector, I think we should first discuss what else to include in the design of the feed display page to make it somewhat realistic as well as how to reveal the existing keyboard affordences. Once we decide what else to add to the page, we can decide where the delay selector best fits.
One thing we definitely want to include is the standard set of navigation links for example pages as well as a link to the example documentation page.
Agreed. However, I am aware of a reference internal to an organization that links to the example, not the documentation. With no warnings on the example, nor link to the documentation, these users are unaware of the "needs work" or "draft" status of the example.
And with people linking directly to the example, they will not discover that.
So if understanding these points is predicated on the documentation page, then how about linking the documentation page as the first tab-stop on the example page?
Can you do that more easily than moving the