OGLC And Accessibility - iSchool Presentation. March 12, 2010


Published on

Presentation to iSchool students regarding Ontario's new accessibility standards and libraries.

Published in: Education, Design, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

OGLC And Accessibility - iSchool Presentation. March 12, 2010

  1. 1. Accessibility and the OGLC Goals and Realities
  2. 2. <ul><li>AODA - Accessibility for Ontarians withDisabilities Act, 2005 </li></ul><ul><li>Reg 429/07 -January 1, 2010 and the Public Sector </li></ul><ul><li>And What About Library Services </li></ul><ul><li>OGLC – Our Experiences </li></ul>What I’ll be talking about…
  3. 3. AODA – What is a disability… <ul><li>AODA uses the same definition of &quot;disability&quot; as the Ontario Human </li></ul><ul><li>Rights Code, including both visible and non-visible disabilities. In the </li></ul><ul><li>Act, &quot;disability&quot; means:   </li></ul><ul><li>any degree of physical disability, infirmity, malformation or disfigurement that is caused by bodily injury, birth defect or illness and, without limiting the generality of the foregoing, includes diabetes mellitus, epilepsy, a brain injury, any degree of paralysis, amputation, lack of physical coordination, blindness or visual impediment, deafness or hearing impediment, muteness or speech impediment, or physical reliance on a guide dog or other animal or on a wheelchair or other remedial appliance or device </li></ul><ul><li>a condition of mental impairment or a developmental disability, </li></ul>
  4. 4. AODA – What is a disability… <ul><li>a learning disability, or a dysfunction in one or more of the processes involved in understanding or using symbols or spoken language, </li></ul><ul><li>a mental disorder, or </li></ul><ul><li>an injury or disability for which benefits were claimed or received under the insurance plan established under the Workplace Safety and Insurance Act, 1997 </li></ul>
  5. 5. AODA – What is a disability… <ul><li>Types of disabilities: </li></ul><ul><li>Vision </li></ul><ul><li>Hearing </li></ul><ul><li>Physical </li></ul><ul><li>Intellectual </li></ul><ul><li>Developmental </li></ul><ul><li>Learning </li></ul><ul><li>mental health </li></ul><ul><li>speech or language </li></ul><ul><li>deaf-blind </li></ul>
  6. 6. AODA – The numbers behind the Act… <ul><li>About 1.85 million people in Ontario have disabilities; 15.5% of Ontario's population </li></ul><ul><li>Aging population, number of Ontarians with a disability will increase </li></ul><ul><li>projections show that in 2025 majority of persons with disabilities will be 65+ years of age </li></ul><ul><li>Unemployment rate 5 times as high - untapped labour market potential </li></ul><ul><li>Spending power $21-25 billion a year </li></ul><ul><li>Learning to better serve people with disabilities is good for business and community. </li></ul>
  7. 7. AODA – The 2025 vision… <ul><li>Fully accessible Ontario by 2025 </li></ul><ul><li>Only jurisdiction in Canada to have legislation that establishes a comprehensive goal </li></ul><ul><li>First jurisdiction in the world to move from complaints-based legislation to a regulatory model in the area of mandated accessibility </li></ul><ul><li>Private sector in compliance to Reg 429/07 by 2012 </li></ul><ul><li>Only jurisdiction in the world requiring both Public and Private sector compliance for customer service </li></ul>
  8. 8. AODA – It’s all about standards… <ul><li>Ontarians with Disabilities Act, 2001 (ODA) was about planning, and the accessibility planning for government and broader public sector still applies </li></ul><ul><li>ODA had no standards; limited enforcement </li></ul><ul><li>AODA is about accessibility standards </li></ul><ul><li>Establish enforceable standards with timelines for compliance in accessing goods, services </li></ul><ul><li>buildings and employment standards will allow for the integration of accessibility into regular business and capital planning </li></ul>
  9. 9. AODA – It’s all about standards… <ul><li>Accessibility standards are completed or currently being developed in 5 key areas: </li></ul><ul><ul><li>Customer Service </li></ul></ul><ul><ul><li>Built Environment </li></ul></ul><ul><ul><li>Employment </li></ul></ul><ul><ul><li>Information and Communications </li></ul></ul><ul><ul><li>Transportation </li></ul></ul><ul><li>Standards Development Committees: inclusive and consensus-based, involve: People with Disabilities; Representatives of Industries and Economic Sector; Ontario Government Ministries; Public Consultation </li></ul>
  10. 10. Reg 429/07… <ul><li>Accessibility Standards for Customer Service Regulation (O. Reg. 429/07) is the first accessibility standard under the AODA - it came into force January 1, 2008 </li></ul><ul><li>Applies to all organizations that provide goods or services to the public or other organizations in Ontario and have at least 1 employee </li></ul><ul><li>Timetable for compliance and reporting: </li></ul><ul><ul><li>Public Sector [Libraries], January 1, 2010, and Org. must file a report in 2010 </li></ul></ul><ul><ul><li>Private Sector [Libraries], January 1, 2012 - Org. must file report depending on number of employees </li></ul></ul>
  11. 11. Reg 429/07… <ul><li>Requirements include: </li></ul><ul><li>Establish policies, practices and procedures on providing goods and services to people with disabilities </li></ul><ul><li>Use reasonable efforts to ensure that policies, practices and procedures are consistent with the key principles of independence, dignity, integration and equality of opportunity </li></ul><ul><li>Communicate with a person with a disability in a manner that takes into account their disability </li></ul><ul><li>Accomodate service animals, support person; communicate / notify when facilities or services are unavailable </li></ul>
  12. 12. Reg 429/07… <ul><li>Requirements include: </li></ul><ul><li>All staff receive training (training policy); front line to policy development  </li></ul><ul><li>Must provide a process to receive and respond to feedback </li></ul><ul><li>Communicate with a person with a disability in a manner that takes into account their disability </li></ul><ul><li>Policy to accomodate service animals, support person, and assistive devices </li></ul><ul><li>Procedures to communicate / notify when facilities or services are unavailable </li></ul>
  13. 13. Reg 429/07… <ul><li>Organizations and businesses with 20 or more employees must: </li></ul><ul><li>Document in writing all our policies, practices and procedures for providing accessible customer service and meet other document requirements set out in the standard. </li></ul><ul><li>Notify customers that documents required under the customer service standard are available on request. </li></ul><ul><li>When giving information / documents required under the customer service standard to a person with a disability, provide the information in a format that takes into account the person’s disability. </li></ul><ul><li>Unless exempted by regulation, all organizations and businesses must file an accessibility report. </li></ul>
  14. 14. And what about library services… <ul><li>Public sector libraries falling under the January 1, 2010 compliance </li></ul><ul><li>Umbrella. </li></ul><ul><li>Customer Service </li></ul><ul><li>Use of terminology, e.g. </li></ul><ul><ul><li>Confined to a Wheelchair, use &quot;A person who uses a wheelchair </li></ul></ul><ul><ul><li>Normal, use &quot;A Person without a disability“ </li></ul></ul><ul><ul><li>Physically Challenged, use &quot;A person who uses a walker / mobility aid&quot;, &quot;a Person with arthritis&quot;... </li></ul></ul><ul><li>See a full list to Choose the Right Word as  provided by the Ontario Government. </li></ul>
  15. 15. And what about library services… <ul><li>Customer Service </li></ul><ul><li>Bet attentive to the specific needs, e.g . </li></ul><ul><ul><li>Identify yourself when you approach a person and speak directly to the person with a disability: e.g. not to the support person </li></ul></ul><ul><ul><li>Ask before you help; library materials in large print; procedures for Braille </li></ul></ul><ul><ul><li>Don't touch devices, e.g. wheelchairs, mobility devices </li></ul></ul><ul><ul><li>Provide information about accessible features of immediate environment </li></ul></ul><ul><ul><li>Procedures for accessing / retrieving stack materials </li></ul></ul>
  16. 16. And what about library services… <ul><li>Customer Service </li></ul><ul><li>Bet attentive to the specific needs, e.g . </li></ul><ul><ul><li>Assisting someone with mental health disabilities; see recent AALL article about Law Libraries and serving persons with mental health disabilities Learning disabilities </li></ul></ul><ul><ul><li>take your time, patience, let the individual identify how best to provide service in a way that works for them   </li></ul></ul><ul><ul><li>Don't touch devices, e.g. wheelchairs, mobility devices </li></ul></ul><ul><ul><li>TTY; and audio format for people with a vision, </li></ul></ul><ul><ul><li>intellectual or developmental, or learning disability who are unable to read print </li></ul></ul>
  17. 17. And what about library services… <ul><li>Information and Communications </li></ul><ul><li>Provide assistive technologies for public / visitor workstations, e.g. </li></ul><ul><li>Screen readers </li></ul><ul><li>Captions for audio portion of video tutorials; screen casts   </li></ul><ul><li>Alternative input devices: alternative keyboards; touch screens </li></ul><ul><li>Screen enlargers / magnifiers </li></ul><ul><li>Speech recognition or voice recognition programs: allow people to give commands and enter data using their voices </li></ul><ul><li>Text-to-speech synthesizers </li></ul><ul><li>Talking and large print Word processors </li></ul><ul><li>TTY </li></ul><ul><li>Braille translation programs </li></ul>
  18. 18. And what about library services… <ul><li>Your Web Services </li></ul><ul><li>Build sites, web services using web accessibility standards and </li></ul><ul><li>principles of design, e.g. </li></ul><ul><li>Sites which address vision disabilities (blindness, colour-blindness, vision loss); </li></ul><ul><li>Hearing disabilities; </li></ul><ul><li>Disabilities which impact motor skills (inability to use a mouse, slow response time, limited fine motor control); </li></ul><ul><li>Cognitive disabilities (learning disabilities, distractibility, inability to remember or focus on large amounts of information) </li></ul>
  19. 19. And what about library services… <ul><li>Your Web Services </li></ul><ul><li>How… </li></ul><ul><li>Alternative text - provides a textual alternative to non-text content in web pages. It is especially helpful for people who are blind and rely on a screen reader to have the content of the website read to them  </li></ul><ul><li>Table Headers - tables that are used to organize tabular data should have appropriate table headers (the <th> element). Data cells should be associated with their appropriate headers, making it easier for screen reader users to navigate and understand the data table </li></ul><ul><li>Links - every link should make sense if the link text is read by itself. Screen reader users may choose to read only the links on a web page. Certain phrases like &quot;click here&quot; and &quot;more&quot; must be avoided </li></ul>
  20. 20. And what about library services… <ul><li>Your Web Services </li></ul><ul><li>Caption and/or provide transcripts for media </li></ul><ul><li>Accessibility of non-html documents; structure your Word and Office documents for accessibility </li></ul><ul><li>Design to standards outline by WAI and W3 </li></ul><ul><li>Clear Language and Design - use clear fonts, and use headings and lists appropriately </li></ul><ul><li>JavaScript - make JavaScript event handlers are device independent (e.g., they do not require the use of a mouse) and make sure that your page does not rely on JavaScript to function </li></ul>
  21. 21. And what about library services… <ul><li>Your Web Services </li></ul><ul><li>Allow users to skip repetitive elements on the page - provide a method that allows users to skip navigation or other elements that repeat on every page, e.g. &quot;Skip to Content“ </li></ul><ul><li>Forms - make sure all form elements (text field, checkbox, dropdown list, etc.) has a label and make sure that label is associated to the correct form element using the <label> tag </li></ul><ul><li>Setup library-wide policies, procedures, and standards to ensure these web accessibility standards are followed </li></ul><ul><li>...accessibility and the mobile web, new services (eReaders, iPads)  </li></ul>
  22. 22. And what about library services… <ul><li>Your Documents </li></ul><ul><li>Do you do deliver Word docs in your research work for clients; do you </li></ul><ul><li>deliver answers via e-mail...then you'll have to Structure your </li></ul><ul><li>Documents </li></ul><ul><li>Use true styles in Word. For example, when creating a heading, don't simply change the font, enlarge the font size, make it bold, etc. If this is done, the document has no real structure that can be discerned by a screen reader. In Word, the correct way to provide structure is to use Word style. </li></ul>
  23. 23. And what about library services… <ul><li>Your Documents </li></ul><ul><li>Setup guidelines fro structuring Office documents (or whatever your </li></ul><ul><li>library works with), and this includes e-mail. </li></ul><ul><li>For e-mail, Html and Plain Text are best, but choosing one over the other depends on whether you're using links: Html best to use if you're including links in the e-mail, but for screen readers to provide useful information to the user you need to ensure that the link is embedded in text instead of simply providing the url Setup your e-mail replies / responses so that the inserted text can be differentiated from the original text </li></ul>
  24. 24. And what about library services… <ul><li>Your Documents </li></ul><ul><li>The PDF Dilemma: </li></ul><ul><li>Many people involved in developing Accessibility policy and standards for AODA see PDF as non-accessible document format...it simply doesnot &quot;screen read&quot; like Word or Html. </li></ul><ul><li>Adobe claims to have provided features built into Acrobat (eg. tagging of document) which allows PDF documents to be accessed with assistive technology: see Accessing PDF Documents with Assistive Technology: A Screen Reader User's Guide </li></ul><ul><li>Our library, and many Ontario Government services, provide all documents to be downloaded in either 2 of the 3: Word, PDF, or Html </li></ul>
  25. 25. And what about library services… <ul><li>Policy & Planning </li></ul><ul><li>Library managers need to now consider accessibility with regard to procurement activities or planning for future development (e.g. physical space, building codes, etc.) </li></ul><ul><li>Are the vendors you work with developing products which meet accessibility standards; think of the ILS industry </li></ul><ul><li>Create a record of vendors who provide goods and services which meet accessibility standards </li></ul><ul><li>Recruitment and employment standards </li></ul>
  26. 26. OGLC’s experience… <ul><li>Who We Are </li></ul><ul><li>The Ontario Government Libraries Council (OGLC) was established to strategically support the Government of Ontario and to assist and advocate for libraries and librarians working in information management services within the Government of Ontario. </li></ul><ul><li>OGLC provides a platform for Ontario Government Libraries to discuss, collaborate, plan, and advocate for information management initiatives which improves the management and sharing of information both within and outside of the Government. </li></ul>
  27. 27. OGLC’s experience… <ul><li>  Dealing with the “Realities” </li></ul><ul><li>The OGLC established the &quot;OGLC Working Group on Accessibility(AODA) Best Practices“ </li></ul><ul><li>Our role is to keep our members informed of the issues and new developments, and to explore possible solutions / options and provide recommendations </li></ul><ul><li>About 32 Libraries / Resource Centres, etc (last time I counted), many quite different in org. setup (virtual, 1 staff to 60 staff), </li></ul><ul><li>Providing different level of services: e.g. my library (the OWTL ) serves both the public and government, many don't. </li></ul>
  28. 28. OGLC’s experience… <ul><li>Dealing with the “Realities” </li></ul><ul><li>Different Funding and Corporate planning structures (Ministries, clusters, ABCs) can slow progress towards accessibility standards compliance: e.g. many libraries don't have a screen reader, screen magnifier, and other assistive technology installed on the client / public / visitor stations </li></ul><ul><li>Our role is to keep our members informed of the issues and new developments, and to explore possible solutions / options and provide recommendations </li></ul><ul><li>Guidelines and procedures on how to deal with requests for Ministry / library documents in braille...not readily available </li></ul>
  29. 29. OGLC’s experience… <ul><li>Dealing with the “Realities” </li></ul><ul><li>We hope to Identify the common and unique accessibility concerns of our members, and help them work toward some solution </li></ul><ul><li>Provide and maintain an online directory of key resources, tools, and documents related to accessibility and libraries </li></ul><ul><li>Help build “templated” policies, procedures, guidelines which we can share with all our OGLC members </li></ul><ul><li>Keep on-top of the standards, accessibility literature, resources, and tools, and get together regularly to discuss next steps… </li></ul>
  30. 30. Thanks… <ul><li>If you have any questions please feel free to contact me: </li></ul><ul><li>Peter Marques </li></ul><ul><li>416-314-8957 </li></ul><ul><li>[email_address] </li></ul><ul><li>Ontario Workplace Tribunals Library </li></ul><ul><li>OGLC Working Group on Accessibility (AODA) Best Practices </li></ul><ul><li>Presentation available on SlideShare at </li></ul><ul><li>http://www.slideshare.net/owtlibrary </li></ul>