And if you recall, I was part of one of those "large U.S. Government Agencies" efforts. Probably the biggest one you had to deal with. But we had to do some MAJOR re-work of the app we had at that time (5.5) in order to get that sign-off. The strategies we used and developed partnering with BMC were not fully utilized in 7.5.
For example, we had to convert every single piece of trim text to character fields displayed as text so that they could be recognized as a tab stop by JAWS and WindowEyes. We had to develop a totally keyboard functional "field level help" system. We had to strip out images and replace them with character fields containing data that could be read by a screen reader. These were just a few. As a result of that effort with us, BMC came up with some great new coding ideas and functionality that was released as part of the 7.0 code line and some good new strategies in implementation. But (IMHO), it's not the technology or strategy that is missing, it's the lack of implementation of that technology or strategy. I understand that the effort required to deliver a truly Section 508 compliant app is tremendous, but.. Regards, Tim From: Timothy Powell [mailto:timothy.pow...@pbs-consulting.com] Sent: Monday, October 26, 2009 1:12 PM To: 'arslist@ARSLIST.ORG' Subject: RE: 7.5 or 7.6 Yes, I already have. The main concerns center around: The status flow bar and the significant use of images (which are not read by a screen reader and are not recognized as a tab stop). Images cannot be the only means to convey a message/result/status. Trim text which are not read by a screen reader and not recognized as a tab stop. Trim text cannot be the only means to convey a message/result/status. Field data is not automatically read by JAWS and the key commands to enforce data reads are not consistent. NOTE: In JAWS 7 data was read automatically. So it seems some functionality has been lost either in the application or it might be a JAWS 10 thing, but we have not been able to find a JAWS 10 setting for this. Field tabbing issues. Tabbing in order is extremely important. Data visualization fields. These were the biggest issues encountered in a 4-5 hour brief run through on 7.5 (via mid-tier) with JAWS 10. More issues as encountered are being reported. Regards, Tim From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Easter, David Sent: Monday, October 26, 2009 12:50 PM To: arslist@ARSLIST.ORG Subject: Re: 7.5 or 7.6 ** Tim, If you know of specific defects that affect the usability of AR System 7.5.00 for disabled persons, please do contact BMC Support and log those defects so they can be corrected. Significant effort has been taken by BMC in recent releases to ensure that the web client follows the guidelines set forward by Section 508 to the maximum extent possible. BMC is confident that our AR System based solutions can meet or exceed the review processes of agencies in the area of Section 508 - and we have, in fact, passed those reviews in many large U.S. Government agencies. A Voluntary Product Assessment Template (VPAT) can be made upon request to any customer who needs further information on this topic. -David J. Easter Sr. Product Manager, Solution Strategy and Development BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Timothy Powell Sent: Monday, October 26, 2009 9:27 AM To: arslist@ARSLIST.ORG Subject: Re: 7.5 or 7.6 ** Oh, I'd dare guess those are the LEAST of the section 508 compliance issues. Tim From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Easter, David Sent: Monday, October 26, 2009 11:51 AM To: arslist@ARSLIST.ORG Subject: Re: 7.5 or 7.6 ** There were some places where the alt tag was incorrect - for example on buttons for increasing or lowering weight. Those have been corrected, to the best of my knowledge, in ITSM 7.6 applications. -David J. Easter Sr. Product Manager, Solution Strategy and Development BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Boyd, Rebecca E. Sent: Monday, October 19, 2009 11:56 AM To: arslist@ARSLIST.ORG Subject: Re: 7.5 or 7.6 ** What are the issues with 508 compliance? From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of michael campbell Sent: Friday, October 16, 2009 6:35 PM To: arslist@ARSLIST.ORG Subject: Re: 7.5 or 7.6 ** Pretty sure 7.6 is going to fix the 508 compliance issues. I think 7.6 gets released very soon. mike _____ _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
