Child pages
  • Web Council - June 9, 2011
Skip to end of metadata
Go to start of metadata
  • Web Council, June 9, 2011
    • July 21 Web Council Meeting - Networking and Treats
      • Chris Heiland (cheiland@uw.edu) is organizer; contact him with your ideas for networking activities
    • Tim Chang-Miller (tcmiller@uw.edu), Header and Footer Wizard
      • 150th Anniversary patches are now available in the Header and Footer wizard (http://uw.edu/marketing/header-footer-wizard)
      • Patches replace the regular W patch where present in header or footer
        • 150th patch links to the UW 150th anniversary page
      • A version was not made for the skinny header and footer. The full-size patch was the only approach that presented the 150th logo well
    • Terrill Thompson, DO-IT, tft@uw.edu
      • Accessibility and the Law
        • There is a lot happening in the Web accessibility world on the federal front
          • This is from the perspective of a technology accessibility specialist, not a lawyer
        • Brief history of law relating to accessibility
          • 1973 - Section 504 of the Rehabilitation Act - programs and services or recipients of federal money must be accessible
          • 1990 - Americans with Disabilities Act - prohibits disability discrimination
            • Title 1 - Employment
            • Title II - Public Entities
            • Title III - Public Accommodations
              • Did not provide guidance on whether technologies were public accomnodations
          • 1998 - Section 508 of Rehabilitation Act amended - required federal agencies to develop, procure, and use accessible IT
          • 2001 - Section 508 IT accessibility standards developed, based in part on W3C Web Content Accessible Guidelines 1.0, priority 1 checkpoints
            • Focused on what was measurable and enforceable
          • 2001 - 2008
            • Web technologies got more and more interactive, standards got hard to apply
          • Dec 2008 - W3C WCAG 2.0 (http://www.w3.org/TR/WCAG20/) became standard
            • Level A Success Criteria (26)
              • All the stuff we usually think of accessible methods, including captions on videos, transcripts for audio
            • Level AA (13)
              • Audio descriptions on video
            • Level AAA (23)
          • 2008 - Re-authorization of Higher Education Act
            • Studying the current state of accessible materials for students with disabilities in post-secondary education
            • Should report soon
          • 2009 - National Federation for the Blind (http://www.nfb.org/nfb/default.asp) became more active on IT issues
            • June 2009 - Sued Arizona State University, settled Jan 2010
              • Really trying to force Amazon to make Kindle accessible
            • November 2010 - Filed complaint against Penn State University
              • Inaccessible library Web site
              • Departmental departmental websites
              • Classroom technologies not usable by flind faculty
              • Inaccessible financial services
            • March 2011 - Filed complaint against Northwester and NYU over use of Google Apps
              • Trying to get education institutions to push Google
          • March 2010 - Section 508 standards draft released for public comment
            • June 2010 - End of public comment periods
          • July 2010 - Dept of Justice proposed new rules to clarify ADA requirements related to web accessibility
            • Request for comments, closed in January 2011
            • Asked 19 questions, including "Should Dept adopt WCAG 2.0 Level AA Success Criteria" as it's standard for Web site accessibility
          • May 26, 2011 - Department of Education Office of Civil Rights sent out Dear Colleague letters
        • Good News, we have solutions
          • Site Checker will be available for UW sites, within limits
          • Accessible design(http://uw.edu/accessibility/) is pretty straightforward
            • Need to evaluate sites and widgets in terms of voice browser use, keyboard-only use, and visually enhanced use
      • Accessible PDFs
        • What makes an electronic document accessible
          • Text alternatives for non-text content
          • Information structure and relations
          • These features are built into HTML, PDF, and Word
        • Three types of PDF images
          • Image - not accessible to someone who cannot see it
          • Image with embedded fonts - somewhat accessible, but no structural stuff
          • Tagged PDF - optimized for accessibility
            • Created by Adobe at 2000, has semantic structure
        • Creating an accessible PDF
          • Use an authoring tool that supports accessible PDFs
            • Steps
              • Create documents with headings and subheadings
              • Add alt text to images
              • Tag text
        • Making an accessible PDF from an inaccessible PDF
          • We want a PDF with structural information
          • Word, in new versions
            • Adding alt text to images
              • Select image, go to Format picture, enter text for alt into Description field
                • Advice is to just use the Description, not the Title, field
              • For headings, just use the heading types in the styles
            • Latest versions offer the ability to create tagged PDF directly from Word
              • Earlier versions the process is more complicated, printing to a PDF with versions before 2011 does not created tagged PDF
            • Can adjust accessibility in Acrobat Pro
              • Can check if a PDF file is tagged
                • .In Acrobat Pro, go to Document Properties and select Description, at bottom is a Tagged PDF item - it should say Yes
          • Good to push accessibility up the production process as much as possible
            • Make it accessible early in the process, rather than fixing it at the end
          • Resources
        • Questions
          • How do you work with external people who provide documents that turn out not to be accessible
            • We do not have a standard practice at the UW for creating accessible documents
            • Good topic for future discussion
          • What about legacy stuff?
            • Institutions that have developed accessibility policies tend to set dates beyond which all new stuff is will be created accessible, with goals set for updating old stuff that is still in use
              • New stuff most important
              • Stuff still being used should be made accessible
          • Who is responsible for ensuring non-web documents are created in an accessible manner?
            • Employee, supervisor, tech staff?
    • Pawan Khera of IBM, Captioning Videos
      • IBM developed a media captioner and editor for internal use and is now working on making it available on the Web
        • Uses advanced speech recognition technology to convert the audio track of a video into captioning
      • The UW is invited to collaborate with IBM on a pilot project
        • Anyone interested should contact Harry Hayward (hhayward@uw.edu)
  • No labels