►
Description
Presented by Stephanie Slattery, Clique Studios.
Roughly 1 in 5 people in America live with a disability and legal actions against inaccessible sites are becoming more and more common. It would be irresponsible to ignore the needs of all our users when developing for the web, so why don't we design accessible sites to begin with? In this talk, I'll explain the basics of web accessibility, including the guidelines you should be following, the adaptive technologies commonly in use, and help you better advocate for users with disabilities in your work.
About GitHub Universe:
GitHub Universe is a two-day conference dedicated to the creativity and curiosity of the largest software community in the world. Sessions cover topics from team culture to open source software across industries and technologies.
For more information on GitHub Universe, check the website:
https://githubuniverse.com
A
Great
okay,
hello,
everybody
and
welcome
to
accessibility.
It's
more
than
just
screen
readers.
My
name
is
Stephanie
Slattery
and
my
twitter
handle
is
sublime
March
if
you
feel
it
in
your
heart
to
live.
Tweet
me
I'm,
a
front-end
engineer
and
I
specialize
in
accessibility,
I've,
led
accessibility,
audits
and
fixes
for
all
sorts
of
clients
and
I,
give
talks
and
workshops
about
accessibility
to
lovely
people
like
yourselves
across
the
United
States
I
work
for
a
place
called
clicks
to
ACOG.
Oh,
we
are
a
design
and
Technology
company.
A
We
work
with
ambitious
teams
to
create
industry-leading
digital
experiences
and
our
philosophy
from
day
one
has
always
been
really
simple:
just
build
something
we're
based.
Our
business
is
based
on
three
things
and
just
those
three
things:
quality,
education
and
people,
and
it
click.
We
place
a
strong
emphasis
on
diversity
and
inclusion,
and
that's
why
I'm
able
to
speak
to
you
today
about
accessibility,
let's
get
started.
So
what
is?
Accessibility?
I
have
a
great
definition
for
you.
A
It's
the
design
of
products,
devices,
services
or
environments
for
people
who
experience
disabilities
and
it's
the
practice
of
removing
barriers
that
might
prevent
people
with
disabilities
from
accessing
all
of
those
things.
Technology
really
shouldn't
be
a
barrier
to
people.
It
should
make
people's
lives
even
easier.
I
can't
imagine
that
there
are
many
of
us
that
would
say.
I
write
my
code
to
make
someone's
life
harder
to
make
someone's
day
awful.
Maybe
you
do
that?
A
I,
don't
know
your
life,
but
should
be
trying
to
make
people's
lives
easier
with
the
things
we
make
and
I've
found
in
my
work
with
accessibility
that
it's
easiest
to
understand
what
accessibility
is
and
why
we
care
about
it
by
talking
about
disability
first,
so
there
are
a
few
general
categories
of
disability
to
think
about
when
we're
designing
for
the
web
or
really
any
technology.
I'm
gonna
give
you
a
list,
but
it's
important
to
think
that
this
is
not
an
exhaustive
list.
A
It's
just
a
starting
point
for
understanding
and
also
these
disabilities
could
be
the
result
of
disease
trauma
or
some
congenital
issue.
So
the
first
category
of
disability
is
probably
the
first
one.
You
might
think
of
when
you
think
accessibility,
when
you
think
designing
a
website
to
be
accessible.
That's
visual
disability.
This
could
be
complete
or
partial
blindness,
low
vision,
color
blindness
things
like
that.
The
next
is
hearing.
So
this
includes
deafness
folks,
who
are
hard
of
hearing
things
like
hyperacusis,
which
is
the
sensitivity
to
certain
frequencies
and
volume
ranges
of
sound
next
is
motor
disability.
A
So
this
includes
things
like
paralysis,
cerebral
palsy,
carpal,
toll
syndrome,
repetitive
strain,
and
things
like
dyspraxia
affects
the
planning
of
how
you
coordinate
your
movements.
When
you
move
your
body
in
some
way
in
general,
these
can
cause
an
inability
to
use
a
mouse,
a
slower
response
time
than
somebody
with
a
disability
or
limited
fine
motor
control.
A
So
those
are
the
motor
disabilities
and
the
last
one
is
kind
of
disability
include
conditions
both
that
alter
your
ignition
head
injury
or
a
development
ability
or
autism
and
learning
disabilities
like
dyslexia,
dyscalculia
or
ADHD
a
lot
of
the
times.
These
can
cause
things
like
a
distractibility
or
an
inability
to
remember
or
focus
on
large
amounts
of
information,
and
these
are
categories
of
disability
that
people
don't
always
think
about.
A
When
they're
thinking
about
accessibility
but
are
just
as
important
and
here's
the
kicker
all
of
these
people
use
technology,
they
use
the
Internet
whoa
right
whenever
I
give
a
talk
like
this,
there's
always
somebody
up
to
you
after
who
is
shocked
that
there's
somebody
who's
paralyzed
from
the
neck
down
who's
using
their
website,
they're
surprised
people
who
are
blind
use
their
website.
All
of
these
folks
use
technology
and
it's
helped
in
part
by
assistive
technology,
so
heard
the
title
of
my
talk.
It's
not
just
screen
readers,
but
a
major
assistive
tech
is
a
screen
reader.
A
Now
these
are
even
cooler
than
you
might
think.
They
don't
just
read
the
text
on
a
website
to
the
user.
They
also
tell
the
user
information
about
how
the
document
of
the
site
is
structured,
so
the
accordion-
and
it
opens
up
this
pitch-
or
this
is
a
link
and
it'll
go
to
this
place.
There's
a
ton
of
detail
that
a
screen
reader
can
give
a
user.
It's
awesome.
A
Another
kind
of
assistive
tech
is
a
magnifier,
so
this
can
either
be
hardware,
but
like
a
physical
magnifier,
you
put
over
a
screen
or
a
software,
magnifier
I'm
sure
I'm,
not
the
only
person
that
has
accidentally
zoomed
on
a
browser
and
everything's
gotten
huge
and
giant
letters.
One
example
of
a
four
magnifier
other
assistive
tech
includes
large
print
and
tactile
keyboards,
so
these
keyboard
keys
will
be
much
larger
than
an
average
keyboard
key
or
will
have
ways
text
or
other
indicators
that
make
it
easier
to
either
see
the
keyboard
or
feel
the
key.
A
You
can
hit
them
correctly.
Other
assistive
tech,
our
eye
gaze
and
head
mouse
systems.
These
are
so
cool.
These
are
devices
that
track
the
way
that
the
users
eye
moves
where
it's
pointing
looking
at
a
screen
and
then
enables
the
user
to
click
and
move
a
mouse
and
whatever
they
need
to
do
just
by
moving
their
eyes
awesome.
A
Another
assistive
tech
is
one
that
the
folks
in
the
room
and
if
you're,
watching
this
recording,
you
can
see
this
right
now
speech
recognition,
either
an
automated
system
or
a
person
who
is
physically
typing.
What's
being
said,
you
also
have
this
if
you
have
most
smartphones
on
your
phone,
if
you're
talking
miss
Siri,
if
you're
talking
to
Google
it's
recognizing
your
voice
and
interpreting
that
command
and
that's
assistive
technology.
A
This
also
include
closed
captions,
which
again
we
have
awesome
speech.
Recognition
powered
closed
captions
that
you
might
be
using
right
now,
and
these
might
also
just
be
written
by
a
person
as
part
of
a
transcript
when
a
video
is
put
on
awesome,
two,
more
examples
that
I
have
pictures
for
you,
so
you
can
understand
a
bit
better.
This
is
something
called
a
sip
and
puff
device.
A
A
Another
one
is
a
head
mouse
or
a
head
button
system,
so
you
can
see
there's
a
little
sort
of
trigger
like
button
next
to
his
head,
he's
able
to
just
move
his
head
directly
against
that
button
in
different
patterns,
different
strengths
as
a
way
to
give
commands
to
a
computer
awesome
right,
so
many
different,
assistive
technologies
that
people
are
using
right
now
to
use
your
website.
Your
technology,
you've
created
cool,
ok,
but
why
does
this
matter?
So
there
are
some
people
that
use
assistive
tech.
A
Why
do
we
care
well
in
the
United
States,
one
in
five
Americans
have
some
form
of
disability
that
significantly
impacts
their
life.
This
is
as
of
2010
according
to
the
US
Census
Bureau,
and
you
might
be
thinking
one
in
five
I'll
represent
that
in
a
different
way
in
the
United
States
alone.
That's
fifty
six
point:
seven
million
people
have
a
disability
of
some
kind
or
another,
and
this
is
even
more,
of
course,
around
the
globe.
A
According
to
the
World
Health
Organization
in
2011,
about
15%
of
the
world's
population
has
a
significant
disability
and
that's
about
785
million
people
worldwide.
A
lot
of
folks.
All
of
these
people
in
the
United
States
about
1
in
10
Americans,
about
half
of
folks
with
a
significant
disability,
have
a
disability
that
impacts
their
computer
use
directly.
They
might
use
any
of
those
different
assistive
technologies
we
mentioned
before,
but
here's
the
thing,
accessibility
and
designing
your
product
or
service
in
an
accessible
way
helps
everybody
all
of
those
different
categories
of
disability.
A
Here's
a
traditional
example
in
meatspace
of
a
curb
cut
will
sometimes
call
this
idea
of
designing
something
excessively
that
helps
everybody
a
curb
cut
effect.
So
in
this
image
we
have
what
looks
to
be
a
curb
up
against
a
street.
We
can
see
a
pedestrian
walkway
and
in
the
space
going
down
to
that
walkway,
the
curb
sort
of
indents
it
makes
a
little
ramp
from
the
sidewalk
down
onto
the
road.
It's
called
a
curb
cut
here
in
the
United
States,
and
this,
of
course
helps
folks
with
disabilities.
A
So
folks,
who
might
use
a
wheelchair
to
get
down
from
the
curb
onto
the
road,
but
this
also
helps
people,
for
example,
who
might
be
pushing
a
cart
of
groceries
or
someone
pushing
a
stroller
with
a
baby
in
it.
This
helps
everybody
be
more
mobile.
It
makes
everybody's
lives
easier
awesome
in
the
digital
space.
A
Here's
the
other
thing,
though,
not
only
do
these
adaptations
help
everyone,
it's
important
to
remember
that
we
are
all
just
temporarily
abled
disease,
injury
and
age
can
all
cause
us
to
gain
a
disability
of
one
kind
or
another,
unlike
a
lot
of
different
kinds
of
marginalization
that
you
might
have.
This
is
something
that
anybody
could
gain
at
any
time
for
a
variety
of
reasons.
Okay,
I
think
I've
convinced
you
that
this
impacts
a
lot
of
people.
It
might
even
impact
you,
oh
my
gosh,
so
why
do
we
make
something
accessible?
A
There
are
several
reasons,
all
of
which
are
valid,
they're,
just
more
or
less
altruistic
and
one
another.
Let's
say
so.
The
first
reason
to
me,
the
one
that's
most
important,
is
to
improve
the
lives
of
people
with
disabilities.
I
believe
that
we
have
an
ethical
duty
to
help
all
people
who
use
what
we're
going
to
make
I
believe
that
we
are
responsible
for
what
we
create,
regardless
of
what
you
make
if
it's
a
website
or
a
book
or
a
painting,
whatever
you
make.
A
If
you
make
something
for
another
human
being
to
interact
with
you're
responsible
for
making
sure
that
those
other
humans
can
use
that
thing
that
you've
made
just
that
simple.
Another
reason
why
we
build
things
excessively
is
to
capitalise
on
a
wider
audience
or
consumer
base.
So,
as
I
mentioned
before,
it's
700
something
million
people
around
the
world,
have
a
disability,
I,
really
can't
think
of
any
ethical
or
economic
argument
that
you
could
make
for
potentially
excluding
that
many
people
from
using
your
product.
A
You
wouldn't
design
a
website
to
not
work
on
20%
of
browsers
that
your
users
use.
So
why
would
you
design
your
website
to
not
work
for
the
20%
of
Americans
that
have
a
disability
right?
Here's
that
thing
those
1
in
5
Americans
in
the
United
States
alone
control,
one
hundred
and
seventy
five
billion
dollars
in
discretionary
income.
A
Now
we
might
debate
whether
it's
you
know
the
best
idea
to
make
something
just
to
get
money,
but
that's
a
lot
of
money.
That's
a
billion
billion
with
a
B
right.
You
want
a
piece
of
that
pie
if
you're
making
something
as
a
way
to
get
money.
You
want
to
receive
part
of
this
funding
third
reason
for
building
something
excessively,
it's
the
law
to
obligation
way
right.
You
might
build
sensibly
to
avoid
lawsuits
or
the
bad
press
you
get
because
you
were
sued
alright,
so
in
the
United
States
and
around
the
world.
A
A
Now
the
threat
of
being
sued
can
cause
a
business
to
decide
to
fix
their
accessibility
problems.
If
some
group
identifies
that
your
product
has
an
accessibility
issue
and
they
threaten
to
sue
you
that
might
be
enough
to
make
you
go
whoa,
never
mind
we'll
fix
it.
We
are
so
sorry,
please
don't
sue
us
and
also,
if
that's
not
enough
for
you
frequently,
the
terms
of
a
settlement
for
a
lawsuit
can
require
you
to
be
accessible
hurray.
It's
the
law.
I'm
gonna
go
over
two
major
laws
in
the
United
States
about
accessibility
and
technology.
A
There
are,
of
course,
a
ton
of
different
laws
around
the
globe
that
vary
in
all
sorts
of
different
ways:
I'm
based
in
the
US.
This
is
what
I
know,
but
it
should
give
you
a
basis
for
understanding
for
how
things
might
work
in
your
country
if
you're
not
from
the
US.
So
the
first
one
is
called
the
Rehabilitation
Act
of
1973.
You
can
see
in
the
background
here.
There
are
some
folks
who
are
part
of
that
disability
rights,
movement
fighting
for
the
passage
of
this
law
in
the
70s.
A
This
law
prohibits
discrimination
on
the
basis
of
disability
in
programs
that
are
run
by
the
federal
government
or
that
receive
financial
assistance
from
the
federal
government
or
in
federal
employment
or
in
the
employment
practices
of
federal
contractors.
In
1998,
Congress
amended
this
act
with
something
you
may
have
heard
of
called
section
508,
and
that
requires
federal
agencies
to
provide
accessible,
electronic
resources
and
information
tech
to
people
with
disabilities.
A
Now
you
heard
me
say
the
word
federal
government
a
lot
in
that
description
right
currently,
the
rehab
Act
doesn't
require
private
websites
that
don't
receive
government
funding
that
have
nothing
to
do
with
the
government
to
be
accessible,
although
this
law
is
evolving
as
cases
go
on,
but
if
you
work
for
a
company
that
does
work
for
the
federal
government
or
maybe
the
United
States
federal
government
itself,
I'm
sure
you
are
very
familiar
with
this
law.
The
next
probably
more
familiar
a
lot
of
most
folks
about
accessibility
in
the
u.s.
A
is
called
the
Americans
with
Disabilities
Act
or
the
ADA.
A
folks
will
call
it.
This
was
passed
in
90.
This
is
a
labor
law.
It
prohibits
discrimination
on
the
basis
of
disability
and
it
created
accessibility
requirements
for
public
services
and
accommodations
in
the
US.
Here's
the
thing,
though
you
see
the
year
1990,
that's
when
it
was
passed.
As
a
result,
the
ATA
doesn't
directly
mention
the
web
or
the
internet
right,
but
it
works
to
ensure
that
people
with
disabilities
have
equal
opportunities
in
in
all
venues.
A
Now
the
Department
of
Justice
was
at
least
developing
regulations
that
address
web
accessibility.
Although
there
are
several
notable
cases,
we
talked
about
lawsuits
earlier,
several
notable
cases
regarding
the
ADA,
a
that
have
made
it
pretty
clear
that
the
ADA
is
Authority
pertains
to
websites,
not
just
physical
things,
and
it's
clear
that
EA
pertains
to
businesses
that
only
exist
online,
that
don't
have
a
physical
presence
and,
as
I
mentioned
before,
there
are
a
lot
of
international
laws.
Okay,
so
this
is
all
well
and
good.
A
We
understand
that
people
have
disabilities,
they
use
assistive
tech
and
apparently
I'm
legally
required
to
make
my
website
accessible.
Oh,
no.
How
do
I
know
if
what
I'm
making
is
accessible?
This
is
a
question.
I
get
a
lot
even
from
folks
who
are
motivated
to
build
an
accessible
technology.
They
don't
know
where
to
start
the
best
starting
place.
The
best
advice
I
can
give
you
to
build
something
accessible
is
to
listen
to
people
with
disabilities.
This
both
means
involving
people
with
disabilities
in
the
creation
of
your
technology,
should
have
folks
on
your
team.
A
You
should
represent
a
diverse
worldview
on
your
team,
including
folks
with
disabilities.
You
should
also
listen
to
the
voices
of
people
with
disabilities
who
will
use
your
technology,
so
this
both
means
and
user
testing
before
you
launch,
as
well
as
in
the
initial
creation
and
design
of
what
you're
making
involve
people
with
disabilities.
A
Also
I
recommend
that
you
follow
best
practices.
So
we
talked
about
those
laws,
some
of
them
around
the
globe
mentioned
very
specific
requirements,
they're
also
guidelines
that
can
help
you
evaluate
what
you're
creating
and
there
are
a
ton
of
different
sets
of
guidelines
and
different
resources.
You
can
use
I
recommend
picking
the
one
that's
best
suited
to
what
you're
creating
and
I'll
go
over
two
right
now.
A
The
one
that
I
will
primarily
discuss
is
the
one
that
web
developers
use,
but
it's
also
a
good
framework
for
understanding,
regardless
of
what
you're
writing
code
for
not
just
the
web,
and
it's
called
the
web
content
accessibility
guidelines.
It's
also
called
the
what
CAG
or
the
Wu
CAG
it's
kind
of
hard
to
pronounce
as
an
acronym.
What
CAG
is
what
we
go
with
it's
currently
in
versions?
Oh,
so
this
was
created
by
the
World
Wide
Web
Consortium
or
the
w3c
they're.
A
The
governing
body
of
the
web
they're,
the
folks
that
create
guidelines
like
this
that
regulate
how
the
internet,
how
the
web
should
work
and
this
2.0
iteration
was
published
in
December
of
2008.
So
that's
a
bit
before
mobile
web
browsers
were
very
common.
That's
a
bit
before
touchscreens
were
very
common.
So
keep
that
in
mind.
When
you
read
this,
there
is
currently
a
working
draft
of
the
wicked
2.1
out.
It
was
released
last
month
if
you're,
an
accessibility
nerd.
You
should
read
it.
If
you're,
not
an
accessibility
nerd,
you
should
read
it.
A
Just
everybody
read
it
they're,
seeking
public
comment
on
their
ideas,
so
tell
them
what
you
think
about
it.
These
guidelines
are
the
basis
for
most
web
accessibility
laws
around
the
world,
and
some
countries
even
directly
include
the
Wyck
AG
in
their
laws
as
a
requirement
in
the
Wyck
AG.
We
have
four
principles
that
encompass
a
ton
of
guidelines
for
web
accessibility
and
under
those
we
have
a
lot
of
sub
guidelines
and
test
criteria
and
detailed
things
like
that.
There
are
also
three
different
conformance
levels
within
the
width
tag.
A
Essentially,
they
are
more
or
less
strict
than
one
another
and,
if
you're
trying
to
decide
which
conformance
level
to
go
with
I
strongly
and
you
to
consult
with
a
legal
team
that
will
tell
you
what's
best
for
you,
I'll
get
the
question
a
lot
of
stéphanie,
which
one
do
I
just
pick,
one
for
me
and
I'm
happy
to
make
a
suggestion,
but
please
do
not
take
what
I
am
saying
is
legal
advice?
I'm,
not
a
lawyer.
Thank
you,
okay.
A
So
let's
talk
about
those
four
principles
of
the
wick
egg
and
again
these
are
large
principles
with
lots
of
guidelines
underneath
them.
The
first
is
perceivable.
This
require
your
sight,
be
available
senses,
either
through
a
browser
or
some
form
of
assistive
technology
which
we
discussed
earlier.
This
information,
content
and
user
interface
components
of
the
website
have
to
be
presentable
to
the
users
in
a
way
that
they
can
perceive.
So
this
includes
guidelines
for
things
like
captions
text,
alternatives
for
image
or
any
non
text,
content
and
different
presentations
of
your
contact.
A
It
needs
to
be
presented
in
multiple
ways,
so
different
assistive
tech
can
receive
it.
Next
is
operable.
This
requires
that
your
users
can
interact
with
all
the
different
controls
and
interactive
elements
of
your
website,
either
using
a
mouse,
a
keyboard
or
one
of
those
assistive
devices
we
mentioned.
This
includes
guidelines
for
timing
on
your
website.
So
if
you
have
like
a
cart,
timer
ticking
down,
this
governs
how
that
can
be
used.
This
also
gotta
includes
guidelines
for
navigation,
keyboard,
navigation
and
different
techniques,
for
preventing
seizures
that
can
be
induced
by
flashing
images
or
colors.
A
Cert
is
understandable.
This
requires
that
your
content
is
clear
and
it
limits
confusion
and
ambiguity.
It
includes
guidelines
for
helping
users
avoid
making
mistakes
or
coming
back
from
a
mistake
when
they
make
it.
So
things
like
error
messages
on
a
form
both
need
to
be
clear,
and
it
needs
to
be
easy
to
fix
the
mistake.
This
also
includes
guidelines
about
making
your
text
readable,
both
visually
readable,
as
well
as
having
the
text
be
possible
and
understandable.
This
also
includes
making
your
content
operate
in
predictable
ways.
A
You
can't
do
strange,
unpredictable,
surprising
things
with
your
users,
a
button
that
says
open,
accordion
needs
to
actually
open
an
accordion
and
not
do
something
else
understandable
and
the
last
is
robust.
This
means
that
your
site
needs
to
work
on
a
wide
range
of
technologies,
both
different
browsers,
different
kinds
of
assistive
tech,
different
operating
systems
and
not
just
the
newest
shiniest
version
of
the
OS
or
a
browser
it
needs
to
work.
Also
I'm
like
Internet
Explorer
10.
It
needs
to
be
accessible
there
too
right.
This
includes
guidelines
about
having
consistently
possible
HTML.
A
Essentially,
you
need
to
follow
the
rules
of
how
HTML
have
to
be
constructed
and
also
having
clear
names,
roles,
values
in
your
code.
This
is
a
lot
more
technical
than
some
of
the
other
guidelines
can
be
so
I
recommend
reading
it
for
yourself,
okay,
so
that's
the
wick
hag
hooray
you're
all
going
to
go
home
and
read
the
hundreds
of
pages
of
the
wick
egg.
Yes
go
you!
The
other
important
set
of
guidelines
or
framework
that
we
talk
about
is
the
open
accessibility
framework
or
the
Oh
AF.
A
Now
this
is
not
so
much
about,
but
in
general,
provides
an
outline
of
steps
that
have
to
be
in
place
for
any
computing
platform
to
be
considered
accessible.
So
this
includes
desktop
and
mobile
operating
systems.
This
includes
web
applications
and
mobile
platforms.
Now
the
steps
that
are
in
this
framework
are
analogous
to
those
necessary
to
make
a
physical
environment
accessible
so
by
following
these
you're.
Also
getting
an
idea
of
what
say
a
civil
engineer,
making
a
curb
cut
has
to
do
to
make
their
product
accessible.
A
There's
two
categories
for
these
steps:
the
first
one
is
creation,
so
the
creation
steps
define
the
precursors
and
building
blocks
required
for
technology
developers
to
create
accessible
applications
and
products.
This
includes
defining
what
accessibility
means
for
the
intended
use
of
your
platform.
What
is
accessibility
even
mean
in
this
case?
You
also
have
to
determine
stock
user
interface
elements
and
components,
so
you
can
have
cohesive
and
predictable
meaning
across
the
technology
and
providing
authoring
tools
that
support
accessibility.
A
So
if
you,
for
example,
are
creating
an
operating
system,
if
you
are
including
authoring
tools
for
P
to
make
an
application
in
your
those
tools
need
to
support
accessibility.
Also,
the
next
section
of
steps
in
the
O
AF
is
use,
so
the
you
steps
describe
what's
necessary
in
a
computing
environment
in
which
those
accessible
applications
will
run.
So
this
includes
providing
a
platform
supports,
providing
accessible
application
software
and
providing
assistive
technologies,
so
you
might
think
about
your
desktop
operating
system.
A
Not
only
could
you
download
and
install
some
assistive
tech,
but
there
are
also
things
like
text
screen
readers
or
magnifiers
built
into
the
operating
system,
and
that's
because
they
followed
some
of
the
guidelines
for
the
Oh
F
oK.
We've
got
two
different
sets
of
guidelines.
We
have
some
homework
to
go
home
and
read
these
and
know
what
they
mean
you
have
homework.
You
have
to
understand
this,
but
here's.
The
thing
accessibility
is
more
than
just
these
guidelines.
A
You
could
make
a
beautiful
website
and
go
through
every
step
of
the
web
content,
accessibility
guidelines
and
still
have
built
something
that
is
inaccessible
to
some
of
your
users.
These
guidelines
are
tools.
They're,
not
solutions
so,
as
I
mentioned
before,
the
current
version
of
the
book
tag
is
from
back
in
2008,
there's
a
lot
of
things
that
doesn't
cover
it's
a
set
of
guidelines
from
a
specific
period
of
time.
These
guidelines
help
us
determine
if
a
page
is
inaccessible.
So
it's
very
easy
to
tell
oh
I
failed
such-and-such
guideline
within
the
Wyck
AG.
A
There
might
be
accessibility
issues
for
some
of
my
users,
but
these
guidelines
can't
tell
us
for
certain
if
a
page
is
accessible,
how
do
we
know
if
it's
accessible?
Why
we
send
to
people
with
disabilities?
That's
a
callback!
Yes,
it's
important
to
listen
to
people
with
disabilities
to
determine
if
your
technology
is
truly
accessible.
It's
important
to
involve
people
with
disabilities
in
the
creation
and
use
of
your
tech
awesome.
Okay,
so
we
care
about
accessibility.
We
have
built
something
excessively.
A
We
know
how
to
check
it
hooray,
but
you
might
be
thinking
stuff,
I'm,
a
product
manager
or
Stephanie
I'm
a
designer.
This
is
cool,
but
isn't
this
all
something
that
a
front-end
engineer
does
I?
Don't
have
to
worry
about
this,
not
true.
I
say
that
everybody
should
be
advocating
for
accessibility
in
whatever
they're
creating,
and
you
need
to
help
better
advocate
for
people
with
disabilities
in
your
work,
whatever
it
is
that
you
do,
how
do
you
do
that?
First,
you
collect
baseline
information.
A
A
Part
of
that
is
because
our
technology
is
not
yet
perfect
right,
but
also
because,
if
you've
constructed
say
in
a
website,
if
you've
constructed
your
HTML,
so
strangely
and
so
weirdly,
this
automated
tool
doesn't
understand
what
you've
done
and
can't
tell
you
that
you've
done
it
wrong.
For
example,
there
are
guidelines
within
the
mechag
about
headers
and
how
they
have
to
be
constructed.
Your
heading
tags
have
to
go
in
order.
You
can't
say
skip
one.
You
can't
go
heading
level,
one
having
level
three
heading
level.
A
Four,
there
have
to
be
a
heading
level
two
in
there
right,
and
these
validator
tools
will
be
so
helpful
if
you've
tagged
everything
as
a
heading
tag
right.
But
if
you
just
have
a
big
blob
of
text
like
a
paragraph
tag
that
you
typed
everything
into
a
validator
tool
might
not
realize
that
that's
supposed
to
be
a
heading
and
that
you've
broken
an
accessibility
rule
so
be
careful.
I
also
have
a
human
check
this
over
okay,
so
you've
gathered
baseline
information.
A
What
next
you
can
gather,
support
at
your
organization,
identify
stakeholders
in
your
business
and
convince
them
of
the
business
value
of
accessibility
and
I
can
see
some
of
you
rolling
your
eyes,
because
we,
this
is
really
hard.
This
is
a
hard
problem,
may
be
harder
than
implementing.
Accessibility
on
your
site
is
convincing
the
people
who
are
in
charge
that
accessibility
is
important.
How
do
you
do
that?
Well,
one!
You
could
link
them
to
this
video.
Obviously
right
now
you
can
talk
about
both.
A
You
have
an
ethical
duty
to
do
this
and
for
some
people,
that's
enough
to
point
out
that
you
have
an
ethical
responsibility
cool.
You
could
also
talk
about
financial
incentives,
getting
some
more
money
because
alienated
part
of
your
user
base.
You
can
talk
about
potential
threats
of
lawsuits.
You
can
give
them
awesome.
A
Well,
you
know
the
other
people
who
built
my
website
if
I
had
just
had
them,
do
this
right,
the
first
time,
how
much
would
it
have
been,
and
the
answer
is
so
much
less
money
than
it
is
to
have
me
fix
it
now
right,
it's
also
a
lot
cheaper
than
getting
sued
most
of
the
time,
it's
so
much
better
to
be
proactively
accessible
and
that's
a
conversation
that
you
should
have
with
the
stakeholders
in
your
product.
Next,
you
should
define
a
standard,
so
define
your
internal
standard
for
accessibility.
That
might
be
oh
well.
A
We
want
to
follow
the
what
CAG
we
want
conformance
level
double-a
done,
it
might
be
more
complicated
than
that,
whatever
is
appropriate
for
your
product
and
then
train
people
on
this
and
don't
just
train
your
front-end
engineers.
Maybe
not
everybody
needs
the
details
of
how
all
the
code
works,
but
everybody
involved
in
your
product
should
understand
what
accessibility
means
at
your
company.
A
Next
and
last,
you
need
to
monitor
conformance
for
accessibility.
I
have
definitely
had
clients
before
where
they
build
a
beautiful,
accessible
website
and
it's
gorgeous
and
compliant
and
I
love
it
and
then
they'll
give
it
off
to
their
support
devs
and
they
forget
about
the
world
word
accessible
entirely.
It's
important
to
be
monitoring
this
as
you
go
on.
You
can
either
do
this
by
scheduling,
regular
audits
of
your
tech.
You
could
also
use
an
automated
tool.
A
There
are
several
ones
that
are
awesome,
that
you
can
even
tie
into
your
gated
pull
requests
and
run
a
check
to
see.
Did
this
destroy
accessibility
in
some
way?
It's
so
fix
it
and
then
we'll
merge
the
code.
It's
really
cool,
but
you
have
to
monitor
your
conformance
for
accessibility
as
your
site
or
your
technology
exists.
A
If
you
have
anything
short
of
a
beautiful
cross-functional
team
that
meets
regularly,
you
can
do
better
than
you're
doing
right
now.
You
owe
it
to
your
users
to
do
better
start
an
initiative
within
your
company
or
your
open
source
project
to
care
about
accessibility
or
if
there
is
an
initiative,
already
join
a
small
one.
A
Even
if
you're,
not
a
person
code,
you
can
still
advocate
for
accessibility.
The
thing
I
believe
that
you
can
do
this
I
know
that
sounds
pissy
hooray.
You
can
do
it
right,
but
here's
the
thing
people
can
be
intimidated
by
accessibility.
It
seems
tricky,
there's
so
many
guidelines
to
understand
and
all
these
complicated
things
and
I
might
get
sued.
If
I
do
it
wrong
and
it
seems
overwhelming
right,
but
accessibility
is
a
solvable
problem,
something
that,
in
my
opinion,
in
the
grand
scheme
of
coding
for
a
website
is
relatively
easy.
A
Once
you
have
support
and
time
you
can
make
your
site
accessible,
you
can
improve
it.
There
are
a
ton
of
resources
out
there
and
compared
to
those
other
problems
in
code.
It's
not
that
hard
and
hopefully,
somewhat
inspiring
to
you.
The
image
on
this
slide
is
folks
that
are
a
part
of
the
disability
rights
movement.
I
believe
this
was
protests
around
in
support
of
the
ADA
a
they're
carrying
a
banner.
These
folks
are
in
wheelchairs,
carrying
a
banner
that
says.
Injustice
anywhere
is
a
threat
to
justice
everywhere,
which
is
a
quote
attributed
to
MLK.
A
You
can
do
this.
It
is
important
to
your
users.
It
is
important
because
you
owe
this
to
them.
As
I
said
before,
we
are
all
responsible
for
improving
the
lives
of
people
who
use
our
technology,
and
accessibility
is
one
of
the
ways
we
can
achieve.
That
and
I
hope
that,
by
sitting
through
this
talk,
you
understand
that
accessibility
is
more
than
just
screen
readers.
Thank
you.