Common Misconceptions About Web Accessibility

🚫 WCAG Levels Are Not a Grading Scale There’s a common misconception in digital accessibility: that WCAG levels A, AA, and AAA represent a “good, better, best” system. They don’t. ✅ WCAG levels are not about quality—they're about scope. • Level A addresses critical blockers for access. • Level AA covers common barriers that impact many users. • Level AAA includes enhanced requirements aimed at specific user needs—not a gold star for perfection. 🔍 Not every AAA criterion is feasible or appropriate for every website or document. That’s by design. AAA is not “better,” it’s more specific. If you got caught up in this misconception, I hope this brought some clarity. 💡 True accessibility is about meeting user needs, not chasing a letter grade. #DigitalAccessibility #WCAG #InclusiveDesign #AccessibilityEducation #A11y #UX #DocumentAccessibility #Chax

Instant web accessibility (unfortunately) doesn’t exist Years of inaccessible design and poor coding practices can’t be solved by installing a plugin or activating an AI widget. Yet, every week, I keep seeing posts and advertising about AI-powered tools, plugins, widgets and authomatic solutions that promise “make your site accessible instantly”. No effort, no training, no need to understand. Just click and done. I remember clearly the first time I saw a plugin on the website and I was genuinely impressed. It seemed almost magical: a tool that could adapt any site for different disabilities in just one click! But as I learned more, I realized that what looks effortless often hides complexity and even harm... Here’s what really happens: 🔹 Automated tools often create new barriers — wrong labels, missing context, inaccessible overlays. 🔹 They can interfere with users’ assistive technologies instead of supporting them. 🔹 And they risk giving organizations a false sense of compliance — without actually improving user experience. Studies on this subject: 1. Caution About Accessibility Overlays — Arizona State University IT Accessibility: outlines that overlay tools often only fix ~25-30% of issues, may slow performance, and create new barriers (a link to the article: https://lnkd.in/eDhqb464) 2. SoK: Detection and Repair of Accessibility Issues — academic paper: demonstrates how automated tools (and by extension overlay-type tools) cover only ~20-30% of issue types, far from replacing human checking (a link to the article: https://lnkd.in/evyz8Qw7) 3. W3C: AI and Accessibility Research Symposium 2023: a published report from W3C summarizing discussions about the risks, benefits, and challenges when combining AI with accessibility — including ethical issues and how AI might misinterpret disability (a link to the report: https://lnkd.in/euk5pBwv) True accessibility can’t be automated. It requires understanding, empathy, and continuous collaboration with people with disabilities. AI can be our helper to detect, suggest, and speed up parts of the process, but never the decision-maker. That’s why I’m convinced we need to make web accessibility education mandatory in all web-related studies, design programs, and professional training. So we teach people why accessibility matters before we ask technology to “solve” it for us. Because accessibility isn’t a plugin you install. It’s something you build through awareness, learning, and human connection. #Accessibility #WebAccessibility #A11y #InclusiveDesign #DigitalInclusion #EthicalAI #WebDevelopment #UXDesign #DigitalAwarness

Paying for accessibility improvements? You might be funding the opposite.   I often see developers spending time and resources on accessibility work that actually makes a website less accessible.   They mean well, but they lack the right knowledge.   The result? A blind screen reader user like me might not be able to use your website at all. Even if it was fairly accessible before the developer made these mistakes.   It comes down to small pieces of code added to your site. Used correctly, they can improve accessibility. But if the developer doesn’t fully understand how to use them, they can completely block some users from accessing your site.   5 Typical Examples of How Web Developers Break Website Accessibility by Misusing ARIA Codes:   #1 Turn your website’s search input into a search landmark. This is perfect if you want screen reader users to miss that they’re even interacting with a search field.   #2 Add menu semantics to your navigation, but ignore the required children, keyboard functionality, etc. This is perfect if you want your global menu to be completely impossible - or at the very least, incredibly difficult - to interact with for screen reader users.   #3 Turn your rapidly auto-updating news carousel into a live region. This is ideal if you want to block screen reader users from accessing anything on your website other than what's in your news carousel.   #4 Turn your entire webpage into an application - just because it sounds cool. This is yet another effective way to ensure that screen reader users can’t access any of your website’s content. #5 Apply tab semantics to your accordion. This is a powerful trick you can use to deliver a truly baffling experience for screen reader users.   ARIA is a powerful tool that can either enhance or destroy accessibility. Please, only use it if you truly know what you're doing.   As a blind screen reader user, I constantly come across well-intended websites that end up being inaccessible due to seemingly harmless ARIA code.   Let’s change that! 🔁 Repost this to help developers recognize and avoid these common pitfalls - making the web a more inclusive place for everyone. Follow Lars Holm Sørensen for daily insights on accessibility awareness.

5 WCAG compliance myths that might be sabotaging your team (and what to do instead) I've heard these myths countless times, and they're costing teams real opportunities to connect with their audiences. Here's what I wish everyone knew: Myth 1: "Accessibility is just for websites" Reality: Your PDFs, presentations, and infographics need to be accessible too. If you work in education, government, or serve the public, this isn't optional. Myth 2: "Good colors and fonts = accessible" Reality: You also need alt text, proper headings, and logical reading order. Quick win: Check your heading structure before hitting send on that next document. Myth 3: "Only tech people can do this" Reality: Anyone can learn the basics. Start with writing good alt text and checking color contrast. I promise it's not as scary as it sounds. Myth 4: "Set it and forget it" Reality: Accessibility needs ongoing attention. Set a quarterly reminder to review your most-used documents. Standards change, and so do your users' needs. Myth 5: "Accessible = ugly" Reality: You can absolutely keep your brand looking sharp while meeting accessibility standards. I've seen gorgeous, compliant designs that would make any marketing team proud. Here's your action step: Pick one document you share regularly and run it through a free accessibility checker today. You might catch something you've been missing and make your content work better for everyone. What accessibility myth have you heard lately?

"Accessibility is too expensive" is one of the most costly misconceptions in web development. Here's what actually costs more: • Rebuilding after accessibility complaints or audits • Lost customers who can't use your site • Legal fees from avoidable lawsuits • Missing out on the spending power of 1 in 4 adults with disabilities When you build accessibility in from the start, you get better outcomes for less effort. Accessible sites tend to be faster, more usable for everyone, and easier to maintain. Plus, you avoid the panic of scrambling to fix everything later. I see this with agencies all the time. The ones who integrate accessibility into their process from day one? They're more confident, their clients trust them more, and they rarely deal with emergency fixes. Accessibility isn't overhead. It's good business. What's your experience been? Have you seen the costs of waiting to address accessibility, or the benefits of building it in early? #accessibility #webdevelopment #agencies

Inaccessibility is all around us - but sometimes we’re doing it without even realising. I’ve made every one of these mistakes in the past. It wasn’t until someone took the time to point them out that I learned how inaccessible I was being - despite having good intentions. Here are 5 ways you might be being inaccessible, without even knowing: 1. Long LinkedIn headlines or overuse of emojis. Screen reader users hear your full headline every single time you post or comment. Every. Single. Time. Even when it’s truncated visually. That can mean hearing your full job title, emojis, and taglines multiple times before even reaching your post content. Try to keep your headline under 100 characters or two lines max - it makes a huge difference. 2. Long email signatures, HTTP links, and unlabelled images. Screen readers will read out every line - including things like “H-T-T-P-colon-slash-slash…” for full URLs. Images without alt text are completely invisible to screen reader users. Keep it short and simple, and use alt text wherever you can. Put only essential info in your email signature and put two dashes at the top to signal your signature is starting. And remember, it’s not your marketing tool. When was the last time you actually bought something from an email signature?! 3. Not running documents through the accessibility checker. You run a spell check, so why not an acceeeibility check? It’s a quick step, but it can flag things like heading structures, contrast issues, and missing image descriptions. It takes seconds and makes a big impact. 4. Using colour alone to convey meaning. For example, “I’ve marked the important cells in green” doesn’t help if someone can’t perceive colour easily. Neither does “I’ve shaded the cells for our RAG status”. Always add a label, icon, or another indicator. 5. Using all lowercase hashtags. #thisisnotaccessible - screen readers can’t parse where one word ends and another begins. Use camel case instead - #ThisIsAccessible - so screen readers pronounce the words correctly. Small changes, big impact. If you’ve made some of these mistakes before - welcome to the club. We learn, we improve, we do better. #DisabilityInclusion #Disability #DisabilityEmployment #Adjustments #DiversityAndInclusion #Content #A11y

The Truth About AI and Digital Accessibility. "The AI will sound very confident. It will say, 'I have coded this website. It's completely accessible.' And then I look at it and go, 'No, it's not.'" That's Eugene Woo, CEO of Venngage, during a fascinating conversation Debra Ruh and I had on the latest AXSChat episode. Here's the hard truth: +90% of websites aren't accessible. So when AI models train on existing data, they're learning from inaccessible examples. The result? Confident hallucinations about accessibility that don't hold up under scrutiny. The real challenge isn't AI itself—it's the training data. AI is incredibly helpful for scaffolding, efficiency, and speed. But right now, when it comes to color contrast, semantic structure, and proper layering for screen readers? It still falls short. But here's the optimistic part: This is fixable. We need to: - Feed AI models with truly accessible examples - Train algorithms on accessibility standards, not just existing (flawed) websites   - Combine AI intelligence with human expertise and built-in accessibility features - Stop treating accessibility as an afterthought—it needs to be baked into the foundation The future isn't about choosing between AI or accessibility. It's about building AI with accessibility from the start. If you're building products, hiring vendors, or working in tech: Hold AI accountable. Don't accept confident-sounding claims about accessibility. Demand better training data. Support tools and platforms that prioritize accessible design from day one. The web's accessibility crisis won't be solved by AI alone—but AI trained on accessible data, combined with human judgment and vendor commitment? That's where the real transformation happens. Tune into AXSChat to hear the full discussion with Eugene on how companies are rethinking accessibility in the AI era. What's your experience been with AI-generated content and accessibility? I'd love to hear your thoughts. #Accessibility #AI #DigitalInclusion #ArtificialIntelligence #InclusiveDesign #AXSChat

Stop confusing Accessibility statements with accessibility practices. There’s a BIG difference. 
The problem? Most companies love to say the right things. 
But employees & customers don’t live in statements. 
(They live in reality) And in reality you say “we value accessibility,” but: Your website breaks with a screen reader. You host events, but captions are “optional.” Your hiring filters out & disqualifies disabled talent. That’s not accessibility at all. That’s marketing. Accessibility isn’t about what you put on paper. 
It’s about what people can actually do, see, and experience. Here’s some potential fixs: - Stop writing fluff. Start fixing barriers. - Test your stuff with actual disabled users. - Be accountable for results, not statements. Words don’t open doors. Practices do. You really want to build an inclusive culture? Don’t just write about it…show it. PS Some of my favorite people to follow around accessibility: Dustin Giannelli🦻🏼 Michael Iannelli Jamie Shields Axel Leblois Debra Ruh Ablr 360 Special mention: M-Enabling Summit G3ict - The Global Initiative for Inclusive ICTs IAAP - International Association of Accessibility Professionals [image description: Quote on background that says accessibility statements aren’t accessibility practices. Stop confusing the two. ] #accessibility #dei #disability #inclusion

One of the most common misunderstandings about accessibility is the belief that it is only about the physical environment - ramps, accessible pedestrian signals, elevators, curb cuts, public seating and accessible entrances. While these elements are essential, accessibility is much broader than the built environment. True accessibility is about ensuring that people with disabilities can fully access information, services, opportunities, and participation in society. Accessibility also includes digital access, which includes websites, documents, software, and public information that can be used with screen readers, captions, keyboard navigation, and other assistive technologies. As more of our work, education, and civic engagement happens online, digital accessibility has become just as important as physical access. Equally important is communication access, such as captioning, plain language materials, sign language interpretation, accessible presentations, and multiple ways to engage with information. Communication access ensures that people with diverse sensory, cognitive, and learning needs can participate meaningfully in classrooms, workplaces, and public life. Accessibility also exists at the programmatic and policy level - how services are designed, how meetings are conducted, how hiring processes work, and how organizations anticipate inclusion. And perhaps most importantly, accessibility includes attitudinal access: the willingness to listen, adapt, and recognize disability as a natural part of human diversity rather than a limitation. In my work in transportation accessibility and public policy, I’m constantly reminded that accessibility is strongest when it is embedded from the beginning; in planning, design, communication, and culture. When we expand our understanding of accessibility beyond the physical, we move closer to creating environments where everyone can participate in school, workplace or community with dignity and independence. #Accessibility #DisabilityInclusion #UniversalDesign #InclusiveLeadership #ADA #DisabilityRights #Equity #Neurodiversity #Disability #DisabilityJustice #CivilRights Image Description: Blue background graphic with white text that reads, “Myth: Accessibility is only physical. Fact: Accessibility includes digital, communication, programmatic, and attitudinal access.” The handle “@AsieduEdmund” appears in the lower left corner, and a small “AE” logo inside a circle appears in the lower right corner.

🚫 Overlay tools are not accessibility solutions. This week, a representative an overlay company reached out to me directly, asking for a “chat” about my stance. Let me be absolutely clear: As a Certified Professional in Web Accessibility (CPWA), an accessibility advocate, and the founder of the Accessibility Book Club, I will always advise organizations to steer clear of companies that sell overlays as a magic fix for accessibility. The Federal Trade Commission (FTC) recently issued a consent order requiring accessiBe Inc. to pay $1 million for misrepresenting its AI‑based product as capable of making websites WCAG compliant. Federal Trade Commission: https://lnkd.in/gd87wGsP If a company genuinely cared about digital inclusion, it would: - Stop pushing overlays as “accessibility solutions” - Stop distributing misleading reports on WCAG conformance - Study the WCAG guidelines inside and out — and build real accessible experiences, not placeholders 📣 If you’re responsible for a website and are serious about accessibility—avoid quick fixes. Partner with experts. Do it right. #Accessibility #A11y #WebAccessibility #CPWA #DigitalInclusion #StopOverlaySolutions #GracefulWebStudio