It seems to me that one main point of SSIS is to turn visual studio into a
graphical front end for microsoft data warehousing features of SQLServer.
Thus, if you wanted to do things in the command line, you would scrap SSIS
and manage your data warehouse directly in SQLServer.
This wouldn't be a problem when working alone, but when you necessarily
have to use components created by members of the team, or when your team is
expecting you to create SSIS components for them to use, it doesn't help to
go playing around with the database manually.
To be honest, the fix for this is that microsoft follow both
internationally recognized and internally created standards and build
accessible things. In fact, the answer is for microsoft to care about
every aspect of quality, and simply build better quality things altogether,
but especially in accessibility which effects us directly. SSIS for 2019
was a train wreck when it first came out. Pressing the tab key in the
wrong places caused crashes and data dumps.
I don't know what it will take to get a culture of accessibility at
microsoft outside of the accessibility team itself, and possibly legal and
marketing. My guess is that trade associations will have to launch huge
class actions in order for microsoft to start taking accessibility seriously.
Meanwhile, anyone can make a mistake. Lots of individual people are doing
their best and making strides. But an ordinary user has to switch
accessibility tools so many times throughout a day that his productivity is
impacted. And their first reaction is not to screem at micrrosoft to fix
their terrible product, but to look for a way to run two of the same tool
simultaneously. It's easier to break more systems trying to make things
work than it is to get a world leader in enterprise technology to produce
something that doesn't suck.
With all due respect, this isn't a mistake or an isolated insident. People
should be mad about this. It's 2022.
Best,
Erik
On January 13, 2022 11:01:42 AM <juanhernandez98@xxxxxxxxx> wrote:
Hi All,
I'm working with VS 2019, and Microsoft SQL Server Integration Services.
There are things in SSIS that read well with Jaws, and others that only read
really well with NVDA.
Is there any way feasible to run both screen readers at the same time
functionally, but keep the active one muted?
Has anyone ever tried this, or does anyone do this?
I just loose some much time when moving between the screen readers on a
daily basis that I wish I could just run them both.
Any ideas would be greatly appreciated.
Best,
Juan
