Your SlideShare is downloading. ×
0
Universell utforming
Case: Nye udi.no
Christian Spidsberg
Nettredaktør/prosjektleder
Om meg
•  Nettredaktør i UDI.
•  Prosjektleder for nye udi.no.
•  Arbeidet med web siden årtusenskiftet.
•  Blogger på web...
Vårt mål for udi.no
Minimum 90 % oppfyllelse av WCAG-kravene på nivå
AA etter en uavhengig ekspertevaluering av udi.no ett...
Universell utforming er…
Side 4
….mer enn
tilgjengelighet for
blinde.
Side 5
….mer enn kvalitets-
vurderingene til DIFI.
Side 6
Side 7
Språk
Pedagogikk
Teknikk
Hent inn
ekspertkompetanse.
Side 8
Kravspesifikasjonen må
sette standarden:
•  koding og programmering
•  innhold og design
•  navigasjon
•  film og video
• ...
Utfordringer blir
det…
Side 10
Men så…
Side 11
•  I dag: Tillatelsen danner grunnlag for
familieinnvandring.
•  Nytt: Familien din kan vanligvis søke
om å bo med deg i N...
Side 13
Takk for meg.
•  www.webetaten.no
•  @webetaten
•  992 99 557
Side 14
Why should that interface be accessible?
How would we make that accessible?
To whom should it be accessible?
• blind
• low-vision
• hearing
• mobility/dexterity
• cognitive
• speech
erceivable
perable
nderstandable
obust
P
O
U
R
w3.org/WAI
P O U R
Focuses on user needs, not technology.
Web Accessibility is a Design Tool
Derek Featherstone
feather@simplyaccessible.com
@feather
Accessibility is part of User Experience.
extremes extremes
Accessibility is not binary, all-or-nothing,
black and white. We have every shade of grey
in between. How you view this po...
The checklist is a
starting point,
not an end
point.
Just because something is compliant,
doesn’t mean it will be easy to use.
How can we get beyond the checklist?
Great design, technical excellence, the
right content and functionality.
Great design, technical excellence, the
right content and functionality.
PRINCIPLE 1
Start with content
Content specific to people with disabilities?
PRINCIPLE 2
Move from what to why.
Overlapping Map Polygons: Non-visual access
Different method to get the same information
(Fictitious) proposed boundary changes, City of Ottawa
Does this change affect...
PRINCIPLE 3
Out of sight, out of mind.
GROUP CLOSELY RELATED ITEMS
Layout: Proximity for Low-vision users
Layout: Proximity for Low-vision users
Use layout to create the right "chunks"
Use layout to create the right "chunks"
PRINCIPLE 4
Design for Quick Consumption
Front-loaded
content
USE HEADINGS
FOR QUICK CONSUMPTION
PRINCIPLE 5
Keyboard.Keyboard.Keyboard.
PRINCIPLE 6
Design for forgetfulness.
Summary and Field-level errors
These principles help
make better, more accessible
designs for everyone.
simplyaccessible.com/newsletter
Derek Featherstone
feather@simplyaccessible.com
@feather
Accessibility consulting, strategy and assessments
Accessible development and remediation services
Training courses, works...
Christian og Derek: Web Accessibility (Webdagene 2013)
Christian og Derek: Web Accessibility (Webdagene 2013)
Christian og Derek: Web Accessibility (Webdagene 2013)
Christian og Derek: Web Accessibility (Webdagene 2013)
Christian og Derek: Web Accessibility (Webdagene 2013)
Christian og Derek: Web Accessibility (Webdagene 2013)
Christian og Derek: Web Accessibility (Webdagene 2013)
Christian og Derek: Web Accessibility (Webdagene 2013)
Christian og Derek: Web Accessibility (Webdagene 2013)
Christian og Derek: Web Accessibility (Webdagene 2013)
Christian og Derek: Web Accessibility (Webdagene 2013)
Christian og Derek: Web Accessibility (Webdagene 2013)
Christian og Derek: Web Accessibility (Webdagene 2013)
Christian og Derek: Web Accessibility (Webdagene 2013)
Christian og Derek: Web Accessibility (Webdagene 2013)
Christian og Derek: Web Accessibility (Webdagene 2013)
Upcoming SlideShare
Loading in...5
×

Christian og Derek: Web Accessibility (Webdagene 2013)

1,041

Published on

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

  • Be the first to like this

No Downloads
Views
Total Views
1,041
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Christian og Derek: Web Accessibility (Webdagene 2013)"

  1. 1. Universell utforming Case: Nye udi.no Christian Spidsberg Nettredaktør/prosjektleder
  2. 2. Om meg •  Nettredaktør i UDI. •  Prosjektleder for nye udi.no. •  Arbeidet med web siden årtusenskiftet. •  Blogger på webetaten.no Side 2
  3. 3. Vårt mål for udi.no Minimum 90 % oppfyllelse av WCAG-kravene på nivå AA etter en uavhengig ekspertevaluering av udi.no etter lansering. Side 3
  4. 4. Universell utforming er… Side 4
  5. 5. ….mer enn tilgjengelighet for blinde. Side 5
  6. 6. ….mer enn kvalitets- vurderingene til DIFI. Side 6
  7. 7. Side 7 Språk Pedagogikk Teknikk
  8. 8. Hent inn ekspertkompetanse. Side 8
  9. 9. Kravspesifikasjonen må sette standarden: •  koding og programmering •  innhold og design •  navigasjon •  film og video •  …. Side 9
  10. 10. Utfordringer blir det… Side 10
  11. 11. Men så… Side 11
  12. 12. •  I dag: Tillatelsen danner grunnlag for familieinnvandring. •  Nytt: Familien din kan vanligvis søke om å bo med deg i Norge. Side 12
  13. 13. Side 13
  14. 14. Takk for meg. •  www.webetaten.no •  @webetaten •  992 99 557 Side 14
  15. 15. Why should that interface be accessible?
  16. 16. How would we make that accessible?
  17. 17. To whom should it be accessible?
  18. 18. • blind • low-vision • hearing • mobility/dexterity • cognitive • speech
  19. 19. erceivable perable nderstandable obust P O U R w3.org/WAI
  20. 20. P O U R Focuses on user needs, not technology.
  21. 21. Web Accessibility is a Design Tool
  22. 22. Derek Featherstone feather@simplyaccessible.com @feather
  23. 23. Accessibility is part of User Experience.
  24. 24. extremes extremes
  25. 25. Accessibility is not binary, all-or-nothing, black and white. We have every shade of grey in between. How you view this point frames everything that you learn and do about accessibility.
  26. 26. The checklist is a starting point, not an end point.
  27. 27. Just because something is compliant, doesn’t mean it will be easy to use.
  28. 28. How can we get beyond the checklist?
  29. 29. Great design, technical excellence, the right content and functionality.
  30. 30. Great design, technical excellence, the right content and functionality.
  31. 31. PRINCIPLE 1 Start with content
  32. 32. Content specific to people with disabilities?
  33. 33. PRINCIPLE 2 Move from what to why.
  34. 34. Overlapping Map Polygons: Non-visual access
  35. 35. Different method to get the same information (Fictitious) proposed boundary changes, City of Ottawa Does this change affect you? Use our Postal Code lookup: Postal code: Search
  36. 36. PRINCIPLE 3 Out of sight, out of mind.
  37. 37. GROUP CLOSELY RELATED ITEMS
  38. 38. Layout: Proximity for Low-vision users
  39. 39. Layout: Proximity for Low-vision users
  40. 40. Use layout to create the right "chunks"
  41. 41. Use layout to create the right "chunks"
  42. 42. PRINCIPLE 4 Design for Quick Consumption
  43. 43. Front-loaded content
  44. 44. USE HEADINGS FOR QUICK CONSUMPTION
  45. 45. PRINCIPLE 5 Keyboard.Keyboard.Keyboard.
  46. 46. PRINCIPLE 6 Design for forgetfulness.
  47. 47. Summary and Field-level errors
  48. 48. These principles help make better, more accessible designs for everyone.
  49. 49. simplyaccessible.com/newsletter
  50. 50. Derek Featherstone feather@simplyaccessible.com @feather
  51. 51. Accessibility consulting, strategy and assessments Accessible development and remediation services Training courses, workshops and conferences simplyaccessible.com feather@simplyaccessible.com @feather on twitter Derek Featherstone
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×