The short version
- I want my site, tools, and forms to work for as many people as possible, including people who use a keyboard, a screen reader, or other assistive technology.
- I'm one person, and I'm still improving things. I can't promise every page works perfectly for everyone.
- If something is hard to use, tell me. I'll fix it where I can, or give you what you need another way.
- You never have to give me a password or a card number to report a problem.
1. My commitment
A website that people can't use isn't doing its job. I want to be able to say that anyone who comes to digitalbusinessmechanic.com can find out what I do, run a free tool, ask a question, and pay for something without getting stuck.
I'm a one-person business, so I'll be honest about where I stand. I work to make things accessible, and I keep improving them. This statement describes my current practices. It's not a certification, and it isn't a claim that every page meets every standard.
2. The standard I'm aiming for
My target is the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. These are the widely used international guidelines for making web content accessible. They're a target I'm working toward. I haven't had the site formally audited against them, so I don't claim that the site fully conforms.
3. What I do
Where practical, I build and maintain my pages with these things in mind:
- Clear structure. Pages use real headings, lists, and landmarks so assistive technology can move around them, and so people can skim.
- Keyboard use. Links, buttons, menus, and form controls should work without a mouse, with a visible focus outline that shows where you are.
- Readable text and contrast. Text is meant to be large enough to read, with enough contrast against its background. You can zoom in without the layout breaking.
- Labels and instructions. Form fields have visible labels and plain-language instructions, and error messages say what went wrong and how to fix it.
- Text alternatives. Meaningful images have alternative text. Decorative images are meant to be skipped.
- Responsive layouts. Pages are designed to work on phones, tablets, and desktops.
- Reduced motion. Animations are designed to turn off or tone down when your device is set to reduce motion.
- Plain language. I try to write the way a person talks, because clear writing helps everyone, including people who read in a second language or use screen readers.
- A human option. My pages don't force you to rely on an automated answer. You can always email or call me.
4. How I check
I check my work with a mix of methods:
- Automated accessibility checks, such as Lighthouse, on key pages
- Keyboard-only walkthroughs of important paths, like the contact form
- Reviewing page structure, labels, and contrast as I build
- Fixing problems that people report to me
Automated checks are useful, but they catch only a portion of real-world problems. A good score is a signal, not proof that every person and every assistive technology will have the same experience on every page. I don't currently claim thorough testing with every screen reader or assistive device.
5. Forms and tools
My forms and free tools are the places where accessibility matters most, since they're how people reach me. I aim to make sure each field has a label, each button can be used by keyboard, and results are written in text that can be read aloud. If a tool doesn't work for you, email me and I'll help you get the same result another way, for example by running the check for you and sending it by email.
Please don't send passwords, card numbers, or other highly sensitive information when you tell me about a problem. I don't need them.
6. Video, audio, and Garage TV
Garage TV episodes and other audio or video content are meant to come with a text transcript so you can read instead of watch or listen. Some short clips are visual-only with the sound off, and those are meant to have the same information available in text. Narration on some episodes is AI-assisted, and I say so on the page.
If an episode doesn't have a transcript or text version that you need, tell me and I'll provide one.
7. Documents and downloads
Guides, reports, and downloads may be in formats like PDF or plain text. I try to make them readable by screen readers and easy to navigate. If a document is hard for you to read, I'll send it in another format that works better, such as plain text or a simpler document.
8. Known limits
I'd rather tell you where things are weak than claim they're perfect. Some current limits:
- Third-party tools. Checkout, scheduling, chat, embedded video, and similar services are run by other companies. Their accessibility is their responsibility and may differ from mine. I choose providers carefully, but I can't control what they build.
- Demos and older pages. My portfolio contains demos and older experiments that may not meet the same standard as the main site. Each one is its own site, and I'm improving them over time.
- Interactive and visual features. Animations and visual effects may not work smoothly with every assistive technology. If something gets in your way, tell me.
- Older content. Some older pages and posts may have missing alternative text or less consistent structure.
If you find a problem that isn't on this list, I want to hear about it.
9. If something doesn't work for you
Email [email protected] or call (509) 868-9784. It helps if you can tell me:
- The page address or the name of the tool or document
- What you were trying to do
- What happened instead
- The device, browser, or assistive technology you were using, if you know it and you're comfortable sharing it
You don't need to explain a disability or share any health information. Just describe the barrier.
10. What I'll do about it
I'll make a reasonable effort to:
- Reply to your message within a few business days
- Give you the information or service you need through another route, such as a plain-text version, a different document format, a phone walkthrough, or doing the task with you by phone or email
- Fix the underlying problem where I can, and tell you if I can't
Your report helps me improve the site for everyone who comes after you.
11. Accessibility in client work
When I build pages or tools for a customer, I build to a practical accessibility baseline: clear structure, keyboard use, labels, readable contrast, text alternatives, and responsive layouts. That's part of good work, and I don't charge extra for it.
A formal accessibility audit, a certification, or a conformance report is a different job. If you need one, ask me, and we'll write it up as a separate scope. I'll be honest about what I can do and what needs a specialist.
Legal compliance depends on your industry, your location, and your customers. I can't give you legal advice on that.
12. Public-sector and subcontract work
If you work with a government agency, you may need to meet requirements like Section 508. I can build and document work to a target you give me, and I can provide accessible deliverables on request, as part of a written scope. I don't currently publish a formal Accessibility Conformance Report for my own site, and I won't claim a certification I don't have.
13. AI and automation
I use AI to help with explanations, drafts, and routing. It can be wrong, and it isn't always accessible to every person. That's why I have human handoff paths: you can always reach me directly.
14. Third-party services
Payment processors, scheduling tools, social platforms, video hosts, and other outside services have their own accessibility features and their own limits. I can't guarantee how they behave. If one of them blocks you, tell me, and I'll help you get what you need another way.
15. What this statement is and isn't
This statement describes my current practices and my plans to improve. It is not a certification, and it is not a legal statement that my site meets every accessibility standard. It also doesn't promise that every third-party service will be accessible.
16. Contact
Digital Business Mechanic Jamie Maniatis, Spokane, Washington Email: [email protected] Phone: (509) 868-9784
This is a plain-language statement, not legal advice.