8. A
few
years
later
he
picked
up
his
bike
again
and
he
now
rides
some
with
a
‘seeing
eye
friend.’
He
spends
a
lot
of
4me
on
the
internet
learning
about
BMX,
photography,
backpacking
and
all
the
adventurous
things
he’s
doing
and
would
love
to
do
more
of.
10. What
is
Accessibility?
Accessibility
is
all
about
our
ability
to
engage
with,
use,
par4cipate
in,
and
belong
to,
the
world
around
us.
11. The
power
of
the
Web
is
in
its
universality.
Access
by
everyone
regardless
of
disability
is
an
essen:al
aspect.
Tim
Berners-‐Lee,
W3C
Director
and
inventor
of
the
World
Wide
Web
12. Why
Accessibility
is
Important
• 246,000,000
visually
impaired
• 39,000,000
legally
blind
• 275,000,000
deaf
&
hard
of
hearing
That’s
560
million
total!!
To
put
this
in
perspec4ve,
the
en4re
popula4on
of
the
United
States
is
315,000,000.
13. What’s
with
all
the
acronyms?
WCAG
2.0
A11y
Sec4on
508
WAI-‐ARIA
14. WCAG
2.0
Web
Content
Accessibility
Guidelines
(WCAG)
is
developed
through
the
W3C
process
in
coopera4on
with
individuals
and
organiza4ons
around
the
world,
with
a
goal
of
proving
a
single
shared
standard
for
web
content
accessibility
that
meets
the
needs
of
individuals,
organiza4ons,
and
governments
interna4onally.
For
a
short
summary
of
the
WCAG
2.0
guidelines,
see
WCAG
2.0
at
a
Glance.
15. Sec4on
508
In
1998,
Congress
amended
the
Rehabilita4on
Act
of
1973
to
require
Federal
agencies
to
make
their
electronic
and
informa4on
technology
(EIT)
accessible
to
people
with
disabili4es.
Sec4on
508
was
enacted
to
eliminate
barriers
in
informa4on
technology,
open
new
opportuni4es
for
people
with
disabili4es,
and
encourage
development
of
technologies
that
will
help
achieve
these
goals.
www.sec4on508.gov/Sec4on-‐508-‐Of-‐The-‐Rehabilita4on-‐Act
16. A11y
Accessibility
is
ogen
abbreviated
as
the
numeronym
a11y,
where
the
number
11
refers
to
the
number
of
lehers
omihed.
This
parallels
the
abbrevia4ons
of
interna4onaliza4on
and
localiza4on
as
i18n
and
l10n
respec4vely.
hhps://en.wikipedia.org/wiki/Computer_accessibility
17. WAI-‐ARIA
The
Web
Accessibility
Ini:a:ve
-‐
Accessible
Rich
Internet
Applica:ons
Suite,
defines
a
way
to
make
Web
content
and
Web
applica4ons
more
accessible
to
people
with
disabili4es.
It
especially
helps
with
dynamic
content
and
advanced
user
interface
controls
developed
with
Ajax,
HTML,
JavaScript,
and
related
technologies.
hhp://www.w3.org/WAI/intro/aria.php
18. Who
Does
Accessibility
Benefit?
• Blind
• Low-‐vision
• Deaf
&
hard
of
hearing
• Color
blind
• Cogni4ve
impairments
• Mobility
impairments
• Mobile
devices
• Brightly
lit
rooms
• Older
Users
19. Accessibility
Benefits
Everyone!
Not
everyone
who
is
disabled
has
been
disabled
forever
or
will
remain
disabled.
A
website
that
is
accessible
for
the
disabled
ogen
gains
the
benefit
of
becoming
easier
to
use
for
everyone
Overview
of
web
accessibility
for
older
users
hhp://www.w3.org/WAI/intro/wai-‐age-‐literature.php
Web
Content
Accessibility
and
Mobile
Web:
Making
a
Website
Accessible
Both
for
People
with
Disabili4es
and
for
Mobile
Devices
hhp://www.w3.org/WAI/mobile/overlap
20. Accessibility
Benefits
Everyone!
Not
everyone
who
is
disabled
has
been
disabled
forever
or
will
remain
disabled.
Overview
of
web
accessibility
for
older
users
Web
Content
Accessibility
and
Mobile
Web:
Making
a
Website
Accessible
Both
for
People
with
Disabili4es
and
for
Mobile
Devices
22. A
simple
test
you
can
do
is
this:
Unplug
your
mouse
and/
or
turn
off
your
trackpad
1.
Can
you
interact
with
all
controls,
links,
and
menus
using
only
the
keyboard?
2. Can
you
see
what
item
has
focus
at
all
4mes?
3. Does
the
visual
focus
order
match
the
intended
interac4on
order?
The
6
Simplest
Web
Accessibility
Tests
Anyone
Can
Do
24. 13
Of
the
2,764
themes
in
the
WordPress.org
theme
repository
only
13
are
accessbile-‐ready.
(10-‐4-‐2014)
25. Theme
Review
Handbook
• Headings
• Link
Text
• Controls
• Keyboard
• Naviga4on
• Contrasts
• Skip
Links
• Forms
• Images
• Media
hhps://make.wordpress.org/themes/handbook/guidelines/accessibility/
26. Headings
• Use
a
reasonable
heading
structure
-‐
including
the
use
of
heading
elements
for
page
sub-‐sec4ons.
• Do
not
use
text
formanng,
such
as
font
size
or
bold
to
give
the
visual
appearance
of
headings
-‐
use
actual
heading
-‐
You
can
use
css
to
change
the
appearance
of
your
text
• Heading
elements
for
structure
MAY
be
posi4oned
off-‐
screen
as
long
as
this
is
not
at
the
expense
of
providing
good,
visual,
structure.
27. Link
Text
• Avoid
repe44ve
non-‐contextual
text
strings
such
as
‘read
more…’
• The
core-‐defined
‘read
more’
links
fall
under
this
guideline
Use
Filters
28. Keyboard
Naviga4on
• Provide
visual
keyboard
focus
highligh4ng
in
naviga4on
menus,
for
form
fields,
submit
buhons
&
text
links.
• Naviga4on
by
keyboard
should
also
be
intui4ve
and
effec4ve.
POTENTIAL
PROBLEMS
• Something
other
than
a
link
or
form
control
(such
as
a
<div>
or
<span>)
is
programmed
with
scrip4ng
to
perform
an
ac4on.
• Scripted
elements
• Lengthy
naviga4on
(use
skip
links)
29. Controls
Using
These:
<buhon>
<input>
<a>
will
ensure
na4ve
keyboard
accessibility
and
interac4on
with
screen
reader
accessibility
APIs.
31. Skip
Links
Include
a
mechanism
that
enables
users
to
navigate
directly
to
content
or
naviga4on
on
entering
any
given
page.
32. Forms
Comment
Forms
Must:
• Have
appropriate
field
labels
• All
content
within
form
tags
MUST
be
explicitly
associated
to
a
form
control
• Errors
or
confirma4ons
MUST
be
perceivable
If
you
are
using
the
default
WordPress
comment
or
search
forms,
these
pass
the
accessibility-‐ready
criteria.
33. Images
• Decora4ve
images
must
be
included
using
CSS
•
Incorporate
an
appropriate
alt
ahribute
or
the
means
for
an
end
user
to
provide
one.
SEE
webaim.org/techniques/alhext/
34. Media
• Media
resources
must
NOT
auto
start
or
change
without
user
ac4on
as
a
default
configura4on
• This
includes
resources
such
as
audio,
video,
or
image/
content
sliders
and
carousels.
In
general,
media
resources
of
this
nature
are
likely
to
fall
under
the
plugin
territory
guidelines,
and
will
not
be
allowed
in
your
theme.
If
you
have
a
conforming
usage,
however,
these
rules
will
apply.
36. Not
Allowed
• Any
posi4ve
tabindex
ahribute.
• The
inclusion
of
the
accesskey
ahribute.
• Spawning
new
windows
or
tabs
without
warning
the
user.
37. Low
Vision
–
Don’t
Do
This
• hhp://youtu.be/HoHnqruA5bg
• hhp://youtu.be/bIW3POa9D-‐o
• hhp://youtu.be/oklmoixpjI0
The
video
clips
from
the
presenta4on
are
on
Youtube
at
the
links
above.
38. Books
A
Web
for
Everyone
Accessibility
Handbook
----- Meeting Notes (10/4/14 12:48) -----
WebDev since 1998
WordPress since 2011
Contributions to BuddyPress & WordPress
i <3 WordPress
Justin’s visual acuity is currently 20/1200 although he has all of his peripheral vision
Justin is an avid BMX rider, outdoorsman and aspiring photographer. Almost every skill he has acquired or enhanced since his vision loss has been aided by the computer.
Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with the Web.
http://www.bunnyfoot.com/blog/tag/accessibility/
according to the World Health Organization the Blind and visually impaired make up [ 285,000,000 ] people
with [ 39,000,000 ] categorized as legally blind and the remaining [ 246,000,000 ] visually impaired.
Deaf and hearing impaired make up [ 275,000,000 ] (2004) in the moderate-to-profound hearing impairment category.
To put these in perspective, the population of the United States of America is [ 315,000,000 ] (January 2013).
http://a11yproject.com/about.html
WCAG - Web Content Accessibility Guidelines(W3C) http://www.w3.org/WAI/intro/wcag.php
A11y - Representing "accessibility" as "a" followed by 11 more letters, followed by "y".
Section 508 - Section 508 Of The Rehabilitation Act
WAI-ARIA – Web Accessibility Initiative Accessible Rich Internet Applications Suite (Making Ajax and Related Technologies Accessible)
Obviously, the main benefactors are those with vision or hearing issues, or who have
physical limitations.
Also, it’s important to remember that not everyone who is disabled has been disabled forever or will remain disabled.
(my ‘mouse arm’ is a good example) How many of you have had a long coding session and have arm/shoulder problems as a result.
A website that is accessible for the disabled often gains the benefit of becoming easier to use for everyone
Overview of web accessibility for older users
http://www.w3.org/WAI/intro/wai-age-literature.php
Web Content Accessibility and Mobile Web:
Making a Website Accessible Both for People with Disabilities and for Mobile Devices
http://www.w3.org/WAI/mobile/overlap
What if I told you that the WCAG 2.0 recommendation by the W3C is 36 pages, printed?
In addition, “How to Meet WCAG 2.0″ is 44 pages and
“Understanding WCAG 2.0″ 230 pages.
the accompanying Techniques and Failures for WCAG 2.0 is 780 pages, printed.
A simple test you can do is this:
Unplug your mouse and/ or turn off your trackpad
1. Can you interact with all controls, links, and menus using only the keyboard?
2. Can you see what item has focus at all times?
3. Does the visual focus order match the intended interaction order?
http://www.karlgroves.com/2013/09/05/the-6-simplest-web-accessibility-tests-anyone-can-do/
There are 2,764 themes in the WordPress theme repository
How many themes are marked as accessible ready?
Ask the question, does anyone have any idea?
13
There are 2,764 themes in the WordPress theme repository
How many themes are marked as accessible ready?
Ask the question, does anyone have any idea?
13
Do not use text formatting, such as font size or bold to give the visual appearance of headings - use actual heading
You can use css to change the appearance of your text
Heading elements for structure MAY be positioned off-screen as long as this is not at the expense of providing good, visual, structure.
http://webaim.org/techniques/semanticstructure/#contentstructure
Bare urls must NOT be used as links. Context-specific text MAY be positioned off-screen.
The core-defined ‘read more’ links fall under this guideline.
You can use filters to replace these links.
The post title should generally be used in addition to the normal directive text.
POTENTIAL PROBLEMS
something other than a link or form control (such as a <div> or <span>) is programmed with scripting to perform an action.
Scripted elements
Lengthy navigation (use skip links)
See Links are not buttons; neither are divs and spans for detailed information.
Background/foreground color contrast also applies to change of state (:focus or :hover) if there is no additional indicator of :focus or :hover, such as a text decoration change.
The default settings will be the only color scheme checked. If a theme offers multiple color schemes, only the default scheme is required to pass these guidelines. Alternative themes should be clearly labeled if they do not meet accessibility guidelines.
http://leaverou.github.io/contrast-ratio/
MAY be positioned off screen initially but MUST be available to screen reader users and MUST be visible on focus for sighted keyboard navigators.
A minimally conforming skip link MUST:
Be the first focusable element perceived by a user via screen reader or keyboard navigation.
Be visible when keyboard focus moves to the link.
Move focus to the main content area of the page when activated.
If you are using the default WordPress comment or search forms, these pass the accessibility-ready criteria.
Forms that include a single input (such as a standard search form) may, optionally, position the input label offscreen.
Themes that incorporate non-standard forms (e.g. a contact form) will be audited using the same criteria.
Adding alternative text for images is the first principle of web accessibility. It is also one of the most difficult to properly implement.
the W3C alt text decision tree is used to determine whether images are using the alt attribute appropriately.
http://dev.w3.org/html5/alt-techniques/#tree
This includes resources such as audio, video, or image/content sliders and carousels.
In general, media resources of this nature are likely to fall under the plugin territory guidelines, and will not be allowed in your theme.
If you have a conforming usage, however, these rules will apply.
Negative or zero value tabindex is allowed in specific circumstances (assessed on a case-by-case basis).
The accesskey attribute allows the user to activate a control on a page using a keyboard shortcut
Generally speaking, browsers do not provide any indication to users that an accesskey attribute is defined on the link, which is a big issue with the accesskey. Most commonly, the accesskey value is indicated within a title attribute, but this solution still relies on the user mousing over the element to which the accesskey is applied.
A web for Everyone – Rosenfeld Media
Accessibility Handbook – O’Reilly