19. Nov 2024Frontend

How we started with accessibility at GoodRequest

At GoodRequest, our vision is to create a meaningful and responsible digital world. That's why, we want to lead by example and have started to address accessibility on the web. Today, I want to tell you why developers don't take accessibility seriously but also how we at GoodRequest started to address accessibility and why all IT companies should address it.

Štylizovaná postava s logom GoodRequest namiesto hlavy skúma úryvok kódu na tmavej obrazovke s lupou - objavuje prvky prístupnosti. Všetko na jasne modrom pozadí.

Why Don’t Developers Take Accessibility Seriously?

Lack of Awareness

Developers often don’t realize the importance of accessibility, which is why they tend to overlook it. Accessibility is a fairly specialized field that requires specific knowledge developers often lack. During my five years of university studies, I had only one lecture dedicated to accessibility.

Time and Money

Creating an accessible website, especially at the beginning, requires extra time, which increases development costs. Developers usually face project deadlines that force them to prioritize other requirements, such as performance, design, bug fixes, or the core functionality of the website.

Challenging Accessibility Implementation

This is especially true for large, existing web applications. Significant changes to the code are often needed, which may discourage developers. They tend to focus on tasks they consider more important.

Lack of Regulation

Government websites are legally required to be accessible, but this doesn’t currently apply to commercial websites. Without legal obligations, developers aren’t compelled to prioritize accessibility unless explicitly requested by clients.

User Feedback

If developers don’t receive feedback or complaints from users with disabilities regarding accessibility issues, they may assume accessibility is not a significant problem.

How Did I Start with Accessibility?

I first encountered accessibility during a lecture at university. A blind man demonstrated how he uses a screen reader and the common issues he faces online. However, this didn’t spark enough interest for me to pursue the topic further at the time. Last year, after attending a lecture on accessibility at the WebExpo conference in Prague, I revisited the subject. I began studying resources available online and started using tools for automated accessibility testing.

Among the most effective tools are solutions by axe® Tools, built on the globally popular testing library axe-core:

  • Browser Plugin
    This plugin helps me identify and fix numerous issues during development. It precisely points out errors and provides guidance on how to fix them. Using this tool, I’ve learned a lot about accessibility since there’s no better way to learn than by working directly on a project and learning from your mistakes.
  • ESLint Plugin
    Most developers already use tools like ESLint, which analyzes your code and highlights issues directly in the editor. This tool allows me to fix accessibility errors even before testing begins.

How Did We Start Addressing Accessibility at GoodRequest?

Innovation Platform

It started with a task in Jira within our innovation platform, created to improve our processes. The goal was to analyze the current state of accessibility on our websites and identify ways to improve it.

Team Education

During meetings, I prepared several presentations to share key insights about accessibility with colleagues. Additionally, we had a session with Peter Halada from the Union of Blind and Partially Sighted People of Slovakia, who showed us how he uses a screen reader and the challenges he faces online as a visually impaired user.

Onboarding Process

Every new developer goes through an onboarding process that includes a lecture on accessibility basics.

Code Review

During project code reviews, we flag potential accessibility issues and recommend fixes.

Community Resources

Based on our experiences, we created blog articles such as “How to Start with Accessibility” and “Common Accessibility Mistakes and How to Fix Them.” We also participated in the CodeCon conference, where we presented on accessibility.

 

Why Should Other IT Companies Think About Accessibility?

Accessible Websites Benefit Everyone

  • Barriers are removed for people with disabilities.
  • Semantic websites enhance accessibility, improve SEO, and increase web discoverability.
  • Accessibility rules also improve usability and user experience for everyone.

More Potential Customers

A common myth is that accessibility concerns only a small group of people. However, over a billion people worldwide have some form of disability. Ignoring accessibility excludes a significant portion of potential customers.

Brand Reputation

Companies that prioritize accessibility demonstrate a commitment to creating a more inclusive digital environment, improving their image and brand reputation.

Compliance with Legal Regulations

Many countries have laws and regulations requiring accessible websites and digital services. In Slovakia, this currently applies only to government websites, but this will soon change with the European Accessibility Act.

Competitive Advantage

Being ahead of the curve in accessibility can provide a significant advantage, especially in markets where it becomes mandatory. For instance, in Europe from 2025, accessibility could become a key differentiator.

What Are Our Future Goals?

A common myth is that accessibility is solely the responsibility of developers. However, it’s the responsibility of the entire team, from designers to testers. Therefore, we aim to continue improving our processes and raising awareness of accessibility among our colleagues:

For example:

  • Testers should perform stricter accessibility checks.
  • Designers should better incorporate accessibility requirements into their designs.
  • Developers should create more accessible web and mobile applications. We’re still learning and see room for improvement.


Lectures at Universities

We believe accessibility should be taught at universities to support the next generation of developers who will think about accessibility and inclusive digital environments from the start. This will also be an essential skill for the future, helping young developers with career opportunities. Therefore, we aim to deliver at least one lecture on digital product accessibility at universities.

Andrej NemečekHead of Frontend