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

Accessible Javascript - Barcamp Brighton 2

on

  • 3,116 views

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

Statistics

Views

Total Views
3,116
Views on SlideShare
3,068
Embed Views
48

Actions

Likes
2
Downloads
6
Comments
0

2 Embeds 48

http://blog.ginader.de 46
http://coderwall.com 2

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Accessible Javascript - Barcamp Brighton 2 Accessible Javascript - Barcamp Brighton 2 Presentation Transcript

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

  • 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?
;‐)

  • 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…)

  • 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



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

are
not
 generally
useless
or
evil
but
o_en

  • 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

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

  • 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)