PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding
Screen Reader support
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 5.4k
- Forks
- 2.4k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 26
Description
Check for duplicates
- I've checked for duplicate issues by using the search function of the issue tracker
Is your feature request related to a problem?
I'd like to be able to read the path of building community fork using my Screen Reader, but this is currently not supported.
Describe the solution you'd like
I'd like to be able to open the program and have it read with my screen reader NVDA, found here https://www.nvaccess.org/download/
I understand this may not be doable depending on the program language being used. It may not even be a priority even if it is possible to make the program accessible to the totally blind. I'd appreciate if someone could look into it though, as most people use these in their build guides and it's impossible for me to either plan out a build or look at one that's already premade. Thank you for the consideration!
Describe alternatives you've considered
I suppose another solution would be to export the skill tree in a readable format? Text, spreadsheet, etc. Really, as long as I could look at the tree and plan things out, that's all I'm looking for.
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by identifying how the Lua program presents its interface and whether it can expose controls and skill-tree information to NVDA. The issue names no files or tests, so first map the UI entry points and investigate the proposed readable skill-tree export as an alternative. Done means a blind user can navigate the program or read and plan a build through an accessible output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- accessibility, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100