Trados Business Manager
Speech to Text
Managed Translation - Enterprise
Translation Management Connectors
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
RWS Community Internal Group
RWS Access Customer Portal
RWS Professional Services
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Academic Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic Tridion Docs User Group
Tridion Docs Europe & APAC User Group
Tridion UK Meetup
Tridion User Group Benelux
Tridion User Group New England
Tridion User Group Ohio Valley
Tridion West Coast User Group
WorldServer User Group
Trados GroupShare Ideas
Trados Studio Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
RWS Language Cloud TMS Ideas
RWS Language Cloud Terminology Ideas
RWS Language Cloud Online Editor Ideas
Managed Translation - Enterprise Ideas
Tridion Docs Ideas
Tridion Sites Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Documentation
To RWS Support
Detecting language please wait for.......
Okay, I shall get the ball rolling.
First of all, a little background so that you can understand where I am coming from.
I have used Trados for more than 15 years now and would find it extremely difficult to work without it. About three years ago, I lost the majority of my vision and now work with a mixture of text to speech systems and magnifiers. With the vast majority of programs, such as the Office suite, email programs, Internet browsers and so on, it would probably be easier for me to use a screen reader such as JAWS, but most of my working day is spent working with Studio 2011/2014, and this simply does not work with any screen reader.
A company has been trying to write scripts for JAWS in order to make Studio accessible, but after 18 months they appear to have given up as a result of intractable problems. I shall go into these in later posts.
Before any program can hope to be accessible for a screen reader, it must first be accessible for users who cannot for any reason use a mouse. In other words, all elements of the program must be available without the need to touch the mouse. This is not the case with Trados, and this is the first and most fundamental problem that needs to be addressed.
There are dozens of functions and screen areas that cannot be accessed without using the mouse. in this post, I shall restrict myself to one or two examples of each type of problem.
These are just a few of many hundreds of individual examples where Studio 2014 cannot be used without the mouse. The situation with Studio 2011 was far better, as the vast majority of primary functions were available from the menu system, which could be navigated in the same way as any other menu system, namely using access keys even if no hotkeys were available.
Although I shall mention many other issues in subsequent posts, the issue of keyboard accessibility is absolutely crucial, as vision-impaired users (and, indeed many other users) simply cannot use a mouse.
To experience the problems for yourself, simply start up Studio, disconnect the mouse and try to set up a project and stopped translating. Even that simple test fails, but does not even begin to address the problems that visually impaired users have.