Skip to content
Snippets Groups Projects
Commit 0abe2426 authored by varkon256's avatar varkon256
Browse files

fixed typos and revised date for final project

parent f151f595
No related branches found
No related tags found
6 merge requests!12Accessibility website jen summer work,!9Q access 24 sp,!8Q access 24 sp,!5Latest update from Spring 2023,!4Latest update after pmp class,!3Updated content for week 3 and week 4 (week 4 still needs work)
......@@ -8,13 +8,13 @@ code: as5
assigned: May 5, 2021
due:
- <strong>Discussion post on canvas with ideas</strong> May 10, 2021
- <strong>email staff about final teams</strong> May 12, 2021
- <strong>submit one page abstract on canvas</strong> May 17, 2021
- <strong>submit slides on canvas and present your idea and approach in class for critique</strong> May 24, 2021
- <strong>Final presentations and deliverables due</strong> June 7,2021
- <strong>Email staff about final teams</strong> May 12, 2021
- <strong>Submit one page abstract on canvas</strong> May 17, 2021
- <strong>Submit slides on canvas and present your idea and approach in class for critique</strong> May 24, 2021
- <strong>Final presentations and deliverables due</strong> June 9, 2021
revised: April27, 2021
revised: April 27, 2021
objective: Make the world slightly more accessible
......@@ -26,16 +26,16 @@ Your final project will have three phases:
# Proposal
*Proposal*: Your proposal be a slide deck with 5 slides that describe your
- What access gap are you trying to address?
- promise: How the world will be better based on your project
- obstacle: Why we don’t have this already.
- solution: How you will achieve the promise. This will most likely be primarily technical, such as a novel device.
- related work: It should also include a related work section with at least 5 references showing some evidence for the importance of this problem. This evidance should be informed by perspectives or your end users, people with disabilities.
- timeline: Finally, it should include a timeline showing that this is feasible.
- Promise: How the world will be better based on your project?
- Obstacle: Why we don’t have this already?
- Solution: How you will achieve the promise? This will most likely be primarily technical, such as a novel device.
- Related work: It should also include a related work section with at least 5 references showing some evidence for the importance of this problem. This evidence should be informed by perspectives or your end users, people with disabilities.
- Timeline: Finally, it should include a timeline showing that this is feasible.
*Development*: We will check in on projects in part of class and/or office hours on a weekly basis to help provide guidance about progress on the milestones laid out in your timeline
# Midterm Writeup
Midway through the project you will turn in a brief update to your project. This should included an up-to-date written version of your promise, obstacle and solution (1-3 paragraphs) and a related work section, also updated based on feedback (3-4 paragraphs). The total should be less than a page long.
Midway through the project you will turn in a brief update to your project. This should included an up-to-date written version of your promise, obstacle and solution (1-3 paragraphs) and a related work section, also updated based on feedback (3-4 paragraphs). In total this should be less than a page long.
# Final Project Writeup
The final 2-page report should be in the 2-column [CHI template format](https://chi2020.acm.org/authors/chi-proceedings-format/)
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment