[NFBCS] Accessibility of AWS Web Console

[Tom Moore]

Hi,
I use Aws on a daily basis with the Awscli and web console.
Some functions work easier with the Awscli than the web console and others
are easier in the console.
There are some functions that are not easy for me to use specifically
creating record sets in Route53 or working with different aspects of Vpcs.
As far as taking legal action I am not really in a position to give you any
advice on this area and I only approach things from a technical prospective.
The tasks I can not do myself I ask for help with other people in the
company and they help with the few things I do need and then I go on my way.

Tom




-----Original Message-----
From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Timothy Breitenfeldt via
NFBCS
Sent: Wednesday, February 05, 2020 11:14 AM
To: nfbcs at nfbnet.org
Cc: Timothy Breitenfeldt <timothyjb310 at gmail.com>
Subject: [NFBCS] Accessibility of AWS Web Console

Hi, I am currently going through training as a full stack web
developer, and we started working with AWS recently. I am a
screenreader user, and use NVDA and JAWS. I have found AWS to be
frustratingly accessible. In otherwords, accessible enough I think to
avoid a lawsuit. Has anyone approached AWS about the state of the
usability of AWS with screenreaders? Honestly, accessibility aside, as
a web developer, I can point out over a dozen problems with just the
HTML design, such as putting column headers in a separate table from
the body of the table.

I do know about the AWS CLI, and I have been using it, but it just is
sometimes easier to use the web console. I am getting the hang of the
user interface, but it is slow and frustrating that every time I
perform an action I get 0 feedback to weather anything happened, and
if anything did, where on the screen that new information is
presented. All of that aside, the AWS web console is inconsistent web
design, where some AWS services are easier to use than others because
the wizards have actual buttons rather than clickable text, or the
table column headers are apart of the same table as the body, etc...

Does anyone know if this problem has been brought to the attention of
AWS, what their response was, and if not, if there is enough
justification to take legal action to force Amazon's hand to fix the
problems?

Thanks,

Timothy Breitenfeldt

-- 

Timothy Breitenfeldt

Phone: 509-388-7262

Skype: timothyjb310 at outlook.com

https://www.linkedin.com/in/timothybreitenfeldt/

_______________________________________________
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/tommym2006%40gmail.com