I would be glad to help you where I can, and to try to engage the consumer organizations such as NFB and Association of Blind Citizens for which I am both on respective boards. I am especially interested in SCCM accessibility among other products. Also I am a big supporter of out of the box OS install accessibility. We are just starting to work on an SCCM deployment. The GUI is terrible with Jaws in many places. I was fortunate that we had a really sharp consultant working with us and he was able to create Powershell scripts that I use in many instances for things that you would normally do in the GUI. He was from a company called: http://dyntek.com/ If any of you are looking for services I can put you in touch with the right people at Dyntek that I worked with because it looks to be a fairly big consulting company. If it was not for the quality and knowledge of the consultant from Dyntek in the areas of SCCM, Active Directory, and Powershell scripting and how to intigrate all of those components, I would not be able to be nearly as efficient and many tasks would be difficult or impossible or very time consuming in the GUI. The GUI is newer than an MMC snapin and does not work anything like an MMC snap in. It is more like a ribbon based interface. While the scripts would make anyone more efficient, they were critical in terms of me being a Jaws user being able to function with the SCCM product and items that it interfaces with. If any of you use SCCM and I know at least 1-2 of you do, I could set up some kind of chat where I could review what we have sscripted and maybe I could do a demo of common tasks I do in SCCM. I'm thinking over Skype or with some similar tool where you could hear both me and the screen reader. I still may need to get some Jaws scripts done for parts of the SCCM GUI, and I plan to engage our Microsoft TAM on SCCM accessibility in the GUI. Best, Mika -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of vic.pereira@ssc-spc.gc.ca Sent: Wednesday, May 21, 2014 9:26 AM To: blind-sysadmins@lists.hodgsonfamily.org Subject: Re: [Blind-sysadmins] Anybody else interested in chiming in on my Microsoft conversations about Accessibility? I will not be able to join you, however if you are successful in getting MS Project, Windows Server, MS Publisher and SharePoint to be more accessible I might have to add you to my Christmas card mailing list. Thank you for taking this on. It is an amazing gesture on your part. Vic Pereira Shared Services Canada/Integrated Network Services | Services partagés Canada/Services Intégrés de Réseau 400-400 St. Mary Avenue Winnipeg MB R3C 4K5 vic.pereira@ssc-spc.gc.ca 204-983-0653 Government of Canada | Gouvernement du Canada -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: May-20-14 6:32 PM To: 'blind-sysadmins@lists.hodgsonfamily.org' Subject: [Blind-sysadmins] Anybody else interested in chiming in on my Microsoft conversations about Accessibility? Hi all, Possibly next week, I plan to call up the Microsoft Accessibility hotline and hopefully get some folks who know what they are talking about so that I can in a very systematic fashion, pour out all of the accessibility issues I see with as many products from Microsoft as possible, and I won't stop escalating the issues until every single one has a solution. Care to join me? _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins This message contains information from Neighborhood Health Plan that may be confidential or privileged. This message is directed only to the individual or entity named above. If you are not the intended recipient, please be aware that any disclosure, copying, distribution, or use of the contents of this email is prohibited. If you have received this email in error, please notify the sender immediately and delete the message and any attachments.