[NFBCS] NFBCS Digest, Vol 190, Issue 5

Brian Buhrow buhrow at nfbcal.org
Wed Mar 4 17:35:30 UTC 2020


	Hello Harry.   Since I believe the archive for this list is public,
I'm wondering how it is that  the list content itself is outside the reach
of modern search engines?  This makes no sense to me.  The search engines
should be getting more capable, not less over time and there's nothing new
about Mailman list archives.  It strikes me that if we can solve the search
engine problem, that is, get the archive of this list into search engines
so messages show up when folks do searches, that would do a lot to solve
most of the complaints I've seen here.  That, combined with a boiler plate
web page with basic instructions about how to search the lists and saying
who we are will do a lot to burnish our image.  I notice that Google seems
to be more selective about what it shows you when one does searches,
preferring to show you something called "favorite snippet from the web"
rather than the direct links themselves.  I wonder if we're suffering from
a side effect of the continued monetization of Googles search results?
In any case, I'm still confused by the notion that Google, Bing and other
search engines can't search and index our mailing list here.

-thanks
-Brian

On Mar 4, 11:12am, Harry Staley via NFBCS wrote:
} Subject: Re: [NFBCS] NFBCS Digest, Vol 190, Issue 5
} Good afternoon;
} 
} While I agree with the sentiment of this list is a good source for researching solutions to issues I also understand that this list is outside of the reach of modern search engines such as Google, Duck Duck Go, etc. It might behoove us to figure out a way to ale such things public ally searchable. One of the things that we may be struggling with is people not being aware of how to access said list serves. Let’s be clear. The list serve has in the past taken the place of a forum, reddit, or wiki.
} 
} Harry Staley
} (330) 718-1876
} Hstaley at nfbtx.org
} 
} > On Mar 3, 2020, at 06:00, nfbcs-request at nfbnet.org wrote:
} > 
} > Send NFBCS mailing list submissions to
} >    nfbcs at nfbnet.org
} > 
} > To subscribe or unsubscribe via the World Wide Web, visit
} >    http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
} > or, via email, send a message with subject or body 'help' to
} >    nfbcs-request at nfbnet.org
} > 
} > You can reach the person managing the list at
} >    nfbcs-owner at nfbnet.org
} > 
} > When replying, please edit your Subject line so it is more specific
} > than "Re: Contents of NFBCS digest..."
} > 
} > 
} > Today's Topics:
} > 
} >   1. Re: Accessibility for programmers (Star Gazer)
} >   2. Re: Making a plan (Bryan Duarte)
} >   3. Re: Accessibility for programmers (Todor Fassl)
} >   4. Re: Making a plan (Tracy Carcione)
} >   5. Minutes For The February 23, 2020 STEM Phone Conference
} >      (Louis Maher)
} >   6. How to get QtWebEngine to work like Electron apps (JooYoung Seo)
} >   7. A Puzzling Ribbon Change (Sahar's Beaded Creations)
} > 
} > 
} > ----------------------------------------------------------------------
} > 
} > Message: 1
} > Date: Mon, 2 Mar 2020 08:37:10 -0500
} > From: Star Gazer <pickrellrebecca at gmail.com>
} > To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
} > Subject: Re: [NFBCS] Accessibility for programmers
} > Message-ID: <5e5d0c05.1c69fb81.569c4.87a1 at mx.google.com>
} > Content-Type: text/plain; charset="utf-8"
} > 
} > Agree with this. 
} > I?d love a resource to give to people, just recently I wanted to give a friend info on how to alt caption. 
} > I found the info and sent it to him, but I had to dig for it. 
} > The friend is a Realtor, a smart guy and had no idea how to make the photos of houses he?s trying to sell accessible. 
} > 
} > Sent from Mail for Windows 10
} > 
} > From: Tracy Carcione via NFBCS
} > Sent: Sunday, March 1, 2020 9:34 AM
} > To: 'NFB in Computer Science Mailing List'
} > Cc: Tracy Carcione
} > Subject: Re: [NFBCS] Accessibility for programmers
} > 
} > Chris, Jack did volunteer use of a server he has access to to host a Wikki.  Let us be patient with each other.
} > 
} > It is surprising to me that NFBCS does not have a website, while the NFB crafters division does.  It seems strange that knitters and crocheters have managed it, while IT professionals have not.  But then many of the craft people are retired, or making a living selling what they make, while most of us are working.  But still ...
} > Tracy
} > 
} > 
} > -----Original Message-----
} > From: NFBCS [mailto:nfbcs-bounces at nfbnet.org] On Behalf Of Christopher Chaltain via NFBCS
} > Sent: Sunday, March 01, 2020 2:45 AM
} > To: NFB in Computer Science Mailing List
} > Cc: Christopher Chaltain
} > Subject: Re: [NFBCS] Accessibility for programmers
} > 
} > On one hand you say this isn't supposed to come from the ground up and 
} > on the other hand you say that the NFB doesn't represent the vast number 
} > of blind people in the country who don't attend the national convention. 
} > This seems like a contradiction to me. If you don't want to be part of 
} > the problem then you need to be part of the solution. Where did I miss 
} > it, but when did you volunteer to host or contribute to a wiki or a 
} > social networking page?
} > 
} > 
} > 
} >> On 2/29/20 9:23 PM, Jack Heim via NFBCS wrote:
} >> First of all, the vast majority of this stuff you can't just do 
} >> without approval from the NFB. I can't just create a web presence for 
} >> the NFBCS without authority from the NFB. But more importantly, its 
} >> not supposed to come from the ground up. There was a spontaneous 
} >> outburst of enthusiasm on this list for things we could do on behalf 
} >> of blind IT professionals. Typically, its the other way around. Lots 
} >> of groups have a problem, leadership asks if anybody wants to take on 
} >> a responsibility and they get crickets back. The leaders of the NFB do 
} >> not have that excuse. Who knows, maybe after this kurfuffle, they 
} >> will. But, no, up to this point, they don't have a problem not getting 
} >> enough volunteers because they haven't asked for any.
} >> 
} >> 
} >> 
} >>> On 2/29/20 8:30 PM, Kevin via NFBCS wrote:
} >>> Now, I'm gonna say something.  Please stand back, I need to clear my 
} >>> throat.  Okay, I'm ready.  Saying the NFBCS isn't doing anything is 
} >>> foolish because, you got it, we are the NFBCS.  If we want things 
} >>> done it is up to us, the volunteers.  That is all.
} >>> 
} >>> 
} >>> On 2/29/2020 9:22 PM, Jack Heim via NFBCS wrote:
} >>>> No, I have not missed the point. After all, I think we can all agree 
} >>>> that the point is that blind IT professionals have needs? There is 
} >>>> the problem of getting backwatered, lack of documentation on 
} >>>> accessibility tricks, little to no advocacy on behalf of blind IT 
} >>>> professionals. The NFBCS doesn't even have a web site. You google 
} >>>> NFBCS and you pretty much come up empty. These are problems. Did 
} >>>> anything in Brian's response indicate that the NFBCS was about to 
} >>>> take on those issues? I don't think so.
} >>>> 
} >>>> 
} >>>> The best proof of any theory is its power of prediction. Einstein 
} >>>> predicted that the sun's rays would be bent by the moon's 
} >>>> gravitational pull during an eclipse. When that prediction was borne 
} >>>> out, it was considered proof of Einsteinn's theory. Well, I made a 
} >>>> prediction. I am willing to wait.
} >>>> 
} >>>> 
} >>>> 
} >>>> 
} >>>> On 2/29/20 2:49 PM, cathy at sks.com wrote:
} >>>>> I am not trying to be contentious, but I think you, Jack, have 
} >>>>> missed the
} >>>>> point.
} >>>>> 
} >>>>> Completely read Brian's e-mail. He states in there that you can now 
} >>>>> pay your
} >>>>> dues online and do not need to attend the convention to be a member.
} >>>>> 
} >>>>> Brian reaches out in his e-mail to all of us to let him know if we are
} >>>>> interested in helping take action on any of the items discussed on 
} >>>>> this
} >>>>> list.
} >>>>> 
} >>>>> We in the NFB, are all volunteers with other things going on in our 
} >>>>> lives.
} >>>>> The Division will not get anything accomplished if members don't 
} >>>>> volunteer
} >>>>> to help. Brian, as our president, needs all of our help to make things
} >>>>> happen.
} >>>>> 
} >>>>> The main point of his e-mail is that he wants to make things happen 
} >>>>> but
} >>>>> wants to find out if there are others that want to volunteer to 
} >>>>> help. If
} >>>>> nobody volunteers, then probably nothing will happen. It is in the 
} >>>>> hands of
} >>>>> the members to step up to the plate and help.
} >>>>> 
} >>>>> Cathy Schroeder
} >>>>> E-mail: cathy at sks.com
} >>>>> 
} >>>>> 
} >>>>> -----Original Message-----
} >>>>> From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Jack Heim via 
} >>>>> NFBCS
} >>>>> Sent: Saturday, February 29, 2020 2:07 PM
} >>>>> To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
} >>>>> Cc: Jack Heim <john at johnheim.com>; Steve Jacobson
} >>>>> <steve.jacobson at outlook.com>
} >>>>> Subject: Re: [NFBCS] Accessibility for programmers
} >>>>> 
} >>>>> Brian, you missed the point.
} >>>>> 
} >>>>> 
} >>>>> The people on this list have been expressing some real needs and it 
} >>>>> just so
} >>>>> happens that the NFBCS is uniquely situated to do something about 
} >>>>> them.
} >>>>> There is an opportunity here. The NFBCS could be so much more than 
} >>>>> just an
} >>>>> email list and an annual meeting. If that is going to happen, you 
} >>>>> have to
} >>>>> choose to make it happen.
} >>>>> 
} >>>>> 
} >>>>> Admittedly, that is your choice. But can you understand that it is not
} >>>>> helpful to tell me that the rules of the NFB are such that I have 
} >>>>> to attend
} >>>>> the convention to have a voice? A typical person's reaction to that 
} >>>>> is not
} >>>>> going to be, "Well, if those are the rules, okay then." The NFB 
} >>>>> starts every
} >>>>> press release talking about how big and influential it is but it 
} >>>>> makes no
} >>>>> attempt to represent the vast majority of blind people who never 
} >>>>> attend a
} >>>>> convention. Ask any member of the NFB about the ACB and they will 
} >>>>> dismiss it
} >>>>> as meaningless and ineffective. True enough. But to me, all that 
} >>>>> means is
} >>>>> that the NFB has that much more of an obligation to represent me. 
} >>>>> If the NFB
} >>>>> isn't going to do this -- nobody is. So when you say that I have to 
} >>>>> attend
} >>>>> the convention or I have no say, that is the same as telling me 
} >>>>> that the NFB
} >>>>> is broken.
} >>>>> 
} >>>>> 
} >>>>> 
} >>>>> 
} >>>>> On 2/28/20 2:50 PM, Brian Buhrow via NFBCS wrote:
} >>>>>>    hello list members.  This is Brian Buhrow, current president 
} >>>>>> of the
} >>>>>> NFB in Computer Science, chiming into this topic. Although I'm coming
} >>>>>> into this discussion rather late, I have been following it and, like
} >>>>>> Steve, I am excited to see folks interested in working on some of
} >>>>>> these accessibility issues.  Since a lot has been covered in this
} >>>>>> thread, I'll try to address some of the points I've seen in this
} >>>>>> discussion and, perhaps, clarify where I think we are as an NFB
} >>>>>> division and what my vision is going forward for the division.  For
} >>>>>> those of you following this thread and contributing to it, if there
} >>>>>> are particular points you think I've missed in the below paragraphs,
} >>>>>> feel free to point them out in the discussion that's sure to 
} >>>>>> follow  this
} >>>>> message.
} >>>>>> 1.  For those of you who don't know me, I'm a long time NFB member 
} >>>>>> who
} >>>>>> has worked in the IT field for the past 25 years.  My expertise is in
} >>>>>> the field of Unix/Linux system programming and networking, both in
} >>>>>> writing client and server software, as well as building and
} >>>>>> maintaining local and wide area IP networks.  I also have a good deal
} >>>>>> of experience building and maintaining VOIP telephony networks and
} >>>>>> services.  For purposes of computer access, I am totally blind and
} >>>>>> rely completely on braille and/or speech output to gain access to the
} >>>>>> systems I work on.  Because I use a variety of equipment, I use a
} >>>>>> variety of access technologies.  I'm proficient with VoiceOver for
} >>>>>> iOS, NVDA under Windows, a long time user of Jaws, and, thanks to 
} >>>>>> Mike
} >>>>> Gorse, another member of this list, the Yasr program under Unix.
} >>>>>> It has long been my experience that creating access solutions which
} >>>>>> enable me to do my work have required thought, creativity, a lot of
} >>>>>> trial and error, much frustration on my part, and, some assistance
} >>>>>> from my colleagues and co-workers.  As someone mentioned up thread on
} >>>>>> this list, I'm certain that I've missed opportunities in my career 
} >>>>>> due
} >>>>>> to lack of accessibility, or my inability to think of a viable access
} >>>>>> solution, or just an assumption on my part  that I couldn't do 
} >>>>>> this or
} >>>>>> that.  Getting "backwatered" in the IT field is a constant problem 
} >>>>>> for
} >>>>>> everyone who works in it, and it is a particular problem for blind
} >>>>>> individuals, myself included.  Still, with that said, my career has
} >>>>>> been a rewarding one that has allowed me to enjoy life, 
} >>>>>> participate in
} >>>>>> a variety of exciting adventures and to join the society of my 
} >>>>>> friends
} >>>>>> and neighbors as a first class citizen.  The NFB and, by extension,
} >>>>>> the NFB CS division, has been a key element of that success because
} >>>>>> they gave me access to the likes of Steve Jacobson, Curtis Chong,
} >>>>>> Curtis Willoughby, Lloyd Rasmussen, Jim Barbour and John Miller, not
} >>>>>> to mention a vast array of other mentors and friends who could not
} >>>>>> only teach me a bit about how to do what I wanted, but who lead by
} >>>>>> example by doing it themselves.  I hope that overview will help 
} >>>>>> inform the
} >>>>> comments I have about particular issues in this thread that I'll 
} >>>>> mention
} >>>>> below.
} >>>>>> 2.  As Steve pointed out, the NFB CS Division is made up entirely of
} >>>>>> volunteers.  That means the things that get done in the division are
} >>>>>> the ones folks find interesting to work on and which can be scheduled
} >>>>>> in available time.  To that end, regarding the topic of an NFB CS web
} >>>>>> site or wikipedia, I think David Andrews said it best. It's not hard
} >>>>>> to build a web site or wikipedia pages, but maintaining them and 
} >>>>>> their
} >>>>>> relevance is very difficult over time.  A complaint I saw in this
} >>>>>> discussion was that folks didn't know how to find the kinds of
} >>>>>> information they were getting once they asked on this list. Since
} >>>>>> this list is archived and since there is a web site where the 
} >>>>>> archives
} >>>>>> are  stored and accessible, it seems that maybe what we should think
} >>>>>> about doing as a division is figuring out how to funnel folks to that
} >>>>>> archive so they can find the answers folks have provided on this 
} >>>>>> list.
} >>>>>> As an example, Nicole provided a nice summary of the solution to her
} >>>>>> 3270 emulation software problem.  There is not a real need, in my
} >>>>>> mind, to complicate the process of geting the word out to other 
} >>>>>> folks by
} >>>>> asking her to write a formal wikipedia page explaining her fixes.
} >>>>>> Rather, a simple page explaining that we have this list and the best
} >>>>>> terms to type into Google to harvest what it has to offer seems like
} >>>>>> the quick and easy way to leverage this list as a valuable resource.
} >>>>>> 
} >>>>>> 3.  As to the issue of accessible certification testing, I do see 
} >>>>>> this
} >>>>>> as a barrier to job entry and, as such, I think it is something the
} >>>>>> division should try to address.  I do not have the bandwidth or 
} >>>>>> enough
} >>>>>> familiarity with the details of the problem to take the lead to 
} >>>>>> work on
} >>>>> this issue.
} >>>>>> However, if there are folks who are willing and able to work on this
} >>>>>> issue and to cary it forward, possibly to formal actions, I'm willing
} >>>>>> to facilitate that work and help bring it to fruition, either by
} >>>>>> advocating for it on the national level, or by writing letters to
} >>>>>> appropriate individuals or agencies, or some combination of that and
} >>>>>> other means.  Write me off list if you are willing and able to 
} >>>>>> work on
} >>>>>> this issue and we'll figure out what steps need to be taken to get 
} >>>>>> things
} >>>>> moving.
} >>>>>> 4.   As an NFB national division, our business meeting, must, by
} >>>>>> definition, be held at the NFB national convention.  That doesn't
} >>>>>> preclude us from holding other meetings throughout the year, but our
} >>>>>> official business meeting is at the NFB national convention. That
} >>>>>> said, beginning last year, we began offering the ability for folks to
} >>>>>> join the division on-line, allowing them to reep the benefits of 
} >>>>>> NFB-CS
} >>>>> membership.
} >>>>>> Browse to:
} >>>>>> https://web.nfbcal.org/nfbcsreg
} >>>>>> to sign up as an NFB-CS member.
} >>>>>> 
} >>>>>>    Today, membership gains you the right to receive a copy of the
} >>>>>> recording of the 2019 NFB-CS meeting held in Las Vegas last summer.
} >>>>>> In future, it will entitle you to access the archive of recordings
} >>>>>> from our past meetings.  If you attend our business meeting, it gives
} >>>>>> you the right to vote.  If you are interested in working on any of 
} >>>>>> the
} >>>>>> issues I've outlined in this e-mail, it would be my preference, but
} >>>>>> not a requirement, that you join the NFB-CS division as part of
} >>>>>> starting inon the work.  In that way, you will be more officially
} >>>>>> connected with  the division if any of the work becomes formal.
} >>>>>> 
} >>>>>> 5.  Again, as Steve pointed out, most of the NFB-CS board monitors 
} >>>>>> and
} >>>>>> participates in discussion on this list.  Curtis Chong, our most
} >>>>>> recent past president and current treasurer, recently posted a
} >>>>>> treatise on the virtues  of upgrading Windows to Windows 10 and 
} >>>>>> trying
} >>>>>> out the new Microsoft Edge browser.  Steve Jacobson, our vice
} >>>>>> president, regularly contributes insightful comments on various
} >>>>>> ongoing discussions.  Jeanine Lineback, one of our board members,
} >>>>>> posts job postings for various accessibility related positions.  I
} >>>>>> send out meeting related announcements regularly, and also try to
} >>>>>> contribute to discussions where I think my input might be helpful.
} >>>>>> 
} >>>>>> 6.  In my mind, as I said earlier in this message, the real value to
} >>>>>> our division is the knowledge and experience of its members. This
} >>>>>> mailing list extends that knowledge and experience further because it
} >>>>>> includes many people who have a lot of experience but who are not
} >>>>>> officially members of the Division.  I know some folks would like us
} >>>>>> to cater more toward people who are working in the computer 
} >>>>>> science or
} >>>>>> IT fields.  I understand that and have tried to move our agendas at
} >>>>>> our annual meeting in that direction by including at least one panel
} >>>>>> or topic of interest to folks working in the computing profession.
} >>>>>> last year, for example, Tom Moore gave an excellent talk on how to
} >>>>>> build and maintain AWS networks and servers with nonvisual tools.
} >>>>>> However, I don't see a lot of value in splitting our resources into
} >>>>>> two lists, those discussing computer sciencey issues and those asking
} >>>>>> general accessibility questions.  The truth is, access technology
} >>>>>> being what it is, complicated, buggy and a moving target, every blind
} >>>>>> computer professional I know has, at one time or another, been 
} >>>>>> reduced
} >>>>>> to a neophyte user by a piece of buggy access technology, a buggy
} >>>>>> application, or just forgetting the magic sequence of commands or
} >>>>>> gestures to do a particular task with a particular ap from time to
} >>>>>> time.  As such, my feeling is that we can all learn from every
} >>>>>> question that comes up on this list and for those of us who are more
} >>>>> sophisticated, we can provide our own filtering if there are things 
} >>>>> we don't
} >>>>> want to follow on this list.
} >>>>>> I, for example, have a very strong knowledge of Unix/Linux, systems
} >>>>>> programming and integration, networking and VOIP systems. However, my
} >>>>>> knowledge of Windows is definitely not as complete. Therefore, I
} >>>>>> value the Windows questions that come up on this list because they
} >>>>>> teach me things I didn't know.
} >>>>>> Also, to that end, if there are things folks want us to work on as a
} >>>>>> division, I'm happy to entertain a discussion and potentially embark
} >>>>>> on the work, but I need your help to do it.  So, when you think about
} >>>>>> suggestions for the Division to work on, also try to think about how
} >>>>>> we might go about working on them in a sustainable manner.
} >>>>>> 
} >>>>>>    Thank you for taking the time to read this missive.  I hope it 
} >>>>>> helps
} >>>>>> clarify how I see the Division.  In the mean time, let's see if we 
} >>>>>> can
} >>>>>> move some of these ideas in this thread forward, shall we?
} >>>>>> 
} >>>>>> -thanks
} >>>>>> Sincerely,
} >>>>>> 
} >>>>>> -Brian, President, NFB in Computer Science.
} >>>>>> 
} >>>>>> _______________________________________________
} >>>>>> NFBCS mailing list
} >>>>>> NFBCS at nfbnet.org
} >>>>>> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
} >>>>>> To unsubscribe, change your list options or get your account info for
} >>>>> NFBCS:
} >>>>>> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/john%40johnheim.com 
} >>>>>> 
} >>>>> _______________________________________________
} >>>>> NFBCS mailing list
} >>>>> NFBCS at nfbnet.org
} >>>>> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
} >>>>> To unsubscribe, change your list options or get your account info 
} >>>>> for NFBCS:
} >>>>> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/cathy%40sks.com
} >>>>> 
} >>>> 
} >>>> _______________________________________________
} >>>> NFBCS mailing list
} >>>> NFBCS at nfbnet.org
} >>>> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
} >>>> To unsubscribe, change your list options or get your account info 
} >>>> for NFBCS:
} >>>> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/kevinsisco61784%40gmail.com
} >>>> 
} >>> 
} >> 
} >> _______________________________________________
} >> NFBCS mailing list
} >> NFBCS at nfbnet.org
} >> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
} >> To unsubscribe, change your list options or get your account info for 
} >> NFBCS:
} >> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/chaltain%40gmail.com
} > 
} > -- 
} > Christopher (CJ)
} > Chaltain at Gmail
} > 
} > 
} > _______________________________________________
} > NFBCS mailing list
} > NFBCS at nfbnet.org
} > http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
} > To unsubscribe, change your list options or get your account info for NFBCS:
} > http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/carcione%40access.net
} > 
} > 
} > _______________________________________________
} > NFBCS mailing list
} > NFBCS at nfbnet.org
} > http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
} > To unsubscribe, change your list options or get your account info for NFBCS:
} > http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/pickrellrebecca%40gmail.com
} > 
} > 
} > 
} > ------------------------------
} > 
} > Message: 2
} > Date: Mon, 2 Mar 2020 08:51:35 -0700
} > From: Bryan Duarte <bjduarte at asu.edu>
} > To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
} > Cc: Tracy Carcione <carcione at access.net>
} > Subject: Re: [NFBCS] Making a plan
} > Message-ID: <32FF1E7C-8E98-41F7-ABED-D40467D3932B at asu.edu>
} > Content-Type: text/plain;    charset=utf-8
} > 
} > Hello all,
} > 
} > I like to stay out of the confrontation but I am all for being a part of the solution. I think it is a great idea to have a website and/or wiki. I believe they both have their purpose and are useful in different ways. I feel we can and should do both but first we need to put our heads together and organize. Getting the server space, domain, and platform is easy as the people who handle that are a part of this organization, division, and list. Once we have the method and place the questions become, what content will we be populating the website and/or wiki with, by who, and when?
} > 
} > ? Content: what content do we want to share? I do not feel a free for all in this matter would be ideal. Can we put our heads together on some common topics of interest to begin with? I have heard several people talk about Linux server admin, perhaps some useful tools, methods, or tips/tricks in that arena would be a good starting point. Beyond that we can branch off with different operating systems, tools, or topics. The main thing here is to determine what is going to be our main thing?
} > ? Roles: who will be responsible for managing the content? I understand there is an open contributing protocol for wiki's under normal circumstances but as we are a division of the National Federation of the Blind I feel it might be best if we have a team who is responsible for managing content. This does not mean they are responsible for producing the content only that there is a central team who will manage the publishing of the content.
} > ? Timeline: we should come up with a road map and timeline for when and how content gets published. We can determine what topics we want to begin with, call for authors, and set a time frame for when submissions are due. Obviously this can be flexible but to keep the process moving deadlines are good.
} > ? Meetings: when and how should we meet to discuss? I personally am a big fan of Zoom for things like this. I have a professional account and would be happy to host an initial meeting to discuss ideas if others are interested. Beyond the initial meeting how should we continue meetings? biweekly, monthly, etc., 
} > ? Tools: I am not sure what the rules are as far as creating and using tools such as Slack, scrum boards, etc. I personally would like to create and use a Slack channel for this group. Also, it would be good to have some kind of software that is available for driving the content creation. Maybe a scrum board is a bit much but something like Trello, or even Google docs would be good.
} > 
} > These are just a few thoughts, suggestions, and ideas to help get us started. 
} > 
} > Brian 
} > 
} > Bryan Duarte | software engineer
} > 
} > Arizona State University Computer Science Ph.D Student
} > IGERT Fellow
} > Alliance for Person-centered Accessible Technology
} > Center for Cognitive Ubiquitous Computing
} > Google Scholar Profile
} > 
} > 
} > 
} > 
} > 
} > 
} > ------------------------------
} > 
} > Message: 3
} > Date: Mon, 2 Mar 2020 11:44:58 -0600
} > From: Todor Fassl <fassl.tod at gmail.com>
} > To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
} > Cc: Brian Buhrow <buhrow at nfbcal.org>,    Steve Jacobson
} >    <steve.jacobson at outlook.com>
} > Subject: Re: [NFBCS] Accessibility for programmers
} > Message-ID: <64b0e6cc-bb3a-2701-24e6-04cede5ae4aa at gmail.com>
} > Content-Type: text/plain; charset=utf-8; format=flowed
} > 
} > Can you expand on why you say you are not interested in trading e-mail 
} > about who the NFBCS represents? If people feel they are under 
} > represented, that seems like a pretty important issue to me.
} > 
} > 
} > 
} > 
} >> On 3/1/20 1:44 PM, Brian Buhrow via NFBCS wrote:
} >> I am not interested in trading e-mail about who we represent and who we
} >> don't as a division.  We are here, and if folks want to contribute their
} > 
} > -- 
} > Todd
} > 
} > 
} > 
} > ------------------------------
} > 
} > Message: 4
} > Date: Mon, 2 Mar 2020 13:31:35 -0500
} > From: "Tracy Carcione" <carcione at access.net>
} > To: "NFB in Computer Science Mailing List" <nfbcs at nfbnet.org>
} > Subject: Re: [NFBCS] Making a plan
} > Message-ID: <d74dfc6f9d9cc5b38f832fdcf0c2470b.squirrel at mail.panix.com>
} > Content-Type: text/plain;charset=iso-8859-1
} > 
} > This is great!  A plan, with real goals and suggested actions needed to
} > achieve them!
} > 
} > I would make a plea that, if we make a Wikki, we include some of the rarer
} > things, like my 3270 emulation solution.  Blind people are still using
} > 3270 emulation, and its very rarity makes it hard to find solutions.  I
} > would have been delighted to find something on the Internet with steps I
} > could try to fix my problem.
} > Tracy
} > 
} >> Hello all,
} >> 
} >> I like to stay out of the confrontation but I am all for being a part of
} >> the solution. I think it is a great idea to have a website and/or wiki. I
} >> believe they both have their purpose and are useful in different ways. I
} >> feel we can and should do both but first we need to put our heads together
} >> and organize. Getting the server space, domain, and platform is easy as
} >> the people who handle that are a part of this organization, division, and
} >> list. Once we have the method and place the questions become, what content
} >> will we be populating the website and/or wiki with, by who, and when?
} >> 
} >> ??? Content: what content do we want to share? I do not feel a free for
} >> all in this matter would be ideal. Can we put our heads together on some
} >> common topics of interest to begin with? I have heard several people talk
} >> about Linux server admin, perhaps some useful tools, methods, or
} >> tips/tricks in that arena would be a good starting point. Beyond that we
} >> can branch off with different operating systems, tools, or topics. The
} >> main thing here is to determine what is going to be our main thing?
} >> ??? Roles: who will be responsible for managing the content? I understand
} >> there is an open contributing protocol for wiki's under normal
} >> circumstances but as we are a division of the National Federation of the
} >> Blind I feel it might be best if we have a team who is responsible for
} >> managing content. This does not mean they are responsible for producing
} >> the content only that there is a central team who will manage the
} >> publishing of the content.
} >> ??? Timeline: we should come up with a road map and timeline for when and
} >> how content gets published. We can determine what topics we want to begin
} >> with, call for authors, and set a time frame for when submissions are due.
} >> Obviously this can be flexible but to keep the process moving deadlines
} >> are good.
} >> ??? Meetings: when and how should we meet to discuss? I personally am a
} >> big fan of Zoom for things like this. I have a professional account and
} >> would be happy to host an initial meeting to discuss ideas if others are
} >> interested. Beyond the initial meeting how should we continue meetings?
} >> biweekly, monthly, etc.,
} >> ??? Tools: I am not sure what the rules are as far as creating and using
} >> tools such as Slack, scrum boards, etc. I personally would like to create
} >> and use a Slack channel for this group. Also, it would be good to have
} >> some kind of software that is available for driving the content creation.
} >> Maybe a scrum board is a bit much but something like Trello, or even
} >> Google docs would be good.
} >> 
} >> These are just a few thoughts, suggestions, and ideas to help get us
} >> started.
} >> 
} >> Brian
} >> 
} >> Bryan Duarte | software engineer
} >> 
} >> Arizona State University Computer Science Ph.D Student
} >> IGERT Fellow
} >> Alliance for Person-centered Accessible Technology
} >> Center for Cognitive Ubiquitous Computing
} >> Google Scholar Profile
} >> 
} >> 
} >> 
} >> 
} >> _______________________________________________
} >> NFBCS mailing list
} >> NFBCS at nfbnet.org
} >> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
} >> To unsubscribe, change your list options or get your account info for
} >> NFBCS:
} >> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/carcione%40access.net
} >> 
} > 
} > 
} > 
} > 
} > 
} > 
} > ------------------------------
} > 
} > Message: 5
} > Date: Mon, 2 Mar 2020 20:44:13 +0000
} > From: Louis Maher <ljmaher03 at outlook.com>
} > To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
} > Subject: [NFBCS] Minutes For The February 23, 2020 STEM Phone
} >    Conference
} > Message-ID:
} >    <SN6PR07MB4976EF460FB2365B51617E65AAE70 at SN6PR07MB4976.namprd07.prod.outlook.com>
} >    
} > Content-Type: text/plain; charset="us-ascii"
} > 
} > Folks,
} > 
} > Here are the minutes from the February 23, 2020 phone conference on the methods which enable blind individuals to be successful in STEM careers.
} > 
} > The conference was presented by the National Association of Blind Students, and the Science and Engineering Division of the NFB.
} > 
} > We want to give special thanks to the presenters of the talks in this conference.
} > 
} > Please let me know if you have any questions.
} > 
} > Regards
} > Louis Maher
} > Phone: 713-444-7838
} > E-mail ljmaher03 at outlook.com<mailto:ljmaher03 at outlook.com>
} > 
} > -------------- next part --------------
} > A non-text attachment was scrubbed...
} > Name: Science Division and NABS Conference Minutes 2020-02-23 (1).docx
} > Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
} > Size: 44023 bytes
} > Desc: Science Division and NABS Conference Minutes 2020-02-23 (1).docx
} > URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20200302/b17f752c/attachment-0001.docx>
} > 
} > ------------------------------
} > 
} > Message: 6
} > Date: Mon, 2 Mar 2020 16:19:53 -0500
} > From: JooYoung Seo <jooyoung at psu.edu>
} > To: nfbcs at nfbnet.org
} > Subject: [NFBCS] How to get QtWebEngine to work like Electron apps
} > Message-ID:
} >    <CAEsZExjDiFwyx2jFkbPsgTNphFOmOjiEMuq25n3BYAi95eLTOw at mail.gmail.com>
} > Content-Type: text/plain; charset="UTF-8"
} > 
} > Hello,
} > 
} > I was wondering if someone could advise me on how I can get JAWS to
} > recognize QtWebEngine UI as being web browsers.
} > 
} > You know, JAWS does recognize Electron apps such as VSCode and Slack
} > as being glorified web browsers and thus allows navigating them as web
} > pages.
} > 
} > Currently, I am involved in a project that uses QtWebEngine wrapper
} > and Chromium rendering engine under the hood.
} > 
} > All Qt accessibility switches are enabled with Chromeium
} > --force-renderer-accessibility flag.
} > 
} > However, the latest JAWS does not recognize our application as being a web mode.
} > 
} > Any advice on how to tackle this issue would be so much appreciated.
} > 
} > All the best,
} > 
} > JooYoung
} > 
} > 
} > -- 
} > --------------------
} >  JooYoung Seo, CPACC
} >  Ph.D. Candidate (ABD),
} >  Learning, Design, and Technology
} >  Learning and Performance Systems
} >  The Pennsylvania State University
} >  Site: https://www.jooyoungseo.com/
} >  Phone: +1 (814) 777-5825
} >  E-mail: jzs323 at psu.edu
} > 
} > 
} > 
} > ------------------------------
} > 
} > Message: 7
} > Date: Tue, 3 Mar 2020 04:58:07 -0600
} > From: "Sahar's Beaded Creations" <sahar at inebraska.com>
} > To: "'Discussion of the Graphical User Interface,    GUI Talk Mailing
} >    List'" <gui-talk at nfbnet.org>,    "'NFB in Computer Science Mailing
} >    List'" <nfbcs at nfbnet.org>
} > Subject: [NFBCS] A Puzzling Ribbon Change
} > Message-ID: <00a301d5f14a$9f5d8d80$de18a880$@inebraska.com>
} > Content-Type: text/plain;    charset="us-ascii"
} > 
} > Hello,
} > 
} > 
} > 
} > For some reason, something in my Outlook ribbons changed. I like to press
} > Alt V A B to change the arrangement of messages, and now, I can't. When I
} > press Alt V, instead of saying "upper ribbon," Jaws says "lower ribbon". My
} > ribbons aren't hidden. I have pressed Control F1 by accident in the past, so
} > I thought that might be the problem, but it doesn't seem to be. If anyone
} > has any ideas, I'd sure appreciate it. I can't seem to find anything on
} > Google, but it is possible I'm asking the wrong question. Thanks in advance
} > for any help.
} > 
} > 
} > 
} > Warm regards,
} > 
} > Sahar Husseini
} > 
} > For hand-crafted, one-of-a-kind jewelry, please visit my Website at
} > <http://www.saharscreations.com/> www.saharscreations.com Find me on
} > Facebook at  <http://www.facebook.com/saharscreations>
} > www.facebook.com/saharscreations And remember, "Obstacles don't have to stop
} > you.  If you run into a wall, don't turn around and give up.
} > 
} > Figure out how to climb it, go through it, or work around it."
} > 
} > Michael Jordan
} > 
} > 
} > 
} > 
} > 
} > ------------------------------
} > 
} > Subject: Digest Footer
} > 
} > _______________________________________________
} > NFBCS mailing list
} > NFBCS at nfbnet.org
} > http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
} > 
} > 
} > ------------------------------
} > 
} > End of NFBCS Digest, Vol 190, Issue 5
} > *************************************
} 
} _______________________________________________
} NFBCS mailing list
} NFBCS at nfbnet.org
} http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
} To unsubscribe, change your list options or get your account info for NFBCS:
} http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/buhrow%40lothlorien.nfbcal.org
} 
>-- End of excerpt from Harry Staley via NFBCS






More information about the NFBCS mailing list