marcysutton

React Combobox - Safari/VO Hacking

A Pen by Marcy Sutton on CodePen.

License.

marcysutton

NOTE: This is no longer an experiment! You can use the accessibility inspector in Chrome Devtools now, including a fantastic color contrast inspection tool. Read more: https://developers.google.com/web/updates/2018/01/devtools#a11y

---

Just like any good element inspector helps you debug styles, accessibility inspection in the browser can help you debug HTML and ARIA exposed for assistive technologies such as screen readers. There's a similar tool in Safari (and reportedly one in Edge) but I like the Chrome one best.

As an internal Chrome experiment, this tool differs from the Accessibility Developer Tools extension in that it has privileged Accessibility API access and reports more information as a result. You can still use the audit feature in the Chrome Accessibility Developer Tools, or you could use the aXe Chrome extension. :)

To enable the accessibility inspector in Chrome stable:

marcysutton

A snippet of an archived email conversation between accessibility professionals: George Zamfir, David Newton, Henri Helvetica, Monica Piotrowicz, Alice Boxhall and Tim Kadlec. I have noted who I thought was speaking, but it was hard to tell from the thread. Please comment if I can update the attribution!

##Glossary

• SR = Screen reader
• AT = Assistive technology
• a11y = Accessibility
• VO = Voiceover

##Transcript

marcysutton

A11y Slack Code of Conduct

Welcome!

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

The current admins are:

• Marcy Sutton (lead) - @marcysutton

marcysutton

Accessibility Testing for Engineers

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:

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

marcysutton

The goal of ngAria is to improve Angular's default accessibility by enabling common ARIA attributes that convey state or semantic information for assistive technologies used by persons with disabilities.

##Including ngAria

Using ngAria is as simple as requiring the ngAria module in your application. ngAria hooks into standard AngularJS directives and quietly injects accessibility support into your application at runtime.

marcysutton

Issue Description

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

How to reproduce / Current behavior

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

How to validate (Acceptance Criteria) / Expected behavior

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

Additional information

marcysutton

import {expect} from 'chai';
import App from '../app/components/App';

import a11yHelper from "./a11yHelper";

describe('Accessibility', function () {
  this.timeout(10000);

  it('Has no errors', function () {
    let config = {};

marcysutton

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" />

marcysutton

### 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: