Teaching Available Isn't Always Usable in Grade 7: Oklahoma Standard 7.IC.CU.02

Teaching accessible technology design in grade 7 does not have to be complicated. Picture an accessibility engineer identifying and fixing barriers that prevent people with disabilities from using software. That kind of thinking is exactly what Oklahoma's grade 7 computer science standard 7.IC.CU.02 asks students to practice — and it is very teachable with the right materials. This post walks through what the standard means, the misconceptions students bring to it, and discussion starters you can use tomorrow, whether you teach in a classroom or at your kitchen table.

What Does Standard 7.IC.CU.02 Actually Ask?

Identify real-world problems in relation to the distribution of computing resources in society. — Oklahoma Academic Standards for Computer Science (February 2023)

In plain language: Oklahoma's standard asks seventh graders to identify real-world problems in relation to the distribution of computing resources in society.

In student-friendly terms, the learning target is: "I can identify real-world problems in relation to the distribution of computing resources in society."

What Students Should Be Able to Do

• I can clearly identify a genuine barrier preventing a specific group from using a resource.
• I can clearly name a specific real-world problem caused by this barrier.
• I can clearly distinguish between a resource being technically available and genuinely usable.
• I can thoughtfully connect the problem to its broader effects on inclusion in society.

Along the way, students pick up the working vocabulary of the topic: accessibility, barrier, inclusive, usable, narrator, caption, localization, interface, obstacle, inclusion, adapt, equitable.

Accessible Technology Design: Misconceptions to Watch For

These are the wrong turns students reliably take with this standard — knowing them ahead of time is half the lesson plan. Each correction strategy below comes straight from the unit's teacher guide (the paragraph and activity references point into the unit itself).

1. "A resource being technically available online means it's automatically usable by everyone."

Use paragraph 1's key point — genuine access means a resource is actually usable, not just technically available.

2. "Access barriers only affect people with visible disabilities."

Reference paragraphs 4-5 — language barriers and age-related unfamiliarity with technology are also genuine access barriers.

3. "Access barriers will naturally disappear over time without any deliberate effort."

Point to paragraph 8 — barriers rarely disappear without genuine, intentional design effort from the people creating resources.

4. "Identifying an access problem just means noticing a resource exists, without considering who can actually use it."

Clarify from paragraph 7 — identifying a real-world problem requires distinguishing technical availability from genuine usability.

Discussion Starters You Can Use Tomorrow

• Why do you think some apps and websites add accessibility features while others don't?
• What's an example of an accessibility feature you'd want to see added to a technology you use?
• Why might an accessibility engineer test a website using a screen reader before it's released?

Bringing It Home

This topic is a natural one for families. One ten-minute activity to try: Together, identify one accessibility feature you've noticed (captions, larger text, voice control) and discuss who that feature genuinely helps and why.

Where This Leads

Students who can identify real-world problems in relation to the distribution of computing resources in society are building skills used every day in accessibility engineering, localization, inclusive design, UX design, and computer science education.

See the Unit in Action

Get the Complete 7.IC.CU.02 Unit

I built a complete, no-prep unit for this standard — Identifying Computing Access Problems for Diverse Users — covering 3-4 days of instruction across 37 pages:

• Teacher guide — day-by-day pacing, misconceptions to watch for, discussion questions, differentiation for support / ELL / extension, and a 4-point rubric
• Student learning target page — a kid-friendly "I can" statement with success criteria
• Full content lesson with 3 embedded "Check Your Understanding" checkpoints
• 12-question assessment (6 multiple choice, 4 true/false, 2 short answer) with a complete answer key, explanations, and exemplar responses
• Group activity — "Identify the Access Barrier" (45-50 minutes)
• Individual activity — "Research a Real Accessibility Problem" (40-50 minutes)
• Crossword and word search built from all 12 vocabulary terms (with answer keys)
• Family connection letter — a plain-language page for parents, with dinner-table questions and a 10-minute home activity
• Certificate of achievement — ready to sign and send home
• Accessibility Practice and Reference Materials (separate printable, 1 page)

Get Available Isn't Always Usable on Teachers Pay Teachers →

Every Sooner Standards resource is built directly from the official Oklahoma Academic Standards for Computer Science (February 2023) — standard text verified, never paraphrased from memory.