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)
@@ -10,9 +10,12 @@ due: March 31, 2021 5PM Pacific
revised:February 15, 2021
objective:reflect on your motivation for wanting to aquire accessibility as a skill
---
* TOC
{:toc}
# Learning Goals
The goal of this activity is to reflect on your motivations for wanting to aquire accessibility as a skill, and help the course staff understand the same so that we can do our best to cater to your learning objectives.
objective:Fix screen reader bugs; Contribute to the accessibility Community
---
* TOC
{:toc}
# Learning Goals
The goal of this activity is to
- Learn more about how screen readers work
- Be a contributor to the accessibility community
- Get direct experience with the relation between web accessibility best practices and screen reader behavior
# Overview
People who are blind or visually impaired (BVI) access computers through screen readers. Simply put, screen readers are software that render the graphical user interface in audio (synthesized speech and sounds) or Braille (using a refreshable braille display). There are different types of screen readers, that run on a variety of platforms; from desktops, to smartphones, to smart-watches to smart speakers. One such screen reader is the Non Visual Desktop Access (NVDA) screen reader, a free, open source screen reader for windows. As per the [WebAIM: Screen Reader User Survey #8 Results](https://webaim.org/projects/screenreadersurvey8/), NVDA is the most used screen reader among respondents.
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 BVI developers so they are your target audience too!)
To reduce the complexity of contributing to an open source project in a short timeframe, 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. If you are not a screen reader user, you may not fully understand why a user needs to comment on such issues. You can find the full list of issues below. Once you decide the github issue that you would like to work on, please enter the information in this spreadsheet, along with a few-sentence description of how you think fixing the issue you picked would make the software more usable. This is to ensure that multiple teams are not picking the same github issue. So please pick a different issue if the issue you were interested in has been picked by another team. The course staff will go through your list of selections. Please do not start posting on the issues until this phase has completed.
Once you receive approval for the issue you’ve picked, you will be reaching towards your solution in phases. Note that your grade is distributed across phases, and if you are unable to reach a stage where you are unable 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.
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 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
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)
3.[Report status of screen curtain at startup when "Play a sound when toggling screen curtain" is disabled. · Issue #10692](https://github.com/nvaccess/nvda/issues/10692)(bug affecting screen reader announcement of screen curtain status. Picked up by a developer, but abandoned).
4.[Add script for aria figure to input gestures and give the user the possibility to turn off reporing of this role in document formating settings · Issue #10826](https://github.com/nvaccess/nvda/issues/10826)(feature request to make NVDA announcement of “figure” optional.
5.[Shorten "out of element" message #10446](https://github.com/nvaccess/nvda/issues/10446)
6.[Selection not announced when jumping to Top/Bottom of Page · Issue #5549](https://github.com/nvaccess/nvda/issues/5549)
7.[aria-labelledby element gets read twice #10512](https://github.com/nvaccess/nvda/issues/10512)(potentially a blocker on chrome?)
8.[Grid cells with focusable controls get read twice #10096](https://github.com/nvaccess/nvda/issues/10096)(abandoned, and potentially a spec conformance but annoying behavior)
