Accessibility & VPAT

Last updated: January 2026

Our Commitment to Accessibility

Runestone Academy's mission is to make high-quality, interactive educational materials available to everyone. Accessibility is central to that mission. We strive to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, and to the applicable requirements of Section 508 of the Rehabilitation Act. Accessibility is an ongoing process, and we continue to improve support for users with disabilities.

Voluntary Product Accessibility Template (VPAT)

Our VPAT — also known as an Accessibility Conformance Report (ACR) — documents how our platform measures up against WCAG 2.1 Level AA success criteria. The full report is summarized below and is also available as a PDF for procurement and adoption reviews.

⇩ Download the VPAT/ACR (PDF)

Report Summary

Product: Runestone Academy Website

Conformance target: WCAG 2.1 — Level AA

Report date: January 2026

Scope of Evaluation

This report covers a representative sample of publicly accessible pages on the Runestone Academy website, including marketing content, authentication workflows, and interactive textbook content rendered via JavaScript. It represents a best-effort conformance assessment based on manual review, not a formal certification.

Conformance Levels

Supports — the criterion is met with no known issues.
Partially Supports — some aspects meet the criterion; others may require improvement or verification.
Does Not Support — the criterion is not met.
Not Applicable — the criterion does not apply to this product.

WCAG 2.1 Conformance Table

WCAG Criterion	Conformance	Remarks
1.1.1 Non-text Content	Partially Supports	Images and icons include visible text alternatives where applicable. Some dynamically rendered interactive content (e.g., exercises, math) may require additional ARIA labeling or verification with assistive technologies.
1.3.1 Info and Relationships	Partially Supports	Pages use headings, lists, and semantic HTML. Consistency of heading hierarchy within interactive book pages should be verified.
1.3.2 Meaningful Sequence	Supports	Reading order appears logical in linearized views.
1.4.3 Contrast (Minimum)	Partially Supports	Text is generally readable; formal contrast ratio verification is recommended to confirm AA compliance in all areas.
1.4.5 Images of Text	Supports	Text content is rendered as text rather than images, except where mathematical notation is rendered programmatically.
2.1.1 Keyboard	Partially Supports	Core navigation and forms are keyboard accessible. Interactive textbook components require further keyboard-only testing.
2.1.2 No Keyboard Trap	Supports	No keyboard traps observed in primary navigation and forms.
2.4.1 Bypass Blocks	Supports	“Skip to main content” links are present on authentication pages; consistent use across all pages is recommended.
2.4.2 Page Titled	Supports	Pages have descriptive and unique titles.
2.4.6 Headings and Labels	Supports	Headings and labels are generally descriptive and informative.
3.1.1 Language of Page	Supports	Page language is programmatically declared.
3.3.2 Labels or Instructions	Supports	Form fields include visible labels and instructions.
4.1.1 Parsing	Supports	Markup appears well-formed in tested pages.
4.1.2 Name, Role, Value	Partially Supports	Standard UI elements expose appropriate accessibility semantics; custom interactive elements may require additional ARIA roles and states.

Known Strengths

Clear page titles and navigation structure
Labeled form fields on login and user workflows
Semantic HTML used for core layout and navigation
Consistent navigation across pages

Known Limitations and Areas for Improvement

Interactive Content: Coding exercises, quizzes, and mathematical content rendered via JavaScript should be verified with screen readers and keyboard-only navigation.
ARIA Enhancements: Some custom widgets may benefit from additional ARIA roles, states, or descriptions.
Contrast Verification: Automated contrast testing is recommended to confirm full WCAG 2.1 AA compliance.

Testing Methodology

Accessibility testing is performed using a combination of manual review, automated tooling, and functional testing:

Manual structural review of page structure, headings, landmarks, semantic HTML, form labels, and page titles.
Keyboard navigation testing of core workflows, including focus order and checks for keyboard traps.
Automated and assisted tooling using the WAVE Accessibility Evaluation Tool, with results reviewed manually to distinguish actionable issues from false positives.
Authenticated page evaluation of dashboards, interactive exercises, group-work, and instructor interfaces after logging in as a standard user.

Due to the dynamic nature of interactive educational content, not all possible user paths are evaluated during each review cycle. Issues identified through testing are prioritized and addressed as part of ongoing development and maintenance.

Assumptions and Disclaimers

This VPAT is based on a limited manual review of representative public pages and does not constitute a legal guarantee of accessibility compliance. Accessibility is an ongoing process, and Runestone Academy continues to improve support for users with disabilities.

Reporting an Accessibility Barrier

If you encounter an accessibility barrier, need content in an alternative format, or have a procurement or accommodation request, please let us know. Include the page URL and a description of the problem so we can reproduce and address it.

Accessibility contact: [email protected]