1 / 8

Who we are

Who we are. Why do an accessibility audit Thinking instead of doing Good timing – JISC/ EDItEUR got in touch A contact person Don’t be frightened. How we did the audit Hired EDItEUR team to do a one day audit 2 points of focus. Technical

britanney-kidd
Download Presentation

Who we are

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Who we are

  2. Why do an accessibility audit • Thinking instead of doing • Good timing – JISC/EDItEUR got in touch • A contact person • Don’t be frightened

  3. How we did the audit Hired EDItEUR team to do a one day audit 2 points of focus Technical Evaluated our websites, ebooks.com ebookservices.com patron portals book content Non Technical Went through a series of questions about policy, internal awareness of accessibility, file processing and rights management

  4. What we learned - Technical WEBSITE • Luckily, our websites weren’t that bad, whew! • Basic webpage navigation • How text-to-speech tools work with html code • How our online reader and other readers worked

  5. CONTENT • The main issue is DRM. Publishers want it. Accessibility tools can’t work with it. • Readers like ADE haven’t applied enough useful functionality… yet • Complex documents need proper formatting and linking • Metadata – ONIX 3 codelist 196 What we learned - Technical

  6. What we learned – Non Technical • Awareness, internally and externally • Develop a policy and share it with customers • Provide instructions

  7. What we’re going to do now Next few weeks: • Creating a policy • Creating a page in our customer service area with advice on how to download and read files Next few months: • Develop our reader to work with watermarked rather than encryped files, esp for pdf • Include codelist 196 in our metadata requirements • Develop the digital comps platform to accommodate requests from librarians with print impaired students to make this easier to manage for publishers

  8. Contact me Veruschka Selbach veruschka.selbach@ebooks.com 0207 268 2885

More Related