1
00:00:03,840 --> 00:00:09,280
All right so it's just about two o'clock. So 
welcome in everyone. Thank you for attending  

2
00:00:09,280 --> 00:00:15,200
another edition of Equidox Webinar Wednesdays. 
This month we are going to be talking about the  

3
00:00:15,200 --> 00:00:22,320
Truth About Auto-Tagging. So a lot of people that 
we speak to seem to have a pretty heavy reliance  

4
00:00:22,320 --> 00:00:29,440
on Adobe Acrobat's auto-tagging feature. Which 
is not really intended to make documents fully  

5
00:00:29,440 --> 00:00:33,840
accessible. It's really just designed to 
get you started on the path of remediating  

6
00:00:33,840 --> 00:00:38,880
that PDF. So we want to talk a little bit 
about how that works, and its limitations,  

7
00:00:39,760 --> 00:00:45,760
and different ways of going about using Equidox 
to fix the issues that auto-tagging can create.  

8
00:00:46,800 --> 00:00:50,800
So as always I'd just like to mention 
that if you would like to contact us  

9
00:00:51,440 --> 00:00:59,280
feel free to reach out to EquidoxSales@ 
Onixnet.com. Our website is www.Equidox.co.

10
00:01:00,160 --> 00:01:05,280
We're also very active on social media, so if 
you would like to connect with us on LinkedIn  

11
00:01:05,280 --> 00:01:09,920
or Twitter, or Facebook we do post a lot of 
information and articles. So you can always  

12
00:01:09,920 --> 00:01:14,640
stay up to date with what's happening with 
the Equidox team. So with that said let's  

13
00:01:14,640 --> 00:01:21,600
get started. I'm just going to quickly mention a 
couple of things about our parent company. So Onix  

14
00:01:22,240 --> 00:01:27,760
is mainly a cloud consultancy. And we're most 
known for our long-standing partnership with  

15
00:01:27,760 --> 00:01:33,760
Google. And Equidox is a software product that 
is owned and developed by Onix, along with other  

16
00:01:33,760 --> 00:01:39,280
professional services based mainly around PDF 
accessibility, and our mission here with the  

17
00:01:39,280 --> 00:01:44,480
Equidox team is to ensure that digital information 
reaches everyone via accessibility solutions.

18
00:01:46,880 --> 00:01:55,760
So just a quick slide here about some clients of 
ours. We do work with notable names of various  

19
00:01:55,760 --> 00:02:01,040
sizes and across all major verticals whether 
it be education, government, or enterprise.  

20
00:02:01,760 --> 00:02:05,520
So we are here to help you regardless 
of how big or small your company is.  

21
00:02:06,240 --> 00:02:09,040
So please don't feel that you're 
too big or too small to work with  

22
00:02:09,040 --> 00:02:12,000
us. We are here to help you with all 
of your digital accessibility needs.

23
00:02:13,760 --> 00:02:20,000
Okay, so what we're going to be doing today is 
we’ve just put together a very stock sample PDF  

24
00:02:20,000 --> 00:02:27,280
document. This is one quick... (Oh, and I should 
mention before we go any further that there are a  

25
00:02:27,280 --> 00:02:31,440
series of polls that we are going to be asking 
during the webinar, so please feel free to  

26
00:02:31,440 --> 00:02:37,680
answer those. Just if you have a moment just to 
answer the little survey questions that pop up,  

27
00:02:37,680 --> 00:02:40,880
that's greatly appreciated. That will 
help us kind of tailor these webinars  

28
00:02:41,520 --> 00:02:46,400
moving forward, to make sure that we're addressing 
any questions or topics that you would like to see  

29
00:02:46,400 --> 00:02:52,320
us cover.) But what we're going to do today is 
take a look here at this sample PDF document.  

30
00:02:52,960 --> 00:02:58,080
And so this document that we've put together, 
it kind of just contains a bunch of the common  

31
00:02:58,080 --> 00:03:03,520
elements that you would find in any given PDF. 
So you'll see things like text, headings, lists,  

32
00:03:03,520 --> 00:03:10,160
tables, images, OCR, and of course the complicated 
task of setting the reading order for different  

33
00:03:10,160 --> 00:03:15,520
pages. So we'll be kind of working through some 
of these different elements and talking about  

34
00:03:15,520 --> 00:03:21,600
ways that auto-tagging can go wrong, and 
ways of fixing it after the fact in Equidox.

35
00:03:23,760 --> 00:03:29,120
Okay, so the first attempt that we made 
at auto-tagging this simple document here,  

36
00:03:29,120 --> 00:03:35,280
the simple one-page document… For whatever 
reason, Adobe Acrobat decided to tag  

37
00:03:35,280 --> 00:03:41,920
the entire document as one big image. So this 
entire page, despite the fact that it has  

38
00:03:41,920 --> 00:03:48,560
embedded text on it, and is full of all kinds of 
different elements such as of course the text,  

39
00:03:48,560 --> 00:03:52,560
the headings, the list, as I mentioned 
before... Acrobat, for whatever reason,  

40
00:03:52,560 --> 00:03:57,920
just decided that this whole thing is just going 
to be one big image. So there's a lot of problems  

41
00:03:57,920 --> 00:04:03,920
with tagging an entire document like this with 
just something as simple as an image. Because  

42
00:04:03,920 --> 00:04:11,840
the image itself is useless to a screen reader 
user. There need to be tags around the content to  

43
00:04:11,840 --> 00:04:15,920
give something for the screen reader to actually 
interact with and navigate around the page.  

44
00:04:16,640 --> 00:04:22,000
So there is no text-based content for the screen 
reader to read from in this current state. So this  

45
00:04:22,000 --> 00:04:27,840
of course would need to be fixed or changed or at 
the very least another attempt at auto-tagging it.  

46
00:04:29,120 --> 00:04:33,440
So the second try, when we tried to auto-tag 
this again, and this kind of speaks to the  

47
00:04:33,440 --> 00:04:40,240
inconsistency and the lack of reliability that 
you'll get with auto-tagging in Acrobat… So the  

48
00:04:40,240 --> 00:04:45,280
second attempt, we actually were able to 
get some tags created around the content.  

49
00:04:45,920 --> 00:04:49,200
So some of the elements were tagged. 
Some of the elements were missed.  

50
00:04:49,840 --> 00:04:54,240
But in the GIF, if you see on the left-hand 
side here, we're kind of scrolling through  

51
00:04:54,240 --> 00:05:00,480
the tag panel in Acrobat… And you can see that 
it's pretty complicated-looking. It's messy. But  

52
00:05:00,480 --> 00:05:06,160
this is what an auto-generated tag structure 
can look like. So if you're a novice user,  

53
00:05:06,160 --> 00:05:11,440
if you don't know exactly what you're doing here, 
trying to understand the complexities of this tag  

54
00:05:11,440 --> 00:05:15,680
structure on the left-hand side and how this 
relates to making the document accessible...  

55
00:05:17,520 --> 00:05:23,120
This can be a tall task. And especially if 
you're trying to work through dozens of pages,  

56
00:05:23,120 --> 00:05:27,040
dozens of documents, it can be a very 
tedious and time-consuming process.  

57
00:05:28,160 --> 00:05:33,360
So the tags that we're looking at here in 
the GIF are entirely inaccurate and this  

58
00:05:33,360 --> 00:05:38,080
document is really a long way away from being 
accessible and usable to a screen reader user.  

59
00:05:38,960 --> 00:05:43,200
And like I said before, the goal of 
auto-tagging is really just to get you started.  

60
00:05:43,760 --> 00:05:49,280
But it is inconsistent. It is unreliable. And 
it definitely requires human intervention after  

61
00:05:49,280 --> 00:05:53,760
the fact to fix the many elements that 
will be missed or inaccurately tagged.

62
00:05:57,200 --> 00:06:03,760
So the next logical step, assuming that you're a 
novice remediator, you've hit the auto-tag button  

63
00:06:03,760 --> 00:06:09,200
and now you've got some tags… The next logical 
step would be to run the accessibility checker.  

64
00:06:09,760 --> 00:06:16,000
Now it's kind of funny because Acrobat is checking 
its own work. Acrobat applied the auto-tagging,  

65
00:06:16,000 --> 00:06:21,040
and now we're using Acrobat again to check 
the accessibility of those tags. So Acrobat  

66
00:06:21,040 --> 00:06:26,640
here is checking its own work. And even when it's 
applying its own tag structures to this document,  

67
00:06:27,200 --> 00:06:32,960
it's still locating multiple errors in the tag 
structure. Keeping in mind that there are also  

68
00:06:32,960 --> 00:06:38,880
many other errors in this tag structure that the 
accessibility checker is incapable of identifying,  

69
00:06:39,520 --> 00:06:44,640
there are many things that require human 
intervention to identify and locate,  

70
00:06:44,640 --> 00:06:49,760
and of course, go back and correct… So 
if you are an experienced remediator  

71
00:06:50,400 --> 00:06:55,840
you would be able to interact with this tag 
structure and navigate through the tag panel.  

72
00:06:55,840 --> 00:07:00,640
And you would find dozens of issues that 
would need to be corrected. And the only  

73
00:07:00,640 --> 00:07:04,560
way that they can be corrected is through manual 
intervention. You cannot just continue to hit  

74
00:07:04,560 --> 00:07:11,440
the auto-tag button and find ways of fixing 
it. There is no magic solution. You simply  

75
00:07:11,440 --> 00:07:15,840
have to work through the elements one by one and 
correct all of the errors that have been created.

76
00:07:21,760 --> 00:07:30,640
Let's see here… There we go, so one of the first 
errors that we're going to point out here in this  

77
00:07:30,640 --> 00:07:37,760
auto-tag structure is the text error. So if you 
notice at the top of the page, all of that content  

78
00:07:37,760 --> 00:07:44,160
across the two columns where we have two separate 
basic contact information or letterhead for the  

79
00:07:44,160 --> 00:07:49,280
chief information officer and the chief executive 
officer of this fake company that we've invented…  

80
00:07:50,000 --> 00:07:56,400
It's going to group all of that text together 
inside of one tag. And the screen reader would be  

81
00:07:56,400 --> 00:08:02,080
instructed by the tag structure to read directly 
across the two columns which are separating the  

82
00:08:02,080 --> 00:08:07,680
two groups of contact information. So if you were 
a screen reader user, it would be very confusing,  

83
00:08:07,680 --> 00:08:12,800
because you would be hearing both names. You would 
hear Joe Smith and Bob Jones read directly after  

84
00:08:12,800 --> 00:08:17,360
each other. Then both addresses... then both phone 
numbers… so on and so forth, all the way down  

85
00:08:17,360 --> 00:08:22,400
these two separate columns. So it would render 
those two bits of contact information pretty  

86
00:08:22,400 --> 00:08:26,960
much useless to a screen reader user because 
it would not be read in the correct order. And  

87
00:08:26,960 --> 00:08:32,160
this is something that of course Acrobat just did 
automatically. so it needs to be fixed manually.

88
00:08:35,760 --> 00:08:42,880
So another error that we are able to easily 
locate here is a heading error. So within  

89
00:08:42,880 --> 00:08:49,360
logical heading structure, the first heading in a 
document needs to be set as a heading level one…  

90
00:08:50,000 --> 00:08:56,160
And for some reason, Acrobat decided to tag this 
very obvious heading level one... the top portion  

91
00:08:56,160 --> 00:09:02,640
of the page as in as a heading level three. So 
this is objectively incorrect. The first heading  

92
00:09:02,640 --> 00:09:08,720
in a document needs to be a heading level one. 
Adobe knows this, and still, their auto-tagger  

93
00:09:09,280 --> 00:09:14,880
is kind of just you know grasping at straws as 
it's applying tags to these different elements.  

94
00:09:14,880 --> 00:09:21,600
So it assigns arbitrarily an H3 to this element, 
despite the fact that it has to be a heading level  

95
00:09:21,600 --> 00:09:28,720
one according to all accessibility rules. So the 
reason it's setting it as an H3 instead of an H1,  

96
00:09:29,600 --> 00:09:35,120
it's anyone's guess, but it's probably due to 
the font size or the font style that was used.  

97
00:09:35,120 --> 00:09:39,440
But whatever the case may be, it does need to be 
corrected. And it can only be corrected manually.  

98
00:09:41,440 --> 00:09:48,800
Okay, so the next major error that we're 
going to see is another heading error. But  

99
00:09:48,800 --> 00:09:54,560
this is a nesting error. So the second heading 
on this document has been identified as an H2.  

100
00:09:55,280 --> 00:10:00,640
Now you cannot have an H2 directly following 
an H3 so this needs to be fixed as well.

101
00:10:04,160 --> 00:10:10,080
Another problem here is that we have this element 
on the page which is actually a block of text, but  

102
00:10:10,080 --> 00:10:15,120
it is sat inside of an image. So this is something 
that can happen depending on the way that the  

103
00:10:15,120 --> 00:10:21,040
document was designed. So if there is text locked 
inside of an image that is just recognized as an  

104
00:10:21,040 --> 00:10:26,480
image, as far as a screen reader is concerned. So 
OCR is required (Optical character recognition)  

105
00:10:26,480 --> 00:10:32,880
to actually convert that text into something that 
is usable and can be read by a screen reader. Now  

106
00:10:32,880 --> 00:10:39,360
Acrobat is able to locate this figure tag, however 
the content inside of it it needs to be converted  

107
00:10:39,360 --> 00:10:43,360
into something that is actually embedded text, 
that can be read aloud by a screen reader.  

108
00:10:44,080 --> 00:10:50,320
However, using OCR like on this one particular 
page, when we're this far down into the actual  

109
00:10:50,320 --> 00:10:56,000
remediation of it, can be a little bit risky. 
There are strange occurrences of Acrobat trying to  

110
00:10:56,000 --> 00:11:02,880
re-OCR the entire page or block the user from 
continuing to tag the rest of the elements  

111
00:11:02,880 --> 00:11:06,800
underneath it for the rest of the 
document. So this is something that  

112
00:11:06,800 --> 00:11:11,200
is it's kind of a challenge to deal with 
in Acrobat, and it needs to be corrected,  

113
00:11:11,200 --> 00:11:16,560
however. So definitely another little challenging 
issue here with just the plain old auto-tagging.  

114
00:11:18,000 --> 00:11:22,480
Now another obvious area, as we just continue to 
work down the page, every single element you'll  

115
00:11:22,480 --> 00:11:27,040
notice seems to have something wrong with it… 
And this is just the nature of auto-tagging…  

116
00:11:27,040 --> 00:11:32,880
So the next problem is the lists. So lists are 
almost never tagged correctly from auto-tagging.  

117
00:11:33,440 --> 00:11:38,880
And the entire list of these seven different 
items, it's going to be read and grouped together  

118
00:11:38,880 --> 00:11:43,600
as a paragraph. So all seven of those list 
items are just going to be read as a strange  

119
00:11:44,160 --> 00:11:51,120
run-on sentence. And doing this in Acrobat is 
extremely tedious. It requires dozens of steps,  

120
00:11:51,120 --> 00:11:56,320
and even for a small simple list like this, 
there are so many clicks and steps associated  

121
00:11:56,320 --> 00:12:01,200
with tagging it correctly that if you're just 
a novice user and you don't know exactly how to  

122
00:12:01,200 --> 00:12:04,960
navigate the complexities of this 
Acrobat program in the tag panel,  

123
00:12:05,600 --> 00:12:10,800
you can have a very very difficult time just 
trying to tag this one very simple list.

124
00:12:14,000 --> 00:12:19,920
The next thing I want to point out is the table. 
So tables are almost never correctly auto-tagged,  

125
00:12:19,920 --> 00:12:26,320
and they also require manual fixes of course. So 
the table cannot be left in this auto-tag state,  

126
00:12:26,320 --> 00:12:30,320
because the screen reader is just going to be... 
it's going to read straight across the cells  

127
00:12:30,880 --> 00:12:35,840
without any indication of how the user is 
currently oriented in terms of rows and  

128
00:12:35,840 --> 00:12:40,640
columns and like where that screen reader 
is actually focused on. So it renders the  

129
00:12:40,640 --> 00:12:46,640
entire table useless because it simply cannot be 
navigated as a table is intended to be navigated.

130
00:12:48,960 --> 00:12:52,240
So how do we go about fixing 
this? So we've pointed out  

131
00:12:52,240 --> 00:12:57,920
obviously at least half a dozen major flaws with 
the auto-tagging of just this one simple page.  

132
00:12:58,480 --> 00:13:05,040
So what we wanted to show you today is just 
opening up Equidox, our PDF remediation software,  

133
00:13:05,040 --> 00:13:12,240
and we are going to use the different features in 
the platform to fix these types of issues. We're  

134
00:13:12,240 --> 00:13:18,960
going to use things like our Zone Detection tools, 
which is effectively its own type of auto-tagging,  

135
00:13:18,960 --> 00:13:24,080
where we're able to group together and find 
different clusters of content to get the user  

136
00:13:24,080 --> 00:13:29,200
started. But of course, we have a much easier 
interface and a much easier workflow to navigate  

137
00:13:29,200 --> 00:13:35,520
through to actually make these corrections to the 
document itself. So this list of bullet points is  

138
00:13:35,520 --> 00:13:40,240
just a handful of things that we are going to 
do as we go through the Equidox demonstration.

139
00:13:42,640 --> 00:13:47,040
I'm going to back out of the slide deck here, 
and I'm actually going to open up Equidox.  

140
00:13:47,040 --> 00:13:53,200
And I already have the document pre-loaded in 
my Equidox account. So if you take a look here,  

141
00:13:53,840 --> 00:13:59,280
this is what the document looks like when we 
just simply import it into Equidox. so we have  

142
00:14:00,080 --> 00:14:04,880
the tag structure that came from the original 
this is Adobe's auto-tagging. If we remember,  

143
00:14:04,880 --> 00:14:10,960
that issue before of the content being read 
straight across the two separate columns up here…  

144
00:14:11,600 --> 00:14:18,480
We have our heading level three, our heading level 
two, our text zone capturing this entire list,  

145
00:14:18,480 --> 00:14:22,880
this image of text is is going to be 
a problem as well… And then down here,  

146
00:14:22,880 --> 00:14:28,400
we have this table, which is going to be read 
simply as text itself. So before we make any  

147
00:14:28,400 --> 00:14:33,200
changes or alterations to this, if you've 
never seen an Equidox demonstration before,  

148
00:14:33,920 --> 00:14:37,440
if I press this button up here which 
looks a bit like a computer monitor,  

149
00:14:38,160 --> 00:14:43,840
this will actually open a separate tab in my 
browser. As soon as my browser wakes up...  

150
00:14:45,600 --> 00:14:51,600
Interesting... there we go! So it will open a 
separate tab in my browser, and what I can see  

151
00:14:51,600 --> 00:14:58,880
here is an HTML rendering of the page that I'm 
currently working on. So the HTML is, basically,  

152
00:14:59,600 --> 00:15:05,680
what it's doing, is it is showing me exactly how a 
screen reader is going to interact with these tags  

153
00:15:05,680 --> 00:15:12,320
as they currently sit. So if I take a look here, 
if we remember the issue with the text jumping  

154
00:15:12,320 --> 00:15:17,840
across the two columns, a screen reader would read 
that as Joe Smith Bob Jones and then would read  

155
00:15:17,840 --> 00:15:23,120
their titles… It would read their corporations 
back to back, it would read their headquarters,  

156
00:15:23,120 --> 00:15:27,520
and their different addresses in terms of 
the street address, the city, and the state,  

157
00:15:27,520 --> 00:15:32,560
their phone numbers… This is very convoluted 
and confusing and not at all intended how it  

158
00:15:32,560 --> 00:15:37,360
should be read by a screen reader. I'm working 
down the page, you can see other issues here…  

159
00:15:37,360 --> 00:15:42,160
We have our list down here at the very bottom, 
which is going to be just read as a strange  

160
00:15:42,160 --> 00:15:48,800
paragraph with little stars inserted inside of 
it for list labels. And then this is actually  

161
00:15:48,800 --> 00:15:52,720
what our table looks like currently. So 
our table is also just going to be read  

162
00:15:52,720 --> 00:15:57,760
as a strange run-on sentence that will make no 
sense to a screen reader user… not even being  

163
00:15:57,760 --> 00:16:02,960
aware that this is supposed to be a table until we 
tag it as such. So what I'll do is, I'm going to  

164
00:16:02,960 --> 00:16:10,320
come back into the actual Equidox Page Editor, and 
I'm going to make some adjustments to this page.  

165
00:16:10,320 --> 00:16:15,600
the first thing that I want to adjust is the 
page. If I go to the Page Tab, what I'll do is I'm  

166
00:16:15,600 --> 00:16:20,960
going to use the Zone Detector tool. So the Zone 
Detector, what this is designed to do is ignore  

167
00:16:20,960 --> 00:16:26,960
the existing tag structure, so that tag structure 
that Acrobat gave us with the auto-tag feature  

168
00:16:26,960 --> 00:16:31,680
that's not helping us at all... And I don't want 
to try to work with those tags. I don't want to  

169
00:16:31,680 --> 00:16:37,360
have to undo all of the mistakes that it made. 
So we can let Equidox just redefine this page  

170
00:16:37,360 --> 00:16:42,880
by using this Zone Detection slider. So if I move 
this slider back and forth, left to right, you'll  

171
00:16:42,880 --> 00:16:47,760
instantly see how we've cleaned things up pretty 
significantly. We've gotten rid of all of those  

172
00:16:47,760 --> 00:16:52,480
extra tags that were just really kind of getting 
in the way. And now we're left with a much cleaner  

173
00:16:52,480 --> 00:16:59,680
starting point that doesn't require as many manual 
adjustments. So if I were to go into the HTML  

174
00:16:59,680 --> 00:17:05,040
Preview again, already I've made some improvements 
simply by the fact that I've grouped together Joe  

175
00:17:05,040 --> 00:17:08,960
Smith and Bob Jones's contact information. 
At least now it's going to be read properly.  

176
00:17:09,760 --> 00:17:14,240
So I do have to make some additional adjustments, 
of course. We have things like images, we have  

177
00:17:14,240 --> 00:17:18,640
heading structure, we have to apply break lines 
to these addresses, we have the list, and the  

178
00:17:18,640 --> 00:17:24,160
table and we also have the OCR. So let's just 
start working through the page, top to bottom.  

179
00:17:25,040 --> 00:17:29,120
Up here in the top margin, we have just the 
version number of this document. Things like  

180
00:17:29,120 --> 00:17:34,160
this can often be artifacted because they're 
not necessarily adding much value to the tag  

181
00:17:34,160 --> 00:17:38,160
structure. So I can start by just hitting 
backspace to get rid of that extra zone.  

182
00:17:38,720 --> 00:17:43,360
I have this image here, which I'll just begin 
with because it's the next tallest zone. But  

183
00:17:43,360 --> 00:17:47,360
what I like...what I can do is actually apply 
an alt description to it. So I can type in  

184
00:17:47,360 --> 00:17:56,640
“letterhead mark maker sample company logo.” So 
I'm able to apply an alt text to that image so  

185
00:17:56,640 --> 00:18:01,760
that it will actually have some context for the 
screen reader user as to what this image is. The  

186
00:18:01,760 --> 00:18:07,680
contact information for Joe Smith and Bob Jones... 
What I want this to do is, I want to apply a small  

187
00:18:07,680 --> 00:18:12,800
pause at the end of each one of these lines so 
that their contact information will be read in a  

188
00:18:12,800 --> 00:18:17,280
bit smoother of a flow for the end-user, rather 
than having it all just be treated as one big  

189
00:18:17,280 --> 00:18:23,280
sentence. So if I apply the break lines checkbox 
to these two different elements, that is going to  

190
00:18:23,280 --> 00:18:28,800
improve the end-user’s experience as they read 
through this page. The next thing I'm going to  

191
00:18:28,800 --> 00:18:34,240
do is focus on my heading structure. So if I click 
on this item here, where it says “Memorandum,” if  

192
00:18:34,240 --> 00:18:40,960
we remember from the auto-tagging, this was set as 
an H3. This is our first heading on the page so we  

193
00:18:40,960 --> 00:18:46,880
really don't want this to be set as an H3. We want 
this to be set as an H1 because it is of course  

194
00:18:47,440 --> 00:18:52,080
a rule for our logical heading structure that 
all documents have to have a heading level one.  

195
00:18:52,080 --> 00:18:56,160
And that heading level one should be the first 
heading on the page. So all I have to do to set  

196
00:18:56,160 --> 00:19:01,360
this as a heading level one is simply tap “1” on 
my keyboard. Now I've made some adjustments to  

197
00:19:01,360 --> 00:19:05,760
the page so far, and just so that we don't get 
too far ahead of ourselves if I press the HTML  

198
00:19:05,760 --> 00:19:10,000
Preview again... I mean this is not something 
that's required... you don't have to press the  

199
00:19:10,000 --> 00:19:14,960
HTML Preview every time you make a change... It's 
just simply something to show you kind of how  

200
00:19:14,960 --> 00:19:19,200
things are evolving here in terms of how a screen 
reader is going to interact with this document  

201
00:19:19,760 --> 00:19:25,680
as we go. So if you can tell, now our actual 
contact information for the Joe Smith and Bob  

202
00:19:25,680 --> 00:19:29,360
Jones... they've actually been treated a little 
bit differently. Where each one of those lines  

203
00:19:29,360 --> 00:19:33,600
of text is going to be read with a slight pause 
at the end of it, just making it a bit easier  

204
00:19:33,600 --> 00:19:41,520
to understand. For example, where the phone number 
starts versus where the actual area code ends. The  

205
00:19:41,520 --> 00:19:47,520
memorandum is now a much larger font because I've 
set this as an H1. So you can see that change  

206
00:19:47,520 --> 00:19:52,640
reflected here in your HTML Preview, and then 
everything else below we have not yet impacted.  

207
00:19:52,640 --> 00:19:56,720
So we still need to make some changes down here. 
But you can kind of see how things are changing as  

208
00:19:56,720 --> 00:20:04,480
we go. So if I come back into the main page here, 
I want to capture this “What is Lorem Ipsum” as an  

209
00:20:04,480 --> 00:20:09,680
H2. So zones can be easily adjusted. If I 
just resize that zone and drag it up, I can  

210
00:20:09,680 --> 00:20:15,600
then grab a new zone, or grab this content by just 
clicking and dragging to capture that text again.  

211
00:20:15,600 --> 00:20:19,840
And then if I just simply hit “2” on my keyboard, 
that will identify that as a heading level two.  

212
00:20:21,440 --> 00:20:26,480
Down below here, here's that bit of OCR. So as 
you can see, right now it's sat inside of an  

213
00:20:26,480 --> 00:20:31,120
image zone. So what I can do is just get rid of 
that image zone by just hitting backspace on my  

214
00:20:31,120 --> 00:20:37,360
keyboard. And if I just draw a new zone on top of 
that text, it's now a text zone. But I can change  

215
00:20:37,360 --> 00:20:42,880
the zone source to OCR. OCR, of course, standing 
for optical character recognition. If I hit the  

216
00:20:42,880 --> 00:20:48,240
“Convert to Text” button here, this is going 
to process this basically a screenshot of this  

217
00:20:48,240 --> 00:20:53,040
area of the page, and it is actually going to turn 
it into something here in this little text field  

218
00:20:53,040 --> 00:20:58,080
where you have real encoded text that 
can be actually read by a screen reader.  

219
00:20:58,080 --> 00:21:03,120
The alternative to that would be literally typing 
out every single word of this in the form of an  

220
00:21:03,120 --> 00:21:07,760
alt text for that image. That's going to take 
you a lot longer than simply just pressing the  

221
00:21:07,760 --> 00:21:12,960
“Convert to Text” button in Equidox. Over 
here we have another heading level two,  

222
00:21:12,960 --> 00:21:18,400
so I'm just going to tap “2” on my keyboard. And 
this is identifying where this list is located, so  

223
00:21:18,400 --> 00:21:22,560
this list of course needs to be addressed right 
now. Again it's just sat there as a text zone,  

224
00:21:22,560 --> 00:21:26,240
so it's going to read this as just one big 
run-on sentence, which is going to be strange  

225
00:21:26,880 --> 00:21:31,680
and not make much sense to an end-user. So what 
we can do to fix this if I just hit “L” on my  

226
00:21:31,680 --> 00:21:37,360
keyboard that will change the zone to a list, and 
then I can use the List Detection Slider. If I use  

227
00:21:37,360 --> 00:21:42,400
the List Detection Slider, Equidox is able to 
automatically identify where those list items  

228
00:21:42,400 --> 00:21:48,640
are located. And it is basically doing all of the 
heavy lifting for me. So it's going to change what  

229
00:21:48,640 --> 00:21:54,640
was something that is simply a text zone, it's now 
going to tag this as a list, and when I export the  

230
00:21:54,640 --> 00:21:59,280
document, Equidox goes through the steps of 
building out the complicated tag structure  

231
00:21:59,280 --> 00:22:04,160
that is required for this list. So that I don't 
have to do that manually. If you remember before,  

232
00:22:04,160 --> 00:22:08,800
I was talking about how a simple little list like 
this has only, I don't know, eight items in it,  

233
00:22:08,800 --> 00:22:13,840
there are so many steps required to properly 
tag this. It's very manual, it's very technical,  

234
00:22:14,480 --> 00:22:19,600
and you have to really have a lot of patience and 
just a deep understanding of what you're doing to  

235
00:22:19,600 --> 00:22:23,840
be able to efficiently work through lists like 
this. So with Equidox, it's simply a matter of  

236
00:22:23,840 --> 00:22:28,400
identifying that this zone is a list, and moving 
the slider from left to right, and you're done.  

237
00:22:29,440 --> 00:22:33,120
The next thing we want to worry about 
here is the table. So as you can see,  

238
00:22:33,120 --> 00:22:38,560
after I've used that Zone Detector the table is 
still not identified as a table. It's just kind of  

239
00:22:38,560 --> 00:22:44,000
grouping the individual columns and rows together 
in their own individual text zones. So I can fix  

240
00:22:44,000 --> 00:22:49,360
this by simply ignoring all of those zones and 
just drawing a single zone over the entire table.  

241
00:22:49,360 --> 00:22:54,720
And if I hit “T” on my keyboard, that will change 
the zone type to Table. And I can now open up the  

242
00:22:54,720 --> 00:23:01,120
Table Editor. So the Table Editor is going to 
isolate the table for me. And if you notice,  

243
00:23:01,120 --> 00:23:05,520
the great green grid lines here, they're kind of 
identifying where the rows are. It's trying to  

244
00:23:05,520 --> 00:23:10,080
figure out the basic structure of this table. 
So this is the initial guess that Equidox has  

245
00:23:10,080 --> 00:23:14,960
given me. And it did an okay job. I can always 
make manual adjustments to this if I'd like to,  

246
00:23:14,960 --> 00:23:21,520
but I prefer to use the Table Detector. 
So using our artificial intelligence,  

247
00:23:21,520 --> 00:23:26,640
a combination of machine learning and computer 
vision, if I move these sliders around,  

248
00:23:26,640 --> 00:23:31,520
Equidox is going to trigger that AI to 
automatically identify the layout of this table.  

249
00:23:32,320 --> 00:23:37,520
Now this table has only column headers and no row 
headers, so what I'm going to do is change my row  

250
00:23:37,520 --> 00:23:43,760
header from the default one (we have a default one 
to one ratio, meaning that you have your top row  

251
00:23:43,760 --> 00:23:48,160
will be your column headers and the farthest left 
column will be your row headers). In this case,  

252
00:23:48,160 --> 00:23:52,240
I'm going to change this, instead of these being 
row headers, I'm going to just change them to  

253
00:23:52,240 --> 00:23:57,760
table data. So if I just change my one to zero, 
that will update my table summary automatically,  

254
00:23:57,760 --> 00:24:02,080
which is another thing that Equidox can automate 
for you. Automatically putting together your  

255
00:24:02,080 --> 00:24:08,080
table summaries based on how you have structured 
your table. And the green grid lines to locate  

256
00:24:08,080 --> 00:24:13,280
the different cells. So after doing that, if I 
take a look at this preview of just the table,  

257
00:24:13,920 --> 00:24:19,520
we'll see that before I had a very strange sort of 
like series of paragraphs like in run-on sentences  

258
00:24:19,520 --> 00:24:23,840
trying to read through this table. But I've 
actually very quickly just converted it into  

259
00:24:23,840 --> 00:24:28,720
a nice clean table. And again the beauty 
of Equidox is that it will take this table  

260
00:24:28,720 --> 00:24:33,760
that I've built here, and I can see in my HTML 
Preview, and it is automatically going to build  

261
00:24:33,760 --> 00:24:42,400
the table tag structure for me when I export the 
document as a PDF. So if I save this table now and  

262
00:24:42,400 --> 00:24:47,840
close out, I will return back to the Page Editor. 
And all of those zones that were underneath  

263
00:24:47,840 --> 00:24:52,000
the individual text zones, that were underneath, 
they have been overwritten. I'm just now left  

264
00:24:52,000 --> 00:24:58,160
with one single table zone. Now if I take a 
look at the HTML Preview for the full page,  

265
00:24:58,160 --> 00:25:04,240
what I'll see is things are looking a lot better. 
But I do have some reading order issues. If you  

266
00:25:04,240 --> 00:25:10,160
remember, I created this zone manually. This was 
the OCR zone. And when I created it manually,  

267
00:25:10,160 --> 00:25:14,960
it took over the lowest available number in 
the reading zone. So it jumped up to number one  

268
00:25:14,960 --> 00:25:19,520
because I deleted the zone that was capturing this 
little thing up here in the header telling me what  

269
00:25:19,520 --> 00:25:25,200
version of this document this is. So to fix the 
reading order, it's really straightforward. I can  

270
00:25:25,200 --> 00:25:30,400
simply go to the Page Tab and press the “Reorder” 
button. And that is going to reorder things in a  

271
00:25:30,400 --> 00:25:35,280
top-to-bottom, left-to-right sequence. So the 
first thing that will be read is my image here  

272
00:25:35,280 --> 00:25:40,800
because this is the tallest zone… Then I have the 
Joe Smith and the Bob Jones contact information,  

273
00:25:40,800 --> 00:25:46,320
my heading 1, and working down the page just as 
a top-to-bottom natural layout. If I go back to  

274
00:25:46,320 --> 00:25:50,320
the HTML Preview, this will be a little bit 
more reflective of what I would like to see.  

275
00:25:50,320 --> 00:25:55,040
Where I have down here... I've got my list and 
my tables, everything kind of in the order that I  

276
00:25:55,040 --> 00:26:00,720
would expect to see it. And one other little thing 
that you might choose to adjust... best practice  

277
00:26:00,720 --> 00:26:05,440
would call to have your heading level 1 be the 
first thing read on the page whenever possible.  

278
00:26:05,440 --> 00:26:09,840
So in this case, just to show you another 
way to impact the reading order… This is  

279
00:26:09,840 --> 00:26:14,960
currently reading zone four. So if I wanted 
to make this the first zone read on the page,  

280
00:26:14,960 --> 00:26:19,520
you might think that I would then need to 
make turn one into two, and two into three,  

281
00:26:19,520 --> 00:26:23,920
and three into four… Just so that I can make room 
for this. But we can actually use the decimal  

282
00:26:23,920 --> 00:26:28,560
system. So if I just put a period over here in 
the little order field... if I put a period in  

283
00:26:28,560 --> 00:26:32,880
front of the 4 that will make that zone 0.4. 
And that is going to reorder it and put it at  

284
00:26:32,880 --> 00:26:37,760
the very top of the reading order because 0.4 is 
of course less than 1. So I don't have to have a  

285
00:26:37,760 --> 00:26:42,560
perfect sequence of numbers. I'm able to impact 
the reading order of this page very quickly.  

286
00:26:42,560 --> 00:26:48,240
And now if I take a look at just the full sort 
of final HTML version of this document, I'm very  

287
00:26:48,240 --> 00:26:53,600
satisfied with what I see. Everything here is 
basically exactly what I would expect and how I  

288
00:26:53,600 --> 00:26:58,720
would anticipate a screen reader should be reading 
through this page. So I'm done with this document,  

289
00:26:58,720 --> 00:27:05,120
and I can save it and I can close out at any time. 
And once I'm done closing out, I could of course  

290
00:27:05,120 --> 00:27:10,800
export the document as a PDF simply by going 
to the Output Tab and hitting “Generate PDF.”  

291
00:27:12,000 --> 00:27:15,840
Now in the interest of time let's jump 
back into the slide presentation here.

292
00:27:19,920 --> 00:27:23,920
So we've covered the Equidox demonstration, 
and again if there's anything else that you'd  

293
00:27:23,920 --> 00:27:30,560
like to see... if you'd like to have a more like 
one-on-one type of demonstration where we take a  

294
00:27:30,560 --> 00:27:35,440
look at your own documents, your organization's 
documents, or talk about the existing workflows  

295
00:27:35,440 --> 00:27:39,760
that you have, please feel free to reach out to 
us through our contact information which I'll  

296
00:27:39,760 --> 00:27:45,040
definitely put up again on the screen. But it's 
definitely something that we would love to chat  

297
00:27:45,600 --> 00:27:49,600
with different organizations about. We'd love to 
know how you're using PDFs, how you're currently  

298
00:27:49,600 --> 00:27:53,760
remediating, or if you're not remediating at 
all. And if you'd like to incorporate a tool  

299
00:27:53,760 --> 00:28:01,200
like Equidox into your workflow. So just in 
full disclosure, we are, of course, just to  

300
00:28:01,200 --> 00:28:06,880
keep things kind of simplified, we are of course 
just using screenshots. But this is a screenshot  

301
00:28:06,880 --> 00:28:14,160
of the accessibility report after we have 
remediated that document. So just to be honest,  

302
00:28:14,160 --> 00:28:19,200
we're not actually opening up Adobe here on the 
slide presentation. We just took a screenshot of  

303
00:28:19,200 --> 00:28:23,920
another version of this one that we did prior to 
the demonstration today. But if you take a look  

304
00:28:23,920 --> 00:28:29,360
here at the Tag Panel, now on the left-hand side.. 
This is after running the accessibility checker,  

305
00:28:29,360 --> 00:28:34,720
and there are only two issues located. But keep 
in mind that these issues will be present in every  

306
00:28:34,720 --> 00:28:41,360
document that you ever remediate and ever attempt 
to validate in Acrobat because Acrobat is not  

307
00:28:41,360 --> 00:28:47,200
capable of checking for the logical reading order 
or the color contrast of the document. So these  

308
00:28:47,200 --> 00:28:52,800
are really just sort of warnings or reminders 
that those types of elements need manual checks.  

309
00:28:52,800 --> 00:28:56,160
But we have already kind of handled that, 
especially from the reading order standpoint,  

310
00:28:56,800 --> 00:29:01,920
by working through the document in Equidox and 
checking things with our HTML Preview. For the  

311
00:29:01,920 --> 00:29:06,640
color contrast, you can always use a third-party 
color contrast-specific checking tool.  

312
00:29:07,440 --> 00:29:11,120
But these are things that are always going to 
be present. But if you can tell now you have  

313
00:29:11,120 --> 00:29:16,480
a very clean-looking accessibility report 
and this document is now perfectly usable,  

314
00:29:16,480 --> 00:29:20,160
perfectly accessible, and ready 
to be posted or distributed to  

315
00:29:21,680 --> 00:29:29,120
your website, or any of your clients, or wherever 
it may be off to. So the just a quick reminder,  

316
00:29:29,120 --> 00:29:33,440
a couple of the things that we covered in the 
Equidox demonstration. We went through a couple  

317
00:29:33,440 --> 00:29:39,440
of our Smart Detection Tools. One click to set 
our heading levels, we were able to very quickly  

318
00:29:39,440 --> 00:29:43,840
adjust our reading order, so there's a number 
of things that we'd love to chat with you  

319
00:29:43,840 --> 00:29:47,920
more on a one-on-one basis. If you'd like to 
have your own personal demonstration of Equidox,  

320
00:29:47,920 --> 00:29:51,680
again please get in touch with us. And you 
can get in touch with us by reaching out to  

321
00:29:51,680 --> 00:29:59,200
EquidoxSales@Onixnet.com. Check out our website 
Equidox.co and of course, we are always active  

322
00:29:59,920 --> 00:30:06,400
on social media. So please feel free to connect 
with us there. So it is 2:30 on the dot. So I  

323
00:30:06,400 --> 00:30:10,320
want to be respectful of everyone's time. I 
really appreciate everyone attending today,  

324
00:30:10,320 --> 00:30:21,840
and come visit us again next month for our 
next edition of Equidox Webinar Wednesdays.