Great work on the functionality, by bringing it to the forefront of the Inspector it will make it much harder for developers to be as dismissive about accessibility concerns as we have generally tended to be.
@neilosman44407 жыл бұрын
Also use chrome://accessibility/ to inspect the a11y tree
@ayeshab56992 жыл бұрын
Thank you! Very helpful and easy to understand for beginners.
@puphuc94153 жыл бұрын
The unicorn head is reallly distracting :))))
@LaloHao4 жыл бұрын
Thanks for the teapot reference, reminded me of FP
@michongoma75987 жыл бұрын
Good Video Rob
@dmitriysmirnov4574 жыл бұрын
Watching this in 2020 and it's strange to see G+, haha
@YageSpirit7 жыл бұрын
I noticed that Angular 1.6.x seems to interfere with some of the aria attributes work in Bootstrap 4.0 Alpha. I am guessing that I will need to work on things like UI Bootstrap did since the CSS framework changed hooks.
@HoaPham-wc4kq3 жыл бұрын
Thanks for this useful content
@chandlerzhu97352 жыл бұрын
I hope chrome has a built-in screen reader someday
@fredbcarneiro7 жыл бұрын
What a amazing thing to do with websites! Thank you for the insight.
@zeinabkamel94396 жыл бұрын
Great Video, Thanks a lot. I just have a question, is there a way I could possibly override some of the things that get to be said anyway regardless of what I wrote. i.e "You are Currently inside the html element ......." ?
@thiruppathimuthukumar71717 жыл бұрын
Dint know any the a11y section in dev tools.. it's cool.. thanks
@sneto_dev_br7 жыл бұрын
cool, it's a very important subject. thx
@rasingangi48757 жыл бұрын
I wonder...What is the latest version for Chrome for Android?(lollipop 5.02)
@waledhajaz30227 жыл бұрын
woow
@TheAlkhemiaStudio7 жыл бұрын
he looks kinda tired tho
@letswatchrob7 жыл бұрын
Alkhemia Studio lol thanks...
@Gettomix2227 жыл бұрын
what is the point in taking care of accessability? is there really a need? i mean.. great that there is the opportunity to support such.. but why?
@letswatchrob7 жыл бұрын
A few important reasons: 1. There are about 1 billion people across the world with some form of disability. So building an inaccessible experience means you'll miss out on those users. Blind people want to order pizza and go on vacation too! 2. In some countries, like the United States, it's against the law to build inaccessible applications. You will get sued and many large companies have been. 3. Adding in good accessibility usually translates into components that are easier for everyone to use. For instance, the trackpad on my laptop literally broke this morning so I'm doing a bunch of stuff using the keyboard today. I'm *very* thankful that apps like gmail and tweetdeck have good built-in keyboard support 4. It's a fun engineering problem to work on. I find that most folks who don't care about accessibility don't understand how it works. Once you have the basics down, it's quite fun adding in good semantics and verifying your components work well with a screen reader. I get a lot of personal satisfaction out of knowing I built a component that looks great, AND is highly usable.
@AnthonyShuker7 жыл бұрын
god forbid anyone with a disability wants to use the internet
@Anan6CMS7 жыл бұрын
Exactly! It also also allows us to answer the WHY question. Just imagine that the labels in your example where not visible. We would just see a bunch of input fields without knowing WHY they're there ... A simple script could alert us the contents of the label associated with the input ...