WeAreDevelopers LIVE - Gaps in CSS, EU Accessibility Act and more!

Is your website ready for the European Accessibility Act? Learn why automated checks aren't enough and what developers must do to truly comply.

#1about 5 minutes

From teaching to a career in web accessibility

A former teacher explains how adapting lessons for students with diverse needs provided a natural foundation for a career in web accessibility.

#2about 6 minutes

Learning front-end development by recreating existing websites

The "Front End Practice" website offers a practical approach to learning by challenging developers to replicate real-world UIs, which demystifies design and coding techniques.

#3about 3 minutes

Exploring the new CSS proposal for element separators

A new CSS proposal aims to simplify creating separators between elements, eliminating the need for hacky solutions like removing the last border in a list.

#4about 7 minutes

Balancing creative control and usability with CSS form styling

While new CSS form styling capabilities offer more design freedom, they also risk creating inconsistent or inaccessible controls if not used carefully.

#5about 5 minutes

Addressing inconsistent spacing and gaps in CSS layouts

Modern CSS offers multiple ways to handle spacing like margin, padding, and gap, which can lead to confusion and inconsistent layouts.

#6about 7 minutes

Preparing for the upcoming European Accessibility Act

The European Accessibility Act (EAA) will soon require private sector services like e-commerce and banking to meet specific accessibility standards.

#7about 11 minutes

The role and limitations of AI in generating alt text

While AI can help generate alternative text for large image backlogs, it often lacks the contextual understanding that a human editor provides.

#8about 5 minutes

Checking browser and screen reader support for accessibility features

The website a11ysupport.com acts like "Can I Use" for accessibility, showing which ARIA roles and properties are supported across different screen readers and browsers.

#9about 3 minutes

How Safari's `list-style: none` behavior impacts accessibility

Safari's controversial decision to remove list semantics when `list-style: none` is applied forces developers to add `role="list"` to ensure screen readers announce it correctly.

#10about 3 minutes

Building accessible animated accordions with the details element

The native HTML `<details>` and `<summary>` elements provide a semantic and accessible foundation for creating animated accordion components without JavaScript.

#11about 5 minutes

Using fieldset and legend to group related form controls

Wrapping related form inputs like an address block in a `<fieldset>` with a `<legend>` provides essential context that is announced by screen readers for each control.

#12about 2 minutes

A look back at the first registered .com domain name

The very first `.com` domain name was registered in 1985, not for a major tech company, but for a computer manufacturer called Symbolics.

#13about 3 minutes

Final advice for integrating accessibility into your workflow

The most effective way to build accessible products is to consider accessibility from the very beginning of the development process rather than treating it as an afterthought.