Chad Chelius, ADS and Dax Castro, ADS unravel accessibility for you in easy-to-understand ways that propel you down the road of remediation and understanding of the Web Content Accessibility Guidelines. Our training styles take complex accessibility topics and focus them into digestible chunks of information that anyone can understand. Visit our website www.accessibilityunraveled.com or subscribe to our podcast Chax Chat on all major streaming platforms.
Regarding artifacting leaders in a TOC, you can also go into the link tag and in "Alternate Description for Links," add the chapter title and page number (e.g., Chapter 1, 1).
Thank you for this; I saw this demonstrated in one of Allyant's training webinars, but it was so much information in such a short amount of time, it really didn't stick.
Commented on the Facebook page a couple of minutes ago but commenting here too. Tried the Pdfix on both mac and Windows and it comes up with an error related to VeraPDF and java. Was merely trying the lite version so see what it could do, especially as the mac environment has so few options besides Acrobat Pro. Wrote the company about the error, and heard back a few hours later of the need to install java for the program to work.
Another question in reference to this topic. I have noticed that Adobe Acrobat creates a table when clearly there is no table in the document. Any idea why?
This video was excellent, as are all of your accessibility tutorials. I have a question regarding the table tags. Sometimes, text is mistakenly marked as a table but there isn't one in the document. I will try to retag the document, which sometimes resolves the problem. However, I am unsure if it's appropriate to change the <TH>, <TD> and <TR> tags to <P>? That is accepted by the accessibility checker, but I don't know if this is the correct way to remediate the issue.
Can you do the document race live and give us the document so we can do it live with you? And then go through it at the end so we can all check our own correctness?
Great discussion Chad and Dax. I particularly appreciated the UX of ATs and how there are different navigation patterns depending on user’s preference and on vendor shortcuts.
Congratulations! That is so wonderful to hear that you received your ADS. We are looking at creating an ADS study course sometime between now and the end of the year to formally help others.
So glad you enjoyed it. You would be amazed at how long animation takes for something like this. I wanted to do an entire series but it is just time prohibitive.
Hi Chad and Dax. I’m an accessibility newbie. I’m afraid my brain has become completely scrambled watching this. For us newbies who are still trying to get to grips with the basics, it’s really confusing to be told that there are multiple ways of achieving the same objective. I appreciate that this video is probably intended for people who are already clued up on accessibility and tags and an intellectual debate of one method over another might be appreciated by them. However, I just need to know what the structure needs to be. It would also be really good if you could go slowly and provide explanations when doing the screen shots as I have to keep pausing the video and going back multiple times to watch the really important bit which gets rushed over. I still don’t understand how to properly tag my QR code 😢
Great point Alfie. This is why we have classes for such things. No worries though. You simply need to apply alt-text to your QR Code image that says "QR Code for (Whatever)" or ensure there is descriptive text before the image. Then you create a link just like you would any other hyperlinked image or text. The podcast is really not meant to be a tutorial but more of a discussion. Hope that helps.
The reference tag nested in TOCs is also PDF/UA standard (per page 16 of the PDF associations Tagged PDF Best Practice Guide: Syntax PDF: "Example C: "substructures in a <TOC> & <TOCI> context containing <Reference> & <Link>"). Blargh! I know that when testing I find the double link speak frustrating, so I'm sure that native screen readers do, too (although NVDA uses are accustomed to it). My struggle is that by removing the reference tags, then I feel untruthful marking the PDF as PDF/UA conformant.
But why? In the end why do we follow the standard? Isn't it to ensure a good user experience? Isn't the standard there to unify solutions so that all screen readers have the best chance of presenting accurate content to the user? So then, what happens when the standard doesn't actually do that? The standards people say it is the screen reader programs fault. But the only ones paying the price are the end users who get to hear "Link, Link." Remember, the goal in all this is a good user experience. Therefore I will always side with the user experience when there is a choice to make between following a standard and knowing the good user experience as long as it does not create more barriers in the process.
@@PDFA Just my own internal aversion to labeling a PDF PDF/UA compliant when I know I didn't fully meet the standard. Today, I'm getting over that aversion-no reference tags will be found in my TOCs moving forward! The more important truth also is that hearing "link, link" is annoying and I change that.
Very helpful! I've seen some tutorials say that the page number at the end of the leader is also not necessary and should be marked as an artifact. Is that correct? Similarly, a TOC that I'm working with has a number at the beginning of each section of the TOC (i.e. 1. Introduction). Is that something that should be marked as an artifact as well?
Do both of the alt texts (image and link) voice if you have both of them? When I've done this in the past, Adobe gives me an alt text error because it's one object (with another inside) with two alt texts assigned. And then I think only the alt text in the parent tag voices, not both. What is your experience when using a screen reader when you've tagged something like this?
@@a11y Yeah, I did both content key and alt text for images for the link. Still only the parent tag is voiced in both scenarios where either is the parent.
@@a11y You were saying that a screen reader will voice BOTH the Figure tag alt text AND the Link tag content key and/or link alt text if you nest one in the other, right? When I populate the alt text/content key/link alt texts correctly (in ways that work on other documents for those tag types), only the parent tag is voiced if I nest them like that. Could you actually do a short video to demonstrate what it should sound like with a screen reader if you nest them correctly and get all their settings/texts right? I was hoping that would be at the end of this video but it wasn't.
There's also a faster way to find a link and put it where you want it. You select the Link tag where you want it to go, then go up to the tag menu (above the Tag tag) and click Find and use the menu to find your unmarked link. When you locate and then tag the link through the Find dialogue box, the OBJR will be right in that Link tag you originally selected.
As I'm doing it right now, I just realized that I actually right-click the Link tag where I want the OBJR to go, select Find from the menu that comes up, then find and tag the element, and the OBJR lands right inside that Link tag.
Thank you so much for the "Disable New Acrobat" mention. I couldn't find any reason for the layout switch, so I was happy to go back to a familiar landscape.
Thanks for this discussion. For voice memos should it be "one message one idea" and rather send more messages than long messages… of is this also breaking for those that need voice mail as first choice.
8:28 Excellent conversation! Recently when I hired an accessibility specialist at my company, the first thing I looked for was an accessible resume. It blew my mind how few accessible resumes came in!
Loved this episode! I don't remember seeing that feature about the PDF/UA identifier either. I think it's new. Thanks for sharing! I agree about Funkify. Great tool, especially for demonstrating to others about certain disabilities.
