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)
@@ -59,25 +59,33 @@ On May 23, 2021, you will submit a slide deck with six slides that describe you
# Final project deliverables
On June 9, 2021, you will turn-in the final set of deliverables. These are:
- a public-facing website containing a write-up of your project.
- a public-facing web page containing a write-up of your project.
- a 2-3 minute video about your project.
- a slide deck presenting your work.
- a presentation of this slide deck in the scheduled final exam time for your class (9 June, 2021 6:30-8:20PM).
## Website
## Slides
You will submit, and present slides in-class. You will follow a similar format as your milestone 1 presentations, but will focus more on your solutions. Presentation time will be decided based on group formation and number of projects. Please ensure that your submitted slides are accessible and that you are making best-effort to present accessibly while staying on-time.
## Video
You should create a brief, accessible, two-three minute captioned and audio-described video motivating your project and describing your solution.
## Webpage
You will make an accessible, public-facing webpage. There are several simple options for you to host a public-facing page. You can use github pages to host a one-page page (here is a [link to documentation](https://guides.github.com/features/pages/)). UW CSE also has resources to host pages; here is a [related FAQ](https://homes.cs.washington.edu/FAQ.html).
You will make an accessible, public-facing webpage. [Here is an example tool from Microsoft](https://accessibilityinsights.io/docs/en/web/overview/) that will help you check for accessibility of your page. [Here is an article](https://www.smashingmagazine.com/2020/08/accessibility-chrome-devtools/) talking about ways to do this using Chrome's DevTools. We recognise that it may not be possible to produce a website with zero accessibility bugs if you are using built-in frameworks; while that should be your goals when designing websites, we expect you to make your best effort and minimize accessibility bugs on your page for this submission. Your webpage should contain the following:
- A brief, three-five minute captioned video motivating your project and describing your solution.
- Text describing:
[Here is an example tool from Microsoft](https://accessibilityinsights.io/docs/en/web/overview/) that will help you check for accessibility of your page. [Here is an article](https://www.smashingmagazine.com/2020/08/accessibility-chrome-devtools/) talking about ways to do this using Chrome's DevTools.
We recognize that it may not be possible to produce a page with zero accessibility bugs if you are using built-in frameworks; while that should be your goals when designing pages, we expect you to make your best effort and minimize accessibility bugs on your page for this submission. You should follow the writing guidelines put out by [SIGACCESS for writing about disability](https://www.sigaccess.org/welcome-to-sigaccess/resources/accessible-writing-guide/)
Your page should contain the following:
- Embedd your video
- Text describing:
- Introduction– 1-3 paragraphs: Present the promise/ obstacle/ solution for your project— What is the problem you are solving and why is it important to solve it?
- Related Work– 1-3 paragraphs: Talk about relevant work that closely connects with your project.
- Methodology– about 3 paragraphs: What did you do in your project- what did you design or implement? What role did people with disabilities play in this, if any
- Disability Studies Perspective– 1 paragraph: How did a disability studies perspective inform your project?
- Learnings and future work -- 1-2 paragraphs: Describe what you learned and how this can be extended/ built on in the future.
You should follow the writing guidelines put out by [SIGACCESS for writing about disability](https://www.sigaccess.org/welcome-to-sigaccess/resources/accessible-writing-guide/)
There are several simple options for you to host a public-facing website. You can use github pages to host a one-page website (here is a [link to documentation](https://guides.github.com/features/pages/)). UW CSE also has resources to host websites; here is a [related FAQ](https://homes.cs.washington.edu/FAQ.html).
## Slides and presentation
You will submit, and present slides in-class. You will follow a similar format as your milestone 1 presentations, but will focus more on your solutions. Presentation time will be decided based on group formation and number of projects. Please ensure that your submitted slides are accessible and that you are making best-effort to present accessibly while staying on-time.