Accessible eLearning Tools for K–12 Districts: What to Ask Before You Buy
By Kalin Schoephoerster | KShep Creative
This is the fifth and final post in a five-part series on eLearning tools for K–12 districts. Previous posts cover how to choose the right format →, which authoring tool fits your district →, whether your district needs an LMS →, and Loom, Camtasia, and when video is enough →.
Most districts evaluate eLearning tools on three things: features, price, and ease of use. Accessibility rarely makes the checklist — until after a purchase has been made and a problem has been discovered.
By then, the district is locked into a platform that may require significant workarounds, ongoing vendor pressure to fix known issues, or in the worst case a procurement decision that needs to be revisited entirely. That's a costly position to be in, and it's an avoidable one.
Accessibility belongs in the tool evaluation process from the start. Not because it's a compliance checkbox, but because a tool that can't produce accessible content will cost more time and money downstream than it saves upfront. And for K–12 districts under ADA Title II, the legal stakes of getting this wrong are real.
This post covers what to ask before any eLearning tool purchase gets made — and how the tools covered in this series perform against those questions.
Why tool accessibility matters separately from content accessibility
There are two distinct accessibility questions with every eLearning tool, and it's worth being clear about both.
The first question is whether the tool itself can be used by staff with disabilities. If a staff member uses a screen reader or keyboard-only navigation, can they operate the authoring tool, access the LMS, or watch and interact with training content? A platform that's inaccessible to the people creating or accessing content is a barrier before any training gets built.
The second question is whether the tool produces accessible output. A tool might be perfectly usable for the person building content but produce output that fails accessibility standards when staff try to access the finished training. Both questions matter, and neither one guarantees the other.
Evaluating tool accessibility means evaluating both: the experience of using the tool and the quality of what it produces. Vendors don't always make this distinction clearly, so asking about both explicitly is worth the extra step.
What a VPAT is and why you should always ask for one
A VPAT, or Voluntary Product Accessibility Template, is a document in which a software vendor self-reports how their product conforms to accessibility standards. It covers WCAG conformance, Section 508 compliance, and other relevant frameworks. It's called "voluntary" because vendors aren't legally required to produce one — but asking for one tells you a great deal about whether a vendor has done the work to evaluate their product's accessibility.
A VPAT doesn't guarantee accessibility. Vendors self-report, which means the document reflects their own assessment rather than an independent audit. A VPAT with many "partially supports" or "does not support" entries is a red flag. No VPAT at all is a bigger one. A VPAT that's several years old may not reflect current product versions.
What to look for: a recent VPAT that covers the specific version of the product your district would be using, with honest reporting on known gaps and a clear statement of what the vendor is doing to address them. For a fuller explanation of what a VPAT is and how to read one, see the FAQ →.
The five questions to ask every eLearning vendor
These questions work for any eLearning platform, authoring tool, LMS, or video tool your district is evaluating. Add them to your RFP process or vendor demo checklist and make them standard rather than optional.
1. Do you have a current VPAT, and can you share it?
The VPAT is your starting point. If a vendor can't or won't provide one, that tells you something important about how seriously they take accessibility. If they provide one, review it carefully before the demo — not after.
2. Does your platform meet WCAG 2.2 Level AA?
This is the standard K–12 districts need to meet under ADA Title II. Some vendors will say their platform "supports accessibility" without specifying which standard or level. Push for a specific answer. Partial conformance or conformance to an older standard may not be sufficient for your district's compliance obligations.
3. Can users navigate your platform using a keyboard only and with a screen reader?
These are the two most fundamental accessibility tests. Keyboard-only navigation matters for users with motor disabilities. Screen reader compatibility matters for users who are blind or have low vision. A vendor who can't answer these questions confidently hasn't done the testing.
4. What does your accessibility remediation process look like when issues are found?
No platform is perfectly accessible, and a vendor who claims otherwise isn't being honest. The more useful question is what happens when issues are identified: how are they logged, prioritized, and fixed? A vendor with a clear, documented remediation process is a safer long-term partner than one who treats accessibility issues as edge cases.
5. What training and documentation do you provide for creating accessible content in your tool?
A tool that can produce accessible output but provides no guidance on how to do so will produce inaccessible content in practice. Ask whether the vendor provides tutorials, templates, or checklists for building accessibly within their platform. The answer tells you whether accessibility is built into their product culture or treated as an afterthought.
How the tools covered in this series perform
Here's a brief accessibility summary for each tool from the previous four posts — useful both as a reference and as a starting point for your own vendor conversations.
Articulate Storyline: Strong accessibility output when used intentionally. Requires deliberate attention to keyboard navigation, focus order, alt text, and color contrast. Articulate provides documentation and templates for accessible development. VPAT available on the Articulate website.
Articulate Rise: Stronger built-in accessibility defaults than Storyline. Block-based structure enforces logical reading order. Still requires attention to alt text and color contrast. Generally more accessible by default for non-specialist builders. VPAT available on the Articulate website.
Canva: Improved accessibility features in recent versions but requires intentional use. Content exported as PDF needs additional work for full screen reader compatibility. Better suited for supplementary materials than for primary training content where full accessibility is required.
Canvas and Schoology: Both major K–12 LMS platforms have VPATs available and have invested significantly in accessibility. Actual conformance varies by feature and version. Request current VPATs and test with your district's assistive technology before committing.
Loom: Supports automatic caption generation with manual review capability. Basic keyboard accessibility. Limited VPAT documentation — worth confirming current status directly with the vendor before purchasing.
Camtasia: Full captioning workflow built into the editing timeline. Strong accessibility output for finished video. TechSmith publishes accessibility documentation on their website.
Build Capable: Designed for mobile-first delivery with accessibility in mind. Request a current VPAT and test with your district's specific assistive technology needs before committing.
Accessibility in tool procurement: the practical steps
Knowing what to ask is the starting point. Here's how to build it into your actual process.
Step 1: Add accessibility questions to every RFP and vendor evaluation. The five questions above are a starting point. Making them standard rather than optional changes the procurement conversation — and signals to vendors that your district takes accessibility seriously.
Step 2: Test with real assistive technology before purchasing. Request a trial or demo environment and have someone in your district who uses a screen reader or keyboard-only navigation actually try to use the platform. Vendor demos are curated. Independent testing is not.
Step 3: Review the VPAT against your specific use case. A VPAT covers the whole platform. Your district may only use a subset of features. Review conformance for the specific features you'll use most — the LMS enrollment flow, the course player, the authoring interface — rather than treating the VPAT as a pass/fail document for the entire product.
For K–12 districts navigating ADA Title II compliance more broadly, see What K–12 Districts Need to Know About the New Federal Digital Accessibility Rules →. For support evaluating your district's current digital content for accessibility barriers, see Accessibility Audits and Remediation →.
Tool features, pricing, and accessibility capabilities change. Always verify current specifications directly with vendors before making a purchase decision. This post reflects my experience and current market options as of 2026. Tools mentioned include Articulate Storyline, Articulate Rise, Canva, Canvas, Schoology, Loom, Camtasia, and Build Capable.
The complete series
This post completes the five-part series on eLearning tools for K–12 districts. Here's the full series in order:
K–12 eLearning: How to Choose the Right Format Before You Choose a Tool →
Articulate, Rise, and Canva: Which eLearning Authoring Tool Is Right for Your K–12 District? →
Does Your K–12 District Need an LMS? A Plain-Language Guide →
Loom, Camtasia, and When Video Is Enough for K–12 Staff Training →
Accessible eLearning Tools for K–12 Districts: What to Ask Before You Buy (this post)
Accessibility belongs at the beginning of the conversation
Tool accessibility doesn't become relevant after a purchase is made. It belongs in the evaluation process, in the RFP, in the vendor demo, and in the first conversation about what your district needs to build.
Districts that build accessibility into procurement decisions spend less time fixing inaccessible content later, carry less compliance risk, and build training that works for more staff from the start.
If your district is evaluating eLearning tools and wants to make sure accessibility is part of the conversation before any purchase gets made, that's exactly the kind of work I support.
Book a free 30-minute intro call →
Or explore accessibility audit and remediation services → to see how this work connects to your district's broader compliance picture.
Kalin Schoephoerster is a CPACC-certified instructional designer and accessibility consultant based in St. Paul, MN. KShep Creative partners with K–12 districts, higher education institutions, and EdTech organizations to develop accessible eLearning, instructor-led training, curriculum, SOPs, and website accessibility audits aligned with WCAG 2.2 and ADA Title II requirements.