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

[Lewis Wood]

My vote is GitHub;

This way some submissions can be simply a branch clone.

We could put a Mater Repo with a Long winded ReadMe file.
Repos could have naming conventions:
 Python==????
  Emulator Ideas --???
Javascript-?????
 And so on.
Even IDE tips and tricks, and accessibility considerations.

Lewis Wood
lewislwood at gmail.com


-----Original Message-----
From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Aaron Cannon via NFBCS
Sent: Sunday, September 4, 2022 12:41 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Aaron Cannon <cannona at fireantproductions.com>
Subject: Re: [NFBCS] generating discussion: what accessibility barriers would you like to see documented?

I'd recommend hosting any wiki with GitHub. It's easy, and likely a familiar tool for the vast majority of people involved in development. Oh, and it's free. We just need a person, or better yet, an active committee that can review submissions.

Aaron

--
This message was sent from a mobile device


> On Sep 4, 2022, at 10:50, Littlefield, Tyler via NFBCS <nfbcs at nfbnet.org> wrote:
> 
> 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/cannona%40fireantproductions.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/lewislwood%40gmail.com