Semantic markup - Designing in the Browser 

I'm from Brazil and I love your videos! You are very friendly, professional and intelligent. Good work!

I was pleasantly surprised at how readable _most_ things were in this presentation (it never ceases to amaze me when someone's presenting on an accessibility topic and fails to account for some of the most common accessibility needs, like using a decent font-size; not indicating meaning with _just_ colors, particularly red & green, etc). Una, please encourage Rob to use larger font-sizes like you do 😉.

I've been almost 2 years in programming without knowing the benefit of using the ARIA attribute and I think it's good to apply in my next project even in my own portfolio to make it accessible even with pwd or like blind person. By the way today is the day when I saw you here in internet since I was searching for a good tutorial and i found google developer channel, this is my 3rd video tutorial I've watched with you. I really enjoy and appreciate your effort. Again, thankyou mam Una - dev from ph

I am excited for this series ❤️❤️❤️❤️

Awesome, thanks a lot! 💜🌿🙌🏼

I'm a complete newbie in this subject. I could just bearly follow what you were talking about. But I definitely thank you for the video! I only have a Chromebook right now to begin my learning journey. I was worried that I wouldn't be able to start until I could purchase a Macbook. Thanks again!

Excellent video. It's a pity that lots of web developers (or at least the developers I have worked with in my career) don't pay any attention to accessibility. I often have to rewrite pieces of HTML/CSS with improper use of headings tags (using them as a "style template" and not a semantic structure) or inadequate elements for the visually impaired (light gray text against white background and so on). In my humble opinion, a good web developer should have "empathy" as a basic skill, so that he/she can always be aware of all the different abilities and limitations that the user could have.

Awesome! More please!

2084: Almost all life transformed into digital space, a matrix, there still were humans, but digital. One little newly initialized human agent was interested in history, so he asked his overlord AI to give him access to historical archive. It was too big info for this little human agent to process, so AI started the conversation: - Back in early 2000’s, up to 2010, there was only div. Humans didn’t know language really. There was a primitive language with some other words like span, and ul/ol, but few people used it. Most humans called everything a div, a that was it. Life was primitive. - But how? How is that possible? How they differentiated anything from everything? - Idk, maybe they were smarter than us, and everything was obvious to them, so they didn’t need differentiating. - Wow... No need in language, words, tags? You think it’s smart? - Of course this isn’t smart. But after all, they’ve created me somehow, so they weren’t dumb. We may not understand them, but that’s what they were. - But... Everything’s a “div”? What’s a div? - Div is everything - Wow...

great content keep it up.

really inspiring video,tks for sharing:)

thank you, that helps a lot

My general rule: Spans and divs are primarily for decoration/display. Use of them otherwise says "I don't know/understand what the content is". If a developer does not understand this (which can be understood in a matter of hours) and create unique javascript selectors (vs blind parent/child grabs), they should not touch the markup. period. It drives me nuts when I see developers abuse spans, divs, and ids - which is nearly every org (mainly jsp or .net devs) I've worked for. As a front-ender, the bulk of my job usually boils down to teaching back-enders how not to make my job difficult. It should be a requirement that web development managers/VPs in any/all organizations understand this. It causes massive bloat, bugs, and extends dev/qa time for everyone. It also exposes the inner workings of an org. All I have to do is view the source of a web app to see how screwed up the dev team is ;-)

The return of Rob Dodson 🙂 I miss his allycasts 🙂

Thanks. Now i need to rewrite my entire website

I always feel hesitant using uncommon semantic elements thinking am I using it in the correct place.

Guess i should use chrome more often! Thanks for touching on this subject, Looking forwards to this new series.

What screen reader was that? Can someone recommend me some screen reader for testesting on Linux or web extension?

Awesome !!!!

Is equivalent to ?

I see that the input/search has an aria attribute of aria-haspoppup which I have not used before and that it indicates the listbox. How does a screen reader user know that the list box was presented/popped up? I didn't hear anything to indicate that I could use the arrows to hear the listbox options.

Great step towards accessibility! regarding simantic structure can you do the demo with the screen reader? it will be more practical.

What is the impact on the SEO ?

Thank you to this new series accessibility I want to become a accessibility testing please tell me how I learn more about accessibility thank you very much

ctrl/command + shift + c save my life! Thank you! I didn't know that lol...

Rob didn't say hi back

Styling links to look like buttons is material dishonest. If you're taking the time to distinguish them semantically to an unsighted user, you should equally distinguish them to a sihted user.

It would be good if one day I could save the CSS and HTML changes to local files directly in my browser

Apparently, I don't know HTML 😶

Why do you use old chrome? New chrome has rectangular tabs.