K12 Academics is committed to making our website usable by as many people as possible, including people with disabilities. We have been online since 2004, and our purpose has always been to help families, students and educators find the right school, college, camp, business and program in their community. That purpose only works if the site is usable by everyone trying to reach it.
This statement explains where we stand, what we have done, what we know is not yet finished, and how to tell us when something does not work for you.
Conformance status
The Web Content Accessibility Guidelines (WCAG) define requirements for making web content more accessible to people with disabilities. WCAG 2.2 is the current version, and Level AA is the level most organizations and regulations work to.
K12 Academics is partially conformant with WCAG 2.2 Level AA. "Partially conformant" means that most of the site meets the standard, and that some parts do not yet fully conform. The sections below set out which parts.
What we have done
Across the site we have worked to ensure:
- Every image carries alternative text, or is correctly marked as decorative so that screen readers skip it
- Text contrast meets the WCAG AA minimum against its background
- A skip link lets keyboard users jump straight past the navigation to the main content of the page
- Pages use proper heading structure, a single main heading, and named page regions (header, navigation, main content, footer) so that screen reader users can navigate by landmark
- Every form field has a visible label
- The page language is declared so that screen readers pronounce content correctly
- Zoom and text scaling are never disabled, so you can magnify the page in your browser
- Links are distinguishable without relying on color alone
- Tap and click targets meet the minimum size and spacing requirements
How we test
We assess the site by self-evaluation, using a combination of:
- Automated testing with axe-core, the open source engine behind most accessibility scanners, run against WCAG 2.0, 2.1 and 2.2 at Levels A and AA
- Testing at both desktop and mobile screen widths, because some issues appear at one and not the other
- Manual review by our team, working through the WCAG 2.2 success criteria that automated tools cannot check
Our most recent automated testing found no WCAG failures on our homepage at desktop width. Testing at mobile width identified one issue affecting assistive technology, which is described under Known limitations below and is scheduled for correction. We treat automated results as a starting point rather than a conclusion. Automated tools can only check a portion of what WCAG requires, so our manual review is the more meaningful measure, and it is ongoing.
This site has not been audited by an independent third party. We will say so here if and when that changes.
Known limitations
We would rather tell you about these than let you discover them.
PDF documents
We publish research reports, guides and media kits as PDFs. Many of these were produced before we adopted accessibility requirements for documents, and they are not fully tagged for screen reader use. If you need the content of any of our PDFs in an accessible format, email us and we will provide it.
Member and partner submitted content
Our directories include profiles, descriptions and images submitted by schools, colleges, camps, vendors and other organizations. We cannot guarantee that text and images supplied by third parties meet accessibility requirements. Where we are told about a problem, we correct it or ask the submitting organization to.
Embedded third party components
Some pages include components we do not control, such as spam protection on our forms and embedded content from other services. These may not meet the same standard as the rest of the site. If one of these blocks you from completing something, contact us and we will complete it with you by another route.
Older pages
We have published continuously since 2004. Some older pages have not yet been reviewed to the current standard. We are working through these.
Page region coverage
Automated testing identified one element on our homepage that sits outside a named page region. This is a best practice issue rather than a WCAG failure, and it is scheduled for correction.
Duplicate element identifiers at mobile width
Testing at mobile screen width identified duplicated element identifiers, which can cause a screen reader to announce the wrong label for a control. This is being corrected.
What we are working on
- Completing our manual review against all WCAG 2.2 Level AA success criteria
- Keyboard only testing across our main user journeys, including search, directory browsing and our contact and membership forms
- Testing the site at 200% zoom and at 320 pixels of width
- Reviewing our form error messages so that every error is announced clearly and explains how to fix the problem
- Reviewing accessibility requirements for new PDF documents
Technical specifications
Accessibility of this site relies on the following technologies working with your browser and any assistive technology you use:
- HTML
- WAI-ARIA
- CSS
- JavaScript
Tell us about a problem
If you cannot access something on K12 Academics, or if something on the site is difficult to use, we want to hear about it. You do not need to know the technical cause, and you do not need to use any particular wording. Tell us what you were trying to do and what happened.
Email: accessibility@k12academics.com
Please include the address of the page if you have it, and a description of the problem. We aim to respond within 5 business days.
If something on the site is blocking you from doing what you came to do, say so in your message and we will help you complete it directly while we work on the underlying fix.
Date
This statement was prepared on November 17, 2026, and reflects our assessment as of that date. We review it as our manual testing progresses.