1
00:00:01,020 --> 00:00:03,020
Equidox by Onix

2
00:00:03,679 --> 00:00:05,200
Reach everyone

3
00:00:05,200 --> 00:00:09,519
Hello everyone. Welcome to our Equidox Smart Table Detector webinar.

4
00:00:10,080 --> 00:00:14,160
My name is Dan Tuleta and I am a sales engineer here with the Equidox team.

5
00:00:14,719 --> 00:00:20,399
And I'm going to be walking you through some of our new technology regarding the way that we detect tables in Equidox.

6
00:00:21,039 --> 00:00:28,159
If you have any questions about this webinar or anything else related to Equidox, please don't hesitate to reach out to us at any time

7
00:00:29,279 --> 00:00:31,039
Okay, so let's get into it!

8
00:00:31,039 --> 00:00:36,639
I'm going to open up Equidox here in my browser and i'm just going to start here on this

9
00:00:36,719 --> 00:00:39,439
example here that has a few tables in it

10
00:00:40,079 --> 00:00:42,398
So if I just navigate to the first page...

11
00:00:43,040 --> 00:00:44,879
What I'll see is

12
00:00:44,879 --> 00:00:52,799
A page that contains very clearly a table. We're able to see that we definitely have rows and columns and headers and things like that

13
00:00:53,520 --> 00:00:59,680
But what I'm noticing is that every zone has actually been detected as a text zone.

14
00:01:00,399 --> 00:01:06,319
This is not ideal. This is not the structure that we're looking for if anyone has used Equidox before,

15
00:01:06,880 --> 00:01:12,799
You might be familiar with this process. But if I take a look at the preview just as things currently stand.

16
00:01:13,840 --> 00:01:15,439
This is what I'm

17
00:01:15,439 --> 00:01:18,319
Going to experience if i'm using a screen reader

18
00:01:19,200 --> 00:01:20,080
so

19
00:01:20,080 --> 00:01:26,819
Considering everything is a text zone. Meaning that's going to be wrapped up in a P tag when we go to export this document.

20
00:01:27,900 --> 00:01:33,139
Everything is going to just be read in this reading order. So this has no table structure whatsoever.

21
00:01:34,159 --> 00:01:38,798
Every one of these individual cells has been marked as a paragraph, which is not ideal.

22
00:01:39,200 --> 00:01:43,280
So to fix this we're just going to ignore all of those different text zones.

23
00:01:43,600 --> 00:01:46,799
And we're going to draw a zone on top of the table.

24
00:01:47,600 --> 00:01:54,960
And once I've done that I will go to the drop down menu and change the zone type from text to table.

25
00:01:56,000 --> 00:02:01,759
And when I do that, I now have a button that will populate underneath table properties that's called Table Editor

26
00:02:02,240 --> 00:02:06,000
So when I open up the Table Editor I've now isolated the table for myself.

27
00:02:06,719 --> 00:02:11,519
And the first thing i'm noticing is I have these green grid lines that have suddenly appeared.

28
00:02:12,160 --> 00:02:19,839
So Equidox took a guess at the basic layout of the table. Just based on how I drew the table zone.

29
00:02:20,640 --> 00:02:25,459
It can certainly do a bit better though. And that's why we have our new technology the Table Detector.

30
00:02:26,000 --> 00:02:33,759
So I have two different sliders columns and rows and these are actually leveraging machine learning and computer vision

31
00:02:34,640 --> 00:02:42,160
to help us better recognize table structure and just minimize the amount of actual manual manipulation that we have to make to tables.

32
00:02:42,720 --> 00:02:43,680
so in this case

33
00:02:43,680 --> 00:02:48,340
My columns have been placed on top of the table by Equidox pretty much perfectly

34
00:02:48,640 --> 00:02:50,640
So I don't even really need to adjust the columns.

35
00:02:50,959 --> 00:02:57,199
But the rows you'll notice I'm missing some rows. I need some additional rows and these aren't exactly place where I want them.

36
00:02:57,599 --> 00:03:01,279
So if I move the row slider back and forth just slightly

37
00:03:02,239 --> 00:03:05,518
You'll notice that now I suddenly have rows

38
00:03:06,400 --> 00:03:08,400
placed perfectly on the table

39
00:03:08,400 --> 00:03:11,039
And my columns have moved over just slightly.

40
00:03:11,519 --> 00:03:17,279
But I can quickly make that fix by using our nudge feature. so I can nudge those back to the right if I need to.

41
00:03:17,680 --> 00:03:24,720
Or I can even click and draw and make these tiny adjustments if needed. We don't have to get everything perfect on the table

42
00:03:24,799 --> 00:03:29,119
So if I left my column right there, it would not make a difference

43
00:03:30,319 --> 00:03:35,999
Because I have good spacing in this table. It's really just about capturing the data inside of the cell.

44
00:03:36,400 --> 00:03:41,940
So having it perfectly lined up with the table grid lines is not required.

45
00:03:42,560 --> 00:03:47,679
Um, it's just simply the the grid lines are going to disappear once we're done working on the table anyway.

46
00:03:47,760 --> 00:03:53,280
So if we're not doing this for aesthetic, we're just simply trying to capture the data in these individual cells.

47
00:03:54,000 --> 00:04:01,759
So we remember what that preview of that table looked like before which was not a table at all. Just a series of

48
00:04:02,400 --> 00:04:07,920
words that were going to be read in this specific reading order with no structure no navigation for them.

49
00:04:08,319 --> 00:04:11,199
So what I'll do is if I refresh the preview now.

50
00:04:11,920 --> 00:04:14,959
You'll see that I have a perfect HTML table.

51
00:04:15,760 --> 00:04:20,479
And all I've had to do is move those... adjust those sliders from left to right just slightly.

52
00:04:21,440 --> 00:04:28,639
So, uh, that's how easy it is to remediate tables in Equidox for your average, you know, standard table.

53
00:04:29,680 --> 00:04:34,799
It's really just a matter of moving those detection bars left to right and Equidox does the rest for you.

54
00:04:35,199 --> 00:04:41,839
Now the beauty of this is if you are converting this document into HTML, this is exactly what you will export.

55
00:04:42,080 --> 00:04:44,080
Essentially you're going to be exporting this

56
00:04:44,300 --> 00:04:46,960
HTML table, it looks exactly like this and

57
00:04:47,600 --> 00:04:54,959
will be very compatible with a screen reader... very easy to work with. But if you choose to export the document as a PDF file,

58
00:04:55,360 --> 00:04:58,960
which many people do, it's definitely our most popular export format.

59
00:05:00,400 --> 00:05:04,979
If you're going to export it as a PDF Equidox automatically takes this HTML

60
00:05:05,520 --> 00:05:10,720
source code that we have here in this table and it will plug it into a PDF tag tree for you.

61
00:05:10,960 --> 00:05:16,079
So that you are not having to make any sort of manipulations or adjustments to the tag tree.

62
00:05:16,639 --> 00:05:19,918
This is going to happen automatically when we export the PDF.

63
00:05:20,720 --> 00:05:25,279
So this HTML page is really a way to just validate your work as you go.

64
00:05:25,680 --> 00:05:28,820
When you're satisfied with the structure that you see here in your HTML,

65
00:05:29,280 --> 00:05:32,399
that is your indication that you can go back to the page or the

66
00:05:32,960 --> 00:05:39,440
Table Editor, save your table, and then just close out and then you'll return to the main page where we started.

67
00:05:40,400 --> 00:05:43,759
And you'll notice that we've gotten rid of all of those

68
00:05:44,240 --> 00:05:48,639
different text zones that were there before they have been overridden by the table zone.

69
00:05:49,199 --> 00:05:54,959
So that's uh, you're not having to go through and delete, you know, 50 different text zones.

70
00:05:55,520 --> 00:05:57,520
Equidox does that for you.

71
00:05:58,560 --> 00:06:00,959
Okay, so let's take a look here at the next page.

72
00:06:01,840 --> 00:06:08,799
And this next page is again a different type of table in the sense that it doesn't have any grid lines wrapping around it

73
00:06:08,800 --> 00:06:11,199
So maybe it's a little bit less obvious that it's a table

74
00:06:11,759 --> 00:06:15,679
Um, but in fact, we actually do have table structure here.

75
00:06:16,319 --> 00:06:23,919
We have the song here and band as our column headers and then a variety of different, you know hit songs from those different years.

76
00:06:24,720 --> 00:06:28,880
So if we uh again just drawing a zone around the entire table.

77
00:06:30,000 --> 00:06:34,239
And then hitting T on my keyboard this time, so I'm going to use my keyboard shortcut

78
00:06:34,319 --> 00:06:37,039
so to change the zone type from text to table I

79
00:06:37,120 --> 00:06:41,759
just press the T on my keyboard and that will allow me to open up the Table Editor

80
00:06:43,120 --> 00:06:46,720
And then if I just zoom out slightly here to make it a little bit easier to see.

81
00:06:48,400 --> 00:06:51,440
Again we have green grid lines that have been placed

82
00:06:52,080 --> 00:06:55,280
not exactly perfect. It can definitely do a bit better.

83
00:06:55,840 --> 00:06:56,639
so

84
00:06:56,639 --> 00:06:58,639
Let's use our Table Detector

85
00:06:58,639 --> 00:07:04,159
And if I just move my column from left to right you'll see it's nailed the columns and now let's try for the rows.

86
00:07:04,479 --> 00:07:08,159
So moving the rows from left to right and it looks like it's got it pretty much perfect.

87
00:07:08,880 --> 00:07:13,439
I'm, not really going to be able to do any better than that because i've got it exactly spot on so...

88
00:07:14,080 --> 00:07:16,720
Let's just check the preview and see how things look.

89
00:07:17,680 --> 00:07:19,680
Pretty much exactly what I would expect to see.

90
00:07:20,720 --> 00:07:22,720
Now if you're curious

91
00:07:22,720 --> 00:07:27,679
about the bold font that is appearing here in the top row in the furthest left column.

92
00:07:28,479 --> 00:07:32,639
This is actually indicating that these are going to be marked as table headers.

93
00:07:32,960 --> 00:07:36,160
So these are our row headers and these are our column headers up here.

94
00:07:36,880 --> 00:07:42,559
And um, this is just applied by default by Equidox at a one to one ratio.

95
00:07:42,960 --> 00:07:48,560
So one row of column headers one column of row headers that can of course be changed if needed.

96
00:07:48,879 --> 00:07:55,599
So if you have multiple column headers or in this case, we don't really have true row headers. So these song titles

97
00:07:55,759 --> 00:08:01,199
Um, they're they're marked with that column header up there. We don't really need these to be marked as row headers.

98
00:08:01,520 --> 00:08:06,479
So what I can do is I can go back to the table editor and underneath my table information,

99
00:08:07,520 --> 00:08:10,639
I have the column header and row header these two little fields here.

100
00:08:11,280 --> 00:08:15,919
You can see that they're just at a one-to-one ratio by default. So if I mark my row header as

101
00:08:16,639 --> 00:08:19,439
zero by just using the arrow key moving it down to zero...

102
00:08:20,319 --> 00:08:22,319
And then if I refresh the preview...

103
00:08:22,800 --> 00:08:29,599
You'll see that now that bold font has disappeared and the only bold is in the top row there for the column headers.

104
00:08:30,400 --> 00:08:36,399
So this is uh, this is a better way of structuring this table by taking that row header away.

105
00:08:37,039 --> 00:08:40,958
And just leaving the three separate column headers for the three separate columns.

106
00:08:41,760 --> 00:08:48,159
Okay, so that's another pretty straightforward table. I don't have to do a whole lot to it. I'm just using our Table Detector.

107
00:08:48,880 --> 00:08:51,439
It's very fast very easy to work with and again,

108
00:08:51,519 --> 00:08:55,759
all of that will automatically be converted into a PDF tag tree when we go to export it.

109
00:08:57,760 --> 00:09:03,599
Okay, so now we are faced with a slightly more challenging table, you might see that there's

110
00:09:04,320 --> 00:09:10,879
a lot more cells there's more densely spaced data. We have multiple rows of column headers.

111
00:09:11,519 --> 00:09:13,519
So we have a bit more to do here.

112
00:09:14,080 --> 00:09:16,080
So what i'll do is I will just again,

113
00:09:16,399 --> 00:09:21,839
same process as always drawing that table zone around the table. I will press T on my keyboard.

114
00:09:22,160 --> 00:09:24,160
And I can now open up the Table Editor.

115
00:09:25,519 --> 00:09:31,599
So, uh we are now looking at just the table and let's use the Table Detector and see if we can improve on it

116
00:09:32,880 --> 00:09:36,159
And it looks like we can certainly give ourselves a nice starting point.

117
00:09:36,959 --> 00:09:40,399
So we've pretty much defined this table spot on.

118
00:09:41,040 --> 00:09:44,480
We could potentially move this to the left slightly...

119
00:09:45,360 --> 00:09:49,200
just to get it more lined up, but it probably wouldn't make all that much of a difference because again,

120
00:09:49,200 --> 00:09:51,040
We're just trying to capture the data.

121
00:09:51,040 --> 00:09:57,279
We're not using these green grid lines for any uh, you know aesthetics they are going to vanish as soon as we save the table.

122
00:09:58,320 --> 00:10:03,839
Um, so let's just take a look at the structure here and see how we're doing. Um, it looks pretty good.

123
00:10:04,800 --> 00:10:09,039
but the one concern or two concerns are this top row up here the

124
00:10:09,579 --> 00:10:11,279
2017 and 18.

125
00:10:11,279 --> 00:10:18,398
Those are being split. We're left with some empty cells up here in our column header row. That's not going to be ideal...

126
00:10:18,800 --> 00:10:20,399
and then we also have

127
00:10:20,399 --> 00:10:23,999
Our Q1 through Q4s, which are in that standard font...

128
00:10:24,720 --> 00:10:30,480
indicating that they're going to be read as table data, whereas we really need them to be read as table headers.

129
00:10:31,339 --> 00:10:34,639
So let's go back to the Table Editor and clean this up a bit.

130
00:10:35,440 --> 00:10:40,640
If I want to in this case, I want to span across these four separate columns...

131
00:10:41,200 --> 00:10:42,060
because

132
00:10:42,060 --> 00:10:47,200
2017 is sort of a parent header for the four individual quarters that make up 2017.

133
00:10:47,760 --> 00:10:49,760
So if I select here above Q1,

134
00:10:50,320 --> 00:10:54,640
And I hold down shift on my keyboard and then select above Q4...

135
00:10:55,360 --> 00:10:58,159
I have a button up here to span those columns.

136
00:10:58,800 --> 00:11:00,800
Or I could press S on my keyboard

137
00:11:01,440 --> 00:11:03,440
so when I press S

138
00:11:03,440 --> 00:11:09,760
That is going to create that span for me and I will do the same thing here for 2018. I will hold down shift,

139
00:11:10,399 --> 00:11:15,359
select above Q4 and press S and then when I refresh the preview...

140
00:11:16,640 --> 00:11:18,160
You'll now see that

141
00:11:18,160 --> 00:11:25,360
we've gotten rid of those empty cells and 2017 and 2018 have been spanned across the four appropriate columns.

142
00:11:26,240 --> 00:11:32,159
Now one last thing to fix here is our Q1s or Q4s. We want those to be read as table headers.

143
00:11:33,120 --> 00:11:33,839
Whereas right now

144
00:11:33,839 --> 00:11:37,119
they're going to be read as table data if we go to export this document.

145
00:11:37,600 --> 00:11:40,560
So to fix that we will come back into our Table Editor.

146
00:11:40,880 --> 00:11:45,999
And again, it's just this automatic ratio of one to one for column and row headers

147
00:11:46,160 --> 00:11:48,959
So if I just change my column header from one to two...

148
00:11:50,000 --> 00:11:53,519
That is going to give me two rows of column headers.

149
00:11:54,160 --> 00:11:58,399
And now when I refresh the preview, we will see that the bold font

150
00:11:58,800 --> 00:12:02,800
is there uh indicating that those are now marked as table headers.

151
00:12:03,600 --> 00:12:08,800
So that's really all we have to do to this table. Uh, there's nothing else that I would recommend doing. This is perfect

152
00:12:09,339 --> 00:12:10,399
structure.

153
00:12:10,399 --> 00:12:12,399
And we can then save the table.

154
00:12:12,720 --> 00:12:15,279
One other thing I will mention on this table is,

155
00:12:15,920 --> 00:12:22,019
If you noticed as I was making adjustments to the table this table summary field started populating.

156
00:12:22,959 --> 00:12:27,839
And this is a really handy feature and it's one of our new enhancements to the table editing tool.

157
00:12:28,639 --> 00:12:33,359
This is Equidox programmatically writing the table summary for you.

158
00:12:34,079 --> 00:12:36,079
And when you have the table summary,

159
00:12:36,959 --> 00:12:40,159
Turned on... the auto summary turned on. Um, it's good.

160
00:12:40,240 --> 00:12:45,279
it's just really nice to have a consistently written table summary, and you're not having to

161
00:12:45,920 --> 00:12:50,420
write it and then you also don't have you know, if you have 20 different users in your organization,

162
00:12:50,720 --> 00:12:53,920
They're not all sort of interpreting. What a table summary is supposed to be.

163
00:12:54,560 --> 00:12:56,560
Equidox is going to

164
00:12:56,639 --> 00:13:02,719
keep that nice and consistent for you. And also just save you the hassle of having to type it all out.

165
00:13:03,360 --> 00:13:09,120
So as you make adjustments to the table this table summary will start to change based on the adjustments that you make.

166
00:13:10,079 --> 00:13:15,359
So in this case, you know, for example the header column contains column spans, so

167
00:13:16,240 --> 00:13:17,600
as I'm

168
00:13:17,600 --> 00:13:24,959
spanning across those. Um, it's giving you that indication that there are spans in that top, uh column header.

169
00:13:25,279 --> 00:13:29,759
So, uh, you're getting all of this nicely written for you and you're not having to do it yourself.

170
00:13:30,480 --> 00:13:32,480
You're going to keep it nice and consistent.

171
00:13:32,720 --> 00:13:38,959
You have to turn on the auto summary feature in your profile, which i'll make sure to show you before the end of the webinar.

172
00:13:40,480 --> 00:13:42,880
Okay, so that's really about all we have for this document.

173
00:13:43,120 --> 00:13:49,359
This is only three pages and contain three separate tables. But let's take a look at something that might have

174
00:13:49,920 --> 00:13:52,399
a little bit of a different curveball for us.

175
00:13:53,519 --> 00:13:54,399
so

176
00:13:54,399 --> 00:13:56,399
Let's open up this table.

177
00:13:56,560 --> 00:14:02,959
Now on its face, this is probably the most simple table we've looked at yet, and that's true. So just to

178
00:14:03,920 --> 00:14:06,479
Quickly go through it. We'll press T on our keyboard...

179
00:14:08,639 --> 00:14:10,639
Open up the Table Editor...

180
00:14:11,440 --> 00:14:15,699
And let's use our detection to move things left and right.

181
00:14:19,760 --> 00:14:23,039
Perfect, all right. So this is what this is the setting that I was looking for.

182
00:14:23,519 --> 00:14:27,839
Um, so what you'll notice is i've got it pretty much spot on where it needs to be.

183
00:14:28,480 --> 00:14:30,399
And as I said before,

184
00:14:30,399 --> 00:14:32,399
You don't have to get the green grid lines perfect.

185
00:14:32,639 --> 00:14:38,159
But if you ever run into an instance where you have all of your columns or all of your rows

186
00:14:38,240 --> 00:14:41,120
Or maybe just offset from where they need to be by

187
00:14:41,680 --> 00:14:45,039
a few pixels or in this case, you know, maybe a half inch...

188
00:14:45,760 --> 00:14:49,439
Um, what we have is a feature called the nudge feature.

189
00:14:50,399 --> 00:14:55,679
So if you go to the Cells Tab in the Table Editor, um, this is the second tab over...

190
00:14:56,720 --> 00:15:01,300
What you will see is we have the column adjustments and the row adjustments.

191
00:15:02,320 --> 00:15:06,719
So these are for nudging the columns and the rows up and down or left and right.

192
00:15:07,040 --> 00:15:11,839
So in this case, I want to nudge my columns over and if I nudge them all to the right....

193
00:15:12,000 --> 00:15:14,000
You'll see as I click on them,

194
00:15:14,160 --> 00:15:18,480
Uh multiple times, all of those columns start to move in unison.

195
00:15:19,519 --> 00:15:24,959
So it's not really that big of a deal here for this very simple table because I could just very quickly click and move things

196
00:15:25,339 --> 00:15:31,599
over but if you can imagine, you know a financial table that might have a hundred different rows in it...

197
00:15:32,560 --> 00:15:36,880
And maybe every one of those rows is just two pixels lower than where it needs to be...

198
00:15:37,360 --> 00:15:43,440
It's very tedious to have to click and adjust every one of those rows by just a little tiny fraction of an inch.

199
00:15:44,399 --> 00:15:50,719
So having that nudge feature to move everything in unison is really helpful and it will save you know your hand from

200
00:15:50,880 --> 00:15:54,399
you know having to grip the mouse and move things around very slightly.

201
00:15:55,360 --> 00:15:59,919
So that's the nudge feature. Keep that in mind that you have that if you ever need it.

202
00:16:00,320 --> 00:16:05,679
You know typically I'd say over 90 percent of the time Equidox is going to place those column and row

203
00:16:06,720 --> 00:16:08,880
grid lines exactly where they need to be.

204
00:16:09,600 --> 00:16:15,040
Or at least close enough that all of the data is captured that you're not going to have to make any adjustments.

205
00:16:15,920 --> 00:16:21,839
But if you ever need to make sort of those manual type of adjustments you certainly can with the left and right.

206
00:16:23,199 --> 00:16:27,119
And then the other adjusting, uh that you can do on this Cells Tab

207
00:16:28,320 --> 00:16:33,439
os the splitting columns and splitting rows. There's also buttons for them up here as well.

208
00:16:34,079 --> 00:16:37,679
So if you're on the Table Tab, you can still add and delete columns and rows.

209
00:16:38,399 --> 00:16:42,958
But if for example, you need to split a column, you can press the split column button.

210
00:16:43,680 --> 00:16:46,399
And then to get rid of a column you can press merge right.

211
00:16:46,959 --> 00:16:50,719
And the same thing for row, if you press split row you can add a row.

212
00:16:51,120 --> 00:16:55,839
And then merge down will get rid of that row. There's also keyboard shortcuts for this.

213
00:16:56,000 --> 00:17:00,719
so if you press C on your keyboard that will create a new column if you press M

214
00:17:01,120 --> 00:17:04,719
On your keyboard (M is in Michael) that will remove that column.

215
00:17:05,120 --> 00:17:10,799
And R for a new row and then D to delete that row, So you have keyboard shortcuts as well.

216
00:17:11,740 --> 00:17:16,319
Typically, the detection tool is close enough that you're not going to have to do too many,

217
00:17:16,799 --> 00:17:22,079
Um, creation of new rows and columns, you know 99 of the cases...

218
00:17:22,480 --> 00:17:26,319
But if you ever do you have keyboard shortcuts to help you be a little bit faster.

219
00:17:27,760 --> 00:17:30,239
Okay, so i'm going to save this table and close out of it.

220
00:17:31,200 --> 00:17:33,120
We've handled that one.

221
00:17:33,120 --> 00:17:38,719
but this is the table that I really brought you to this document for. So this is a little bit of a curveball because

222
00:17:39,120 --> 00:17:46,020
it looks visually exactly the same as this table up here, but this is actually an image and you can see that in the "IMG"

223
00:17:46,559 --> 00:17:49,519
Little flag in the upper left hand corner of the of the zone.

224
00:17:50,160 --> 00:17:55,359
So, although we can visually see that this is in fact a table that contains text...

225
00:17:57,039 --> 00:17:59,039
It in fact is actually just...

226
00:17:59,280 --> 00:18:01,759
someone took a screenshot or a scan

227
00:18:02,720 --> 00:18:09,839
of this table and placed it into this document. So this is actually just an image this text. Although we can visually read it

228
00:18:10,480 --> 00:18:17,679
in the image, a screen reader cannot. There is no encoded font. There's nothing there to be to be read by a screen reader.

229
00:18:18,080 --> 00:18:22,720
So it's our job as the remediator to make sure that we're giving this actual table structure.

230
00:18:23,600 --> 00:18:25,600
I don't want to take this image file

231
00:18:26,240 --> 00:18:32,479
and use the alt description and start typing out a description for all of the different data in this in this table.

232
00:18:32,799 --> 00:18:37,759
Um, that's going to take a long time and it's also going to overload an alt description, which I don't want to do.

233
00:18:38,320 --> 00:18:40,160
So I'll hide the zone.

234
00:18:40,160 --> 00:18:46,799
Um using the check mark, and that is essentially artifacting the table, or artifacting the image of the table. I should say.

235
00:18:47,280 --> 00:18:51,199
And now I can draw a zone around the table itself.

236
00:18:52,160 --> 00:18:54,160
And then press T on my keyboard.

237
00:18:54,559 --> 00:18:57,678
And then open up the Table Editor just the same process as always.

238
00:18:58,240 --> 00:19:04,579
And here is where I will use the Table Detector again to try to better identify

239
00:19:05,280 --> 00:19:06,480
the

240
00:19:06,480 --> 00:19:07,679
the cells

241
00:19:07,679 --> 00:19:12,559
So this might not be quite as accurate because it has no actual data to go off of, it's just using

242
00:19:12,720 --> 00:19:16,240
like its vision to see that there's something there that looks like text.

243
00:19:17,120 --> 00:19:21,199
So I can I had to make a small adjustment but it's really just takes a couple of seconds.

244
00:19:21,760 --> 00:19:24,319
So now I have everything pretty nicely defined.

245
00:19:25,280 --> 00:19:31,119
Based on the layout of the table. And now if I come down here below the Table Detector tool...

246
00:19:31,840 --> 00:19:33,840
Where I have my row and columns,

247
00:19:34,480 --> 00:19:40,160
I have the optical character recognition section. And if I press "OCR all cells,"

248
00:19:40,720 --> 00:19:48,319
this is going to run an optical character recognition process on all of these individual cells and plug that text data into the table.

249
00:19:48,799 --> 00:19:52,239
So that just took a few seconds because this is a relatively small table.

250
00:19:52,480 --> 00:19:55,520
But if I refresh the preview, let's just see what we're looking at.

251
00:19:56,160 --> 00:20:03,679
Here's our table that's actually OCR and you can see that it's populated that table data with all of the appropriate information.

252
00:20:04,080 --> 00:20:06,080
So i've taken something that's an image,

253
00:20:06,400 --> 00:20:08,559
of a table and i've actually, um,

254
00:20:09,179 --> 00:20:14,158
extracted the text from that image and Equidox has placed it into

255
00:20:14,640 --> 00:20:17,359
a table layout so I have that proper structure.

256
00:20:18,080 --> 00:20:26,000
And now it's actually something that is machine readable, for people that are interacting with the document with assistive technology.

257
00:20:27,200 --> 00:20:34,580
So that's how we can OCR a table. Hopefully you're not tasked with having to do a lot of OCRing

258
00:20:35,200 --> 00:20:37,200
or dealing with OCR tables...

259
00:20:37,919 --> 00:20:44,158
Because they're not always going to be you know, this clean and simple with any tool to be honest.

260
00:20:44,880 --> 00:20:48,959
OCR has a lot of limitations just in general, um dealing with

261
00:20:49,500 --> 00:20:51,500
scanned old Xeroxed

262
00:20:51,600 --> 00:20:56,799
PDFs that, you know,might be 20 years old might have a crease in the middle... might have handwritten notes...

263
00:20:57,039 --> 00:20:59,039
You really just don't know what you're going to have.

264
00:20:59,600 --> 00:21:00,640
so

265
00:21:00,640 --> 00:21:04,640
having, you know a tool like Equidox to quickly convert something into

266
00:21:05,200 --> 00:21:12,960
usable text is helpful. Uh, but again, hopefully you're not dealing with too many of those because you know just OCR data is

267
00:21:13,840 --> 00:21:15,840
is always going to be tricky for screen readers.

268
00:21:17,039 --> 00:21:18,960
Okay, so,

269
00:21:18,960 --> 00:21:24,319
one other thing i'll mention about OCR is if you go to the Cells Tab where I was using the nudge feature before

270
00:21:24,799 --> 00:21:26,640
there is also

271
00:21:26,640 --> 00:21:31,520
This field that will populate you can now see that the cell source has been marked as OCR.

272
00:21:32,320 --> 00:21:35,360
Whereas before it would have been marked as PDF just by default.

273
00:21:36,080 --> 00:21:38,480
Meaning it's pulling the data straight from the PDF file.

274
00:21:39,360 --> 00:21:46,000
But here it actually has the text inside of this window for that specific cell that I have selected.

275
00:21:46,240 --> 00:21:52,640
So if you ever need to make an adjustment to the text, let's say for example, it recognized that one as a lowercase L

276
00:21:53,840 --> 00:21:55,600
(which, you know, sometimes happens)

277
00:21:55,600 --> 00:21:59,919
It just depends on the font, and I know the quality of the scan all sorts of factors are involved.

278
00:22:00,400 --> 00:22:03,199
But if you ever need to make an adjustment, you certainly can.

279
00:22:04,000 --> 00:22:08,239
By just adjusting it here in the text field. We also have another

280
00:22:09,600 --> 00:22:12,159
cell source, which is called Custom

281
00:22:13,039 --> 00:22:17,839
And if you select Custom it will give you a similar looking field, but it won't have anything

282
00:22:18,799 --> 00:22:25,219
it will only have in it what is contained in the cell, but if you need to you can type in something, um..

283
00:22:26,880 --> 00:22:29,039
For example I'll just type in "custom information."

284
00:22:29,679 --> 00:22:32,739
So if you have a table that contains

285
00:22:33,280 --> 00:22:40,159
a lot of blank cells, or if you want to make adjustments to how it is currently laid out

286
00:22:40,640 --> 00:22:45,039
visually on the table on the page (which we can take a look at an example of that shortly)

287
00:22:45,679 --> 00:22:50,579
But that Custom cell source is also helpful. It allows you to plug in information

288
00:22:52,000 --> 00:22:58,959
where maybe the table is missing something that would be critical for a non-visual user to understand that table.

289
00:22:59,679 --> 00:23:02,239
So you have the flexibility there to sort of

290
00:23:03,039 --> 00:23:05,279
work around poorly designed tables.

291
00:23:06,080 --> 00:23:12,000
Because not all tables are this simple where you just have one column header one row header and then some table data.

292
00:23:13,280 --> 00:23:16,559
A lot of people design tables to

293
00:23:17,360 --> 00:23:24,159
be like visually stunning, but the actual structure of them is not very compatible with machine readers. So

294
00:23:24,799 --> 00:23:27,139
tables can get very tricky and complex.

295
00:23:27,360 --> 00:23:33,520
But you have Equidox and all of these tools up your sleeve to quickly work around bad table design...

296
00:23:34,159 --> 00:23:39,359
Because not everyone is designing tables with accessibility in mind when they're  laying them out.

297
00:23:40,799 --> 00:23:44,879
All right. So let's take a look. I want to show you another example of when you might

298
00:23:45,520 --> 00:23:47,200
find the Custom

299
00:23:47,200 --> 00:23:48,559
Cell source

300
00:23:48,559 --> 00:23:50,480
very helpful.

301
00:23:50,480 --> 00:23:56,659
And this is again an example of, this is actually a document that was pre-OCR'd before it came into Equidox.

302
00:23:56,960 --> 00:24:01,840
Which is why we have this giant image that's covering the entire page. So I can just hide that image.

303
00:24:02,480 --> 00:24:04,480
And get rid of that zone altogether.

304
00:24:04,799 --> 00:24:09,538
To artifact that image. because we actually do have the text here that's already been recognized by Equidox.

305
00:24:10,320 --> 00:24:12,320
And it's given us all of these different text zones...

306
00:24:13,120 --> 00:24:13,840
but

307
00:24:13,840 --> 00:24:15,840
I really want to take a look at these tables.

308
00:24:15,840 --> 00:24:20,319
So let me just get rid of all these zones just to look at them at a more clean layout.

309
00:24:21,679 --> 00:24:23,120
so

310
00:24:23,120 --> 00:24:26,880
This table here while it might look very simple on its face...

311
00:24:27,600 --> 00:24:30,400
um, what we actually have are these sort of

312
00:24:31,340 --> 00:24:33,279
strange, um headers

313
00:24:33,279 --> 00:24:37,599
That are inserted into the middle of the table and then they have a blank cell

314
00:24:38,480 --> 00:24:40,480
That they correspond with over here...

315
00:24:41,200 --> 00:24:44,880
So this is kind of an example of, although it's a small table,

316
00:24:45,440 --> 00:24:49,700
this is pretty bad table design as far as accessibility is concerned.

317
00:24:50,320 --> 00:24:54,320
because really this "permanent supply" that we can see here, it actually

318
00:24:54,860 --> 00:24:56,000
pertains,

319
00:24:56,000 --> 00:24:58,559
It's actually a row header for these different

320
00:24:59,200 --> 00:25:02,640
"Irrigation" and the "M&I Water Fishery Flows..." all this stuff.

321
00:25:02,960 --> 00:25:05,199
So this is actually a row header,

322
00:25:05,520 --> 00:25:11,919
but it's not placed in the correct location in the table to be able to quickly define it that way, so,

323
00:25:12,640 --> 00:25:14,000
we can

324
00:25:14,000 --> 00:25:16,959
work around this by just drawing a zone around the table...

325
00:25:17,679 --> 00:25:23,839
And if you're wondering why I'm not including that this is actually not part of the table. So people sometimes get that confused.

326
00:25:24,080 --> 00:25:28,799
They see this big black border outlining the table and they want to include everything.

327
00:25:29,200 --> 00:25:32,640
You don't need to include that part of the table. That can be marked as a header.

328
00:25:33,679 --> 00:25:39,759
You know, which would probably make the document more easily read and navigate for the end users.

329
00:25:41,120 --> 00:25:46,479
So I've identified the table, and I'm going to press T on my keyboard. I will open up the Table Editor...

330
00:25:48,320 --> 00:25:53,360
And let's try our Detection see if we get a better starting point. That looks pretty good, and...

331
00:25:54,080 --> 00:25:56,080
So what I'm going to do here,

332
00:25:56,240 --> 00:26:02,799
is I'm going to basically migrate this "permanent supply" and the "temporary supply."

333
00:26:03,520 --> 00:26:05,839
And I'm going to create them as extra row headers.

334
00:26:06,559 --> 00:26:08,798
And I'm going to get rid of them, so they're not duplicated.

335
00:26:09,039 --> 00:26:11,439
So if we take a look at the preview for how it sits now...

336
00:26:12,000 --> 00:26:14,799
you know, it's pretty much what we would expect to see, but you can

337
00:26:15,440 --> 00:26:19,279
understand the confusion that this would give an end user who's

338
00:26:19,840 --> 00:26:26,159
hearing "temporary supply" and then it doesn't actually have any data that corresponds with it. So to fix this

339
00:26:27,200 --> 00:26:28,720
let's

340
00:26:28,720 --> 00:26:31,039
make sure that we have the right amount of rows.

341
00:26:33,360 --> 00:26:35,360
And then let's create an extra column...

342
00:26:35,440 --> 00:26:36,400
So what I'm going to do, is I

343
00:26:36,400 --> 00:26:40,879
press C on my keyboard to create an extra column, and i'm going to move this over here to the far left.

344
00:26:41,200 --> 00:26:43,200
The size of it doesn't really matter.

345
00:26:43,520 --> 00:26:45,759
We just need to have a little bit of room in there to work.

346
00:26:46,559 --> 00:26:48,559
And what I will do is,

347
00:26:49,279 --> 00:26:51,839
I'm actually going to get rid of this extra row as well.

348
00:26:52,480 --> 00:26:56,559
Because I don't need, I won't need it ultimately, and if I come in here into this cell,

349
00:26:57,120 --> 00:26:58,400
and if I press

350
00:26:58,400 --> 00:27:00,400
the Custom cell source,

351
00:27:00,559 --> 00:27:02,719
I can now type in "Permanent

352
00:27:05,039 --> 00:27:06,480
Supply"

353
00:27:06,480 --> 00:27:08,480
(If I can spell permanent)...

354
00:27:08,880 --> 00:27:15,599
And then I can span down here to the subtotal "Permanent Supply." So I'll span down there

355
00:27:16,400 --> 00:27:19,139
and then if I come into my actual, um

356
00:27:21,200 --> 00:27:23,200
Custom cell source for this cell

357
00:27:23,360 --> 00:27:28,479
I can get rid of this duplicated word, which is "supply." So I just need "Irrigation Water" in that cell.

358
00:27:29,200 --> 00:27:36,000
And then what we'll see when we refresh this preview is now "Permanent Supply" has actually migrated over

359
00:27:36,720 --> 00:27:42,000
into this row header and into this row header column and then these individual

360
00:27:42,799 --> 00:27:44,799
pieces of data in here

361
00:27:45,120 --> 00:27:51,359
indicating "Purpose" and the "Acreage" and "Feet"... they now have this parent row header. That is more appropriate for them.

362
00:27:51,520 --> 00:27:53,759
So we're sort of taking this table that was

363
00:27:55,120 --> 00:28:00,079
not properly structured for accessibility purposes... we're able to work around these types of problems.

364
00:28:00,640 --> 00:28:04,640
So I'm going to do the same thing here. Where I'm going to get rid of that

365
00:28:05,200 --> 00:28:10,419
extra row... I'm going to change this cell source to Custom and now I can type in "Temporary

366
00:28:12,240 --> 00:28:13,520
Supply."

367
00:28:13,520 --> 00:28:18,079
And then I'll go into the Custom cell source here as well to just get rid of that extra word...

368
00:28:18,559 --> 00:28:20,639
So we don't need that duplicated in both cells.

369
00:28:21,279 --> 00:28:23,279
And then this will give me

370
00:28:24,159 --> 00:28:25,520
the appropriate

371
00:28:25,520 --> 00:28:27,520
row heading.

372
00:28:27,760 --> 00:28:32,319
So you can see I now have "Temporary Supply," which is a row heading for the "Irrigation Water."

373
00:28:32,799 --> 00:28:36,079
And then I can also of course span across my totals...

374
00:28:36,720 --> 00:28:43,839
So what I'll do there is, just since I've created this extra column, I'll just hold down shift, and I'll press S to span

375
00:28:44,720 --> 00:28:46,720
those two columns. So

376
00:28:46,799 --> 00:28:49,439
now my "Total" is actually marked as a row header as well.

377
00:28:49,840 --> 00:28:56,240
So this is a better layout of this table, and it doesn't take very long. It's just you know that extra step.

378
00:28:56,880 --> 00:29:00,159
But what we've done is we've taken a poorly designed table...

379
00:29:00,799 --> 00:29:03,199
It's not our fault that whoever put this document together

380
00:29:03,919 --> 00:29:07,299
wasn't thinking in terms of screen readers and accessibility...

381
00:29:08,240 --> 00:29:14,240
But we have tools up our sleeve with Equidox to work around those types of problems and create a better

382
00:29:14,480 --> 00:29:16,480
table structure for the end user.

383
00:29:17,679 --> 00:29:20,158
Okay, so that's about it for that table there.

384
00:29:21,279 --> 00:29:25,779
And I would repeat that process on this table as well. You can see it's similar sort of layout.

385
00:29:26,480 --> 00:29:32,079
So I'm going to just, uh, to avoid the redundant information. I'll just skip onto something else...

386
00:29:33,279 --> 00:29:36,879
All right. So we've taken a look at some pretty straightforward tables.

387
00:29:36,960 --> 00:29:43,840
But I also want to show you something that might be classified as a more densely, or tighter, or more complicated table.

388
00:29:45,039 --> 00:29:47,119
So let's open up something that looks like this.

389
00:29:48,240 --> 00:29:49,919
And,

390
00:29:49,919 --> 00:29:57,919
again, all of these different text zones as you can see not ideal. How would anyone using a screen reader be able to understand this?

391
00:29:58,960 --> 00:30:05,360
It's just a bunch of nonsense. You know, what does that number, like, pertain to? I have no idea. So to fix this,

392
00:30:06,000 --> 00:30:08,000
again, same process as always...

393
00:30:09,679 --> 00:30:11,759
Drawing a table zone around it pressing T...

394
00:30:13,440 --> 00:30:19,200
Making sure we're not taking in a big bunch of margin with us, opening up the Table Editor...

395
00:30:21,440 --> 00:30:24,000
And let's use our Table Detection tools.

396
00:30:25,279 --> 00:30:28,159
So we can adjust these rows and columns. Got them pretty

397
00:30:29,020 --> 00:30:31,020
nicely spot on.

398
00:30:31,679 --> 00:30:34,319
Not too bad. I'm going to have to get rid of a couple of extra rows...

399
00:30:35,360 --> 00:30:38,959
Just because this is kind of a... Up here you can see our column headers are like...

400
00:30:46,399 --> 00:30:48,659
Quick adjustments I can..

401
00:30:50,799 --> 00:30:53,119
I can get rid of these extra rows by pressing

402
00:30:53,760 --> 00:30:55,659
the D key

403
00:30:55,659 --> 00:30:59,599
And I think that should maybe one extra row here as well.

404
00:31:00,720 --> 00:31:04,799
And then we can take a look at how things are shaking out.

405
00:31:06,240 --> 00:31:13,439
So pretty solid table structure. Um, I would probably recommend running it through that same process before as making this "Costs"

406
00:31:14,080 --> 00:31:17,620
And the "Cumulative depreciation and Impairment Losses."

407
00:31:18,320 --> 00:31:21,439
I would probably move those over as row headers as well.

408
00:31:22,080 --> 00:31:24,080
Just the same process that we just went through.

409
00:31:24,640 --> 00:31:28,159
Or alternatively, you could press shift and then span across

410
00:31:29,279 --> 00:31:31,839
these four columns or these five extra columns...

411
00:31:32,799 --> 00:31:34,959
And that will give you something that looks more like this:

412
00:31:35,600 --> 00:31:38,640
Where you have these marked as row headers.

413
00:31:39,600 --> 00:31:40,880
Not ideal.

414
00:31:40,880 --> 00:31:47,839
But also not necessarily incorrect either. It's just, uh, sort of up to the remediator and the individual table.

415
00:31:48,159 --> 00:31:50,159
This is definitely a faster way of doing it.

416
00:31:50,559 --> 00:31:51,519
So...

417
00:31:51,519 --> 00:31:52,399
You can

418
00:31:52,399 --> 00:31:58,319
kind of go both ways with it, but that's again a more densely spaced more complicated looking table.

419
00:31:58,640 --> 00:32:02,959
You can see how quickly we can get it cleaned up and then I will close out of the Table Editor.

420
00:32:03,679 --> 00:32:06,339
And save the page and just back out entirely.

421
00:32:07,440 --> 00:32:11,440
Now there was one last thing I wanted to show you, and that is of course,

422
00:32:12,159 --> 00:32:14,159
how to turn on

423
00:32:14,480 --> 00:32:17,699
your auto table summary in your profile.

424
00:32:18,320 --> 00:32:23,700
So whenever you log into Equidox, if you just go up to the upper right hand corner and go to your profile...

425
00:32:24,559 --> 00:32:26,559
That will give you a page that looks something like this...

426
00:32:27,360 --> 00:32:34,240
And you'll notice that you have the Zone Highlight with the Auto Summarize mode and the Output Default tab.

427
00:32:35,200 --> 00:32:37,600
So these are three options that you have to change.

428
00:32:38,080 --> 00:32:44,880
So if you just turn to your Auto Summarize mode, and you hit the drop down menu change it from default to enabled...

429
00:32:45,360 --> 00:32:50,240
And that will give you the same setting that I had where it's automatically writing the table summary for you.

430
00:32:50,960 --> 00:32:54,559
Otherwise, it might be hidden or it might be default to disabled. So

431
00:32:55,120 --> 00:33:00,399
if you want to change that you can set it from default to enabled and then just save your profile change.

432
00:33:00,720 --> 00:33:06,640
And then that will give you the same feature that I was showing you earlier where the table summary is auto. populating for you

433
00:33:07,919 --> 00:33:11,999
Um, okay great. So that's about all we have for today.

434
00:33:12,159 --> 00:33:13,919
So I do appreciate uh,

435
00:33:13,919 --> 00:33:20,959
everyone for for watching and viewing. And again if you have any questions regarding Equidox or anything we've covered today

436
00:33:21,519 --> 00:33:26,099
uh, please do not hesitate to reach out to us at EquidoxSales@onixnet.com.

437
00:33:27,200 --> 00:33:29,200
or visit our website at Equidox.co

438
00:33:30,960 --> 00:33:34,960
Or please get in touch with one of your account managers, we would love to hear from you.

439
00:33:35,039 --> 00:33:38,319
We'd love to chat more about some of your specific examples.

440
00:33:38,880 --> 00:33:43,279
We can definitely set up demos and take a look at some of your tables that you're working with.

441
00:33:44,000 --> 00:33:50,079
And help you straighten out your workflow or show you how fast Equidox can can turn those around for you. All right, so great!

442
00:33:50,240 --> 00:33:53,219
So, thank you everyone for joining and have a great rest of your day.