W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2018

Re: AW: Assistive Technology Detection

From: David Woolley <forums@david-woolley.me.uk>
Date: Wed, 31 Jan 2018 10:46:48 +0000
To: w3c-wai-ig@w3.org
Message-ID: <67d85987-9772-43b4-c3a6-227ce9907cc9@david-woolley.me.uk>
On 31/01/18 07:03, Batusic, Mario wrote:
> Years ago Microsoft offered standard windows GUI controls and the most windows desktop programmesr used them in their software solutions. Thanks to this fact it was simple and easy for screen reader users (I am also one of them) to use almost every new windows program.

Even in those days, my experience was that marketing departments wanted 
user interfaces to either be different from the standard, or to look 
like those of the upcoming version of Windows, so an awful lot of 
programmer man hours went into trying to use a combination of the 
standard interfaces, and lower level APIs to create a unique user 
interface, or an emulation of one in a Microsoft Beta.

Going back even further, my experience was that a lot of the programming 
effort in most developments goes into trying make the chosen platform do 
something that it was not designed to do, often when it was designed to 
do something that would have been good enough for the end user, or there 
was a platform that would do it, but the marketing people weren't 
prepared to use it (e.g. it used languages associated with more skilled 
programmers).

(Just considering user interfaces, they would insist on number 
formatting rules which required a lot of explicit code in COBOL, but 
were trivial in the underlying machine language, rather than adapting 
the formats to what was easy in COBOL.)
Received on Wednesday, 31 January 2018 10:48:07 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 31 January 2018 10:48:07 UTC