Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Request No.2019-09
Date of RequestJanuary 1, 2019
RequesterOmid Pourzanjani, Chancellor's Office, Redesign Wkgrp
Application(s)Standard, Noncredit and Promise Grant
Section / Page

All pages

Steering Hearing DateAPPROVED 
Proposed Change to Download FileN/A
Proposed Change to Residency LogicN/A


Problems / Issues

Currently, CCCApply applications are only available (mostly) in English language. 

Accessibility Review of 2016 - Identified through 508 Compliance review that the current version of CCCApply Application were not compliant with screen readers and other visual-impaired technology.  CCCApply had been using the Hover Help to provide spanish language translation and additional onscreen help information to ESL and/or Spanish only readers and speakers.  State allowed us to keep the Spanish Hover Help with condition that we would convert to a different format for translation using a different method in any new versions of CCCApply.  (Note: English hover help would be restricted to text input fields only until any new version of CCCApply was developed.) 

CACCRAO Issue #5: CCCApply poses challenges for students whose first language is not English – and it’s not just Spanish that is needed – many colleges named a number of different languages that were needed and that the toggle switch does not work effectively for students – especially our under-served populations and ESL students whose computer skills are minimal.


When the OpenCCCApply applications were developed, the decision was made to not build a separate Spanish application because based on the feedback from the colleges that were subscribing to the XAP Spanish application, students weren't using that version; instead they were having a friend or family member help them complete the standard english application. A solution was to implement Spanish translations of the "Hover Help", which could also be easily nationalized with other languages down the road, easily. Unfortunately, per the 508 accessibility audit of 2015, our implementation of the Hover Help translation is NOT accessible. Therefore, if we want to translate the application to other languages in the future, we will have to find another method and/or create fully translated versions of the current application. 


Proposed Solution



Dependencies, Risks and/or Reporting Requirements?


Question

Yes

No

Which data field(s)?

What/How?

Would this change affect an existing question or data field on the Standard Application?
  •  
  •  


Would this change affect an existing question or data field on the International Application?
  •  


  •  
  •  


Would this change affect an existing question or data field on the Promise Grant Application?
  •  
  •  




Would Account (OpenCCC) data be affected by this change?
  •  
  •  


Does the question or data field align to an MIS reporting requirement now?
  •  
  •  


Does this change affect any other state or federal regulations or requirements?

  •  
  •  


Would this change affect existing residency logic?
  •  
  •  


Would any other data fields be affected by this change?
  •  
  •  


Would students users be affected by this change?
  •  
  •  


Would colleges be affected by this change? 
  •  
  •  


Would the Download Client be affected by this change?
  •  
  •  


What other tech center web services will be affected by this change?
  •  
  •  

i.e., Glue staging table?  Multiple Measur
Other dependencies?



Other implementation considerations?




Supporting Documentation

DescriptionFile TypeURLNotes
















  • No labels