A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials


 

Dear NVDA community,

 

As I read messages on recent discussions, I realized just how much enthusiasm and concern people have over NVDA and its future. At the same time, it became clear to me that I and other developers and community elders need a day off and just listen to you all, as listening allows us to think about what others are saying and plan things accordingly.

 

But first, a humble opinion about surveys and other points:

 

First, when calls for the seventh Web AIM survey went out, I told people to not just do it to “increase” market share. I specifically told screen reader companies to not coerce users to do it, but let people take it out of their own willingness. This advice was to avoid a fiasco that happened with Web AIM 6 where AI Squared (now part of VFO) staff told Window-Eyes users to fill out the survey in mass numbers, which became a small controversy within the screen reading world, and to me, making Web AIM results no longer credible.

 

As some folks pointed out, Web AIM numbers depend on how many people fill it out and where they come from (and this is true of any surveys where word of mouth drives participation). The results also depend on demographics and other factors such as choices given, how the questions are worded, and overall objective. If one or more data points seems to be dominant, they can be either skewed or outliers, with the more extreme cases being termed “outliers” and they affect how the results are explicated (interpreted). Even skewed data, such as what I can perceive from some surveys including recent Web AIM iterations can affect statistical calculations to a point where it raises genuine questions about bias, credibility, and others (after all, success of statistics, particularly inferential statistics, depends on a representative sample or a close equivalent that allows researchers to approximate the real world, which is prone to errors if not done correctly such as misinterpretation, bad outliers, only some groups participating, not looking at things more deeply and what not).

 

One important thing to note is that Web AIM is a representative survey, thus the result in front of me could reflect reality. However, due to recent controversy, possible type I and II errors (false-positive and false-negative, respectively) and because of outliers and skewed data and participation, it does not truly reflect actual data, which is a point some folks here are trying to say and I concur with. My explication of Web AIM 7 is that, in some parts of the world, JAWS for Windows is more popular. However, given the fact that not all geographical regions are represented, I’d counter by saying that this is not a true representative sample that includes every continent, and if it did, the story would be different and will reflect reality a bit better (not a lot because there are other ways of skewing data such as filling it out on behalf of an organization, robotic fillers and so on). Coupled with the fact that Web AIM went through a major controversy recently that damaged its credibility somewhat, I would dare not trust Web AIM results again.

 

This leads to my second point: quantity versus quality. If NV Access went straight for quantity alone, they could have implemented all possible feature requests in hopes of boosting market share. The reality in front of us says otherwise: not all feature requests are here. Numerous factors contribute to this problem:

 

  • Lack of leading developers: in 2017, a long-time NVDA developer started working for another organization, and NV Access has been looking for his replacement ever since. Even if the replacement is found, it’ll take several months for him or her to become used to this community, learn about accessibility and how to interact with members, and earn our trust (it took Reef Turner a year to fully earn our trust). Folks can counter this by saying that there are countless contributors out there, but ultimately what gets into NVDA depends on pull requests and review time from NV Access.
  • Attitudes about open-source software from organizations: as some folks pointed out, there are prevailing attitudes about open-source in organizations that makes it a bit harder for NVDA to land on their computers, which allows developers to assess true needs of organizations through user feedback. Without valuable feedback from organizations (a quality one at that), we won’t see huger progress in NVDA development.
  • Outside attitudes about the NVDA community: from the inside, NVDA community is seen as a tight nit of enthusiasts who strives to make NVDA better every day. On the outside, however, we have a mixed bag of reputations, from admiration to honorable mentions to disdain. Every organization have these mixed reputations, especially more so for a community powered by technology such as Linux kernel developers, web browser vendors and web standards organizations, and even screen reader community. Not only we need to show that we are united inside, we need to showcase unity outside of this community.
  • Inside matters just as outside: public relations outside of NVDA community is important, but unity within an organization is just as important as public organizational face (I’ll address developer’s point of view below). What makes NVDA stand out is our unity despite coming from different circumstances and backgrounds.

 

Most of these point to quality, not quantity alone. In summary, quantity is important, but quality is just as important as how many people download NVDA 2017.4 between Christmas and New Year.

 

Lastly, in regards to organization internals, I’d like to address something I really wanted to say for the past few weeks: sometimes, I felt burnt out. My initial response to your enthusiasm over my audio tutorials was that I’ll ask for justifications for producing an updated version, seeing that there are countless free videos and tutorials out there. This was partly because I truly felt burnt out with academics, speech and debate competitions and what not (especially after a debate regarding a potential feature held not long ago), at one point telling myself that I’ll retire from the NVDA community sooner than later and feeling as though I carried important burdens on my shoulders. But you didn’t see that justification post; instead, I posted links to where you can download the 2018 version of my audio tutorial series. In effect, I’ve given up my Christmas holidays for this community, knowing that I needed a time to listen to you all and do something about it. All this was possible because of a simple act of listening and thinking about what the community means to me and what my work means to everyone. I’m committed to finishing Welcome to NVDA 2018 series before NVDA 2018.1 ships, with several addenda coming after that, all because of support from this community and outsiders. And I promise again: The Welcome to NVDA 2018 series was, and will remain, free for all. All I ask of you in return is donate to a cause that makes equal access to technology possible, especially during this holiday season and beyond.

 

I’m sure for many of you, my musings above are a bit hard to digest. Now you know why I don’t trust Web AIM survey results, quality is just as important as quantity, and read a confession from a community leader on his inner feelings. But there are two more things you need to know, something all of us needs to think about:

 

Community leaders won’t stay with you forever. In early 2017, I sensed that a long-time NVDA developer would leave this community for something better. Only I and others didn’t know until summer that it would be Jamie moving onto Mozilla Foundation.

 

I also felt, back in early 2017, that my active time with the NVDA community is slowly drawing to a close. I don’t know when it’ll happen, but I’ve been laying foundations for the next generation of developers and enthusiasts to take the lead. This is one of the reasons for setting up the devlearning subgroup, because I felt it is time for me and other leaders to teach NVDA internals and other concepts to the next group of community leaders and developers so they can bring NVDA to the next level and do more amazing things than I and others did (in my case, for the past five years).

 

Lastly, I sense a time when this community will face a sharp divide to a point where people will start questioning the merits of this community. I only told a select few earlier because it wasn’t right for me to disclose it early and for them to prepare a plan. The screen shade debate is, in fact, a sort of a preview of what is to come. One of the fundamental questions you will face at that time will be whether you still have your first love for NVDA, and whether you still have your original reasons for joining this community. The survival of this community at that time will depend on your ability to unite to face a difficult situation, even if that means facing possible splits. One thing you should NOT do at that time: ignoring new users and outside critics, because they are influential opinion leaders and are key stakeholders in NVDA’s future. One thing you SHOULD do though: listen to others and think critically.

 

Hope this makes sense.

Merry (early) Christmas,

Joseph


Pascal Lambert
 

Thank you Joseph and merry Christmas to you too.

Blessings

Pascal

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Saturday, December 23, 2017 12:26 PM
To: nvda@nvda.groups.io
Subject: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials

 

Dear NVDA community,

 

As I read messages on recent discussions, I realized just how much enthusiasm and concern people have over NVDA and its future. At the same time, it became clear to me that I and other developers and community elders need a day off and just listen to you all, as listening allows us to think about what others are saying and plan things accordingly.

 

But first, a humble opinion about surveys and other points:

 

First, when calls for the seventh Web AIM survey went out, I told people to not just do it to “increase” market share. I specifically told screen reader companies to not coerce users to do it, but let people take it out of their own willingness. This advice was to avoid a fiasco that happened with Web AIM 6 where AI Squared (now part of VFO) staff told Window-Eyes users to fill out the survey in mass numbers, which became a small controversy within the screen reading world, and to me, making Web AIM results no longer credible.

 

As some folks pointed out, Web AIM numbers depend on how many people fill it out and where they come from (and this is true of any surveys where word of mouth drives participation). The results also depend on demographics and other factors such as choices given, how the questions are worded, and overall objective. If one or more data points seems to be dominant, they can be either skewed or outliers, with the more extreme cases being termed “outliers” and they affect how the results are explicated (interpreted). Even skewed data, such as what I can perceive from some surveys including recent Web AIM iterations can affect statistical calculations to a point where it raises genuine questions about bias, credibility, and others (after all, success of statistics, particularly inferential statistics, depends on a representative sample or a close equivalent that allows researchers to approximate the real world, which is prone to errors if not done correctly such as misinterpretation, bad outliers, only some groups participating, not looking at things more deeply and what not).

 

One important thing to note is that Web AIM is a representative survey, thus the result in front of me could reflect reality. However, due to recent controversy, possible type I and II errors (false-positive and false-negative, respectively) and because of outliers and skewed data and participation, it does not truly reflect actual data, which is a point some folks here are trying to say and I concur with. My explication of Web AIM 7 is that, in some parts of the world, JAWS for Windows is more popular. However, given the fact that not all geographical regions are represented, I’d counter by saying that this is not a true representative sample that includes every continent, and if it did, the story would be different and will reflect reality a bit better (not a lot because there are other ways of skewing data such as filling it out on behalf of an organization, robotic fillers and so on). Coupled with the fact that Web AIM went through a major controversy recently that damaged its credibility somewhat, I would dare not trust Web AIM results again.

 

This leads to my second point: quantity versus quality. If NV Access went straight for quantity alone, they could have implemented all possible feature requests in hopes of boosting market share. The reality in front of us says otherwise: not all feature requests are here. Numerous factors contribute to this problem:

 

  • Lack of leading developers: in 2017, a long-time NVDA developer started working for another organization, and NV Access has been looking for his replacement ever since. Even if the replacement is found, it’ll take several months for him or her to become used to this community, learn about accessibility and how to interact with members, and earn our trust (it took Reef Turner a year to fully earn our trust). Folks can counter this by saying that there are countless contributors out there, but ultimately what gets into NVDA depends on pull requests and review time from NV Access.
  • Attitudes about open-source software from organizations: as some folks pointed out, there are prevailing attitudes about open-source in organizations that makes it a bit harder for NVDA to land on their computers, which allows developers to assess true needs of organizations through user feedback. Without valuable feedback from organizations (a quality one at that), we won’t see huger progress in NVDA development.
  • Outside attitudes about the NVDA community: from the inside, NVDA community is seen as a tight nit of enthusiasts who strives to make NVDA better every day. On the outside, however, we have a mixed bag of reputations, from admiration to honorable mentions to disdain. Every organization have these mixed reputations, especially more so for a community powered by technology such as Linux kernel developers, web browser vendors and web standards organizations, and even screen reader community. Not only we need to show that we are united inside, we need to showcase unity outside of this community.
  • Inside matters just as outside: public relations outside of NVDA community is important, but unity within an organization is just as important as public organizational face (I’ll address developer’s point of view below). What makes NVDA stand out is our unity despite coming from different circumstances and backgrounds.

 

Most of these point to quality, not quantity alone. In summary, quantity is important, but quality is just as important as how many people download NVDA 2017.4 between Christmas and New Year.

 

Lastly, in regards to organization internals, I’d like to address something I really wanted to say for the past few weeks: sometimes, I felt burnt out. My initial response to your enthusiasm over my audio tutorials was that I’ll ask for justifications for producing an updated version, seeing that there are countless free videos and tutorials out there. This was partly because I truly felt burnt out with academics, speech and debate competitions and what not (especially after a debate regarding a potential feature held not long ago), at one point telling myself that I’ll retire from the NVDA community sooner than later and feeling as though I carried important burdens on my shoulders. But you didn’t see that justification post; instead, I posted links to where you can download the 2018 version of my audio tutorial series. In effect, I’ve given up my Christmas holidays for this community, knowing that I needed a time to listen to you all and do something about it. All this was possible because of a simple act of listening and thinking about what the community means to me and what my work means to everyone. I’m committed to finishing Welcome to NVDA 2018 series before NVDA 2018.1 ships, with several addenda coming after that, all because of support from this community and outsiders. And I promise again: The Welcome to NVDA 2018 series was, and will remain, free for all. All I ask of you in return is donate to a cause that makes equal access to technology possible, especially during this holiday season and beyond.

 

I’m sure for many of you, my musings above are a bit hard to digest. Now you know why I don’t trust Web AIM survey results, quality is just as important as quantity, and read a confession from a community leader on his inner feelings. But there are two more things you need to know, something all of us needs to think about:

 

Community leaders won’t stay with you forever. In early 2017, I sensed that a long-time NVDA developer would leave this community for something better. Only I and others didn’t know until summer that it would be Jamie moving onto Mozilla Foundation.

 

I also felt, back in early 2017, that my active time with the NVDA community is slowly drawing to a close. I don’t know when it’ll happen, but I’ve been laying foundations for the next generation of developers and enthusiasts to take the lead. This is one of the reasons for setting up the devlearning subgroup, because I felt it is time for me and other leaders to teach NVDA internals and other concepts to the next group of community leaders and developers so they can bring NVDA to the next level and do more amazing things than I and others did (in my case, for the past five years).

 

Lastly, I sense a time when this community will face a sharp divide to a point where people will start questioning the merits of this community. I only told a select few earlier because it wasn’t right for me to disclose it early and for them to prepare a plan. The screen shade debate is, in fact, a sort of a preview of what is to come. One of the fundamental questions you will face at that time will be whether you still have your first love for NVDA, and whether you still have your original reasons for joining this community. The survival of this community at that time will depend on your ability to unite to face a difficult situation, even if that means facing possible splits. One thing you should NOT do at that time: ignoring new users and outside critics, because they are influential opinion leaders and are key stakeholders in NVDA’s future. One thing you SHOULD do though: listen to others and think critically.

 

Hope this makes sense.

Merry (early) Christmas,

Joseph


Lino Morales
 

Well put young man. I for appriciate what you for the NVDA community. Really you and Derrek bust your asses off despite you two doing the school thing. In future assuming the NV Access team will do future podcasts I suggest they do a meet the code contributors series. Of course people know you well, but their some who do indeed bust their ass and put out some dang good add-ons etc. and we should meet them via interviews. Again, thanks Joseph for your hard work and to you too Derrek.


On 12/23/2017 12:25 PM, Joseph Lee wrote:

Dear NVDA community,

 

As I read messages on recent discussions, I realized just how much enthusiasm and concern people have over NVDA and its future. At the same time, it became clear to me that I and other developers and community elders need a day off and just listen to you all, as listening allows us to think about what others are saying and plan things accordingly.

 

But first, a humble opinion about surveys and other points:

 

First, when calls for the seventh Web AIM survey went out, I told people to not just do it to “increase” market share. I specifically told screen reader companies to not coerce users to do it, but let people take it out of their own willingness. This advice was to avoid a fiasco that happened with Web AIM 6 where AI Squared (now part of VFO) staff told Window-Eyes users to fill out the survey in mass numbers, which became a small controversy within the screen reading world, and to me, making Web AIM results no longer credible.

 

As some folks pointed out, Web AIM numbers depend on how many people fill it out and where they come from (and this is true of any surveys where word of mouth drives participation). The results also depend on demographics and other factors such as choices given, how the questions are worded, and overall objective. If one or more data points seems to be dominant, they can be either skewed or outliers, with the more extreme cases being termed “outliers” and they affect how the results are explicated (interpreted). Even skewed data, such as what I can perceive from some surveys including recent Web AIM iterations can affect statistical calculations to a point where it raises genuine questions about bias, credibility, and others (after all, success of statistics, particularly inferential statistics, depends on a representative sample or a close equivalent that allows researchers to approximate the real world, which is prone to errors if not done correctly such as misinterpretation, bad outliers, only some groups participating, not looking at things more deeply and what not).

 

One important thing to note is that Web AIM is a representative survey, thus the result in front of me could reflect reality. However, due to recent controversy, possible type I and II errors (false-positive and false-negative, respectively) and because of outliers and skewed data and participation, it does not truly reflect actual data, which is a point some folks here are trying to say and I concur with. My explication of Web AIM 7 is that, in some parts of the world, JAWS for Windows is more popular. However, given the fact that not all geographical regions are represented, I’d counter by saying that this is not a true representative sample that includes every continent, and if it did, the story would be different and will reflect reality a bit better (not a lot because there are other ways of skewing data such as filling it out on behalf of an organization, robotic fillers and so on). Coupled with the fact that Web AIM went through a major controversy recently that damaged its credibility somewhat, I would dare not trust Web AIM results again.

 

This leads to my second point: quantity versus quality. If NV Access went straight for quantity alone, they could have implemented all possible feature requests in hopes of boosting market share. The reality in front of us says otherwise: not all feature requests are here. Numerous factors contribute to this problem:

 

  • Lack of leading developers: in 2017, a long-time NVDA developer started working for another organization, and NV Access has been looking for his replacement ever since. Even if the replacement is found, it’ll take several months for him or her to become used to this community, learn about accessibility and how to interact with members, and earn our trust (it took Reef Turner a year to fully earn our trust). Folks can counter this by saying that there are countless contributors out there, but ultimately what gets into NVDA depends on pull requests and review time from NV Access.
  • Attitudes about open-source software from organizations: as some folks pointed out, there are prevailing attitudes about open-source in organizations that makes it a bit harder for NVDA to land on their computers, which allows developers to assess true needs of organizations through user feedback. Without valuable feedback from organizations (a quality one at that), we won’t see huger progress in NVDA development.
  • Outside attitudes about the NVDA community: from the inside, NVDA community is seen as a tight nit of enthusiasts who strives to make NVDA better every day. On the outside, however, we have a mixed bag of reputations, from admiration to honorable mentions to disdain. Every organization have these mixed reputations, especially more so for a community powered by technology such as Linux kernel developers, web browser vendors and web standards organizations, and even screen reader community. Not only we need to show that we are united inside, we need to showcase unity outside of this community.
  • Inside matters just as outside: public relations outside of NVDA community is important, but unity within an organization is just as important as public organizational face (I’ll address developer’s point of view below). What makes NVDA stand out is our unity despite coming from different circumstances and backgrounds.

 

Most of these point to quality, not quantity alone. In summary, quantity is important, but quality is just as important as how many people download NVDA 2017.4 between Christmas and New Year.

 

Lastly, in regards to organization internals, I’d like to address something I really wanted to say for the past few weeks: sometimes, I felt burnt out. My initial response to your enthusiasm over my audio tutorials was that I’ll ask for justifications for producing an updated version, seeing that there are countless free videos and tutorials out there. This was partly because I truly felt burnt out with academics, speech and debate competitions and what not (especially after a debate regarding a potential feature held not long ago), at one point telling myself that I’ll retire from the NVDA community sooner than later and feeling as though I carried important burdens on my shoulders. But you didn’t see that justification post; instead, I posted links to where you can download the 2018 version of my audio tutorial series. In effect, I’ve given up my Christmas holidays for this community, knowing that I needed a time to listen to you all and do something about it. All this was possible because of a simple act of listening and thinking about what the community means to me and what my work means to everyone. I’m committed to finishing Welcome to NVDA 2018 series before NVDA 2018.1 ships, with several addenda coming after that, all because of support from this community and outsiders. And I promise again: The Welcome to NVDA 2018 series was, and will remain, free for all. All I ask of you in return is donate to a cause that makes equal access to technology possible, especially during this holiday season and beyond.

 

I’m sure for many of you, my musings above are a bit hard to digest. Now you know why I don’t trust Web AIM survey results, quality is just as important as quantity, and read a confession from a community leader on his inner feelings. But there are two more things you need to know, something all of us needs to think about:

 

Community leaders won’t stay with you forever. In early 2017, I sensed that a long-time NVDA developer would leave this community for something better. Only I and others didn’t know until summer that it would be Jamie moving onto Mozilla Foundation.

 

I also felt, back in early 2017, that my active time with the NVDA community is slowly drawing to a close. I don’t know when it’ll happen, but I’ve been laying foundations for the next generation of developers and enthusiasts to take the lead. This is one of the reasons for setting up the devlearning subgroup, because I felt it is time for me and other leaders to teach NVDA internals and other concepts to the next group of community leaders and developers so they can bring NVDA to the next level and do more amazing things than I and others did (in my case, for the past five years).

 

Lastly, I sense a time when this community will face a sharp divide to a point where people will start questioning the merits of this community. I only told a select few earlier because it wasn’t right for me to disclose it early and for them to prepare a plan. The screen shade debate is, in fact, a sort of a preview of what is to come. One of the fundamental questions you will face at that time will be whether you still have your first love for NVDA, and whether you still have your original reasons for joining this community. The survival of this community at that time will depend on your ability to unite to face a difficult situation, even if that means facing possible splits. One thing you should NOT do at that time: ignoring new users and outside critics, because they are influential opinion leaders and are key stakeholders in NVDA’s future. One thing you SHOULD do though: listen to others and think critically.

 

Hope this makes sense.

Merry (early) Christmas,

Joseph



Lino Morales
 

Oh BTW you all, I'll never take Webame survey again. I alrea stated what Joe Steincamp told me via Twitter yesterday and he's right and so is Joseph. Thenks for informing of the contraversy in survey 6. Never knew anythihng happened. Survey 7 was the first time I took it.


On 12/23/2017 12:25 PM, Joseph Lee wrote:

Dear NVDA community,

 

As I read messages on recent discussions, I realized just how much enthusiasm and concern people have over NVDA and its future. At the same time, it became clear to me that I and other developers and community elders need a day off and just listen to you all, as listening allows us to think about what others are saying and plan things accordingly.

 

But first, a humble opinion about surveys and other points:

 

First, when calls for the seventh Web AIM survey went out, I told people to not just do it to “increase” market share. I specifically told screen reader companies to not coerce users to do it, but let people take it out of their own willingness. This advice was to avoid a fiasco that happened with Web AIM 6 where AI Squared (now part of VFO) staff told Window-Eyes users to fill out the survey in mass numbers, which became a small controversy within the screen reading world, and to me, making Web AIM results no longer credible.

 

As some folks pointed out, Web AIM numbers depend on how many people fill it out and where they come from (and this is true of any surveys where word of mouth drives participation). The results also depend on demographics and other factors such as choices given, how the questions are worded, and overall objective. If one or more data points seems to be dominant, they can be either skewed or outliers, with the more extreme cases being termed “outliers” and they affect how the results are explicated (interpreted). Even skewed data, such as what I can perceive from some surveys including recent Web AIM iterations can affect statistical calculations to a point where it raises genuine questions about bias, credibility, and others (after all, success of statistics, particularly inferential statistics, depends on a representative sample or a close equivalent that allows researchers to approximate the real world, which is prone to errors if not done correctly such as misinterpretation, bad outliers, only some groups participating, not looking at things more deeply and what not).

 

One important thing to note is that Web AIM is a representative survey, thus the result in front of me could reflect reality. However, due to recent controversy, possible type I and II errors (false-positive and false-negative, respectively) and because of outliers and skewed data and participation, it does not truly reflect actual data, which is a point some folks here are trying to say and I concur with. My explication of Web AIM 7 is that, in some parts of the world, JAWS for Windows is more popular. However, given the fact that not all geographical regions are represented, I’d counter by saying that this is not a true representative sample that includes every continent, and if it did, the story would be different and will reflect reality a bit better (not a lot because there are other ways of skewing data such as filling it out on behalf of an organization, robotic fillers and so on). Coupled with the fact that Web AIM went through a major controversy recently that damaged its credibility somewhat, I would dare not trust Web AIM results again.

 

This leads to my second point: quantity versus quality. If NV Access went straight for quantity alone, they could have implemented all possible feature requests in hopes of boosting market share. The reality in front of us says otherwise: not all feature requests are here. Numerous factors contribute to this problem:

 

  • Lack of leading developers: in 2017, a long-time NVDA developer started working for another organization, and NV Access has been looking for his replacement ever since. Even if the replacement is found, it’ll take several months for him or her to become used to this community, learn about accessibility and how to interact with members, and earn our trust (it took Reef Turner a year to fully earn our trust). Folks can counter this by saying that there are countless contributors out there, but ultimately what gets into NVDA depends on pull requests and review time from NV Access.
  • Attitudes about open-source software from organizations: as some folks pointed out, there are prevailing attitudes about open-source in organizations that makes it a bit harder for NVDA to land on their computers, which allows developers to assess true needs of organizations through user feedback. Without valuable feedback from organizations (a quality one at that), we won’t see huger progress in NVDA development.
  • Outside attitudes about the NVDA community: from the inside, NVDA community is seen as a tight nit of enthusiasts who strives to make NVDA better every day. On the outside, however, we have a mixed bag of reputations, from admiration to honorable mentions to disdain. Every organization have these mixed reputations, especially more so for a community powered by technology such as Linux kernel developers, web browser vendors and web standards organizations, and even screen reader community. Not only we need to show that we are united inside, we need to showcase unity outside of this community.
  • Inside matters just as outside: public relations outside of NVDA community is important, but unity within an organization is just as important as public organizational face (I’ll address developer’s point of view below). What makes NVDA stand out is our unity despite coming from different circumstances and backgrounds.

 

Most of these point to quality, not quantity alone. In summary, quantity is important, but quality is just as important as how many people download NVDA 2017.4 between Christmas and New Year.

 

Lastly, in regards to organization internals, I’d like to address something I really wanted to say for the past few weeks: sometimes, I felt burnt out. My initial response to your enthusiasm over my audio tutorials was that I’ll ask for justifications for producing an updated version, seeing that there are countless free videos and tutorials out there. This was partly because I truly felt burnt out with academics, speech and debate competitions and what not (especially after a debate regarding a potential feature held not long ago), at one point telling myself that I’ll retire from the NVDA community sooner than later and feeling as though I carried important burdens on my shoulders. But you didn’t see that justification post; instead, I posted links to where you can download the 2018 version of my audio tutorial series. In effect, I’ve given up my Christmas holidays for this community, knowing that I needed a time to listen to you all and do something about it. All this was possible because of a simple act of listening and thinking about what the community means to me and what my work means to everyone. I’m committed to finishing Welcome to NVDA 2018 series before NVDA 2018.1 ships, with several addenda coming after that, all because of support from this community and outsiders. And I promise again: The Welcome to NVDA 2018 series was, and will remain, free for all. All I ask of you in return is donate to a cause that makes equal access to technology possible, especially during this holiday season and beyond.

 

I’m sure for many of you, my musings above are a bit hard to digest. Now you know why I don’t trust Web AIM survey results, quality is just as important as quantity, and read a confession from a community leader on his inner feelings. But there are two more things you need to know, something all of us needs to think about:

 

Community leaders won’t stay with you forever. In early 2017, I sensed that a long-time NVDA developer would leave this community for something better. Only I and others didn’t know until summer that it would be Jamie moving onto Mozilla Foundation.

 

I also felt, back in early 2017, that my active time with the NVDA community is slowly drawing to a close. I don’t know when it’ll happen, but I’ve been laying foundations for the next generation of developers and enthusiasts to take the lead. This is one of the reasons for setting up the devlearning subgroup, because I felt it is time for me and other leaders to teach NVDA internals and other concepts to the next group of community leaders and developers so they can bring NVDA to the next level and do more amazing things than I and others did (in my case, for the past five years).

 

Lastly, I sense a time when this community will face a sharp divide to a point where people will start questioning the merits of this community. I only told a select few earlier because it wasn’t right for me to disclose it early and for them to prepare a plan. The screen shade debate is, in fact, a sort of a preview of what is to come. One of the fundamental questions you will face at that time will be whether you still have your first love for NVDA, and whether you still have your original reasons for joining this community. The survival of this community at that time will depend on your ability to unite to face a difficult situation, even if that means facing possible splits. One thing you should NOT do at that time: ignoring new users and outside critics, because they are influential opinion leaders and are key stakeholders in NVDA’s future. One thing you SHOULD do though: listen to others and think critically.

 

Hope this makes sense.

Merry (early) Christmas,

Joseph



Brian's Mail list account <bglists@...>
 

Certainly I do understand the burned out part of this its the same for all volunteers. if we are good at what we do we are in demand and take on more and more. it was only a comment from somebody else that made me try to bring a sense of realism to life. You cannot be a one man fixer of everything, and the cemeteries are full of people who were indispensable.
 Most screenreader users are just that, users, many of us know the basics of what is going on, but really, its now so complex its beyond all but the few to grasp it all.
 Obviously as we kind of slip into a world very much like we used to have in the 80s, where computers run lots of different operating systems and even windows differs  in the internals between many different systems, the problems of access move from the screenreader to the platform.
 that is, NVDA will probably be OK on mainstream Windows computers for some years, but with tablets, phones and various different processors and operating systems now coming in, its going to be the user who has to change and become expert in many more interfaces, as clearly, what we use in Windows today with a keyboard may not fit in any way the interface of the future.
Sadly the problem is as it always has been, training and the cost and indeed the ability of blind people particularly the older ones to actually grasp the abstract concepts and enable them to see equivalents  and have a grasp of what is actually going on.
 I really think that somebody needs to invest a lot more money globally in trying to get more blind people computer literate, but its just not happening, so although in theory we have access, not everyone will be able to actually use it.
 
Change is life after all, and people going to take other jobs is normal. the problem for nvda is that the two people who started it were visionary, and not everyone can share the vision, if you get my drift.
 I don't know what is about to happen to tech, but it seems to me that nobody does. Who could have predicted this year that tablet sales have dropped but laptop and desktop sales are up. I suspect its down to novelty wearing off and nothing really new on the market just revamps of what has gone before.
 Personally, my gut tells me that although cloud computing can be good in some cases, many people do not want to pitch all their eggs into somebody elses basket. Its the same reason I still buy CDs. I don't want somebody taking my access away due to whatever. The danger at the moment is that the net is going down the packet priority  road as well, another legal form of highway robbery in my view.
 As for surveys, yes, well I already told you my opinion of those. Almost be better to use some tracking system, like a cookie to see what is on any given machine, but many would find that intrusive even though if you own an Android device its more or less going on now.
 Its all about trust and whether you can always trust others with data about you.
 If it can be created it can be hacked and  messed about with. Bots are all over the place after all.
 If you cannot trust the metrics one gets then the data collected becomes worthless.
 Anyway I'm up in the night again  wibbling on. Look at it this way, it matters what happens to nvda, but in the great scheme of life, what really matters is trying to be happy while you are  here on the planet. You cannot own other people like Mick or Jamie.
 
Its not right or  fair to expect people to be some kind of God.
 Been there got the TO Shirt, and the community awards etc, and for what?
 I prefer now to just help if I can but not to get so het up that it makes my life owned by others.
 Big mistake.
 Brian

bglists@... 
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
This message sent from a Windows XP machine!

----- Original Message -----
From: Joseph Lee
Sent: Saturday, December 23, 2017 5:25 PM
Subject: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials

Dear NVDA community,

 

As I read messages on recent discussions, I realized just how much enthusiasm and concern people have over NVDA and its future. At the same time, it became clear to me that I and other developers and community elders need a day off and just listen to you all, as listening allows us to think about what others are saying and plan things accordingly.

 

But first, a humble opinion about surveys and other points:

 

First, when calls for the seventh Web AIM survey went out, I told people to not just do it to “increase” market share. I specifically told screen reader companies to not coerce users to do it, but let people take it out of their own willingness. This advice was to avoid a fiasco that happened with Web AIM 6 where AI Squared (now part of VFO) staff told Window-Eyes users to fill out the survey in mass numbers, which became a small controversy within the screen reading world, and to me, making Web AIM results no longer credible.

 

As some folks pointed out, Web AIM numbers depend on how many people fill it out and where they come from (and this is true of any surveys where word of mouth drives participation). The results also depend on demographics and other factors such as choices given, how the questions are worded, and overall objective. If one or more data points seems to be dominant, they can be either skewed or outliers, with the more extreme cases being termed “outliers” and they affect how the results are explicated (interpreted). Even skewed data, such as what I can perceive from some surveys including recent Web AIM iterations can affect statistical calculations to a point where it raises genuine questions about bias, credibility, and others (after all, success of statistics, particularly inferential statistics, depends on a representative sample or a close equivalent that allows researchers to approximate the real world, which is prone to errors if not done correctly such as misinterpretation, bad outliers, only some groups participating, not looking at things more deeply and what not).

 

One important thing to note is that Web AIM is a representative survey, thus the result in front of me could reflect reality. However, due to recent controversy, possible type I and II errors (false-positive and false-negative, respectively) and because of outliers and skewed data and participation, it does not truly reflect actual data, which is a point some folks here are trying to say and I concur with. My explication of Web AIM 7 is that, in some parts of the world, JAWS for Windows is more popular. However, given the fact that not all geographical regions are represented, I’d counter by saying that this is not a true representative sample that includes every continent, and if it did, the story would be different and will reflect reality a bit better (not a lot because there are other ways of skewing data such as filling it out on behalf of an organization, robotic fillers and so on). Coupled with the fact that Web AIM went through a major controversy recently that damaged its credibility somewhat, I would dare not trust Web AIM results again.

 

This leads to my second point: quantity versus quality. If NV Access went straight for quantity alone, they could have implemented all possible feature requests in hopes of boosting market share. The reality in front of us says otherwise: not all feature requests are here. Numerous factors contribute to this problem:

 

  • Lack of leading developers: in 2017, a long-time NVDA developer started working for another organization, and NV Access has been looking for his replacement ever since. Even if the replacement is found, it’ll take several months for him or her to become used to this community, learn about accessibility and how to interact with members, and earn our trust (it took Reef Turner a year to fully earn our trust). Folks can counter this by saying that there are countless contributors out there, but ultimately what gets into NVDA depends on pull requests and review time from NV Access.
  • Attitudes about open-source software from organizations: as some folks pointed out, there are prevailing attitudes about open-source in organizations that makes it a bit harder for NVDA to land on their computers, which allows developers to assess true needs of organizations through user feedback. Without valuable feedback from organizations (a quality one at that), we won’t see huger progress in NVDA development.
  • Outside attitudes about the NVDA community: from the inside, NVDA community is seen as a tight nit of enthusiasts who strives to make NVDA better every day. On the outside, however, we have a mixed bag of reputations, from admiration to honorable mentions to disdain. Every organization have these mixed reputations, especially more so for a community powered by technology such as Linux kernel developers, web browser vendors and web standards organizations, and even screen reader community. Not only we need to show that we are united inside, we need to showcase unity outside of this community.
  • Inside matters just as outside: public relations outside of NVDA community is important, but unity within an organization is just as important as public organizational face (I’ll address developer’s point of view below). What makes NVDA stand out is our unity despite coming from different circumstances and backgrounds.

 

Most of these point to quality, not quantity alone. In summary, quantity is important, but quality is just as important as how many people download NVDA 2017.4 between Christmas and New Year.

 

Lastly, in regards to organization internals, I’d like to address something I really wanted to say for the past few weeks: sometimes, I felt burnt out. My initial response to your enthusiasm over my audio tutorials was that I’ll ask for justifications for producing an updated version, seeing that there are countless free videos and tutorials out there. This was partly because I truly felt burnt out with academics, speech and debate competitions and what not (especially after a debate regarding a potential feature held not long ago), at one point telling myself that I’ll retire from the NVDA community sooner than later and feeling as though I carried important burdens on my shoulders. But you didn’t see that justification post; instead, I posted links to where you can download the 2018 version of my audio tutorial series. In effect, I’ve given up my Christmas holidays for this community, knowing that I needed a time to listen to you all and do something about it. All this was possible because of a simple act of listening and thinking about what the community means to me and what my work means to everyone. I’m committed to finishing Welcome to NVDA 2018 series before NVDA 2018.1 ships, with several addenda coming after that, all because of support from this community and outsiders. And I promise again: The Welcome to NVDA 2018 series was, and will remain, free for all. All I ask of you in return is donate to a cause that makes equal access to technology possible, especially during this holiday season and beyond.

 

I’m sure for many of you, my musings above are a bit hard to digest. Now you know why I don’t trust Web AIM survey results, quality is just as important as quantity, and read a confession from a community leader on his inner feelings. But there are two more things you need to know, something all of us needs to think about:

 

Community leaders won’t stay with you forever. In early 2017, I sensed that a long-time NVDA developer would leave this community for something better. Only I and others didn’t know until summer that it would be Jamie moving onto Mozilla Foundation.

 

I also felt, back in early 2017, that my active time with the NVDA community is slowly drawing to a close. I don’t know when it’ll happen, but I’ve been laying foundations for the next generation of developers and enthusiasts to take the lead. This is one of the reasons for setting up the devlearning subgroup, because I felt it is time for me and other leaders to teach NVDA internals and other concepts to the next group of community leaders and developers so they can bring NVDA to the next level and do more amazing things than I and others did (in my case, for the past five years).

 

Lastly, I sense a time when this community will face a sharp divide to a point where people will start questioning the merits of this community. I only told a select few earlier because it wasn’t right for me to disclose it early and for them to prepare a plan. The screen shade debate is, in fact, a sort of a preview of what is to come. One of the fundamental questions you will face at that time will be whether you still have your first love for NVDA, and whether you still have your original reasons for joining this community. The survival of this community at that time will depend on your ability to unite to face a difficult situation, even if that means facing possible splits. One thing you should NOT do at that time: ignoring new users and outside critics, because they are influential opinion leaders and are key stakeholders in NVDA’s future. One thing you SHOULD do though: listen to others and think critically.

 

Hope this makes sense.

Merry (early) Christmas,

Joseph


Adriani Botez
 

Brian,

With respect to investing money globally to make screen reader users more computer literate, well believe or not there was always a solution for that. A screen reader should imply a social movement and not a gain of capital out of selling. There are lots of development institutions, Christian Blind Mission, blind federations and lots of other non governamental organizations which support everything which gives people access to education, information and technology. But in the last 30 years, many people hoped to gain money out of selling licenses and did not really concentrate on learning the user detailed aspects on how to use that software. Thus, users became more and more change resistent because they invested lot of time to learn by themselves how to use it productively. In my opinion, we should not only think about technical aspects of a screen reader, but also about social impact and user interaction.

Best
Adriani


Von meinem iPhone gesendet

Am 24.12.2017 um 04:44 schrieb Brian's Mail list account via Groups.Io <bglists@...>:

Certainly I do understand the burned out part of this its the same for all volunteers. if we are good at what we do we are in demand and take on more and more. it was only a comment from somebody else that made me try to bring a sense of realism to life. You cannot be a one man fixer of everything, and the cemeteries are full of people who were indispensable.
 Most screenreader users are just that, users, many of us know the basics of what is going on, but really, its now so complex its beyond all but the few to grasp it all.
 Obviously as we kind of slip into a world very much like we used to have in the 80s, where computers run lots of different operating systems and even windows differs  in the internals between many different systems, the problems of access move from the screenreader to the platform.
 that is, NVDA will probably be OK on mainstream Windows computers for some years, but with tablets, phones and various different processors and operating systems now coming in, its going to be the user who has to change and become expert in many more interfaces, as clearly, what we use in Windows today with a keyboard may not fit in any way the interface of the future.
Sadly the problem is as it always has been, training and the cost and indeed the ability of blind people particularly the older ones to actually grasp the abstract concepts and enable them to see equivalents  and have a grasp of what is actually going on.
 I really think that somebody needs to invest a lot more money globally in trying to get more blind people computer literate, but its just not happening, so although in theory we have access, not everyone will be able to actually use it.
 
Change is life after all, and people going to take other jobs is normal. the problem for nvda is that the two people who started it were visionary, and not everyone can share the vision, if you get my drift.
 I don't know what is about to happen to tech, but it seems to me that nobody does. Who could have predicted this year that tablet sales have dropped but laptop and desktop sales are up. I suspect its down to novelty wearing off and nothing really new on the market just revamps of what has gone before.
 Personally, my gut tells me that although cloud computing can be good in some cases, many people do not want to pitch all their eggs into somebody elses basket. Its the same reason I still buy CDs. I don't want somebody taking my access away due to whatever. The danger at the moment is that the net is going down the packet priority  road as well, another legal form of highway robbery in my view.
 As for surveys, yes, well I already told you my opinion of those. Almost be better to use some tracking system, like a cookie to see what is on any given machine, but many would find that intrusive even though if you own an Android device its more or less going on now.
 Its all about trust and whether you can always trust others with data about you.
 If it can be created it can be hacked and  messed about with. Bots are all over the place after all.
 If you cannot trust the metrics one gets then the data collected becomes worthless.
 Anyway I'm up in the night again  wibbling on. Look at it this way, it matters what happens to nvda, but in the great scheme of life, what really matters is trying to be happy while you are  here on the planet. You cannot own other people like Mick or Jamie.
 
Its not right or  fair to expect people to be some kind of God.
 Been there got the TO Shirt, and the community awards etc, and for what?
 I prefer now to just help if I can but not to get so het up that it makes my life owned by others.
 Big mistake.
 Brian

bglists@... 
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
This message sent from a Windows XP machine!
----- Original Message -----
From: Joseph Lee
Sent: Saturday, December 23, 2017 5:25 PM
Subject: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials

Dear NVDA community,

 

As I read messages on recent discussions, I realized just how much enthusiasm and concern people have over NVDA and its future. At the same time, it became clear to me that I and other developers and community elders need a day off and just listen to you all, as listening allows us to think about what others are saying and plan things accordingly.

 

But first, a humble opinion about surveys and other points:

 

First, when calls for the seventh Web AIM survey went out, I told people to not just do it to “increase” market share. I specifically told screen reader companies to not coerce users to do it, but let people take it out of their own willingness. This advice was to avoid a fiasco that happened with Web AIM 6 where AI Squared (now part of VFO) staff told Window-Eyes users to fill out the survey in mass numbers, which became a small controversy within the screen reading world, and to me, making Web AIM results no longer credible.

 

As some folks pointed out, Web AIM numbers depend on how many people fill it out and where they come from (and this is true of any surveys where word of mouth drives participation). The results also depend on demographics and other factors such as choices given, how the questions are worded, and overall objective. If one or more data points seems to be dominant, they can be either skewed or outliers, with the more extreme cases being termed “outliers” and they affect how the results are explicated (interpreted). Even skewed data, such as what I can perceive from some surveys including recent Web AIM iterations can affect statistical calculations to a point where it raises genuine questions about bias, credibility, and others (after all, success of statistics, particularly inferential statistics, depends on a representative sample or a close equivalent that allows researchers to approximate the real world, which is prone to errors if not done correctly such as misinterpretation, bad outliers, only some groups participating, not looking at things more deeply and what not).

 

One important thing to note is that Web AIM is a representative survey, thus the result in front of me could reflect reality. However, due to recent controversy, possible type I and II errors (false-positive and false-negative, respectively) and because of outliers and skewed data and participation, it does not truly reflect actual data, which is a point some folks here are trying to say and I concur with. My explication of Web AIM 7 is that, in some parts of the world, JAWS for Windows is more popular. However, given the fact that not all geographical regions are represented, I’d counter by saying that this is not a true representative sample that includes every continent, and if it did, the story would be different and will reflect reality a bit better (not a lot because there are other ways of skewing data such as filling it out on behalf of an organization, robotic fillers and so on). Coupled with the fact that Web AIM went through a major controversy recently that damaged its credibility somewhat, I would dare not trust Web AIM results again.

 

This leads to my second point: quantity versus quality. If NV Access went straight for quantity alone, they could have implemented all possible feature requests in hopes of boosting market share. The reality in front of us says otherwise: not all feature requests are here. Numerous factors contribute to this problem:

 

  • Lack of leading developers: in 2017, a long-time NVDA developer started working for another organization, and NV Access has been looking for his replacement ever since. Even if the replacement is found, it’ll take several months for him or her to become used to this community, learn about accessibility and how to interact with members, and earn our trust (it took Reef Turner a year to fully earn our trust). Folks can counter this by saying that there are countless contributors out there, but ultimately what gets into NVDA depends on pull requests and review time from NV Access.
  • Attitudes about open-source software from organizations: as some folks pointed out, there are prevailing attitudes about open-source in organizations that makes it a bit harder for NVDA to land on their computers, which allows developers to assess true needs of organizations through user feedback. Without valuable feedback from organizations (a quality one at that), we won’t see huger progress in NVDA development.
  • Outside attitudes about the NVDA community: from the inside, NVDA community is seen as a tight nit of enthusiasts who strives to make NVDA better every day. On the outside, however, we have a mixed bag of reputations, from admiration to honorable mentions to disdain. Every organization have these mixed reputations, especially more so for a community powered by technology such as Linux kernel developers, web browser vendors and web standards organizations, and even screen reader community. Not only we need to show that we are united inside, we need to showcase unity outside of this community.
  • Inside matters just as outside: public relations outside of NVDA community is important, but unity within an organization is just as important as public organizational face (I’ll address developer’s point of view below). What makes NVDA stand out is our unity despite coming from different circumstances and backgrounds.

 

Most of these point to quality, not quantity alone. In summary, quantity is important, but quality is just as important as how many people download NVDA 2017.4 between Christmas and New Year.

 

Lastly, in regards to organization internals, I’d like to address something I really wanted to say for the past few weeks: sometimes, I felt burnt out. My initial response to your enthusiasm over my audio tutorials was that I’ll ask for justifications for producing an updated version, seeing that there are countless free videos and tutorials out there. This was partly because I truly felt burnt out with academics, speech and debate competitions and what not (especially after a debate regarding a potential feature held not long ago), at one point telling myself that I’ll retire from the NVDA community sooner than later and feeling as though I carried important burdens on my shoulders. But you didn’t see that justification post; instead, I posted links to where you can download the 2018 version of my audio tutorial series. In effect, I’ve given up my Christmas holidays for this community, knowing that I needed a time to listen to you all and do something about it. All this was possible because of a simple act of listening and thinking about what the community means to me and what my work means to everyone. I’m committed to finishing Welcome to NVDA 2018 series before NVDA 2018.1 ships, with several addenda coming after that, all because of support from this community and outsiders. And I promise again: The Welcome to NVDA 2018 series was, and will remain, free for all. All I ask of you in return is donate to a cause that makes equal access to technology possible, especially during this holiday season and beyond.

 

I’m sure for many of you, my musings above are a bit hard to digest. Now you know why I don’t trust Web AIM survey results, quality is just as important as quantity, and read a confession from a community leader on his inner feelings. But there are two more things you need to know, something all of us needs to think about:

 

Community leaders won’t stay with you forever. In early 2017, I sensed that a long-time NVDA developer would leave this community for something better. Only I and others didn’t know until summer that it would be Jamie moving onto Mozilla Foundation.

 

I also felt, back in early 2017, that my active time with the NVDA community is slowly drawing to a close. I don’t know when it’ll happen, but I’ve been laying foundations for the next generation of developers and enthusiasts to take the lead. This is one of the reasons for setting up the devlearning subgroup, because I felt it is time for me and other leaders to teach NVDA internals and other concepts to the next group of community leaders and developers so they can bring NVDA to the next level and do more amazing things than I and others did (in my case, for the past five years).

 

Lastly, I sense a time when this community will face a sharp divide to a point where people will start questioning the merits of this community. I only told a select few earlier because it wasn’t right for me to disclose it early and for them to prepare a plan. The screen shade debate is, in fact, a sort of a preview of what is to come. One of the fundamental questions you will face at that time will be whether you still have your first love for NVDA, and whether you still have your original reasons for joining this community. The survival of this community at that time will depend on your ability to unite to face a difficult situation, even if that means facing possible splits. One thing you should NOT do at that time: ignoring new users and outside critics, because they are influential opinion leaders and are key stakeholders in NVDA’s future. One thing you SHOULD do though: listen to others and think critically.

 

Hope this makes sense.

Merry (early) Christmas,

Joseph


Sky Mundell
 

I totally agree with you. You are absolutely right.  Screen readers should certainly be a social impact. The reason there is capital invested in it is because the agencies are the ones who are funding the capital.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Adriani Botez
Sent: Saturday, December 23, 2017 7:08 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials

 

Brian,

 

With respect to investing money globally to make screen reader users more computer literate, well believe or not there was always a solution for that. A screen reader should imply a social movement and not a gain of capital out of selling. There are lots of development institutions, Christian Blind Mission, blind federations and lots of other non governamental organizations which support everything which gives people access to education, information and technology. But in the last 30 years, many people hoped to gain money out of selling licenses and did not really concentrate on learning the user detailed aspects on how to use that software. Thus, users became more and more change resistent because they invested lot of time to learn by themselves how to use it productively. In my opinion, we should not only think about technical aspects of a screen reader, but also about social impact and user interaction.

 

Best

Adriani

 

Von meinem iPhone gesendet


Am 24.12.2017 um 04:44 schrieb Brian's Mail list account via Groups.Io <bglists@...>:

Certainly I do understand the burned out part of this its the same for all volunteers. if we are good at what we do we are in demand and take on more and more. it was only a comment from somebody else that made me try to bring a sense of realism to life. You cannot be a one man fixer of everything, and the cemeteries are full of people who were indispensable.

 Most screenreader users are just that, users, many of us know the basics of what is going on, but really, its now so complex its beyond all but the few to grasp it all.

 Obviously as we kind of slip into a world very much like we used to have in the 80s, where computers run lots of different operating systems and even windows differs  in the internals between many different systems, the problems of access move from the screenreader to the platform.

 that is, NVDA will probably be OK on mainstream Windows computers for some years, but with tablets, phones and various different processors and operating systems now coming in, its going to be the user who has to change and become expert in many more interfaces, as clearly, what we use in Windows today with a keyboard may not fit in any way the interface of the future.

Sadly the problem is as it always has been, training and the cost and indeed the ability of blind people particularly the older ones to actually grasp the abstract concepts and enable them to see equivalents  and have a grasp of what is actually going on.

 I really think that somebody needs to invest a lot more money globally in trying to get more blind people computer literate, but its just not happening, so although in theory we have access, not everyone will be able to actually use it.

 

Change is life after all, and people going to take other jobs is normal. the problem for nvda is that the two people who started it were visionary, and not everyone can share the vision, if you get my drift.

 I don't know what is about to happen to tech, but it seems to me that nobody does. Who could have predicted this year that tablet sales have dropped but laptop and desktop sales are up. I suspect its down to novelty wearing off and nothing really new on the market just revamps of what has gone before.

 Personally, my gut tells me that although cloud computing can be good in some cases, many people do not want to pitch all their eggs into somebody elses basket. Its the same reason I still buy CDs. I don't want somebody taking my access away due to whatever. The danger at the moment is that the net is going down the packet priority  road as well, another legal form of highway robbery in my view.

 As for surveys, yes, well I already told you my opinion of those. Almost be better to use some tracking system, like a cookie to see what is on any given machine, but many would find that intrusive even though if you own an Android device its more or less going on now.

 Its all about trust and whether you can always trust others with data about you.

 If it can be created it can be hacked and  messed about with. Bots are all over the place after all.

 If you cannot trust the metrics one gets then the data collected becomes worthless.

 Anyway I'm up in the night again  wibbling on. Look at it this way, it matters what happens to nvda, but in the great scheme of life, what really matters is trying to be happy while you are  here on the planet. You cannot own other people like Mick or Jamie.

 

Its not right or  fair to expect people to be some kind of God.

 Been there got the TO Shirt, and the community awards etc, and for what?

 I prefer now to just help if I can but not to get so het up that it makes my life owned by others.

 Big mistake.

 Brian


bglists@... 
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
This message sent from a Windows XP machine!

----- Original Message -----

From: Joseph Lee

Sent: Saturday, December 23, 2017 5:25 PM

Subject: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials

 

Dear NVDA community,

 

As I read messages on recent discussions, I realized just how much enthusiasm and concern people have over NVDA and its future. At the same time, it became clear to me that I and other developers and community elders need a day off and just listen to you all, as listening allows us to think about what others are saying and plan things accordingly.

 

But first, a humble opinion about surveys and other points:

 

First, when calls for the seventh Web AIM survey went out, I told people to not just do it to “increase” market share. I specifically told screen reader companies to not coerce users to do it, but let people take it out of their own willingness. This advice was to avoid a fiasco that happened with Web AIM 6 where AI Squared (now part of VFO) staff told Window-Eyes users to fill out the survey in mass numbers, which became a small controversy within the screen reading world, and to me, making Web AIM results no longer credible.

 

As some folks pointed out, Web AIM numbers depend on how many people fill it out and where they come from (and this is true of any surveys where word of mouth drives participation). The results also depend on demographics and other factors such as choices given, how the questions are worded, and overall objective. If one or more data points seems to be dominant, they can be either skewed or outliers, with the more extreme cases being termed “outliers” and they affect how the results are explicated (interpreted). Even skewed data, such as what I can perceive from some surveys including recent Web AIM iterations can affect statistical calculations to a point where it raises genuine questions about bias, credibility, and others (after all, success of statistics, particularly inferential statistics, depends on a representative sample or a close equivalent that allows researchers to approximate the real world, which is prone to errors if not done correctly such as misinterpretation, bad outliers, only some groups participating, not looking at things more deeply and what not).

 

One important thing to note is that Web AIM is a representative survey, thus the result in front of me could reflect reality. However, due to recent controversy, possible type I and II errors (false-positive and false-negative, respectively) and because of outliers and skewed data and participation, it does not truly reflect actual data, which is a point some folks here are trying to say and I concur with. My explication of Web AIM 7 is that, in some parts of the world, JAWS for Windows is more popular. However, given the fact that not all geographical regions are represented, I’d counter by saying that this is not a true representative sample that includes every continent, and if it did, the story would be different and will reflect reality a bit better (not a lot because there are other ways of skewing data such as filling it out on behalf of an organization, robotic fillers and so on). Coupled with the fact that Web AIM went through a major controversy recently that damaged its credibility somewhat, I would dare not trust Web AIM results again.

 

This leads to my second point: quantity versus quality. If NV Access went straight for quantity alone, they could have implemented all possible feature requests in hopes of boosting market share. The reality in front of us says otherwise: not all feature requests are here. Numerous factors contribute to this problem:

 

  • Lack of leading developers: in 2017, a long-time NVDA developer started working for another organization, and NV Access has been looking for his replacement ever since. Even if the replacement is found, it’ll take several months for him or her to become used to this community, learn about accessibility and how to interact with members, and earn our trust (it took Reef Turner a year to fully earn our trust). Folks can counter this by saying that there are countless contributors out there, but ultimately what gets into NVDA depends on pull requests and review time from NV Access.
  • Attitudes about open-source software from organizations: as some folks pointed out, there are prevailing attitudes about open-source in organizations that makes it a bit harder for NVDA to land on their computers, which allows developers to assess true needs of organizations through user feedback. Without valuable feedback from organizations (a quality one at that), we won’t see huger progress in NVDA development.
  • Outside attitudes about the NVDA community: from the inside, NVDA community is seen as a tight nit of enthusiasts who strives to make NVDA better every day. On the outside, however, we have a mixed bag of reputations, from admiration to honorable mentions to disdain. Every organization have these mixed reputations, especially more so for a community powered by technology such as Linux kernel developers, web browser vendors and web standards organizations, and even screen reader community. Not only we need to show that we are united inside, we need to showcase unity outside of this community.
  • Inside matters just as outside: public relations outside of NVDA community is important, but unity within an organization is just as important as public organizational face (I’ll address developer’s point of view below). What makes NVDA stand out is our unity despite coming from different circumstances and backgrounds.

 

Most of these point to quality, not quantity alone. In summary, quantity is important, but quality is just as important as how many people download NVDA 2017.4 between Christmas and New Year.

 

Lastly, in regards to organization internals, I’d like to address something I really wanted to say for the past few weeks: sometimes, I felt burnt out. My initial response to your enthusiasm over my audio tutorials was that I’ll ask for justifications for producing an updated version, seeing that there are countless free videos and tutorials out there. This was partly because I truly felt burnt out with academics, speech and debate competitions and what not (especially after a debate regarding a potential feature held not long ago), at one point telling myself that I’ll retire from the NVDA community sooner than later and feeling as though I carried important burdens on my shoulders. But you didn’t see that justification post; instead, I posted links to where you can download the 2018 version of my audio tutorial series. In effect, I’ve given up my Christmas holidays for this community, knowing that I needed a time to listen to you all and do something about it. All this was possible because of a simple act of listening and thinking about what the community means to me and what my work means to everyone. I’m committed to finishing Welcome to NVDA 2018 series before NVDA 2018.1 ships, with several addenda coming after that, all because of support from this community and outsiders. And I promise again: The Welcome to NVDA 2018 series was, and will remain, free for all. All I ask of you in return is donate to a cause that makes equal access to technology possible, especially during this holiday season and beyond.

 

I’m sure for many of you, my musings above are a bit hard to digest. Now you know why I don’t trust Web AIM survey results, quality is just as important as quantity, and read a confession from a community leader on his inner feelings. But there are two more things you need to know, something all of us needs to think about:

 

Community leaders won’t stay with you forever. In early 2017, I sensed that a long-time NVDA developer would leave this community for something better. Only I and others didn’t know until summer that it would be Jamie moving onto Mozilla Foundation.

 

I also felt, back in early 2017, that my active time with the NVDA community is slowly drawing to a close. I don’t know when it’ll happen, but I’ve been laying foundations for the next generation of developers and enthusiasts to take the lead. This is one of the reasons for setting up the devlearning subgroup, because I felt it is time for me and other leaders to teach NVDA internals and other concepts to the next group of community leaders and developers so they can bring NVDA to the next level and do more amazing things than I and others did (in my case, for the past five years).

 

Lastly, I sense a time when this community will face a sharp divide to a point where people will start questioning the merits of this community. I only told a select few earlier because it wasn’t right for me to disclose it early and for them to prepare a plan. The screen shade debate is, in fact, a sort of a preview of what is to come. One of the fundamental questions you will face at that time will be whether you still have your first love for NVDA, and whether you still have your original reasons for joining this community. The survival of this community at that time will depend on your ability to unite to face a difficult situation, even if that means facing possible splits. One thing you should NOT do at that time: ignoring new users and outside critics, because they are influential opinion leaders and are key stakeholders in NVDA’s future. One thing you SHOULD do though: listen to others and think critically.

 

Hope this makes sense.

Merry (early) Christmas,

Joseph


Moti Azrad
 

Dear friends,

 

First, as Israeli NVDA user, I must say good things and a lot of thanks to Joseph Lee and derek and sure for all the other develpers – who try to improve NVDA AND CREATE MORE AND MORE good addons and other useful features.

 

Thanks much

 

Moti

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Adriani Botez
Sent: Sunday, December 24, 2017 5:08
To: nvda@nvda.groups.io
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials

 

Brian,

 

With respect to investing money globally to make screen reader users more computer literate, well believe or not there was always a solution for that. A screen reader should imply a social movement and not a gain of capital out of selling. There are lots of development institutions, Christian Blind Mission, blind federations and lots of other non governamental organizations which support everything which gives people access to education, information and technology. But in the last 30 years, many people hoped to gain money out of selling licenses and did not really concentrate on learning the user detailed aspects on how to use that software. Thus, users became more and more change resistent because they invested lot of time to learn by themselves how to use it productively. In my opinion, we should not only think about technical aspects of a screen reader, but also about social impact and user interaction.

 

Best

Adriani

 

Von meinem iPhone gesendet


Am 24.12.2017 um 04:44 schrieb Brian's Mail list account via Groups.Io <bglists@...>:

Certainly I do understand the burned out part of this its the same for all volunteers. if we are good at what we do we are in demand and take on more and more. it was only a comment from somebody else that made me try to bring a sense of realism to life. You cannot be a one man fixer of everything, and the cemeteries are full of people who were indispensable.

 Most screenreader users are just that, users, many of us know the basics of what is going on, but really, its now so complex its beyond all but the few to grasp it all.

 Obviously as we kind of slip into a world very much like we used to have in the 80s, where computers run lots of different operating systems and even windows differs  in the internals between many different systems, the problems of access move from the screenreader to the platform.

 that is, NVDA will probably be OK on mainstream Windows computers for some years, but with tablets, phones and various different processors and operating systems now coming in, its going to be the user who has to change and become expert in many more interfaces, as clearly, what we use in Windows today with a keyboard may not fit in any way the interface of the future.

Sadly the problem is as it always has been, training and the cost and indeed the ability of blind people particularly the older ones to actually grasp the abstract concepts and enable them to see equivalents  and have a grasp of what is actually going on.

 I really think that somebody needs to invest a lot more money globally in trying to get more blind people computer literate, but its just not happening, so although in theory we have access, not everyone will be able to actually use it.

 

Change is life after all, and people going to take other jobs is normal. the problem for nvda is that the two people who started it were visionary, and not everyone can share the vision, if you get my drift.

 I don't know what is about to happen to tech, but it seems to me that nobody does. Who could have predicted this year that tablet sales have dropped but laptop and desktop sales are up. I suspect its down to novelty wearing off and nothing really new on the market just revamps of what has gone before.

 Personally, my gut tells me that although cloud computing can be good in some cases, many people do not want to pitch all their eggs into somebody elses basket. Its the same reason I still buy CDs. I don't want somebody taking my access away due to whatever. The danger at the moment is that the net is going down the packet priority  road as well, another legal form of highway robbery in my view.

 As for surveys, yes, well I already told you my opinion of those. Almost be better to use some tracking system, like a cookie to see what is on any given machine, but many would find that intrusive even though if you own an Android device its more or less going on now.

 Its all about trust and whether you can always trust others with data about you.

 If it can be created it can be hacked and  messed about with. Bots are all over the place after all.

 If you cannot trust the metrics one gets then the data collected becomes worthless.

 Anyway I'm up in the night again  wibbling on. Look at it this way, it matters what happens to nvda, but in the great scheme of life, what really matters is trying to be happy while you are  here on the planet. You cannot own other people like Mick or Jamie.

 

Its not right or  fair to expect people to be some kind of God.

 Been there got the TO Shirt, and the community awards etc, and for what?

 I prefer now to just help if I can but not to get so het up that it makes my life owned by others.

 Big mistake.

 Brian


bglists@... 
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
This message sent from a Windows XP machine!

----- Original Message -----

From: Joseph Lee

Sent: Saturday, December 23, 2017 5:25 PM

Subject: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials

 

Dear NVDA community,

 

As I read messages on recent discussions, I realized just how much enthusiasm and concern people have over NVDA and its future. At the same time, it became clear to me that I and other developers and community elders need a day off and just listen to you all, as listening allows us to think about what others are saying and plan things accordingly.

 

But first, a humble opinion about surveys and other points:

 

First, when calls for the seventh Web AIM survey went out, I told people to not just do it to “increase” market share. I specifically told screen reader companies to not coerce users to do it, but let people take it out of their own willingness. This advice was to avoid a fiasco that happened with Web AIM 6 where AI Squared (now part of VFO) staff told Window-Eyes users to fill out the survey in mass numbers, which became a small controversy within the screen reading world, and to me, making Web AIM results no longer credible.

 

As some folks pointed out, Web AIM numbers depend on how many people fill it out and where they come from (and this is true of any surveys where word of mouth drives participation). The results also depend on demographics and other factors such as choices given, how the questions are worded, and overall objective. If one or more data points seems to be dominant, they can be either skewed or outliers, with the more extreme cases being termed “outliers” and they affect how the results are explicated (interpreted). Even skewed data, such as what I can perceive from some surveys including recent Web AIM iterations can affect statistical calculations to a point where it raises genuine questions about bias, credibility, and others (after all, success of statistics, particularly inferential statistics, depends on a representative sample or a close equivalent that allows researchers to approximate the real world, which is prone to errors if not done correctly such as misinterpretation, bad outliers, only some groups participating, not looking at things more deeply and what not).

 

One important thing to note is that Web AIM is a representative survey, thus the result in front of me could reflect reality. However, due to recent controversy, possible type I and II errors (false-positive and false-negative, respectively) and because of outliers and skewed data and participation, it does not truly reflect actual data, which is a point some folks here are trying to say and I concur with. My explication of Web AIM 7 is that, in some parts of the world, JAWS for Windows is more popular. However, given the fact that not all geographical regions are represented, I’d counter by saying that this is not a true representative sample that includes every continent, and if it did, the story would be different and will reflect reality a bit better (not a lot because there are other ways of skewing data such as filling it out on behalf of an organization, robotic fillers and so on). Coupled with the fact that Web AIM went through a major controversy recently that damaged its credibility somewhat, I would dare not trust Web AIM results again.

 

This leads to my second point: quantity versus quality. If NV Access went straight for quantity alone, they could have implemented all possible feature requests in hopes of boosting market share. The reality in front of us says otherwise: not all feature requests are here. Numerous factors contribute to this problem:

 

  • Lack of leading developers: in 2017, a long-time NVDA developer started working for another organization, and NV Access has been looking for his replacement ever since. Even if the replacement is found, it’ll take several months for him or her to become used to this community, learn about accessibility and how to interact with members, and earn our trust (it took Reef Turner a year to fully earn our trust). Folks can counter this by saying that there are countless contributors out there, but ultimately what gets into NVDA depends on pull requests and review time from NV Access.
  • Attitudes about open-source software from organizations: as some folks pointed out, there are prevailing attitudes about open-source in organizations that makes it a bit harder for NVDA to land on their computers, which allows developers to assess true needs of organizations through user feedback. Without valuable feedback from organizations (a quality one at that), we won’t see huger progress in NVDA development.
  • Outside attitudes about the NVDA community: from the inside, NVDA community is seen as a tight nit of enthusiasts who strives to make NVDA better every day. On the outside, however, we have a mixed bag of reputations, from admiration to honorable mentions to disdain. Every organization have these mixed reputations, especially more so for a community powered by technology such as Linux kernel developers, web browser vendors and web standards organizations, and even screen reader community. Not only we need to show that we are united inside, we need to showcase unity outside of this community.
  • Inside matters just as outside: public relations outside of NVDA community is important, but unity within an organization is just as important as public organizational face (I’ll address developer’s point of view below). What makes NVDA stand out is our unity despite coming from different circumstances and backgrounds.

 

Most of these point to quality, not quantity alone. In summary, quantity is important, but quality is just as important as how many people download NVDA 2017.4 between Christmas and New Year.

 

Lastly, in regards to organization internals, I’d like to address something I really wanted to say for the past few weeks: sometimes, I felt burnt out. My initial response to your enthusiasm over my audio tutorials was that I’ll ask for justifications for producing an updated version, seeing that there are countless free videos and tutorials out there. This was partly because I truly felt burnt out with academics, speech and debate competitions and what not (especially after a debate regarding a potential feature held not long ago), at one point telling myself that I’ll retire from the NVDA community sooner than later and feeling as though I carried important burdens on my shoulders. But you didn’t see that justification post; instead, I posted links to where you can download the 2018 version of my audio tutorial series. In effect, I’ve given up my Christmas holidays for this community, knowing that I needed a time to listen to you all and do something about it. All this was possible because of a simple act of listening and thinking about what the community means to me and what my work means to everyone. I’m committed to finishing Welcome to NVDA 2018 series before NVDA 2018.1 ships, with several addenda coming after that, all because of support from this community and outsiders. And I promise again: The Welcome to NVDA 2018 series was, and will remain, free for all. All I ask of you in return is donate to a cause that makes equal access to technology possible, especially during this holiday season and beyond.

 

I’m sure for many of you, my musings above are a bit hard to digest. Now you know why I don’t trust Web AIM survey results, quality is just as important as quantity, and read a confession from a community leader on his inner feelings. But there are two more things you need to know, something all of us needs to think about:

 

Community leaders won’t stay with you forever. In early 2017, I sensed that a long-time NVDA developer would leave this community for something better. Only I and others didn’t know until summer that it would be Jamie moving onto Mozilla Foundation.

 

I also felt, back in early 2017, that my active time with the NVDA community is slowly drawing to a close. I don’t know when it’ll happen, but I’ve been laying foundations for the next generation of developers and enthusiasts to take the lead. This is one of the reasons for setting up the devlearning subgroup, because I felt it is time for me and other leaders to teach NVDA internals and other concepts to the next group of community leaders and developers so they can bring NVDA to the next level and do more amazing things than I and others did (in my case, for the past five years).

 

Lastly, I sense a time when this community will face a sharp divide to a point where people will start questioning the merits of this community. I only told a select few earlier because it wasn’t right for me to disclose it early and for them to prepare a plan. The screen shade debate is, in fact, a sort of a preview of what is to come. One of the fundamental questions you will face at that time will be whether you still have your first love for NVDA, and whether you still have your original reasons for joining this community. The survival of this community at that time will depend on your ability to unite to face a difficult situation, even if that means facing possible splits. One thing you should NOT do at that time: ignoring new users and outside critics, because they are influential opinion leaders and are key stakeholders in NVDA’s future. One thing you SHOULD do though: listen to others and think critically.

 

Hope this makes sense.

Merry (early) Christmas,

Joseph


Brian's Mail list account <bglists@...>
 

Unfortunately though, those who traditionally offered the training, do not have the resources to provide it any more. Its certainly the case in the UK as the Government increasingly tries to get charities to produce other services 'on the cheap'.
Also I have issues with trainers who teach by wrote, they do not carry the person along and explain what is going on to them, giving them the ability to adapt.



I'm not setting myself up as a trainer, but I wince sometimes when I encounter people who seem to have been told, don't bother about this or that you won't need it etc.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Adriani Botez" <adriani.botez@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, December 24, 2017 3:07 AM
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials


Brian,

With respect to investing money globally to make screen reader users more computer literate, well believe or not there was always a solution for that. A screen reader should imply a social movement and not a gain of capital out of selling. There are lots of development institutions, Christian Blind Mission, blind federations and lots of other non governamental organizations which support everything which gives people access to education, information and technology. But in the last 30 years, many people hoped to gain money out of selling licenses and did not really concentrate on learning the user detailed aspects on how to use that software. Thus, users became more and more change resistent because they invested lot of time to learn by themselves how to use it productively. In my opinion, we should not only think about technical aspects of a screen reader, but also about social impact and user interaction.

Best
Adriani


Von meinem iPhone gesendet

Am 24.12.2017 um 04:44 schrieb Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io>:

Certainly I do understand the burned out part of this its the same for all volunteers. if we are good at what we do we are in demand and take on more and more. it was only a comment from somebody else that made me try to bring a sense of realism to life. You cannot be a one man fixer of everything, and the cemeteries are full of people who were indispensable.
Most screenreader users are just that, users, many of us know the basics of what is going on, but really, its now so complex its beyond all but the few to grasp it all.
Obviously as we kind of slip into a world very much like we used to have in the 80s, where computers run lots of different operating systems and even windows differs in the internals between many different systems, the problems of access move from the screenreader to the platform.
that is, NVDA will probably be OK on mainstream Windows computers for some years, but with tablets, phones and various different processors and operating systems now coming in, its going to be the user who has to change and become expert in many more interfaces, as clearly, what we use in Windows today with a keyboard may not fit in any way the interface of the future.
Sadly the problem is as it always has been, training and the cost and indeed the ability of blind people particularly the older ones to actually grasp the abstract concepts and enable them to see equivalents and have a grasp of what is actually going on.
I really think that somebody needs to invest a lot more money globally in trying to get more blind people computer literate, but its just not happening, so although in theory we have access, not everyone will be able to actually use it.

Change is life after all, and people going to take other jobs is normal. the problem for nvda is that the two people who started it were visionary, and not everyone can share the vision, if you get my drift.
I don't know what is about to happen to tech, but it seems to me that nobody does. Who could have predicted this year that tablet sales have dropped but laptop and desktop sales are up. I suspect its down to novelty wearing off and nothing really new on the market just revamps of what has gone before.
Personally, my gut tells me that although cloud computing can be good in some cases, many people do not want to pitch all their eggs into somebody elses basket. Its the same reason I still buy CDs. I don't want somebody taking my access away due to whatever. The danger at the moment is that the net is going down the packet priority road as well, another legal form of highway robbery in my view.
As for surveys, yes, well I already told you my opinion of those. Almost be better to use some tracking system, like a cookie to see what is on any given machine, but many would find that intrusive even though if you own an Android device its more or less going on now.
Its all about trust and whether you can always trust others with data about you.
If it can be created it can be hacked and messed about with. Bots are all over the place after all.
If you cannot trust the metrics one gets then the data collected becomes worthless.
Anyway I'm up in the night again wibbling on. Look at it this way, it matters what happens to nvda, but in the great scheme of life, what really matters is trying to be happy while you are here on the planet. You cannot own other people like Mick or Jamie.

Its not right or fair to expect people to be some kind of God.
Been there got the TO Shirt, and the community awards etc, and for what?
I prefer now to just help if I can but not to get so het up that it makes my life owned by others.
Big mistake.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
This message sent from a Windows XP machine!
----- Original Message -----
From: Joseph Lee
To: nvda@nvda.groups.io
Sent: Saturday, December 23, 2017 5:25 PM
Subject: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials

Dear NVDA community,

As I read messages on recent discussions, I realized just how much enthusiasm and concern people have over NVDA and its future. At the same time, it became clear to me that I and other developers and community elders need a day off and just listen to you all, as listening allows us to think about what others are saying and plan things accordingly.

But first, a humble opinion about surveys and other points:

First, when calls for the seventh Web AIM survey went out, I told people to not just do it to “increase” market share. I specifically told screen reader companies to not coerce users to do it, but let people take it out of their own willingness. This advice was to avoid a fiasco that happened with Web AIM 6 where AI Squared (now part of VFO) staff told Window-Eyes users to fill out the survey in mass numbers, which became a small controversy within the screen reading world, and to me, making Web AIM results no longer credible.

As some folks pointed out, Web AIM numbers depend on how many people fill it out and where they come from (and this is true of any surveys where word of mouth drives participation). The results also depend on demographics and other factors such as choices given, how the questions are worded, and overall objective. If one or more data points seems to be dominant, they can be either skewed or outliers, with the more extreme cases being termed “outliers” and they affect how the results are explicated (interpreted). Even skewed data, such as what I can perceive from some surveys including recent Web AIM iterations can affect statistical calculations to a point where it raises genuine questions about bias, credibility, and others (after all, success of statistics, particularly inferential statistics, depends on a representative sample or a close equivalent that allows researchers to approximate the real world, which is prone to errors if not done correctly such as misinterpretation, bad outliers, only some groups participating, not looking at things more deeply and what not).

One important thing to note is that Web AIM is a representative survey, thus the result in front of me could reflect reality. However, due to recent controversy, possible type I and II errors (false-positive and false-negative, respectively) and because of outliers and skewed data and participation, it does not truly reflect actual data, which is a point some folks here are trying to say and I concur with. My explication of Web AIM 7 is that, in some parts of the world, JAWS for Windows is more popular. However, given the fact that not all geographical regions are represented, I’d counter by saying that this is not a true representative sample that includes every continent, and if it did, the story would be different and will reflect reality a bit better (not a lot because there are other ways of skewing data such as filling it out on behalf of an organization, robotic fillers and so on). Coupled with the fact that Web AIM went through a major controversy recently that damaged its credibility somewhat, I would dare not trust Web AIM results again.

This leads to my second point: quantity versus quality. If NV Access went straight for quantity alone, they could have implemented all possible feature requests in hopes of boosting market share. The reality in front of us says otherwise: not all feature requests are here. Numerous factors contribute to this problem:

Lack of leading developers: in 2017, a long-time NVDA developer started working for another organization, and NV Access has been looking for his replacement ever since. Even if the replacement is found, it’ll take several months for him or her to become used to this community, learn about accessibility and how to interact with members, and earn our trust (it took Reef Turner a year to fully earn our trust). Folks can counter this by saying that there are countless contributors out there, but ultimately what gets into NVDA depends on pull requests and review time from NV Access.
Attitudes about open-source software from organizations: as some folks pointed out, there are prevailing attitudes about open-source in organizations that makes it a bit harder for NVDA to land on their computers, which allows developers to assess true needs of organizations through user feedback. Without valuable feedback from organizations (a quality one at that), we won’t see huger progress in NVDA development.
Outside attitudes about the NVDA community: from the inside, NVDA community is seen as a tight nit of enthusiasts who strives to make NVDA better every day. On the outside, however, we have a mixed bag of reputations, from admiration to honorable mentions to disdain. Every organization have these mixed reputations, especially more so for a community powered by technology such as Linux kernel developers, web browser vendors and web standards organizations, and even screen reader community. Not only we need to show that we are united inside, we need to showcase unity outside of this community.
Inside matters just as outside: public relations outside of NVDA community is important, but unity within an organization is just as important as public organizational face (I’ll address developer’s point of view below). What makes NVDA stand out is our unity despite coming from different circumstances and backgrounds.

Most of these point to quality, not quantity alone. In summary, quantity is important, but quality is just as important as how many people download NVDA 2017.4 between Christmas and New Year.

Lastly, in regards to organization internals, I’d like to address something I really wanted to say for the past few weeks: sometimes, I felt burnt out. My initial response to your enthusiasm over my audio tutorials was that I’ll ask for justifications for producing an updated version, seeing that there are countless free videos and tutorials out there. This was partly because I truly felt burnt out with academics, speech and debate competitions and what not (especially after a debate regarding a potential feature held not long ago), at one point telling myself that I’ll retire from the NVDA community sooner than later and feeling as though I carried important burdens on my shoulders. But you didn’t see that justification post; instead, I posted links to where you can download the 2018 version of my audio tutorial series. In effect, I’ve given up my Christmas holidays for this community, knowing that I needed a time to listen to you all and do something about it. All this was possible because of a simple act of listening and thinking about what the community means to me and what my work means to everyone. I’m committed to finishing Welcome to NVDA 2018 series before NVDA 2018.1 ships, with several addenda coming after that, all because of support from this community and outsiders. And I promise again: The Welcome to NVDA 2018 series was, and will remain, free for all. All I ask of you in return is donate to a cause that makes equal access to technology possible, especially during this holiday season and beyond.

I’m sure for many of you, my musings above are a bit hard to digest. Now you know why I don’t trust Web AIM survey results, quality is just as important as quantity, and read a confession from a community leader on his inner feelings. But there are two more things you need to know, something all of us needs to think about:

Community leaders won’t stay with you forever. In early 2017, I sensed that a long-time NVDA developer would leave this community for something better. Only I and others didn’t know until summer that it would be Jamie moving onto Mozilla Foundation.

I also felt, back in early 2017, that my active time with the NVDA community is slowly drawing to a close. I don’t know when it’ll happen, but I’ve been laying foundations for the next generation of developers and enthusiasts to take the lead. This is one of the reasons for setting up the devlearning subgroup, because I felt it is time for me and other leaders to teach NVDA internals and other concepts to the next group of community leaders and developers so they can bring NVDA to the next level and do more amazing things than I and others did (in my case, for the past five years).

Lastly, I sense a time when this community will face a sharp divide to a point where people will start questioning the merits of this community. I only told a select few earlier because it wasn’t right for me to disclose it early and for them to prepare a plan. The screen shade debate is, in fact, a sort of a preview of what is to come. One of the fundamental questions you will face at that time will be whether you still have your first love for NVDA, and whether you still have your original reasons for joining this community. The survival of this community at that time will depend on your ability to unite to face a difficult situation, even if that means facing possible splits. One thing you should NOT do at that time: ignoring new users and outside critics, because they are influential opinion leaders and are key stakeholders in NVDA’s future. One thing you SHOULD do though: listen to others and think critically.

Hope this makes sense.
Merry (early) Christmas,
Joseph


Brian's Mail list account <bglists@...>
 

Well I'm not so sure this is the whole story. I notice that the same argument is going on on the hardware front now. IE a smart phone can do most of what a media player, OCR machine, and navigational aid did. The people are still trying to sell such hardware, and I'd imagine in certain cases, they might have a a use, ie if the user has poor feeling in their hands or a tremor etc, but for the masses, no.
As I noted before, I don't like the kind of computer access Dolphin Guide gives. Its just a suite of self voicing software. It traps you.
Than goodness people can now put nvda on such machines and then when folk like me come along to help them when windows throws a wobbly we can.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Sky Mundell" <skyt@shaw.ca>
To: <nvda@nvda.groups.io>
Sent: Sunday, December 24, 2017 3:26 AM
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials


I totally agree with you. You are absolutely right. Screen readers should certainly be a social impact. The reason there is capital invested in it is because the agencies are the ones who are funding the capital.



From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Adriani Botez
Sent: Saturday, December 23, 2017 7:08 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials



Brian,



With respect to investing money globally to make screen reader users more computer literate, well believe or not there was always a solution for that. A screen reader should imply a social movement and not a gain of capital out of selling. There are lots of development institutions, Christian Blind Mission, blind federations and lots of other non governamental organizations which support everything which gives people access to education, information and technology. But in the last 30 years, many people hoped to gain money out of selling licenses and did not really concentrate on learning the user detailed aspects on how to use that software. Thus, users became more and more change resistent because they invested lot of time to learn by themselves how to use it productively. In my opinion, we should not only think about technical aspects of a screen reader, but also about social impact and user interaction.



Best

Adriani



Von meinem iPhone gesendet


Am 24.12.2017 um 04:44 schrieb Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io>:

Certainly I do understand the burned out part of this its the same for all volunteers. if we are good at what we do we are in demand and take on more and more. it was only a comment from somebody else that made me try to bring a sense of realism to life. You cannot be a one man fixer of everything, and the cemeteries are full of people who were indispensable.

Most screenreader users are just that, users, many of us know the basics of what is going on, but really, its now so complex its beyond all but the few to grasp it all.

Obviously as we kind of slip into a world very much like we used to have in the 80s, where computers run lots of different operating systems and even windows differs in the internals between many different systems, the problems of access move from the screenreader to the platform.

that is, NVDA will probably be OK on mainstream Windows computers for some years, but with tablets, phones and various different processors and operating systems now coming in, its going to be the user who has to change and become expert in many more interfaces, as clearly, what we use in Windows today with a keyboard may not fit in any way the interface of the future.

Sadly the problem is as it always has been, training and the cost and indeed the ability of blind people particularly the older ones to actually grasp the abstract concepts and enable them to see equivalents and have a grasp of what is actually going on.

I really think that somebody needs to invest a lot more money globally in trying to get more blind people computer literate, but its just not happening, so although in theory we have access, not everyone will be able to actually use it.



Change is life after all, and people going to take other jobs is normal. the problem for nvda is that the two people who started it were visionary, and not everyone can share the vision, if you get my drift.

I don't know what is about to happen to tech, but it seems to me that nobody does. Who could have predicted this year that tablet sales have dropped but laptop and desktop sales are up. I suspect its down to novelty wearing off and nothing really new on the market just revamps of what has gone before.

Personally, my gut tells me that although cloud computing can be good in some cases, many people do not want to pitch all their eggs into somebody elses basket. Its the same reason I still buy CDs. I don't want somebody taking my access away due to whatever. The danger at the moment is that the net is going down the packet priority road as well, another legal form of highway robbery in my view.

As for surveys, yes, well I already told you my opinion of those. Almost be better to use some tracking system, like a cookie to see what is on any given machine, but many would find that intrusive even though if you own an Android device its more or less going on now.

Its all about trust and whether you can always trust others with data about you.

If it can be created it can be hacked and messed about with. Bots are all over the place after all.

If you cannot trust the metrics one gets then the data collected becomes worthless.

Anyway I'm up in the night again wibbling on. Look at it this way, it matters what happens to nvda, but in the great scheme of life, what really matters is trying to be happy while you are here on the planet. You cannot own other people like Mick or Jamie.



Its not right or fair to expect people to be some kind of God.

Been there got the TO Shirt, and the community awards etc, and for what?

I prefer now to just help if I can but not to get so het up that it makes my life owned by others.

Big mistake.

Brian


bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
This message sent from a Windows XP machine!

----- Original Message -----

From: Joseph Lee <mailto:joseph.lee22590@gmail.com>

To: nvda@nvda.groups.io

Sent: Saturday, December 23, 2017 5:25 PM

Subject: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials



Dear NVDA community,



As I read messages on recent discussions, I realized just how much enthusiasm and concern people have over NVDA and its future. At the same time, it became clear to me that I and other developers and community elders need a day off and just listen to you all, as listening allows us to think about what others are saying and plan things accordingly.



But first, a humble opinion about surveys and other points:



First, when calls for the seventh Web AIM survey went out, I told people to not just do it to “increase” market share. I specifically told screen reader companies to not coerce users to do it, but let people take it out of their own willingness. This advice was to avoid a fiasco that happened with Web AIM 6 where AI Squared (now part of VFO) staff told Window-Eyes users to fill out the survey in mass numbers, which became a small controversy within the screen reading world, and to me, making Web AIM results no longer credible.



As some folks pointed out, Web AIM numbers depend on how many people fill it out and where they come from (and this is true of any surveys where word of mouth drives participation). The results also depend on demographics and other factors such as choices given, how the questions are worded, and overall objective. If one or more data points seems to be dominant, they can be either skewed or outliers, with the more extreme cases being termed “outliers” and they affect how the results are explicated (interpreted). Even skewed data, such as what I can perceive from some surveys including recent Web AIM iterations can affect statistical calculations to a point where it raises genuine questions about bias, credibility, and others (after all, success of statistics, particularly inferential statistics, depends on a representative sample or a close equivalent that allows researchers to approximate the real world, which is prone to errors if not done correctly such as misinterpretation, bad outliers, only some groups participating, not looking at things more deeply and what not).



One important thing to note is that Web AIM is a representative survey, thus the result in front of me could reflect reality. However, due to recent controversy, possible type I and II errors (false-positive and false-negative, respectively) and because of outliers and skewed data and participation, it does not truly reflect actual data, which is a point some folks here are trying to say and I concur with. My explication of Web AIM 7 is that, in some parts of the world, JAWS for Windows is more popular. However, given the fact that not all geographical regions are represented, I’d counter by saying that this is not a true representative sample that includes every continent, and if it did, the story would be different and will reflect reality a bit better (not a lot because there are other ways of skewing data such as filling it out on behalf of an organization, robotic fillers and so on). Coupled with the fact that Web AIM went through a major controversy recently that damaged its credibility somewhat, I would dare not trust Web AIM results again.



This leads to my second point: quantity versus quality. If NV Access went straight for quantity alone, they could have implemented all possible feature requests in hopes of boosting market share. The reality in front of us says otherwise: not all feature requests are here. Numerous factors contribute to this problem:



* Lack of leading developers: in 2017, a long-time NVDA developer started working for another organization, and NV Access has been looking for his replacement ever since. Even if the replacement is found, it’ll take several months for him or her to become used to this community, learn about accessibility and how to interact with members, and earn our trust (it took Reef Turner a year to fully earn our trust). Folks can counter this by saying that there are countless contributors out there, but ultimately what gets into NVDA depends on pull requests and review time from NV Access.
* Attitudes about open-source software from organizations: as some folks pointed out, there are prevailing attitudes about open-source in organizations that makes it a bit harder for NVDA to land on their computers, which allows developers to assess true needs of organizations through user feedback. Without valuable feedback from organizations (a quality one at that), we won’t see huger progress in NVDA development.
* Outside attitudes about the NVDA community: from the inside, NVDA community is seen as a tight nit of enthusiasts who strives to make NVDA better every day. On the outside, however, we have a mixed bag of reputations, from admiration to honorable mentions to disdain. Every organization have these mixed reputations, especially more so for a community powered by technology such as Linux kernel developers, web browser vendors and web standards organizations, and even screen reader community. Not only we need to show that we are united inside, we need to showcase unity outside of this community.
* Inside matters just as outside: public relations outside of NVDA community is important, but unity within an organization is just as important as public organizational face (I’ll address developer’s point of view below). What makes NVDA stand out is our unity despite coming from different circumstances and backgrounds.



Most of these point to quality, not quantity alone. In summary, quantity is important, but quality is just as important as how many people download NVDA 2017.4 between Christmas and New Year.



Lastly, in regards to organization internals, I’d like to address something I really wanted to say for the past few weeks: sometimes, I felt burnt out. My initial response to your enthusiasm over my audio tutorials was that I’ll ask for justifications for producing an updated version, seeing that there are countless free videos and tutorials out there. This was partly because I truly felt burnt out with academics, speech and debate competitions and what not (especially after a debate regarding a potential feature held not long ago), at one point telling myself that I’ll retire from the NVDA community sooner than later and feeling as though I carried important burdens on my shoulders. But you didn’t see that justification post; instead, I posted links to where you can download the 2018 version of my audio tutorial series. In effect, I’ve given up my Christmas holidays for this community, knowing that I needed a time to listen to you all and do something about it. All this was possible because of a simple act of listening and thinking about what the community means to me and what my work means to everyone. I’m committed to finishing Welcome to NVDA 2018 series before NVDA 2018.1 ships, with several addenda coming after that, all because of support from this community and outsiders. And I promise again: The Welcome to NVDA 2018 series was, and will remain, free for all. All I ask of you in return is donate to a cause that makes equal access to technology possible, especially during this holiday season and beyond.



I’m sure for many of you, my musings above are a bit hard to digest. Now you know why I don’t trust Web AIM survey results, quality is just as important as quantity, and read a confession from a community leader on his inner feelings. But there are two more things you need to know, something all of us needs to think about:



Community leaders won’t stay with you forever. In early 2017, I sensed that a long-time NVDA developer would leave this community for something better. Only I and others didn’t know until summer that it would be Jamie moving onto Mozilla Foundation.



I also felt, back in early 2017, that my active time with the NVDA community is slowly drawing to a close. I don’t know when it’ll happen, but I’ve been laying foundations for the next generation of developers and enthusiasts to take the lead. This is one of the reasons for setting up the devlearning subgroup, because I felt it is time for me and other leaders to teach NVDA internals and other concepts to the next group of community leaders and developers so they can bring NVDA to the next level and do more amazing things than I and others did (in my case, for the past five years).



Lastly, I sense a time when this community will face a sharp divide to a point where people will start questioning the merits of this community. I only told a select few earlier because it wasn’t right for me to disclose it early and for them to prepare a plan. The screen shade debate is, in fact, a sort of a preview of what is to come. One of the fundamental questions you will face at that time will be whether you still have your first love for NVDA, and whether you still have your original reasons for joining this community. The survival of this community at that time will depend on your ability to unite to face a difficult situation, even if that means facing possible splits. One thing you should NOT do at that time: ignoring new users and outside critics, because they are influential opinion leaders and are key stakeholders in NVDA’s future. One thing you SHOULD do though: listen to others and think critically.



Hope this makes sense.

Merry (early) Christmas,

Joseph


 

Well dedicated hardware while costing a bit has a few advantages.

1.  bigger speakers, no added destractions etc.

The issue of all on one device is that especially with traditional headphone jacks going you can't just connect a pair of speakers anymore.

Even with that out the way, if you load your smartphone with a lot of stuff, you will still use that power.

Bluetooth, gps, and data use a lot if you are not carefull never mind that if you are not in the country you registered in the data will cost a lot so you will need to turn that off.

Unless you are on wifi and some of that can be not secured.

Even if you have extra batteries with the revelations of apple slowing devices, you will now have to add in new devices costs or batteries for that device.

Most dedicated devices at least quite a few will either have their battery which they use or if you are lucky use standard off the shelf batteries which actually don't cost that much especially if you buy that in a bundle.

I have a lot of electronics using aa and tripple aa battery types, and it costs not much to run any of them.

On 24/12/2017 10:18 p.m., Brian's Mail list account via Groups.Io wrote:
Well I'm not so sure this is the whole story. I notice that the same argument is going on on the hardware front now. IE a smart phone can do most of what a media player, OCR machine, and navigational aid did. The people are still trying to sell such hardware, and I'd imagine in certain cases, they might have a a use, ie if the user has poor feeling in their hands or a tremor etc, but for the masses, no.
As I noted before, I don't like the kind of computer access Dolphin Guide gives. Its just a suite of  self voicing software. It traps you.
Than goodness people can now put nvda on such machines and then when folk like me come along to help them when windows throws a wobbly we can.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Sky Mundell" <skyt@shaw.ca>
To: <nvda@nvda.groups.io>
Sent: Sunday, December 24, 2017 3:26 AM
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials


I totally agree with you. You are absolutely right.  Screen readers should certainly be a social impact. The reason there is capital invested in it is because the agencies are the ones who are funding the capital.



From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Adriani Botez
Sent: Saturday, December 23, 2017 7:08 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials



Brian,



With respect to investing money globally to make screen reader users more computer literate, well believe or not there was always a solution for that. A screen reader should imply a social movement and not a gain of capital out of selling. There are lots of development institutions, Christian Blind Mission, blind federations and lots of other non governamental organizations which support everything which gives people access to education, information and technology. But in the last 30 years, many people hoped to gain money out of selling licenses and did not really concentrate on learning the user detailed aspects on how to use that software. Thus, users became more and more change resistent because they invested lot of time to learn by themselves how to use it productively. In my opinion, we should not only think about technical aspects of a screen reader, but also about social impact and user interaction.



Best

Adriani



Von meinem iPhone gesendet


Am 24.12.2017 um 04:44 schrieb Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io>:

Certainly I do understand the burned out part of this its the same for all volunteers. if we are good at what we do we are in demand and take on more and more. it was only a comment from somebody else that made me try to bring a sense of realism to life. You cannot be a one man fixer of everything, and the cemeteries are full of people who were indispensable.

Most screenreader users are just that, users, many of us know the basics of what is going on, but really, its now so complex its beyond all but the few to grasp it all.

Obviously as we kind of slip into a world very much like we used to have in the 80s, where computers run lots of different operating systems and even windows differs  in the internals between many different systems, the problems of access move from the screenreader to the platform.

that is, NVDA will probably be OK on mainstream Windows computers for some years, but with tablets, phones and various different processors and operating systems now coming in, its going to be the user who has to change and become expert in many more interfaces, as clearly, what we use in Windows today with a keyboard may not fit in any way the interface of the future.

Sadly the problem is as it always has been, training and the cost and indeed the ability of blind people particularly the older ones to actually grasp the abstract concepts and enable them to see equivalents  and have a grasp of what is actually going on.

I really think that somebody needs to invest a lot more money globally in trying to get more blind people computer literate, but its just not happening, so although in theory we have access, not everyone will be able to actually use it.



Change is life after all, and people going to take other jobs is normal. the problem for nvda is that the two people who started it were visionary, and not everyone can share the vision, if you get my drift.

I don't know what is about to happen to tech, but it seems to me that nobody does. Who could have predicted this year that tablet sales have dropped but laptop and desktop sales are up. I suspect its down to novelty wearing off and nothing really new on the market just revamps of what has gone before.

Personally, my gut tells me that although cloud computing can be good in some cases, many people do not want to pitch all their eggs into somebody elses basket. Its the same reason I still buy CDs. I don't want somebody taking my access away due to whatever. The danger at the moment is that the net is going down the packet priority  road as well, another legal form of highway robbery in my view.

As for surveys, yes, well I already told you my opinion of those. Almost be better to use some tracking system, like a cookie to see what is on any given machine, but many would find that intrusive even though if you own an Android device its more or less going on now.

Its all about trust and whether you can always trust others with data about you.

If it can be created it can be hacked and  messed about with. Bots are all over the place after all.

If you cannot trust the metrics one gets then the data collected becomes worthless.

Anyway I'm up in the night again  wibbling on. Look at it this way, it matters what happens to nvda, but in the great scheme of life, what really matters is trying to be happy while you are here on the planet. You cannot own other people like Mick or Jamie.



Its not right or  fair to expect people to be some kind of God.

Been there got the TO Shirt, and the community awards etc, and for what?

I prefer now to just help if I can but not to get so het up that it makes my life owned by others.

Big mistake.

Brian


bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
This message sent from a Windows XP machine!

----- Original Message -----
From: Joseph Lee <mailto:joseph.lee22590@gmail.com>

To: nvda@nvda.groups.io

Sent: Saturday, December 23, 2017 5:25 PM

Subject: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials



Dear NVDA community,



As I read messages on recent discussions, I realized just how much enthusiasm and concern people have over NVDA and its future. At the same time, it became clear to me that I and other developers and community elders need a day off and just listen to you all, as listening allows us to think about what others are saying and plan things accordingly.



But first, a humble opinion about surveys and other points:



First, when calls for the seventh Web AIM survey went out, I told people to not just do it to “increase” market share. I specifically told screen reader companies to not coerce users to do it, but let people take it out of their own willingness. This advice was to avoid a fiasco that happened with Web AIM 6 where AI Squared (now part of VFO) staff told Window-Eyes users to fill out the survey in mass numbers, which became a small controversy within the screen reading world, and to me, making Web AIM results no longer credible.



As some folks pointed out, Web AIM numbers depend on how many people fill it out and where they come from (and this is true of any surveys where word of mouth drives participation). The results also depend on demographics and other factors such as choices given, how the questions are worded, and overall objective. If one or more data points seems to be dominant, they can be either skewed or outliers, with the more extreme cases being termed “outliers” and they affect how the results are explicated (interpreted). Even skewed data, such as what I can perceive from some surveys including recent Web AIM iterations can affect statistical calculations to a point where it raises genuine questions about bias, credibility, and others (after all, success of statistics, particularly inferential statistics, depends on a representative sample or a close equivalent that allows researchers to approximate the real world, which is prone to errors if not done correctly such as misinterpretation, bad outliers, only some groups participating, not looking at things more deeply and what not).



One important thing to note is that Web AIM is a representative survey, thus the result in front of me could reflect reality. However, due to recent controversy, possible type I and II errors (false-positive and false-negative, respectively) and because of outliers and skewed data and participation, it does not truly reflect actual data, which is a point some folks here are trying to say and I concur with. My explication of Web AIM 7 is that, in some parts of the world, JAWS for Windows is more popular. However, given the fact that not all geographical regions are represented, I’d counter by saying that this is not a true representative sample that includes every continent, and if it did, the story would be different and will reflect reality a bit better (not a lot because there are other ways of skewing data such as filling it out on behalf of an organization, robotic fillers and so on). Coupled with the fact that Web AIM went through a major controversy recently that damaged its credibility somewhat, I would dare not trust Web AIM results again.



This leads to my second point: quantity versus quality. If NV Access went straight for quantity alone, they could have implemented all possible feature requests in hopes of boosting market share. The reality in front of us says otherwise: not all feature requests are here. Numerous factors contribute to this problem:



* Lack of leading developers: in 2017, a long-time NVDA developer started working for another organization, and NV Access has been looking for his replacement ever since. Even if the replacement is found, it’ll take several months for him or her to become used to this community, learn about accessibility and how to interact with members, and earn our trust (it took Reef Turner a year to fully earn our trust). Folks can counter this by saying that there are countless contributors out there, but ultimately what gets into NVDA depends on pull requests and review time from NV Access.
* Attitudes about open-source software from organizations: as some folks pointed out, there are prevailing attitudes about open-source in organizations that makes it a bit harder for NVDA to land on their computers, which allows developers to assess true needs of organizations through user feedback. Without valuable feedback from organizations (a quality one at that), we won’t see huger progress in NVDA development.
* Outside attitudes about the NVDA community: from the inside, NVDA community is seen as a tight nit of enthusiasts who strives to make NVDA better every day. On the outside, however, we have a mixed bag of reputations, from admiration to honorable mentions to disdain. Every organization have these mixed reputations, especially more so for a community powered by technology such as Linux kernel developers, web browser vendors and web standards organizations, and even screen reader community. Not only we need to show that we are united inside, we need to showcase unity outside of this community.
* Inside matters just as outside: public relations outside of NVDA community is important, but unity within an organization is just as important as public organizational face (I’ll address developer’s point of view below). What makes NVDA stand out is our unity despite coming from different circumstances and backgrounds.



Most of these point to quality, not quantity alone. In summary, quantity is important, but quality is just as important as how many people download NVDA 2017.4 between Christmas and New Year.



Lastly, in regards to organization internals, I’d like to address something I really wanted to say for the past few weeks: sometimes, I felt burnt out. My initial response to your enthusiasm over my audio tutorials was that I’ll ask for justifications for producing an updated version, seeing that there are countless free videos and tutorials out there. This was partly because I truly felt burnt out with academics, speech and debate competitions and what not (especially after a debate regarding a potential feature held not long ago), at one point telling myself that I’ll retire from the NVDA community sooner than later and feeling as though I carried important burdens on my shoulders. But you didn’t see that justification post; instead, I posted links to where you can download the 2018 version of my audio tutorial series. In effect, I’ve given up my Christmas holidays for this community, knowing that I needed a time to listen to you all and do something about it. All this was possible because of a simple act of listening and thinking about what the community means to me and what my work means to everyone. I’m committed to finishing Welcome to NVDA 2018 series before NVDA 2018.1 ships, with several addenda coming after that, all because of support from this community and outsiders. And I promise again: The Welcome to NVDA 2018 series was, and will remain, free for all. All I ask of you in return is donate to a cause that makes equal access to technology possible, especially during this holiday season and beyond.



I’m sure for many of you, my musings above are a bit hard to digest. Now you know why I don’t trust Web AIM survey results, quality is just as important as quantity, and read a confession from a community leader on his inner feelings. But there are two more things you need to know, something all of us needs to think about:



Community leaders won’t stay with you forever. In early 2017, I sensed that a long-time NVDA developer would leave this community for something better. Only I and others didn’t know until summer that it would be Jamie moving onto Mozilla Foundation.



I also felt, back in early 2017, that my active time with the NVDA community is slowly drawing to a close. I don’t know when it’ll happen, but I’ve been laying foundations for the next generation of developers and enthusiasts to take the lead. This is one of the reasons for setting up the devlearning subgroup, because I felt it is time for me and other leaders to teach NVDA internals and other concepts to the next group of community leaders and developers so they can bring NVDA to the next level and do more amazing things than I and others did (in my case, for the past five years).



Lastly, I sense a time when this community will face a sharp divide to a point where people will start questioning the merits of this community. I only told a select few earlier because it wasn’t right for me to disclose it early and for them to prepare a plan. The screen shade debate is, in fact, a sort of a preview of what is to come. One of the fundamental questions you will face at that time will be whether you still have your first love for NVDA, and whether you still have your original reasons for joining this community. The survival of this community at that time will depend on your ability to unite to face a difficult situation, even if that means facing possible splits. One thing you should NOT do at that time: ignoring new users and outside critics, because they are influential opinion leaders and are key stakeholders in NVDA’s future. One thing you SHOULD do though: listen to others and think critically.



Hope this makes sense.

Merry (early) Christmas,

Joseph






.


Brian's Mail list account <bglists@...>
 

I was thinking more in the region of cost. Many of us watch costs, but if its for work in many well off economies, the equipment and software is purchased by the state.
Think of the Braille display. A lot has been made of late of these being used by nvda and indeed mainstream gear like Apple products, but really unless the person is well off these devices are a luxury unless bought by an organisation or government.

The same can be said of all the other devices. Also if you want things to be portable, you want to have a solution that does not demand you take half a truck load of gear everywhere you go.
I had to chuckle the other day when Humanware launched their Trek, which is basically a media player, downloader and GPs in a box.
If they only added a cellular modem and a camera, they would have a phone.

Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Shaun Everiss" <sm.everiss@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, December 24, 2017 11:05 PM
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials


Well dedicated hardware while costing a bit has a few advantages.

1. bigger speakers, no added destractions etc.

The issue of all on one device is that especially with traditional headphone jacks going you can't just connect a pair of speakers anymore.

Even with that out the way, if you load your smartphone with a lot of stuff, you will still use that power.

Bluetooth, gps, and data use a lot if you are not carefull never mind that if you are not in the country you registered in the data will cost a lot so you will need to turn that off.

Unless you are on wifi and some of that can be not secured.

Even if you have extra batteries with the revelations of apple slowing devices, you will now have to add in new devices costs or batteries for that device.

Most dedicated devices at least quite a few will either have their battery which they use or if you are lucky use standard off the shelf batteries which actually don't cost that much especially if you buy that in a bundle.

I have a lot of electronics using aa and tripple aa battery types, and it costs not much to run any of them.




On 24/12/2017 10:18 p.m., Brian's Mail list account via Groups.Io wrote:
Well I'm not so sure this is the whole story. I notice that the same argument is going on on the hardware front now. IE a smart phone can do most of what a media player, OCR machine, and navigational aid did. The people are still trying to sell such hardware, and I'd imagine in certain cases, they might have a a use, ie if the user has poor feeling in their hands or a tremor etc, but for the masses, no.
As I noted before, I don't like the kind of computer access Dolphin Guide gives. Its just a suite of self voicing software. It traps you.
Than goodness people can now put nvda on such machines and then when folk like me come along to help them when windows throws a wobbly we can.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Sky Mundell" <skyt@shaw.ca>
To: <nvda@nvda.groups.io>
Sent: Sunday, December 24, 2017 3:26 AM
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials


I totally agree with you. You are absolutely right. Screen readers should certainly be a social impact. The reason there is capital invested in it is because the agencies are the ones who are funding the capital.



From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Adriani Botez
Sent: Saturday, December 23, 2017 7:08 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials



Brian,



With respect to investing money globally to make screen reader users more computer literate, well believe or not there was always a solution for that. A screen reader should imply a social movement and not a gain of capital out of selling. There are lots of development institutions, Christian Blind Mission, blind federations and lots of other non governamental organizations which support everything which gives people access to education, information and technology. But in the last 30 years, many people hoped to gain money out of selling licenses and did not really concentrate on learning the user detailed aspects on how to use that software. Thus, users became more and more change resistent because they invested lot of time to learn by themselves how to use it productively. In my opinion, we should not only think about technical aspects of a screen reader, but also about social impact and user interaction.



Best

Adriani



Von meinem iPhone gesendet


Am 24.12.2017 um 04:44 schrieb Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io>:

Certainly I do understand the burned out part of this its the same for all volunteers. if we are good at what we do we are in demand and take on more and more. it was only a comment from somebody else that made me try to bring a sense of realism to life. You cannot be a one man fixer of everything, and the cemeteries are full of people who were indispensable.

Most screenreader users are just that, users, many of us know the basics of what is going on, but really, its now so complex its beyond all but the few to grasp it all.

Obviously as we kind of slip into a world very much like we used to have in the 80s, where computers run lots of different operating systems and even windows differs in the internals between many different systems, the problems of access move from the screenreader to the platform.

that is, NVDA will probably be OK on mainstream Windows computers for some years, but with tablets, phones and various different processors and operating systems now coming in, its going to be the user who has to change and become expert in many more interfaces, as clearly, what we use in Windows today with a keyboard may not fit in any way the interface of the future.

Sadly the problem is as it always has been, training and the cost and indeed the ability of blind people particularly the older ones to actually grasp the abstract concepts and enable them to see equivalents and have a grasp of what is actually going on.

I really think that somebody needs to invest a lot more money globally in trying to get more blind people computer literate, but its just not happening, so although in theory we have access, not everyone will be able to actually use it.



Change is life after all, and people going to take other jobs is normal. the problem for nvda is that the two people who started it were visionary, and not everyone can share the vision, if you get my drift.

I don't know what is about to happen to tech, but it seems to me that nobody does. Who could have predicted this year that tablet sales have dropped but laptop and desktop sales are up. I suspect its down to novelty wearing off and nothing really new on the market just revamps of what has gone before.

Personally, my gut tells me that although cloud computing can be good in some cases, many people do not want to pitch all their eggs into somebody elses basket. Its the same reason I still buy CDs. I don't want somebody taking my access away due to whatever. The danger at the moment is that the net is going down the packet priority road as well, another legal form of highway robbery in my view.

As for surveys, yes, well I already told you my opinion of those. Almost be better to use some tracking system, like a cookie to see what is on any given machine, but many would find that intrusive even though if you own an Android device its more or less going on now.

Its all about trust and whether you can always trust others with data about you.

If it can be created it can be hacked and messed about with. Bots are all over the place after all.

If you cannot trust the metrics one gets then the data collected becomes worthless.

Anyway I'm up in the night again wibbling on. Look at it this way, it matters what happens to nvda, but in the great scheme of life, what really matters is trying to be happy while you are here on the planet. You cannot own other people like Mick or Jamie.



Its not right or fair to expect people to be some kind of God.

Been there got the TO Shirt, and the community awards etc, and for what?

I prefer now to just help if I can but not to get so het up that it makes my life owned by others.

Big mistake.

Brian


bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
This message sent from a Windows XP machine!

----- Original Message -----
From: Joseph Lee <mailto:joseph.lee22590@gmail.com>

To: nvda@nvda.groups.io

Sent: Saturday, December 23, 2017 5:25 PM

Subject: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials



Dear NVDA community,



As I read messages on recent discussions, I realized just how much enthusiasm and concern people have over NVDA and its future. At the same time, it became clear to me that I and other developers and community elders need a day off and just listen to you all, as listening allows us to think about what others are saying and plan things accordingly.



But first, a humble opinion about surveys and other points:



First, when calls for the seventh Web AIM survey went out, I told people to not just do it to “increase” market share. I specifically told screen reader companies to not coerce users to do it, but let people take it out of their own willingness. This advice was to avoid a fiasco that happened with Web AIM 6 where AI Squared (now part of VFO) staff told Window-Eyes users to fill out the survey in mass numbers, which became a small controversy within the screen reading world, and to me, making Web AIM results no longer credible.



As some folks pointed out, Web AIM numbers depend on how many people fill it out and where they come from (and this is true of any surveys where word of mouth drives participation). The results also depend on demographics and other factors such as choices given, how the questions are worded, and overall objective. If one or more data points seems to be dominant, they can be either skewed or outliers, with the more extreme cases being termed “outliers” and they affect how the results are explicated (interpreted). Even skewed data, such as what I can perceive from some surveys including recent Web AIM iterations can affect statistical calculations to a point where it raises genuine questions about bias, credibility, and others (after all, success of statistics, particularly inferential statistics, depends on a representative sample or a close equivalent that allows researchers to approximate the real world, which is prone to errors if not done correctly such as misinterpretation, bad outliers, only some groups participating, not looking at things more deeply and what not).



One important thing to note is that Web AIM is a representative survey, thus the result in front of me could reflect reality. However, due to recent controversy, possible type I and II errors (false-positive and false-negative, respectively) and because of outliers and skewed data and participation, it does not truly reflect actual data, which is a point some folks here are trying to say and I concur with. My explication of Web AIM 7 is that, in some parts of the world, JAWS for Windows is more popular. However, given the fact that not all geographical regions are represented, I’d counter by saying that this is not a true representative sample that includes every continent, and if it did, the story would be different and will reflect reality a bit better (not a lot because there are other ways of skewing data such as filling it out on behalf of an organization, robotic fillers and so on). Coupled with the fact that Web AIM went through a major controversy recently that damaged its credibility somewhat, I would dare not trust Web AIM results again.



This leads to my second point: quantity versus quality. If NV Access went straight for quantity alone, they could have implemented all possible feature requests in hopes of boosting market share. The reality in front of us says otherwise: not all feature requests are here. Numerous factors contribute to this problem:



* Lack of leading developers: in 2017, a long-time NVDA developer started working for another organization, and NV Access has been looking for his replacement ever since. Even if the replacement is found, it’ll take several months for him or her to become used to this community, learn about accessibility and how to interact with members, and earn our trust (it took Reef Turner a year to fully earn our trust). Folks can counter this by saying that there are countless contributors out there, but ultimately what gets into NVDA depends on pull requests and review time from NV Access.
* Attitudes about open-source software from organizations: as some folks pointed out, there are prevailing attitudes about open-source in organizations that makes it a bit harder for NVDA to land on their computers, which allows developers to assess true needs of organizations through user feedback. Without valuable feedback from organizations (a quality one at that), we won’t see huger progress in NVDA development.
* Outside attitudes about the NVDA community: from the inside, NVDA community is seen as a tight nit of enthusiasts who strives to make NVDA better every day. On the outside, however, we have a mixed bag of reputations, from admiration to honorable mentions to disdain. Every organization have these mixed reputations, especially more so for a community powered by technology such as Linux kernel developers, web browser vendors and web standards organizations, and even screen reader community. Not only we need to show that we are united inside, we need to showcase unity outside of this community.
* Inside matters just as outside: public relations outside of NVDA community is important, but unity within an organization is just as important as public organizational face (I’ll address developer’s point of view below). What makes NVDA stand out is our unity despite coming from different circumstances and backgrounds.



Most of these point to quality, not quantity alone. In summary, quantity is important, but quality is just as important as how many people download NVDA 2017.4 between Christmas and New Year.



Lastly, in regards to organization internals, I’d like to address something I really wanted to say for the past few weeks: sometimes, I felt burnt out. My initial response to your enthusiasm over my audio tutorials was that I’ll ask for justifications for producing an updated version, seeing that there are countless free videos and tutorials out there. This was partly because I truly felt burnt out with academics, speech and debate competitions and what not (especially after a debate regarding a potential feature held not long ago), at one point telling myself that I’ll retire from the NVDA community sooner than later and feeling as though I carried important burdens on my shoulders. But you didn’t see that justification post; instead, I posted links to where you can download the 2018 version of my audio tutorial series. In effect, I’ve given up my Christmas holidays for this community, knowing that I needed a time to listen to you all and do something about it. All this was possible because of a simple act of listening and thinking about what the community means to me and what my work means to everyone. I’m committed to finishing Welcome to NVDA 2018 series before NVDA 2018.1 ships, with several addenda coming after that, all because of support from this community and outsiders. And I promise again: The Welcome to NVDA 2018 series was, and will remain, free for all. All I ask of you in return is donate to a cause that makes equal access to technology possible, especially during this holiday season and beyond.



I’m sure for many of you, my musings above are a bit hard to digest. Now you know why I don’t trust Web AIM survey results, quality is just as important as quantity, and read a confession from a community leader on his inner feelings. But there are two more things you need to know, something all of us needs to think about:



Community leaders won’t stay with you forever. In early 2017, I sensed that a long-time NVDA developer would leave this community for something better. Only I and others didn’t know until summer that it would be Jamie moving onto Mozilla Foundation.



I also felt, back in early 2017, that my active time with the NVDA community is slowly drawing to a close. I don’t know when it’ll happen, but I’ve been laying foundations for the next generation of developers and enthusiasts to take the lead. This is one of the reasons for setting up the devlearning subgroup, because I felt it is time for me and other leaders to teach NVDA internals and other concepts to the next group of community leaders and developers so they can bring NVDA to the next level and do more amazing things than I and others did (in my case, for the past five years).



Lastly, I sense a time when this community will face a sharp divide to a point where people will start questioning the merits of this community. I only told a select few earlier because it wasn’t right for me to disclose it early and for them to prepare a plan. The screen shade debate is, in fact, a sort of a preview of what is to come. One of the fundamental questions you will face at that time will be whether you still have your first love for NVDA, and whether you still have your original reasons for joining this community. The survival of this community at that time will depend on your ability to unite to face a difficult situation, even if that means facing possible splits. One thing you should NOT do at that time: ignoring new users and outside critics, because they are influential opinion leaders and are key stakeholders in NVDA’s future. One thing you SHOULD do though: listen to others and think critically.



Hope this makes sense.

Merry (early) Christmas,

Joseph






.


 

Yeah, and wifi and stuff.

If humanware had a trecker phone I'd buy one why not.

On 25/12/2017 11:05 p.m., Brian's Mail list account via Groups.Io wrote:
I was thinking more in the region of cost. Many of us watch costs, but if its for work in many  well off economies, the equipment and software is purchased by the state.
Think of the Braille display. A lot has been made of late of these being used by nvda and indeed mainstream gear like Apple products, but really unless the person is well off these devices are a luxury unless bought by an organisation or government.

The same can be said of all the other devices. Also if you want things to be portable, you want to have a solution that does not demand you take half a truck load of gear everywhere you go.
I had to chuckle the other day when Humanware launched their Trek, which is basically a media player, downloader and GPs in a box.
If they only added a cellular modem and a camera, they would have a phone.

Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Shaun Everiss" <sm.everiss@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, December 24, 2017 11:05 PM
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials


Well dedicated hardware while costing a bit has a few advantages.

1. bigger speakers, no added destractions etc.

The issue of all on one device is that especially with traditional headphone jacks going you can't just connect a pair of speakers anymore.

Even with that out the way, if you load your smartphone with a lot of stuff, you will still use that power.

Bluetooth, gps, and data use a lot if you are not carefull never mind that if you are not in the country you registered in the data will cost a lot so you will need to turn that off.

Unless you are on wifi and some of that can be not secured.

Even if you have extra batteries with the revelations of apple slowing devices, you will now have to add in new devices costs or batteries for that device.

Most dedicated devices at least quite a few will either have their battery which they use or if you are lucky use standard off the shelf batteries which actually don't cost that much especially if you buy that in a bundle.

I have a lot of electronics using aa and tripple aa battery types, and it costs not much to run any of them.




On 24/12/2017 10:18 p.m., Brian's Mail list account via Groups.Io wrote:
Well I'm not so sure this is the whole story. I notice that the same argument is going on on the hardware front now. IE a smart phone can do most of what a media player, OCR machine, and navigational aid did. The people are still trying to sell such hardware, and I'd imagine in certain cases, they might have a a use, ie if the user has poor feeling in their hands or a tremor etc, but for the masses, no.
As I noted before, I don't like the kind of computer access Dolphin Guide gives. Its just a suite of self voicing software. It traps you.
Than goodness people can now put nvda on such machines and then when folk like me come along to help them when windows throws a wobbly we can.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Sky Mundell" <skyt@shaw.ca>
To: <nvda@nvda.groups.io>
Sent: Sunday, December 24, 2017 3:26 AM
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials


I totally agree with you. You are absolutely right. Screen readers should certainly be a social impact. The reason there is capital invested in it is because the agencies are the ones who are funding the capital.



From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Adriani Botez
Sent: Saturday, December 23, 2017 7:08 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials



Brian,



With respect to investing money globally to make screen reader users more computer literate, well believe or not there was always a solution for that. A screen reader should imply a social movement and not a gain of capital out of selling. There are lots of development institutions, Christian Blind Mission, blind federations and lots of other non governamental organizations which support everything which gives people access to education, information and technology. But in the last 30 years, many people hoped to gain money out of selling licenses and did not really concentrate on learning the user detailed aspects on how to use that software. Thus, users became more and more change resistent because they invested lot of time to learn by themselves how to use it productively. In my opinion, we should not only think about technical aspects of a screen reader, but also about social impact and user interaction.



Best

Adriani



Von meinem iPhone gesendet


Am 24.12.2017 um 04:44 schrieb Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io>:

Certainly I do understand the burned out part of this its the same for all volunteers. if we are good at what we do we are in demand and take on more and more. it was only a comment from somebody else that made me try to bring a sense of realism to life. You cannot be a one man fixer of everything, and the cemeteries are full of people who were indispensable.

Most screenreader users are just that, users, many of us know the basics of what is going on, but really, its now so complex its beyond all but the few to grasp it all.

Obviously as we kind of slip into a world very much like we used to have in the 80s, where computers run lots of different operating systems and even windows differs in the internals between many different systems, the problems of access move from the screenreader to the platform.

that is, NVDA will probably be OK on mainstream Windows computers for some years, but with tablets, phones and various different processors and operating systems now coming in, its going to be the user who has to change and become expert in many more interfaces, as clearly, what we use in Windows today with a keyboard may not fit in any way the interface of the future.

Sadly the problem is as it always has been, training and the cost and indeed the ability of blind people particularly the older ones to actually grasp the abstract concepts and enable them to see equivalents and have a grasp of what is actually going on.

I really think that somebody needs to invest a lot more money globally in trying to get more blind people computer literate, but its just not happening, so although in theory we have access, not everyone will be able to actually use it.



Change is life after all, and people going to take other jobs is normal. the problem for nvda is that the two people who started it were visionary, and not everyone can share the vision, if you get my drift.

I don't know what is about to happen to tech, but it seems to me that nobody does. Who could have predicted this year that tablet sales have dropped but laptop and desktop sales are up. I suspect its down to novelty wearing off and nothing really new on the market just revamps of what has gone before.

Personally, my gut tells me that although cloud computing can be good in some cases, many people do not want to pitch all their eggs into somebody elses basket. Its the same reason I still buy CDs. I don't want somebody taking my access away due to whatever. The danger at the moment is that the net is going down the packet priority road as well, another legal form of highway robbery in my view.

As for surveys, yes, well I already told you my opinion of those. Almost be better to use some tracking system, like a cookie to see what is on any given machine, but many would find that intrusive even though if you own an Android device its more or less going on now.

Its all about trust and whether you can always trust others with data about you.

If it can be created it can be hacked and messed about with. Bots are all over the place after all.

If you cannot trust the metrics one gets then the data collected becomes worthless.

Anyway I'm up in the night again wibbling on. Look at it this way, it matters what happens to nvda, but in the great scheme of life, what really matters is trying to be happy while you are here on the planet. You cannot own other people like Mick or Jamie.



Its not right or fair to expect people to be some kind of God.

Been there got the TO Shirt, and the community awards etc, and for what?

I prefer now to just help if I can but not to get so het up that it makes my life owned by others.

Big mistake.

Brian


bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
This message sent from a Windows XP machine!

----- Original Message -----
From: Joseph Lee <mailto:joseph.lee22590@gmail.com>

To: nvda@nvda.groups.io

Sent: Saturday, December 23, 2017 5:25 PM

Subject: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials



Dear NVDA community,



As I read messages on recent discussions, I realized just how much enthusiasm and concern people have over NVDA and its future. At the same time, it became clear to me that I and other developers and community elders need a day off and just listen to you all, as listening allows us to think about what others are saying and plan things accordingly.



But first, a humble opinion about surveys and other points:



First, when calls for the seventh Web AIM survey went out, I told people to not just do it to “increase” market share. I specifically told screen reader companies to not coerce users to do it, but let people take it out of their own willingness. This advice was to avoid a fiasco that happened with Web AIM 6 where AI Squared (now part of VFO) staff told Window-Eyes users to fill out the survey in mass numbers, which became a small controversy within the screen reading world, and to me, making Web AIM results no longer credible.



As some folks pointed out, Web AIM numbers depend on how many people fill it out and where they come from (and this is true of any surveys where word of mouth drives participation). The results also depend on demographics and other factors such as choices given, how the questions are worded, and overall objective. If one or more data points seems to be dominant, they can be either skewed or outliers, with the more extreme cases being termed “outliers” and they affect how the results are explicated (interpreted). Even skewed data, such as what I can perceive from some surveys including recent Web AIM iterations can affect statistical calculations to a point where it raises genuine questions about bias, credibility, and others (after all, success of statistics, particularly inferential statistics, depends on a representative sample or a close equivalent that allows researchers to approximate the real world, which is prone to errors if not done correctly such as misinterpretation, bad outliers, only some groups participating, not looking at things more deeply and what not).



One important thing to note is that Web AIM is a representative survey, thus the result in front of me could reflect reality. However, due to recent controversy, possible type I and II errors (false-positive and false-negative, respectively) and because of outliers and skewed data and participation, it does not truly reflect actual data, which is a point some folks here are trying to say and I concur with. My explication of Web AIM 7 is that, in some parts of the world, JAWS for Windows is more popular. However, given the fact that not all geographical regions are represented, I’d counter by saying that this is not a true representative sample that includes every continent, and if it did, the story would be different and will reflect reality a bit better (not a lot because there are other ways of skewing data such as filling it out on behalf of an organization, robotic fillers and so on). Coupled with the fact that Web AIM went through a major controversy recently that damaged its credibility somewhat, I would dare not trust Web AIM results again.



This leads to my second point: quantity versus quality. If NV Access went straight for quantity alone, they could have implemented all possible feature requests in hopes of boosting market share. The reality in front of us says otherwise: not all feature requests are here. Numerous factors contribute to this problem:



* Lack of leading developers: in 2017, a long-time NVDA developer started working for another organization, and NV Access has been looking for his replacement ever since. Even if the replacement is found, it’ll take several months for him or her to become used to this community, learn about accessibility and how to interact with members, and earn our trust (it took Reef Turner a year to fully earn our trust). Folks can counter this by saying that there are countless contributors out there, but ultimately what gets into NVDA depends on pull requests and review time from NV Access.
* Attitudes about open-source software from organizations: as some folks pointed out, there are prevailing attitudes about open-source in organizations that makes it a bit harder for NVDA to land on their computers, which allows developers to assess true needs of organizations through user feedback. Without valuable feedback from organizations (a quality one at that), we won’t see huger progress in NVDA development.
* Outside attitudes about the NVDA community: from the inside, NVDA community is seen as a tight nit of enthusiasts who strives to make NVDA better every day. On the outside, however, we have a mixed bag of reputations, from admiration to honorable mentions to disdain. Every organization have these mixed reputations, especially more so for a community powered by technology such as Linux kernel developers, web browser vendors and web standards organizations, and even screen reader community. Not only we need to show that we are united inside, we need to showcase unity outside of this community.
* Inside matters just as outside: public relations outside of NVDA community is important, but unity within an organization is just as important as public organizational face (I’ll address developer’s point of view below). What makes NVDA stand out is our unity despite coming from different circumstances and backgrounds.



Most of these point to quality, not quantity alone. In summary, quantity is important, but quality is just as important as how many people download NVDA 2017.4 between Christmas and New Year.



Lastly, in regards to organization internals, I’d like to address something I really wanted to say for the past few weeks: sometimes, I felt burnt out. My initial response to your enthusiasm over my audio tutorials was that I’ll ask for justifications for producing an updated version, seeing that there are countless free videos and tutorials out there. This was partly because I truly felt burnt out with academics, speech and debate competitions and what not (especially after a debate regarding a potential feature held not long ago), at one point telling myself that I’ll retire from the NVDA community sooner than later and feeling as though I carried important burdens on my shoulders. But you didn’t see that justification post; instead, I posted links to where you can download the 2018 version of my audio tutorial series. In effect, I’ve given up my Christmas holidays for this community, knowing that I needed a time to listen to you all and do something about it. All this was possible because of a simple act of listening and thinking about what the community means to me and what my work means to everyone. I’m committed to finishing Welcome to NVDA 2018 series before NVDA 2018.1 ships, with several addenda coming after that, all because of support from this community and outsiders. And I promise again: The Welcome to NVDA 2018 series was, and will remain, free for all. All I ask of you in return is donate to a cause that makes equal access to technology possible, especially during this holiday season and beyond.



I’m sure for many of you, my musings above are a bit hard to digest. Now you know why I don’t trust Web AIM survey results, quality is just as important as quantity, and read a confession from a community leader on his inner feelings. But there are two more things you need to know, something all of us needs to think about:



Community leaders won’t stay with you forever. In early 2017, I sensed that a long-time NVDA developer would leave this community for something better. Only I and others didn’t know until summer that it would be Jamie moving onto Mozilla Foundation.



I also felt, back in early 2017, that my active time with the NVDA community is slowly drawing to a close. I don’t know when it’ll happen, but I’ve been laying foundations for the next generation of developers and enthusiasts to take the lead. This is one of the reasons for setting up the devlearning subgroup, because I felt it is time for me and other leaders to teach NVDA internals and other concepts to the next group of community leaders and developers so they can bring NVDA to the next level and do more amazing things than I and others did (in my case, for the past five years).



Lastly, I sense a time when this community will face a sharp divide to a point where people will start questioning the merits of this community. I only told a select few earlier because it wasn’t right for me to disclose it early and for them to prepare a plan. The screen shade debate is, in fact, a sort of a preview of what is to come. One of the fundamental questions you will face at that time will be whether you still have your first love for NVDA, and whether you still have your original reasons for joining this community. The survival of this community at that time will depend on your ability to unite to face a difficult situation, even if that means facing possible splits. One thing you should NOT do at that time: ignoring new users and outside critics, because they are influential opinion leaders and are key stakeholders in NVDA’s future. One thing you SHOULD do though: listen to others and think critically.



Hope this makes sense.

Merry (early) Christmas,

Joseph






.





Brian's Mail list account <bglists@...>
 

It would probably cost more than an I phone 10.
The one that shatters if you drop it. Next version includes retro rockets obviously! grin.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Shaun Everiss" <sm.everiss@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, December 25, 2017 6:00 PM
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials


Yeah, and wifi and stuff.

If humanware had a trecker phone I'd buy one why not.




On 25/12/2017 11:05 p.m., Brian's Mail list account via Groups.Io wrote:
I was thinking more in the region of cost. Many of us watch costs, but if its for work in many well off economies, the equipment and software is purchased by the state.
Think of the Braille display. A lot has been made of late of these being used by nvda and indeed mainstream gear like Apple products, but really unless the person is well off these devices are a luxury unless bought by an organisation or government.

The same can be said of all the other devices. Also if you want things to be portable, you want to have a solution that does not demand you take half a truck load of gear everywhere you go.
I had to chuckle the other day when Humanware launched their Trek, which is basically a media player, downloader and GPs in a box.
If they only added a cellular modem and a camera, they would have a phone.

Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Shaun Everiss" <sm.everiss@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, December 24, 2017 11:05 PM
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials


Well dedicated hardware while costing a bit has a few advantages.

1. bigger speakers, no added destractions etc.

The issue of all on one device is that especially with traditional headphone jacks going you can't just connect a pair of speakers anymore.

Even with that out the way, if you load your smartphone with a lot of stuff, you will still use that power.

Bluetooth, gps, and data use a lot if you are not carefull never mind that if you are not in the country you registered in the data will cost a lot so you will need to turn that off.

Unless you are on wifi and some of that can be not secured.

Even if you have extra batteries with the revelations of apple slowing devices, you will now have to add in new devices costs or batteries for that device.

Most dedicated devices at least quite a few will either have their battery which they use or if you are lucky use standard off the shelf batteries which actually don't cost that much especially if you buy that in a bundle.

I have a lot of electronics using aa and tripple aa battery types, and it costs not much to run any of them.




On 24/12/2017 10:18 p.m., Brian's Mail list account via Groups.Io wrote:
Well I'm not so sure this is the whole story. I notice that the same argument is going on on the hardware front now. IE a smart phone can do most of what a media player, OCR machine, and navigational aid did. The people are still trying to sell such hardware, and I'd imagine in certain cases, they might have a a use, ie if the user has poor feeling in their hands or a tremor etc, but for the masses, no.
As I noted before, I don't like the kind of computer access Dolphin Guide gives. Its just a suite of self voicing software. It traps you.
Than goodness people can now put nvda on such machines and then when folk like me come along to help them when windows throws a wobbly we can.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Sky Mundell" <skyt@shaw.ca>
To: <nvda@nvda.groups.io>
Sent: Sunday, December 24, 2017 3:26 AM
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials


I totally agree with you. You are absolutely right. Screen readers should certainly be a social impact. The reason there is capital invested in it is because the agencies are the ones who are funding the capital.



From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Adriani Botez
Sent: Saturday, December 23, 2017 7:08 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials



Brian,



With respect to investing money globally to make screen reader users more computer literate, well believe or not there was always a solution for that. A screen reader should imply a social movement and not a gain of capital out of selling. There are lots of development institutions, Christian Blind Mission, blind federations and lots of other non governamental organizations which support everything which gives people access to education, information and technology. But in the last 30 years, many people hoped to gain money out of selling licenses and did not really concentrate on learning the user detailed aspects on how to use that software. Thus, users became more and more change resistent because they invested lot of time to learn by themselves how to use it productively. In my opinion, we should not only think about technical aspects of a screen reader, but also about social impact and user interaction.



Best

Adriani



Von meinem iPhone gesendet


Am 24.12.2017 um 04:44 schrieb Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io>:

Certainly I do understand the burned out part of this its the same for all volunteers. if we are good at what we do we are in demand and take on more and more. it was only a comment from somebody else that made me try to bring a sense of realism to life. You cannot be a one man fixer of everything, and the cemeteries are full of people who were indispensable.

Most screenreader users are just that, users, many of us know the basics of what is going on, but really, its now so complex its beyond all but the few to grasp it all.

Obviously as we kind of slip into a world very much like we used to have in the 80s, where computers run lots of different operating systems and even windows differs in the internals between many different systems, the problems of access move from the screenreader to the platform.

that is, NVDA will probably be OK on mainstream Windows computers for some years, but with tablets, phones and various different processors and operating systems now coming in, its going to be the user who has to change and become expert in many more interfaces, as clearly, what we use in Windows today with a keyboard may not fit in any way the interface of the future.

Sadly the problem is as it always has been, training and the cost and indeed the ability of blind people particularly the older ones to actually grasp the abstract concepts and enable them to see equivalents and have a grasp of what is actually going on.

I really think that somebody needs to invest a lot more money globally in trying to get more blind people computer literate, but its just not happening, so although in theory we have access, not everyone will be able to actually use it.



Change is life after all, and people going to take other jobs is normal. the problem for nvda is that the two people who started it were visionary, and not everyone can share the vision, if you get my drift.

I don't know what is about to happen to tech, but it seems to me that nobody does. Who could have predicted this year that tablet sales have dropped but laptop and desktop sales are up. I suspect its down to novelty wearing off and nothing really new on the market just revamps of what has gone before.

Personally, my gut tells me that although cloud computing can be good in some cases, many people do not want to pitch all their eggs into somebody elses basket. Its the same reason I still buy CDs. I don't want somebody taking my access away due to whatever. The danger at the moment is that the net is going down the packet priority road as well, another legal form of highway robbery in my view.

As for surveys, yes, well I already told you my opinion of those. Almost be better to use some tracking system, like a cookie to see what is on any given machine, but many would find that intrusive even though if you own an Android device its more or less going on now.

Its all about trust and whether you can always trust others with data about you.

If it can be created it can be hacked and messed about with. Bots are all over the place after all.

If you cannot trust the metrics one gets then the data collected becomes worthless.

Anyway I'm up in the night again wibbling on. Look at it this way, it matters what happens to nvda, but in the great scheme of life, what really matters is trying to be happy while you are here on the planet. You cannot own other people like Mick or Jamie.



Its not right or fair to expect people to be some kind of God.

Been there got the TO Shirt, and the community awards etc, and for what?

I prefer now to just help if I can but not to get so het up that it makes my life owned by others.

Big mistake.

Brian


bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
This message sent from a Windows XP machine!

----- Original Message -----
From: Joseph Lee <mailto:joseph.lee22590@gmail.com>

To: nvda@nvda.groups.io

Sent: Saturday, December 23, 2017 5:25 PM

Subject: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials



Dear NVDA community,



As I read messages on recent discussions, I realized just how much enthusiasm and concern people have over NVDA and its future. At the same time, it became clear to me that I and other developers and community elders need a day off and just listen to you all, as listening allows us to think about what others are saying and plan things accordingly.



But first, a humble opinion about surveys and other points:



First, when calls for the seventh Web AIM survey went out, I told people to not just do it to “increase” market share. I specifically told screen reader companies to not coerce users to do it, but let people take it out of their own willingness. This advice was to avoid a fiasco that happened with Web AIM 6 where AI Squared (now part of VFO) staff told Window-Eyes users to fill out the survey in mass numbers, which became a small controversy within the screen reading world, and to me, making Web AIM results no longer credible.



As some folks pointed out, Web AIM numbers depend on how many people fill it out and where they come from (and this is true of any surveys where word of mouth drives participation). The results also depend on demographics and other factors such as choices given, how the questions are worded, and overall objective. If one or more data points seems to be dominant, they can be either skewed or outliers, with the more extreme cases being termed “outliers” and they affect how the results are explicated (interpreted). Even skewed data, such as what I can perceive from some surveys including recent Web AIM iterations can affect statistical calculations to a point where it raises genuine questions about bias, credibility, and others (after all, success of statistics, particularly inferential statistics, depends on a representative sample or a close equivalent that allows researchers to approximate the real world, which is prone to errors if not done correctly such as misinterpretation, bad outliers, only some groups participating, not looking at things more deeply and what not).



One important thing to note is that Web AIM is a representative survey, thus the result in front of me could reflect reality. However, due to recent controversy, possible type I and II errors (false-positive and false-negative, respectively) and because of outliers and skewed data and participation, it does not truly reflect actual data, which is a point some folks here are trying to say and I concur with. My explication of Web AIM 7 is that, in some parts of the world, JAWS for Windows is more popular. However, given the fact that not all geographical regions are represented, I’d counter by saying that this is not a true representative sample that includes every continent, and if it did, the story would be different and will reflect reality a bit better (not a lot because there are other ways of skewing data such as filling it out on behalf of an organization, robotic fillers and so on). Coupled with the fact that Web AIM went through a major controversy recently that damaged its credibility somewhat, I would dare not trust Web AIM results again.



This leads to my second point: quantity versus quality. If NV Access went straight for quantity alone, they could have implemented all possible feature requests in hopes of boosting market share. The reality in front of us says otherwise: not all feature requests are here. Numerous factors contribute to this problem:



* Lack of leading developers: in 2017, a long-time NVDA developer started working for another organization, and NV Access has been looking for his replacement ever since. Even if the replacement is found, it’ll take several months for him or her to become used to this community, learn about accessibility and how to interact with members, and earn our trust (it took Reef Turner a year to fully earn our trust). Folks can counter this by saying that there are countless contributors out there, but ultimately what gets into NVDA depends on pull requests and review time from NV Access.
* Attitudes about open-source software from organizations: as some folks pointed out, there are prevailing attitudes about open-source in organizations that makes it a bit harder for NVDA to land on their computers, which allows developers to assess true needs of organizations through user feedback. Without valuable feedback from organizations (a quality one at that), we won’t see huger progress in NVDA development.
* Outside attitudes about the NVDA community: from the inside, NVDA community is seen as a tight nit of enthusiasts who strives to make NVDA better every day. On the outside, however, we have a mixed bag of reputations, from admiration to honorable mentions to disdain. Every organization have these mixed reputations, especially more so for a community powered by technology such as Linux kernel developers, web browser vendors and web standards organizations, and even screen reader community. Not only we need to show that we are united inside, we need to showcase unity outside of this community.
* Inside matters just as outside: public relations outside of NVDA community is important, but unity within an organization is just as important as public organizational face (I’ll address developer’s point of view below). What makes NVDA stand out is our unity despite coming from different circumstances and backgrounds.



Most of these point to quality, not quantity alone. In summary, quantity is important, but quality is just as important as how many people download NVDA 2017.4 between Christmas and New Year.



Lastly, in regards to organization internals, I’d like to address something I really wanted to say for the past few weeks: sometimes, I felt burnt out. My initial response to your enthusiasm over my audio tutorials was that I’ll ask for justifications for producing an updated version, seeing that there are countless free videos and tutorials out there. This was partly because I truly felt burnt out with academics, speech and debate competitions and what not (especially after a debate regarding a potential feature held not long ago), at one point telling myself that I’ll retire from the NVDA community sooner than later and feeling as though I carried important burdens on my shoulders. But you didn’t see that justification post; instead, I posted links to where you can download the 2018 version of my audio tutorial series. In effect, I’ve given up my Christmas holidays for this community, knowing that I needed a time to listen to you all and do something about it. All this was possible because of a simple act of listening and thinking about what the community means to me and what my work means to everyone. I’m committed to finishing Welcome to NVDA 2018 series before NVDA 2018.1 ships, with several addenda coming after that, all because of support from this community and outsiders. And I promise again: The Welcome to NVDA 2018 series was, and will remain, free for all. All I ask of you in return is donate to a cause that makes equal access to technology possible, especially during this holiday season and beyond.



I’m sure for many of you, my musings above are a bit hard to digest. Now you know why I don’t trust Web AIM survey results, quality is just as important as quantity, and read a confession from a community leader on his inner feelings. But there are two more things you need to know, something all of us needs to think about:



Community leaders won’t stay with you forever. In early 2017, I sensed that a long-time NVDA developer would leave this community for something better. Only I and others didn’t know until summer that it would be Jamie moving onto Mozilla Foundation.



I also felt, back in early 2017, that my active time with the NVDA community is slowly drawing to a close. I don’t know when it’ll happen, but I’ve been laying foundations for the next generation of developers and enthusiasts to take the lead. This is one of the reasons for setting up the devlearning subgroup, because I felt it is time for me and other leaders to teach NVDA internals and other concepts to the next group of community leaders and developers so they can bring NVDA to the next level and do more amazing things than I and others did (in my case, for the past five years).



Lastly, I sense a time when this community will face a sharp divide to a point where people will start questioning the merits of this community. I only told a select few earlier because it wasn’t right for me to disclose it early and for them to prepare a plan. The screen shade debate is, in fact, a sort of a preview of what is to come. One of the fundamental questions you will face at that time will be whether you still have your first love for NVDA, and whether you still have your original reasons for joining this community. The survival of this community at that time will depend on your ability to unite to face a difficult situation, even if that means facing possible splits. One thing you should NOT do at that time: ignoring new users and outside critics, because they are influential opinion leaders and are key stakeholders in NVDA’s future. One thing you SHOULD do though: listen to others and think critically.



Hope this makes sense.

Merry (early) Christmas,

Joseph






.






Mário Navarro
 


absolutely right.

thank you good friend.


long life to Joseph Lee.

cheers.



Às 17:25 de 23/12/2017, Joseph Lee escreveu:

Dear NVDA community,

 

As I read messages on recent discussions, I realized just how much enthusiasm and concern people have over NVDA and its future. At the same time, it became clear to me that I and other developers and community elders need a day off and just listen to you all, as listening allows us to think about what others are saying and plan things accordingly.

 

But first, a humble opinion about surveys and other points:

 

First, when calls for the seventh Web AIM survey went out, I told people to not just do it to “increase” market share. I specifically told screen reader companies to not coerce users to do it, but let people take it out of their own willingness. This advice was to avoid a fiasco that happened with Web AIM 6 where AI Squared (now part of VFO) staff told Window-Eyes users to fill out the survey in mass numbers, which became a small controversy within the screen reading world, and to me, making Web AIM results no longer credible.

 

As some folks pointed out, Web AIM numbers depend on how many people fill it out and where they come from (and this is true of any surveys where word of mouth drives participation). The results also depend on demographics and other factors such as choices given, how the questions are worded, and overall objective. If one or more data points seems to be dominant, they can be either skewed or outliers, with the more extreme cases being termed “outliers” and they affect how the results are explicated (interpreted). Even skewed data, such as what I can perceive from some surveys including recent Web AIM iterations can affect statistical calculations to a point where it raises genuine questions about bias, credibility, and others (after all, success of statistics, particularly inferential statistics, depends on a representative sample or a close equivalent that allows researchers to approximate the real world, which is prone to errors if not done correctly such as misinterpretation, bad outliers, only some groups participating, not looking at things more deeply and what not).

 

One important thing to note is that Web AIM is a representative survey, thus the result in front of me could reflect reality. However, due to recent controversy, possible type I and II errors (false-positive and false-negative, respectively) and because of outliers and skewed data and participation, it does not truly reflect actual data, which is a point some folks here are trying to say and I concur with. My explication of Web AIM 7 is that, in some parts of the world, JAWS for Windows is more popular. However, given the fact that not all geographical regions are represented, I’d counter by saying that this is not a true representative sample that includes every continent, and if it did, the story would be different and will reflect reality a bit better (not a lot because there are other ways of skewing data such as filling it out on behalf of an organization, robotic fillers and so on). Coupled with the fact that Web AIM went through a major controversy recently that damaged its credibility somewhat, I would dare not trust Web AIM results again.

 

This leads to my second point: quantity versus quality. If NV Access went straight for quantity alone, they could have implemented all possible feature requests in hopes of boosting market share. The reality in front of us says otherwise: not all feature requests are here. Numerous factors contribute to this problem:

 

  • Lack of leading developers: in 2017, a long-time NVDA developer started working for another organization, and NV Access has been looking for his replacement ever since. Even if the replacement is found, it’ll take several months for him or her to become used to this community, learn about accessibility and how to interact with members, and earn our trust (it took Reef Turner a year to fully earn our trust). Folks can counter this by saying that there are countless contributors out there, but ultimately what gets into NVDA depends on pull requests and review time from NV Access.
  • Attitudes about open-source software from organizations: as some folks pointed out, there are prevailing attitudes about open-source in organizations that makes it a bit harder for NVDA to land on their computers, which allows developers to assess true needs of organizations through user feedback. Without valuable feedback from organizations (a quality one at that), we won’t see huger progress in NVDA development.
  • Outside attitudes about the NVDA community: from the inside, NVDA community is seen as a tight nit of enthusiasts who strives to make NVDA better every day. On the outside, however, we have a mixed bag of reputations, from admiration to honorable mentions to disdain. Every organization have these mixed reputations, especially more so for a community powered by technology such as Linux kernel developers, web browser vendors and web standards organizations, and even screen reader community. Not only we need to show that we are united inside, we need to showcase unity outside of this community.
  • Inside matters just as outside: public relations outside of NVDA community is important, but unity within an organization is just as important as public organizational face (I’ll address developer’s point of view below). What makes NVDA stand out is our unity despite coming from different circumstances and backgrounds.

 

Most of these point to quality, not quantity alone. In summary, quantity is important, but quality is just as important as how many people download NVDA 2017.4 between Christmas and New Year.

 

Lastly, in regards to organization internals, I’d like to address something I really wanted to say for the past few weeks: sometimes, I felt burnt out. My initial response to your enthusiasm over my audio tutorials was that I’ll ask for justifications for producing an updated version, seeing that there are countless free videos and tutorials out there. This was partly because I truly felt burnt out with academics, speech and debate competitions and what not (especially after a debate regarding a potential feature held not long ago), at one point telling myself that I’ll retire from the NVDA community sooner than later and feeling as though I carried important burdens on my shoulders. But you didn’t see that justification post; instead, I posted links to where you can download the 2018 version of my audio tutorial series. In effect, I’ve given up my Christmas holidays for this community, knowing that I needed a time to listen to you all and do something about it. All this was possible because of a simple act of listening and thinking about what the community means to me and what my work means to everyone. I’m committed to finishing Welcome to NVDA 2018 series before NVDA 2018.1 ships, with several addenda coming after that, all because of support from this community and outsiders. And I promise again: The Welcome to NVDA 2018 series was, and will remain, free for all. All I ask of you in return is donate to a cause that makes equal access to technology possible, especially during this holiday season and beyond.

 

I’m sure for many of you, my musings above are a bit hard to digest. Now you know why I don’t trust Web AIM survey results, quality is just as important as quantity, and read a confession from a community leader on his inner feelings. But there are two more things you need to know, something all of us needs to think about:

 

Community leaders won’t stay with you forever. In early 2017, I sensed that a long-time NVDA developer would leave this community for something better. Only I and others didn’t know until summer that it would be Jamie moving onto Mozilla Foundation.

 

I also felt, back in early 2017, that my active time with the NVDA community is slowly drawing to a close. I don’t know when it’ll happen, but I’ve been laying foundations for the next generation of developers and enthusiasts to take the lead. This is one of the reasons for setting up the devlearning subgroup, because I felt it is time for me and other leaders to teach NVDA internals and other concepts to the next group of community leaders and developers so they can bring NVDA to the next level and do more amazing things than I and others did (in my case, for the past five years).

 

Lastly, I sense a time when this community will face a sharp divide to a point where people will start questioning the merits of this community. I only told a select few earlier because it wasn’t right for me to disclose it early and for them to prepare a plan. The screen shade debate is, in fact, a sort of a preview of what is to come. One of the fundamental questions you will face at that time will be whether you still have your first love for NVDA, and whether you still have your original reasons for joining this community. The survival of this community at that time will depend on your ability to unite to face a difficult situation, even if that means facing possible splits. One thing you should NOT do at that time: ignoring new users and outside critics, because they are influential opinion leaders and are key stakeholders in NVDA’s future. One thing you SHOULD do though: listen to others and think critically.

 

Hope this makes sense.

Merry (early) Christmas,

Joseph


-- 
A acção pode nem sempre ser felicidade, mas não há felicidade sem acção...


Brian's Mail list account <bglists@...>
 

Yeah well I'm surveyed and consultation out. it seems these days there are such consultations done all over the place about everything from babies nappies to screenreaders and I've yet to see any of them bear any fruit in the way things are done because I feel that everything these days is driven by vested interests and cost.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Mário Navarro" <mario.gnv@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, January 24, 2018 3:50 PM
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality, feeling burnt out and tutorials



absolutely right.

thank you good friend.


long life to Joseph Lee.

cheers.



Às 17:25 de 23/12/2017, Joseph Lee escreveu:

Dear NVDA community,

As I read messages on recent discussions, I realized just how much
enthusiasm and concern people have over NVDA and its future. At the
same time, it became clear to me that I and other developers and
community elders need a day off and just listen to you all, as
listening allows us to think about what others are saying and plan
things accordingly.

But first, a humble opinion about surveys and other points:

First, when calls for the seventh Web AIM survey went out, I told
people to not just do it to “increase” market share. I specifically
told screen reader companies to not coerce users to do it, but let
people take it out of their own willingness. This advice was to avoid
a fiasco that happened with Web AIM 6 where AI Squared (now part of
VFO) staff told Window-Eyes users to fill out the survey in mass
numbers, which became a small controversy within the screen reading
world, and to me, making Web AIM results no longer credible.

As some folks pointed out, Web AIM numbers depend on how many people
fill it out and where they come from (and this is true of any surveys
where word of mouth drives participation). The results also depend on
demographics and other factors such as choices given, how the
questions are worded, and overall objective. If one or more data
points seems to be dominant, they can be either skewed or outliers,
with the more extreme cases being termed “outliers” and they affect
how the results are explicated (interpreted). Even skewed data, such
as what I can perceive from some surveys including recent Web AIM
iterations can affect statistical calculations to a point where it
raises genuine questions about bias, credibility, and others (after
all, success of statistics, particularly inferential statistics,
depends on a representative sample or a close equivalent that allows
researchers to approximate the real world, which is prone to errors if
not done correctly such as misinterpretation, bad outliers, only some
groups participating, not looking at things more deeply and what not).

One important thing to note is that Web AIM is a representative
survey, thus the result in front of me could reflect reality. However,
due to recent controversy, possible type I and II errors
(false-positive and false-negative, respectively) and because of
outliers and skewed data and participation, it does not truly reflect
actual data, which is a point some folks here are trying to say and I
concur with. My explication of Web AIM 7 is that, in some parts of the
world, JAWS for Windows is more popular. However, given the fact that
not all geographical regions are represented, I’d counter by saying
that this is not a true representative sample that includes every
continent, and if it did, the story would be different and will
reflect reality a bit better (not a lot because there are other ways
of skewing data such as filling it out on behalf of an organization,
robotic fillers and so on). Coupled with the fact that Web AIM went
through a major controversy recently that damaged its credibility
somewhat, I would dare not trust Web AIM results again.

This leads to my second point: quantity versus quality. If NV Access
went straight for quantity alone, they could have implemented all
possible feature requests in hopes of boosting market share. The
reality in front of us says otherwise: not all feature requests are
here. Numerous factors contribute to this problem:

* Lack of leading developers: in 2017, a long-time NVDA developer
started working for another organization, and NV Access has been
looking for his replacement ever since. Even if the replacement is
found, it’ll take several months for him or her to become used to
this community, learn about accessibility and how to interact with
members, and earn our trust (it took Reef Turner a year to fully
earn our trust). Folks can counter this by saying that there are
countless contributors out there, but ultimately what gets into
NVDA depends on pull requests and review time from NV Access.
* Attitudes about open-source software from organizations: as some
folks pointed out, there are prevailing attitudes about
open-source in organizations that makes it a bit harder for NVDA
to land on their computers, which allows developers to assess true
needs of organizations through user feedback. Without valuable
feedback from organizations (a quality one at that), we won’t see
huger progress in NVDA development.
* Outside attitudes about the NVDA community: from the inside, NVDA
community is seen as a tight nit of enthusiasts who strives to
make NVDA better every day. On the outside, however, we have a
mixed bag of reputations, from admiration to honorable mentions to
disdain. Every organization have these mixed reputations,
especially more so for a community powered by technology such as
Linux kernel developers, web browser vendors and web standards
organizations, and even screen reader community. Not only we need
to show that we are united inside, we need to showcase unity
outside of this community.
* Inside matters just as outside: public relations outside of NVDA
community is important, but unity within an organization is just
as important as public organizational face (I’ll address
developer’s point of view below). What makes NVDA stand out is our
unity despite coming from different circumstances and backgrounds.

Most of these point to quality, not quantity alone. In summary,
quantity is important, but quality is just as important as how many
people download NVDA 2017.4 between Christmas and New Year.

Lastly, in regards to organization internals, I’d like to address
something I really wanted to say for the past few weeks: sometimes, I
felt burnt out. My initial response to your enthusiasm over my audio
tutorials was that I’ll ask for justifications for producing an
updated version, seeing that there are countless free videos and
tutorials out there. This was partly because I truly felt burnt out
with academics, speech and debate competitions and what not
(especially after a debate regarding a potential feature held not long
ago), at one point telling myself that I’ll retire from the NVDA
community sooner than later and feeling as though I carried important
burdens on my shoulders. But you didn’t see that justification post;
instead, I posted links to where you can download the 2018 version of
my audio tutorial series. In effect, I’ve given up my Christmas
holidays for this community, knowing that I needed a time to listen to
you all and do something about it. All this was possible because of a
simple act of listening and thinking about what the community means to
me and what my work means to everyone. I’m committed to finishing
Welcome to NVDA 2018 series before NVDA 2018.1 ships, with several
addenda coming after that, all because of support from this community
and outsiders. And I promise again: The Welcome to NVDA 2018 series
was, and will remain, free for all. All I ask of you in return is
donate to a cause that makes equal access to technology possible,
especially during this holiday season and beyond.

I’m sure for many of you, my musings above are a bit hard to digest.
Now you know why I don’t trust Web AIM survey results, quality is just
as important as quantity, and read a confession from a community
leader on his inner feelings. But there are two more things you need
to know, something all of us needs to think about:

Community leaders won’t stay with you forever. In early 2017, I sensed
that a long-time NVDA developer would leave this community for
something better. Only I and others didn’t know until summer that it
would be Jamie moving onto Mozilla Foundation.

I also felt, back in early 2017, that my active time with the NVDA
community is slowly drawing to a close. I don’t know when it’ll
happen, but I’ve been laying foundations for the next generation of
developers and enthusiasts to take the lead. This is one of the
reasons for setting up the devlearning subgroup, because I felt it is
time for me and other leaders to teach NVDA internals and other
concepts to the next group of community leaders and developers so they
can bring NVDA to the next level and do more amazing things than I and
others did (in my case, for the past five years).

Lastly, I sense a time when this community will face a sharp divide to
a point where people will start questioning the merits of this
community. I only told a select few earlier because it wasn’t right
for me to disclose it early and for them to prepare a plan. The screen
shade debate is, in fact, a sort of a preview of what is to come. One
of the fundamental questions you will face at that time will be
whether you still have your first love for NVDA, and whether you still
have your original reasons for joining this community. The survival of
this community at that time will depend on your ability to unite to
face a difficult situation, even if that means facing possible splits.
One thing you should NOT do at that time: ignoring new users and
outside critics, because they are influential opinion leaders and are
key stakeholders in NVDA’s future. One thing you SHOULD do though:
listen to others and think critically.

Hope this makes sense.

Merry (early) Christmas,

Joseph

--
A acção pode nem sempre ser felicidade, mas não há felicidade sem acção...


 

hi joseph and all.
i pray and wish for unity of our comunity.
i admire opensource and helpful programs like nvda, always remember
your kindness and never forget praying for all of you sincerely!

On 1/24/18, Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:
Yeah well I'm surveyed and consultation out. it seems these days there are

such consultations done all over the place about everything from babies
nappies to screenreaders and I've yet to see any of them bear any fruit in
the way things are done because I feel that everything these days is driven

by vested interests and cost.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Mário Navarro" <mario.gnv@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, January 24, 2018 3:50 PM
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality,

feeling burnt out and tutorials



absolutely right.

thank you good friend.


long life to Joseph Lee.

cheers.



Às 17:25 de 23/12/2017, Joseph Lee escreveu:

Dear NVDA community,

As I read messages on recent discussions, I realized just how much
enthusiasm and concern people have over NVDA and its future. At the
same time, it became clear to me that I and other developers and
community elders need a day off and just listen to you all, as
listening allows us to think about what others are saying and plan
things accordingly.

But first, a humble opinion about surveys and other points:

First, when calls for the seventh Web AIM survey went out, I told
people to not just do it to “increase” market share. I specifically
told screen reader companies to not coerce users to do it, but let
people take it out of their own willingness. This advice was to avoid
a fiasco that happened with Web AIM 6 where AI Squared (now part of
VFO) staff told Window-Eyes users to fill out the survey in mass
numbers, which became a small controversy within the screen reading
world, and to me, making Web AIM results no longer credible.

As some folks pointed out, Web AIM numbers depend on how many people
fill it out and where they come from (and this is true of any surveys
where word of mouth drives participation). The results also depend on
demographics and other factors such as choices given, how the
questions are worded, and overall objective. If one or more data
points seems to be dominant, they can be either skewed or outliers,
with the more extreme cases being termed “outliers” and they affect
how the results are explicated (interpreted). Even skewed data, such
as what I can perceive from some surveys including recent Web AIM
iterations can affect statistical calculations to a point where it
raises genuine questions about bias, credibility, and others (after
all, success of statistics, particularly inferential statistics,
depends on a representative sample or a close equivalent that allows
researchers to approximate the real world, which is prone to errors if
not done correctly such as misinterpretation, bad outliers, only some
groups participating, not looking at things more deeply and what not).

One important thing to note is that Web AIM is a representative
survey, thus the result in front of me could reflect reality. However,
due to recent controversy, possible type I and II errors
(false-positive and false-negative, respectively) and because of
outliers and skewed data and participation, it does not truly reflect
actual data, which is a point some folks here are trying to say and I
concur with. My explication of Web AIM 7 is that, in some parts of the
world, JAWS for Windows is more popular. However, given the fact that
not all geographical regions are represented, I’d counter by saying
that this is not a true representative sample that includes every
continent, and if it did, the story would be different and will
reflect reality a bit better (not a lot because there are other ways
of skewing data such as filling it out on behalf of an organization,
robotic fillers and so on). Coupled with the fact that Web AIM went
through a major controversy recently that damaged its credibility
somewhat, I would dare not trust Web AIM results again.

This leads to my second point: quantity versus quality. If NV Access
went straight for quantity alone, they could have implemented all
possible feature requests in hopes of boosting market share. The
reality in front of us says otherwise: not all feature requests are
here. Numerous factors contribute to this problem:

* Lack of leading developers: in 2017, a long-time NVDA developer
started working for another organization, and NV Access has been
looking for his replacement ever since. Even if the replacement is
found, it’ll take several months for him or her to become used to
this community, learn about accessibility and how to interact with
members, and earn our trust (it took Reef Turner a year to fully
earn our trust). Folks can counter this by saying that there are
countless contributors out there, but ultimately what gets into
NVDA depends on pull requests and review time from NV Access.
* Attitudes about open-source software from organizations: as some
folks pointed out, there are prevailing attitudes about
open-source in organizations that makes it a bit harder for NVDA
to land on their computers, which allows developers to assess true
needs of organizations through user feedback. Without valuable
feedback from organizations (a quality one at that), we won’t see
huger progress in NVDA development.
* Outside attitudes about the NVDA community: from the inside, NVDA
community is seen as a tight nit of enthusiasts who strives to
make NVDA better every day. On the outside, however, we have a
mixed bag of reputations, from admiration to honorable mentions to
disdain. Every organization have these mixed reputations,
especially more so for a community powered by technology such as
Linux kernel developers, web browser vendors and web standards
organizations, and even screen reader community. Not only we need
to show that we are united inside, we need to showcase unity
outside of this community.
* Inside matters just as outside: public relations outside of NVDA
community is important, but unity within an organization is just
as important as public organizational face (I’ll address
developer’s point of view below). What makes NVDA stand out is our
unity despite coming from different circumstances and backgrounds.

Most of these point to quality, not quantity alone. In summary,
quantity is important, but quality is just as important as how many
people download NVDA 2017.4 between Christmas and New Year.

Lastly, in regards to organization internals, I’d like to address
something I really wanted to say for the past few weeks: sometimes, I
felt burnt out. My initial response to your enthusiasm over my audio
tutorials was that I’ll ask for justifications for producing an
updated version, seeing that there are countless free videos and
tutorials out there. This was partly because I truly felt burnt out
with academics, speech and debate competitions and what not
(especially after a debate regarding a potential feature held not long
ago), at one point telling myself that I’ll retire from the NVDA
community sooner than later and feeling as though I carried important
burdens on my shoulders. But you didn’t see that justification post;
instead, I posted links to where you can download the 2018 version of
my audio tutorial series. In effect, I’ve given up my Christmas
holidays for this community, knowing that I needed a time to listen to
you all and do something about it. All this was possible because of a
simple act of listening and thinking about what the community means to
me and what my work means to everyone. I’m committed to finishing
Welcome to NVDA 2018 series before NVDA 2018.1 ships, with several
addenda coming after that, all because of support from this community
and outsiders. And I promise again: The Welcome to NVDA 2018 series
was, and will remain, free for all. All I ask of you in return is
donate to a cause that makes equal access to technology possible,
especially during this holiday season and beyond.

I’m sure for many of you, my musings above are a bit hard to digest.
Now you know why I don’t trust Web AIM survey results, quality is just
as important as quantity, and read a confession from a community
leader on his inner feelings. But there are two more things you need
to know, something all of us needs to think about:

Community leaders won’t stay with you forever. In early 2017, I sensed
that a long-time NVDA developer would leave this community for
something better. Only I and others didn’t know until summer that it
would be Jamie moving onto Mozilla Foundation.

I also felt, back in early 2017, that my active time with the NVDA
community is slowly drawing to a close. I don’t know when it’ll
happen, but I’ve been laying foundations for the next generation of
developers and enthusiasts to take the lead. This is one of the
reasons for setting up the devlearning subgroup, because I felt it is
time for me and other leaders to teach NVDA internals and other
concepts to the next group of community leaders and developers so they
can bring NVDA to the next level and do more amazing things than I and
others did (in my case, for the past five years).

Lastly, I sense a time when this community will face a sharp divide to
a point where people will start questioning the merits of this
community. I only told a select few earlier because it wasn’t right
for me to disclose it early and for them to prepare a plan. The screen
shade debate is, in fact, a sort of a preview of what is to come. One
of the fundamental questions you will face at that time will be
whether you still have your first love for NVDA, and whether you still
have your original reasons for joining this community. The survival of
this community at that time will depend on your ability to unite to
face a difficult situation, even if that means facing possible splits.
One thing you should NOT do at that time: ignoring new users and
outside critics, because they are influential opinion leaders and are
key stakeholders in NVDA’s future. One thing you SHOULD do though:
listen to others and think critically.

Hope this makes sense.

Merry (early) Christmas,

Joseph

--
A acção pode nem sempre ser felicidade, mas não há felicidade sem
acção...





--
we have not sent you but as a mercy to the entire creation.
holy quran, chapter 21, verse 107.
in the very authentic narration from prophet Mohammad is:
indeed, imam husayn is the beacon of guidance and the ark of salvation.
best website for studying islamic book in different languages
www.al-islam.org


 

Well I always fill out serveys and to some extent petitions because they make me feel I am doing my bit, weather they do actually mean anything is another matter.

But that is a point.

If company x ie I don't know, say me who makes so called accessible software, which could be substandard, insecure and something, makes my users just fill out the servey, or even worse, sends a pile of bots to do a ddos and basically hijack the servey to suit me so it looks crapreader for crap os evn though its full of ransomware, is actually secure, and trustwerthy and this means I get people to download my system for my own benifit is a problem.

We must therefor assume that a lot of these places serveys etc don't have security checks.

We all know about vfo and its issues, but if all they need to do is jack up servey results they can continue making the same old software for the same price and no one will be the wizer.

I fill out serveys and online petitions to make me feel like I am doing something and while in the back of my mind I know its probably just being hijacked by those that want results or at worse a scam to harvest my email I still do it.

However knowing that companies actually do this actually is now a concern.

How can we trust any accessibility studdies or serveys.

The only way to do this fairly is simply have any organisations including schools and governments as well as employees etc in those pluss companies, even down to devs from this list and nv access not do them, and just indevidual users even so, thats not full proof.

The catch 22 here is if serveys are not trustable anymore people will not do them, and if people don't do them the big guys win probably.

Ofcause the fact is that we are still to small for the big guys to really take us as a real threat.

Since we are our own we can't really be brought or to some extent even sued for anything we try to be neutral so at least we will never bee invaded.

However our advantages compaired to others are our weakness.

We don't have protection of a graphics intercepter driver and our own in house code with our own scripting language.

We use a known one, and take most everything from the os so in theory we can handle a lot more than the competition we can also release faster and get ideas and features in faster.

Worse, just about every company is being absorbed by vfo, dolphin is the only comercial I know of for the pc still out there.

Then there is us.

No one has moved that far into it all you'd think someone would have looked at the accessibility monopoly they beat microsoft over that to some extent, but vfo is a monster allowed to grow into what it is now.

It started as most have at humble beginnings but now who knows.

On 25/01/2018 8:40 p.m., zahra wrote:
hi joseph and all.
i pray and wish for unity of our comunity.
i admire opensource and helpful programs like nvda, always remember
your kindness and never forget praying for all of you sincerely!

On 1/24/18, Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:
Yeah well I'm surveyed and consultation out. it seems these days there are

such consultations done all over the place about everything from babies
nappies to screenreaders and I've yet to see any of them bear any fruit in
the way things are done because I feel that everything these days is driven

by vested interests and cost.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Mário Navarro" <mario.gnv@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, January 24, 2018 3:50 PM
Subject: Re: [nvda] A few thoughts: Web Aim survey, quantity versus quality,

feeling burnt out and tutorials


absolutely right.

thank you good friend.


long life to Joseph Lee.

cheers.



Às 17:25 de 23/12/2017, Joseph Lee escreveu:
Dear NVDA community,

As I read messages on recent discussions, I realized just how much
enthusiasm and concern people have over NVDA and its future. At the
same time, it became clear to me that I and other developers and
community elders need a day off and just listen to you all, as
listening allows us to think about what others are saying and plan
things accordingly.

But first, a humble opinion about surveys and other points:

First, when calls for the seventh Web AIM survey went out, I told
people to not just do it to “increase” market share. I specifically
told screen reader companies to not coerce users to do it, but let
people take it out of their own willingness. This advice was to avoid
a fiasco that happened with Web AIM 6 where AI Squared (now part of
VFO) staff told Window-Eyes users to fill out the survey in mass
numbers, which became a small controversy within the screen reading
world, and to me, making Web AIM results no longer credible.

As some folks pointed out, Web AIM numbers depend on how many people
fill it out and where they come from (and this is true of any surveys
where word of mouth drives participation). The results also depend on
demographics and other factors such as choices given, how the
questions are worded, and overall objective. If one or more data
points seems to be dominant, they can be either skewed or outliers,
with the more extreme cases being termed “outliers” and they affect
how the results are explicated (interpreted). Even skewed data, such
as what I can perceive from some surveys including recent Web AIM
iterations can affect statistical calculations to a point where it
raises genuine questions about bias, credibility, and others (after
all, success of statistics, particularly inferential statistics,
depends on a representative sample or a close equivalent that allows
researchers to approximate the real world, which is prone to errors if
not done correctly such as misinterpretation, bad outliers, only some
groups participating, not looking at things more deeply and what not).

One important thing to note is that Web AIM is a representative
survey, thus the result in front of me could reflect reality. However,
due to recent controversy, possible type I and II errors
(false-positive and false-negative, respectively) and because of
outliers and skewed data and participation, it does not truly reflect
actual data, which is a point some folks here are trying to say and I
concur with. My explication of Web AIM 7 is that, in some parts of the
world, JAWS for Windows is more popular. However, given the fact that
not all geographical regions are represented, I’d counter by saying
that this is not a true representative sample that includes every
continent, and if it did, the story would be different and will
reflect reality a bit better (not a lot because there are other ways
of skewing data such as filling it out on behalf of an organization,
robotic fillers and so on). Coupled with the fact that Web AIM went
through a major controversy recently that damaged its credibility
somewhat, I would dare not trust Web AIM results again.

This leads to my second point: quantity versus quality. If NV Access
went straight for quantity alone, they could have implemented all
possible feature requests in hopes of boosting market share. The
reality in front of us says otherwise: not all feature requests are
here. Numerous factors contribute to this problem:

* Lack of leading developers: in 2017, a long-time NVDA developer
started working for another organization, and NV Access has been
looking for his replacement ever since. Even if the replacement is
found, it’ll take several months for him or her to become used to
this community, learn about accessibility and how to interact with
members, and earn our trust (it took Reef Turner a year to fully
earn our trust). Folks can counter this by saying that there are
countless contributors out there, but ultimately what gets into
NVDA depends on pull requests and review time from NV Access.
* Attitudes about open-source software from organizations: as some
folks pointed out, there are prevailing attitudes about
open-source in organizations that makes it a bit harder for NVDA
to land on their computers, which allows developers to assess true
needs of organizations through user feedback. Without valuable
feedback from organizations (a quality one at that), we won’t see
huger progress in NVDA development.
* Outside attitudes about the NVDA community: from the inside, NVDA
community is seen as a tight nit of enthusiasts who strives to
make NVDA better every day. On the outside, however, we have a
mixed bag of reputations, from admiration to honorable mentions to
disdain. Every organization have these mixed reputations,
especially more so for a community powered by technology such as
Linux kernel developers, web browser vendors and web standards
organizations, and even screen reader community. Not only we need
to show that we are united inside, we need to showcase unity
outside of this community.
* Inside matters just as outside: public relations outside of NVDA
community is important, but unity within an organization is just
as important as public organizational face (I’ll address
developer’s point of view below). What makes NVDA stand out is our
unity despite coming from different circumstances and backgrounds.

Most of these point to quality, not quantity alone. In summary,
quantity is important, but quality is just as important as how many
people download NVDA 2017.4 between Christmas and New Year.

Lastly, in regards to organization internals, I’d like to address
something I really wanted to say for the past few weeks: sometimes, I
felt burnt out. My initial response to your enthusiasm over my audio
tutorials was that I’ll ask for justifications for producing an
updated version, seeing that there are countless free videos and
tutorials out there. This was partly because I truly felt burnt out
with academics, speech and debate competitions and what not
(especially after a debate regarding a potential feature held not long
ago), at one point telling myself that I’ll retire from the NVDA
community sooner than later and feeling as though I carried important
burdens on my shoulders. But you didn’t see that justification post;
instead, I posted links to where you can download the 2018 version of
my audio tutorial series. In effect, I’ve given up my Christmas
holidays for this community, knowing that I needed a time to listen to
you all and do something about it. All this was possible because of a
simple act of listening and thinking about what the community means to
me and what my work means to everyone. I’m committed to finishing
Welcome to NVDA 2018 series before NVDA 2018.1 ships, with several
addenda coming after that, all because of support from this community
and outsiders. And I promise again: The Welcome to NVDA 2018 series
was, and will remain, free for all. All I ask of you in return is
donate to a cause that makes equal access to technology possible,
especially during this holiday season and beyond.

I’m sure for many of you, my musings above are a bit hard to digest.
Now you know why I don’t trust Web AIM survey results, quality is just
as important as quantity, and read a confession from a community
leader on his inner feelings. But there are two more things you need
to know, something all of us needs to think about:

Community leaders won’t stay with you forever. In early 2017, I sensed
that a long-time NVDA developer would leave this community for
something better. Only I and others didn’t know until summer that it
would be Jamie moving onto Mozilla Foundation.

I also felt, back in early 2017, that my active time with the NVDA
community is slowly drawing to a close. I don’t know when it’ll
happen, but I’ve been laying foundations for the next generation of
developers and enthusiasts to take the lead. This is one of the
reasons for setting up the devlearning subgroup, because I felt it is
time for me and other leaders to teach NVDA internals and other
concepts to the next group of community leaders and developers so they
can bring NVDA to the next level and do more amazing things than I and
others did (in my case, for the past five years).

Lastly, I sense a time when this community will face a sharp divide to
a point where people will start questioning the merits of this
community. I only told a select few earlier because it wasn’t right
for me to disclose it early and for them to prepare a plan. The screen
shade debate is, in fact, a sort of a preview of what is to come. One
of the fundamental questions you will face at that time will be
whether you still have your first love for NVDA, and whether you still
have your original reasons for joining this community. The survival of
this community at that time will depend on your ability to unite to
face a difficult situation, even if that means facing possible splits.
One thing you should NOT do at that time: ignoring new users and
outside critics, because they are influential opinion leaders and are
key stakeholders in NVDA’s future. One thing you SHOULD do though:
listen to others and think critically.

Hope this makes sense.

Merry (early) Christmas,

Joseph

--
A acção pode nem sempre ser felicidade, mas não há felicidade sem
acção...