Talks
Speakers
Events
Topics
Search
Sign in
Search
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
search talks for
⏎
Suggest modification to this talk
Title
Description
Is your web app accessible? In his talk at #RailsWorld, Bruno Prieto shares his first-hand perspective as a blind developer on building accessible web apps with real-world examples taking advantage of tools provided by Rails, Hotwire, and the browser. It's easier than you think! #rails #accessibility #webaccessibility Thank you Shopify for sponsoring the editing and post-production of these videos. Check out insights from the Engineering team at: https://shopify.engineering/ Stay tuned: all 2024 Rails World videos will be subtitled in Japanese and Brazilian Portuguese soon thanks to our sponsor Happy Scribe, a transcription service built on Rails. https://www.happyscribe.com/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the video titled "Making Accessible Web Apps with Rails and Hotwire," Bruno Prieto, a blind developer and programmer at 37 Signals, shares insights into creating accessible web applications using Rails and Hotwire. He emphasizes the importance of accessibility and shares his personal journey of navigating technology as a visually impaired individual. The talk highlights key elements that contribute to web accessibility and offers practical tips for developers. ### Key Points Discussed: - **Personal Experience:** Bruno lost his sight at two years old and learned computer navigation through his father's guidance. He created his first website using Micromedia Dreamweaver, illustrating how technology became an integral part of his independence and learning. - **Understanding Screen Readers:** Steps to interact with screen readers are explained, noting that each screen reader has unique navigation commands. Emphasis is placed on using screen readers correctly to read content efficiently. - **Importance of HTML Semantics:** Bruno discusses the significance of semantic HTML, noting that proper structure (e.g., headings, and navigation regions) facilitates better navigation for both users and screen readers. - **Recommendations for Accessibility:** He provides practical advice for developers: - Use appropriate roles and tags in HTML, such as `main`, `header`, `navigation`, and proper heading levels. - Avoid modifying standard elements (like using a link as a button) to ensure consistent behavior across platforms. - Use ARIA attributes sparingly and make sure that all icons have accessible labels. - **Avoiding Common Pitfalls:** Choosing the right elements is crucial (e.g., using buttons for actions, links for navigation) to prevent confusion and enhance usability. - **Embracing Accessibility Standards:** Bruno encourages adherence to accessibility standards from the start of the development process. Introducing accessibility late in the design can lead to challenges and inefficiencies. - **Final Thoughts:** He concludes by urging developers to review their projects for basic semantic elements and test their sites with screen readers to identify accessibility issues. ### Main Takeaways: - Accessibility is vital in web development and can be achieved more easily now than ever. - Developers should engage in practices that make websites accessible by design rather than as an afterthought, thereby providing a smoother user experience for everyone. - Bruno invites viewers to reach out for further questions and discussions about improving web accessibility. Overall, the presentation aims to empower developers to create inclusive web applications that can be easily navigated by everyone, regardless of their physiological abilities.
Suggest modifications
Cancel
