We've provided the 508 compliance guidelines for both web and software 
(1194.21) to BMC along with the testing scripts the goverment uses to verify 
whether an application is 508 compliant.  Keep in mind that even if you are 
using the web client only (which relates to 1194.22) you also need to account 
for the use of 'Flash' which is a software app and falls under 1194.21).

BMC's view on 508 compliance is that they are compatible with JAWS.  However, 
the government's testing of 508 compliance is based on the standards as there 
are other tools there.  We have 5 outstanding items which I have RFE's into BMC 
based on version 7.6.03.  Initially, I submitted them and they were promptly 
rejected as not being valid tests - had to talk to a couple of folks at BMC to 
get them to re-open the items.  Doesn't mean we'll be successful in getting the 
improvements done, but at least they are open.

I don't have my list in front of me, but your list looks a bit different than 
the one I have to work off of (several of us are taking their 'Trusted Tester 
training).  I know mine has an item dealing specifically with shutting off 
style sheets - tested via the Web Accessibility Toolbar in IE.

Hope this helps for a start.
  ----- Original Message ----- 
  From: Leihkauff, Kenneth G (LEIHKAUFFK) 
  Newsgroups: public.remedy.arsystem.general
  To: [email protected] 
  Sent: Wednesday, June 01, 2011 6:13 PM
  Subject: Remedy ARS 508 Compliance Evaluation for Government


  ** 
  Hello,

   

  Does anyone know if BMC has provided help with completing the government's 
508 Evaluation Template, like the one shown below?  Thanks for any guidance or 
insight to completing the template or obtaining details from BMC.  I have seen 
BMC's whitepaper for guidance when developing ARS applications, but need to 
complete the required evaluation template when pursuing federal work.  

   

  Thank you.

   

  Ken Leihkauff

  SAIC

   

        Section 1194.22 Web-based Internet information and applications

        *  Refer to ( http://www.access-board.gov/sec508/guide/1194.22.htm) for 
details on the guidelines listed below.
       
        Criteria 
       Supporting Features
       Remarks and explanations
       
        (a) A text equivalent for every non-text element shall be provided 
(e.g., via "alt", "longdesc", or in element content).
        
        
       
        (b) Equivalent alternatives for any multimedia presentation shall be 
synchronized with the presentation.
        
        
       
        (c) Web pages shall be designed so that all information conveyed with 
color is also available without color, for example from context or markup.
        
        
       
        (d) Documents shall be organized so they are readable without requiring 
an associated style sheet.
        
        
       
        (e) Redundant text links shall be provided for each active region of a 
server-side image map.
        
        
       
        (f) Client-side image maps shall be provided instead of server-side 
image maps except where the regions cannot be defined with an available 
geometric shape.
        
        
       
        (g) Row and column headers shall be identified for data tables.
        
        
       
        (h) Markup shall be used to associate data cells and header cells for 
data tables that have two or more logical levels of row or column headers.
        
        
       
        (i) Frames shall be titled with text that facilitates frame 
identification and navigation
        
        
       
        (j) Pages shall be designed to avoid causing the screen to flicker with 
a frequency greater than 2 Hz and lower than 55 Hz.
        
        
       
        (k) A text-only page, with equivalent information or functionality, 
shall be provided to make a web site comply with the provisions of this part, 
when compliance cannot be accomplished in any other way. The content of the 
text-only page shall be updated whenever the primary page changes.
        
        
       
        (l) When pages utilize scripting languages to display content, or to 
create interface elements, the information provided by the script shall be 
identified with functional text that can be read by Assistive Technology.
        
        
       
        (m) When a web page requires that an applet, plug-in or other 
application be present on the client system to interpret page content, the page 
must provide a link to a plug-in or applet that complies with 1194.21(a) 
through (l).
        
        
       
        (n) When electronic forms are designed to be completed on-line, the 
form shall allow people using Assistive Technology to access the information, 
field elements, and functionality required for completion and submission of the 
form, including all directions and cues.
        
        
       
        (o) A method shall be provided that permits users to skip repetitive 
navigation links.
        
        
       
        (p) When a timed response is required, the user shall be alerted and 
given sufficient time to indicate more time is required.
        
        
       

   

   

   

  _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Reply via email to