“An accessible website does not rely on the mouse; it makes all functionality available from a keyboard." [1]
Much of the content found in the Navigation tab is primarily controlled by the program rather than the page creator (i.e., LibGuides controls the navigational elements rather than the librarian that adds content to the page). However, it is important to understand these elements so that you don't include objects on your page that are not accessible.
"Many people do not use the mouse and rely on the keyboard to interact with the Web. This requires keyboard access to all functionality, including form controls, input, and other user interface components."
Keyboard accessibility includes:
In terms of including alternate keyboard navigation, perhaps you found a great widget that allows users to drag a resource and drop it into a set of folders labeled "Primary" and "Secondary." You think it would be a fun way to teach your users about differentiating between the two sources. It sounds like a great idea! However, now imagine this same educational game being operated by a user "with no vision (who cannot use devices such as mice that require eye-hand coordination) as well as by [users] who must use alternate keyboards or input devices that act as keyboard emulators...[including] speech input software, sip-and-puff software, on-screen keyboards, scanning software and a variety of assistive technologies and alternate keyboards." [3]
As discussed early on in this guide, "The Web must be accessible to provide equal access and equal opportunity to people with diverse abilities. Indeed, the UN Convention on the Rights of Persons with Disabilities recognizes access to information and communications technologies, including the Web, as a basic human right." [1]
So, does that mean that you cannot use the drag-and-drop widget you found? Perhaps, but perhaps not. You may be so used to using a mouse that you never thought to see if the game could be operated using keyboard controls. And while drag-and-drop programs are sometimes difficult to code with accessibility practices, it can be done. Maybe the application supports "cut" and "paste" as an alternative. Maybe there are form controls available. And maybe there are no alternatives - in this case, you might consider not putting the widget on your page, finding an alternative game, or even contacting the widget's maker about options. Whatever the end result, "An accessible website does not rely on the mouse; it makes all functionality available from a keyboard." [1]