Congratulations Rob. The video is very clear and precise regarding the importance of implementing good practices when programming web applications. It is also clear how important this is for people with reduced abilities and poor vision.
Thank for this informative video, a11y is very important, but spreading the word and creating awareness is also important, you are contributing to that goal.
This is a great video Rob, as demystifying accessibility is one of the key ways to open up accessibility knowledge in my view. One point though, when you interact with the size dropdown at 5:20 using the up and down arrow keys, I'm not hearing any feedback from Voiceover. Did the audio get edited out there, or is that actually a problem in that site?
In the video description: "Sidenote: at 5:18, not sure why the video didn't announce the different sizes but I tried again later and it was working. Maybe a VoiceOver quirk. "
Rob ai am a designer so from that point of view what do you recommend (causes, articles, general material, etc) to get better at auditing for accessibility? Thanks
Thank you so much for how you audit websites! I'm new to this and wondered about color/contrast for images or icons associated with text. For example, sometimes the social media icons next to the text of facebook, or twitter have really poor contrast. Is this a WCAG error, or is it sufficient if the text has enough contrast? I thought it would be an error in case someone with a cognitive impairment and low vision relies on using those icons. In short, when do you check for the color/contrast of images/icons and when do you ignore them to help companies achieve WCAG 2.0 standards?
I don't know any official guidance on this topic. However my best assumption is as long as you are suspecting. As long as the *text* has sufficient contrast it is fine, since that is the most important content. A lot of brands have guidance requirements on how you are allowed to display their logos. Those requirements don't change based on accessibility needs.
Megan Kennedy if you low vision, contrast might play an important role. But if you are using a screen reader, the altattribute is very important when using images.
Good one , but can you please help me on this .. I have some doubts, how to test the elements in the web application like Radio group, checkbox group, Menu etc... for example : 1. Assume that you have radio group , how we can test this group like how to move between radio buttons using Tab or arrow keys. 2. Assume that you have Check box group, again same question here , how to test this check box group , do we need to use arrow keys or tab key to move between the checkbox and how we can enable and disable the checkbox. Is there any standards define to test. I am having big confusion here.
I tried using the google chrome extensions shown in this video, but there are deprecated. Anyone know other tools that I can use to validate contrast and other accessibility issues? Thanks
Google Chrome developer tools are implementing more and more a11y tools, please check them out. You have contrast ratio check built in for example. The other worthy toolset I use is the Audit part or Lighthouse if you want. Amazing tool, also for performance etc., not just a11y per-se.
You are right of course that skip links aren't mandatory, but they are really helpful for some - and not just for blind users. Screen reader users do have the option of jumping around the page from heading to heading or to specific landmark roles (main), so that's fine. But sighted keyboard only users do not have that option in any of the major browsers - so that's one place where skip links are very useful, and why it's also important to ensure that yopur skip link becomes visible when it gets keyboard focus. It would be useful if browsers did introduce corresponding jump functionality but I don't see much sign of that happening.
![Stromae, Pomme - “Ma Meilleure Ennemie” (from Arcane Season 2) [Official Visualizer]](http://i.ytimg.com/vi/1F3OGIFnW1k/mqdefault.jpg)
Congratulations Rob. The video is very clear and precise regarding the importance of implementing good practices when programming web applications. It is also clear how important this is for people with reduced abilities and poor vision.
Thank for this informative video, a11y is very important, but spreading the word and creating awareness is also important, you are contributing to that goal.
This series is beautiful!
This is great! I did most of this already, but you showed off some things I didn’t know.
Your tutorials are awesome. Thank you.
Thanks, Rob! Awesome overview of your testing process.
Great explanations and information. Thx!
Super helpful! Thank you ☺🙏
vo is not notifying when u were moving on in the dropdown from small to medium to large to xl is also a bug
This is a great video Rob, as demystifying accessibility is one of the key ways to open up accessibility knowledge in my view.
One point though, when you interact with the size dropdown at 5:20 using the up and down arrow keys, I'm not hearing any feedback from Voiceover. Did the audio get edited out there, or is that actually a problem in that site?
Yeah. I thought that too.
In the video description: "Sidenote: at 5:18, not sure why the video didn't announce the different sizes but I tried again later and it was working. Maybe a VoiceOver quirk. "
Great information sharing. Very clear and current on web accessibility. Thank you.
Thanks Rob, for the useful check-list.
Very good primer. I'll share with our developers!
Excellent summary. Thank you.
Thanks for this important info. It is awesome. I need your help on how to make a final analysis report in excel to give to the client.
Thanks, This is awesome list to check accessibility.
Anyone know a video that teaches mobile ada like this one? That would be really helpful
Yes i can teach u in ios and android
Rob ai am a designer so from that point of view what do you recommend (causes, articles, general material, etc) to get better at auditing for accessibility? Thanks
Good efforts
Do you that the W3C online validation is accurate with accessibility features, or does not detect everything? Thanks a lot.
The browser plugin Tota11y is also very useful
I wonder how much control I have over these things on a Six site?
*Wix
Hi Rob, I'm wondering if these basics stuff are already covered in automated tool like axe? navigating thru tab and screenreader.
any free tool which does the accessibility testing for the entire application and not page by page?
Helpful content :)
Excellent. Thanks.
Thank you
Hey, is it a normal thing for a pop-up menu not read the available options when navigating with up and down arrow keys?
Can please ask u r doubt with more clarity ill help u
For the test you might consider turning the sound / voice feedback on. 😋
Nice, Thanks 👍
Or how you can include AXE audit with automation? Like what tools to use with what?
AXe will through some accessibility issues
Thank you so much for how you audit websites! I'm new to this and wondered about color/contrast for images or icons associated with text. For example, sometimes the social media icons next to the text of facebook, or twitter have really poor contrast. Is this a WCAG error, or is it sufficient if the text has enough contrast? I thought it would be an error in case someone with a cognitive impairment and low vision relies on using those icons. In short, when do you check for the color/contrast of images/icons and when do you ignore them to help companies achieve WCAG 2.0 standards?
I don't know any official guidance on this topic. However my best assumption is as long as you are suspecting. As long as the *text* has sufficient contrast it is fine, since that is the most important content. A lot of brands have guidance requirements on how you are allowed to display their logos. Those requirements don't change based on accessibility needs.
Megan Kennedy if you low vision, contrast might play an important role. But if you are using a screen reader, the altattribute is very important when using images.
For barand icons and images color cobtrast is exception we won't check
Good one , but can you please help me on this ..
I have some doubts, how to test the elements in the web application like Radio group, checkbox group, Menu etc...
for example :
1. Assume that you have radio group , how we can test this group like how to move between radio buttons using Tab or arrow keys.
2. Assume that you have Check box group, again same question here , how to test this check box group , do we need to use arrow keys or tab key to move between the checkbox and how we can enable and disable the checkbox.
Is there any standards define to test. I am having big confusion here.
Account 1 use the x key to move forward between checkboxes and shift x to go back
Use left and riht or up and down arrow keyz based on funcationality. Once screen reader mode off
Love your style of asking to subscribe or look for more content on the channel
On all the pages I visit and I hit ctrl+cmd+u it says that headings is empty. Am I doing something wrong?
Press h to identity heading in page. Or h1 h2 h3 at atime h and 1 keys
Hi Rob, thank you so much for info, Is there any other we need to check for as part of UI testing?
11 pm
I tried using the google chrome extensions shown in this video, but there are deprecated. Anyone know other tools that I can use to validate contrast and other accessibility issues? Thanks
Google Chrome developer tools are implementing more and more a11y tools, please check them out. You have contrast ratio check built in for example. The other worthy toolset I use is the Audit part or Lighthouse if you want. Amazing tool, also for performance etc., not just a11y per-se.
If want all accessibllity testing tools extensions ill help u. Wbicb tool u want
Awesome, thanks!
Brilliant
I would argue though that you shouldn't HAVE to go for a skip link. You should design your page in order that you the main content is obvious
Soochoup
You are right of course that skip links aren't mandatory, but they are really helpful for some - and not just for blind users.
Screen reader users do have the option of jumping around the page from heading to heading or to specific landmark roles (main), so that's fine. But sighted keyboard only users do not have that option in any of the major browsers - so that's one place where skip links are very useful, and why it's also important to ensure that yopur skip link becomes visible when it gets keyboard focus.
It would be useful if browsers did introduce corresponding jump functionality but I don't see much sign of that happening.
Soochoup imagine you have to browse past the top content every time. Nain menu, social menu etc. nope that button must stay. 👍🏻
Thanks for tips :)
also pls Tell me y m not getting this option of accessibility properties in my chrome
For which tool do u want
thank you 😘
helpful, sir
Thanks!
Hey
𝕐𝔼𝕊.. Am trying