Web accessibility pass - Githubissues

Here's a really good checklist from Vox:

Designers

[x] Make sure there is enough contrast between text and its background color More Info
[x] Don't indicate important information using color alone More Info
[ ] Pair values of colors together (not only hues) to increase contrast More Info
[ ] Don't rely on sensory characteristics as the sole indicator for understanding and operating content More Info
[ ] Design focus states to help users navigate and understand where they are More Info
[ ] Help users understand inputs, and help them avoid and correct mistakes More Info
[x] Write good alt text for your images More Info
[x] If an experience cannot be made accessible, create another route for users to get that information More Info
[x] Be as consistent and clear as possible in layout and copy More Info

[x] Use the correct HTML element for your content More Info
[x] Support keyboard navigation More Info
[x] Understand and use HTML landmarks More Info
[x] Write good alt text for your images More Info
[x] Design focus states to help users navigate and understand where they are More Info
[x] Help users understand inputs, and help them avoid and correct mistakes More Info
[x] Use ARIA attributes when applicable More Info
[x] Give users a way to skip top level navigation to access main content More Info
[x] Make links descriptive More Info
[x] Avoid images and iconography in pseudo-elements More Info
[x] Make SVGs accessible to assistive technology More Info
[ ] Hide decorative elements from screen readers More Info
[ ] Create alternate routes for users to access information More Info
[ ] Links should be visually identifiable and have clear :focus and :active states More Info
[ ] HTML document should have a language attribute More Info

[ ] Familiarize yourself with the work associated with making content accessible More Info
[ ] Build in time for accessibility during project planning and sprint planning More Info
[ ] When sharing good work done by your team, praise efforts to increase accessibility More Info
[ ] The tools and products that you create should make accessibility easier to achieve More Info
[ ] Be an advocate for accessibility More Info

[ ] Run through each page with the WAVE Chrome Extension. More Info
[ ] Users should be able to navigate through content using their keyboard. More Info
[ ] Users should be able to navigate content using a screen reader. More Info
[ ] The general architecture and hierarchy of the content should make sense. More Info
[ ] Charts and images should all have alt-text so that users with screen readers or users on a slow connection will still be able to understand the images. More Info
[ ] Decorative images should not be visible to screen readers. More Info

[ ] Write good alt text for your images More Info
[ ] Editorial Engineers: think about how custom experiences can be made accessible More Info
[ ] Be as consistent and clear as possible More Info
[ ] Links should be descriptive More Info
[ ] Important information should not be conveyed through images, color, or sensory characteristics alone More Info