Should Browsers Provide Accessible Components?

I recently had the pleasure of chatting with Sara Soueidan, a renowned expert in web accessibility. Our conversation was a deep dive into the nuances of making the web more inclusive and accessible for everyone.

Follow Sara:

• Her course, Practical Accessibility: https://practical-accessibility.today/
• Her newsletter: https://www.sarasoueidan.com/newsletter/
• Bluesky: https://bsky.app/profile/sarasoueidan.com
• Mastodon: https://front-end.social/@SaraSoueidan
• Linkedin: https://www.linkedin.com/in/sarasoueidan/
• X: https://x.com/SaraSoueidan

Things we mentioned during our conversations:

• Making the web sweeter with Food Network and Cupcakes https://www.youtube.com/watch?v=M2l56RmQAQE
• Blockquotes in screen readers https://adrianroselli.com/2023/07/blockquotes-in-screen-readers.html
• The Blockquote element https://heydonworks.com/article/the-blockquote-element/
• The HTML Living Standard https://html.spec.whatwg.org/multipage/grouping-content.html
• WCAG Quick Reference (contains links to Understanding and Techniques docs) https://www.w3.org/WAI/WCAG22/quickref/
• HTML AAM https://www.w3.org/TR/html-aam-1.0/
• ARIA 1.3 https://www.w3.org/TR/wai-aria-1.3/
• My course :D https://practical-accessibility.today
• My newsletter https://sarasoueidan.com/newsletter/