8. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 7/13/2017 3:41:34 PM Eastern Daylight Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.

8.1 Files compared

# Location File Last Modified
1 Genisis_v3.zip\Release 3_Docs Genisis2_Section_508_Release 3_Test_Approach_06162017.docx Wed Jun 28 20:38:24 2017 UTC
2 Genisis_v3.zip\Release 3_Docs Genisis2_Section_508_Release 3_Test_Approach_06162017.docx Wed Jul 12 20:07:38 2017 UTC

8.2 Comparison summary

Description Between
Files 1 and 2
Text Blocks Lines
Unchanged 1 20
Changed 0 0
Inserted 0 0
Removed 0 0

8.3 Comparison options

Whitespace
Character case Differences in character case are significant
Line endings Differences in line endings (CR and LF characters) are ignored
CR/LF characters Not shown in the comparison detail

8.4 Active regular expressions

No regular expressions were active.

8.5 Comparison detail

  1   This docum ent encomp asses the  steps perf ormed by t he Genisis 2 Test Tea m to place  them in c ompliance  with VA-50 8 requirem ents for B uild 1 thr ough Build  3.
  2   The Genisi s2 Test Le ad contact ed the 508  Complianc e Team for  assistanc e in ident ifying the  OIT 508 U ser Storie s that app ly to the  Genisis2 a pplication . Once the  user stor ies were i dentified,  the Genes is2 Test L ead create d a folder  and uploa ded the co llection t o Rational  Requireme nts Manage r (RM).
  3   The Genisi s2 Test an d Developm ent Teams  met with t he VA-508  Audit/Revi ew Team to  discuss t he Section  508 Audit  findings  and obtain  a better  understand ing of Sec tion 508 r equirement s and acce ptance cri teria.
  4   The Genisi s2 Team wo rked with  a JAWS SME  to conduc t 508 test ing using  JAWS and r esults wer e submitte d to the G enesis2 De velopment  Team. 
  5   The Genisi s2 Develop ment Team  worked wit h the JAWS  SME to di scuss pote ntial solu tions to t he issues  found.  
  6   This infor mation was  applied t o the fixe s and once  deployed,  testers p erformed r egression  testing of  the appli cation. On ce complet e, 508 tes ts were su ccessfully  re-execut ed using J AWS, the 5 08-recomme nded tool  for Genisi s2.
  7   A copy of  the 508 te st finding s is attac hed as bel ow for rev iew, if ne eded:
  8                                                        
  9  
  10