Accessibility, a joint effort
Expectations about accessibility, from a client perspective
Expectations about accessibility, from a client perspective
Adding some flair to my game with graphics and a cool parallax effect!
Why on Earth did I start building a game?
A little journey back to the past and why I started this blog
Over the past months, I’ve spent a significant amount of my time at work focusing on accessibility. It’s a topic that’s not just technical or theoretical, it’s deeply practical and transformative when embraced fully. Based on my experiences, I wanted to share insights into what accessibility truly means and why it requires collaboration between developers and clients.
Accessibility isn’t just a technical checkbox; it’s a shared responsibility that extends beyond developers and requires active participation from clients as well. Often, clients expect their supplier or developer to handle everything, but the reality is that we need a collaboration. In my experience working with organizations, I’ve seen this expectation many times, but true accessibility starts much earlier, right at the source.
Ofcourse, developers play a crucial role in creating an accessible foundation. From writing semantic HTML to implementing ARIA roles and ensuring compatibility with assistive technologies, their work is essential. However, even the most perfectly coded website can fail accessibility standards if clients and content creators don’t uphold their side of the equation. Accessibility isn’t just about the code, it’s also about the content.
In many organizations, content is created by various departments long before it reaches the online world. This is often where accessibility starts to face its first challenges. If the source content isn’t created with accessibility in mind, it’s almost impossible to make it fully compliant later. For example:
By embedding accessibility practices into the workflows of these departments, organizations can prevent many issues before they arise.
Clients, particularly those who manage and update content, are just as responsible for maintaining accessibility. Here are some examples of how their contributions make a difference:
In conclusion: accessibility isn’t a one-time project—it’s a continuous process. Clients need to stay informed and engaged to ensure their content remains accessible.
Accessibility isn’t just about websites and applications. It’s a mindset that should be the core of an organization’s culture. This means thinking about inclusion at every level, from strategic planning to daily operations. In my experience, organizations that truly embrace accessibility as part of their identity see the biggest impact. Here are some examples of this mindset:
When accessibility is treated as a core value, it becomes a natural part of decision making rather than an afterthought. This approach not only ensures compliance but also embraces innovation and inclusivity. Once this mindset is fully embraced, maintaining accessibility becomes significantly cheaper and easier. Accessibility evolves into a seamless, ongoing process that aligns with the organization’s operations and goals.