- Improving the accessibility of a [VS Code plugin for code tours](https://github.com/cclaridad/codetour)
- Creating [tactile schematics](https://www.hackster.io/monica/creating-tactile-schematics-using-fritzing-5b47f8) for circuits
- Making [markdown accessible](https://github.com/jaedong98/accessibility4md)
- Addressing [open issues](https://github.com/odilia-app/odilia/pulls?q=is%3Apr+is%3Aclosed+author%3Asamtay) for a free and open source screen reader, [odilia](https://github.com/odilia-app/)
{% enddetails %}
In this phase of the final project, you will present a complete *final* proposal for your idea to the class.
See the [Proposal](projects-proposals.html) and [Checkin](project-checkpoint.html) for more information on project goals.
In this phase of the final project, you will present a complete *final* report on yoru project
## Learning Goals / Competencies
This homework may contribute to
This homework may contribute to any competency (you tell us which ones you want assessed, individually)
- Disability Awareness and Justice (including Disability Justice Framing; Finding First Person Accounts)
- Accessibility Compliance (including Accessibility Problem Fixes; Automated Checking (if you turn in relevant UARS); AT based Checking (if you turn in relevant UARS))
- Accessible Media and Documents (including Accessible Document Creation; Accessible Presentation Deck; Accessible Presenting; Image Description).
- Your participation grade, as a percentage of completeness (all required parts are present)
## Length & Difficulty
We do not have details on how long this single piece of the final project usually takes students. However, overall students report a median of 7.5 hours per week plus meetings during the four weeks of the project. Some things students commented on regarding the project include:
- "I appreciate the open-endedness of this project. It gives a good opportunity to apply what we have learned, combined with the knowledge we have brought to this course."
- "I really enjoyed working with [disabled mentor]"
- "I like how open ended the project is, and it made for a really interesting last session with a wide variety of presentations."
- "Learned a lot through the project"
# Details
## 0. Work on your final project
You should work to meet the goals you set out in your [Project Checkpoint](project-checkpoint.html). Make sure to leave sufficient time for validation and writing up your project.
You should work to meet the goals you set out in your [Project Checkpoint](project-checkpoint.html). Make sure to leave sufficient time for validation and creating a webpage for your project.
Along the way, you will participate in checkpoints throughout the weeks of the final project. All team members are expected to attend such meetings.
In addition, please drop by office hours if you need guidance on any aspect of your project. The course staff can work with you on a case-by-case basis if you are unable to attend office hours and would like to meet at a different time.
## 1. Create Slides And Present Them
## 1. Create a Poster by Thursday 12/7 (HARD DEADLINE)
You will submit a poster to us by 12/7 bedtime (hard deadline). This is required so we can print it before the poster session. Here is a [UW page with poster templates](https://www.washington.edu/brand/templates/research-posters/). Please follow DO-IT's [guide to creating an accessible poster](https://www.washington.edu/doit/how-can-i-create-conference-poster-accessible-people-disabilities) when you do this.
You should start with these templates and add the following things:
1. Key basic information
a. A [CREATE logo](https://drive.google.com/drive/u/1/folders/1d7XCBCCrWdhcw3gLB_l50YaZgySatbgK)
b. a QR code that links to your website
2. The following headers:
a. What did you do
b. Why is it needed (including first person evidence & disability justice analysis)
c. Technical details of what you did including how you achieved goal and what software / platforms you used
d. How you validated the idea
e. What you learned & suggested questions ("Ask me about...")
## 2. Be prepared to talk about your poster at a poster session (REQUIRED)
You will submit, and present slides in-class. You will follow a similar format as your proposal 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. Your slides should include the following. Note that *update* are slides you have presented before and **new** are new content.
You should bring a demo with you to the poster session and be prepared to show what you did in addition to talking about your poster.
1.*update* What (at a high level) did <s>will</s> you do?
2.*update* What is your evidence for why this is needed? Includes your first person evidence and your disability justice analysis.
3.*update* Why don't we have this already? To answer this you will need to look at what we *do* have and explain why your idea isn't already solved
4.*update* Provide technical details. How did <s>will</s> you achieve your goals? What software/platforms did <s>will</s> you use? What did <s>will</s> you do yourself?
5.**new** Show us a demo!
5.*update* How did <s>will</s> you validate your idea and what were the results
6.**new** What are some things you learned from this effort? <s> Why is this feasible (timeline, etc)</s>
Presenting a poster accessibly is similar to giving an accessible talk -- you need to describe images visuals you are talking about on the poster. In addition, keep in mind the following points (quoted from Rua Williams' [Guide to Making Accessible Research Posters](http://www.ruamae.com/disability-advocacy/guide-to-making-accessible-research-posters/)
Presentation length TBD depending on the number of groups.
- "conversation during poster presentation times can be difficult for people who are Deaf, Hard of Hearing, have auditory processing issues, affected speech or expressive language, or use AAC to communicate."
- "As a presenter, keeping a notepad on hand to pass notes back and forth with interested attendees can help."
- "Also, remain patient and allow people with communication disabilities equal access to your time."
- Finally, "don’t assume someone is uninterested in talking to you based solely on their equipment or behavior. Any person who seems to linger around your poster deserves to be asked directly if they have questions or would like you explain the poster for them."
## 2. Create a web page
You will make a (minimum W3C Level A) accessible, public-facing web page. There are several simple options for you to host a public-facing page, we'll post more details about that.
Rua also recommends:
"While your poster should be informational enough to be of interest even when you aren’t present, don’t expect people to read the poster while you are standing there. Present it! When you are not there, consider leaving a way for people to ask questions, such as post-it notes, a Sli.do event, or even a twitter tag."
## 3. Create a web page
You will make a (minimum W3C Level A) accessible, public-facing web page. There are several simple options for you to host a public-facing page, we recommend [wordpress](https://www.codeable.io/blog/wordpress-accessibility/). [github](https://docs.github.com/en/pages/getting-started-with-github-pages/creating-a-github-pages-site) is also an option, again here you'll need to make sure you use an accessible theme.
You should also follow the writing guidelines put out by [SIGACCESS for writing about disability](https://www.sigaccess.org/welcome-to-sigaccess/resources/accessible-writing-guide/)
...
...
@@ -97,7 +92,6 @@ web page. In your video, you should present accessibly, verbally
describing important visual elements and events. Your video should
also include captions.
# Turnin
Your final set of deliverables are individual as competencies are assessed and submitted individually.
