custom

Spina, Carli; Cohen, Margaret

40 Survey Results: Survey Questions and Responses descriptive link text proper use of header tags video captions/subtitles short, descriptive image and file names SiteImprove beginning Spring 2018. Wave, Total Validator, AInspector, NUDA WCAG 2.0, but do not know the level. We aim for conformance with WCAG 2.0 Level AA, and incorporate some criteria from WCAG 2.0 Level AAA and WCAG 2.1 for internal testing. We are currently undertaking a university-wide program on accessibility testing. New university guidelines are under construction. We do automated testing against WCAG 2.0 AA criteria and have an Assistive Technology specialist conduct manual testing as well. We follow the university guidelines for web accessibility, which state that we comply with WCAG 2.0 AA level with the goal of achieving AAA level where possible. We use the wave accessibility tool, which includes guidelines from Section 508 and WCAG 2. Web accessibility testing is conducted at the campus level. 27. Please list any tools your library uses for web accessibility testing. N=34 http://wave.webaim.org/ AMP, Chrome Development Tools, Springshare and other link checkers, Chrome Vox, various screen readers Browser-based accessibility plugins (e.g., WAVE, aXE), Deque WorldSpace Comply, Adobe Accessibility Checker, Microsoft Accessibility Checker ComplianceShare (via central IT), Webaim.org FAE, WAVE, AInspector, Jaws, NVDA, VoiceOver https://www.w3.org/WAI/ER/tools, web style edit Manual testing, WAVE tool, Lighthouse (Google), 3rd party tracking/testing/manual check PA11Y & Accessibility Checker SiteImprove SiteImprove SiteImprove, WAVE (web accessibility evaluation tool) SortSite (three responses) W3C HTML validator, AEe core, Geo Metric W3C WCAG 2.0 AA standards Wave tool by webaim TAW Accessibility report. We used a combination of automated and manual testing to fill out a template provided by the W3C WCAG. We did an Accessibility Audit as part of our discovery process from our new redesign website. WAVE, aXe WAVE Web Accessibility Tool (seven responses) WAVE Web Accessibility Tool (wave.webaim.org), Canadian Government Standard on Web Accessibility (https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=23601)

Previous Page Next Page

SPEC Kit 358: Accessibility and Universal Design (May 2018) resources

Free Attachments

Follow Link Accessibility-Universal-Design-SPEC-Kit-358.pdf

Extracted Text (may have errors)

40 Survey Results: Survey Questions and Responses descriptive link text proper use of header tags video captions/subtitles short, descriptive image and file names SiteImprove beginning Spring 2018. Wave, Total Validator, AInspector, NUDA WCAG 2.0, but do not know the level. We aim for conformance with WCAG 2.0 Level AA, and incorporate some criteria from WCAG 2.0 Level AAA and WCAG 2.1 for internal testing. We are currently undertaking a university-wide program on accessibility testing. New university guidelines are under construction. We do automated testing against WCAG 2.0 AA criteria and have an Assistive Technology specialist conduct manual testing as well. We follow the university guidelines for web accessibility, which state that we comply with WCAG 2.0 AA level with the goal of achieving AAA level where possible. We use the wave accessibility tool, which includes guidelines from Section 508 and WCAG 2. Web accessibility testing is conducted at the campus level. 27. Please list any tools your library uses for web accessibility testing. N=34 http://wave.webaim.org/ AMP, Chrome Development Tools, Springshare and other link checkers, Chrome Vox, various screen readers Browser-based accessibility plugins (e.g., WAVE, aXE), Deque WorldSpace Comply, Adobe Accessibility Checker, Microsoft Accessibility Checker ComplianceShare (via central IT), Webaim.org FAE, WAVE, AInspector, Jaws, NVDA, VoiceOver https://www.w3.org/WAI/ER/tools, web style edit Manual testing, WAVE tool, Lighthouse (Google), 3rd party tracking/testing/manual check PA11Y & Accessibility Checker SiteImprove SiteImprove SiteImprove, WAVE (web accessibility evaluation tool) SortSite (three responses) W3C HTML validator, AEe core, Geo Metric W3C WCAG 2.0 AA standards Wave tool by webaim TAW Accessibility report. We used a combination of automated and manual testing to fill out a template provided by the W3C WCAG. We did an Accessibility Audit as part of our discovery process from our new redesign website. WAVE, aXe WAVE Web Accessibility Tool (seven responses) WAVE Web Accessibility Tool (wave.webaim.org), Canadian Government Standard on Web Accessibility (https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=23601)

Help

39 SPEC Kit 358: Accessibility and Universal Design I think we’re heading in the direction of trying to develop accessibility expectations into our collection development policies and procedures. However, we have to balance accessibility concerns with ensuring that the disciplines we support have the scholarly resources they need to be competitive in their respective fields. Institution has new procurement rules regarding accessibility of purchases. The libraries acquisitions fall outside of that workflow. No official policy, but we include accessibility language in licenses when possible. Staff not currently trained. The Libraries Accessibility Working Group recommended integrating a statement on accessibility into the collection development policy. This is a developing area for us. We participate in the Big Ten Academic Alliance’s initiative to develop standard license language regarding accessibility for database purchases and renewals. We are currently developing a process for integrating accessibility procedures into our acquisitions process. We are currently discussing a project to review and revise all collection development policies and procedures so this may be addressed as part of that. We are in the midst of adding a statement but it is not yet in place. We are just starting to incorporate accessibility requirements into our collection development policies and procedures. Has been done sporadically in the past. We do not have a formal collection development policy. We don’t actually refer to it in our collection development statement. The statement is general in scope and doesn’t allow for a lot of detail. We have not integrated accessibility procedures into our collection development policy. That information is provided under accessibility services. 26. Which, if any, of the following criteria does your library use for web accessibility testing? Check all that apply. N=57 Level AA Conformance to WCAG 2.0 38 67% Section 508 Compliance 34 60% Institution standards 30 53% Level A Conformance to WCAG 2.0 21 37% Level AAA Conformance to WCAG 2.0 7 12% Other criteria 14 25% Please briefly describe the other criteria. N=14 Accessibility for Ontarians with Disabilities Act (AODA) http://accessibility.arl.org/standards-best-practices/#technical-standards Level AAA are tested and corrected but are not top priority. Most probably WCAG also, I just don’t know which level. Our web content and User Experience designers check the ADA-related criteria based on institutional web. Proper alt text in html code making sure color alone is not used to convey info color contrast

Previous Page Next Page

SPEC Kit 358: Accessibility and Universal Design (May 2018) resources

41 SPEC Kit 358: Accessibility and Universal Design WAVE, aXe, Deque products (WorldSpace, Attest), manual testing, screen readers, voice recognition software, color contrast checkers WAVE, Developer Tools WAVE, FAE UNL ChromDevTools, aXe, Totally, Funkify, NoCoffee WAVE, paciello colour contrast analyzer, NVDA (mostly), JAWS (not as much), manual/look at code, Adobe Acrobat PDF checker Wave, Web Sheriff Wave, WebAIM Color Contrast Checker WAVE: Web Accessibility Evaluation Tool, Web Developer Toolbar, WebAIM Contrast Checker, JAWS Screen Reader (although not recently), Checklists provided by our institution (based on WCAG 2.0 standards) WC3 accessibility checker Web Content Accessibility Guidelines 2.0, automated testers (WebAIM WAVE, A Checker), manual testing (i.e., testing for keyboard access), screen readers (NVDA, Chromevox), colour contrast checkers (i.e., WCAG contrast checker, Snook.ca), user testing UNIVERSAL DESIGN 28. Has library staff received training on Universal Design principles? N=64 Yes 35 55% No 29 45% If yes, who provided the training? Check all that apply. N=35 Attendance at conferences, symposia, etc. 26 74% Our parent institution 12 34% An outside training provider 9 26% Other provider 12 34% Please specify the other provider of training on Universal Design principles. N=12 A workshop was presented by external subject experts. Architectural firm working on library renovation. Not specifically formal training, but information is provided throughout the renovation process. Librarian who is trained/well versed in UDL. Library and Office of Disability Services staff Library staff committees Library staff experts Library staff in the Accessibility and Learning Technologies working group Only library staff and faculty who attend some conferences that may have topics on universal design principles.

Previous Page Next Page

Page 1Survey Results click to expand contents

Page 47Representative Documents click to expand contents

Page 48Services, Facilities, and Technology click to expand contents

Page 91Statements click to expand contents

Page 100Policies click to expand contents

Page 117Resources click to expand contents

Page 132Job Descriptions click to expand contents

Page 147Selected Resources click to expand contents

SPEC Kit 358: Accessibility and Universal Design (May 2018) resources

All section downloads (PDF) click to expand contents

Free Attachments

Extracted Text (may have errors)

Help

loading

SPEC Kit 358: Accessibility and Universal Design (May 2018) resources

SPEC Kit 358: Accessibility and Universal Design (May 2018) resources