[NFBCS] generating discussion: what accessibility barriers would you like to see documented?

[Michael Walker]

Hi Traci,

What is 3270 terminal emulation?

How do you read Outlook emails that are only scanned images?

I also love the GitHub idea for a wiki, and linking to external resources, as well as using the wiki to write down information where there are not external resources.

Mike

> On Sep 4, 2022, at 1:14 PM, Tracy Carcione via NFBCS <nfbcs at nfbnet.org> wrote:
> 
> I have experience with making 3270 terminal emulation accessible.  
> 
> I do a couple things in SQL Management Studio that I think make it easier to
> debug and check results using a screen reader. 
> 
> I have notes on how to read an Outlook email that is only a scanned image.
> 
> I have notes on how to get a transcript or subtitles out of Youtube.
> 
> I have notes on how to save the chat part of a Zoom meeting.
> 
> I have experience with the Goodfeel music translator suite of programs, and
> can go from a pdf or print sheet of music to a braille copy.
> 
> I have other miscellaneous notes, but these are the things I might start
> with.
> Tracy
> 
> -----Original Message-----
> From: NFBCS [mailto:nfbcs-bounces at nfbnet.org] On Behalf Of Littlefield,
> Tyler via NFBCS
> Sent: Sunday, September 04, 2022 11:49 AM
> To: NFB in Computer Science Mailing List
> Cc: Littlefield, Tyler
> Subject: [NFBCS] generating discussion: what accessibility barriers would
> you like to see documented?
> 
> Hello all,
> 
> If you've not read any of the current thread about creating a wiki or a 
> platform to share content, I'll give you a TL/DR; a few of us have 
> committed (as we're able) to creating a platform to document 
> accessibility issues. I am pulling together a site and a resource over 
> the next week or so to get this going. My question to you (and anyone 
> you want to circulate this to) is as follows:
> 
> 
> What accessibility barriers have you encountered as a student or as a 
> professional that had solutions that could be documented?
> 
> Further to this point, what would you yourself be willing to document?
> 
> 
> If you don't have time or resources to assist with the second point, 
> please still respond. It would be very easy to take your tips and ideas 
> and still generate documentation around the issue. The goal here is to 
> generate discussion and ideas around what could be placed here, and how 
> helpful it could be.
> 
> 
> I'll lead the race, just to get us all started:
> 
> * Editor accessibility with JAWS and NVDA
> 
> * Using AWS through AWSCli as well as other services (linode, etc). This 
> is more important for AWS because that website would make anyone sad.
> 
> * Usable frontend design tools (document Bootstrap here).
> 
> * Accessible SSH clients and workflows for using them.
> 
> * Maybe a section like applevis where services (Jenkins, Github, etc) 
> can just be noted as being accessible with notes either way? Sometimes I 
> just want to know if something is accessible or will be, without 
> installing it or using it first.
> 
> 
> Looking forward to hearing your thoughts on this!
> 
> 
> Thanks,
> 
> Ty Littlefield
> 
> 
> 
> _______________________________________________
> 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/michael.walker199014%40gmail.com