Skip to content

Add a product vision and guiding principles document.#15022

Merged
michaelDCurran merged 11 commits into
masterfrom
productVision
Jul 10, 2023
Merged

Add a product vision and guiding principles document.#15022
michaelDCurran merged 11 commits into
masterfrom
productVision

Conversation

@michaelDCurran

Copy link
Copy Markdown
Member

Provide a product vision statement and guiding principles document for NVDA.
The goal of this document is to clearly define the reason NVDA exists, who it helps, what it tries to achieve, and how it does it.
It contains:

  • A vision statement: the state of the world we are trying to get to by creating this product.
  • A product description: a clear description of what the product is, who it helps and who is creating it.
  • Guiding principles: a list of objectives, each containing subpoints describing how they are achieved.
    Community feedback is very much welcome.
    This pr will remain as a draft for receiving feedback until July 1, at which time it will be marked for approval / mergin

Comment thread product_vision.md Outdated
Comment thread product_vision.md Outdated
Comment thread product_vision.md Outdated
Comment thread product_vision.md Outdated
Comment thread product_vision.md Outdated
Comment thread product_vision.md Outdated
Comment thread product_vision.md Outdated
Comment thread product_vision.md Outdated
Comment thread product_vision.md Outdated

## Product description
NVDA (NonVisual Desktop Access) is software that allows blind and vision impaired people to independently interact with the Windows Operating System and popular third party applications by outputting content in either synthetic speech or via a refreshable Braille Display.
Developed by NV Access in partnership with a dedicated open source community, NVDA enables blind and vision impaired people to increase their chances at education and employment, and to make a contribution to society.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is perhaps more of a political question - but I am interested to know thoughts on rephrasing "make a contribution to society" to "participate within society".
The phrase "contribute to society" is also used in the first sentence of the product vision.

The difference being an expectation of contributing / performing work, which might not be suitable to all users.
Lowering barriers for employment and education is great - but I've also heard user stories about NVDA aiding participation in society in other ways, e.g. social platforms.

Maybe this can be a separate added sentence rather than rephrasing this one, mentioning that NVDA aims to enable users to participate in society, outside education and employment.

@nvdaes nvdaes Jun 19, 2023

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I strongly agree with @seanbudd. Participation is related to something much more active than productive contribution, which may not be possible for everyone due to expectations and considerations about what productivity is. Contribution sounds like to give something to a given social structire, and participation seems more precise meaning action,not just accepting and helping.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some good points here.
As context, ever since the beginning Jamie and I have always said "contribute to society" as we believe that everyone has a right to contribute to society, though some may require some extra tools to do so.
Also note that the statement says "allow", I.e. we are allowing people to contribute if they wish, not forcing or expecting them to.
"Participate" may be a more acceptable word. What are your thoughts @jcsteh ? I think both have their own valid need. "participate in and or contribute to society" is what I would want, but perhaps "participate" covers both enough.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an interesting question. I've always used the word "contribute" because I strongly believe that everyone has a right but also a responsibility to contribute to society in some way. Historically, even where people with disabilities might not have been excluded from participating in certain aspects of society, there were more often excluded from contributing because they didn't have the right tools or because they weren't given the right opportunities. I believe this also created a situation where this norm became so firmly established that even where opportunities and tools became available, some people with disabilities didn't contribute (and perhaps didn't even feel they should have to) even though they could have. Given the right tools and opportunities, I don't think anyone should be excluded from this responsibility or the rights that come with it. Reflecting on this, I do realise this stance comes to some extent from a position of privilege. Just because I have opportunities doesn't mean that everyone does.

Also, it's worth noting that contributing to society doesn't necessarily mean traditional contribution. You don't have to work a paid job and pay taxes to contribute. Perhaps you volunteer where it's needed most, etc.

All of that said, I think it's reasonable to say "participate in and contribute to society". I don't think I'd want to drop contribute to - I still think this is important for all the reasons outlined above - but adding "participate" makes it clear that we think both are important. As @michaelDCurran noted, "enables" also makes it clear that we want to enable these things, but that we can't force or require our users to do them.

Comment thread readme.md Outdated
Several small typos
Comment thread product_vision.md
@@ -0,0 +1,65 @@
## Product Vision
A world where blind and vision impaired people can independently and fully interact with the Windows Operating System and popular third party applications, enabling them to contribute to society, no matter their language, location or economic status.
Blind and vision impaired people are empowered to control their own destiny and ensure this vision, through being able to significantly contribute to the technology that makes this possible.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that under-represented people like deaf and blind should be mentioned too.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree we must consider deaf-blind users always. I welcome any ideas on how that could be worded.
I would suggest though that The vision statement should continue to target just one group. So far it is "blind and vision impaired people", which of course is a superset containing "deaf-blind". So Deaf-blind people are certainly not excluded here.

  • Should we make the group more explicit and say "blind, vision impaired, and deaf-blind"? Sounds very clunky and confusing to me.
  • Can we extend "language, location and economic status" to include "abilities" or "other sensory abilities"?
  • Should we add a third sentence talking explicitly about ensuring that blind and vision impaired people of all abilities are included?
  • What about motor and cognitive abilities?
    The vision statement can certainly be a perfect world we strive towards, but it also should be attainable, and not so large that we could never manage it.
    How ever we improve this statement, we will also need to ensure it is backed up by the guiding principles. E.g. if we do acknowledge motor abilities, then we should add voice input to the multimodal goal. Which although is the right thing to do, we also commit the project to ensuring that voice input is actually available.
    Thoughts anyone?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

• Should we make the group more explicit and say "blind, vision impaired, and deaf-blind"? Sounds Sounds very clunky and confusing to me.

I agree: this is confusing and redundant.

Can we extend "language, location and economic status" to include "abilities" or "other sensory abilities"?

I think we can extend "language, location and economic status", but I prefer sensory characteristics instead of abilities, since characteristic sounds more qualitative instead of something measurable in terms of numerical values. Anyway I'm not a native English speaker.

What about motor and cognitive abilities?

I thought about this too, and even mental or psichological states, not necessarily, but also mental illness. In Spain usually it's distinguished between cognitive and psichosocial (previously named mental) disabilities. I understand that NVDA itself may not contain specific code for mental abilities, but the code ofconduct aims to decrease stress, so I think that maybe mentioned in this principles.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have tried to address your points in my last commit. However, I have chosen to keep with the word 'abilities', as I believe that is still the most suitable word in English.
I removed language, location and economic status from the first sentence, and moved it to its own third sentence, extending it to include sensory, physical, cognitive, and mental abilities. I also added a specific example to the multimodal section of the guiding principles, which specifically mentions deaf-blind users being able to use NVDA with Braille alone.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For me is good. Thanks.

@nvdaes

nvdaes commented Jun 19, 2023

Copy link
Copy Markdown
Collaborator

Also, I think that, somewhere, collaboration between blind or impaired visual people and sighted people should be mentioned. For example, sometimes I may use focus highlighting capabilities of NVDA to request help or explain what I'm reading to my sighted colleagues at work. Also, testers may be mentioned as possible users of NVDA, which making more accessible products are also fostering these principles. So, speech viewer, braille viewer and visual aids maybe mentioned.

Co-authored-by: Sean Budd <sean@nvaccess.org>
@seanbudd seanbudd marked this pull request as ready for review June 19, 2023 07:33
@seanbudd seanbudd requested a review from a team as a code owner June 19, 2023 07:33
@seanbudd seanbudd self-requested a review June 19, 2023 07:33
@seanbudd seanbudd marked this pull request as draft June 19, 2023 07:33
@michaelDCurran

michaelDCurran commented Jun 19, 2023 via email

Copy link
Copy Markdown
Member Author

@nvdaes

nvdaes commented Jun 19, 2023

Copy link
Copy Markdown
Collaborator

I agree that collaboration with sighted people should be mentioned. E.g.
focus highlight. Sounds like it should be its own goal with subpoints.

As for using NVDA for testing: I was hesitant to mention it it as it is
certainly not to do with the primary target group, and I would never
want features of a testing tool to take priority or sacrifice the
primary goal of providing independent access. However, maybe we could
add to or slightly reword the compliance goal, to include being used by
app / web developers to use as a tool to verify.

I agree.
Also, in goals maybe mentioned that NVDA will provide accurate information about the operative system. For example, recently I read someone complaining about NVDA not providing info regarding clipboard gestures like copy, and reasons are explained in issue #553 , but sometimes people can make dismissive comments without taking account this goal.

@Brian1Gaff

Brian1Gaff commented Jun 19, 2023 via email

Copy link
Copy Markdown

@AppVeyorBot

Copy link
Copy Markdown

See test results for failed build of commit b01e8040af

Comment thread product_vision.md Outdated
Co-authored-by: Sean Budd <sean@nvaccess.org>
@michaelDCurran michaelDCurran marked this pull request as ready for review July 9, 2023 22:43
…rences' in main statement, and remove goal in subpoint..
…he first sentence down to its own third sentence, also including sensory, physical, cognitive and mental abilities. Also added a specific example to the multipmodal section of the guiding principles to call out abiility for a deaf-blind user to use NvDA with Braille alone.
@AppVeyorBot

Copy link
Copy Markdown

See test results for failed build of commit 606775b04b

@michaelDCurran michaelDCurran merged commit 03033ba into master Jul 10, 2023
@michaelDCurran michaelDCurran deleted the productVision branch July 10, 2023 08:20
@nvaccessAuto nvaccessAuto added this to the 2023.2 milestone Jul 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants