Accessibility in Practice
Upcoming SlideShare
Loading in...5
×
 

Accessibility in Practice

on

  • 1,013 views

Accessibility in Practice: Real world design challenges Action for Blind People website design & build. Guest Lecture at MSc Digital Inclusion, Middlesex University. 26th September 2011

Accessibility in Practice: Real world design challenges Action for Blind People website design & build. Guest Lecture at MSc Digital Inclusion, Middlesex University. 26th September 2011

Statistics

Views

Total Views
1,013
Views on SlideShare
968
Embed Views
45

Actions

Likes
0
Downloads
2
Comments
0

3 Embeds 45

http://paper.li 37
http://bitly.com 7
https://twitter.com 1

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

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
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

Accessibility in Practice Accessibility in Practice Presentation Transcript

  • Accessibility in PracticeReal world design challenges Action for Blind People website design & build Sandi Wassmer, Guest Lecturer MSc Digital Inclusion, Middlesex University 26th September 2011
  • A website is a product that people interact with Accessibility is not standalone It is one of many designconsiderations that competes to meet a projects objectives
  • If you dont know why, whats the point? Purpose: Whats the purpose? Audience: Whos it for? Objectives: What must the Audience do to fulfil the Purpose? Plan: How will they do it?
  • The TeamRelationships underpin everything.Knowledge, skill and experienceare meaningless without respect,understanding & communication.
  • ConsiderationsContent Types: ‣ Text ‣ Graphics ‣ Images ‣ Audio ‣ Video ‣ Downloadable Documents
  • ConsiderationsDesign: ‣ Conceptual ‣ Visual ‣ User Interface ‣ Information Architecture ‣ Interaction
  • ConsiderationsClient Side Development: ‣ Content HTML ‣ Style CSS ‣ Experience Javascript
  • ConsiderationsServer Side Development: ‣ CMS ‣ Database ‣ Programming
  • ConsiderationsBest Practices: ‣ Design ‣ Development ‣ Content Strategy ‣ Web Standards ‣ User Experience ‣ Usability ‣ Accessibility ‣ User Testing
  • User Experts are involved from the start Learning: collating existing knowledge, conducting market research, analysis, reporting Scoping: functional scoping, technical scoping, use cases documentationPrototyping: schematics, user journeys, wireframes, user interactions Testing: features & functionality, task completion, accessibility conformance, markup validation, browser & device compatibility, assistive technologies
  • Laying the foundation‣ Clean semantic markup‣ XHTML 1.0 Strict vs HTML 4.01
  • User Interfaces‣ Intuitive‣ Consistent‣ Memorable
  • Information Architecture‣ Well Structured‣ Meaningful‣ Consistent‣ Informative
  • Findability‣ Search‣ Filter‣ Navigation‣ Sitemap
  • Presentation‣ Style Switcher‣ Keyboard Focus‣ Screenreader Navigation‣ Disable CSS‣ Printability
  • Presentation: Style Switcher
  • Presentation: Keyboard Focus
  • Presentation: Screenreader Navigation
  • Presentation: Disable CSS
  • Presentation: Printability
  • Interactions‣ Instructions‣ Error Prevention‣ Error Handling‣ Success
  • WCAG 2.0: Think. Dont Tick.1.4.4 Resize text: "....text can be resizedwithout assistive technology up to 200 percent" (Level AA) 200 percent of what?
  • WCAG 2.0: Think. Dont Tick.3.1.5 Reading Level: When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does notrequire reading ability more advanced than the lower secondary education level, is available. (Level AAA) Sure. Right after I rewrite War and Peace.
  • WCAG 2.0: Think. Dont Tick.2.4.4 Link Purpose (In Context): "The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, ...." (Level A) Made sense until we tested with screenreader users who group links out of context.
  • WCAG 2.0: Think. Dont Tick. 1.1.1 Non-text Content: "All non-textcontent that is presented to the user has a text alternative that serves the equivalent purpose..." (Level A) Is the purpose to describe or convey meaning?
  • Testing, Testing, Testing Experts: test the whole website for conformance against known standards and objectives Users: are set a series of tasks to complete that determine whether a website is fit for purpose
  • Any Questions? Transcript of this presentation available for Download2011 Sandi Wassmer