This project was conceived in order to explore the possibility of micro professional development for computer science faculty with the goal of helping them incorporate accessibility topics in their courses. The version as of October 13, 2018 is currently hosted at https://homes.cs.washington.edu/~laurav4/access/. This work resulted in a publication at SIGCSE:
Teaching Accessibility: A Design Exploration of Faculty Professional Development at Scale Saba Kawas, Laura Vonessen, and Andrew J. Ko (2019) ACM Technical Symposium on Computer Science Education (SIGCSE), Research Track, to appear. Describes and evaluates a vision for teaching higher education CS faculty how to integrate accessibility topics into their classes, discovering many personal and organizationl barriers to adoption.
- build/
- content-media/
- slides/
- index.html
- custom.css
- .htaccess
(although technically speaking I think at the moment the 'slides/' directory is not used)
python server.py
Note that this app is written using ReactJS
- app.js controls which view people see. It should give you some idea of the architecture
- At the moment, the "course" view (see course.js) only shows the first topic (see json/course.json) of each course. A topic will show its argument (this depends on the course, so it's stored in json/course.json), then a list of subtopics determined by the course's topic "flavor" (this was based on the idea that an accessibility topic like "exposing structure" would have a different set of topics in, say, a web dev class than an HCI class). The subtopics (json/subtopics.json) (presented as specified in lotile.js) in particular have a field "material" which has as its value the html to be presented to instructors.
- Sorry it's confusing but maybe this info helps a bit?
npm run build
npm run watch