1
00:00:03,191 --> 00:00:08,800
[Dan Tuleta] Okay so I have two o'clock on my 
phone, so I think it's a good time to get started.  

2
00:00:09,440 --> 00:00:13,760
Thank you everyone for attending another 
edition of our Equidox Webinar Wednesdays.  

3
00:00:14,720 --> 00:00:19,360
Today we're going to be talking a bit 
about the on-premise solution. So Equidox,  

4
00:00:19,360 --> 00:00:24,800
as many of you may know from previous webinars or 
just exploring our website, historically, we've  

5
00:00:24,800 --> 00:00:31,120
always been a web-based application. So a PDF 
remediation solution that is hosted in the cloud.  

6
00:00:31,840 --> 00:00:37,920
But now we have a new development where we've 
actually taken the same functionality that the  

7
00:00:37,920 --> 00:00:42,560
end-users would experience when remediating 
with Equidox on the cloud-based version, and  

8
00:00:42,560 --> 00:00:47,680
we've given it a new platform for the on-premise 
solution. So for organizations that are looking  

9
00:00:47,680 --> 00:00:53,360
for different security protocols and measures, we 
can now have Equidox hosted and operating on your  

10
00:00:53,360 --> 00:00:59,840
network inside your own four walls. So that's the 
topic of the webinar today, and as always just to  

11
00:00:59,840 --> 00:01:03,920
mention, if you'd like to reach out to us, if 
you'd like to have a one-on-one discussion with  

12
00:01:04,560 --> 00:01:09,440
someone from our team, please feel free to 
reach out to us at EquidoxSales@onixnet.com,  

13
00:01:10,080 --> 00:01:17,200
or visit our website at Equidox.co. We're also 
very active on all of the social media platforms  

14
00:01:17,200 --> 00:01:21,040
so please feel free to follow us on 
LinkedIn, Twitter, Youtube, and Facebook.  

15
00:01:23,280 --> 00:01:28,880
Just before we get in into the nitty-gritty 
of the on-premise solution just a reminder  

16
00:01:28,880 --> 00:01:36,880
Equidox is a division of Onix. Onix is primarily 
a Google and an Amazon web services cloud partner.  

17
00:01:37,680 --> 00:01:42,480
So we are a major cloud consultancy and our 
mission is to improve organizational efficiency  

18
00:01:42,480 --> 00:01:48,160
through cloud computing solutions. We've 
been in business for 28 going on 29 years now  

19
00:01:48,720 --> 00:01:52,960
and Equidox being a division of Onix, our 
mission is to ensure that digital information  

20
00:01:52,960 --> 00:01:58,800
reaches everyone via accessibility solutions. So 
we are primarily affiliated with PDF remediation  

21
00:01:59,360 --> 00:02:02,960
both in our software and our services, 
but we also have a number of other  

22
00:02:02,960 --> 00:02:10,000
digital accessibility services as well. Just a 
quick slide here about who we serve we do have  

23
00:02:10,000 --> 00:02:16,640
quite a few customers across all the major 
verticals and we work with clients large small and  

24
00:02:16,640 --> 00:02:21,680
anything in between. So it doesn't matter 
which type of market you are in how large  

25
00:02:21,680 --> 00:02:27,120
your organization is, we are more than happy to 
work with you and help you in any way we can.

26
00:02:29,920 --> 00:02:36,800
So today, if you've been on these webinars before 
you probably are familiar with me. I'm typically  

27
00:02:36,800 --> 00:02:41,200
on all of them so my name is Dan Tuleta. I'm 
a sales engineer here with the Equidox team.  

28
00:02:41,840 --> 00:02:46,240
So I typically have been hosting these webinars. 
But today everyone's going to be lucky you're  

29
00:02:46,240 --> 00:02:51,200
going to hear some different voices. So we 
also have Ron Runyan our development lead.  

30
00:02:52,160 --> 00:02:57,520
Ron is primarily involved with the development and 
the implementation of all of the new features and  

31
00:02:57,520 --> 00:03:03,120
functionality within Equidox. We also have Zach 
Easterling, who handles our quality assurance.  

32
00:03:03,120 --> 00:03:08,800
So Zach does a number of different testing and 
is heavily involved in the development cycles  

33
00:03:08,800 --> 00:03:15,360
prioritizing what should be coming out next and 
also works a lot with customer support as well. So  

34
00:03:15,360 --> 00:03:20,560
a couple of different people from our team will 
be talking today and with that said I'm actually  

35
00:03:20,560 --> 00:03:26,560
gonna turn it over to Zach to kind of get started 
here. And we're gonna have a little bit of a Q&A,  

36
00:03:26,560 --> 00:03:32,160
a little bit of back and forth to start talking 
through some of the different components and why  

37
00:03:32,160 --> 00:03:37,360
the on-premise solution of Equidox is really 
beneficial to a lot of different organizations.  

38
00:03:38,720 --> 00:03:46,080
So Zach the first thing first things first why 
did we create this Equidox on-premise solution? 

39
00:03:46,080 --> 00:03:51,600
[Zach Easterling] Thanks, Dan! Well again just to 
start off, thank you very much for giving us an  

40
00:03:51,600 --> 00:03:56,560
opportunity to answer some of these questions. 
This is my first webinar so go easy on me!  

41
00:03:57,120 --> 00:04:04,800
But I, you know the title of this slide is 
actually probably the answer to your question.  

42
00:04:04,800 --> 00:04:10,880
We recognized a need. A lot of our customers 
are starting to move into some of the secure  

43
00:04:10,880 --> 00:04:18,320
documentation. And because of that security 
because of the security requirements, it's  

44
00:04:18,320 --> 00:04:23,920
sometimes necessary to bring that data or maybe to 
keep and maintain that data within, like you said,  

45
00:04:23,920 --> 00:04:30,800
your four walls. Up in the cloud, you know, we 
trust our partners Google, we trust our partners  

46
00:04:30,800 --> 00:04:39,440
AWS. But a lot of organizations have put a lot of 
hard work and money into security protocols and  

47
00:04:41,520 --> 00:04:51,840
so they want their data to be stored within that 
security protocol. So just really the concept of  

48
00:04:51,840 --> 00:04:58,800
making sure that data is maintained within your 
four walls, and always follows the security  

49
00:04:58,800 --> 00:05:06,480
protocols set forth for your organization.
[Dan] Great! And who is this on-premise this  

50
00:05:06,480 --> 00:05:12,400
on-premise version of Equidox really intended for?
[Zach ] Well we like to think that it's for all  

51
00:05:12,400 --> 00:05:20,720
levels of government: local, state, and federal. 
It's for financial organizations, banking,  

52
00:05:20,720 --> 00:05:29,840
insurance, healthcare, as well any types of 
organizations where you have secure data...  

53
00:05:30,560 --> 00:05:38,240
where you might need to limit the access of 
that data outside your current network...  

54
00:05:38,240 --> 00:05:47,120
or any organization that has some unique security 
protocols that really can't be adhered to  

55
00:05:47,120 --> 00:05:54,560
using a solution that's up in the cloud.
[Dan] Great, and Zach so you've talked a  

56
00:05:54,560 --> 00:05:58,240
little bit about some sensitive data. 
What would qualify as sensitive data? 

57
00:05:58,240 --> 00:06:04,640
[Zach] Well on this slide, we've 
listed it out, but let's think about it  

58
00:06:04,640 --> 00:06:10,160
from an organizational perspective. So if you're 
in the healthcare industry, you're looking for  

59
00:06:11,840 --> 00:06:16,240
personally identifiable information, PII, 
or sometimes in healthcare, it's called PHI.  

60
00:06:17,040 --> 00:06:23,120
That could be things like your social security 
number, or your Medicare or Medicaid number,  

61
00:06:23,920 --> 00:06:30,960
any kind of health records or condition reports. 
Maybe diagnoses or medications that you have  

62
00:06:32,560 --> 00:06:39,360
as well. If we take a look at the next point, 
client data, what comes to mind for me at least,  

63
00:06:39,360 --> 00:06:48,640
is in the legal realm. We see a lot of legal 
contracts that need to be remediated, or maybe  

64
00:06:48,640 --> 00:06:54,080
even evidence as well. Evidence in trials. All 
of that needs to stay within your four walls.  

65
00:06:55,760 --> 00:07:02,240
Company records is another great example. Internal 
Human Resources need to be able to transfer that  

66
00:07:02,240 --> 00:07:08,400
documentation back and forth between each other. 
That needs to be remediated, but that has a lot of  

67
00:07:09,600 --> 00:07:12,640
very personal information in it, 
whether that's your work history,  

68
00:07:13,840 --> 00:07:19,120
whether that could be proprietary 
information that a company is working on,  

69
00:07:19,920 --> 00:07:26,640
or maybe unique individuals within 
a very, let's say limited groupset.  

70
00:07:28,320 --> 00:07:34,400
Things like financial records as well in the 
banking industry. That's kind of paramount.  

71
00:07:35,280 --> 00:07:46,160
So account information, routing information, any 
kind of stocks or tax information, things that are  

72
00:07:48,000 --> 00:07:54,560
future looking like maybe PR releases, 
as well proprietary information.  

73
00:07:58,000 --> 00:08:03,920
Again PR releases and in just other 
sensitive information general things that  

74
00:08:03,920 --> 00:08:07,760
need to stay within your four 
walls, that need to be remediated,  

75
00:08:07,760 --> 00:08:12,160
that need to be shared internally, but 
should never really reach the outside world.

76
00:08:14,760 --> 00:08:20,480
[Dan] Great, and so Zach, so what is this 
Equidox on-premise solution? [Zach] Well  

77
00:08:22,400 --> 00:08:28,320
it's the same as the cloud-based. It is just a 
little bit different in the location of where  

78
00:08:28,320 --> 00:08:34,160
it lives. We basically plucked it right out of 
the cloud and kind of packaged it up so that  

79
00:08:34,160 --> 00:08:41,280
it can live within your hardware well within 
a customer's hardware, within their network.

80
00:08:43,560 --> 00:08:50,960
[Dan] Great and for anyone that isn't really sure 
what Equidox is, at the end of this webinar I'm  

81
00:08:50,960 --> 00:08:54,640
going to be doing a short demonstration to 
just kind of walk through some of the basics  

82
00:08:54,640 --> 00:08:58,720
so you'll have an idea of what this Equidox 
solution is for if you've not yet seen it.  

83
00:09:00,640 --> 00:09:03,520
So Zach if you don't mind, 
would you just take a moment to  

84
00:09:04,160 --> 00:09:08,800
describe some of the components and maybe some of 
the slight differences but similarities between  

85
00:09:08,800 --> 00:09:13,520
the cloud-based and the on-premise version?
[Zach] Sure. I actually love this slide because  

86
00:09:13,520 --> 00:09:21,120
it's going to give me a real strong basis for what 
we need to talk about. So again, like we said,  

87
00:09:21,760 --> 00:09:26,640
the difference is really where it lives. So in 
the on-premise solution, you're still going to get  

88
00:09:26,640 --> 00:09:31,600
all of your Smart Detection Tools. It's going to 
look and feel the same. You'll still have your UI,  

89
00:09:31,600 --> 00:09:36,480
you'll still have your import and your 
export, you've got your collaboration.  

90
00:09:36,480 --> 00:09:41,280
So you'll still be able to share documents 
to specific users or to a group of users.

91
00:09:43,760 --> 00:09:50,160
Again because it's basically mimicking the 
cloud-based solution it's easy to learn.  

92
00:09:50,160 --> 00:09:55,920
All of the documentation works exactly the same 
and you're still always going to get your same  

93
00:09:56,480 --> 00:09:59,280
output type. So PDF, HTML, and ePub.  

94
00:10:01,280 --> 00:10:05,760
A little bit of the differences in there: the 
cloud-based solution generally can be accessed  

95
00:10:05,760 --> 00:10:11,440
from any internet connection. So whether you're 
in your office, whether you're in your car,  

96
00:10:11,440 --> 00:10:19,680
or at home on your desk, you can get to the 
Equidox in the cloud. Now on the on-premise,  

97
00:10:19,680 --> 00:10:25,760
that's really restricted. The application is 
run in a very restricted environment on virtual  

98
00:10:25,760 --> 00:10:33,120
machines. It's generally only accessible via the 
internal network or the intranet and there are no  

99
00:10:33,120 --> 00:10:38,480
cloud dependencies. So you wouldn't be able to 
work on a document at home and then, I'm sorry,  

100
00:10:38,480 --> 00:10:42,400
work on a document at work and then realize you 
need to download a copy of it at home. That just  

101
00:10:44,080 --> 00:10:48,720
wouldn't meet the requirements for the security 
to maintain all of that data at an organization.

102
00:10:51,640 --> 00:10:57,600
[Dan] Great and just here is just another 
slide kind of talking about the on-premise  

103
00:10:57,600 --> 00:11:02,000
components. Maybe this will help you 
visualize a little bit more. But Zach,  

104
00:11:02,000 --> 00:11:05,760
do you want to take a moment to explain?
[Zach] Of course. Equidox has really broken  

105
00:11:05,760 --> 00:11:11,680
down into three main cores. We've got the 
application core, and that handles the UI,  

106
00:11:12,480 --> 00:11:19,280
the user interface, the import and the 
export at its base level. We've got the AI  

107
00:11:19,280 --> 00:11:23,440
so that's all of your Smart Detection Tools. 
So if you detect a table or you detect a list  

108
00:11:24,720 --> 00:11:30,320
or you use any of the sensitivity, that's where 
that lives. Then lastly there's a data storage.  

109
00:11:30,320 --> 00:11:40,480
So that stores all of your layouts and all 
of your PDFs as originals. All of that is  

110
00:11:40,480 --> 00:11:46,560
packaged into one image and that's provided 
to your IT team in the on-premise solution.

111
00:11:48,600 --> 00:11:53,360
[Dan] So Zach, what are some of the setup 
options? How do we get this set up and deployed? 

112
00:11:53,360 --> 00:11:59,520
[Zach] Well the simplest setup is just a single 
machine that runs all three of those cores.  

113
00:12:00,240 --> 00:12:03,680
It runs... the app core runs, the 
ML core and it runs the data store.  

114
00:12:05,520 --> 00:12:15,440
We've kind of... we have a user count in mind. 
So generally that single machine is going to be  

115
00:12:15,440 --> 00:12:20,880
good for you know 20 to 25 users. There are 
different ways to set it up you could set  

116
00:12:20,880 --> 00:12:28,240
the application core up onto multiple machines 
and balance that. So that maybe an organization  

117
00:12:28,240 --> 00:12:36,720
that has a hundred or 200 users could have 
just a similar experience as just a single  

118
00:12:36,720 --> 00:12:43,280
machine. But in general you can set it up with all 
three of those cores on one machine, or you can  

119
00:12:43,280 --> 00:12:51,040
split those cores up across multiple machines.
[Dan] Great and what would the sort of minimum  

120
00:12:51,040 --> 00:12:54,240
system requirements be for 
the on-premise solution? 

121
00:12:54,240 --> 00:13:02,000
[Zach] Well the individual single 
image does handle 20 to 25 users.  

122
00:13:04,480 --> 00:13:09,520
If we come into a customer and we consult with 
them and we find that 20 to 25 is the number  

123
00:13:09,520 --> 00:13:14,800
that they're shooting for, we generally recommend 
four CPUs on the hardware that they're deploying,  

124
00:13:14,800 --> 00:13:23,520
eight gigs of RAM and about 100 gigs of storage. 
Let's say that the system needed to be accessible  

125
00:13:23,520 --> 00:13:28,960
for a hundred users, you'd probably quadruple 
most everything. So you'd go up to 16 CPUs,  

126
00:13:30,240 --> 00:13:34,800
you probably wouldn't have to quadruple the 
RAM although 32 gigs would be nice, and maybe  

127
00:13:34,800 --> 00:13:42,320
doubling or tripling the hard drive space.
[Dan] Great. And Zach can you talk a little  

128
00:13:42,320 --> 00:13:50,240
bit about the scalability of Equidox?
[Zach] Sure so each one of those individual  

129
00:13:50,240 --> 00:13:58,480
components: the AI core, the ML core, or the 
data storage can be split out. And by scaling to  

130
00:13:58,480 --> 00:14:03,360
each one of those, you can scale to the number 
of users that you need. So increasing the RAM,  

131
00:14:03,360 --> 00:14:11,200
again increasing the RAM or the CPUs for any 
kind of situation where you're going to do heavy  

132
00:14:12,000 --> 00:14:20,080
heavy user loads... You can allocate larger hard 
drive resources. In cases where we know that most  

133
00:14:20,080 --> 00:14:25,840
PDFs are in the two to three mg range, but if 
you're working on thousand-page legal documents  

134
00:14:26,400 --> 00:14:33,280
or thousand-page documents that have 
full-blown architectural images in them,  

135
00:14:33,280 --> 00:14:39,040
we know those sometimes can get to 200-300 
mg large. So by allocating more hard drive  

136
00:14:39,040 --> 00:14:44,800
space, it really allows you to stay scalable 
to the types of documents that you work with.

137
00:14:47,160 --> 00:14:53,200
[Dan] Great, and Zach can you talk 
a little about the IT administrator  

138
00:14:53,200 --> 00:14:59,520
interface and how that's going to work?
[Zach] Yeah so the on-premise solution has  

139
00:14:59,520 --> 00:15:04,320
one additional piece, one additional 
user interface that the app doesn't have.  

140
00:15:04,320 --> 00:15:10,400
And it's the IT administrator interface. 
This is really a point where your IT team  

141
00:15:11,280 --> 00:15:15,040
at a customer is going to come in and 
set some of your base configurations. So  

142
00:15:16,080 --> 00:15:22,320
it'll kind of help them decide whether they should 
have one AI core, one ML core, and one datastore  

143
00:15:22,320 --> 00:15:30,320
all on the same machine, or it might allow them 
to decide that they need to have three application  

144
00:15:30,320 --> 00:15:37,680
cores, one ML, and one storage core. So it gives 
them basically a setup wizard to do all of that.  

145
00:15:38,640 --> 00:15:41,920
Additionally, it allows them to 
monitor the system status. So  

146
00:15:41,920 --> 00:15:48,160
they can see that if the application core is 
running at maybe 85 or 90 percent of capacity.  

147
00:15:48,800 --> 00:15:55,600
It'll allow them to create a new application 
core, kind of reduce that capacity and balance  

148
00:15:55,600 --> 00:16:01,920
that load across multiple applications. It 
also is a place for them to install updates,  

149
00:16:03,120 --> 00:16:08,000
and we know that the IT, as well, generally 
is…. well I shouldn't say generally,  

150
00:16:08,000 --> 00:16:14,400
but could be responsible for user administration. 
This new screen isn't necessarily where they  

151
00:16:14,400 --> 00:16:18,400
would do that. They'd still do all of their 
user administration inside the Equidox app.  

152
00:16:18,400 --> 00:16:23,520
This really is more of a very technical 
interface to give them a status of the system.

153
00:16:26,360 --> 00:16:31,120
[Dan] And Zach can you talk a little 
bit about the how support is going to  

154
00:16:31,120 --> 00:16:38,720
work with the Equidox on premise solution?
[Zach] Sure. So customers are still going  

155
00:16:38,720 --> 00:16:44,160
to get the same level of application support 
as they've experienced in the cloud solution.  

156
00:16:46,400 --> 00:16:54,000
Additionally, we're going to offer operational and 
configuration support to start-up and set up the  

157
00:16:56,640 --> 00:17:03,040
machine. So your when your IT team gets this 
image, we'll be able to help configure and  

158
00:17:03,040 --> 00:17:09,840
support that. But more importantly, what we're 
really interested in doing is helping to handle  

159
00:17:09,840 --> 00:17:17,520
the day-to-day remediation support and all of 
the questions around that. And that kind of sets  

160
00:17:17,520 --> 00:17:24,480
up what we consider an ”Equidox specialist,” 
or maybe an “Equidox champion”. That champion  

161
00:17:24,480 --> 00:17:29,760
is really going to be trained and designed to 
kind of foster the accessibility culture within  

162
00:17:29,760 --> 00:17:37,600
an organization. That could be an individual. 
or at a large organization, it could be a team.  

163
00:17:37,600 --> 00:17:41,920
And that team is really designed to handle the 
remediation-specific questions for documents.  

164
00:17:43,440 --> 00:17:48,560
Especially for documents that can't be shared 
via the internet through our normal support  

165
00:17:48,560 --> 00:17:57,280
channels. So in the on-premise implementation, we 
do help train and build an internal team to handle  

166
00:17:57,280 --> 00:18:05,200
some of those remediation-specific questions.
[Dan] Great and can you take a moment to describe  

167
00:18:05,200 --> 00:18:10,240
some of the benefits of this on-prem solution?
[Zach] Sure well as  

168
00:18:12,320 --> 00:18:17,360
as we've talked about. It's mainly for security. 
But some of the other things that you're going  

169
00:18:17,360 --> 00:18:22,560
to inherit when you use this on-premise is that 
it's as fast and secure as the internal network  

170
00:18:22,560 --> 00:18:30,480
that you're placing this image on. You don't have 
to rely on internet upload or download speeds.  

171
00:18:31,120 --> 00:18:38,880
You can rely on your intranet speeds. So moving a 
let's say a 200 mg file through the internet via  

172
00:18:38,880 --> 00:18:44,640
an upload could take 10 minutes, but on your 
internal network that might take 10 seconds.  

173
00:18:45,200 --> 00:18:47,680
It could be faster, could be slower, depending on  

174
00:18:48,320 --> 00:18:55,840
what your intranet looks like, but you'll you'll 
find a huge benefit in just moving files around.  

175
00:18:56,400 --> 00:19:03,200
So you know, we've seen that definitely through 
upload speeds. The way that the data storage is  

176
00:19:03,200 --> 00:19:10,720
accessed as well, allows us to export documents 
a lot faster. So in general we can go through,  

177
00:19:10,720 --> 00:19:14,720
I would say, maybe 15 or 20 pages 
in a minute in the cloud solution.  

178
00:19:16,240 --> 00:19:23,360
We can get that down to just a couple of seconds 
with this on-premise. So transferring that that  

179
00:19:23,360 --> 00:19:28,640
information between cloud services is no longer 
necessary because it all lives in the same place  

180
00:19:28,640 --> 00:19:35,600
in your local hardware, in your local 
storage. The UI is faster as well, again,  

181
00:19:35,600 --> 00:19:39,840
because it's page loading and it's page loading 
within the intranet. It's just a lot faster,  

182
00:19:41,520 --> 00:19:51,600
and as well, like we talked about, when 
you buy Equidox on-prem, we do foster  

183
00:19:51,600 --> 00:19:58,800
that culture of accessibility. We help train 
and build those Equidox internal specialists.

184
00:20:02,120 --> 00:20:11,840
[Dan] All right. So thank you so much Zach for 
all of that great information. Now for all the  

185
00:20:11,840 --> 00:20:17,760
attendees on the call right now, we do have this 
video inserted that contains an Equidox demo. But  

186
00:20:17,760 --> 00:20:22,000
while we're all here I'm actually to just close 
out of this and do a live demonstration. So when  

187
00:20:22,000 --> 00:20:25,840
you receive the recording this video will be here 
available for you. So if you'd like to share this  

188
00:20:25,840 --> 00:20:29,600
internally with someone else from your team 
or someone that couldn't make this call today  

189
00:20:30,160 --> 00:20:37,680
they will be able to get more of a visualization 
of how Equidox works. Now what I'm going to do is…  

190
00:20:39,040 --> 00:20:52,000
Excuse me this ZOOM button is always giving 
me a problem. If I can just close out of that…  

191
00:21:00,240 --> 00:21:15,840
This ZOOM. It does never...it's 
always in the way for me...

192
00:21:16,560 --> 00:21:25,040
Okay! All right so what I'm going to do is I've 
pulled up Equidox and I'm actually working on the  

193
00:21:25,040 --> 00:21:30,480
cloud version of Equidox. But keep in mind that 
from the remediator’s perspective the interface  

194
00:21:30,480 --> 00:21:34,640
and the functionality are going to be exactly 
the same. So this is essentially what Equidox  

195
00:21:34,640 --> 00:21:39,680
will look like for any user that is interacting 
with the tool. Now what we have here is just  

196
00:21:40,240 --> 00:21:44,720
a page or a list of documents that have been 
loaded into the application by importing them  

197
00:21:44,720 --> 00:21:48,480
through this second tab on the left-hand side. 
And just in the interest of time, I'm actually  

198
00:21:48,480 --> 00:21:54,320
going to jump straight into the remediation of a 
document. Now this document here, if I click on it  

199
00:21:54,880 --> 00:21:59,600
this will present me the Document Detail page. And 
here I have basic information about the document:  

200
00:22:00,240 --> 00:22:04,880
when it was published, the title of the document, 
which I can edit and enhance if I need to. I can  

201
00:22:04,880 --> 00:22:09,040
do things like setting the language attribute if 
I have documents that are in multiple languages or  

202
00:22:09,040 --> 00:22:14,880
different languages. I have an Images tab that 
will give me a consolidated list of all of the  

203
00:22:14,880 --> 00:22:20,000
images in the document in one location where I'm 
able to actually apply alt text if I need to.  

204
00:22:20,960 --> 00:22:26,400
And I also have the Output tab here that I want 
to mention. So if you aren't aware, it was briefly  

205
00:22:26,400 --> 00:22:31,680
mentioned during the webinar but we are able to 
export documents in either an HTML a PDF or an  

206
00:22:31,680 --> 00:22:37,520
ePub format. And we also have this new feature 
called Zone Transfer where if you have documents  

207
00:22:37,520 --> 00:22:43,920
that are of a very similar layout or maybe you 
have you've made some minor edits to a document or  

208
00:22:43,920 --> 00:22:48,160
you have a document that is basically a template 
that you're producing on a daily, or weekly, or  

209
00:22:48,160 --> 00:22:53,120
monthly basis, you can actually take the layout of 
these zones (which we'll get to in just a second)  

210
00:22:53,120 --> 00:22:56,720
and you can apply that to future iterations of 
that document. So that you don't actually have  

211
00:22:56,720 --> 00:23:02,880
to remediate that same basic layout time and time 
again. It's a very powerful tool especially with  

212
00:23:02,880 --> 00:23:07,280
longer documents that you might spend several 
hours working through. Because it's hundreds  

213
00:23:07,280 --> 00:23:11,920
of pages. If you can take that same layout and 
apply it to a future iteration or a different  

214
00:23:12,880 --> 00:23:18,880
copy of that document in the future, it can be a 
massive time saver. So speaking of those zones,  

215
00:23:18,880 --> 00:23:23,520
what I'm going to do is I'm going to actually 
just jump right into to the main interface here.  

216
00:23:23,520 --> 00:23:29,200
And what I'm looking at, I've now just isolated 
the single page of this document and what I'm  

217
00:23:29,200 --> 00:23:34,320
struck with right away are these different boxes 
that are covering up the content on this page.  

218
00:23:34,880 --> 00:23:40,080
Now, this is what Equidox does while 
it's importing. The file, this document,  

219
00:23:40,080 --> 00:23:44,720
was completely untagged, to begin with. There 
was no tag structure at all. But Equidox what it  

220
00:23:44,720 --> 00:23:49,760
does is it starts recognizing where the data is 
located and it will begin identifying that data  

221
00:23:49,760 --> 00:23:54,560
and drawing reading zones, what we call reading 
zones, around them. Now these reading zones,  

222
00:23:54,560 --> 00:23:59,120
when we import, they're going to be things like 
images. So these images are here and they are  

223
00:23:59,120 --> 00:24:04,720
locked in place and it's my job as a remediator 
to either describe them with an alt text or I  

224
00:24:04,720 --> 00:24:09,840
can artifact them if I find them to be sort of 
just decorative in nature. I also have other  

225
00:24:09,840 --> 00:24:14,720
components here where I have like headings, for 
example, which are critical for PDF accessibility,  

226
00:24:14,720 --> 00:24:20,400
I need to provide that sort of navigation tool for 
an end-user to freely move around this document.  

227
00:24:21,040 --> 00:24:25,840
And that is done mainly by headings. S I'll have 
to identify my headings. I also have a pretty  

228
00:24:25,840 --> 00:24:30,640
complicated list here. So this is what we call a 
nested list, where you have lists inside of list  

229
00:24:30,640 --> 00:24:35,520
items inside of other lists. So you have it's 
almost like an outline. But these can be quite  

230
00:24:35,520 --> 00:24:40,560
tricky to remediate in other tools. So I will show 
you how we remediate this document or this list  

231
00:24:40,560 --> 00:24:45,680
rather in our Equidox solution. And we also have 
a table down below that I'm going to work through.  

232
00:24:45,680 --> 00:24:50,560
So some different elements here. The reason I'm 
using this document, it's pretty straightforward,  

233
00:24:50,560 --> 00:24:55,680
but it does kind of consolidate a lot of the 
functionality that you'll see throughout all of  

234
00:24:55,680 --> 00:25:00,800
your documents into a single page. So we can kind 
of keep it all isolated here on just one page.  

235
00:25:02,080 --> 00:25:07,120
Okay, so a couple of things to mention 
about the Equidox remediation process. If  

236
00:25:07,120 --> 00:25:11,680
you're not satisfied with the detection 
level that Equidox has given you, or  

237
00:25:12,240 --> 00:25:16,480
if you have a document that was previously tagged 
and you don't like the existing tag structure,  

238
00:25:16,480 --> 00:25:21,280
you can use this Detection Slider. So if you 
notice, if I move this Detection Slider tool,  

239
00:25:22,720 --> 00:25:28,720
the zones will start to change their sort of size 
and granularity. So as I zoom this in and out,  

240
00:25:28,720 --> 00:25:32,640
I'm able to just redefine my starting 
point so that I don't have to make as many  

241
00:25:32,640 --> 00:25:37,120
manual adjustments to the page. So if I find a 
detection level that I feel works a bit better  

242
00:25:37,120 --> 00:25:40,640
for me on this page, I can stick with it 
and then just begin working from there.  

243
00:25:41,600 --> 00:25:47,120
Most of the time Equidox will give you a really 
nice Detection level just by simply importing it.  

244
00:25:47,120 --> 00:25:51,520
But there can be some of those outlier pages where 
you have a strange layout and you might want to  

245
00:25:51,520 --> 00:25:55,280
move that around a bit to give yourself a 
different starting point so that you like I said,  

246
00:25:55,280 --> 00:26:00,000
don't have to make as many changes. Now another 
important part of Equidox is this button up here  

247
00:26:00,000 --> 00:26:04,800
which looks like a computer monitor. If I press 
this at any time, what this does is it opens a  

248
00:26:05,600 --> 00:26:09,840
separate tab in your browser which gives you 
an HTML rendering of the page that you're  

249
00:26:09,840 --> 00:26:15,600
currently working on. So you can see here 
in your HTML preview exactly what you're  

250
00:26:15,600 --> 00:26:22,160
building in terms of your lists, your tables, your 
headings, all of this starts to render in HTML.  

251
00:26:22,160 --> 00:26:26,960
And it gives you this preview so that you don't 
have to actually interact with the tags yourself.  

252
00:26:26,960 --> 00:26:32,080
You simply need to check your progress as you 
go via this HTML preview. So we'll jump back  

253
00:26:32,080 --> 00:26:38,880
and forth from that a couple of times. Now just 
starting here at the top of this particular page,  

254
00:26:39,520 --> 00:26:43,600
one thing I want to do is I'm going to just 
artifact these things like logos. These can be  

255
00:26:43,600 --> 00:26:48,560
considered decorative and also this is where it 
says “PDF sample document.” I don't necessarily  

256
00:26:48,560 --> 00:26:53,280
need that in the form of an image. What I could do 
with it, if I really chose to since it's an image,  

257
00:26:53,280 --> 00:26:57,600
is I could actually use an OCR feature where I 
can actually convert that into something that  

258
00:26:57,600 --> 00:27:03,200
is text. I don't then have to actually type out 
anything to describe that as an image. The next  

259
00:27:03,200 --> 00:27:07,120
thing I want to worry about are my headings. So 
this is my heading level one. I actually have  

260
00:27:07,120 --> 00:27:11,760
it labeled for us right here. So this being a 
heading level one, I can simply tap “1” on my  

261
00:27:11,760 --> 00:27:18,000
keyboard to identify it as a heading level one. 
Down below I have a heading level 2 so I'm gonna,  

262
00:27:18,000 --> 00:27:24,000
because of the font size being similar and the 
spacing kind of very tight on this page, it kind  

263
00:27:24,000 --> 00:27:29,120
of consolidated the heading and the text into a 
single zone. So I'm just going to quickly resize  

264
00:27:29,120 --> 00:27:35,120
and just draw a new zone. Just so you can see 
that. You know identifying content is as simple  

265
00:27:35,120 --> 00:27:41,600
as just clicking and dragging and resizing zones. 
It is very easy as well. Here's another just an  

266
00:27:41,600 --> 00:27:45,600
image that I'm going to define as decorative. 
This is just like a silhouette. It's there to  

267
00:27:45,600 --> 00:27:49,840
just break up the page. So again I'm just going 
to hit “backspace” to artifact it because there's  

268
00:27:49,840 --> 00:27:53,520
really not much of a description that I would type 
in there that's going to add value to this page.  

269
00:27:54,160 --> 00:28:00,560
I might take this image here of our what we 
call Equidog. So this is a little dog holding  

270
00:28:00,560 --> 00:28:04,720
a briefcase that has our Equidox logo on it. 
So that's exactly what I can type in. So I can  

271
00:28:04,720 --> 00:28:12,320
come over here to the alt text field and type in 
“dog holding a briefcase with an Equidox logo.”  

272
00:28:13,840 --> 00:28:18,800
And then so moving down the page here, 
now that we've handled all of our images,  

273
00:28:18,800 --> 00:28:23,360
I have this... this is actually in a heading 
level 3 that I'm gonna call I'm gonna tap “3” on  

274
00:28:23,360 --> 00:28:27,360
my keyboard to set that as a heading level three. 
To identify this list... but the list here is the  

275
00:28:27,360 --> 00:28:32,240
real star of the show. So as it currently sits, 
if we go back to the preview just for a second…  

276
00:28:34,240 --> 00:28:41,440
If you can tell, this list is really... it's got 
some major issues. We have the all these bullet  

277
00:28:41,440 --> 00:28:46,240
points are kind of just running together, and this 
would be read as just a strange run-on sentence.  

278
00:28:46,240 --> 00:28:52,240
But if I were to just hit “L” on my keyboard, and 
move my Detection Slider from left to right, this  

279
00:28:52,240 --> 00:28:57,280
is going to trigger machine learning and computer 
vision where Equidox is able to define all of  

280
00:28:57,280 --> 00:29:02,960
these list items. And then the sub lists inside of 
those list items. So just by moving that Detection  

281
00:29:02,960 --> 00:29:09,280
Slider from left to right, I have built a nice 
clean nested list with the proper structure. And  

282
00:29:09,280 --> 00:29:14,160
keep in mind, Equidox does the hard part where 
it will actually export this in the form of a  

283
00:29:14,160 --> 00:29:20,320
PDF with all of the necessary tags. So even if you 
know nothing about PDF tagging, you don't have to  

284
00:29:20,320 --> 00:29:25,360
know really anything to just be able to identify 
this as a list and move that Detection Slider.  

285
00:29:25,360 --> 00:29:30,080
And Equidox does the hard part. Now the next thing 
here is this table. So I want to make sure that I  

286
00:29:30,080 --> 00:29:36,000
define this as a table. And again, as you can see 
because this isn't a tagged document, that table  

287
00:29:36,000 --> 00:29:39,840
would be read just in this sort of scrambled 
mess where you have all of these different...  

288
00:29:40,560 --> 00:29:44,800
every single zone is going to be sort of read in 
its own individual way. There's really no way to  

289
00:29:44,800 --> 00:29:49,280
deviate from that reading order. So what we'll do 
is we'll just draw a single zone over the entire  

290
00:29:49,280 --> 00:29:55,760
table. And then we can press “T” on our keyboard 
to change the zone to a table. And then open  

291
00:29:55,760 --> 00:30:00,720
up the Table Editor. Now the Table Editor, once 
I've opened it up if I just move these Detection  

292
00:30:00,720 --> 00:30:06,240
Sliders around… left and right back and forth, I'm 
able to get this detection of this table structure  

293
00:30:06,240 --> 00:30:12,747
basically spot on. And the only thing else that 
I have to do is span across these years. So there  

294
00:30:12,747 --> 00:30:17,760
are four different cells there for the year 2017. 
So I'm going to span across just to make sure that  

295
00:30:17,760 --> 00:30:22,960
I don't have any blank cells or any duplicated 
data. And then also there are two rows of column  

296
00:30:22,960 --> 00:30:27,440
headers here. So what I'll do is, the default for 
Equidox is that column and row headers are set at  

297
00:30:27,440 --> 00:30:32,800
a one-to-one ratio. So I will just choose ‘2” for 
my column header. And when I check my preview,  

298
00:30:33,760 --> 00:30:38,560
you will see that we have a nice clean HTML 
table. Whereas before we had that scrambled  

299
00:30:38,560 --> 00:30:45,680
mess of all of the different cells being sort of 
read individually. So a page like this as you sort  

300
00:30:45,680 --> 00:30:50,880
of get the feel for how Equidox works. Oce you 
just press the “Reorder” button, and we take one  

301
00:30:50,880 --> 00:31:01,760
final look at the HTML preview. You can see where 
we've come from... like we had a te. We have our  

302
00:31:01,760 --> 00:31:07,040
image which is described, and we have our table 
down below. Once you get into the habit of using  

303
00:31:07,040 --> 00:31:13,360
Equidox on a frequent basis, pages like this will 
take you less than a minute to remediate. Very,  

304
00:31:13,360 --> 00:31:17,440
very simple, and straightforward once you kind of 
go through the training and have a feel for what  

305
00:31:17,440 --> 00:31:22,800
you're trying to accomplish. But with that said it 
is 2:31 and I apologize for keeping people over.  

306
00:31:22,800 --> 00:31:32,720
I do want to be respectful of everyone's time. But 
just as a final wrap up you can feel free to reach  

307
00:31:32,720 --> 00:31:40,000
out to us anytime at Equidox Sales@onixnet.com 
or our website Equidox.co. Or give us a call  

308
00:31:40,000 --> 00:31:46,160
at 800-664-9638. And then of course follow us on 
all of our social media. We would love to have a  

309
00:31:46,160 --> 00:31:52,960
chat with you and kind of talk at maybe a slower 
pace about your specific PDF-related questions  

310
00:31:52,960 --> 00:31:57,120
and how we can help. This is really just kind of 
scratching the surface. But I hope that everyone  

311
00:31:57,120 --> 00:32:14,400
found value in this webinar and I really 
appreciate everyone for attending. Thank you!