A11y: keyboard navigation isn't working as expected

[pedrowindisch]

Description

The keyboard navigation isn't working as expected.

Current behavior

After pressing tab, the page focus on the search field. The user clicks enter and then the app starts fetching the articles. The first article is focused after pressing tab, but if the user presses it again, the app just opens the article up, which is not the correct behavior. I think this issue is better explained with a visual demonstration, so here's a short GIF I made showing what's happening right now.

This is happening because each result has an onKeyDown listener, which also captures the tab key.

Expected behavior

After the results are fetched and rendered, the user should be able to navigate through them by clicking tab or the arrow down key. If the user wants to open an article, he then would click enter. You can find more information about keyboard accessibility here.