How I try to make Live Off The Grid usable for everyone, including people with disabilities, what I aim for, where it still falls short, and how to reach me if something on the site is hard to use.

I want everyone who visits Live Off The Grid, whatever device they use and whatever abilities they have, to be able to read the articles, browse the archives, and sign up for the newsletter without running into unnecessary barriers. This page explains what I actually do to support that, where I still fall short, and how to reach me if something isn't working for you.

My Commitment

I'm one person running this site as a resource for people interested in off-grid living, self-sufficiency, and simpler ways of doing things. There's no team, no agency, no dedicated accessibility department. Just me, writing articles and maintaining a website in whatever hours I can find. That said, accessibility matters to me, not as a checkbox but because I've had readers tell me they use screen readers, or rely on keyboard navigation, or need larger text to read comfortably, and I want this site to work for them too.

My goal is simple: nobody should be locked out of the information here because of how the site is built. I take that seriously, and I keep working at it even when there's no one checking my homework.

The Standard I Aim For

I use the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, as my target. In plain terms, this is a widely recognized set of guidelines for making websites usable by people with a range of disabilities, including visual, hearing, motor, and cognitive differences. Level AA is generally considered the practical, achievable standard that most well-built websites aim for.

I want to be upfront: this site is not formally certified as meeting WCAG 2.1 AA, and I don't want to claim otherwise. Accessibility isn't a box you check once and forget. It's an ongoing effort, especially on a site like this that's regularly updated with new articles, images, and the occasional redesign. What I can tell you honestly is that WCAG AA is the bar I measure myself against, and I'm working toward it steadily rather than treating it as finished.

What I've Actually Done

Here are the concrete things built into the site to support accessibility:

• Semantic HTML structure: Pages use proper heading levels, lists, and landmark structure so that screen readers and other assistive tools can understand the layout and let you jump to the section you want, rather than reading everything top to bottom as one long block.
• Descriptive alt text: Meaningful images, like photos of solar setups, garden layouts, or diagrams, have alt text describing what's shown. Purely decorative images are marked so assistive technology can skip over them without cluttering your listening or reading experience.
• Color contrast: Text and background colors are chosen to meet sufficient contrast ratios, so reading isn't a strain even in bright light or for readers with low vision.
• Resizable, reflowing text: You can zoom in or increase your browser's text size, and the layout adjusts rather than breaking, overlapping, or requiring you to scroll sideways to read a sentence.
• Responsive design: The site is built to work on phones, tablets, and desktops, since I know a lot of readers browse from wherever they happen to be, not just a desk.
• Keyboard navigation: You should be able to get through menus, links, and forms using just a keyboard, no mouse required. This matters for people with motor disabilities and anyone who simply prefers keyboard navigation.
• Visible focus indicators: When you tab through the site, there's a visible outline or highlight showing where you are, so you don't lose track of your place.
• Labeled forms: Fields like the newsletter signup are labeled clearly, so screen readers can tell you what information is expected in each box, not just leave you guessing.
• Plain-language writing: I try to write clearly and directly, avoiding unnecessary jargon, long convoluted sentences, or fluff. This helps readers with cognitive disabilities, non-native English speakers, and honestly, everyone who's just trying to get useful information quickly.
• Not relying on color alone: Where I use color to indicate something, like a warning or a highlighted tip, I also use text, icons, or labels, so the meaning isn't lost on anyone who can't distinguish certain colors.

Assistive Technologies and Browsers I Aim to Support

I build and test with the following in mind:

• Screen readers, including common tools people use to have web content read aloud or converted to braille.
• Browser and OS zoom features, for readers who need larger text or images.
• Browser reader modes, which strip away extra design elements and present just the article text in a clean, simplified view.
• Recent versions of major browsers like Chrome, Firefox, Safari, and Edge. I don't have the resources to test against very old or discontinued browser versions, so if you're using something several years out of date, you may run into more rough edges.

I don't have access to every assistive technology or every combination of device and software out there, so my testing is necessarily limited to what's most common. If something doesn't work well with your particular setup, I want to know about it.

Known Limitations

I'd rather be honest with you than pretend everything is perfect. Some areas I know need work:

• Older blog posts, some going back several years, may have images with missing or thin alt text, since my standards for writing alt text have improved over time and I haven't gone back to fix every old post yet.
• Some embedded third-party content, like videos or maps from other services, may not be fully accessible, since I don't control how those tools are built.
• Certain older PDFs or downloadable guides linked from articles may not be fully screen-reader friendly. I'm gradually replacing these with accessible web pages where it makes sense.
• Some interactive elements added early on in the site's life may not have the same level of keyboard support as newer features. I'm working through these as I update pages.

None of this is an excuse, just a realistic picture of where things stand. I go back through old content periodically to fix issues as I find them, but with years of articles on the site, it's an ongoing project rather than something I can finish in one pass.

Third-Party Content and Links

Live Off The Grid links to other websites, and sometimes embeds content from outside services, like videos, social posts, or maps. I have no control over how those third parties build their sites or how accessible they are. I try to choose reputable services and link to good resources, but I can't guarantee that every external site meets the same standards I aim for here. If you run into a problem with a linked site, that's worth raising with the site itself, though I'm happy to hear about it too, especially if it affects how you use my content.

Requesting Information in a Different Format

If there's something on the site you can't access, whether that's an article, an image description, a downloadable guide, or anything else, reach out and I'll do what I can to get you that information in a way that works for you. That might mean describing an image in more detail over email, sending you plain text instead of a PDF, or finding another workaround. I can't promise instant results, but I will make a genuine effort.

Reporting an Accessibility Problem

If something on the site isn't working for you, please tell me. I mean that sincerely, not as a formality. I read every message that comes in, and accessibility reports get real attention because they point to something concrete I can actually fix.

When you report a problem, it helps a lot if you can include:

• The specific page or article where you ran into the issue (a link or the page title works fine).
• What browser and device you're using, and if applicable, what assistive technology (like a specific screen reader) you were using at the time.
• What happened, and what you expected to happen instead. Even a rough description is useful, you don't need technical language.

I'll do my best to understand the issue, fix it if I can, and in the meantime, get you the information you need another way. I can't promise every fix will happen overnight, since this is a one-person operation, but I won't ignore it either.

How to Reach Me

You can email me directly at mike@liveoffthegrid.com, or use the /contact page on the site. Either way works, and either way, a real person (me) will read it and respond.

Keeping This Statement Current

This site changes over time, new articles get published, old ones get updated, and occasionally I redesign parts of the layout. As that happens, I revisit this statement to make sure it still reflects reality rather than describing a version of the site that no longer exists. If you notice something here that seems out of date compared to what you're actually experiencing on the site, let me know that too.

This accessibility approach is reviewed periodically as the site grows and changes, rather than on a fixed schedule.

How I test and review accessibility

Accessibility on this site is checked in a few practical ways rather than treated as a one-time box to tick. New pages and templates are built with semantic structure from the start, keyboard navigation is tried by tabbing through pages without a mouse, and color choices are checked against contrast guidelines before they ship. Automated tools that flag common problems, such as missing labels, low contrast, or images without alt text, are run against the site from time to time, and I read the pages the way a screen reader would encounter them to catch anything that reads out of order or without context. Automated tools only catch part of the picture, so real judgment and manual checking matter just as much, and I keep learning as standards and tools improve.

Accessibility of the newsletter and forms

The parts of the site where you actually do something, the contact form and the newsletter signup, get particular attention, because a form that is hard to use is a real barrier rather than a cosmetic one. Form fields have visible labels tied to their inputs, error messages aim to be clear and specific rather than vague, and you should be able to complete and submit a form using only a keyboard. The email newsletter is written in plain language and includes a clear one-click unsubscribe in every message. If you run into any trouble signing up, reaching me, or reading a message, that is exactly the kind of problem I want to hear about, and I will help you get the information another way while I fix it.