If not an audit, then what drives change?Article contains
  1. Introduction
  2. Do we really not know what is wrong?
    1. The problem is not diagnostic. It is organizational.
  3. Why are audits so easy to sell?
  4. This is not about choosing what is easier
  5. What actually drives change?
  6. What role do experts play?
  7. The myth of secret knowledge
  8. The key point
Why DevTools and screen readers are inconsistentArticle contains
  1. The four-layer pipeline
    1. 1. DOM - developer intent
    2. 2. Browser accessibility tree - browser interpretation
    3. 3. OS-level accessibility API - platform translation
    4. 4. Screen reader interpretation - user experience
  2. Why DevTools and screen readers are inconsistent
  3. Practical examples of where inconsistencies arise
    1. Static structure issues
    2. Dynamic content updates
  4. Why manual screen-reader testing is non-optional
  5. Pipeline comparison: A visual reference
  6. Common misconceptions
  7. Effective testing strategies
  8. Operational implications for teams
  9. Quick wins: getting started
  10. Conclusion: a framework for reliable accessibility
  11. Further reading
Abstract image on text on it: "

Why DevTools and screen readers are inconsistent

Digital accessibility depends on recognizing a fundamental reality: the information shown in DevTools is not the same information a screen reader announces. This is not a flaw in DevTools or in screen readers. It is the natural outcome of a multi-stage translation pipeline that transforms the DOM into something assistive technologies can consume.

Teams often overlook this pipeline, which leads to false confidence, unexpected behavior in testing, and accessibility regressions that escape into production.

This gap between what developers see and what users experience is not merely academic. It creates real-world problems: developers ship features they believe are accessible, QA teams pass issues they cannot see, and users encounter barriers that never appeared in testing.

Continue reading “Why DevTools and screen readers are inconsistent”
Digital accessibility without an audit? Why "audit first" approach doesn't work.Article contains
  1. Introduction
  2. The myth: accessibility starts with an audit
  3. Reality: accessibility is a systemic problem
  4. Accessibility debt: do you really need to start with an audit?
    1. The thinking issue: let's fix everything at once
  5. What accessibility debt really means
    1. Where do you really need to start?
    2. Another metaphor
  6. Why the audit first model doesn't scale
    1. The scale of the problem
    2. The audit market
  7. What an audit actually does (and doesn't do)
    1. An audit
    2. But an audit does not:
  8. What I mean by "audit"
  9. When I say audit, I don't mean…
  10. How does an organisation know what to fix?
    1. Sources of knowledge about problems
  11. What to do instead of an audit (at the start)
  12. An audit - yes, but later
  13. Accessibility as a maturation process
  14. The most important shift
  15. When an audit is necessary
    1. Formal requirements and legal accountability
    2. Independent verification
    3. Key moments of change
    4. Complex or high-risk areas
  16. Summary
Minimalist illustration of a cluttered, inaccessible website interface highlighting issues like missing alt text, low contrast, unlabeled buttons, and no video captions - symbolizing why "audit first" fails in digital accessibility.

Digital accessibility without an audit? Why “audit first” approach doesn’t work.

Introduction

In discussions about digital accessibility, one phrase keeps coming up: Audit first.

Other phrases follow: an audit is essential, you can’t do without an audit. It sounds rational. After all, to fix something, you first need to know what’s wrong.

The problem is that in practice, the audit first, then fix approach usually does not lead to lasting accessibility improvement. What’s more, it very often reinforces the very mechanisms that cause barriers to appear in the first place.

Continue reading “Digital accessibility without an audit? Why “audit first” approach doesn’t work.”
CSS contrast-color() function, its possibilities and limitationsArticle contains
  1. What contrast-color() is and why it matters
  2. How the function works under the hood
  3. Syntax and basic usage
  4. Customizing contrast choices
  5. Practical use cases for real-world UI
    1. Buttons and interactive components
    2. User-selected themes
    3. Data visualizations
    4. Design systems
  6. Improving accessibility with automatic contrast
  7. Browser support and progressive enhancement
  8. Common pitfalls to avoid
    1. Assuming it enforces WCAG ratios
    2. Overriding the computed color
    3. Using too many candidate colors
    4. No support for gradients or images
    5. No support for APCA
    6. No transparent or currentColor support
      1. The transparent problem
      2. The currentColor problem
      3. Why CSS can't solve this natively
      4. What actually works
      5. Practical workarounds
      6. Future possibilities
  9. Conclusion
Abstract background and the following text on it: "CSS, contrast-color()"

CSS contrast-color() function, its possibilities and limitations

Color contrast has always been one of those deceptively simple problems. On the surface, it’s just light text on dark backgrounds or vice versa. In practice, it’s a constant balancing act between design intent, accessibility requirements, and dynamic UI states. We often ending up writing custom logic, maintaining color tokens, or relying on design system heuristics that don’t always hold up.

The new contrast-color() CSS function changes that dynamic. It gives the browser the responsibility of choosing an accessible foreground color based on the background in an automatically, predictably, and in line with modern color science.

Continue reading “CSS contrast-color() function, its possibilities and limitations”
The hidden SEO advantage with accessibility properties in JSON-LDArticle contains
  1. Introduction
  2. What are accessibility properties in JSON-LD?
  3. Core JSON-LD accessibility properties
    1. The speakable property
      1. How speakable works
      2. Implementation speakable in your WebPage schema node
    2. Choosing the right selectors
    3. Technical requirements for speakable
  4. Visual diagram that illustrates how accessibility JSON-LD properties act as a bridge between accessible code and search engine understanding
  5. What are the benefits of including accessibility-related data in a schema?
    1. Semantic clarity for search engines
    2. Preparation for Accessible Search
    3. Potential for enhanced visibility
    4. Strengthening E-E-A-T through technical integrity
    5. Synergy with WCAG compliance
    6. A warning on vanity metrics
  6. Testing your markup
  7. Conclusion
SEO inscription on three blocks and below it: Accessibility & JSON-LD

The hidden SEO advantage with accessibility properties in JSON-LD

While developers obsess over Core Web Vitals and keyword density, a powerful SEO signal hides in plain sight: accessibility metadata. By adding schema.org’s accessibility properties to your JSON-LD, you’re not just helping users with disabilities – you’re creating machine-readable proof of quality that search engines are already beginning to prioritize.

Continue reading “The hidden SEO advantage with accessibility properties in JSON-LD”
Native built-in browser elements you can use today instead of ARIA or ROLE attributesArticle contains
  1. The first rule of ARIA
  2. Why move away from ARIA?
    1. Browser-engine privilege
    2. Less code, less maintenance
    3. Smaller payload, faster render
    4. Built-in resilience to future spec changes
    5. Mobile and voice-input compatibility
    6. Security and performance isolation
    7. Internationalisation for free
    8. Future-proofing for new input modalities
    9. Easier testing and audits
    10. Legal, procurement safety
  3. When ARIA is still justified
  4. Native HTML replacements for ARIA roles and attributes
  5. Conclusion
Text "Aria to semantic HTML" where "HTML" is on tiles.

Native built-in browser elements you can use today instead of ARIA or ROLE attributes

When building accessible web applications, developers have long relied on ARIA and role attributes to fill gaps in native HTML.

But today, many of those gaps are gone. Modern browsers support a wide range of semantic HTML elements and built-in behaviors that make ARIA redundant in most cases, often with better results and fewer bugs.

This shift towards native accessibility features means that developers can now create accessible web applications using built-in browser elements and attributes, rather than relying solely on ARIA and ROLE only.

We’ll explore the native built-in browser elements and attributes that you can use today to improve accessibility, and how they can replace or complement ARIA and ROLE attributes in your web development workflow. By leveraging these native features, you can simplify your code, improve maintainability, and create more accessible web applications for everyone.

Continue reading “Native built-in browser elements you can use today instead of ARIA or ROLE attributes”
Accessibility automated website scans and how much can they catchArticle contains
  1. Introduction
  2. What percentage of accessibility issues can automated tools catch?
  3. What automated tools can catch
  4. Why manual testing is non-negotiable
  5. WCAG 2.2 quick-reference: which Success Criteria can be scripted, which can't, and why
Two chairs and multiple monitors opposite. One of them bears the words: "Digital Accessibility Audit in progress...". Image by Andy from Pixabay

Accessibility automated website scans and how much can they catch

Automated accessibility testing tools have gained traction due to their ability to quickly analyze web pages for compliance with accessibility standards, such as the Web Content Accessibility Guidelines (WCAG). These tools can scan a website’s code and identify potential issues, making them an attractive option for developers and organizations looking to improve accessibility.

Continue reading “Accessibility automated website scans and how much can they catch”
Accessibility, VPAT, ACR in questions and answersArticle contains
  1. What is a VPAT?
  2. What is an ACR?
  3. Understanding the relationship: Template vs. Completed Report
  4. What is the purpose of the VPAT template?
  5. Key components of a VPAT/ACR
  6. VPAT editions
  7. Is a VPAT/ACR mandatory?
  8. Mobile app accessibility: do you need to complete a VPAT?
  9. Who is responsible for completing the VPAT?
  10. What happens if you don't have an ACR?
  11. Does an ACR guarantee 100% compliance?
  12. What standards and guidelines are used to evaluate accessibility in an ACR?
  13. Who needs to provide an ACR?
  14. How often should you update your ACR?
  15. Why is the VPAT/ACR important?
  16. Can the completed VPAT (ACR) be used for auditing and compliance purposes?
  17. What are the requirements for creating an ACR?
  18. Where can I find ACRs (completed VPATs)?
  19. Steps to create your ACR from the VPAT template
  20. Key Takeaways
  21. Conclusion
  22. Example ACR (Completed VPAT version 2.4)
Magnifying glass with inscription: "Frequently asked questions" and below: "Accessibility, VPAT, ACR". Image by Louis from Pixabay.

Accessibility, VPAT, ACR in questions and answers

The VPAT® is a free template used to create an Accessibility Conformance Report (ACR), which plays a vital role in promoting accessibility in technology. The completed VPAT document is the ACR, providing transparency for consumers and organizations to make informed decisions. This single document helps organizations comply with legal requirements and foster an inclusive environment for all users.

Understanding this relationship is crucial: the VPAT is the standardized template, and the ACR is the final report generated by completing that template with your product’s specific accessibility information.

Continue reading “Accessibility, VPAT, ACR in questions and answers”
The role of AI in streamlining accessibility and SEO testingArticle contains
  1. Understanding Accessibility and SEO
  2. How AI is transforming accessibility testing
  3. Key benefits of AI in accessibility testing
  4. AI's role in SEO testing
  5. How AI enhances SEO testing
  6. The intersection of accessibility and SEO
  7. Challenges and considerations
  8. Implementing AI for accessibility and SEO testing
  9. The future of AI in accessibility and SEO
    1. Voice search optimisation
    2. Personalized experiences
    3. Predictive analytics
  10. Closing points
  11. Frequently asked questions (FAQ)
    1. How does AI make websites more accessible?
    2. Can AI do SEO optimization?
    3. What are the mutual advantages of accessibility and SEO?
    4. Are there issues to using AI for accessibility and SEO?
  12. Need help?
  13. Author biography
Large, stylized, light-green letters spelling out "SEO" are centrally featured. Three stylized figures, a man and two women, are positioned around the "SEO" letters.

The role of AI in streamlining accessibility and SEO testing

Business success depends heavily on the development of websites which provide convenient navigation alongside search engine compatibility. Accessibility, together with Search Engine Optimization (SEO), stands as the key dimension for reaching this objective. The separate practices of accessibility and Search Engine Optimization (SEO) share many common elements while AI technology reshapes modern business methods for them.

Continue reading “The role of AI in streamlining accessibility and SEO testing”
Explore focusable, clickable, tabbable or active statesArticle contains
  1. What is the difference between an interactive element that can receive focus, be clicked, be active, or be tabbable?
  2. Determine if an element is clickable
  3. Determine if an element is focusable
    1. Determining if an element is a type of focusable element
    2. Determining if the element can receive focus right now
  4. Determine which element is active now
Laptop and cactus on the left side and coffee on the right side. Image by Megan Rexazin Conde from Pixabay.

Explore focusable, clickable, tabbable or active states

Determining whether an element is interactive or not can be crucial for various purposes, such as improving accessibility, enhancing user experience, testing purpose or debugging issues.

An interactive element is one that can receive focus, be clicked, be active, or be tabbable, allowing users to engage with it in some way. Let’s find out how to determine if an element is focusable or active using JavaScript.

Continue reading “Explore focusable, clickable, tabbable or active states”