TPG Interactive (TPGi) - Your Accessibility Partner We help achieve end-to-end accessibility in your organization’s websites, applications and processes. Our consulting services include accessibility testing and evaluation, WCAG/Section 508 compliance audits, VPAT analysis and production, training, user testing and research, design reviews and strategic planning to embed accessible user experience into all aspects of your product development lifecycle.
18:30 How does it make sense that we don't know what technical updates some with EAA? Is that different from the "accessibility requirements" set out in Article 4?
Hi Paige - You can learn about the formatting Exclusion Patterns in the ARC User Guide, which is located in your ARC account. if you need assistance accessing the user guide, please contact arcsupport@tpgi.com
Hey Jared, Really EXCELLENT VIDEO!!! There is so much misinformation out on the net about contrast, this video really should be required viewing! (And wow, it was 2017, two years before I started working on the WCAG perception problem). MORE: A couple additions from recent research, regarding perceptually uniform contrast, my current research focus: Regarding the red text on black that WCAG 2 says is 5.25:1, and the same red text on white that WCAG says is 4:1 - this is one of the more significant failures of the WCAG 2 contrast. And not just for standard vision, it is an even more serious problem for color insensitive vision, especially protanopia. Since protans see red darker, they see the red on black version with substantially lowered luminance, lowering the contrast so much so it can become unreadable. On the other hand, they see the red on white with greatly enhanced contrast. This is one place where WCAG 2 contrast math does the opposite of what it needs to do to help color insensitive vision. The candidate replacement math/method (APCA) shows the red on black as less than Lc 40 (which means less than about 3:1 per WCAG2) and the red on white is about Lc 62 (which is sort of like 4.5:1). For the record, the red from the picker was #ff3710 (that might be slightly different than that used for the video, due to different color encoding). Another issue is that the current peer reviewed research on CVD, including studies within the last couple years, shows that deutan and protan have standard, normal contrast sensitivity. The one exception is that as protan sees red darker, the one place they have a contrast loss is for red on black. This is also true for the rare achromatopsia, also lacking L cones (and who also need AT due to low vis and photophobia). So one thing we can say is that for sighted users, even deutan, protan, and tritan, red on white IS accessible but red on black is very poor. All sighted users need good luminance contrast for readability, and standard and CVD are not different in this regard for readability (The common CVD types demonstrate better than standard visual function otherwise, including studies showing d/p/t having better acuity due to lower noise),. The important difference of course is distinguishability (i.e. colors on maps, etc.) and that's where color (hue) can not be the only means of conveying information. Orange/Brn vs White/Blue With the other question, the brown on orange vs blue on white, where WCAG 2 says they are both 4.5:1, one of WCAG 2's failings is over-rating darker colors. A perceptual method finds the orange/brown to be Lc 46.4, and the white/blue as Lc 67.9. Here are links with those colors to demo: orange/brown Lc 46.4: www.myndex.com/APCA/?BG=ffa24e&TXT=8c342b&DEV=G4g&BUF=YT white/blue Lc 67.9: www.myndex.com/APCA/?BG=f4f6f6&TXT=0079a3&DEV=G4g&BUF=YT I have a lot of information regarding APCA and the continuing research at git.myndex.com Thank you for reading! Andy
JAWS Inspect can be used on a Mac through virtual machine or via Bootcamp, but not on a regular Mac OS. Contact us if you still have questions: www.tpgi.com/contact/
20:07 "Start doing something for a few minutes every day and once that becomes habit, add to it." This is a powerful statement. Step by step. Baby step by baby step if we have to. :D 22:24 Joe Devon's father spoke ten languages? That's awesome! Which ones? And a Holocaust survivor? Man... that must've been tough.
Good work, Try it, It is free now only, Web accessibility tool atoall.com and webaccessibilitytool.com as per govt guidelines also. For 1 billion disabled and 3 billion regional people.
Hi and thank you for uploading this video. On the report, when you open a section such as Buttons, are they listed in the reading order the JAWS will read the text or is it listed randomly. Secondly, is the report as a whole listing of each item in the reading order the JAWS will reader will read out the information?
Finally got around to watching this. To the point towards the end of the video about voice design, one interesting development is that Google has actually moved AWAY from the use of earcons - little audio "trills" to denote certain things like links, instead of actually saying the word "link". So lots of interesting discussion there. Loved the talk... thanks, Eric!
I know it wasn't explicitly discussed because it's off-topic, but wouldn't he use of placeholder text in the form fields example be a labelling failure (SC 3.3.2) anyway, regardless of the colour/contrast problems?
Great talk, thank you. In the case that someone uses Role="heading" pair it with aria-level="Num"? Or at least that would be best practice as far as I understand. In regards to HTML labels I often see an input wrapped in a label for element. Except there is no accessible text. :-)
From experience screen readers don't convey styling such as bold, italic. So if that is the only means used to identify a link it is not sufficient. So regardless of whether you use CSS font-weight, HTML <b> or <strong> the result is pretty much the same. It is only a visual indicator.
