---
# System prepended metadata

title: Untitled

---

## PR Midway Report

We have extensively looked at the issues available, including the ones labeled as good for new developers. There are unfortunately not a lot of opportunities for contributing language and documentation information. Due to the nature of NVDA, it was already important for them to have extensive documentation and guides for multiple languages in order to be as accessible as possible. We decided on [this issue](https://github.com/nvaccess/nvda/issues/10446) on shortening the length of a warning message when leaving a UI element, as it seemed like it could be a good first issue. 

We posted a message introducing ourselves and asking for permission to work on the issue, however, we have yet to receive a reply by a developer giving the go-ahead. As we cannot wait too long, we will try to contact other developers on the NVDA mailing list about this, to see if it is okay to start working on it anyways. The issue has already had some discussion, and seems to be something that the community is ultimately okay with implementing. Hopefully, we will be able to start working on it as soon as possible, and be able to contribute to NVDA.



## PR Final Report

As we did not hear back from any developers after posting a message on the issue, we decided to use the developer mailing list to see if we could get a response.
We finally received the go-ahead from a core developer to start working on both the aforementioned issue, as well as another issue we were considering.
Finally, there is a third issue which we created, but for which the implementation would not fit within the timeframe of the project.
All three issues will be discussed below.
In the end, contributing to NVDA was complicated by the fact that they were in the middle of a development cycle.
Additionally, they were dealing with a big backlog of issues and pull requests, so they were not very open to pull requests which are not bug fixes or maintenance issues.

### [PR (#12260): Shorten "out of element" message](https://github.com/nvaccess/nvda/pull/12260)

When browsing through various UI elements, NVDA often gives an announcement when the user enters and exits the element.
For example, it announces "out of table" when the user exits a table element.
This pull request shortens this message for various UI elements to a shorter and more intuitive one.
Some system tests also had to be modified to accommodate the changes.

### [PR (#12277): NVDA announces "Article" before every article](https://github.com/nvaccess/nvda/pull/12277)

When using quick keys to navigate articles on a web page, the article text/label should be announced first and then "article" should be announced after it in order to streamline the browsing process.
Otherwise users hear "Article" before a lot of element on a webpage such a headings and paragraphs.

### [Issue (#12261): Fix a load of linting issues](https://github.com/nvaccess/nvda/issues/12261)

When working on essay 3 about technical debt, we noticed that the NVDA codebase is full of linting issues that could easily be solved with an auto-formatter.
We decided to propose fixing (part of) the codebase this way.
We created an issue describing our idea and considerations and asking for feedback what parts of the code would be more important to fix quickly.

The issue generated a lot of discussion already in the 4 days since creation.
The discussion was about when would be the best time to do it, what order (entire codebase vs module by module vs issue by issue), whether this would be an issue for git blame practices, and how to handle potential conflicts with existing PRs.

It is clear that this issue could not be fixed within the timeframe of the course, in the first place because we started late on it, but also because issues in NVDA are discussed extensively over a long period before getting the heads-up.
The discussion shows much care for the development flow, with everyone agreeing that fixing linting issues will make it easier for new developers and new changes but it also interrupting existing change processes.
We will not be abandoning this issue after the course, if a consensus is reached on the approach, we will put effort into making it happen.
