Christian og Derek: Web Accessibility (Webdagene 2013)

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å webetaten.no

Side 2

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

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

Side 9

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

Side 12

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

erceivableperablenderstandableobust

POUR

w3.org/WAI

P O U R

Focuses on user needs, not technology.

Web Accessibility is a Design Tool

Derek Featherstonefeather@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 point frames everything that you learn and do about accessibility.

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 you?Use our Postal Code lookup:Postal code:

Search

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 HEADINGSFOR QUICK CONSUMPTION

PRINCIPLE 5

Keyboard. Keyboard. Keyboard.

PRINCIPLE 6

Design for forgetfulness.

Summary and Field-level errors

These principles helpmake better, more accessible

designs for everyone.

simplyaccessible.com/newsletter

Derek Featherstonefeather@simplyaccessible.com

@feather

Accessibility consulting, strategy and assessmentsAccessible development and remediation servicesTraining courses, workshops and conferences

simplyaccessible.com

feather@simplyaccessible.com@feather on twitter

Derek Featherstone