Marcy Sutton-Todd marcysutton

Issue Description

// What is the nature of the issue? Which browser and/or Assistive Technology?

// Step-by-step instructions explaining how to reproduce the problem. Environment required, explicit identification of the component in question

// A set of assumptions which, when tested, verify that the accessibility requirement was met.

A dedicated accessibility space to ask questions, help other people figure stuff out or chat about accessibility in general.

The current admins are:

Ahoy, engineering team!

I'd like to share some best practices around accessibility testing: what to look for, how to test it, how to balance the work with other priorities.

The important things to remember are that:

Accessibility is about access for disabled people. Marginalizing their experience forever is continuous discrimination, full stop.
The best time to start is now. The earlier you address it the better, but you can always iterate as you move forward.

	module.exports = function (grunt) {
	'use strict'

	require('load-grunt-tasks')(grunt)

	grunt.initConfig({

	mochaTest: {
	test: {
	options: {

	import React from "react"
	import { Link } from "gatsby"

	import Layout from "../components/layout"
	import SEO from "../components/seo"
	import "./styles.scss"

	const SecondPage = () => (
	<Layout>
	<SEO title="Page two" />

	### Keybase proof

	I hereby claim:

	* I am marcysutton on github.
	* I am mazzafied (https://keybase.io/mazzafied) on keybase.
	* I have a public key ASAqE9vmg_MMg22bQ7M91ivpYu17k9Z3dVtG_6RLXUsn1Qo

	To claim this, I am signing this object: