Re: AW: Assistive Technology Detection

that was great IF you happened to be a windows user.
but what about the unix and apple and linux etc users??
all left out in the cold.
the company I worked for would fire someone if they even so much as 
brought a windows bit of software onto the property on their own machine. 
they had been fined heavily by the software alliance some years earlier 
for "stealing" software that was on someones personal computer.  so they 
took a hard line.

thus we were an all Linux operation and I became an all linux user on my 
personal computers.

Bob


On Wed, 31 Jan 2018, Batusic, Mario wrote:

> Date: Wed, 31 Jan 2018 07:03:25 +0000
> From: "Batusic, Mario" <mario.batusic@fabasoft.com>
> To: Patrick H. Lauke <redux@splintered.co.uk>,
>     "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
> Subject: AW: Assistive Technology Detection
> Resent-Date: Wed, 31 Jan 2018 07:05:13 +0000
> Resent-From: w3c-wai-ig@w3.org
> 
> Hello Patrick, All,
>
> The fact is, that more and more Websites/Applications are programmed using open source libraries. This is at the same time a problem and a big chance for the accessibility.
>
> 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.
>
> Would it be possible to organize globally a bin programming action to improve the main JavaScript libraries offering in all of them automatically accessible UI widgets similar to the standard windows controls? Naturally it would be necessary to pay programmers for this action, to finance several projects in this direction. "Waiting on Godo" in form of voluntary programmers - all people that have no free time - is nonsense.
>
> Ciao     Mario
>
> -----Ursprüngliche Nachricht-----
> Von: Patrick H. Lauke [mailto:redux@splintered.co.uk]
> Gesendet: Mittwoch, 31. Januar 2018 00:00
> An: w3c-wai-ig@w3.org
> Betreff: Re: Assistive Technology Detection
>
> On 30/01/2018 22:39, Sean Murphy (seanmmur) wrote:
>> The point I was making. If someone builds a web site using NodeJS, BootStrap or simular technology. Then accessibility is going to be a major headache for the developers with extra unrequired work to find solutions in relation to accesisbility. Focus must be placed on these type of development tools to have accessibility baked within the tool environment to improve software. As some of the tech articles I have read indicates this is going to become the norm, rather than the exception. Some of the newer tools out there are going to be even less code base focus. Therefore the author (developer) of the web site might not necessarily have deep coding skills.
>
> For clarity, I'd suggest using the term "frameworks" or "libraries" here for Bootstrap and co, rather than "development tools" or "tool environments".
>
> And yes - as most/all of these frameworks/libraries are open source, there's great value in focusing on improving these, in a variety of ways, depending on individual time/skill levels:
>
> - file good issues/bugs, with clear reduced test cases etc., showing where the output of these frameworks/libraries is inaccessible
> - suggest how the output could/should look like (i.e. rather than simply stating something doesn't work and needs to be fixed, actually give a clear example of what the output code should actually look like)
> - make actual code contributions/pull requests that fix the issue
>
> For my sins, I've been spending some time with Bootstrap over the years.
> While not perfect, we've managed to make quite a few changes for the better (and always happy to see any contributions as per the above).
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
>