Most people agree on one thing: Children should be safe online.

That’s not really the issue. The issue is how we get there, and whether we’re quietly moving toward something that replaces parents instead of helping them.

HB5511 sounds like it’s about safety. But the more you look at it, the more it feels like it’s shifting responsibility away from families and into the systems that run our phones and apps. And that should make people stop and think a little.

1. HB5511 and the Shift Away From Parents

On paper, the bill says platforms should better protect kids. But the way it does that is by having systems figure out who is a minor and then automatically applying restrictions everywhere. So instead of a parent deciding what’s right for their kid, you end up with:

• phones trying to determine a child’s age

• apps being told how to behave based on that

• platforms enforcing rules automatically

And once you step back from the technical language, what that really means is simple: decisions that used to happen in the home start happening inside the device itself That’s a big shift. And it doesn’t get talked about enough.

2. The Real Problem Isn’t Missing Rules: It’s Missing Awareness

A lot of people assume we don’t have enough protections right now. But that’s not really true. The bigger issue is much simpler: most parents don’t know what’s already available to them

There are already tools built into phones, apps, and home internet systems. They’re just not clearly explained. And they’re definitely not widely talked about. So instead of fixing that gap, we’re talking about building a whole new system on top of everything else.

3. What Actually Works Today (Tools Parents Can Use Right Now)

If you strip away the jargon, there are already a lot of practical tools families can use today.

The problem isn’t that they don’t exist; it’s that most people haven’t been shown how to use them.

a) Device Controls (Built into Phones and Tablets)

Most devices already let parents:

• block or limit apps

• approve downloads before they happen

• set screen time limits

• filter certain types of content

This is basically the “front door” control. If it’s set up right, kids don’t even get full access in the first place.

b) Child Accounts (Safer Profiles for Kids)

Most platforms offer kid-specific accounts.

These usually:

• limit who kids can talk to

• filter what shows up in feeds

• block certain types of content automatically

The issue is simple: a lot of kids are still using full adult accounts with no restrictions at all.

c) App and Social Media Settings

Apps like YouTube, TikTok, and Instagram all have safety settings.

They can:

• limit what shows up in recommendations

• restrict messaging

• enable “restricted” or teen-safe modes

They help, but only if someone actually turns them on.

d) Home Internet Filters

This one gets overlooked a lot.

At home, you can set up Wi-Fi rules that:

• block entire categories of websites

• apply across every device in the house

• don’t depend on individual apps

It’s one of the strongest protections most people already have access to.

e) App Installation Controls

Parents can also require approval before new apps are installed.

That means:

• no surprise downloads

• no hidden apps

• more visibility into what’s being added

It’s simple, but powerful.

f) Screen Time Limits

These tools help manage:

• how long kids are on devices

• when devices can’t be used

• overall daily exposure

Not about content, just balance.

g) The Part That Really Matters

None of these tools matter much without one thing: parents actually knowing they exist and feeling comfortable using them That’s the missing piece in all of this.

So what does all of this add up to?

It adds up to something important: We already have a full set of tools to protect kids.

They’re not perfect. But they’re real, and they’re already here.

The problem isn’t absence of ways to protect children on the internet. It’s awareness of their existence.

4. Where We Could Actually Improve Things

Instead of building new systems, there are a lot of simpler fixes that would actually help:

• make parental controls easier to find and understand

• make settings more consistent across apps

• improve default protections for kids

• give parents clearer instructions in plain language

• actually teach people these tools exist

None of that requires rewriting how the internet works. It just requires making what already exists easier to use.

5. What Illinois Can Do Right Now (Without HB5511)

If the goal is truly to protect kids, there’s something much more immediate we can do. Start by helping parents, not replacing them.

a) A Simple State Website for Parents

Illinois could create a straightforward site called something like:

“How to Protect Kids Online”

And it should just be practical:

• step-by-step guides for phones, tablets, computers, consoles

• simple instructions (no tech language)

• short videos for people who don’t want to read manuals

• “start here” guides so nobody feels lost

The goal isn’t to overwhelm people. It’s to actually help them.

b) Printed Guides for Schools and Communities

Not every parent is going to go online and search for this.

So the information should also go out physically:

• sent home with students

• handed out at PTA meetings

• available in libraries and community centers

• shared through civic groups

If it matters, it should be easy to get.

c) Fund Education Instead of New Systems

If lawmakers are serious about this, then the money should go toward:

• awareness campaigns

• parent education

• simple instruction materials

Because the fastest way to improve safety right now isn’t more control systems. It’s making sure people know what they can already do.

6. A Simpler Alternative: RAVE

There’s another way to handle this problem without changing how the internet works or adding a lot of new rules for every app and device. It’s called RAVE (Responsible Age Verification for Entry). The idea is simple.

This is not an afterthought proposal developed in response to current legislation. RAVE was developed last fall and presented as a comprehensive concept package to leading Illinois lawmakers well before the current debate.

a) How it works

Instead of every website or app trying to figure out your age, each person would have an AVN number (Age Verification Number).

That number would:
• confirm if someone is an adult or a minor
• be used only for age checks
• not share personal details like name, address, or browsing history

So when you sign up for something online, the system only gets one answer: “Is this person old enough: yes or no?” That’s it.

b) Using what already exists

RAVE doesn’t try to build a whole new identity system. The Illinois Secretary of State already has:

· verified birth records for adults

· age information for most residents

So instead of asking people to keep proving their age over and over again to different companies, the state would handle it once. No new databases spread across the internet. No new systems for every app or platform.

This approach relies on existing public infrastructure, not a newly created system introduced in reaction to current legislative proposals.

c) How this compares to HB5511

HB5511 takes a much more complicated approach. It would require:

· phones and computers to identify whether users are minors

· app stores and platforms to enforce different rules for kids

· companies to constantly update and monitor compliance

· penalties if they don’t follow the rules correctly

In simple terms, it turns child safety into a system that every tech company has to constantly manage and prove they are following. That means more rules, more tracking, and more systems working behind the scenes.

RAVE, by contrast, was designed from the beginning as a simpler alternative to this kind of layered compliance structure.

d) The simpler approach

RAVE works differently. Instead of building rules into every part of the internet, it:

· checks age once

· uses a simple verification number

· doesn’t require apps or websites to collect extra personal data

· avoids turning every platform into a compliance system

It was designed specifically to avoid expanding system-wide enforcement across the internet.

e) The real choice

At the center of all of this is a simple question: Who should handle age verification online? We either:

· trust the Illinois Secretary of State, which already verifies identity and age today or

· require Apple, Google, Microsoft, and thousands of platforms to manage it across the entire internet

One approach keeps it simple and centralized. The other spreads responsibility across every digital system we use. This framing was part of the original RAVE concept package shared with lawmakers, not something added after the fact.

f) Why this matters

The more complicated a system becomes, the more problems it creates:

· more places where data is stored

· more rules for companies to follow

· more chances for confusion or failure

RAVE tries to avoid that by keeping things simple:

· almost all adults in Illinois are already age verified with the Secretary of State

· uses a basic signal (token)

· doesn’t try to rebuild the internet to solve the problem

It was designed specifically to minimize system expansion while still addressing the policy goal.

g) Bottom line

HB5511 tries to solve a real issue, but does it by adding a lot of new systems and enforcement rules across the internet. RAVE takes a simpler approach: one check, one number, and no need to redesign how the internet works just to keep kids safe.

RAVE was not created after the fact, it was developed in advance as an alternative approach to exactly this kind of system expansion.

7. The Real Choice in Front of Us

This debate isn’t really complicated when you strip it down. There are two paths:

HB5511 approach

• build new identity and enforcement systems

• shift control into devices and platforms

• expand centralized data systems

Simple approach

• help parents use what already exists

• improve awareness and education

• strengthen family-level control

This isn’t about intent. Everyone wants kids to be safe. It’s about whether we solve it by adding layers of system control or by helping families actually use the tools they already have.

8. Final Thought

Nobody is saying do nothing. That’s not the argument. The argument is this: We don’t need to rebuild the internet to protect kids.

HB5511 tries to solve a real issue, but does it by adding a lot of new systems and enforcement rules across the internet. RAVE takes a simpler approach: one check, one number, and no need to redesign how the internet works just to keep kids safe.

RAVE was not created after the fact, it was developed in advance as an alternative approach to exactly this kind of system expansion.

HB5511also moved very quickly, from introduction to passage in the Illinois House in a mere 74 days. For legislation with this level of scope and long-term impact, that is simply too fast.

When something affects how identity, access, and online safety could be handled across the internet, it deserves more time, not less. It deserves real public discussion, expert testimony, and meaningful hearings where concerns can be fully examined, not rushed through a compressed timeline.

Pausing it for that kind of review is not unreasonable. In fact, it’s the bare minimum you would expect for legislation of this importance. Is that really too much to ask for?

(Disclaimer: RAVE is currently only a proposal. No bill has yet been introduced.)