2012-07-24: Accessibility On The Web
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

2012-07-24: Accessibility On The Web

  • 428 views
Uploaded on

Presentation by Jessica Keyes ...

Presentation by Jessica Keyes
Baltimore Lean Startup meetup
July 24, 2012

More in: Technology , Design
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
428
On Slideshare
428
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
1
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. ACCESSIBILITY ON THE WEB
  • 2. MARYLAND PUBLIC LIBRARY ACCESSIBILIT Y PROJECTGoal: Make all public library websites inMaryland fully compliant withSection 508 Accessibility Standards.Enoch Pratt Free Library is the State LibraryResource Center.We will be leading by example and providingsupport to county libraries.
  • 3. WHAT IS SECTION 508?
  • 4. SECTION 508Section 508 of the Rehabilitation Act is afederal law and set of standards.It requires federal agencies to make theirelectronic and information technologyaccessible to people with disabilities.
  • 5. SECTION 508Includes:  software applications and operating systems  w eb-based information or applications  telecommunication products  video and multimedia products  self contained, closed products (e.g., information kiosks, calculators, and fax machines)  desktop and portable computers
  • 6. WCAG 2.0The World Wide Web Consortium (W3) maintainsstandards called WCAG 2.0 (Web ContentAccessibility Guidelines, implemented in 2008).They are international standards .Section 508 standards will soon be updated to referdevelopers and site owners to to WCAG.
  • 7. WHAT ISACCESSIBILITY?
  • 8. WHO DOES IT SERVE?Accessible web content is usable and meaningful forpeople with ANY disability, including:  Blindness  Color blindness  Nearsightedness  Deafness  Reduced motor skills, caused by conditions such as arthritis or amputation  Cognitive impairment  Seizure conditions
  • 9. CONTENT MUST BE PERCEIVABLE P rovide text alternative to non-text content, including images, tables, and forms. P rovide transcripts for audio content, or closed captions for video content D on’t use visual elements such as color or font to communicate important information.
  • 10. SITE MUST BE OPERABLE A ll functions must be available from the keyboard . G ive users  enough time  to read and use content. D o not use content that causes  seizures . H elp users  navigate and find content .
  • 11. CONTENT MUST BE UNDERSTANDABLE M ake text  readable and understandable by using clear and concise writing M ake content appear and operate in  predictable  ways by adhering to best practice standards. C learly define forms and help users  avoid and correct mistakes .
  • 12. SITE MUST BE ROBUST M aximize compatibility with current and future user tools, such as:  S creen readers  D isabling of CSS, Javascript, and/or images  Z ooming tools  M obile devices
  • 13. WHY YOU SHOULD BE ACCESSIBLE
  • 14. WHY? I f your website is not accessible, you will lose valuable market share . A ccessible websites are generally good examples of web design best practices , and will therefore last longer and work better. I t’s not the law yet, but it will be. There have already been successful suits filed against businesses with inaccessible websites.
  • 15. BECOMING ACCESSIBLE
  • 16. TECHNICAL TRICKSUnderstand how people with disabilities use the web.Try:  Activating your operating system’s built-in screen reader and navigating your site blindfolded.  Navigating your site using only the keyboard.  Disabling CSS and Javascript, and see if your site is still usable.
  • 17. PROVIDE ALTERNATE CONTENT A dd alt tags to images P rovide transcripts for audio content P rovide closed captions for video content G ive descriptions to tables and forms
  • 18. USE SEMANTIC MARKUPHTML5 has tags for almost every kind of content.Call your content what it is: Header (<h1>, <h2>) tags for headers and subheaders Emphasis (<em>) rather than italic (<i> is deprecated in HTML5) Footer (<footer>) for the footer area Ordered list (<ol>) for numbered lists
  • 19. FOLLOW GOOD DESIGN PRINCIPLES U se easy-to-read fonts U se fluid layouts so the site displays properly at any resolution L eave ample white space to improve readability U se high-contrast colors
  • 20. TOOLS & RESOURCES The W3 Web Accessibility Initiative (WAI) website has case studies of people with disabilities using the web. WAVE shows errors and warnings in context for individual pages Use your operating system’s built-in text-to-voice software for experiencing your site through a screen reader.For links to these tools and more, visit prairieskydesigns.com .
  • 21. jessica keyes @prairieskygal Thank You!jessica.m.keyes@gmail.com prairieskydesigns.com