starts automated accessibility steps: loads @axe-core/react on next dev, enables eslint-plugin-jsx-a11y on strict

[mattxwang]

This PR does a couple of things:

1. installs and enables eslint-plugin-jsx-a11y, and turns it on with strict mode
   • this triggers on the navbar improperly using the <label> element, which is a valid concern. reworking it involves changing the DOM structure of the navbar, which in turn breaks the CSS - I'd like to table fixing this until we rework the navbar
   • this also triggers on next's <Link><a></a></Link> pattern, which is realistically a false-positive. Unfortunately, there's no great solution to this, and as such I've temporarily disabled the rule for <Link>; see the comments in the eslint config for more info
2. installs and enables @axe-core/react, which logs accessibility issues to the console in dev
   • there are a ton of issues to resolve. so, I'll scope that out for another PR instead.

Something that's still left to be desired is to get aXe's level of accessibility specificity, but getting it as a CI action (like eslint-plugin-jsx-a11y) - will figure that out soon!

Part of #218.

[evanzhong]

lgtm.

Small thing:

• this triggers on the navbar improperly using the element, which is a valid concern. reworking it involves changing the DOM structure of the navbar, which in turn breaks the CSS

  • I think tabling this rather large change is the right call here. If you haven't already, could you create a new issue outlining a navbar refactor and reference this PR.

[mattxwang]

Huh, having some problems w/ the merge - let me roll this back.

[mattxwang]

I think tabling this rather large change is the right call here. If you haven't already, could you create a new issue outlining a navbar refactor and reference this PR.

Yup, will do!