110 likes | 211 Views
Learn about APIP's purpose, model, and adoption steps for improving item portability and accessibility in testing. Explore the APIP conceptual model, integration with QTI and Access for All, and the importance of embedding accessibility information. Discover how APIP promotes portability and accessibility across testing systems.
E N D
Accessible Portable Item Profile (APIP) Standard CCSSO Pre-Session June 19, 2011
Purpose of Forum • Develop Common Understanding • What APIP is and what it is not • Conceptual model guiding APIP • How does APIP Work – Walk Through Item • Next Steps • What does it mean to adopt APIP • Action steps for adoption • Additional actions need to assure quality • Questions/Comments
The Problem • Portability of item and test content • Need for accessibility to be built into items
Existing Options • Question & Test Interoperability (QTI) Specifications • Starting point for #1, but . . . • Interpreted and implemented differently across industry • Lack method for embedding accessibility information • The Problem . . . • Portability of item and test content • Need for accessibility to be built into items
Existing Options • Access for All • Starting point for #2, but . . . • Focuses largely on visual needs • Not specific to testing • Not integrated with QTI • The Problem . . . • Portability of item and test content • Need for accessibility to be built into items
Solution • Accessible Portable Item Profile (APIP) Standard • Integrates elements of QTI 2.1 and Access for All • Expands accessibility tags to cover fuller range of test accessibility needs • Provides definition of expected system behavior for each accessibility tag
A Simple Analogy • Internet in the 1980s • groups used Internet to share information • Tagging of content dependent on “browser” used by group • Content was not portable across “browsers” • 1990: HTML developed • Internet in the 1990s • Multiple browsers developed to interpret HTML • Web page creation tools developed to produce content tagged with HTML • Content portable across HTML compliant browsers
A Simple Analogy - Part 2 • Testing Industry in the 2000s • Programs use Internet to deliver tests • Tagging of content dependent on test delivery system used by program • Items not portable across systems • 2010 - APIP developed • Goal for 2010s • Test delivery systems modified to interpret APIP • Item writing systems modified to produce APIP items • Items portable across systems • Caveat: Student rostering systems modified to produce APIP student access profiles