1. Universell utforming
Case: Nye udi.no
Christian Spidsberg
Nettredaktør/prosjektleder

2. Om meg
• Nettredaktør i UDI.
• Prosjektleder for nye udi.no.
• Arbeidet med web siden årtusenskiftet.
• Blogger på webetaten.no
Side 2

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. Universell utforming er…
Side 4

5. ….mer enn
tilgjengelighet for
blinde.
Side 5

6. ….mer enn kvalitets-
vurderingene til DIFI.
Side 6

7. Side 7
Språk
Pedagogikk
Teknikk

8. Hent inn
ekspertkompetanse.
Side 8

9. Kravspesifikasjonen må
sette standarden:
• koding og programmering
• innhold og design
• navigasjon
• film og video
• ….
Side 9

10. Utfordringer blir
det…
Side 10

11. Men så…
Side 11

12. • I dag: Tillatelsen danner grunnlag for
familieinnvandring.
• Nytt: Familien din kan vanligvis søke
om å bo med deg i Norge.
Side 12

13. Side 13

14. Takk for meg.
• www.webetaten.no
• @webetaten
• 992 99 557
Side 14

17. Why should that interface be accessible?

18. How would we make that accessible?

19. To whom should it be accessible?

20. • blind
• low-vision
• hearing
• mobility/dexterity
• cognitive
• speech

22. erceivable
perable
nderstandable
obust
P
O
U
R
w3.org/WAI

23. P O U R
Focuses on user needs, not technology.

24. Web Accessibility is a Design Tool

25. Derek Featherstone
feather@simplyaccessible.com
@feather

26. Accessibility is part of User Experience.

27. extremes extremes

28. 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.

29. The checklist is a
starting point,
not an end
point.

30. Just because something is compliant,
doesn’t mean it will be easy to use.

32. How can we get beyond the checklist?

33. Great design, technical excellence, the
right content and functionality.

34. Great design, technical excellence, the
right content and functionality.

35. PRINCIPLE 1
Start with content

36. Content specific to people with disabilities?

37. PRINCIPLE 2
Move from what to why.

38. Overlapping Map Polygons: Non-visual access

39. 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

40. PRINCIPLE 3
Out of sight, out of mind.

43. GROUP CLOSELY RELATED ITEMS

44. Layout: Proximity for Low-vision users

45. Layout: Proximity for Low-vision users

46. Use layout to create the right "chunks"

47. Use layout to create the right "chunks"

48. PRINCIPLE 4
Design for Quick Consumption

49. Front-loaded
content

52. USE HEADINGS
FOR QUICK CONSUMPTION

55. PRINCIPLE 5
Keyboard.Keyboard.Keyboard.

62. PRINCIPLE 6
Design for forgetfulness.

63. Summary and Field-level errors

64. These principles help
make better, more accessible
designs for everyone.

65. simplyaccessible.com/newsletter

66. Derek Featherstone
feather@simplyaccessible.com
@feather

67. 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