We're removing the left padding from the aside.localNav so that the text in the nav aligns properly on the left with other text elements in the header above. 

Isabella's testing also revealed some user issues with the Accordion Template on mobile. Users didn't understand that the arrow toggle button would open/close the accordion. We brainstormed and experimented a few possible solutions, including:

• Moving the toggle button to float left, as opposed to be farther away from the text on the right. 
• Removing the 'button styling' (gray background and border).
• Changing the orientation of the caret (facing right to start, and up when opened.)

Changing some of these ideas presented new problems; we are a bit special in the webspace with out UI here. One button toggles a dropdown, while clicking the text can lead the site visitor to another location altogether. Having the two items (toggle button and text) close together with two separate click actions feels wrong, and is not intuitive. But this was our original solve for what to do with two different click actions (one that opens a new link, the other that toggles the accordion).

Keeping the toggle on the right but removing the button styling then doesn't really indicate any sort of clickable action. Similarly, changing the orientation without moving the caret closer to the text showed little improvement on the UI.

We opted to leave this as-is for now, with bigger fish to fry in this sprint.