Development

A lot of eslint rules and reusable components already exist for accessibility in HTML, Javascript and React. When working with developers with varying levels of theoretical and practical experience with accessibility implementations, we realised that the mistakes that our devs were making with respect to accessible implementations, were either not general enough to have an existing eslint rule and / or the mitigation was very specific to the usages in our codebase. We started with a simple thought: can we automate the detection and fixes for these repeated mistakes?

Overwhelmed by the task of making your project accessible? Come learn how two developers have seen firsthand how tangible and accessible accessibility can be.

What if you started every discussion with, "how do we make this accessible." What if every decision for a product was thought of from a point of maximum inclusion?

In this talk, GrahamTheDev will show how leading with accessibility can lead to better UX, quicker development and ultimately, more profitability for a company.

One would think that language has been solved in 2023. We have translation apps, sign languages, an international phonetic alphabet that is supposed to be able to represent any sound in any language for academics to endlessly discuss over. And yet, the challenges are myriad. From screen readers not knowing how to pronounce the ultimate guide to pronouncing things to less than helpful apps and from several different alphabets to unhelpful, incorrect language tagging, the topic of linguistics accessibility can be a wonderfully twisty-turny rabbit hole to go down.

When it comes to web accessibility, timing is of the essence. It’s easier when you do it earlier. What if your CMS could spot content problems and help you fix them, before your content even goes live? What if it could warn content editors about potential issues, ship with accessible defaults, make it easier to see content structure implications and offer alternatives to inaccessible content (like colours with better contrast). In Hidde’s talk, you’ll learn how these kinds of features can help you “shift left”.

In this talk, we will discuss the next generation of automated testing. Our speaker, the Founder of SiteLint, recalibrated the remediation process significantly, improving accessibility quality testing and focusing on the user behavior. He will discuss the new technology and it's unique approach. It goes beyond crawling and analyzing data on the server side.

Many accessibility defects originate in design, so why do the bulk of accessibility considerations fall to developers and quality assurance? In this talk, we will discuss why we need more accessibility designers, what it means to be an accessibility designer, and the day-to-day responsibilities of an accessibility designer. Learn how you can advocate to create accessibility designer roles and begin to train yourself to specialize in accessibility as a designer.

Automated testing for accessibility issues with axe-core is one of the best and most effective ways to catch up to 50% of accessibility violations. In this talk, we will take a look at the levels of testing needed from an automated perspective to ensure your content is accessible at a component level and an application-level using a working React application and the axe-core testing frameworks.