Using Web Applications and Purchasing Software from a Vendor
Please contact CTS prior to purchasing any software. You must also request a VPAT from the vendor. A VPAT is a document created by the vendor that details how the software or product meets accessibility standards as outlined by Section 508 Standards.
State University of New York System
SUNY Policy states that all software/hardware (opens in a new tab) should be accessible and be used in the best accessible manner.
Web2 Access has been developed as a product of the Online Accessibility SUNY FACT2 task group who was charged with identifying competencies and skill sets related to online accessibility and provide professional development opportunities for SUNY, along with developing and recommending guidelines for software and educational resources (OERs, Web tools, publisher content, etc.) that may be purchased or recommended by the campus to ensure accessibility to meet Section 508 compliance. Please visit SUNYs Fact2 Online Accessibility Technology (opens in a new tab) to learn more.
VPAT (Voluntary Product Accessibility Template)
Ask publishers/software vendors to complete a Voluntary Product Accessibility Template (VPAT). Recommend that VPAT be on file for campus to use if purchasing on own. Verify the version of software and date when template was completed.
Contact Campus Technology Services by phone: (914) 251-6465 or by email: firstname.lastname@example.org
Accessible Application Methods
Web sites and applications use various tags to ensure all content is accessible to everyone. If you follow all the how to guides in this section you would cover most of these solutions. Web applications and widgets have a few extra issues you would not normally see and that is the “focus of the user” as noted on the Keyboard Accessibility page, must follow the same logical order for everyone using the application.
ARIA: Accessible Rich Internet Applications
Currently certain functionality used in Web sites is not available to some users with disabilities, especially people who rely on screen readers and people who cannot use a mouse. WAI-ARIA addresses these accessibility challenges, for example, by defining new ways for functionality to be provided to assistive technology. With WAI-ARIA, developers can make advanced Web applications accessible and usable to people with disabilities.
Status: Updated 15 January 2016. (first published December 2006). Editor: Michael Cooper. Developed with the Accessible Rich Internet Applications Working Group (ARIA WG) and the Education and Outreach Working Group (EOWG). Copyright © 1994-2014 W3C® (MIT, ERCIM, Keio), All Rights Reserved.
Learn more about WAI-ARIA for Application development
Website and Web Application Notes
All Purchase College websites are checked for accessibility against W3C AA standards - (opens new tab).