Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Resource Entry Macro

...

Notes

  • Handling inquiries seeking "situated" information (relevant to context)
  • Starting simple - gathering stuff onto a wiki page. Our own resources and from partners.
  • Questions
    • What questions do our communities have?
    • What kind of resources do we have or recommend?
    • How do we encourage the use of this knowledge resource? (i.e. formality and process)
  • Inclusive Design, Co-Design, and Co-Creation Resources
  • https://sojustrepairit.org/resources.html
  • Inclusive Design Guidelines - Research
  • What do we know already and how did we describe them for previous audiences?
  • "a wonderful collaborative mess of stuff"
    • "Draw from the pool"
  • Maybe turn this into a gist so that people can comment and edit?
  • Coordinate with OCAD librarians who publish our scholarly work
  • Shared links and articles via IRC chats
  • Share recorded community meetings via YouTube (and caption first)
  • Summaries of books that we find useful
  • Cherry pick from this stockpile and pull it into another organization for other projects (someone in the project can do the annotation and curation)
  • What things do you draw from this pool for?
    • Links and descriptions or keywords to be able to find it later
    • What sort of workflow each person has to use this for?
    • What project it was for, if it was our own, where we sourced it from if it wasn't ours, tagging/metadata to describe resources in general in order to retrieve them
      • if it applies to specific sectors (which would require specific resources)
  • Make an open Zotero group for anyone to join (https://www.zotero.org/groups/2086760/inclusive_design?)
  • Zotero, are.na, or Mendeley
  • Use it day-to-day, reflect on how to use it, how often to use it
  • a general approach to organizing resources:
    • three separate, but related concerns:
      • archiving of IDRC research artefacts, which we will work with the OCAD library to help with

Racial bias test from Harvard:

https://implicit.harvard.edu/implicit/user/agg/blindspot/indexrk.htm

Where to start -- making an accessible website:

https://wiki.fluidproject.org/display/fluid/Making+an+Inclusive+and+Accessible+Website

List of resources for Edify (OER and EMS context)

Learning simulations and interactive content (Learning content)


https://gist.github.com/waharnum/83abbef3f7ec2f850b9add43b62edd8a

CMHR Inclusive Accessibility Guide - design of inclusive spaces for exhibits and galleries

Bodies in Translation Toolkit

stuff to add content for

Inclusive Volunteering Guide and tip Sheets (english and french on volunteer.ca)

Outside-In workshops & feature topics (housed on http://outsidein.tigweb.org/

SNOW resources (and possibly workshops–these have a fee)

Our Doors Are Open Guide for Accessible Congregation (will be available soon in English and French on https://opendoors.idrc.ocadu.ca/)



Testing Tools:

Headings Map Firefox plugin

HTML Validation (Nu HTML Checker) + WCAG only parsing bookmark  (WCAG 2.0 parsing error bookmarklet)

Colour contrast evaluators (TPG Contrast Analyser)

Zoom TextChrome extension andZoom PageFirefox Add-On.

Accessibility evaluators (AChecker,WebAIM WAVE,FAE)

Firebug plugin for Firefox

Developer Toolbar plugin for Firefox

WAVE Toolbar extension for Chrome

Screen reader (e.g.NVDA,JAWS, for Windows;

  VoiceOver for Mac OS, iOS)

Readability-Score

Automating Accessibility Testing:

...

Examining the Accessibility API:

Inspector (Windows) andAccessibility Inspector

(OS X) are system tools for graphically examining

the Accessibility API; the FirefoxDOM Inspector

is also useful for this.

Accerciser for Linux.

Communities of Practice

Web Accessibility Initiative,WebAIM and theweb-a11y Slack group are open groups for discussing web accessibility topics.

...

Some Useful Articles and Essays and Books

”Writing CSS With Accessibility In Mind” by Manuel Matuzovic

“Making An Inclusive and Accessible Website” (IDRC resource)

“Accessibility APIs: A Key To Web Accessibility” by Léonie Watson & Chaals McCathie Nevile

...

A Web for Everyone - Sarah Horton & Whitney Quesenbery 

Becoming Human - Jean Vanier

...

Web Specifications and Related Best-Practices

...