1
00:00:00,800 --> 00:00:02,960
Equidox by Onix 

2
00:00:03,840 --> 00:00:08,560
Reach everyone.

3
00:00:08,560 --> 00:00:14,880
[Dan Tuleta]  All right, well welcome everyone to another edition of Equidox Webinar Wednesdays. It's  

4
00:00:14,880 --> 00:00:17,120
just about two o'clock, so I 
think we should get started.  

5
00:00:18,240 --> 00:00:22,880
Now for anyone that has joined us before, we 
really appreciate you continuing to attend  

6
00:00:22,880 --> 00:00:30,320
these webinars to learn a bit more about document 
remediation and Equidox. So today's presentation  

7
00:00:30,320 --> 00:00:36,400
is going to be talking about refining and 
designing a workflow for attacking these documents  

8
00:00:36,400 --> 00:00:42,800
from a remediation standpoint. So as always please 
feel free to reach out to us at any given time  

9
00:00:42,800 --> 00:00:53,920
through EquidoxSales@onixnet.com. Our website is 
www.Equidox.co and our 800 number is 800-664-9638.  

10
00:00:54,640 --> 00:01:01,040
So we do encourage follow-up questions or feedback 
for these webinars and if you'd like to see any  

11
00:01:01,040 --> 00:01:07,680
personalized demonstrations of Equidox, maybe more 
tailored to your specific workflow, please feel  

12
00:01:07,680 --> 00:01:14,400
free to reach out to us. We would love to start 
a conversation with you. Now before we get into  

13
00:01:15,040 --> 00:01:19,600
the Equidox specifics, I just wanted to mention 
a couple of quick things about our parent company  

14
00:01:19,600 --> 00:01:26,160
Onix Networking. Onix Networking is primarily a 
Google cloud consultancy and an AWS consultancy  

15
00:01:26,160 --> 00:01:32,000
as well. Our mission is to improve organizational 
efficiency through cloud computing solutions. We  

16
00:01:32,000 --> 00:01:39,040
are headquartered in Cleveland, Ohio with offices 
in Canada as well, and we do have quite a few  

17
00:01:39,040 --> 00:01:46,400
remote employees scattered across North America. 
We've been in business since 1992, so quite a long  

18
00:01:46,400 --> 00:01:52,880
time in the IT space, and one of the one of the 
actual divisions of Onix is of course Equidox,  

19
00:01:53,520 --> 00:01:59,120
where we focus mainly on digital accessibility with a niche in PDF documents. So, we're going  

20
00:01:59,120 --> 00:02:05,200
to be talking a bit about our Equidox software 
which is designed for PDF remediation. And we'll  

21
00:02:05,200 --> 00:02:12,320
be going through a couple of ways of looking at 
various workflows for approaching PDF documents  

22
00:02:12,320 --> 00:02:17,680
in the most efficient ways to remediate them. 
And I’ll actually be going through a few examples  

23
00:02:17,680 --> 00:02:24,160
in the Equidox software. So for anyone that has 
seen a demonstration or maybe is an existing user  

24
00:02:24,160 --> 00:02:30,000
of Equidox, some of this might be a little 
bit of a review, from perhaps a recent demo  

25
00:02:30,000 --> 00:02:33,840
or training session we might have had. But for 
those of you who have not seen Equidox before,  

26
00:02:33,840 --> 00:02:40,000
you'll get to get a little bit of a feel for what 
PDF remediation can look like in our tool. Now  

27
00:02:41,280 --> 00:02:49,040
just a quick little blurb about who we serve... some 
of some of our clients: Carnival, Bose, PNC,  

28
00:02:49,040 --> 00:02:56,240
Pella, NYU. We serve a number of clients across 
all different verticals from large to small.  

29
00:02:56,960 --> 00:03:02,080
So we do appreciate everyone joining us today 
regardless of the size of the organization or  

30
00:03:02,640 --> 00:03:06,640
which type of market you are actually in. 
So thank you very much for attending today. 

31
00:03:08,080 --> 00:03:15,120
Now in terms of document remediation, if you 
are assigned with remediating documents… if  

32
00:03:15,120 --> 00:03:19,920
this is your everyday job… or if this 
is just a one-off project, maybe that  

33
00:03:19,920 --> 00:03:25,600
that you've been asked to complete as a 
content creator, there's a few things to  

34
00:03:25,600 --> 00:03:31,840
consider in the pre-flight process. So before 
you get started with remediating a document,  

35
00:03:32,640 --> 00:03:37,920
one of the first things that I like to look at is 
how many pages are there, If there are just one  

36
00:03:37,920 --> 00:03:43,760
or a couple of pages in this document, you know, 
then then you can kind of just power through it  

37
00:03:45,120 --> 00:03:49,600
and just kind of approach it by just opening the 
document up and taking a look at what you have  

38
00:03:49,600 --> 00:03:55,040
and start working on it. Now if there are a lot 
of pages in this document, typically I like to  

39
00:03:56,320 --> 00:04:01,280
take a few minutes to just investigate what 
the document is compiled of. Because you might  

40
00:04:01,280 --> 00:04:07,040
choose to be a little bit more strategic and 
tactical in how you approach that document.  

41
00:04:07,040 --> 00:04:12,240
Because there could be a number of things that 
you could consolidate… steps along the way  

42
00:04:12,240 --> 00:04:17,440
that will eliminate redundancies and, you know, 
forcing you to repeat steps page after page.  

43
00:04:18,080 --> 00:04:22,000
So we'll take a look at a few of those 
things later on during the demonstration.  

44
00:04:22,960 --> 00:04:29,360
Now another thing to consider is how complex is 
the content? Now a document might have a lot of  

45
00:04:29,360 --> 00:04:36,800
pages, but if you consider a document maybe that's 
just all text, for example, where you just have a  

46
00:04:36,800 --> 00:04:42,080
series of paragraphs page after page after page… 
The great thing about Equidox is its ability  

47
00:04:42,080 --> 00:04:47,040
to auto-detect that type of content. And it's 
going to do a lot of the heavy lifting for you.  

48
00:04:47,840 --> 00:04:52,960
So the complexity of the content does have a 
lot to do with your workflow as you remediate.  

49
00:04:53,520 --> 00:05:00,880
Now a 100-page document made up entirely of text 
elements could be easier than a 10-page document  

50
00:05:01,440 --> 00:05:07,120
although it's much longer. A 10-page document 
might have very technical engineering drawings, or  

51
00:05:08,000 --> 00:05:15,600
very complex elements that take more actual work
to tag properly. So something to look at is the  

52
00:05:15,600 --> 00:05:20,400
complexity of the content. To kind of build out 
the workflow in your head before you get started.  

53
00:05:21,280 --> 00:05:26,080
Another thing that I look at is, is the design 
and the formatting of the document consistent  

54
00:05:26,080 --> 00:05:33,040
throughout? So is this document coming from 
a template? Is there a consistent use of  

55
00:05:33,040 --> 00:05:38,160
heading structure throughout? Are the lists 
properly formatted throughout the document?  

56
00:05:38,160 --> 00:05:43,440
How consistent is this page after page? 
Sometimes I see documents which are almost  

57
00:05:43,440 --> 00:05:50,960
like a Frankenstein document. Where it's a series 
of pages that have come together from various  

58
00:05:50,960 --> 00:05:56,480
locations. There's nothing consistent about them. 
Every page is unique, and every page has to be  

59
00:05:56,480 --> 00:06:03,360
treated like as its own individual puzzle. So 
it's just important to note if there's consistent  

60
00:06:03,360 --> 00:06:09,600
formatting throughout the document. There are 
ways within Equidox to consolidate steps and to  

61
00:06:09,600 --> 00:06:14,320
eliminate some redundancies so that you don't have 
to repeat the same exact steps page after page.  

62
00:06:15,920 --> 00:06:21,520
Now another thing that I look at always, is if 
there is existing tag structure associated with  

63
00:06:21,520 --> 00:06:28,160
the document. And existing tag structure could 
be good or bad. Now many documents, depending  

64
00:06:28,160 --> 00:06:34,000
on where they come from… for example, Microsoft 
Word being a very common one, when you hit “Save  

65
00:06:34,000 --> 00:06:40,080
as PDF” coming out of Microsoft Word oftentimes 
there is an automated tagging process where  

66
00:06:40,080 --> 00:06:48,560
Microsoft Word will attempt to convert that word 
file into a PDF and generate some automated tags  

67
00:06:48,560 --> 00:06:54,400
throughout that process. Now that can be good 
or bad, depending on the way that the document  

68
00:06:54,400 --> 00:06:59,280
was put together. But the point is that you don't 
really know what you're going to get during that  

69
00:07:00,720 --> 00:07:07,360
conversion process from Microsoft Word into PDF. 
Because how those how those tags are generated  

70
00:07:08,080 --> 00:07:12,960
is basically a mystery to the user. You just 
have to kind of wait and see what you get. There  

71
00:07:12,960 --> 00:07:17,040
are of course many things that you can take into 
consideration when you're designing your documents  

72
00:07:17,920 --> 00:07:22,400
to improve the accessibility of them 
when you do convert them into a PDF.  

73
00:07:23,040 --> 00:07:28,160
But they still need to be looked at 
because PDF and Word are different formats  

74
00:07:28,160 --> 00:07:32,560
and they just have different ways of marking 
up documents from an accessibility standpoint.  

75
00:07:33,120 --> 00:07:36,960
So just because your Microsoft Word 
document is technically accessible,  

76
00:07:36,960 --> 00:07:41,280
it does not mean that the PDF that that generates 
is going to be automatically accessible. So  

77
00:07:41,280 --> 00:07:46,800
you still need to take into consideration 
that the existing tags that were generated  

78
00:07:46,800 --> 00:07:52,160
automatically through Microsoft Word, they 
might still need to be touched up or adjusted.  

79
00:07:53,280 --> 00:07:59,840
Now there are other documents that a that may 
have been remediated at some point in their  

80
00:08:00,400 --> 00:08:06,800
life cycle where someone might have opened the 
document in Adobe Acrobat and pressed auto tag  

81
00:08:07,600 --> 00:08:11,840
and just kind of crossed their fingers and hoped 
that they got some sort of usable tag structure.  

82
00:08:13,040 --> 00:08:19,280
This can be something that is going to cause you more problems than be of service. So these are  

83
00:08:19,280 --> 00:08:24,160
just things to look at. If you have existing
tag structure. What is the quality of those  

84
00:08:24,160 --> 00:08:30,240
existing tags, and are they worth maintaining, 
or is it better to just use Equidox and start  

85
00:08:30,240 --> 00:08:36,160
from scratch? Because of the automation and all of 
the tools that Equidox gives you to tag documents,  

86
00:08:36,960 --> 00:08:39,840
there are many instances where it 
can be easier to just start over  

87
00:08:41,120 --> 00:08:50,000
rather than trying to rescue poor existing tags. 
Another feature that or another aspect that I  

88
00:08:50,000 --> 00:08:55,520
like to look at is does the document require OCR? 
And OCR stands for Optical Character Recognition.  

89
00:08:57,040 --> 00:09:00,000
This can be relevant for documents 
that are scanned, for example,  

90
00:09:01,040 --> 00:09:06,400
or documents that might contain infographics 
that have text that is actually locked inside  

91
00:09:06,400 --> 00:09:13,760
of images. Now OCR certainly adds another 
layer of complexity to remediation because  

92
00:09:13,760 --> 00:09:17,760
in order to make these documents compatible 
with screen readers and machine-readable,  

93
00:09:18,560 --> 00:09:24,400
an image is simply an image. We need to extract 
text from it if there is in fact text inside of  

94
00:09:24,400 --> 00:09:29,920
it. So if you have a document where someone took 
an old newspaper and ran it through a scanner,  

95
00:09:30,480 --> 00:09:36,240
technically that document can come out of that 
scanner as a PDF. But it is simply just an image  

96
00:09:36,240 --> 00:09:42,160
as far as a machine reader is concerned. So 
that this requires an extra step called Optical  

97
00:09:42,160 --> 00:09:48,720
Character Recognition, where you're actually 
analyzing the image and extracting the usable  

98
00:09:48,720 --> 00:09:54,880
searchable, selectable text from it. So you have 
to run this OCR process to extract that text,  

99
00:09:54,880 --> 00:10:00,640
which can take it can take a little bit of extra 
time, but this is just sort of the nature of the  

100
00:10:00,640 --> 00:10:06,160
of the format. If you're dealing with scanned 
images then you have to take the time to make sure  

101
00:10:06,160 --> 00:10:11,600
that you are extracting the content from it in 
order to make it machine readable. Another thing  

102
00:10:11,600 --> 00:10:17,120
to consider is are there form fields present? 
So documents PDF documents that are intended  

103
00:10:17,120 --> 00:10:23,120
to be fillable forms oftentimes will have form 
fields present within them. And this is another  

104
00:10:23,680 --> 00:10:30,080
element that does take a little bit of extra care 
because form fields need to have what are called  

105
00:10:30,080 --> 00:10:34,240
Tooltips applied to them. So if you find that 
there are form fields in the document, that's  

106
00:10:34,240 --> 00:10:38,720
another thing to be aware of and another thing 
to sort of budget your time and your workflow  

107
00:10:38,720 --> 00:10:44,160
around… making sure that you that you take 
the time to properly handle those form fields.  

108
00:10:45,360 --> 00:10:50,880
And then one of the last things that I like to 
look at are the images. So if there are images  

109
00:10:50,880 --> 00:10:55,280
present in the document, which many times there 
will be, how many images are there? About how  

110
00:10:55,280 --> 00:11:02,160
many images per page are there? I mean, are these 
images informative are they technical or are they  

111
00:11:02,160 --> 00:11:07,200
something that are just decorative? Now decorative 
images could be things like repetitive logos…  

112
00:11:07,920 --> 00:11:17,200
they could be like watermark… or background 
images… they could be stock images. So some sort  

113
00:11:17,200 --> 00:11:23,440
of brochure where you just have two people bending 
over a computer smiling at the computer screen…  

114
00:11:24,240 --> 00:11:29,520
These are sorts of like stock images that are not 
actually adding any content a contextual value  

115
00:11:30,240 --> 00:11:34,960
to the document itself. They're simply there 
for the aesthetics and to take up some space  

116
00:11:34,960 --> 00:11:42,080
and maybe balance out the page. So not all images 
require alt text, but that's up to the remediator  

117
00:11:42,080 --> 00:11:47,600
to determine… If there are images, what kind 
of alt text and what kind of effort do you  

118
00:11:47,600 --> 00:11:53,920
have to make to apply that alt text? Perhaps the 
image… the document is full of technical images.  

119
00:11:53,920 --> 00:11:59,440
Maybe this is like engineering content where 
you have a bunch of complex diagrams and graphs  

120
00:11:59,440 --> 00:12:03,600
and charts. If you're just the remediator 
and you're not the subject matter expert,  

121
00:12:03,600 --> 00:12:08,080
you might need to incorporate someone who 
knows more about that subject than you  

122
00:12:08,080 --> 00:12:13,280
to help you with the alt text writing. So 
these are just things to consider as you  

123
00:12:13,280 --> 00:12:18,000
are going through your remediation and as you're 
developing your workflow throughout that document.  

124
00:12:20,960 --> 00:12:27,920
Now some collaboration ideas! Because Equidox is 
a web-based application, there's a collaboration  

125
00:12:27,920 --> 00:12:34,480
aspect built into the tool. So we can 
actually work together and share documents  

126
00:12:34,480 --> 00:12:40,080
through the Equidox platform. And because we work 
on a concurrent user licensing model, that means  

127
00:12:40,080 --> 00:12:45,440
you can have multiple people logged into the 
account, into the same account simultaneously,  

128
00:12:45,440 --> 00:12:49,760
and you can even have multiple people working 
together on the same document simultaneously.  

129
00:12:51,120 --> 00:12:55,680
So Equidox gives you the ability to share 
documents with other users or groups  

130
00:12:56,240 --> 00:13:01,280
and you can actually divide and conquer. 
So let's say you have a 200-page document  

131
00:13:01,280 --> 00:13:05,120
and it's got a very tight deadline. You know, 
you'd like to get it posted by the end of the day.  

132
00:13:05,680 --> 00:13:10,400
Well rather than one person having to 
hunch over their computer all day and  

133
00:13:10,400 --> 00:13:15,200
kind of panic about this very large dense 
document, you might have five different users  

134
00:13:15,200 --> 00:13:20,560
and everyone takes 40 pages. And then you can kind 
of power through that document in an hour or two,  

135
00:13:20,560 --> 00:13:24,960
rather than having one person have to stress out 
and clear their calendar to make sure that they  

136
00:13:24,960 --> 00:13:29,520
can get through it. So this is all made possible 
because this is a cloud-based application.  

137
00:13:30,080 --> 00:13:33,600
Being able to share the document and 
even have multiple users working together  

138
00:13:33,600 --> 00:13:40,880
simultaneously has a lot of advantages built 
into it. As I mentioned before, images could  

139
00:13:40,880 --> 00:13:46,640
require subject matter experts so depending on 
your background or the nature of the document  

140
00:13:48,240 --> 00:13:53,600
these images that are contained in the document 
might be so complex that you're not exactly sure  

141
00:13:53,600 --> 00:13:58,320
how to provide an accurate alt description. So 
that again, the advantage of being web-based,  

142
00:13:58,320 --> 00:14:04,160
is you could send the URL for the page over 
through an instant messenger or through an email  

143
00:14:04,160 --> 00:14:08,400
to one of your colleagues, or one of your 
teammates who might be more familiar with the  

144
00:14:08,400 --> 00:14:14,160
content, and just ask them to take a few minutes 
to provide alt text for those images. And then you  

145
00:14:14,160 --> 00:14:18,800
can do the rest of the tagging of the documents. 
So from a structural standpoint, you can set your  

146
00:14:18,800 --> 00:14:22,960
reading order, and your headings, and your lists 
and your tables, but those images that require  

147
00:14:22,960 --> 00:14:28,480
that alternate text you might not be comfortable 
trying to provide that… If they are very technical  

148
00:14:28,480 --> 00:14:33,280
or very complex images… so you can get someone 
else involved in that workflow. Because this is  

149
00:14:33,280 --> 00:14:37,200
cloud-based, they can be working on that alt text 
while you are working on the rest of the document.  

150
00:14:38,960 --> 00:14:44,960
And also in the Equidox application, there is 
a validation tool, and a Page Notes feature,  

151
00:14:44,960 --> 00:14:49,760
so assuming that you're working together with 
a large team on a specific document, you can  

152
00:14:49,760 --> 00:14:56,320
use the validation tool to essentially mark pages 
as complete. So that you can avoid redundancies…  

153
00:14:56,320 --> 00:15:00,800
so someone isn't coming into a page and making 
adjustments and changing things that have already  

154
00:15:00,800 --> 00:15:08,640
been marked as validated. And then also the Page 
Notes feature is a way of just leaving yourself or  

155
00:15:08,640 --> 00:15:13,200
other users a note. Perhaps you skipped over 
an element because you weren't sure how to  

156
00:15:13,200 --> 00:15:19,920
approach it, or you'd like to just have some 
sort of communication with your colleagues  

157
00:15:20,480 --> 00:15:25,520
as to what happened on that specific page, or 
how you decided to approach it. Where they might  

158
00:15:25,520 --> 00:15:32,400
be able to sort of replicate that process on 
other similar pages. And Equidox will give you  

159
00:15:32,400 --> 00:15:36,480
a consolidated list of all of these various page 
notes that you take throughout the throughout the  

160
00:15:36,480 --> 00:15:42,480
document. And whether you're an Administrator 
or a power user, and you have less skilled less  

161
00:15:42,480 --> 00:15:46,800
trained workers working underneath you, you 
can very quickly look through the page notes  

162
00:15:46,800 --> 00:15:50,960
and make sure that everything has been addressed. 
If there were questions, or if there were issues,  

163
00:15:50,960 --> 00:15:56,240
you can always just follow up in the in the 
application and look at that specific page and  

164
00:15:56,240 --> 00:16:00,320
make sure that that issue was addressed. And we'll 
go through that as well in the demonstration.  

165
00:16:02,320 --> 00:16:09,040
Now eliminating repetition. So, if we have a 
lot of different tools built into Equidox that  

166
00:16:09,040 --> 00:16:16,000
allow you to programmatically apply things to all 
pages. So, if you are an existing Equidox user or  

167
00:16:16,000 --> 00:16:20,480
perhaps you've seen a demonstration before, you're 
probably familiar with our Zone detection slider.  

168
00:16:21,280 --> 00:16:27,280
So this is a tool that will redefine or detect 
the reading zones within a document. And if  

169
00:16:27,280 --> 00:16:31,120
you find that you have a pretty consistent 
formatting throughout the entire document,  

170
00:16:31,120 --> 00:16:36,880
you can apply this to all pages. Now the same 
thing can be done for the reading order. So  

171
00:16:36,880 --> 00:16:41,840
if you have, for example, every page in 
the document is a two-column reading order,  

172
00:16:41,840 --> 00:16:45,840
you can choose two columns as that 
reading order and hit “Apply to all pages”  

173
00:16:45,840 --> 00:16:50,800
and then Equidox will programmatically set that 
two column layouts to every one of those pages.  

174
00:16:51,840 --> 00:16:55,680
We also have the ability to set up a heading 
template. So again, assuming that the document  

175
00:16:57,120 --> 00:17:03,440
is consistently formatted and designed throughout, 
you can actually identify your heading hierarchy.  

176
00:17:03,440 --> 00:17:09,760
So for example if you find that your heading level 
twos are all in the same font style, the same font  

177
00:17:09,760 --> 00:17:15,280
characteristics, you can hit a simple checkbox and 
Equidox will programmatically look forward in the  

178
00:17:15,280 --> 00:17:21,520
document and identify all of the different areas 
of the document where you have that same font  

179
00:17:21,520 --> 00:17:26,480
style and will automatically apply that heading 
level two for you. And that can be done for all  

180
00:17:26,480 --> 00:17:32,320
of your various heading levels. We also have 
an “Ignore” feature. The Ignore feature is  

181
00:17:32,320 --> 00:17:38,400
the ability to bulk artifact repetitive 
elements in a document. So if you have  

182
00:17:39,120 --> 00:17:44,560
a footer or a header (maybe it's like a revision 
date or a serial number, something that is just  

183
00:17:44,560 --> 00:17:51,280
continuously repeating on every single page) you 
don't necessarily need to tag that on every page.  

184
00:17:51,280 --> 00:17:54,640
And you can use the ignore feature, 
if it's located in the same location,  

185
00:17:55,200 --> 00:18:00,080
to bulk artifacts all of that information 
throughout the entire document. So that you're  

186
00:18:00,080 --> 00:18:05,200
not feeding this redundant information to the 
screen reader user page after page after page.  

187
00:18:07,440 --> 00:18:13,040
Now another important part of this is to keep 
a rhythm. So, I find when I’m working on longer  

188
00:18:13,040 --> 00:18:20,160
documents particularly, that remediation can be 
a very rhythmic process. So if you have similar  

189
00:18:20,160 --> 00:18:25,200
layouts and designs throughout the document, 
a lot of those pages will require the same  

190
00:18:25,200 --> 00:18:31,520
techniques. And once you get through a handful of 
pages, you will start to eliminate redundancies  

191
00:18:31,520 --> 00:18:37,200
and consolidate steps. So that you can start 
just eliminating, literally eliminating clicks.  

192
00:18:37,200 --> 00:18:42,000
And if you're if you're doing a high volume 
type of project where you have a lot of pages to  

193
00:18:42,000 --> 00:18:47,360
get through, if you can eliminate a handful 
of clicks or a handful of steps on every page,  

194
00:18:47,360 --> 00:18:51,760
that really adds up to a lot of time savings 
at the end of that document, or the end of that  

195
00:18:51,760 --> 00:18:59,200
project. So, as you get into a rhythm, I find it's 
very helpful to try to stay within that rhythm.  

196
00:18:59,840 --> 00:19:04,080
And then the outlier type of pages, 
perhaps you come across a page  

197
00:19:04,080 --> 00:19:10,160
where you have a completely different layout, or 
there's a large infographic or a flow chart or  

198
00:19:10,160 --> 00:19:13,360
something that is completely different than the 
pages that you've been previously working, on  

199
00:19:14,400 --> 00:19:18,640
you can always skip over that page and just 
return to it at the very end of the process.  

200
00:19:19,200 --> 00:19:24,320
So rather than disrupting that flow that you've 
just developed for the previous 10 or 20 pages,  

201
00:19:24,320 --> 00:19:28,960
you can just skip over it and go back 
to that flow chart or back to that  

202
00:19:28,960 --> 00:19:34,560
infographic that requires a lot of extra work. 
And then you can kind of finish off the document  

203
00:19:34,560 --> 00:19:39,120
at the very end by addressing that outlier 
type of page at the very end of the workflow.  

204
00:19:41,040 --> 00:19:46,400
Now another part of Equidox is validating as you 
go. And this is something that we will also cover  

205
00:19:46,400 --> 00:19:52,160
in the in the demonstration when we get 
to it. So the HTML preview, if you've  

206
00:19:52,160 --> 00:19:58,400
used Equidox before I’m sure you're familiar 
with this, but the HTML preview is a way of  

207
00:19:58,400 --> 00:20:03,360
checking the structure that you've built on the 
page in terms of reading order, your headings,  

208
00:20:03,360 --> 00:20:08,960
lists, tables. All of that information that 
you have structured in that remediation process  

209
00:20:08,960 --> 00:20:15,920
will be previewable in the HTML preview page. And 
this is a way of just checking your work before  

210
00:20:15,920 --> 00:20:20,880
moving on to a subsequent page. So, you'll get 
a lot of feedback from the application as you're  

211
00:20:20,880 --> 00:20:26,160
going through at the page level. And if you're 
struggling with a certain page, you can always  

212
00:20:26,160 --> 00:20:30,960
revisit it and finish it off at the very end. So, 
it's just a way of checking your work as you go.  

213
00:20:31,920 --> 00:20:36,480
Also when you are finished working through 
a document, when you export the PDF,  

214
00:20:38,000 --> 00:20:44,000
Equidox will run a series of accessibility 
checks on that export. Now the bullet points  

215
00:20:44,000 --> 00:20:48,160
here on the slide… this is not a comprehensive 
list of everything that it is checking for,  

216
00:20:48,880 --> 00:20:53,680
but just a few examples of the things that it's 
looking for are missing alt text for images…  

217
00:20:53,680 --> 00:20:59,440
if you have illogical reading orders or logical 
heading structures… invalid merges… for example,  

218
00:20:59,440 --> 00:21:05,280
if you are trying to merge a list with a 
text zone, for example… And then the errors  

219
00:21:05,840 --> 00:21:11,280
that Equidox finds throughout this accessibility 
check, they are directly linked to the specific  

220
00:21:11,280 --> 00:21:15,360
page where it was found on. And they give you 
a clickable link where you can just select the  

221
00:21:15,360 --> 00:21:19,840
link and go straight to the page where that error 
was found. And then you can make your correction  

222
00:21:19,840 --> 00:21:24,800
in Equidox and then just re-export the document 
once you've worked through all of those errors.  

223
00:21:25,680 --> 00:21:29,840
So this accessibility check 
that we are applying on export,  

224
00:21:30,960 --> 00:21:36,480
as I said it's not a fully comprehensive 
accessibility report that you are getting…  

225
00:21:37,440 --> 00:21:41,520
We still highly recommend using 
third-party validation tools  

226
00:21:41,520 --> 00:21:47,440
and especially screen readers. Screen readers 
to replicate exactly what a screen reader user  

227
00:21:47,440 --> 00:21:52,080
is experiencing when they're working with this 
document. Now automated accessibility checking…  

228
00:21:52,720 --> 00:21:57,840
it can be automated to a certain degree but there 
are many, many different elements that it can miss  

229
00:21:58,640 --> 00:22:03,920
because it's simply looking for technical 
requirements. But it's not actually able to  

230
00:22:04,640 --> 00:22:08,960
replicate what an end user is going through with a 
screen reader. So it's very important to make sure  

231
00:22:08,960 --> 00:22:15,120
that you are that you are checking your work as 
you as you export the document. Putting it through  

232
00:22:15,120 --> 00:22:22,880
various third-party tools, or using screen readers 
which is the best and the ultimate check for the  

233
00:22:22,880 --> 00:22:29,760
actual usability of that document. Okay, so let's 
jump into Equidox now, and we'll work through a  

234
00:22:29,760 --> 00:22:34,800
couple of examples here… and I realize that we’ve 
got about 10 minutes left. So I’m going to go  

235
00:22:34,800 --> 00:22:39,120
pretty quickly through these documents. But that's 
sort of the point with Equidox, is to be able to  

236
00:22:39,120 --> 00:22:44,560
move very efficiently through them. So I have a 
couple of documents pre-loaded here into Equidox  

237
00:22:44,560 --> 00:22:49,760
and I want to start with this one here. And this 
is just a one-page document. So as I said before,  

238
00:22:49,760 --> 00:22:53,840
when you have a one-page document, sometimes it's 
best to just jump right in and see what you have  

239
00:22:54,480 --> 00:22:59,440
rather than trying to spend a few minutes 
to be very strategic and tactical with it.  

240
00:22:59,440 --> 00:23:04,640
You can just approach this page and just see what 
you've got in here, and start working through it.  

241
00:23:04,640 --> 00:23:09,360
Now what I notice right away is I have some 
images, I have some headings, I have text,  

242
00:23:09,360 --> 00:23:15,120
I have a list here, ( in fact, a nested list), and 
a table down here at the very bottom. So just to  

243
00:23:15,120 --> 00:23:20,160
quickly work through this, what I’m going to do is 
I’m going to start by, at the top and just start  

244
00:23:20,160 --> 00:23:24,560
artifacting images that I don't really need. 
I don't know what this is, just a background  

245
00:23:24,560 --> 00:23:32,800
sort of watermark type of image… Here's another 
image of black and white dog holding a briefcase…  

246
00:23:34,320 --> 00:23:39,600
here's our Equidox logo up here. So I’m 
just typing in all descriptions for them.  

247
00:23:39,600 --> 00:23:43,760
Now I’m going to work on my heading structures. So 
I hit… everything right now is currently set as a  

248
00:23:43,760 --> 00:23:48,800
text zone because this document was untagged 
to begin with. So if I just start hitting my  

249
00:23:48,800 --> 00:23:55,120
appropriate keyboard shortcuts to set my headings. 
Heading level 1, heading level 2, heading level 2,  

250
00:23:55,840 --> 00:24:02,080
and heading level 2. Now I’ve defined my headings 
for this page. Next up is this list. As you can  

251
00:24:02,080 --> 00:24:07,920
tell this is a nested list, and what I’ll do is 
I will hit “L” on my keyboard and I will use my  

252
00:24:07,920 --> 00:24:13,280
List Detection slider. So if I move this over, 
Equidox is going to look inside of this list and  

253
00:24:13,280 --> 00:24:18,400
it's going to pick up these nested layers inside 
of the individual list items. So if you can tell,  

254
00:24:18,400 --> 00:24:23,040
or if you've used Equidox before, you'll notice 
that this list has been automatically detected,  

255
00:24:23,040 --> 00:24:26,880
and the nestings have been detected 
inside of those individual list items,  

256
00:24:26,880 --> 00:24:31,680
simply by moving this list detection slider. So 
this is using artificial intelligence and machine  

257
00:24:31,680 --> 00:24:36,400
learning to better understand list structures, 
and something like this only takes a few seconds.  

258
00:24:37,280 --> 00:24:41,600
Now this down here is a table, and if you can 
tell I have a bunch of different text zones  

259
00:24:41,600 --> 00:24:47,440
covering up this table because it has no existing 
tag structure. So I’m not going to worry too much  

260
00:24:47,440 --> 00:24:52,320
about those existing zones. I’m just going to draw 
a single zone over the entire table, hit “T” on my  

261
00:24:52,320 --> 00:24:58,640
keyboard and open up the Table Editor. Once I 
open up the Table Editor, I’m going to then use  

262
00:24:58,640 --> 00:25:04,880
my detection tools here. So again, the computer 
vision and machine learning to redefine the table  

263
00:25:04,880 --> 00:25:10,400
structure. So the individual rows and columns 
and cells have been all identified through our  

264
00:25:10,400 --> 00:25:16,560
artificial intelligence. And then I can actually 
use the spanning feature to span across here for  

265
00:25:16,560 --> 00:25:21,440
these various years. I’m just holding Shift and 
pressing “S” on my keyboard. And then this is an  

266
00:25:21,440 --> 00:25:26,960
example of a table where I actually have two rows 
of column headers so 2017 and 18. And then the  

267
00:25:26,960 --> 00:25:33,200
various Q1s through Q4s… these are also going to 
be read as column headers. So, I will just change  

268
00:25:33,200 --> 00:25:39,440
my column header from the standard one to two. And 
then if I look at my HTML preview of this table,  

269
00:25:40,080 --> 00:25:45,520
what I see is a nice clean accessible HTML table. 
And then the great part of Equidox is that it will  

270
00:25:45,520 --> 00:25:52,000
take this table and it will automatically convert 
it into a PDF tag tree. Now when I save this table  

271
00:25:52,000 --> 00:25:57,360
and close out, all of those individual zones that 
were previously there have been artifacted. So I’m  

272
00:25:57,360 --> 00:26:04,000
just left with the single Table zone. So, the last 
thing I need to do now is just reorder the page.  

273
00:26:04,000 --> 00:26:08,400
Because I’ve removed some zones and I’ve drawn 
some zones manually, my reading order is a little  

274
00:26:08,400 --> 00:26:12,960
bit out of sync. So, all I’m going to do is go 
to the Page Tab and press “Reorder.” And I can  

275
00:26:12,960 --> 00:26:17,680
always check my HTML preview just to validate 
that I’m satisfied with everything that I see.  

276
00:26:17,680 --> 00:26:21,200
This all looks pretty good to me, so what 
I’ll do is I will just save the page.  

277
00:26:22,160 --> 00:26:27,040
I can mark it as validated if I'd like to, just 
to remind myself that I’ve already finished this>  

278
00:26:27,040 --> 00:26:33,360
And if I go to the Output Tab, I’m then able to 
generate the PDF. Now when I generate the PDF,  

279
00:26:33,360 --> 00:26:38,800
hopefully I’m not going to get any errors, and 
in fact I did not. But now the PDF opens up in  

280
00:26:38,800 --> 00:26:43,280
a separate tab for me in my browser. If you can 
tell, nothing is visually changed about this  

281
00:26:43,280 --> 00:26:48,080
document. It's exactly the same, but all of the 
tag structure that I’ve just set up during that  

282
00:26:48,080 --> 00:26:55,600
remediation process is going to be automatically 
converted into those PDF tags for me. Now with  

283
00:26:55,600 --> 00:27:00,960
just a few minutes left, I want to take a look at 
a bit of a longer document. And this is a document  

284
00:27:00,960 --> 00:27:08,320
here where it's quite a bit older. It's been it 
was created in 2007, and actually this document  

285
00:27:08,320 --> 00:27:14,240
has an OCR page. So this kind of incorporates a 
few different elements into it one place. I like  

286
00:27:14,240 --> 00:27:18,640
to start, when working with longer documents… Of 
course I’ll take a look at the thumbnails for each  

287
00:27:18,640 --> 00:27:24,160
of the pages and just try to get an understanding 
for what is this document actually made up of.  

288
00:27:24,800 --> 00:27:30,080
But then one thing I like to look at is the Images 
Tab. Now the Images Tab, I can see here there are  

289
00:27:30,080 --> 00:27:34,800
quite a few images in this document. And they are 
somewhat technical, because these are screenshots  

290
00:27:34,800 --> 00:27:40,640
and sort of instructional images. And some of the 
images already have alt text, whereas others do  

291
00:27:40,640 --> 00:27:44,640
not. So this is something to pay attention to 
as you're going through page by page, making  

292
00:27:44,640 --> 00:27:50,560
sure that your images have all been described or 
in some cases artifacted if you do not feel that  

293
00:27:50,560 --> 00:27:55,840
they need to be given a description. So this is 
something where I’m not really able to tell, based  

294
00:27:55,840 --> 00:28:00,480
on the context of the document, what this image is 
trying to represent. So I don't feel comfortable  

295
00:28:00,480 --> 00:28:05,760
providing alt text quite yet. I’ll wait till I get 
through the document and go through page by page.  

296
00:28:07,360 --> 00:28:12,880
Since I have OCR here on this very first page, 
I’m just going to use my Zone Detector. This  

297
00:28:12,880 --> 00:28:19,680
Zone Detection tool is something that we have not 
yet demoed, but it's definitely a huge part of the  

298
00:28:19,680 --> 00:28:25,120
Equidox system is using that Zone Detection 
tool. And you can redefine the granularity of  

299
00:28:25,120 --> 00:28:28,960
the reading zones. I have this background image, 
so I’m going to just get rid of that background  

300
00:28:28,960 --> 00:28:33,360
image, and I’m going to OCR all zones. So, I’m 
going to convert this scanned page. If you can  

301
00:28:33,360 --> 00:28:38,400
tell, this is actually scanned I’m actually going 
to convert it now into selectable searchable  

302
00:28:38,400 --> 00:28:43,520
usable text. And once I’ve done that, I can then 
set my heading level. So this is a heading level  

303
00:28:43,520 --> 00:28:48,720
one, because it's on the very first page, nice big 
bold font. And you can check your HTML preview.  

304
00:28:49,760 --> 00:28:56,240
So I’m pretty satisfied with that page I can then 
move on to the next. Now if we had the if we had  

305
00:28:56,240 --> 00:29:01,040
more time I would basically just be working 
through this document very quickly. A page  

306
00:29:01,040 --> 00:29:06,400
like this, where I had existing tag structure of 
one big P tag covering the entire page… this can  

307
00:29:06,400 --> 00:29:11,360
be very quickly adjusted, setting my headings 
and setting my list down here. So if I just  

308
00:29:11,360 --> 00:29:16,240
move my List Detector from left to right that will 
define this list with all the individual elements.  

309
00:29:17,040 --> 00:29:23,920
I can check my HTML preview… perhaps I want to 
get rid of these headers and footers, for example,  

310
00:29:23,920 --> 00:29:28,880
like for the revision date… This is the type 
of information that can just be very redundant…  

311
00:29:29,440 --> 00:29:32,880
So, using the Ignore feature as 
I mentioned before, if I just  

312
00:29:32,880 --> 00:29:37,680
draw a zone that's intersecting with that zone, 
I press “I” on my keyboard, that will become an  

313
00:29:37,680 --> 00:29:43,760
Ignore zone. And then if I go back to the preview, 
the revision date is no longer part of the tagged  

314
00:29:45,040 --> 00:29:49,200
elements. So if I go forward into the 
document and I look at other pages,  

315
00:29:50,160 --> 00:29:57,360
the Ignore zone is already waiting for me. So it's 
already there, ready to remove that revision date.  

316
00:29:58,480 --> 00:30:05,600
Now this is a 14- page document, and working 
through it I would spend probably about 30 seconds  

317
00:30:05,600 --> 00:30:10,720
per page on average to get through this. So it 
would be about a five- to ten-minute document  

318
00:30:10,720 --> 00:30:16,880
to get through using some of the steps that 
I’ve already explained and described. You know,  

319
00:30:16,880 --> 00:30:22,800
the Ignore feature, setting up a heading template, 
using the auto detection feature of the zones,  

320
00:30:23,360 --> 00:30:28,480
you can very quickly get through content 
like this. Because we've taken the time  

321
00:30:28,480 --> 00:30:32,400
to be a little bit more strategic in how we 
approach it. So you don't have to remember  

322
00:30:32,400 --> 00:30:35,760
to remove this on every page, you don't 
have to set your headings on every page,  

323
00:30:35,760 --> 00:30:40,720
because you can do it programmatically through 
the heading template. But this is what a sort of a  

324
00:30:41,760 --> 00:30:46,160
more refined workflow can look like when 
you're working through longer documents.  

325
00:30:46,160 --> 00:30:50,640
And even longer than 14 pages. Many times, you 
might have documents that are hundreds of pages,  

326
00:30:50,640 --> 00:30:56,000
and so the time savings can really be 
multiplied over those various pages.  

327
00:30:56,960 --> 00:31:01,680
And then when you export a document like this, 
(keeping in mind that I have not addressed every  

328
00:31:01,680 --> 00:31:07,440
page, this is going to actually produce some error 
messages for me) so this is where I just wanted to  

329
00:31:07,440 --> 00:31:12,160
show you that, for example, those missing images 
and as well as some other elements that I have  

330
00:31:12,160 --> 00:31:18,000
not yet touched, these are going to populate in 
this in this error list for me. And if I were  

331
00:31:18,000 --> 00:31:22,560
actually remediating this document, I would be 
able to go to the list of errors or warnings,  

332
00:31:22,560 --> 00:31:27,040
and I'd be able to click on these warning messages 
and go directly to the page where they're located,  

333
00:31:27,600 --> 00:31:32,720
fix them and then regenerate the PDF. Now I 
realize that we are just about out of time,  

334
00:31:32,720 --> 00:31:36,480
and I want to be respectful of everyone else's 
time, so I’m actually going to just jump back  

335
00:31:36,480 --> 00:31:41,840
to the slide deck here. And I will just say 
thank you again for everyone for joining today.  

336
00:31:42,480 --> 00:31:48,160
As I said before if you have any specific 
questions or feedback, we would love to chat  

337
00:31:48,160 --> 00:31:55,040
with you and talk about how Equidox can fit into 
your PDF remediation workflow. We can do another  

338
00:31:55,040 --> 00:32:00,720
more specific demonstration, working through some 
of your documents if you'd like, and talk about  

339
00:32:00,720 --> 00:32:07,440
how to define and refine a workflow for yourself. 
So please feel free to visit us at www.Equidox.co  

340
00:32:07,440 --> 00:32:13,840
or email EquidoxSales@Onixnet.com. So thank 
you everyone and we will see you next month! 

341
00:32:13,840 --> 00:32:19,600
[Tammy Albee] I will just interject that we've had 
a large number of questions during this webinar. I  

342
00:32:19,600 --> 00:32:26,240
believe I have answered all of them, but if anyone 
had more questions or needs a personalized demo to  

343
00:32:26,240 --> 00:32:33,280
get more questions answered and see the software 
in action, maybe in a little more detail, we are  

344
00:32:33,280 --> 00:32:39,360
more than happy to schedule that. Or you can email 
us at EquidoxSales@Onix.net.com, as you see on the  

345
00:32:39,360 --> 00:32:44,880
screen, and we'll be happy to answer any of those 
additional questions you might have. Thanks Dan! 

346
00:32:44,880 --> 00:32:55,840
[Dan Tuleta] Thanks everyone! 
Have a great rest of your day!