You can see in the photo our little pantry was quickly thrown up. Now we are facing winter weather in Wisconsin. We realized we needed a better structure. So we bought a small 22 sq foot shed. We posted that this was happening on social media and looking for assistance to install it as both my wife and I are disabled.
Comments closedTimes are tough, but we have a little extra. Instead of shaming people for needing help, we are sharing what we can. I have been a Buddhist for over a decade. I’ve read all the major religious texts as well as the major philosophy and ethics books as part of getting my degree in philosophy. My wife is a deacon at her Episcopal church. One thing we agree upon is that all humans deserve care, love, support, the right to food, clothing, shelter, and healthcare. Actually, we agree on a lot, but most of it is irrelevant to this post.
‘Truly I tell you, whatever you did for one of the least of these brothers and sisters of mine, you did for me.’ – Matthew 25(40)
If you have the means to help your local community, I encourage you to do so. If you can’t provide a pantry like ours, find somewhere to donate time or money. Because our budget for this is coming out of our pockets, we have limits. If you’d like to help us support our community, please visit our page about the pantry and donate.
Comments closedOk, the title is clickbait, but what isn’t these days.
Today Americans from the United States of America celebrate our Independence Day from British rule. This annual celebration usually includes trips to the lake or beach. People often grill outside with friends and family. The day wraps up with fireworks. Growing up, the Fourth of July was one of the greatest parties of the year.
Comments closedHopefully those of you working towards EAA are breathing a little easier today. While some of you were pushing last minute updates, I attended my local Pride celebration.
Well organized and attended, it reminded me why I do this work. People from 1-99+. People with visible disabilities. People with disabilities only visible because they made it so by wearing a device to control the disability (hearings aids off, headphones, walkers instead of canes). This wasn’t a celebration of LGBTQ+, this was a celebration of people being people.
1 CommentThis is being posted Monday June 23rd, 2025. On Friday, the 28th, EAA goes into effect. If you haven’t completed your efforts to be completely accessible, I have one piece of advice:
Don’t stop now. Keep working on it.
2 CommentsI’ve been in the tech industry for over two decades. I’ve worked with Java, PHP, Ruby, JavaScript. I have really strong HTML and CSS skills. I know accessibility and how to manage an accessibility program. I talk weekly with executives and attorneys about their legal risks under ADA, EAA, Section 508, and other standards. I guide them on how to make their program robust to mitigate future legal action. And I’m wrong. Often. And I’m willing to admit it every time.
You will make a mistake. Hopefully it is small. But no matter what, it is OK to make mistakes. What matters is how you respond to your mistake. Take ownership. Review your thinking to see what you missed. If you can’t figure it out easily, ask for help.
The number of things I don’t know about in the accessibility space is tremendous.
– Nat Tarnoff
Sometimes the only way to learn something is to fail at it first, or for the 10,000 time. If you fail, own it and work it out. Feel free to fail.
I’m highly trained. I’m highly observant. I think outside the box. Throw whatever corps-speak you want my way, I don’t care. I learn something every day or I try to. The number of things I don’t know about in the accessibility space is tremendous. I’m not a writer, so I’m still learning about content creation. I’m trying to expand my knowledge and I’m sure I’ll never understand it all. And this is good. It drives me. It gives me space to fail. So when I do fail, I can learn, fix, and grow. And the more work you do, the less you will fail in that field.
If someone claims to be an expert and knows all the the things, make a tinfoil hat. This person may be highly skilled, but they have a superiority issue and will be hard to work with. They have hardened opinions on techniques. Even if the best advice has moved on, they stick to the old approaches. You have valid questions and ideas. Changing the “expert’s” mind will be challenging if your ideas and feedback challenges their idea of perfect. They will be less willing to look at new research. They’ll take offense to your opinion and suggestions.
This isn’t mine, I just learned it Thursday night and love it. Thank Kai Wong for it. The first thing is not call someone out. You call them in. If you see someone make a mistake, take them to the side and let them know. Give them the chance to fix it.
But there are some places we don’t get to call them in. Some platforms have a code of conduct that only allows direct, private messages if you get permission publicly first. In those cases, you may have to call them out.
Like I was the other day. I made a mistake and left part of my thinking out of a response. Someone else in the community asked for clarification. This made me revisit the comment. Turns out they were right. I made a mistake. I admitted it, corrected my meaning and thanked them for challenging me.
Keep learning. Challenge the experts. Your input and feedback is important to grow this community. It enhances our understanding of standards. It helps us know where to create new standards and when to throw others out.
Have comments or thoughts on this post, let’s talk about it on LinkedIn or BlueSky.
1 CommentI have a bad habit of saying, “this is easy” or simple. It’ll only take a moment. Like I said, a bad habit that I try hard to break. Why? Just because it is easy to me doesn’t mean it is to you. I was about to start this off with, “This is pretty much straight forward and don’t reference anything requiring senses.”
And I realize, that this isn’t that simple. I’ve been doing this for over two decades as of this writing. Today may be your first day. English may not be your first language. Maybe you can’t relate to the idea of senses.
All animals on the planet have the ability to experience their environment. They do this with their senses. Senses are built in detectors to assess our environment. In the accessibility industry, we create solutions. These solutions are for people who may have malfunctioning senses.
When we are little, we are taught about our 5 major senses: Sight, Taste, Touch, Hearing, and Scent. But we also have senses that can detect electrical stimuli, heat, cold, our awareness in space. If you tell someone to find the green button, you’ve violated the success criteria.
First, we make sure that everything has a proper accessible name. Next, we make sure it unique to the page we are on. It’s super easy to say, “click the submit button” in your instructions if there is only one submit button.
Of course we want to keep the page as simple as possible, so we probably won’t use instructions like that. We wouldn’t say, “click the triangle.” Instead, we should let the construction of the page tell us what to do next.
This looks like first coding the HTML so that if nothing else loads everything is presented and understandable. You can’t position items in a visual order or paint them pretty colors. You also can’t make them do magic. Therefore, we need to rely on the content itself. If your content can’t stand on it’s own, rewrite it.
With the content corrected, we can build out the site. Paint it, position it, then test it. Does it still make senses in the reading order? Focus order?
Lastly, teach the team. Make it an internal standard. Put in monitoring just in case someone makes a mistake.
Want to discuss this more? Come say hi on BlueSky and LinkedIn.
Comments closedWhenever I come across a a violation of 1.3.1, I have a primal need to look deeper. I investigate because I believe if something falls under this success criterion, it is most likely improperly classified. It is extremely important that we understand the relevant context, information and relationships of content. Frequently, I observe that this particular success criterion is misused. It often serves as a catch-all for “Where does this go?”
Per WCAG, 1.3.1 Info and Relationships is:
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
Cool. We used the original words to define it. I didn’t like third grade English when I was in third grade.
Let’s look at the intent:
The intent of this Success Criterion is to ensure that information and relationships that are implied by visual or auditory formatting are preserved when the presentation format changes. For example, the presentation format changes when the content is read by a screen reader or when a user style sheet is substituted for the style sheet provided by the author.
Now this is better. We’re given a breakdown and example. The intent is to ensure that what is visually indicated as structural, explanatory, and informational is available to everyone. This includes people using different presentation formats.
When talking about structure, it is crucial to distinguish between visual structure and code structure. We need to consider both.
When we look at our mock-up of a page, we want to absorb it visually. Is the most important item in the page grabbing the eye? Does the way it is designed lead you to the next thing you want to say or a primary CTA
(Call to Action)? Take it all in, then we start deciding what HTML elements best represent all those pieces of the page. We begin to think of how we order them. Should it be in a landmark like header, aside, footer, main, or nav? Or is does it need a textual element like headings, anchors, paragraphs, lists, or quotes?
We need to ensure that any information expressed visually is communicated non-visually. If a button is disabled, how do we inform a screen reader user it is disabled? How does a screen reader user know if a Menu is opened? This is the information we should be looking for. In many cases ARIA attributes will be the answers to provide this information.
Under relationships we find little programmatic lines connecting the page together. We might specify via aria-label that the first navigation is the “Primary navigation.” Forms point to a more direct relationship in how we set up labels, inputs, and error messages. Using the label’s “for” attribute we build a relationship of the name and input. Aria-describedby with the ID of an error message is another bridge creating a relationship.
Much of the time these are not errors of information or relationships. They’re a failure of properly using HTML or ARIA. Sometimes both.
In my example of using the landmarks to construct the basic layout, it isn’t a violation. But we didn’t provide an accessible name. That’s a violation of 4.1.2, so why dump it here?
My disabled button? Case of missing aria-disabled, a 4.1.2 issue.
Headings used out of order? Not a WCAG SC.
Headings not sized to their importance? Now you have a 1.3.1 violation! The visual size provides a hierarchy of importance. On the code side we do this with heading elements H1 – H6.
Info and relationships are important on the web. They provide context and details that may not be picked up right away. Anything we do on this account visually needs to be conveyed programmatically too. But that doesn’t mean everything that falls into this bucket belongs. Dumping things in here can harm your clients. You might not provide them enough context to resolve their issues.
Look deeper at the issue. Is it a matter of a screen reader not announcing something? Look at the code, is it missing ARIA? Does it apply to another criteria? Make sure you flag it the right way. And don’t flag it twice, once here and once under the other SC. If it fits under another SC, then fixing it under that criteria will fix it for 1.3.1 as well.
Have a thought, feedback or concern about this article, let’s discuss it on BlueSky or LinkedIn.
Comments closedI’m pretty lucky. I have a solid career and reliable income. I also have health insurance through my employer, unlike millions of other Americans. However, something happened this week that scared the hell out of me. I caught pneumonia.
Comments closed
