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)
@@ -32,13 +32,14 @@ People who are blind or visually impaired (BVI) access computers through screen
In this homework, you will be fixing a bug in the NVDA screen reader. Your fix should improve the usability of the NVDA screen reader for its intended audience. (remember, NVDA is developed by a huge community of developers who may be BVI so they are your target audience too!)
To reduce the complexity of contributing to an open source project in a short time frame, we curated a list of potential github issues that you could fix. You are also free to pick other open issues from the NVDA github repository. We however recommend refraining from issues with high complexity or issues where a consensus has not been reached.
To reduce the complexity of contributing to an open source project in a short time frame, we curated a list of potential github issues that you could fix. You are also free to pick other open issues from the NVDA github repository. We however recommend refraining from issues with high complexity or issues where a consensus has not been reached. You can find the full list of issues below.
Once you decide the github issue that you would like to work on, please join the corresponding [group on Canvas](https://canvas.uw.edu/courses/1465814/groups#tab-122183). You may start working *individually* on a solution right away, but the group is there to share ideas and for phase 1's handin.
You can find the full list of issues below. Once you decide the github issue that you would like to work on, please email the class, along with a few-sentence description of how you think fixing the issue you picked would make the software more usable. Note that you should aim to reach a state where you could submit a fix; but it is not required that it be accepted. reach a stage where you are able to push code to the NVDA repository due to the delays at the NVDA maintainer's end to merge your code, or any equivalent reason, you will not lose points as long as you are able to explain the series of events that lead to the outcome.
# NVDA Issues
You will join a [group of your choice on Canvas](https://canvas.uw.edu/courses/1465814/groups#tab-122183) based on which issue you wish to address. You may start working *individually* on a solution right away, but the group is there to share ideas and for phase 1's handin.
1.[NVDA announces "Article" before every article while browsing the articles via quick keys #11103](https://github.com/nvaccess/nvda/issues/11103)
2.[Failing the checkPot step should be more obvious. #10928](https://github.com/nvaccess/nvda/issues/10928)
...
...
@@ -51,17 +52,30 @@ You will join a [group of your choice on Canvas](https://canvas.uw.edu/courses/1
## Phase 1: Jointly prepare solution approach submission for NVDA (only for us)
You will work as a group to prepare a sollution approach, proposing one or multiple ways of fixing a bug to improve the user experience for NVDA users. Please keep in mind that you should consider the oppinions expressed by the NVDA user community through comments on the github issue of your choosing. You will not submit these to NVDA; you will submit these proposals as a group to [this Canvas Assignment](https://canvas.uw.edu/courses/1465814/assignments/6267341) for review by the course staff. You may start communicating with NVDA after receiving approval from the staff.
You will work as a group to prepare a solution approach, proposing one or multiple ways of fixing a bug to improve the user experience for NVDA users. To do this you should all try to replicate the issue and think individually about solutions. Then summarize your results in a group-constructed document.
You will not submit these to NVDA; you will submit these proposals as a group to [this Canvas Assignment](https://canvas.uw.edu/courses/1465814/assignments/6267341) for review by the course staff.
Your group may start communicating with NVDA after receiving approval from the staff. Please keep in mind that you should consider the opinions expressed by the NVDA user community through comments on the github issue of your choosing.
## Phase 2: the solution
This will be a ten minute presentation re-capping your first-phase, and:
You should work individually to try to solve the issue you chose.
You will also give a ten minute presentation re-capping your first-phase, and:
- What was your planned solution, and how did your solution differ from your plans?
- Why did your plans have to differ?
- If you are unable to fix the issue, why? E.g. disagreement within the community, etc.
You will need to submit accessible slides to [this canvas assignment](https://canvas.uw.edu/courses/1465814/assignments/6148838). Please [make your presentations accessible, and present accessibly](http://www.sigaccess.org/welcome-to-sigaccess/resources/accessible-presentation-guide/)(here is [a short video](https://www.youtube.com/watch?v=L9TxhGv91kc) that provides some guidance)
## Optional Phase 3: Submitting your solution to NVDA
If your approach is approved by the NVDA community, you and any other group members who use the same approach will have the opportunity to actually submit the best of your solutions.
## NVDA setup and other pre-requisites
You will need a Windows computer running Windows 10 and python 3.7 (32-bit) to install NVDA. If you do not have a Windows machine, please reach out to us as soon as possible. We have a limited number of machines that can be accessed remotely. The instructions to build NVDA are in the [NVDA github repository readme](https://github.com/nvaccess/nvda). Please also be sure to [read the contributing guide](https://github.com/nvaccess/nvda/wiki/Contributing).