Hello, For the past year I have been working hard at trying to get Mcafee to make the web interface for their secure line of products accessible. This has not getting very far however I am now at a stage where I have direct contact with the product manager for the Secure web product. I have a way to go yet but I thought I'd send the list a quick mail with what has been the most promising update in twelve months. If you have any suggestions as to what I should do next I'm certainly open to them. This seems like an empty promis to me. No timelines, no definitive plans and a lot of talking in circles. Quoted mail begins: While the remarks made in context of this matter, are correct in regards to the Java technology being able to utilize the accessible assistance tools of Swing, I was assured by my engineering team that it would still not be fully supporting usage of the product in an accessible manner, which renders the decision to go with Java obviously problematic in the regard. I understand that you and especially the people affected by this are seeing this a decrease of functionality in capabilities in the product and I apologize for not respecting this fact. The question is, how did this happen? When we stated development of the new version, we didn't claim at all that Webwasher (historic name of the product) was supporting any technology that would allow screen readers or other tools to be used to administered the UI. Essentially it was a drop off from the HTML based technology we used back then. When the project started back in 2005, we first thought about continuing with a HTML/Javascript based frontend, whereas the AJAX technologies back in these days didn't deliver enough horse power to be used in conjunction with the product underlying capabilities. The decision to use Java was due to the fact that we could use client-side preprocessing of data to just feed that back to the backend and relief the backend from some operations – and Java was the only technology that could do that. In 2010, when 7 was released, the world had changed and the Ajax tools were much more powerful, so were the browsers, however we couldn't change the UI to something else, as this would have been dramatic delay. Having said, all this, the next question is, what are the plans? As we are not in a position to simply inject the assistive technology that Swing provides below a 2 years timeframe, we have taken a different approach. While we understand that the current UI is powerful and flexible and allows customer to do what they want, we also are aware of the fact that due to the freedom it provides, it limits certain customers, who are looking for an easy UI. We have started a priority initiative to create something that is called "Common UI". The commonality is in regards to the product using the UI – these are targeted to the Web products (appliance and SaaS), the emails products (appliance and SaaS) as well as the network security products in a later step. The key focus of this UI lies in easiness and plugin-less browser integration. The request to support assistive technology has been conveyed to the team in charge, which falls into the overall usability initiative that is embedded into this project. Mail ends: Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie Oireachtas email policy and disclaimer. http://www.oireachtas.ie/parliament/about/oireachtasemailpolicyanddisclaimer... Beartas ríomhphoist an Oireachtais agus séanadh. http://www.oireachtas.ie/parliament/ga/eolas/beartasriomhphoistanoireachtais...