I love the emphasis on the manual. This is especially important as vendors ramp up their A.I toolsets and products and claims that might be hard to prove. I love automating as much of my remediation work as possible (and we have 8,000+ PDF) but a lot of it is manual.
Great presentation Tolu, thank-you! I thought the points about avoiding placeholder text, and also placement of the language profile selector in the header, were both great points. I will certainly take not of these one which were new to me.
This is a very informative talk, and I appreciate it, but using words like "unfair" and "ableist" (18:25) create a victimhood mentality and do nothing to encourage developers to make the right choices. Rather, use words that evoke empathy, like "unthoughtful" or "unhelpful," and "we can do better." I'm not disabled in any way, praise God, but I have great compassion for those who are and that's why I watch this kind of content. Not because I'm required to, but because I want to create more accessible apps. What I don't understand is why browsers don't have a setting for toggling an accessibility / WCAG signal that websites can read and automatically switch to the accessible version of their site. We have CSS media queries that are used for mobile screens, so why don't we have one to toggle WCAG compatibility?
Excellent webinar! Speaker is clear, concise and very engaging style! Thank you!
Thanks for the webinar. All questions at the end were answered to the point.
Thanks a lot! I went through a lot of information, but here I found the most important points from very interesting point of view (of manual testing)
I love the emphasis on the manual. This is especially important as vendors ramp up their A.I toolsets and products and claims that might be hard to prove. I love automating as much of my remediation work as possible (and we have 8,000+ PDF) but a lot of it is manual.
Great presentation Tolu, thank-you! I thought the points about avoiding placeholder text, and also placement of the language profile selector in the header, were both great points. I will certainly take not of these one which were new to me.
Thank you, great webinar
34:50 great tip! Take them back .
Amazing Webinar! Thanks for sharing :)
Awesome 👏
Is it okay to forgo alt attribute instead of empty alt for decorative images?
This is a very informative talk, and I appreciate it, but using words like "unfair" and "ableist" (18:25) create a victimhood mentality and do nothing to encourage developers to make the right choices. Rather, use words that evoke empathy, like "unthoughtful" or "unhelpful," and "we can do better." I'm not disabled in any way, praise God, but I have great compassion for those who are and that's why I watch this kind of content. Not because I'm required to, but because I want to create more accessible apps. What I don't understand is why browsers don't have a setting for toggling an accessibility / WCAG signal that websites can read and automatically switch to the accessible version of their site. We have CSS media queries that are used for mobile screens, so why don't we have one to toggle WCAG compatibility?