What this assessment covers
This self-assessment covers the Tuva Data Tools plotview. Plotview is the data-plotting interface: the canvas where students drag attributes onto axes, switch between chart types (dot plot, bar chart, histogram, box plot, scatterplot, map, and more), apply filters, and explore patterns in a dataset. It's the primary Tuva surface licensed to educational publishers for lessons, assessments, and state testing environments.
The assessment evaluates plotview against two standards:
- WCAG 2.1 Level AA — the standard referenced in the 2024 U.S. Department of Justice regulations requiring digital accessibility in public schools and universities (effective April 24, 2026).
- WCAG 2.2 Level AA — the current W3C Recommendation, published October 2023, adding six criteria most relevant to drag-and-drop interaction and touch-target size.
Out of scope: The Tuva Jr (playview) product and its accessibility posture will be documented separately when that assessment is complete.
How to read the status column
Every row in the assessment tables uses one of four status values. This matches the Section 508 / VPAT convention that procurement reviewers expect.
- Supports — The criterion applies to plotview and plotview meets it. Notes cite the feature and key file.
- Partially Supports — The criterion applies; some paths meet it, others don't. Notes cite what works, what's gapped, and planned remediation.
- Does Not Support — The criterion applies and plotview doesn't currently meet it. Notes cite the gap and planned work.
- Not Applicable — The criterion doesn't apply to plotview (e.g., no timed media, no authentication). Notes give a one-line justification.
Every criterion — including Not Applicable ones — is listed explicitly, with the reason stated in Notes. This is intentional: it lets a reviewer scan the column vertically rather than wondering whether something was omitted.
Status at a glance
Plotview demonstrates strong accessibility maturity in the perceivable and operable categories — dedicated infrastructure, contrast themes, colorblind-safe palettes, sonification (beta), full keyboard navigation, and 10+ language support. Remaining gaps are concentrated in automated testing, a handful of keyboard/focus patterns, and the WCAG 2.2 drag-movement alternative, which is implemented but currently gated behind a toggle.
WCAG 2.1 Level AA — 50 criteria
- 28Supports
- 11Partial
- 1Does Not Support
- 10Not Applicable
WCAG 2.2 Level AA — 55 criteria
- 30Supports
- 13Partial
- 1Does Not Support
- 11Not Applicable
These counts reflect our interim self-review. The independent Accessible Web audit will produce the formal conformance claim.
How we assessed
This self-assessment is the product of an internal review of the plotview source tree mapped against the W3C WCAG 2.1 and 2.2 Recommendations. Every Level A and AA success criterion was reviewed in turn; status values and evidence notes are grounded in code-level findings, not marketing claims.
- Evaluation methods
- Source-level code review of ARIA usage, keyboard handlers, and theming infrastructure; manual keyboard-only operability checks against the documented shortcut map; screen-reader spot-tests with VoiceOver on macOS; contrast-ratio verification of default and reverse-contrast themes; mapping of every Level A/AA success criterion to observed implementation.
- Product assessed
- Tuva Data Tools plotview (the data-exploration React package). Tuva Jr / playview is out of scope.
- Version / snapshot
- Review conducted against Data Tools v4.0.1 (data-exploration source as of March 2026); last reviewed April 2026.
- Browsers covered
- Chrome, Firefox, and Safari (latest stable releases). Edge is expected to behave equivalently to Chrome but was not spot-tested.
- Assistive technology covered
- VoiceOver on macOS. Coverage of NVDA (Windows) and JAWS (Windows) is part of the scope of the forthcoming Accessible Web audit.
- Standards referenced
- W3C WCAG 2.1 (June 2018) Level A + AA, and W3C WCAG 2.2 (October 2023) Level A + AA. WCAG 2.1 AA is a strict superset of WCAG 2.0 AA, which also satisfies U.S. Section 508 (Revised) software requirements.
- Accessibility contact
- support@tuvalabs.com — Use the subject line "Accessibility" and your message will be routed to the team member who leads accessibility at Tuva.
- Refresh cadence
- This page is reviewed within 30 days of each plotview release and updated whenever a change could affect any criterion's status. A revision history is maintained internally and can be provided on request. If you're evaluating Tuva for procurement and need a dated snapshot of this page, email the accessibility contact above.
Terms used on this page
Short definitions for readers who aren't accessibility specialists.
Open glossary
- WCAG (Web Content Accessibility Guidelines)
- The international standard for digital accessibility, published by the W3C. We assess against version 2.1 (the legal standard under the 2024 DOJ rule) and version 2.2 (the current W3C Recommendation).
- Principle, Guideline, Success Criterion
- WCAG is organized hierarchically: four Principles (Perceivable, Operable, Understandable, Robust) → Guidelines (1.1, 1.2, …) → numbered Success Criteria (1.1.1, 1.2.1, …). Every row in our tables is one success criterion.
- Level A / AA / AAA
- WCAG criteria are tiered by conformance level. Level A covers the most essential requirements. Level AA is what the DOJ rule and most state procurement processes require — it includes all Level A plus a stricter set. Level AAA is the highest bar and is generally not expected for entire products. Our tables cover A and AA.
- Conformance
- A formal claim that a product meets every applicable success criterion at a given level. Because conformance is all-or-nothing per criterion, we avoid "percent compliant" framing and report status criterion-by-criterion instead.
- VPAT (Voluntary Product Accessibility Template)
- A standardized document, maintained by the ITIC, that vendors fill in to report how their product maps to accessibility standards (WCAG and Section 508). Procurement offices routinely request a VPAT. The forthcoming Accessible Web audit will produce Tuva's formal VPAT; this page is the interim self-review.
- Section 508
- The U.S. federal accessibility regulation for information and communication technology. The 2018 "Revised" Section 508 is technically aligned with WCAG 2.0 AA, which WCAG 2.1 AA fully covers.
- ARIA (Accessible Rich Internet Applications)
- A set of HTML attributes (
role,aria-label,aria-live,aria-expanded, etc.) that describe interactive components to assistive technology. Screen readers use ARIA to announce what a button does, whether a menu is open, and so on. - Live region
- An ARIA feature that lets an area of the page announce updates to screen readers without moving focus (e.g., when a grid cell changes, a filter is applied, or a chart updates). Tuva uses live regions to announce grid navigation.
- Sonification
- Representing data as sound. Tuva's sonification feature plays a tone for each data point so users who can't see the chart can still perceive the shape of the data (spikes, clusters, outliers). Currently released as a beta feature.
- Focus indicator
- The visual outline that marks which element has keyboard focus. A visible focus indicator is required by WCAG 2.4.7 so keyboard users can see where they are on the page.
- Skip link
- A visually hidden link at the very top of a page (revealed on keyboard focus) that lets assistive-tech users jump past navigation straight to the main content. Required by WCAG 2.4.1 Bypass Blocks.
- Assistive technology (AT)
- Software or hardware that helps people with disabilities use a computer. Common examples include screen readers (VoiceOver, NVDA, JAWS), screen magnifiers, switch devices, and speech-input software.
Full criteria tables
WCAG 2.1 Level AA
All 50 Level A + Level AA criteria, sorted by success-criterion number. This is the standard referenced in the 2024 DOJ regulations.
↓ Download as PDF available on this page
WCAG 2.2 Level AA
The full 2.2 Level AA set (55 criteria): every 2.1 A + AA criterion except the removed 4.1.1 Parsing, plus the six new 2.2 criteria covering focus visibility, drag alternatives, target size, consistent help, redundant entry, and accessible authentication.
↓ Download as PDF available on this page