The Cake Is a Lie... And So Is Your Login’s Accessibility

The main topic of Ramona Schwering's session is accessibility, specifically focusing on why a lack of accessibility in applications and websites can be misleading and how it can affect users with disabilities.

Ramona Schwering uses the analogy of the game Portal, where players are promised cake that never arrives, to explain how some projects claim to be accessible but aren't truly implementing necessary accessibility features.

Temporary disabilities are short-term impairments like sensitivity to light after an eye checkup. Situational disabilities occur in specific contexts, like not being able to hear your phone in a loud environment. Permanent disabilities are long-term conditions such as blindness or deafness.

Accessibility is important to ensure that websites, applications, and projects are usable by everyone, including those with temporary, situational, or permanent disabilities. It is also supported by laws like the European Accessibility Act and the Americans with Disabilities Act.

Common pitfalls include using placeholders as labels, insufficient color contrast, poor keyboard navigation, and inadequate error handling. These issues can make it difficult for users with disabilities to navigate and use applications effectively.

For accessible authentication, avoid disabling functionality in password fields, consider password-free options like Passkeys, avoid object recognition tasks, and provide alternatives for QR code setups. Ensure multi-factor authentication is accessible with features like clear progress indication and sufficient time limits.

Screen readers are assistive technologies that read aloud what appears on a computer screen, helping users with visual impairments navigate applications. They can highlight errors, required fields, and other important information that might not be visible.

The purpose of Ramona Schwering's sample application is to demonstrate accessibility pitfalls and solutions in a practical setting, using a simple React-built application to showcase the importance of proper semantic markup and accessibility practices.

Error messages should be connected to their corresponding input fields using attributes like 'aria-require' and 'aria-invalid', and they should be labeled as 'role=alert' to ensure screen readers can notify users of errors effectively.