Your SlideShare is downloading. ×
Accessible Javascript - Barcamp Brighton 2
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Accessible Javascript - Barcamp Brighton 2

1,743

Published on

A quick overview about how to make Javascript Accessible. Held at Barcamp Brighton 2

A quick overview about how to make Javascript Accessible. Held at Barcamp Brighton 2

Published in: Education, Technology, Design
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,743
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
7
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Accessible
Javascript
 Not
Vodoo
–
not
much
 Dirk
Ginader
 Barcamp
Brighton
2
 h>p://blog.ginader.de

  • 2. SemanCc
Markup
 •  Markup
your
Content
to
make
it
work
by
itself
 •  Think
about
every
element
and
its
Role
 – Have
you
really
found
a
new
Use
for
DL?
;‐)

  • 3. Serverside
InteracCon
 •  Everything
you
want
to
do
using
Javascript
 Magic
you
first
have
to
solve
without
 •  Think
what
you
can
do
with
Page
reloads
(yes
I
 know
they’re
not
the
cool
Kids
anymore…)

  • 4. Progressive
Enhancement
 •  Everybody
should
have
heard
about
this
by
 now.
Do
you?
 •  When
everything
works
start
adding
Magic
 •  Hijack
ExisCng
Elements
and
add
new
 FuncConality
 •  Add
new
Controls
for
Javascript
only



  • 5. CSS
 •  Pay
A>enCon
what
you
hide,
how
and
when
 •  Display:none
and
visibility:hidden

are
not
 generally
useless
or
evil
but
o_en

  • 6. Update
and
Inform
 •  (Most)
Screen
Readers
know
Javascript
 •  Most
of
the
Stuff
actually
works,
they
just
 don’t
know
 •  Make
them
know
something
changed
by
 seang
the
focus()
 •  Use
a
hidden
Form
Element
to
force
the
 Screen
Reader
rebuild
its
Virtual
Buffer

  • 7. Not
Only
Screen
Readers
 •  Think
about
Keyboard
only
Users
 •  Tab
your
App.
Does
it
work?
 •  Do
hidden
Elements
Show
on
focus?

  • 8. Good
Ressources
 h>p://www.isolani.co.uk/blog/
 h>p://www.accessibilityCps.com/
 h>p://juicystudio.com/
 h>p://learningtheworld.eu/
 h>p://uk.tv.yahoo.com/
(The
Search
on
the
 upper
right
was
used
for
the
Example)


×