How Networks Actually Work (and Why They Matter for Assistive Tech)

Why I Finally Cared About Networks

When I first started building tools for people with disabilities, I could not have cared less about the difference between a LAN and a WAN. I just wanted the screen reader to work. But then a client's smart cane stopped navigating, and I spent an hour blaming the app before realizing the office router had died. That's when I got serious about this stuff.

Assistive tech is more dependent on connectivity than most people realize. A communication app that turns text into speech for a kid with autism—that's not just software. It's a cloud service, a network path, and a device all talking to each other. If any layer fails, the whole thing falls apart.

The Internet: The Physical Plumbing

The internet is the actual infrastructure—the cables under the ocean, the routers in basements, the servers in data centers. It started as ARPANET in 1969, a military project that nobody thought would become anything. Then NSFNET in the 1980s connected universities, and by the mid-90s it was commercial. Now it's just... everywhere.

For assistive tech, this global reach is a double-edged sword. On one hand, a user in a remote village can access the same speech synthesis service as someone in New York. On the other, if the cables don't reach you, you're out of luck. I remember reading about a telehealth pilot in rural India that had to switch to satellite because the fiber just didn't exist.

Internet vs. Internet: A Spelling Lesson That Actually Matters

Here's a weird one. In English, 'internet' with a lowercase i means any network of connected computers—even your home LAN. 'Internet' with a capital I is the global network. In 2016, the Associated Press decided to lowercase it because it had become as common as 'telephone.' That's fine, but it makes things confusing.

In Chinese, there's an even messier situation. The official term is '因特网' (Yīntèwǎng), but everyone says '互联网' (Hùliánwǎng), which means 'interconnected network.' When I'm debugging with a Chinese manufacturer, this confusion has caused more than one wasted afternoon.

The Web: An App That Runs on the Internet

Tim Berners-Lee invented the World Wide Web in 1989 at CERN. It's a system of documents linked by URLs and served over HTTP. The web is not the internet—it's an application that uses the internet. When you open a browser, you're on the web. When you send an email, you're using a different internet service.

This distinction is crucial for developers. Building an accessible web app means understanding HTML, HTTP, and WCAG. A page with poor semantic markup can be impossible for a screen reader to parse, no matter how fast the connection is. I once saw a beautifully designed website that was completely unusable because the buttons were just divs with no keyboard support.

LAN, WAN, and the In-Between

Networks are also classified by their physical size. A LAN is a Local Area Network—your house or office. A MAN covers a city, a WAN spans countries. For assistive tech, LANs are where most smart home devices live. My friend uses a voice-controlled light system because he has limited hand mobility. That system runs entirely on his home LAN. If the router goes down, he's fumbling in the dark.

The scale matters for troubleshooting. If a smart wheelchair's remote stops working, the problem is probably in the LAN, not the internet. Similarly, a telehealth appointment over spotty Wi-Fi might be better on a wired Ethernet connection.

Ethernet and Wi-Fi: The Last Mile

Ethernet is the wired technology for LANs. It's reliable and fast, but it requires cables. Wi-Fi is wireless, using radio waves. Both are used in assistive tech. For a stationary device like a speech-generating communication board, Ethernet might be the better choice—it's less prone to interference. For a portable device like smart glasses that narrate the environment, Wi-Fi is essential.

I once helped a school set up a classroom for students with visual impairments. We used Ethernet for the desktop readers because the Wi-Fi was congested. It made a huge difference in response time. But for the students' tablets, we had to invest in better access points.

Practical Takeaways (Not a Conclusion)

So what does this mean for you? Here are a few things I've learned the hard way:

• If a web-based assistive tool is slow, check your Wi-Fi signal or try Ethernet. A wired connection can be a lifesaver.
• Test your assistive app over different network types—LAN, WAN, and with varying bandwidth. What works on fiber might choke on 3G.
• Remember that the web is just one application. VoIP calls, video conferencing, and real-time data have different requirements.
• Don't ignore the physical layer. A faulty cable can bring down an entire network, taking your assistive devices with it. I've seen it happen.

Networks are invisible, but they're the backbone of modern assistive tech. The more you understand these layers, the better you can support the people who rely on them. And honestly, it's kind of cool to know why your Wi-Fi is slow.