### Keyboard nav to and from QuickView panel
If a user navigates to an image and presses enter to open the QuickView panel, they would have to tab through all the remaining image results before getting to the QuickView aside element. When a user opens QuickView we should move focus to the panel, probably on the title link to the filepage. Similarly, when the user closes the panel, we should return them to the image they expanded.
### Keyboard nav within QuickView panel
None of the links in the QuickView component are reachable by keyboard. It's most important that the two buttons, "close" and "more details", are keyboard accessible. There are a few issues with the close button:
- It needs to be reachable by keyboard
- We should add (hidden) link text
- The focus styles could be more obvious
One way to tackle this would be to use the Button component and change the styles to match the current design. Similarly, the Button component probably shouldn't be used for the "more details" link, so we might consider a simple LinkButton component that produces a link styled like a button.
[ ] User can navigate to and from quickview panel via keyboard
[ ] All links in the quickview panel are accessible by keyboard navigation
[ ] Close button has visually-hidden label or title and visible focus styles
[ ] More Details button is a link styled like a button
### COVID-19 Deployment Criteria
[x] Can you roll back this change without lasting impact? - Yes
# A recovery plan is required as this will help identify our capacity for recovering from the failure
# THIS IS A KEY QUESTION, if you can’t answer it, you shouldn’t deploy
[x] Is specialized knowledge required to support this change in production? If so, are there multiple people with this knowledge? - No specialized knowledge needed
[x] Is there a way to increase confidence about the correctness of this change?
# Reviews (Design, Code, etc)
# Testing coverage (unit tests, integration tests)
# Manual testing (e.g. Beta, vagrant, docker)