Releases and limitations

Components and the reference assessment player

The item and section players, assessment toolkit, tools, theme and print player are the project's production components.

The assessment player is a reference implementation using those components. It can change without the same compatibility guarantees. Your application manages accounts, content, storage, navigation, timing and submission.

Pin the versions you test

Site examples use player suite version 1.0.0-beta.5. Install all packages in the suite at the same exact version.

The suite's documented policy permits breaking changes in patch releases. Read the intervening changelogs before upgrading. Element packages version independently, and item content names the exact element versions it uses.

Versions and upgrades · Legacy-player migration

Element and view coverage

The library has 31 types: 30 with editors and 12 with print views. Each element page lists its supported views and scoring behavior.

Data reference comes from versioned schema snapshots. Use the schema matching your element version. Documentation and examples link to their source revisions.

Accessibility target and evidence

PIE targets WCAG 2.2 AA. Automated and browser tests run, but manual assistive-technology testing is incomplete and known issues remain. Test the complete application with your content.

Some interface translations are generated and unreviewed. Accessibility catalogs can also hold alternative content types that require a custom renderer.

Accessibility and learner supports · Known player issues and evidence gaps(opens in new tab) · Element coverage(opens in new tab)

Accessibility of this site

The website is reviewed against WCAG 2.2 AA, with automated checks in both themes and browser checks for keyboard navigation, focus, narrow layouts and text spacing.

Live demos use published player and element packages. Known findings include unnamed authoring controls, a mismatch between visible and accessible labels in the theme tool, and duplicate landmarks in section demos. Some graphical interactions and assistive-technology workflows still need manual testing. Full conformance has not been established.

To report an access problem, open a website issue(opens in new tab) with the page, task and browser or assistive technology you were using.

Graded delivery

For secure grading, keep answer keys and scoring on your server, using hosted rendering and server-redacted models. Player modes and roles control presentation; your application enforces access permissions and supplies the backend.

Secure delivery and CSP · Persistence boundaries

Proposals and implementation

Design documents may describe features that are still proposals. Check the status records for branching, process events, evidence capture, embedded speech recognition and authoritative submission. The timed-media and formative guides describe the implemented APIs.

Shared-contract status(opens in new tab) · Independent QTI project and status