1 00:00:04,580 --> 00:00:06,790 All right so it is 2 o'clock. Welcome, everyone. 2 00:00:06,790 --> 00:00:13,940 Thank you for joining us again for another addition of Equidox Webinar Wednesdays Advanced 3 00:00:13,940 --> 00:00:19,930 Table Training. So today we're mainly going to be talking about advanced table remediation 4 00:00:19,930 --> 00:00:20,930 techniques. 5 00:00:20,930 --> 00:00:26,410 So I have quite a few different examples pulled up of different tables that can present some 6 00:00:26,410 --> 00:00:28,080 unique challenges. 7 00:00:28,080 --> 00:00:35,750 So if you deal with a lot of tables, this should be a helpful guide to showing you like 8 00:00:35,750 --> 00:00:40,110 the best and most efficient ways to deal with those unique tables. 9 00:00:40,110 --> 00:00:44,680 So, as always, what I'd like to mention is if you have any, follow-up questions. 10 00:00:44,680 --> 00:00:50,070 Or if you are not a current user or client of Equidox, and you'd like to have a more 11 00:00:50,070 --> 00:00:55,680 personal one-on-one demonstration where we can talk about your challenges with PDF remediation 12 00:00:55,680 --> 00:00:56,680 and any 13 00:00:56,680 --> 00:00:59,690 of your use cases. we can look at some of your specific documents and challenges that 14 00:00:59,690 --> 00:01:00,690 you have. 15 00:01:00,690 --> 00:01:09,430 Please feel free to reach out to us at EquidoxSales@Onixn.com website is Www.Equidox.co and we also can 16 00:01:09,430 --> 00:01:16,000 be reached by phone at 800.664.9638. 17 00:01:16,000 --> 00:01:19,930 So before moving into the demonstration, I just want to quickly remind everyone that 18 00:01:19,930 --> 00:01:24,260 Equidox is a division of Onix networking. 19 00:01:24,260 --> 00:01:26,270 So Onix is headquartered in Cleveland, Ohio. 20 00:01:26,270 --> 00:01:31,320 We have employees all over North America. so we've been in business for about 28 years, 21 00:01:31,320 --> 00:01:36,320 and we're primarily a Google Cloud partner, a cloud consultancy as well. 22 00:01:36,320 --> 00:01:41,370 We're also partnered with Amazon Web Services as well. our mission is to improve organizational 23 00:01:41,370 --> 00:01:44,390 efficiency through cloud computing solutions. 24 00:01:44,390 --> 00:01:51,450 Now Equidox is a division of Onix, and we are primarily focused on PDF accessibility. 25 00:01:51,450 --> 00:01:54,420 So we have the best-class PDF remediation software. 26 00:01:54,420 --> 00:02:00,470 We also offer professional remediation services for organizations. that have large volumes 27 00:02:00,470 --> 00:02:03,729 of documents, and they don't have the bandwidth to deal with that type of volume. 28 00:02:03,729 --> 00:02:08,890 You can outsource to our services. We also can provide all kinds of accessibility services 29 00:02:08,890 --> 00:02:11,220 regarding training or website help. 30 00:02:11,220 --> 00:02:15,700 Really anything related to digital accessibility, and our mission is to ensure that digital 31 00:02:15,700 --> 00:02:21,050 information reaches everyone through accessibility solutions. 32 00:02:21,050 --> 00:02:26,290 So this is just a quick slide with a few of our customers. So I'm just gonna let those 33 00:02:26,290 --> 00:02:32,310 play through. and we're gonna jump now into the Equidox demonstration. 34 00:02:32,310 --> 00:02:39,030 So if anyone is able to stay for the duration of this webinar, we will insert the video 35 00:02:39,030 --> 00:02:44,870 of it here into the slide deck, and you'll receive this after the call is over. 36 00:02:44,870 --> 00:02:50,660 Okay, So well now, I'm in Equidox our PDF remediation tool. 37 00:02:50,660 --> 00:02:55,260 So anyone on the webinar that is a current user, this should look fairly familiar to 38 00:02:55,260 --> 00:02:59,040 you, but for anyone that isn't a current Equidox user. 39 00:02:59,040 --> 00:03:03,849 I just want to get started with a simple example of how we can remediate a table. 40 00:03:03,849 --> 00:03:09,470 So if I were to open up a simple standard document like this where there’s a simple 41 00:03:09,470 --> 00:03:13,980 table inside of this page. 42 00:03:13,980 --> 00:03:17,700 Sometimes you'll arrive at a document and you will see a setup of the reading zones 43 00:03:17,700 --> 00:03:22,660 that will look something like this, and using the HTML preview to just look at how this 44 00:03:22,660 --> 00:03:24,410 would be read by a screen reader, 45 00:03:24,410 --> 00:03:29,310 You can probably tell that this is not actual table structure each one of those cells inside 46 00:03:29,310 --> 00:03:34,000 of that table will just be read in this particular order, rendering this pretty much useless 47 00:03:34,000 --> 00:03:38,110 to a screen reader, user, because they're not really sure which row or column that they 48 00:03:38,110 --> 00:03:43,319 are currently situated in so in Equidox. All we need to do is draw a single zone over the 49 00:03:43,319 --> 00:03:45,230 top of the entire table. 50 00:03:45,230 --> 00:03:50,260 I'll use my keyboard shortcut and hit “T” to change the zones to a table, and that will 51 00:03:50,260 --> 00:03:53,240 give me this button here for the Table Editor. 52 00:03:53,240 --> 00:03:59,140 So when I press the Table Editor button this will isolate the table, and I will see the 53 00:03:59,140 --> 00:04:05,080 green gridlines here, which I'm free to move around and get a line manually, if I'd like 54 00:04:05,080 --> 00:04:08,940 so you can see that the green gridlines, for the most part, are lined up with the rows 55 00:04:08,940 --> 00:04:09,940 and columns. 56 00:04:09,940 --> 00:04:15,570 There are a few adjustments that can be made so to make those adjustments. If I don't want 57 00:04:15,570 --> 00:04:18,620 to do that manually, I can also use our Table Detector. 58 00:04:18,620 --> 00:04:24,120 So the Table Detector is using computer vision and machine learning to better understand 59 00:04:24,120 --> 00:04:29,259 the cell structure of these tables, and it will automatically draw those gridlines in 60 00:04:29,259 --> 00:04:30,990 the location that they need to be. 61 00:04:30,990 --> 00:04:36,800 So. so we remember what the HTML preview looked like just a moment ago, with no table structure 62 00:04:36,800 --> 00:04:37,800 whatsoever. 63 00:04:37,800 --> 00:04:42,870 But if I were to refresh that preview you'll see that now I have a real table Now this 64 00:04:42,870 --> 00:04:44,389 is rendered in HTML. 65 00:04:44,389 --> 00:04:48,539 But the beautiful thing about Equidox is that it will take this HTML structure and it will 66 00:04:48,539 --> 00:04:52,039 automatically convert it into a PDF tag tree for you. 67 00:04:52,039 --> 00:04:58,930 So anyone that has done manual PDF. for remediation of tables, you know, in a a tool where you 68 00:04:58,930 --> 00:05:04,610 have to tag every individual cell. there are so many steps associated with working through 69 00:05:04,610 --> 00:05:07,189 tables that a simple little table like 70 00:05:07,189 --> 00:05:10,960 this can take upwards of, you know, 1015 min. In some cases. 71 00:05:10,960 --> 00:05:15,699 In many cases it can take a lot longer. Tables, of course, get much more complicated than 72 00:05:15,699 --> 00:05:20,289 this, So you can see that within Equidox we have the automation of with the detection 73 00:05:20,289 --> 00:05:24,270 tool and just a much cleaner workflow in an interface 74 00:05:24,270 --> 00:05:29,930 that allows for simple and fast table remediation, even if you are a novice user. 75 00:05:29,930 --> 00:05:35,659 Okay, so let's jump out of this document. forgive me as I jump around from documents 76 00:05:35,659 --> 00:05:38,870 to documents. So I wanted to make sure that we covered a bunch of different bases. 77 00:05:38,870 --> 00:05:43,180 So I'm gonna do some simple table I that was a simple table, and I'll jump into a slightly 78 00:05:43,180 --> 00:05:45,189 more complicated example here. 79 00:05:45,189 --> 00:05:51,319 So. So this this table, as you can tell, is quite large, quite dense. 80 00:05:51,319 --> 00:05:57,430 This can be kind of intimidating to look at there's also a multiple column headers in 81 00:05:57,430 --> 00:05:58,689 this particular table. 82 00:05:58,689 --> 00:06:03,639 So you have different levels of column headers here that all correlate with the table data 83 00:06:03,639 --> 00:06:04,639 which falls below. 84 00:06:04,639 --> 00:06:10,080 Now it's the same concept where I'm just gonna draw a single table on top of, or a single 85 00:06:10,080 --> 00:06:16,129 zone on top of the table as I just drag it all the way to the bottom can Then again. 86 00:06:16,129 --> 00:06:21,530 Press t on my keyboard and the Table Editor Button will appear so I'll press the Table 87 00:06:21,530 --> 00:06:27,110 Editor Button and I'm gonna zoom out a bit to make this a little bit easier. 88 00:06:27,110 --> 00:06:31,249 To see. But you can tell here that there's so much going on that equodox didn't even 89 00:06:31,249 --> 00:06:32,650 bother to draw the roads. 90 00:06:32,650 --> 00:06:35,710 So again we're going to use our table detection sliders here. 91 00:06:35,710 --> 00:06:40,409 So, as I move these around, I can just find the best possible starting point where I don't 92 00:06:40,409 --> 00:06:45,229 have to make too many manual adjustments, so you can see that the sliders here are able 93 00:06:45,229 --> 00:06:48,129 to land pretty much spot on with all of 94 00:06:48,129 --> 00:06:51,449 the rows and the columns might need just a tiny little adjustment. 95 00:06:51,449 --> 00:06:56,219 If I just drag these a little bit left to right you'll see that I'm able to get everything 96 00:06:56,219 --> 00:06:58,419 pretty much aligned with the table. 97 00:06:58,419 --> 00:07:05,089 So, taking a look at the preview for this table now you'll see that I have pretty clean 98 00:07:05,089 --> 00:07:06,089 table structure. 99 00:07:06,089 --> 00:07:09,969 There are a few things that I need to adjust up here because of the way that this table 100 00:07:09,969 --> 00:07:10,969 is set up. 101 00:07:10,969 --> 00:07:16,610 There is some spanning that needs to be done within the within the column headers. So to 102 00:07:16,610 --> 00:07:17,610 span. 103 00:07:17,610 --> 00:07:22,569 This is another technique in Equidox, where you need to join multiple cells together. 104 00:07:22,569 --> 00:07:27,439 I can just click in one cell that I'd like to join hold down the shift key, and then 105 00:07:27,439 --> 00:07:29,500 select in another cell as well. 106 00:07:29,500 --> 00:07:34,139 So wherever I would like to span to a span button will appear at the top, or you can 107 00:07:34,139 --> 00:07:39,499 also use your keyboard shortcut and press s, and that will complete the spam. so just 108 00:07:39,499 --> 00:07:42,229 quickly going back to the preview you'll see that 109 00:07:42,229 --> 00:07:47,879 Now I have proposal falling. in one cell that sits at the very top of the table, so there's 110 00:07:47,879 --> 00:07:49,919 some other spanning that needs to be done here. 111 00:07:49,919 --> 00:07:54,629 I actually don't even need this extra row if I zoom in You'll see that Equidox was maybe 112 00:07:54,629 --> 00:07:57,129 thrown off because this this text. 113 00:07:57,129 --> 00:08:02,379 Was it's situated on 2 separate lines so I could do using the computer vision was thinking, 114 00:08:02,379 --> 00:08:05,889 Maybe that this is a situation where you've got 2 separate rows there. 115 00:08:05,889 --> 00:08:09,440 I don't really need that extra row, though so what I can do is I can either press the 116 00:08:09,440 --> 00:08:12,840 delete row button, or I can just press D on my keyboard. 117 00:08:12,840 --> 00:08:16,839 And that will that will basically merge down where it will get rid of that extra row that 118 00:08:16,839 --> 00:08:17,889 I don't actually need. 119 00:08:17,889 --> 00:08:24,729 Now I need to span across these 4 cells for the for this second level of column headers. 120 00:08:24,729 --> 00:08:29,219 So if I click in the cell hold shift and again. just clicking to the other cell, I'd like 121 00:08:29,219 --> 00:08:35,909 to join with, then press us Another situation here where I don't need this row you can see 122 00:08:35,909 --> 00:08:38,070 that the the double lines of text was 123 00:08:38,070 --> 00:08:42,440 to make, maybe thinking, or maybe made aqueducts think that this could be 2 separate rows. 124 00:08:42,440 --> 00:08:46,970 So again I'll just press d to get rid of that extra row, and then I will spam the trust 125 00:08:46,970 --> 00:08:52,020 fund cell over here, so I'll just again click in my 2 cells. and press s Now, if I go back 126 00:08:52,020 --> 00:08:53,020 to the 127 00:08:53,020 --> 00:08:58,210 HTML preview you'll see that we've cleaned this up quite a bit, so we have our we've 128 00:08:58,210 --> 00:09:02,700 kind of fixed the structure where it looks a little bit better in each Tml but we still 129 00:09:02,700 --> 00:09:03,700 have a few things 130 00:09:03,700 --> 00:09:09,740 to adjust. So the next thing to adjust is addressing the column and row headers. 131 00:09:09,740 --> 00:09:15,660 So by default products, assumes that your table will have one column header, which will 132 00:09:15,660 --> 00:09:19,900 be the top row, and the farthest left column, will be the row headers. 133 00:09:19,900 --> 00:09:24,330 That's just the default assumption. Now in this particular example because of the way 134 00:09:24,330 --> 00:09:25,480 this table is designed. 135 00:09:25,480 --> 00:09:30,440 I have a column header here I have another row of column headers here, and I even have 136 00:09:30,440 --> 00:09:32,910 a third row of column headers. 137 00:09:32,910 --> 00:09:37,390 So what I'll do is I'll come over here to the column header field, and as you can see 138 00:09:37,390 --> 00:09:39,010 these in the little text input fields. 139 00:09:39,010 --> 00:09:44,770 Here they are automatically set one to one, and if I just adjust that one to 3 that will, 140 00:09:44,770 --> 00:09:51,300 that will change the the output of this table where the top 3 rows will be tagged as column 141 00:09:51,300 --> 00:09:53,000 headers now the year 142 00:09:53,000 --> 00:09:57,490 over here, which is again by defaults going to be tagged as a row. 143 00:09:57,490 --> 00:10:02,150 Header. This is not necessarily a row header I think this is the table really. 144 00:10:02,150 --> 00:10:07,310 That's just consists of column headers. so I can change my row header from one to 0. 145 00:10:07,310 --> 00:10:13,060 Now, if I go back to the HTML preview what we'll see is I now have bold fonts for the 146 00:10:13,060 --> 00:10:17,320 top 3 rows, and this is just giving you that visual confirmation that you've 147 00:10:17,320 --> 00:10:24,900 adjusted the table to export with 3 with 3 rows of column headers. 148 00:10:24,900 --> 00:10:29,000 You'll also notice that in the far left column where the years are situated. 149 00:10:29,000 --> 00:10:34,690 You don't have that bold font anymore. indicating that the years themselves will be tagged as 150 00:10:34,690 --> 00:10:36,120 table data. 151 00:10:36,120 --> 00:10:41,020 So all of these cells here, where you're just seeing a standard font will be tagged as table 152 00:10:41,020 --> 00:10:48,320 data, and will be attributed to whichever series of column headers they fall under. 153 00:10:48,320 --> 00:10:54,210 So the another thing that I can talk about in this table, and is sometimes because of 154 00:10:54,210 --> 00:10:55,210 the computer vision. 155 00:10:55,210 --> 00:11:00,480 And you have such small fonts in this table, and things can be very tightly spaced. 156 00:11:00,480 --> 00:11:06,730 You might have a situation where the green gridlines fall maybe one or 2 pixels away 157 00:11:06,730 --> 00:11:07,730 from where they should. 158 00:11:07,730 --> 00:11:11,800 And if that's ever the case it would be extremely tedious to have to go through and individually 159 00:11:11,800 --> 00:11:20,160 adjust every single one of these rows, and new up like a pixel or 2, it could be done 160 00:11:20,160 --> 00:11:21,160 if you had the patients to 161 00:11:21,160 --> 00:11:27,650 do it, but that can be tedious and time-consuming, and so to address that occasional issue that 162 00:11:27,650 --> 00:11:29,920 you might run into on a very dense table. 163 00:11:29,920 --> 00:11:35,750 We have this tool here underneath the cells tab called nudge, where you're able to nudge 164 00:11:35,750 --> 00:11:38,050 the rows up or down. 165 00:11:38,050 --> 00:11:43,290 So if you, if you click the nudge button, your rows will move in unison where they will 166 00:11:43,290 --> 00:11:48,490 all just bump up one pixel out of time, so you can get things more closely aligned to 167 00:11:48,490 --> 00:11:49,490 where they need to 168 00:11:49,490 --> 00:11:57,150 be so there can be. Did I have a little bit of an Internet glitch? 169 00:11:57,150 --> 00:12:10,040 Wonder am I Still, we can still hear you interesting. I was wondering if I, my Internet cut out 170 00:12:10,040 --> 00:12:11,520 for a second. 171 00:12:11,520 --> 00:12:16,330 That's odd so we'll I'll show you in in fast pace. 172 00:12:16,330 --> 00:12:21,060 How quickly we can get back to where we were so again just going, talking about how to 173 00:12:21,060 --> 00:12:27,060 do this manually in a tool like, or a manual tagging tool table like this could really 174 00:12:27,060 --> 00:12:30,200 be a big problem where you're spending upwards 175 00:12:30,200 --> 00:12:35,490 of an hour to working through this single table, and then extrapolating that out over 176 00:12:35,490 --> 00:12:41,510 a document that might have dozens of tables in it, if not hundreds of tables and sort 177 00:12:41,510 --> 00:12:44,050 of financial reports and things of that nature you 178 00:12:44,050 --> 00:12:55,360 can spend a lot of time working through working through documents where you are actually spending 179 00:12:55,360 --> 00:12:57,730 just seconds on tables like this. 180 00:12:57,730 --> 00:13:04,320 So pretty dramatic pretty dramatic time savings, especially when you're thinking about longer 181 00:13:04,320 --> 00:13:05,550 documents, as I said before. 182 00:13:05,550 --> 00:13:09,110 So again we're back to the same table structure that I had I would just need to. 183 00:13:09,110 --> 00:13:17,800 Then again fix my column and row headers. Another feature of Equidox is the auto summarized 184 00:13:17,800 --> 00:13:18,800 mode. 185 00:13:18,800 --> 00:13:22,820 So if your current Equidox user, you may or may not know that this is a feature. 186 00:13:22,820 --> 00:13:29,980 But table summaries are one of those requirements for tagging tables where you need to have 187 00:13:29,980 --> 00:13:32,710 a table summary to give that end user. 188 00:13:32,710 --> 00:13:38,510 Who's using a screen reader, a general overview of what? what? that table consists of in terms 189 00:13:38,510 --> 00:13:40,000 of the structure of it. 190 00:13:40,000 --> 00:13:44,220 So what Equidox is able to do is programmatically write the table summary for you. 191 00:13:44,220 --> 00:13:49,810 If you turn the auto summarize mode on So by doing that, it's giving the user the indication 192 00:13:49,810 --> 00:13:50,810 that. 193 00:13:50,810 --> 00:13:52,790 Okay, they're 79 rows in this table there are 5 columns. 194 00:13:52,790 --> 00:13:55,190 It's letting them know that there are multiple column headers. 195 00:13:55,190 --> 00:14:00,130 There are no row headers it's letting them know that there are spans going on inside 196 00:14:00,130 --> 00:14:02,750 of the data cells and the the column headers. 197 00:14:02,750 --> 00:14:08,050 So it's giving them that that sort of navigation key right up front that that they can that 198 00:14:08,050 --> 00:14:11,830 can they can find helpful when they're trying to navigate through a very dense table like 199 00:14:11,830 --> 00:14:13,190 this that contains a whole bunch 200 00:14:13,190 --> 00:14:18,860 of cells which could be you know quite challenging to work through So again, we'll. we'll finish 201 00:14:18,860 --> 00:14:23,200 up with this table, and since I'm talking about the table summary what I'll do is for 202 00:14:23,200 --> 00:14:24,570 any existing users 203 00:14:24,570 --> 00:14:29,290 of Equidox. I will show you how to turn that auto summarized mode on in your profile. 204 00:14:29,290 --> 00:14:35,370 So if I just close out out, out very quickly if I go to my profile, what you'll see is 205 00:14:35,370 --> 00:14:39,110 and that's in the upper right hand corner, you can go to your profile, and there is an 206 00:14:39,110 --> 00:14:40,140 auto summarized mode 207 00:14:40,140 --> 00:14:44,820 dropdown. You can turn that on to default, to enable default to disabled, or you can 208 00:14:44,820 --> 00:14:46,360 hide it all together. 209 00:14:46,360 --> 00:14:50,500 So I have mindset to default to enabled so that way when I'm working on a table, I oxygen 210 00:14:50,500 --> 00:14:53,750 is automatically summarizing that table for you. 211 00:14:53,750 --> 00:14:58,450 There are quite a few advantages to that so especially if you're working on a long document, 212 00:14:58,450 --> 00:15:02,900 and perhaps collaborating on that document with multiple users or mediating tables. 213 00:15:02,900 --> 00:15:07,390 It will ensure that your table summaries are very much consistent where you don't have 214 00:15:07,390 --> 00:15:10,010 different people interpreting what they think. 215 00:15:10,010 --> 00:15:14,060 A table summary is supposed to be, it will also ensure accuracy. 216 00:15:14,060 --> 00:15:17,400 So if you're thinking about a table like this if I just jump back in for a second. 217 00:15:17,400 --> 00:15:22,350 But a table that has 79 rows. If you were trying to manually count how many rows there 218 00:15:22,350 --> 00:15:26,170 are, you could easily come up with a an incorrect number. 219 00:15:26,170 --> 00:15:29,120 So just for the sake of consistency and accuracy. 220 00:15:29,120 --> 00:15:34,150 The table summary feature is very very helpful you're also able to, of course, enhance that 221 00:15:34,150 --> 00:15:35,150 table summary. 222 00:15:35,150 --> 00:15:40,340 So you're able to insert more information about that table if you feel that it's necessary. 223 00:15:40,340 --> 00:15:43,720 But it's just nice that Equidox will programmatically write it for you, so that you don't have to 224 00:15:43,720 --> 00:15:48,610 necessarily think about table summaries as you're working through documents that are 225 00:15:48,610 --> 00:15:50,320 full of dozens and 226 00:15:50,320 --> 00:15:55,340 dozens of tables, and on the next table can you demonstrate the nudging again. So I'm 227 00:15:55,340 --> 00:16:00,180 going to ask for that, sure, and I'm not sure exactly what happened there, but I'm I'm happy 228 00:16:00,180 --> 00:16:01,180 to to 229 00:16:01,180 --> 00:16:09,290 nudge again. So let's talk about I want to talk about a table that contains a few different 230 00:16:09,290 --> 00:16:12,040 are different elements inside of the table. 231 00:16:12,040 --> 00:16:16,010 So a table like this, you actually have links inside of it. 232 00:16:16,010 --> 00:16:19,900 So if I were to use our zone detector, which many of you will be familiar with, we actually 233 00:16:19,900 --> 00:16:23,560 have links that are situated inside of this table. 234 00:16:23,560 --> 00:16:27,100 So this is very much a simple table by comparison to what we just looked at. 235 00:16:27,100 --> 00:16:29,360 There's really just a little bit of spanning that needs to go on. 236 00:16:29,360 --> 00:16:34,640 But when you have different elements nested inside of tables, Equidox is also able to 237 00:16:34,640 --> 00:16:35,640 handle this. 238 00:16:35,640 --> 00:16:41,680 So again, just drawing a single zone, capturing the entire table, opening up my Table Editor. 239 00:16:41,680 --> 00:16:46,640 And if you notice there's a slight blue hue that is covering up these different elements, 240 00:16:46,640 --> 00:16:52,220 indicating that the there is a another zone sat on top of that when we return to the PDF. 241 00:16:52,220 --> 00:16:56,400 When we turn to the entire PDF. page, not just looking at the Table Editor. 242 00:16:56,400 --> 00:17:05,481 So again, using my detection tools here. we will get this as close as we can, and that 243 00:17:05,481 --> 00:17:06,481 looks pretty good. 244 00:17:06,481 --> 00:17:09,309 I think I want. I might have drawn the table a little bit too large. 245 00:17:09,309 --> 00:17:12,939 I have one extra column over there. but now I'll just quickly go through the spanning 246 00:17:12,939 --> 00:17:20,799 process which we've already covered, and you can see here, we've got basically our our 247 00:17:20,799 --> 00:17:24,149 table set up as neat as we need so just maybe 248 00:17:24,149 --> 00:17:28,610 a couple of minor adjustments to the gridlines, and I'll add an extra row here for some reason 249 00:17:28,610 --> 00:17:33,559 it missed that row. But looking at the HTML preview because I have those links you can 250 00:17:33,559 --> 00:17:34,559 see 251 00:17:34,559 --> 00:17:36,960 I actually have the links inside of the HTML preview here, and these will actually go to 252 00:17:36,960 --> 00:17:40,549 the destination point as defined in the source. 253 00:17:40,549 --> 00:17:46,659 PDF: So whatever the encoded link was directing that user to these links will actually be 254 00:17:46,659 --> 00:17:49,690 active in the exported version, so really helpful. 255 00:17:49,690 --> 00:17:53,220 If you're dealing with like directories, and you have a bunch of email addresses, or in 256 00:17:53,220 --> 00:17:58,080 this example, you have different web pages with more information about the person's health 257 00:17:58,080 --> 00:18:01,269 needs so you're able to go straight to those 258 00:18:01,269 --> 00:18:05,889 links through the table structure. So it's a common thing that can occur in many different 259 00:18:05,889 --> 00:18:06,889 tables. 260 00:18:06,889 --> 00:18:10,090 But as you can see there's really nothing different in Equidox, the main recommendation 261 00:18:10,090 --> 00:18:15,710 that I would have would be just to address the links before you create the table, because 262 00:18:15,710 --> 00:18:18,450 that table is a very large zone. 263 00:18:18,450 --> 00:18:22,850 So once You've created it, it's can be kind of tedious to try to like draw zones outside 264 00:18:22,850 --> 00:18:28,559 of it and drag it in place, So I would recommend creating the links first which were in this 265 00:18:28,559 --> 00:18:30,210 case created automatically 266 00:18:30,210 --> 00:18:34,850 because they were encoded into the source file. But once you got those links identified, 267 00:18:34,850 --> 00:18:40,690 when you place that table on top, those links will be maintained, and they will, of course, 268 00:18:40,690 --> 00:18:42,649 have the anchor point that came in with the 269 00:18:42,649 --> 00:18:46,169 source file. So as you click on these links, you can see the anchor point is right here. 270 00:18:46,169 --> 00:18:50,770 So those are now going to be working links inside of this table structure. 271 00:18:50,770 --> 00:18:54,150 Now the the nudge feature I'm sorry I forgot about that. 272 00:18:54,150 --> 00:18:59,499 For a second the nudge feature again. where, if I go to the cells tab, I can nudge all 273 00:18:59,499 --> 00:19:01,139 of my columns left. 274 00:19:01,139 --> 00:19:06,119 So if you see they're all kind of moving just very slightly left, I can nudge them to the 275 00:19:06,119 --> 00:19:07,119 right. 276 00:19:07,119 --> 00:19:12,559 I don't really need to in this example because this is pretty a pretty well spaced out table. 277 00:19:12,559 --> 00:19:17,299 But sometimes I see like financial tables where like the previous example. you have 278 00:19:17,299 --> 00:19:20,080 so many rows and so many columns, and they're very, very small. 279 00:19:20,080 --> 00:19:23,909 You don't want to be in a situation we're having to like click on every single one, 280 00:19:23,909 --> 00:19:25,750 and just bump it up and down. 281 00:19:25,750 --> 00:19:29,879 You can spend a lot of time doing, that so we've been we've incorporated this nudge feature, 282 00:19:29,879 --> 00:19:34,470 where everything will move together in unison, depending and if you need to move the rows 283 00:19:34,470 --> 00:19:35,600 up or down or left or 284 00:19:35,600 --> 00:19:41,230 right Now I find that this is a tool that I don't use very often because the computer 285 00:19:41,230 --> 00:19:45,700 vision and machine learning is very good at detecting the table structure just automatically. 286 00:19:45,700 --> 00:19:50,740 So. But there, there will be the occasional, instance, where like I said you have a very 287 00:19:50,740 --> 00:19:53,220 dense table, and it needs just a slight adjustment. 288 00:19:53,220 --> 00:19:58,030 So it's it's there when you need it But I probably use it on less than 5% of the tables 289 00:19:58,030 --> 00:20:01,940 that I see 290 00:20:01,940 --> 00:20:10,869 Now let's Let me go to the next page here. This is another example of different elements 291 00:20:10,869 --> 00:20:13,380 that can fall inside of table structure. 292 00:20:13,380 --> 00:20:19,289 So here. This is not necessarily a table, but I can use it as an example just to keep 293 00:20:19,289 --> 00:20:21,990 us in the same document here. So we have a list. 294 00:20:21,990 --> 00:20:26,799 We have lists inside of table structure, so what I can do is I can just draw, like, I 295 00:20:26,799 --> 00:20:28,789 said before, with the similar to the links. 296 00:20:28,789 --> 00:20:32,700 I like to address the list first, and then create the table on top of it. 297 00:20:32,700 --> 00:20:35,119 So I'm just drawing a zone over the list and I'm! 298 00:20:35,119 --> 00:20:39,639 Hitting L. and Then I'm bumping the list detection Slider from left to right, so as I bumped 299 00:20:39,639 --> 00:20:40,639 that list detection. 300 00:20:40,639 --> 00:20:46,850 Slider I'm picking up the list items automatically So I'm just bumping it left to right and left 301 00:20:46,850 --> 00:20:50,649 to right. 302 00:20:50,649 --> 00:20:54,769 So I'm able to create those 3 separate lists inside of these 3 separate cells. 303 00:20:54,769 --> 00:21:01,860 Now, once I've done that I can draw that table zone on top, and I will again hit t and open 304 00:21:01,860 --> 00:21:03,369 up the table. 305 00:21:03,369 --> 00:21:13,070 Editor. So, because I have these lists here I don't really need any extra rows. 306 00:21:13,070 --> 00:21:19,619 I just need one column, and I don't need the extra rows there and then. 307 00:21:19,619 --> 00:21:28,299 I can just span across up here. So when I span and I take a look at the HTML preview, 308 00:21:28,299 --> 00:21:33,529 I don't know why that I must be having some sort of glitch with my Internet or something 309 00:21:33,529 --> 00:21:34,649 to get that error message but here I 310 00:21:34,649 --> 00:21:39,480 am in the HTML preview. You can see I have the list structure inside of the table. 311 00:21:39,480 --> 00:21:45,779 Now, just because by defaults, Equidox, assumes that your first column is a row header, it's 312 00:21:45,779 --> 00:21:50,440 giving me that bold frontier to just give me that visual, and for that visual confirmation 313 00:21:50,440 --> 00:21:51,440 through the 314 00:21:51,440 --> 00:21:57,279 interface. But again I can change my row header from one to and when I go back to my preview 315 00:21:57,279 --> 00:22:01,490 you'll see that I have just that some font for the individual lists. 316 00:22:01,490 --> 00:22:07,740 So those are the 2 common elements that I see Often inside of tables are are lists and 317 00:22:07,740 --> 00:22:08,740 links. 318 00:22:08,740 --> 00:22:14,639 Another one that you might uncover, are things like footnote links which we have an example 319 00:22:14,639 --> 00:22:15,639 of. 320 00:22:15,639 --> 00:22:21,169 Actually, I believe, a client sent this in if I take a look at this document here. 321 00:22:21,169 --> 00:22:26,679 We'll just pull up like page 2 and we can look there's actually footnotes that fall 322 00:22:26,679 --> 00:22:28,410 underneath this table. 323 00:22:28,410 --> 00:22:34,419 Now there's footnotes are not really ideal for tables, because what the footnote is going 324 00:22:34,419 --> 00:22:38,090 to do, It's going to direct the user outside of the table, and then it's going to return 325 00:22:38,090 --> 00:22:39,640 them to the top left 326 00:22:39,640 --> 00:22:43,029 cell essentially of the table, and they have to renavigate through. 327 00:22:43,029 --> 00:22:48,239 So it's really not an ideal it's really not ideal for usability purposes. 328 00:22:48,239 --> 00:22:52,970 But it many cases you are not the designer of the document you've just been given a document 329 00:22:52,970 --> 00:22:54,330 and you've been asked to tag it. 330 00:22:54,330 --> 00:22:56,970 So won't work for through it with using Equidox. 331 00:22:56,970 --> 00:23:02,830 So I'm gonna just build this kind of manually here to show you the the step-by-step process. 332 00:23:02,830 --> 00:23:06,600 So. so I have 2 tech zones capturing my 2 footnotes. 333 00:23:06,600 --> 00:23:10,639 What I'll do, is I will direct these I'll change these to footnotes through the drop-down 334 00:23:10,639 --> 00:23:11,710 menu. 335 00:23:11,710 --> 00:23:17,100 You'll see Now they say fn and fn fn and fn for the zone types instead of text. 336 00:23:17,100 --> 00:23:19,580 And then here are those reference points inside of the table. 337 00:23:19,580 --> 00:23:24,730 So if I draw 2 zones and I'm just going to put it over the entire, the entire character 338 00:23:24,730 --> 00:23:27,370 there. 339 00:23:27,370 --> 00:23:32,580 I'm just gonna these can be it can be kind of tedious to deal with tiny little these 340 00:23:32,580 --> 00:23:36,179 tiny little superscripts for the footnote reference links. 341 00:23:36,179 --> 00:23:39,680 But what I'll do, is I'll draw the 2 zones and place them on top of those and then I 342 00:23:39,680 --> 00:23:45,909 will create these as footnote links, and I I'll direct these footnote links to the the 343 00:23:45,909 --> 00:23:46,909 corresponding 344 00:23:46,909 --> 00:23:51,330 footnote down here. So I have a drop-down menu that will tell me which zone. 345 00:23:51,330 --> 00:23:56,690 I want you directed to. so I want to direct the first footnote to this footnote here, 346 00:23:56,690 --> 00:24:00,009 and I want to direct the second footnote to the second footnote: Right here. 347 00:24:00,009 --> 00:24:06,679 So once I've created that I can then just draw my table and and then open up the table. 348 00:24:06,679 --> 00:24:12,039 Editor, and again you'll see that those blue bars are those blue boxes there, indicating 349 00:24:12,039 --> 00:24:14,340 that I have that I have. 350 00:24:14,340 --> 00:24:18,570 Footnote Links zones place their back on the PDF. 351 00:24:18,570 --> 00:24:21,370 And again, just using my detection. Slider. None of this is very. 352 00:24:21,370 --> 00:24:26,850 This is all getting kind of repetitive but I think I hope you're able to see how simple 353 00:24:26,850 --> 00:24:31,590 this is by comparison, especially if you've done this before. 354 00:24:31,590 --> 00:24:36,039 But once I've got those rows and columns in their general location. 355 00:24:36,039 --> 00:24:43,030 If I take a look at the HTML preview you'll see that I have some sort of duplication here. 356 00:24:43,030 --> 00:24:54,269 I wonder what that's from there. we go so you can see we have the developed category, 357 00:24:54,269 --> 00:24:55,269 and the number one. 358 00:24:55,269 --> 00:24:59,190 And then there's your little superscript with the footnote reference, and the same thing. 359 00:24:59,190 --> 00:25:03,279 Here you have the number 2, and if you look closely it is highlighted blue, and it's actually 360 00:25:03,279 --> 00:25:05,220 an active hyperlink that you can click on. 361 00:25:05,220 --> 00:25:08,489 So I will save this table, and I will close out. 362 00:25:08,489 --> 00:25:13,690 So that is what table remediation looks like when you have footnotes, and if you look at 363 00:25:13,690 --> 00:25:18,499 the full page preview, you can see you have your footnotes down below, and those references 364 00:25:18,499 --> 00:25:20,009 will direct them to the corresponding 365 00:25:20,009 --> 00:25:32,600 Footnote: Okay, So we have about 5 min left, and I wanted to just cover one other example. 366 00:25:32,600 --> 00:25:39,730 If I were to look at a table like this, and forgive me for jumping around to so many documents. 367 00:25:39,730 --> 00:25:44,850 I know it can be kind of a lot to look at as we go from document to document. 368 00:25:44,850 --> 00:25:50,159 But there really is no perfect single document that covers all of these sort of unique instances. 369 00:25:50,159 --> 00:25:56,230 but this table here is kind of unique, because if you look at it, there is this temperature 370 00:25:56,230 --> 00:25:59,779 which is actually a row header that pertains to these 371 00:25:59,779 --> 00:26:06,769 6 rows here, and per person again pertains to these 6 rows, but they're not visually 372 00:26:06,769 --> 00:26:12,480 situated in the table in in such a way that can be accurately tag where you tag the temperature 373 00:26:12,480 --> 00:26:13,480 and precipitation 374 00:26:13,480 --> 00:26:17,419 as row headers that have these child rows underneath it but I'm going to show you in 375 00:26:17,419 --> 00:26:19,320 Equidox how we can fix this. 376 00:26:19,320 --> 00:26:24,159 So I'm going to draw a table I'm going to draw a zone, and if you notice I've left a 377 00:26:24,159 --> 00:26:28,830 little bit of a margin down the left-hand side and again I'm gonna hit t for table and 378 00:26:28,830 --> 00:26:41,169 I will open up the Table Editor So, creating my rows and columns. 379 00:26:41,169 --> 00:26:48,559 Okay, that looks pretty good, and I will just drag this one over a hair. 380 00:26:48,559 --> 00:26:53,230 So that will give us our our basic table structure, not going to span. 381 00:26:53,230 --> 00:26:58,080 Get get rid of some of these spannings and then I'm going to create an extra column over 382 00:26:58,080 --> 00:27:01,610 here on the far left side, and I'll explain why, in just a second. 383 00:27:01,610 --> 00:27:07,289 So by creating that extra column. what I'm going to do then, is I'm going to actually 384 00:27:07,289 --> 00:27:08,610 migrate this information. 385 00:27:08,610 --> 00:27:12,889 So precipitation and temperature I'm going to place them over here in this extra column, 386 00:27:12,889 --> 00:27:18,809 and span down these blanks cells to make it so that this is a row header for these 6 rows 387 00:27:18,809 --> 00:27:19,809 So what I'll do 388 00:27:19,809 --> 00:27:23,320 to accomplish this is I'm gonna get rid of this extra row here because I won't need it 389 00:27:23,320 --> 00:27:28,070 and I don't need all these blank cells over here and I'm going to go to the cells tab 390 00:27:28,070 --> 00:27:29,070 and then in 391 00:27:29,070 --> 00:27:34,690 the cells tab. If I go to custom in the drop-down menu for the cell source, I go to custom, 392 00:27:34,690 --> 00:27:40,769 I can can actually cut the temperature right out of this this particular cell, and I can 393 00:27:40,769 --> 00:27:43,970 paste it into this cell here and 394 00:27:43,970 --> 00:27:53,529 once I've done that I can then span the corresponding rows, and by doing that before I do the precipitation 395 00:27:53,529 --> 00:27:59,999 I'll show you where you now have temperature as a row header for these rows here so this 396 00:27:59,999 --> 00:28:04,739 is a way of kind of making without making visual edits to the templates, or going back 397 00:28:04,739 --> 00:28:07,100 and redesigning the table. 398 00:28:07,100 --> 00:28:13,460 You're able to make these adjustments to how this will be tagged on export simply by going 399 00:28:13,460 --> 00:28:17,359 through these steps, so it can be a little bit confusing in the beginning. 400 00:28:17,359 --> 00:28:21,210 But once you get the hang of it it becomes second nature where you're just taking what 401 00:28:21,210 --> 00:28:24,919 doesn't belong there, and placing it where it does belong, which is over here in this 402 00:28:24,919 --> 00:28:27,809 column, which is actually doesn't have any content in it, but 403 00:28:27,809 --> 00:28:35,100 we're able to place that content in it using custom so I'm able to then set myself up with 404 00:28:35,100 --> 00:28:42,211 2 row headers, and I have one and 2 column headers, so I will I'll have my ratio at 2 405 00:28:42,211 --> 00:28:48,480 to 2, and when I look at the HTML preview have temperature, precipitation, and then 406 00:28:48,480 --> 00:28:54,629 the the other categories here that fall underneath those sort of parent row headers, One other 407 00:28:54,629 --> 00:28:55,629 thing that I can mention here with 408 00:28:55,629 --> 00:29:01,999 our last moment is that these months are actually labeled with just the letter which can be 409 00:29:01,999 --> 00:29:06,279 a little bit confusing if you're if you're not quite sure exactly that these are referring 410 00:29:06,279 --> 00:29:07,279 to months. 411 00:29:07,279 --> 00:29:11,549 So instead of J I can again go into the cell source, and I can change it to custom. 412 00:29:11,549 --> 00:29:15,979 And I can actually type out January, and I could repeat that for these 12 months. 413 00:29:15,979 --> 00:29:20,539 But the idea is that if you don't have like the full context, or something of a table 414 00:29:20,539 --> 00:29:21,539 needs to be edited. 415 00:29:21,539 --> 00:29:24,350 Maybe it's the use of acronyms maybe it's blank cells. 416 00:29:24,350 --> 00:29:29,489 Maybe it's dashes instead of you know zeros or it could be different. 417 00:29:29,489 --> 00:29:33,980 Symbols that are non-standard. and a screen reader might not be able to read you're able 418 00:29:33,980 --> 00:29:38,690 to go in and actually insert additional contexts, and it really increase the value of that table 419 00:29:38,690 --> 00:29:40,929 by providing the full word which can 420 00:29:40,929 --> 00:29:44,370 be enunciated by a screen reader rather than just. 421 00:29:44,370 --> 00:29:51,879 Jfm. A. M. So on, and so forth so that's and part of the problem that is jay and J for 422 00:29:51,879 --> 00:29:54,149 June and July that can cause confusion. 423 00:29:54,149 --> 00:29:58,119 So Which which column are you actually in? Are you in the June month, or are you in the 424 00:29:58,119 --> 00:29:59,119 July month? 425 00:29:59,119 --> 00:30:03,369 So just going through like extra steps like that can really increase the value of a table 426 00:30:03,369 --> 00:30:05,039 for an end user. 427 00:30:05,039 --> 00:30:09,759 Okay, So it is 2, 30, and I wanted to I just thank everyone for joining. 428 00:30:09,759 --> 00:30:14,989 I'm gonna jump back to the slide deck here and get us to our contact screen. 429 00:30:14,989 --> 00:30:18,120 So I just I want to thank everyone again for joining us for another edition of Equodox 430 00:30:18,120 --> 00:30:19,519 Webinar Wednesdays. I don't know. 431 00:30:19,519 --> 00:30:24,529 That was kind of a fast-paced training, if you will, showing some different table examples. 432 00:30:24,529 --> 00:30:29,220 But I hope that you found value in it. and like, I said, for anyone that that is on this 433 00:30:29,220 --> 00:30:32,309 call that is not an existing ecodox user or client. 434 00:30:32,309 --> 00:30:37,479 Please feel free to reach out to us at Equidox sales, and Onix net com or visit our website 435 00:30:37,479 --> 00:30:43,320 and get in touch with us to talk more about your specific use case your PDF challenges. 436 00:30:43,320 --> 00:30:46,570 We'd be we'd love to learn about it and we'd love to talk to you about how we can help. 437 00:30:46,570 --> 00:30:50,669 We're also very active. social media so Linkedin Twitter. 438 00:30:50,669 --> 00:30:55,519 We have a whole bunch of information up on. Youtube So please follow us on any of these 439 00:30:55,519 --> 00:30:57,399 social media platforms that you use. 440 00:30:57,399 --> 00:31:01,249 And I believe Tammy will be sending out a short survey after this. 441 00:31:01,249 --> 00:31:05,470 After this webinar. So if you could just take a moment to fill out that survey, we really 442 00:31:05,470 --> 00:31:06,470 appreciate the feedback. 443 00:31:06,470 --> 00:31:11,309 It really helps us kind of address challenges or questions that any people might be having, 444 00:31:11,309 --> 00:31:13,250 and helps us kind of tailor. 445 00:31:13,250 --> 00:31:16,841 These webinars to be as relevant as possible for the most amount of people. 446 00:31:16,841 --> 00:31:17,841 So thank you very much. Everyone have a great rest of your afternoon. 447 00:31:17,841 --> 00:31:18,841 ll right so it is 2 o'clock. Welcome everyone. 448 00:31:18,841 --> 00:31:19,841 Thank you for joining us again for another addition of Equidox, webinar Wednesdays path 449 00:31:19,841 --> 00:31:20,841 to PDF. 450 00:31:20,841 --> 00:31:21,841 Accessibility. So today we're mainly going to be talking about advanced table remediation 451 00:31:21,841 --> 00:31:22,841 techniques. 452 00:31:22,841 --> 00:31:23,841 So I have quite a few different examples pulled up of different tables that can present some 453 00:31:23,841 --> 00:31:24,841 unique challenges. 454 00:31:24,841 --> 00:31:25,841 So if you deal with a lot of tables, this should be a helpful guide to showing you like 455 00:31:25,841 --> 00:31:26,841 the best and most efficient ways to deal with those unique tables. 456 00:31:26,841 --> 00:31:27,841 So, as always, what I'd like to mention is if you have any, follow-up questions. 457 00:31:27,841 --> 00:31:28,841 Or if you are not a current user or client of Equidox, and you'd like to have a more 458 00:31:28,841 --> 00:31:29,841 personal one-on-one demonstration where we can talk about your challenges with PDF remediation 459 00:31:29,841 --> 00:31:30,841 and any 460 00:31:30,841 --> 00:31:31,841 of your use cases. we can look at some of your specific documents and challenges that 461 00:31:31,841 --> 00:31:32,841 you have. 462 00:31:32,841 --> 00:31:33,841 Please feel free to reach out to us at Equidox sales at Onix net Com website is Www. 463 00:31:33,841 --> 00:31:34,841 Dot, Ecodox Co. and we also can be reached by phone at 806, 6, 4, 9, 6, 3, 8. 464 00:31:34,841 --> 00:31:35,841 So before moving into the demonstration, I just want to quickly remind everyone that 465 00:31:35,841 --> 00:31:36,841 Equidox is a division of Onix networking. 466 00:31:36,841 --> 00:31:37,841 So Onix is headquartered in Cleveland, Ohio. 467 00:31:37,841 --> 00:31:38,841 We have employees all over North America. so we've been in business for about 28 years, 468 00:31:38,841 --> 00:31:39,841 and we're primarily a Google cloud partner, a Cloud consultancy as well. 469 00:31:39,841 --> 00:31:40,841 We're also partnered with amazon web services as well. our mission is to improve organizational 470 00:31:40,841 --> 00:31:41,841 efficiency through cloud computing solutions. 471 00:31:41,841 --> 00:31:42,841 Now Equidox is a division of Onix, and we are primarily focused on PDF accessibility. 472 00:31:42,841 --> 00:31:43,841 So we have the best-class PDF remediation software. 473 00:31:43,841 --> 00:31:44,841 We also offer professional remediation services for organizations. that have large volumes 474 00:31:44,841 --> 00:31:45,841 of documents, and the don't have the bandwidth to deal with that type of volume. 475 00:31:45,841 --> 00:31:46,841 You can outsource to our services. We also can provide all kinds of accessibility services 476 00:31:46,841 --> 00:31:47,841 regarding training or website help. 477 00:31:47,841 --> 00:31:48,841 Really anything related to digital accessibility, and our mission is to ensure that digital 478 00:31:48,841 --> 00:31:49,841 information reaches everyone through accessibility solutions. 479 00:31:49,841 --> 00:31:50,841 So this is just a quick slide with a few of our customers. So I'm just gonna let those 480 00:31:50,841 --> 00:31:51,841 play through. and we're gonna jump now into the Equidox demonstration. 481 00:31:51,841 --> 00:31:52,841 So if anyone is able to stay for the duration of this webinar, we will insert the the video 482 00:31:52,841 --> 00:31:53,841 of it here into the slide deck, and you'll receive this after after the call is over. 483 00:31:53,841 --> 00:31:54,841 Okay, So well now, I'm in Equidox our PDF remediation tool. 484 00:31:54,841 --> 00:31:55,841 So anyone on the webinar that is a current user. 485 00:31:55,841 --> 00:31:56,841 This should look fairly familiar to you, but for anyone that isn't current Equidox user. 486 00:31:56,841 --> 00:31:57,841 I just want to get started with a simple example of how we can remediate a table. 487 00:31:57,841 --> 00:31:58,841 So if I were to open up a simple standard document like this where they simple table 488 00:31:58,841 --> 00:31:59,841 inside of this page. 489 00:31:59,841 --> 00:32:00,841 Sometimes you'll arrive at a document and you will see a setup of the reading zones 490 00:32:00,841 --> 00:32:01,841 that will look something like this, and using the HTML preview to just look at how this 491 00:32:01,841 --> 00:32:02,841 would be read by a screen reader, 492 00:32:02,841 --> 00:32:03,841 You can probably tell that this is not actual table structure each one of those cells inside 493 00:32:03,841 --> 00:32:04,841 of that table will just be read in this particular order, rendering this pretty much useless 494 00:32:04,841 --> 00:32:05,841 to a screen reader, user, because they're not really sure which 495 00:32:05,841 --> 00:32:06,841 row or column that they are currently situated in so in Equidox. All we need to do is draw 496 00:32:06,841 --> 00:32:07,841 a single zone over the top of the entire table. 497 00:32:07,841 --> 00:32:08,841 I'll use my keyboard shortcut and hit t to change the zones to a table, and that will 498 00:32:08,841 --> 00:32:09,841 give me this button here for the Table Editor. 499 00:32:09,841 --> 00:32:10,841 So when I press the Table Editor button this will isolate the table, and I will see the 500 00:32:10,841 --> 00:32:11,841 green gridlines here, which I'm free to move around and get a line manually, if I'd like 501 00:32:11,841 --> 00:32:12,841 so you can see that the 502 00:32:12,841 --> 00:32:13,841 green grid line, for the most part are lined up with the rows and columns. 503 00:32:13,841 --> 00:32:14,841 There are a few adjustments that can be made so to make those adjustments. If I don't want 504 00:32:14,841 --> 00:32:15,841 to do that manually, I can also use our Table Detector. 505 00:32:15,841 --> 00:32:16,841 So the Table Detector is using computer vision and machine learning to better understand 506 00:32:16,841 --> 00:32:17,841 the cell structure of these tables, and it will automatically draw those gridlines in 507 00:32:17,841 --> 00:32:18,841 the location that they need to be. 508 00:32:18,841 --> 00:32:19,841 So. so we remember what the HTML preview looked like just a moment ago, with no table structure 509 00:32:19,841 --> 00:32:20,841 whatsoever. 510 00:32:20,841 --> 00:32:21,841 But if I were to refresh that preview you'll see that now I have a real table. Now this 511 00:32:21,841 --> 00:32:22,841 is rendered in HTML. 512 00:32:22,841 --> 00:32:23,841 But the beautiful thing about Equidox is that it will take this HTML structure and it will 513 00:32:23,841 --> 00:32:24,841 automatically convert it into a PDF tag tree for you. 514 00:32:24,841 --> 00:32:25,841 So anyone that has done manual PDF. for remediation of tables, you know, in a tool where you have 515 00:32:25,841 --> 00:32:26,841 to tag every individual cell. there are so many steps associated with working through 516 00:32:26,841 --> 00:32:27,841 tables that a simple little table like 517 00:32:27,841 --> 00:32:28,841 This can take upwards of, you know, 10-15 min. In some cases. 518 00:32:28,841 --> 00:32:29,841 In many cases, it can take a lot longer. Tables, of course, get much more complicated than 519 00:32:29,841 --> 00:32:30,841 this, So you can see that within Equidox we have the automation of with the detection 520 00:32:30,841 --> 00:32:31,841 tool and just a much cleaner workflow in an interface that allows for simple and fast 521 00:32:31,841 --> 00:32:32,841 table remediation, even if you are a novice user. 522 00:32:32,841 --> 00:32:33,841 Okay, so let's jump out of this document. forgive me as I jump around from documents 523 00:32:33,841 --> 00:32:34,841 to documents. So I wanted to make sure that we covered a bunch of different bases. 524 00:32:34,841 --> 00:32:35,841 So I'm gonna do some simple table. That was a simple table, and I'll jump into a slightly 525 00:32:35,841 --> 00:32:36,841 more complicated example here. 526 00:32:36,841 --> 00:32:37,841 So. So this table, as you can tell, is quite large, quite dense. 527 00:32:37,841 --> 00:32:38,841 This can be kind of intimidating to look at there's also multiple column headers in this 528 00:32:38,841 --> 00:32:39,841 particular table. 529 00:32:39,841 --> 00:32:40,841 So you have different levels of column headers here that all correlate with the table data 530 00:32:40,841 --> 00:32:41,841 which falls below. 531 00:32:41,841 --> 00:32:42,841 Now it's the same concept where I'm just gonna draw a single table on top of, or a single 532 00:32:42,841 --> 00:32:43,841 zone on top of the table as I just drag it all the way to the bottom can Then again. 533 00:32:43,841 --> 00:32:44,841 Press t on my keyboard and the Table Editor Button will appear so I'll press the Table 534 00:32:44,841 --> 00:32:45,841 Editor Button and I'm gonna zoom out a bit to make this a little bit easier. 535 00:32:45,841 --> 00:32:46,841 To see. But you can tell here that there's so much going on that Equidox didn't even 536 00:32:46,841 --> 00:32:47,841 bother to draw the zones. 537 00:32:47,841 --> 00:32:48,841 So again we're going to use our Table Detection sliders here. 538 00:32:48,841 --> 00:32:49,841 So, as I move these around, I can just find the best possible starting point where I don't 539 00:32:49,841 --> 00:32:50,841 have to make too many manual adjustments, so you can see that the sliders here are able 540 00:32:50,841 --> 00:32:51,841 to land pretty much spot on with all of the rows and the columns might need just a tiny 541 00:32:51,841 --> 00:32:52,841 little adjustment. 542 00:32:52,841 --> 00:32:53,841 If I just drag these a little bit left to right you'll see that I'm able to get everything 543 00:32:53,841 --> 00:32:54,841 pretty much aligned with the table. 544 00:32:54,841 --> 00:32:55,841 So, taking a look at the preview for this table now you'll see that I have pretty clean 545 00:32:55,841 --> 00:32:56,841 table structure. 546 00:32:56,841 --> 00:32:57,841 There are a few things that I need to adjust up here because of the way that this table 547 00:32:57,841 --> 00:32:58,841 is set up. 548 00:32:58,841 --> 00:32:59,841 There is some spanning that needs to be done within the column headers. So to span. 549 00:32:59,841 --> 00:33:00,841 This is another technique in Equidox, where you need to join multiple cells together. 550 00:33:00,841 --> 00:33:01,841 I can just click in one cell that I'd like to join hold down the shift key, and then 551 00:33:01,841 --> 00:33:02,841 select in another cell as well. 552 00:33:02,841 --> 00:33:03,841 So wherever I would like to span to a span button will appear at the top, or you can 553 00:33:03,841 --> 00:33:04,841 also use your keyboard shortcut and press “S” and that will complete the spam. so 554 00:33:04,841 --> 00:33:05,841 just quickly going back to the preview you'll see that Now I have overlap in one cell that 555 00:33:05,841 --> 00:33:06,841 sits at the very top of the table, so there's some other spanning that needs to be done 556 00:33:06,841 --> 00:33:07,841 here. 557 00:33:07,841 --> 00:33:08,841 I actually don't even need this extra row if I zoom in you'll see that Equidox was maybe 558 00:33:08,841 --> 00:33:09,841 thrown off because this text… it's situated on 2 separate lines so I could do using the 559 00:33:09,841 --> 00:33:10,841 computer vision was thinking, Maybe that this is a situation where you've got 2 separate 560 00:33:10,841 --> 00:33:11,841 rows there. 561 00:33:11,841 --> 00:33:12,841 I don't really need that extra row, though so what I can do is I can either press the 562 00:33:12,841 --> 00:33:13,841 delete row button, or I can just press “D” on my keyboard. 563 00:33:13,841 --> 00:33:14,841 And that will basically merge down where it will get rid of that extra row that I don't 564 00:33:14,841 --> 00:33:15,841 actually need. 565 00:33:15,841 --> 00:33:16,841 Now I need to span across these 4 cells for this second level of column headers. 566 00:33:16,841 --> 00:33:17,841 So if I click in the cell hold shift and again. just clicking to the other cell, I'd like 567 00:33:17,841 --> 00:33:18,841 to join with, then press us Another situation here where I don't need this row you can see 568 00:33:18,841 --> 00:33:19,841 that the double lines of text was 569 00:33:19,841 --> 00:33:20,841 to make, maybe thinking, or maybe made Equidox thinks that this could be 2 separate rows. 570 00:33:20,841 --> 00:33:21,841 So again I'll just press d to get rid of that extra row, and then I will spam the trust 571 00:33:21,841 --> 00:33:22,841 fund cell over here, so I'll just again click in my 2 cells. and press “S” Now, if I 572 00:33:22,841 --> 00:33:23,841 go back to the HTML preview you'll see that we've cleaned this up quite a bit, so we have 573 00:33:23,841 --> 00:33:24,841 kind of fixed the structure where it looks a little bit better in HTML but we still have 574 00:33:24,841 --> 00:33:25,841 a few things to adjust. So the next thing to adjust is addressing the column and row 575 00:33:25,841 --> 00:33:26,841 headers. 576 00:33:26,841 --> 00:33:27,841 So by default products, assumes that your table will have one column header, which will 577 00:33:27,841 --> 00:33:28,841 be the top row, and the farthest left column, will be the row headers. 578 00:33:28,841 --> 00:33:29,841 That's just the default assumption. Now in this particular example because of the way 579 00:33:29,841 --> 00:33:30,841 this table is designed. 580 00:33:30,841 --> 00:33:31,841 I have a column header here I have another row of column headers here, and I even have 581 00:33:31,841 --> 00:33:32,841 a third row of column headers. 582 00:33:32,841 --> 00:33:33,841 So what I'll do is I'll come over here to the column header field, and as you can see 583 00:33:33,841 --> 00:33:34,841 these in the little text input fields. 584 00:33:34,841 --> 00:33:35,841 Here they are automatically set one to one, and if I just adjust that one to 3 that will, 585 00:33:35,841 --> 00:33:36,841 that will change the output of this table where the top 3 rows will be tagged as column 586 00:33:36,841 --> 00:33:37,841 headers now the year 587 00:33:37,841 --> 00:33:38,841 over here, which is again by default is going to be tagged as a row. 588 00:33:38,841 --> 00:33:39,841 Header. This is not necessarily a row header I think this is the table really. 589 00:33:39,841 --> 00:33:40,841 That just consists of column headers. so I can change my row header from one to 0. 590 00:33:40,841 --> 00:33:41,841 Now, if I go back to the HTML preview what we'll see is I now have bold fonts for the 591 00:33:41,841 --> 00:33:42,841 top 3 rows, and this is just giving you that visual confirmation that you've 592 00:33:42,841 --> 00:33:43,841 adjusted the table to export with 3 rows of column headers. 593 00:33:43,841 --> 00:33:44,841 You'll also notice that in the far left column where the years are situated. 594 00:33:44,841 --> 00:33:45,841 You don't have that bold font anymore. indicating that the years themselves will be tagged as 595 00:33:45,841 --> 00:33:46,841 table data. 596 00:33:46,841 --> 00:33:47,841 So all of these cells here, where you're just seeing a standard font will be tagged as table 597 00:33:47,841 --> 00:33:48,841 data, and will be attributed to whichever series of column headers they fall under. 598 00:33:48,841 --> 00:33:49,841 So another thing that I can talk about in this table, and is sometimes because of the 599 00:33:49,841 --> 00:33:50,841 computer vision. 600 00:33:50,841 --> 00:33:51,841 And you have such small fonts in this table, and things can be very tightly spaced. 601 00:33:51,841 --> 00:33:52,841 You might have a situation where the green gridlines fall maybe one or 2 pixels away 602 00:33:52,841 --> 00:33:53,841 from where they should. 603 00:33:53,841 --> 00:33:54,841 And if that's ever the case it would be extremely tedious to have to go through and individually 604 00:33:54,841 --> 00:33:55,841 adjust every single one of these rows, and new up like a pixel or 2, it could be done 605 00:33:55,841 --> 00:33:56,841 if you had the patients to 606 00:33:56,841 --> 00:33:57,841 do it, but that can be tedious and time-consuming, and so to address that occasional issue that 607 00:33:57,841 --> 00:33:58,841 you might run into on a very dense table. 608 00:33:58,841 --> 00:33:59,841 We have this tool here underneath the cells tab called nudge, where you're able to nudge 609 00:33:59,841 --> 00:34:00,841 the rows up or down. 610 00:34:00,841 --> 00:34:01,841 So if you click the Nudge button, your rows will move in unison where they will all just 611 00:34:01,841 --> 00:34:02,841 bump up one pixel out of time, so you can get things more closely aligned to where they 612 00:34:02,841 --> 00:34:03,841 need to 613 00:34:03,841 --> 00:34:04,841 be so there can be. Did I have a little bit of an Internet glitch? 614 00:34:04,841 --> 00:34:05,841 Wonder am I Still, we can still hear you interesting. I was wondering if my Internet cut out for 615 00:34:05,841 --> 00:34:06,841 a second. 616 00:34:06,841 --> 00:34:07,841 That's odd so we'll I'll show you in fast pace. 617 00:34:07,841 --> 00:34:08,841 How quickly we can get back to where we were so again just going, talking about how to 618 00:34:08,841 --> 00:34:09,841 do this manually in a tool like, or a manual tagging tool table like this could really 619 00:34:09,841 --> 00:34:10,841 be a big problem where you're spending upwards 620 00:34:10,841 --> 00:34:11,841 of an hour to working through this single table, and then extrapolating that out over 621 00:34:11,841 --> 00:34:12,841 a document that might have dozens of tables in it, if not hundreds of tables and sort 622 00:34:12,841 --> 00:34:13,841 of financial reports and things of that nature you 623 00:34:13,841 --> 00:34:14,841 can spend a lot of time working through working through documents where you are actually spending 624 00:34:14,841 --> 00:34:15,841 just seconds on tables like this. 625 00:34:15,841 --> 00:34:16,841 So pretty dramatic pretty dramatic time savings, especially when you're thinking about longer 626 00:34:16,841 --> 00:34:17,841 documents, as I said before. 627 00:34:17,841 --> 00:34:18,841 So again we're back to the same table structure that I had I would just need to. 628 00:34:18,841 --> 00:34:19,841 Then again fix my column and row headers. Another feature of Equidox is the auto summarized 629 00:34:19,841 --> 00:34:20,841 mode. 630 00:34:20,841 --> 00:34:21,841 So if your current Equidox user, you may or may not know that this is a feature. 631 00:34:21,841 --> 00:34:22,841 But table summaries are one of those requirements for tagging tables where you need to have 632 00:34:22,841 --> 00:34:23,841 a table summary to give that end user. 633 00:34:23,841 --> 00:34:24,841 Who's using a screen reader, a general overview of what? what? that table consists of in terms 634 00:34:24,841 --> 00:34:25,841 of the structure of it. 635 00:34:25,841 --> 00:34:26,841 So what Equidox is able to do is programmatically write the table summary for you. 636 00:34:26,841 --> 00:34:27,841 If you turn the auto summarize mode on So by doing that, it's giving the user the indication 637 00:34:27,841 --> 00:34:28,841 that. 638 00:34:28,841 --> 00:34:29,841 Okay, they're 79 rows in this table there are 5 columns. 639 00:34:29,841 --> 00:34:30,841 It's letting them know that there are multiple column headers. 640 00:34:30,841 --> 00:34:31,841 There are no row headers it's letting them know that there are spans going on inside 641 00:34:31,841 --> 00:34:32,841 of the data cells and the column headers. 642 00:34:32,841 --> 00:34:33,841 So it's giving them that that sort of navigation key right up front that they can that can 643 00:34:33,841 --> 00:34:34,841 they can find helpful when they're trying to navigate through a very dense table like 644 00:34:34,841 --> 00:34:35,841 this that contains a whole bunch 645 00:34:35,841 --> 00:34:36,841 of cells which could be you know quite challenging to work through So again, we'll. we'll finish 646 00:34:36,841 --> 00:34:37,841 up with this table, and since I'm talking about the table summary what I'll do is for 647 00:34:37,841 --> 00:34:38,841 any existing users of Equidox. I will show you how to turn that auto summarized mode 648 00:34:38,841 --> 00:34:39,841 on in your profile. 649 00:34:39,841 --> 00:34:40,841 So if I just close out very quickly if I go to my profile, what you'll see is and that's 650 00:34:40,841 --> 00:34:41,841 in the upper right-hand corner, you can go to your profile, and there is an auto summarized 651 00:34:41,841 --> 00:34:42,841 mode 652 00:34:42,841 --> 00:34:43,841 dropdown. You can turn that on to default, to enable default to disabled, or you can 653 00:34:43,841 --> 00:34:44,841 hide it all together. 654 00:34:44,841 --> 00:34:45,841 So I have mine set to default to “Enabled” so that way when I'm working on a table, machine 655 00:34:45,841 --> 00:34:46,841 learning is automatically summarizing that table for you. 656 00:34:46,841 --> 00:34:47,841 There are quite a few advantages to that so especially if you're working on a long document, 657 00:34:47,841 --> 00:34:48,841 and perhaps collaborating on that document with multiple users or mediating tables. 658 00:34:48,841 --> 00:34:49,841 It will ensure that your table summaries are very much consistent where you don't have 659 00:34:49,841 --> 00:34:50,841 different people interpreting what they think. 660 00:34:50,841 --> 00:34:51,841 A table summary is supposed to be, it will also ensure accuracy. 661 00:34:51,841 --> 00:34:52,841 So if you're thinking about a table like this if I just jump back in for a second. 662 00:34:52,841 --> 00:34:53,841 But a table that has 79 rows. If you were trying to manually count how many rows there 663 00:34:53,841 --> 00:34:54,841 are, you could easily come up with an incorrect number. 664 00:34:54,841 --> 00:34:55,841 So just for the sake of consistency and accuracy. 665 00:34:55,841 --> 00:34:56,841 The table summary feature is very very helpful you're also able to, of course, enhance that 666 00:34:56,841 --> 00:34:57,841 table summary. 667 00:34:57,841 --> 00:34:58,841 So you're able to insert more information about that table if you feel that it's necessary. 668 00:34:58,841 --> 00:34:59,841 But it's just nice that Equidox will programmatically write it for you, so that you don't have to 669 00:34:59,841 --> 00:35:00,841 necessarily think about table summaries as you're working through documents that are 670 00:35:00,841 --> 00:35:01,841 full of dozens and dozens of tables. So I'm going to ask for that, sure, and I'm not sure 671 00:35:01,841 --> 00:35:02,841 exactly what happened there, but I'm happy to nudge again. So let's talk about I want 672 00:35:02,841 --> 00:35:03,841 to talk about a table that contains a few different elements inside of the table. 673 00:35:03,841 --> 00:35:04,841 So a table like this, you actually have links inside of it. 674 00:35:04,841 --> 00:35:05,841 So if I were to use our Zone Detector, which many of you will be familiar with, we actually 675 00:35:05,841 --> 00:35:06,841 have links that are situated inside of this table. 676 00:35:06,841 --> 00:35:07,841 So this is very much a simple table by comparison to what we just looked at. 677 00:35:07,841 --> 00:35:08,841 There's really just a little bit of spanning that needs to go on. 678 00:35:08,841 --> 00:35:09,841 But when you have different elements nested inside of tables, Equidox is also able to 679 00:35:09,841 --> 00:35:10,841 handle this. 680 00:35:10,841 --> 00:35:11,841 So again, just drawing a single zone, capturing the entire table, opening up my Table Editor. 681 00:35:11,841 --> 00:35:12,841 And if you notice there's a slight blue hue that is covering up these different elements, 682 00:35:12,841 --> 00:35:13,841 indicating that there is a another zone sat on top of that when we return to the PDF. 683 00:35:13,841 --> 00:35:14,841 When we turn to the entire PDF page, not just looking at the Table Editor. 684 00:35:14,841 --> 00:35:15,841 So again, using my detection tools here. we will get this as close as we can, and that 685 00:35:15,841 --> 00:35:16,841 looks pretty good. 686 00:35:16,841 --> 00:35:17,841 I think I want. I might have drawn the table a little bit too large. 687 00:35:17,841 --> 00:35:18,841 I have one extra column over there. but now I'll just quickly go through the spanning 688 00:35:18,841 --> 00:35:19,841 process which we've already covered, and you can see here, we've got basically our table 689 00:35:19,841 --> 00:35:20,841 set up as neat as we need so just maybe 690 00:35:20,841 --> 00:35:21,841 a couple of minor adjustments to the gridlines, and I'll add an extra row here for some reason 691 00:35:21,841 --> 00:35:22,841 it missed that row. But looking at the HTML preview because I have those links you can 692 00:35:22,841 --> 00:35:23,841 see I actually have the links inside of the HTML preview here, and these will actually 693 00:35:23,841 --> 00:35:24,841 go to the destination point as defined in the source. 694 00:35:24,841 --> 00:35:25,841 PDF: So whatever the encoded link was directing that user to these links will actually be 695 00:35:25,841 --> 00:35:26,841 active in the exported version, so really helpful. 696 00:35:26,841 --> 00:35:27,841 If you're dealing with directories, and you have a bunch of email addresses, or in this 697 00:35:27,841 --> 00:35:28,841 example, you have different web pages with more information about the person's health 698 00:35:28,841 --> 00:35:29,841 needs so you're able to go straight to those links through the table structure. So it's 699 00:35:29,841 --> 00:35:30,841 a common thing that can occur in many different tables. 700 00:35:30,841 --> 00:35:31,841 But as you can see there's really nothing different in Equidox, the main recommendation 701 00:35:31,841 --> 00:35:32,841 that I would have would be just to address the links before you create the table, because 702 00:35:32,841 --> 00:35:33,841 that table is a very large zone. 703 00:35:33,841 --> 00:35:34,841 So once you've created it, it's can be kind of tedious to try to like draw zones outside 704 00:35:34,841 --> 00:35:35,841 of it and drag it in place, So I would recommend creating the links first which were in this 705 00:35:35,841 --> 00:35:36,841 case created automatically because they were encoded into the source file. But once you 706 00:35:36,841 --> 00:35:37,841 got those links identified, when you place that table on top, those links will be maintained, 707 00:35:37,841 --> 00:35:38,841 and they will, of course, have the anchor point that came in with the source file. So 708 00:35:38,841 --> 00:35:39,841 as you click on these links, you can see the anchor point is right here. 709 00:35:39,841 --> 00:35:40,841 So those are now going to be working links inside of this table structure. 710 00:35:40,841 --> 00:35:41,841 Now the nudge feature I'm sorry I forgot about that for a second. the Nudge feature again. 711 00:35:41,841 --> 00:35:42,841 where, if I go to the cells tab, I can nudge all of my columns left. 712 00:35:42,841 --> 00:35:43,841 So if you see they're all kind of moving just very slightly left, I can nudge them to the 713 00:35:43,841 --> 00:35:44,841 right. 714 00:35:44,841 --> 00:35:45,841 I don't really need to in this example because this is pretty a pretty well-spaced table. 715 00:35:45,841 --> 00:35:46,841 But sometimes I see like financial tables where like the previous example. you have 716 00:35:46,841 --> 00:35:47,841 so many rows and so many columns, and they're very, very small. 717 00:35:47,841 --> 00:35:48,841 You don't want to be in a situation we're having to like click on every single one, 718 00:35:48,841 --> 00:35:49,841 and just bump it up and down. 719 00:35:49,841 --> 00:35:50,841 You can spend a lot of time doing, that so we've been we've incorporated this nudge feature, 720 00:35:50,841 --> 00:35:51,841 where everything will move together in unison, depending and if you need to move the rows 721 00:35:51,841 --> 00:35:52,841 up or down or left or right Now I find that this is a tool that I don't use very often 722 00:35:52,841 --> 00:35:53,841 because the computer vision and machine learning is very good at detecting the table structure 723 00:35:53,841 --> 00:35:54,841 just automatically. 724 00:35:54,841 --> 00:35:55,841 So. But there, there will be the occasional, instance, where like I said you have a very 725 00:35:55,841 --> 00:35:56,841 dense table, and it needs just a slight adjustment. 726 00:35:56,841 --> 00:35:57,841 So it's there when you need it But I probably use it on less than 5% of the tables that 727 00:35:57,841 --> 00:35:58,841 I see 728 00:35:58,841 --> 00:35:59,841 Now let's Let me go to the next page here. This is another example of different elements 729 00:35:59,841 --> 00:36:00,841 that can fall inside of table structure. 730 00:36:00,841 --> 00:36:01,841 So here. This is not necessarily a table, but I can use it as an example just to keep 731 00:36:01,841 --> 00:36:02,841 us in the same document here. So we have a list. 732 00:36:02,841 --> 00:36:03,841 We have lists inside of table structure, so what I can do is I can just draw, like, I 733 00:36:03,841 --> 00:36:04,841 said before, the similar to the links. 734 00:36:04,841 --> 00:36:05,841 I like to address the list first, and then create the table on top of it. 735 00:36:05,841 --> 00:36:06,841 So I'm just drawing a zone over the list and I'm! 736 00:36:06,841 --> 00:36:07,841 Hitting L. and Then I'm bumping the list detection Slider from left to right, so as I bumped 737 00:36:07,841 --> 00:36:08,841 that list detection. 738 00:36:08,841 --> 00:36:09,841 Slider I'm picking up the list items automatically So I'm just bumping it left to right and left 739 00:36:09,841 --> 00:36:10,841 to right. 740 00:36:10,841 --> 00:36:11,841 So I'm able to create those 3 separate lists inside of these 3 separate cells. 741 00:36:11,841 --> 00:36:12,841 Now, once I've done that I can draw that table zone on top, and I will again hit t and open 742 00:36:12,841 --> 00:36:13,841 up the table. 743 00:36:13,841 --> 00:36:14,841 Editor. So, because I have these lists here I don't really need any extra rows. 744 00:36:14,841 --> 00:36:15,841 I just need one column, and I don't need the extra rows there and then. 745 00:36:15,841 --> 00:36:16,841 I can just span across up here. So when I span and I take a look at the HTML preview, 746 00:36:16,841 --> 00:36:17,841 I don't know why that I must be having some sort of glitch with my Internet or something 747 00:36:17,841 --> 00:36:18,841 to get that error message but here I am in the HTML preview. You can see I have the list 748 00:36:18,841 --> 00:36:19,841 structure inside of the table. 749 00:36:19,841 --> 00:36:20,841 Now, just because by defaults, Equidox, assumes that your first column is a row header, it's 750 00:36:20,841 --> 00:36:21,841 giving me that bold frontier to just give me that visual, and for that visual confirmation 751 00:36:21,841 --> 00:36:22,841 through the interface. But again I can change my row header from one to and when I go back 752 00:36:22,841 --> 00:36:23,841 to my preview you'll see that I have just that some font for the individual lists. 753 00:36:23,841 --> 00:36:24,841 So those are the 2 common elements that I see Often inside of tables are lists and links. 754 00:36:24,841 --> 00:36:25,841 Another one that you might uncover, are things like footnote links which we have an example 755 00:36:25,841 --> 00:36:26,841 of. 756 00:36:26,841 --> 00:36:27,841 Actually, I believe, a client sent this in if I take a look at this document here. 757 00:36:27,841 --> 00:36:28,841 We'll just pull up like page 2 and we can look there's actually footnotes that fall 758 00:36:28,841 --> 00:36:29,841 underneath this table. 759 00:36:29,841 --> 00:36:30,841 Now ootnotes are not really ideal for tables, because what the footnote is going to do, 760 00:36:30,841 --> 00:36:31,841 It's going to direct the user outside of the table, and then it's going to return them 761 00:36:31,841 --> 00:36:32,841 to the top left cell essentially of the table, and they have to renavigate through. 762 00:36:32,841 --> 00:36:33,841 So it's really not ideal for usability purposes. 763 00:36:33,841 --> 00:36:34,841 But in many cases you are not the designer of the document you've just been given a document 764 00:36:34,841 --> 00:36:35,841 and you've been asked to tag it. 765 00:36:35,841 --> 00:36:36,841 So we’ll work through it with using Equidox. 766 00:36:36,841 --> 00:36:37,841 So I'm gonna just build this kind of manually here to show you the step-by-step process. 767 00:36:37,841 --> 00:36:38,841 So. so I have 2 tech zones capturing my 2 footnotes. 768 00:36:38,841 --> 00:36:39,841 What I'll do, is I will direct these I'll change these to footnotes through the drop-down 769 00:36:39,841 --> 00:36:40,841 menu. 770 00:36:40,841 --> 00:36:41,841 You'll see Now they say FN and FN and FN for the zone types instead of text. 771 00:36:41,841 --> 00:36:42,841 And then here are those reference points inside of the table. 772 00:36:42,841 --> 00:36:43,841 So if I draw 2 zones and I'm just going to put it over the entire, the entire character 773 00:36:43,841 --> 00:36:44,841 there. 774 00:36:44,841 --> 00:36:45,841 I'm just gonna these can be it can be kind of tedious to deal with tiny little these 775 00:36:45,841 --> 00:36:46,841 tiny little superscripts for the footnote reference links. 776 00:36:46,841 --> 00:36:47,841 But what I'll do, is I'll draw the 2 zones and place them on top of those and then I 777 00:36:47,841 --> 00:36:48,841 will create these as footnote links, and I'll direct these footnote links to the corresponding 778 00:36:48,841 --> 00:36:49,841 footnote down here. So I have a drop-down menu that will tell me which zone I want you 779 00:36:49,841 --> 00:36:50,841 directed to. so I want to direct the first footnote to this footnote here, and I want 780 00:36:50,841 --> 00:36:51,841 to direct the second footnote to the second footnote: Right here. 781 00:36:51,841 --> 00:36:52,841 So once I've created that I can then just draw my table and then open up the table. 782 00:36:52,841 --> 00:36:53,841 Editor, and again you'll see that those blue bars are those blue boxes there, indicating 783 00:36:53,841 --> 00:36:54,841 that I have that I have. footnote Links zones place their back on the PDF. 784 00:36:54,841 --> 00:36:55,841 And again, just using my Detection Slider. None of this is very hard. This is all getting 785 00:36:55,841 --> 00:36:56,841 kind of repetitive but I think I hope you're able to see how simple this is by comparison, 786 00:36:56,841 --> 00:36:57,841 especially if you've done this before. 787 00:36:57,841 --> 00:36:58,841 But once I've got those rows and columns in their general location. 788 00:36:58,841 --> 00:36:59,841 If I take a look at the HTML preview you'll see that I have some sort of duplication here. 789 00:36:59,841 --> 00:37:00,841 I wonder what that's from there. we go so you can see we have the developed category, 790 00:37:00,841 --> 00:37:01,841 and the number one. 791 00:37:01,841 --> 00:37:02,841 And then there's your little superscript with the footnote reference, and the same thing. 792 00:37:02,841 --> 00:37:03,841 Here you have the number 2, and if you look closely it is highlighted blue, and it's actually 793 00:37:03,841 --> 00:37:04,841 an active hyperlink that you can click on. 794 00:37:04,841 --> 00:37:05,841 So I will save this table, and I will close out. 795 00:37:05,841 --> 00:37:06,841 So that is what table remediation looks like when you have footnotes, and if you look at 796 00:37:06,841 --> 00:37:07,841 the full-page preview, you can see you have your footnotes down below, and those references 797 00:37:07,841 --> 00:37:08,841 will direct them to the corresponding 798 00:37:08,841 --> 00:37:09,841 Footnote: Okay, So we have about 5 min left, and I wanted to just cover one other example. 799 00:37:09,841 --> 00:37:10,841 If I were to look at a table like this, and forgive me for jumping around to so many documents. 800 00:37:10,841 --> 00:37:11,841 I know it can be kind of a lot to look at as we go from document to document. 801 00:37:11,841 --> 00:37:12,841 But there really is no perfect single document that covers all of these sorts of unique instances. 802 00:37:12,841 --> 00:37:13,841 but this table here is kind of unique, because if you look at it, there is this temperature 803 00:37:13,841 --> 00:37:14,841 which is actually a row header that pertains to these 804 00:37:14,841 --> 00:37:15,841 6 rows here, and per person again pertains to these 6 rows, but they're not visually 805 00:37:15,841 --> 00:37:16,841 situated in the table in such a way that can accurately tag where you tag the temperature 806 00:37:16,841 --> 00:37:17,841 and precipitation as row headers that have these child rows 807 00:37:17,841 --> 00:37:18,841 underneath it but I'm going to show you in Equidox how we can fix this. 808 00:37:18,841 --> 00:37:19,841 So I'm going to draw a table I'm going to draw a zone, and if you notice I've left a 809 00:37:19,841 --> 00:37:20,841 little bit of a margin down the left-hand side and again I'm gonna hit t for table and 810 00:37:20,841 --> 00:37:21,841 I will open up the Table Editor So, creating my rows and columns. 811 00:37:21,841 --> 00:37:22,841 Okay, that looks pretty good, and I will just drag this one over a hair. 812 00:37:22,841 --> 00:37:23,841 So that will give us our basic table structure, not going to span. 813 00:37:23,841 --> 00:37:24,841 Get rid of some of these spannings and then I'm going to create an extra column over here 814 00:37:24,841 --> 00:37:25,841 on the far left side, and I'll explain why, in just a second. 815 00:37:25,841 --> 00:37:26,841 So by creating that extra column. what I'm going to do then, is I'm going to actually 816 00:37:26,841 --> 00:37:27,841 migrate this information. 817 00:37:27,841 --> 00:37:28,841 So precipitation and temperature I'm going to place them over here in this extra column, 818 00:37:28,841 --> 00:37:29,841 and span down these blanks cells to make it so that this is a row header for these 6 rows 819 00:37:29,841 --> 00:37:30,841 So what I'll do 820 00:37:30,841 --> 00:37:31,841 to accomplish this is I'm gonna get rid of this extra row here because I won't need it 821 00:37:31,841 --> 00:37:32,841 and I don't need all these blank cells over here and I'm going to go to the cells tab 822 00:37:32,841 --> 00:37:33,841 and then in 823 00:37:33,841 --> 00:37:34,841 the cells tab. If I go to custom in the drop-down menu for the cell source, I go to custom, 824 00:37:34,841 --> 00:37:35,841 I can actually cut the temperature right out of this particular cell, and I can paste it 825 00:37:35,841 --> 00:37:36,841 into this cell here and once I've done that I can then span the corresponding rows, and 826 00:37:36,841 --> 00:37:37,841 by doing that before I do the precipitation I'll show you where you now have temperature 827 00:37:37,841 --> 00:37:38,841 as a row header for these rows here so this is a way of kind of making without making 828 00:37:38,841 --> 00:37:39,841 visual edits to the templates, or going back and redesigning the table. 829 00:37:39,841 --> 00:37:40,841 You're able to make these adjustments to how this will be tagged on export simply by going 830 00:37:40,841 --> 00:37:41,841 through these steps, so it can be a little bit confusing in the beginning. 831 00:37:41,841 --> 00:37:42,841 But once you get the hang of it it becomes second nature where you're just taking what 832 00:37:42,841 --> 00:37:43,841 doesn't belong there, and placing it where it does belong, which is over here in this 833 00:37:43,841 --> 00:37:44,841 column, which is actually doesn't have any content in it, but 834 00:37:44,841 --> 00:37:45,841 we're able to place that content in it using custom so I'm able to then set myself up with 835 00:37:45,841 --> 00:37:46,841 2 row headers, and I have one and 2 column headers, so I will I'll have my ratio at 2 836 00:37:46,841 --> 00:37:47,841 to 2, and when I look at the HTML preview have temperature, precipitation, and then 837 00:37:47,841 --> 00:37:48,841 the other categories here that fall underneath those sort of parent row headers, One other 838 00:37:48,841 --> 00:37:49,841 thing that I can mention here with our last moment is that these months are actually labeled 839 00:37:49,841 --> 00:37:50,841 with just the letter which can be a little bit confusing if you're not quite sure exactly 840 00:37:50,841 --> 00:37:51,841 that these are referring to months. 841 00:37:51,841 --> 00:37:52,841 So instead of J, I can again go into the cell source, and I can change it to custom. 842 00:37:52,841 --> 00:37:53,841 And I can actually type out January, and I could repeat that for these 12 months. 843 00:37:53,841 --> 00:37:54,841 But the idea is that if you don't have like the full context, or something of a table 844 00:37:54,841 --> 00:37:55,841 needs to be edited. 845 00:37:55,841 --> 00:37:56,841 Maybe it's the use of acronyms maybe it's blank cells. 846 00:37:56,841 --> 00:37:57,841 Maybe it's dashes instead of you know zeros or it could be different. 847 00:37:57,841 --> 00:37:58,841 Symbols that are non-standard. and a screen reader might not be able to read you're able 848 00:37:58,841 --> 00:37:59,841 to go in and actually insert additional contexts, and it really increase the value of that table 849 00:37:59,841 --> 00:38:00,841 by providing the full word which can be enunciated by a screen reader rather than just “JFM” 850 00:38:00,841 --> 00:38:01,841 and so on, and so forth so that's part of the 851 00:38:01,841 --> 00:38:02,841 problem that is J and J for June and July that can cause confusion. 852 00:38:02,841 --> 00:38:03,841 So Which which column are you actually in? Are you in June month, or are you in July 853 00:38:03,841 --> 00:38:04,841 month? 854 00:38:04,841 --> 00:38:05,841 So just going through like extra steps like that can really increase the value of a table 855 00:38:05,841 --> 00:38:06,841 for an end-user. 856 00:38:06,841 --> 00:38:07,841 Okay, So it is 2, 30, and I wanted to I just thank everyone for joining. 857 00:38:07,841 --> 00:38:08,841 I'm gonna jump back to the slide deck here and get us to our contact screen. 858 00:38:08,841 --> 00:38:09,841 So I just I want to thank everyone again for joining us for another edition of Equodox 859 00:38:09,841 --> 00:38:10,841 Webinar Wednesdays. I don't know. 860 00:38:10,841 --> 00:38:11,841 That was kind of a fast-paced training, if you will, showing some different table examples. 861 00:38:11,841 --> 00:38:12,841 But I hope that you found value in it and like, I said, for anyone that is on this call 862 00:38:12,841 --> 00:38:13,841 that is not an existing Equidox user or client please feel free to reach out to us at EquidoxSales@Onixnet.com 863 00:38:13,841 --> 00:38:14,841 or visit our website and get in touch with us to talk more about your specific use case 864 00:38:14,841 --> 00:38:15,841 your PDF challenges. 865 00:38:15,841 --> 00:38:16,841 We'd be we'd love to learn about it and we'd love to talk to you about how we can help. 866 00:38:16,841 --> 00:38:17,841 We're also very active on social media so Linkedin Twitter. 867 00:38:17,841 --> 00:38:18,841 We have a whole bunch of information up on Youtube. So please follow us on any of these 868 00:38:18,841 --> 00:38:19,841 social media platforms that you use. 869 00:38:19,841 --> 00:38:20,841 And I believe Tammy will be sending out a short survey after this webinar. So if you 870 00:38:20,841 --> 00:38:21,841 could just take a moment to fill out that survey, we really appreciate the feedback. 871 00:38:21,841 --> 00:38:22,841 It really helps us kind of address challenges or questions that any people might be having 872 00:38:22,841 --> 00:38:23,841 and helps us kind of tailor these webinars to be as relevant as possible for the most 873 00:38:23,841 --> 00:38:24,841 amount of people. 874 00:38:24,841 --> 00:38:25,341 So thank you very much. Everyone have a great rest of your afternoon.