Wisconsin K–6 technology standards
Wisconsin writes its own technology standards. They are published as Wisconsin Standards for Computer Science, adopted 2025 and are not a version of a national framework. 149 of 166 are matched to a national standard.
The `technology` subject anchors to ISTE. WI publishes three relevant things and only one is both current AND grade-taggable for K-6: the SUPERSEDED 1998 Model Academic Standards for Technology Education (A.8.1, what CSP served — the reason technology was deferred); Information & Technology Literacy (the 2017 ITL is grade-banded and built on ISTE's 7 strands by name, but the CURRENT Dec-2025 ITL revision replaced grade bands with a grade-AGNOSTIC Exploring/Developing/Implementing continuum that cannot be grade-tagged without fabricating a grade); and the Computer Science standards, whose Dec-2025 revision (formally adopted Fall 2025, superseding the 2017 draft) IS grade-banded (PK-5/6-8/9-12). So the CS Dec-2025 document is ingested — the current, grade-taggable adoption — matching the technology-subject precedent (NC/TN/RI/UT: state CS -> ISTE with the documented CSTA gap). Five domains ALG/PRO/DA/CSS/FUT; codes <DOMAIN>.<std>.<lp>.<band>.<seq> (band e=PK-5 filed K–5, m=6-8 filed grade 6; h=9-12 out of K-6 scope; a few codes typeset std.lp.seq.band were canonicalised). Extracted directly from DPI's adopted PDF via scripts/extract-wi-cs.py: the document embeds a subset font whose ToUnicode map is a substitution cipher, so scripts/pdftext.mjs (CMap-merge) reproduces the cipher and PyMuPDF/poppler decode the real glyphs (field-note RI-technology PyMuPDF prescription). The superseded CSP family 'Technology Education (1998-2017)' is excluded via the draft manifest subjectMap so a re-fetch can't clobber this CSV; re-run the extractor after any re-fetch. Doctrine #6 sex-ed strip applied at extraction (0 rows matched). VERIFIED full: complete code-set difference vs the document's own code scan (166 e+m codes in the PDF, 166 in the CSV, 0 either-only) and 166/166 rows at 100% word-recall vs an independent poppler dump.
- Framework
- Wisconsin Standards for Computer Science
- Adopted
- December 2025
- Source last checked
- August 11, 2026
166 standards, kindergarten through 6th grade
- ALG.1.a.e.1K–5
- ALG.1.a.e.2K–5
- ALG.1.b.e.1K–5
- ALG.1.b.e.2K–5
- ALG.1.c.e.1K–5
- ALG.1.c.e.2K–5
- ALG.2.a.e.1K–5
- ALG.2.a.e.2K–5
- ALG.3.a.e.1K–5
- ALG.3.a.e.2K–5
- ALG.3.a.e.3K–5
- ALG.3.b.e.1K–5
- ALG.3.b.e.2K–5
- ALG.4.a.e.1K–5
- ALG.4.b.e.1K–5
- PRO.1.a.e.1K–5
- PRO.2.a.e.1K–5
- PRO.2.a.e.2K–5
- PRO.2.b.e.1K–5
- PRO.2.c.e.1K–5
- PRO.3.a.e.1K–5
- PRO.4.a.e.1K–5
- PRO.4.b.e.1K–5
- PRO.4.c.e.1K–5
- PRO.4.c.e.2K–5
- DA.1.a.e.1K–5
- DA.1.a.e.2K–5
- DA.1.b.e.1K–5
- DA.1.b.e.2K–5
- DA.1.c.e.1K–5
- DA.2.a.e.1K–5
- DA.2.a.e.2K–5
- DA.2.a.e.3K–5
- DA.2.b.e.1K–5
- DA.3.a.e.1K–5
- DA.3.a.e.2K–5
- DA.3.a.e.3K–5
- DA.3.b.e.1K–5
- DA.3.c.e.1K–5
- DA.3.c.e.2K–5
- DA.4.a.e.1K–5
- DA.4.a.e.2K–5
- DA.4.b.e.1K–5
- DA.4.b.e.2K–5
- DA.4.c.e.1K–5
- DA.4.c.e.2K–5
- CSS.1.a.e.1K–5
- CSS.1.a.e.2K–5
- CSS.1.a.e.3K–5
- CSS.1.b.e.1K–5
- CSS.1.b.e.2K–5
- CSS.1.c.e.1K–5
- CSS.2.a.e.1K–5
- CSS.2.a.e.2K–5
- CSS.2.b.e.1K–5
- CSS.3.a.e.1K–5
- CSS.3.b.e.1K–5
- CSS.3.b.e.2K–5
- CSS.3.b.e.3K–5
- CSS.3.b.e.4K–5
- CSS.4.a.e.1K–5
- CSS.4.a.e.2K–5
- CSS.4.b.e.1K–5
- CSS.4.b.e.2K–5
- FUT.1.a.e.1K–5
- FUT.1.b.e.1K–5
- FUT.1.c.e.1K–5
- FUT.1.d.e.1K–5
- FUT.2.a.e.1K–5
- FUT.2.a.e.2K–5
- FUT.2.b.e.1K–5
- FUT.2.b.e.2K–5
- FUT.2.b.e.3K–5
- FUT.2.c.e.1K–5
- FUT.2.d.e.1K–5
- FUT.2.e.e.1K–5
- FUT.2.e.e.2K–5
- FUT.2.f.e.1K–5
- FUT.2.f.e.2K–5
- FUT.3.a.e.1K–5
- FUT.3.a.e.2K–5
- FUT.3.b.e.1K–5
- FUT.3.b.e.2K–5
- ALG.1.a.m.16
- ALG.1.a.m.26
- ALG.1.b.m.16
- ALG.1.b.m.26
- ALG.1.c.m.16
- ALG.1.c.m.26
- ALG.2.a.m.16
- ALG.2.a.m.26
- ALG.3.a.m.16
- ALG.3.a.m.26
- ALG.3.a.m.36
- ALG.3.b.m.16
- ALG.3.b.m.26
- ALG.4.a.m.16
- ALG.4.b.m.16
- PRO.1.a.m.16
- PRO.1.a.m.26
- PRO.2.a.m.26
- PRO.2.b.m.16
- PRO.2.c.m.16
- PRO.3.a.m.16
- PRO.4.b.m.16
- PRO.4.b.m.26
- PRO.4.c.m.16
- PRO.4.c.m.26
- PRO.5.a.m.16
- DA.1.a.m.16
- DA.1.a.m.26
- DA.1.b.m.16
- DA.1.b.m.26
- DA.1.c.m.16
- DA.2.a.m.16
- DA.2.a.m.26
- DA.2.a.m.36
- DA.2.b.m.16
- DA.3.a.m.16
- DA.3.a.m.26
- DA.3.a.m.36
- DA.3.b.m.16
- DA.3.c.m.16
- DA.3.c.m.26
Communicate the results of a Construct formal data reports that data investigation by explaining justify conclusions using evidence, the question, data collection models, and visualizations for methods, analysis process, and acknowledging limitations, potential evidence that supports biases, and tradeoffs (e.g., data conclusions. representation, compression, or storage formats).
- DA.4.a.m.16
- DA.4.a.m.26
- DA.4.b.m.16
- DA.4.b.m.26
- DA.4.c.m.16
- DA.4.c.m.26
- CSS.1.a.m.16
- CSS.1.a.m.26
- CSS.1.a.m.36
- CSS.1.b.m.16
- CSS.1.b.m.26
- CSS.1.c.m.16
- CSS.2.a.m.16
- CSS.2.a.m.26
- CSS.2.b.m.16
- CSS.2.b.m.36
- CSS.2.b.m.46
Describe safe practices for accessing systems, including recognizing secure sites, managing passwords, and avoiding risky downloads or pop-ups. Analyze how widely used technology helps individuals solve problems, (education, communication) while also creating challenges (cyberbullying, privacy issues, screen time).
- CSS.3.a.m.16
- CSS.3.a.m.26
- CSS.3.b.m.16
- CSS.3.b.m.26
- CSS.4.b.m.16
- CSS.4.b.m.26
- FUT.1.a.m.16
- FUT.1.b.m.16
- FUT.1.c.m.16
- FUT.1.d.m.16
- FUT.2.a.m.16
- FUT.2.a.m.26
- FUT.2.b.m.16
- FUT.2.b.m.26
- FUT.2.b.m.36
- FUT.2.c.m.16
- FUT.2.d.m.16
- FUT.2.e.m.16
- FUT.2.e.m.26
- FUT.2.f.m.16
- FUT.2.f.m.26
- FUT.3.a.m.16
- FUT.3.a.m.26
- FUT.3.b.m.16
- FUT.3.b.m.26