Background

I think this happened as a side-effect of having the screenreader skip the more button. We discussed and decided that it's more important to be able to reach every interactive element using the keyboard, than the possible annoyance or unnecessary interaction with it in a screenreader.

Requirements

• Re-introduce more button to the tab order (ok, if this mean that the screen reader 'sees' it again)