1
00:00:04,880 --> 00:00:08,560
All right, so it is just about two 
o'clock. So I think we should get started.  

2
00:00:09,360 --> 00:00:13,440
Welcome everyone to another edition 
of Equidox Webinar Wednesdays,  

3
00:00:14,080 --> 00:00:18,960
Today we're gonna be talking about accessibility 
checkers. Some of the pros, cons, and beyond.  

4
00:00:19,840 --> 00:00:24,960
As always my name is Dan Tuleta I'm a sales 
engineer here with the Equidox team. If you  

5
00:00:24,960 --> 00:00:30,720
have any questions as a follow-up to this short 
presentation or webinar today, please feel free  

6
00:00:30,720 --> 00:00:37,760
to reach out to us at EquidoxSales@Onixnet.com, 
or visit our website Equidox.co. And we're also  

7
00:00:37,760 --> 00:00:42,560
very active on LinkedIn and social media, so 
please follow us if you are on those various  

8
00:00:42,560 --> 00:00:49,840
platforms. So let's get started. Just a quick 
mention of our parent company Onix Networking.  

9
00:00:50,480 --> 00:00:57,360
So Onix is one of Google's first and most trusted 
partners. We also work closely with Amazon web  

10
00:00:57,360 --> 00:01:04,000
services. We're primarily a cloud consultancy. We 
offer a lot of different services and solutions  

11
00:01:04,000 --> 00:01:10,160
around cloud computing. And Equidox is a division 
of Onix, really a product, as we're most known  

12
00:01:10,160 --> 00:01:15,920
for our PDF remediation solution. So within 
Equidox, we do offer various services around  

13
00:01:15,920 --> 00:01:23,920
PDF accessibility, and as I said most commonly 
known for our software called Equidox. And our  

14
00:01:23,920 --> 00:01:28,160
mission is to ensure that digital information 
reaches everyone via accessibility solutions.
  

15
00:01:30,320 --> 00:01:36,160
Just a quick slide here about some of our 
clients. So we do work with government,  

16
00:01:36,160 --> 00:01:41,840
EDU, and enterprise corporations of all 
different shapes and sizes. So we offer a  

17
00:01:41,840 --> 00:01:46,640
lot of different solutions to a lot of different 
types of industries and sizes of organizations.
  

18
00:01:49,600 --> 00:01:55,040
Just a quick mention here of the 
accessibility standards and legislation. Now,  

19
00:01:55,040 --> 00:02:00,320
these are some of the most common various sets of 
standards and legislation that many people on this  

20
00:02:00,880 --> 00:02:03,760
webinar are probably familiar with, 
seeing at least some if not all of these.  

21
00:02:04,640 --> 00:02:08,000
So we just want to make sure that 
everyone is aware of some of the common  

22
00:02:08,000 --> 00:02:13,760
acronyms and terms that could be used to refer 
to when talking about digital accessibility.
  

23
00:02:16,560 --> 00:02:25,520
Now another mention here of accessibility versus 
usability. So there are big gaps between what  

24
00:02:25,520 --> 00:02:31,680
accessibility versus usability actually is. 
Now an example that I like to use for this is,  

25
00:02:31,680 --> 00:02:37,440
imagine that you're working on a document that 
is a form. And the form is asking you to fill out  

26
00:02:37,440 --> 00:02:42,640
the date. Now if you're a blind individual using 
a screen reader if that form is asking you to  

27
00:02:42,640 --> 00:02:47,280
fill in the date, which dates are they 
asking for? Is it your birth date?  

28
00:02:47,280 --> 00:02:52,720
Is it the date that you're signing it? Is it the 
date that the receiver of that form is signing it?  

29
00:02:52,720 --> 00:02:59,200
Is it the date that the office is actually filing 
that form? There are massive gaps between what can  

30
00:02:59,200 --> 00:03:04,560
actually be defined as accessible versus usable. 
While technically the form is accessible if it's  

31
00:03:04,560 --> 00:03:10,640
telling you to fill in the date, there needs to be 
additional context given to that end-user so that  

32
00:03:10,640 --> 00:03:17,600
they're able to accurately fill out the date. 
That's just one of many examples of how these  

33
00:03:17,600 --> 00:03:23,600
types of challenges can arise for different people 
with various levels of ability and disability.
  

34
00:03:28,320 --> 00:03:34,320
Just talking a bit more about 
accessibility but versus usability. So  

35
00:03:35,040 --> 00:03:41,920
another example, other examples of where these 
things can arise in PDF documents or websites.  

36
00:03:41,920 --> 00:03:46,720
For example, alt text that is present, but 
doesn't actually describe the image properly.  

37
00:03:47,440 --> 00:03:51,760
Now for these accessibility checkers which we're 
going to be talking a little bit about today,  

38
00:03:52,480 --> 00:03:57,760
they're designed to check for the presence of 
alt text. But they're not necessarily designed  

39
00:03:57,760 --> 00:04:04,320
to check for accuracy of alt text. So you could 
apply alt text to an image that says “image one”  

40
00:04:04,320 --> 00:04:10,560
or “picture one.” Now if that's an important and 
technical image that has a lot of information, how  

41
00:04:10,560 --> 00:04:16,560
is a blind user supposed to draw any information 
from an alt text that says “image one?”  

42
00:04:18,080 --> 00:04:23,360
So there are many different examples of these 
types of challenges that can arise. Another common  

43
00:04:23,360 --> 00:04:30,320
one that I like to use is, imagine a website that 
has restaurant menus on it. And oftentimes with  

44
00:04:30,320 --> 00:04:37,120
restaurant menus, they'll use different symbols, 
such as gluten-free or vegan types of options  

45
00:04:37,120 --> 00:04:44,080
to indicate exactly what types of options they 
have on that menu for those different patrons to  

46
00:04:44,080 --> 00:04:51,920
the website. So if you have, for example, a Thai 
restaurant that's offering very spicy food, they  

47
00:04:51,920 --> 00:04:58,880
might use symbols of peppers to indicate how spicy 
the food is. Now those peppers are typically going  

48
00:04:58,880 --> 00:05:05,040
to be little tiny images within the context of 
that PDF document. And if they are all described  

49
00:05:05,040 --> 00:05:10,560
as “pepper” “pepper” “pepper” “pepper,” how is an 
end-user supposed to know what that is referring  

50
00:05:10,560 --> 00:05:15,360
to? That could be a mistake in the document. What 
are these peppers all about? Is this document  

51
00:05:15,360 --> 00:05:20,800
just a plate of peppers? Or is this meal just a 
plate of peppers? So in those types of instances,  

52
00:05:20,800 --> 00:05:25,600
technically those peppers could be technically 
accessible, but not usable for an end-user  

53
00:05:25,600 --> 00:05:30,800
who's not aware that the pepper symbol is an 
indication of how spicy or how hot that food is. 

54
00:05:32,480 --> 00:05:39,360
Other examples might be undefined acronyms. 
So for example internally within our team when  

55
00:05:39,360 --> 00:05:43,520
we're talking on instant messenger and sending 
little emails back and forth to each other,  

56
00:05:43,520 --> 00:05:51,280
sometimes we will use the acronym “EQ” to refer 
to Equidox. Now if you're using a screen-reader  

57
00:05:51,280 --> 00:05:57,840
and there's references in a document to Equidox 
as “EQ,” a screen reader does not know that EQ  

58
00:05:57,840 --> 00:06:06,000
means Equidox. And it's going to pronounce “ECK” 
or “EEEK.” So that is very useless to an end-user  

59
00:06:06,000 --> 00:06:10,800
who's not familiar enough with our internal 
communication and how we talk amongst ourselves as  

60
00:06:10,800 --> 00:06:18,000
a team to actually be able to draw any information 
from the word “ECK” or “EEK.” So it's important to  

61
00:06:18,000 --> 00:06:23,200
make sure that you are properly spelling out 
and making reference to these acronyms and  

62
00:06:23,200 --> 00:06:28,640
using plain English to describe these types of 
shortcuts that we use when we're communicating.  

63
00:06:30,560 --> 00:06:36,480
I've already mentioned form fields with proper 
or with poorly defined labels. So for example,  

64
00:06:37,120 --> 00:06:42,000
you know, if you're asking for (going back to 
the date example) there's other problems that  

65
00:06:42,000 --> 00:06:46,960
can arise when asking for a date. Which format do 
you want the date to be entered in? You have to  

66
00:06:46,960 --> 00:06:53,280
indicate in explicit detail as to, do you want the 
days first then the month then the year? Do you  

67
00:06:53,280 --> 00:06:58,640
want four digits for the year or do you want two 
digits for the year? So depending on, you know,  

68
00:06:58,640 --> 00:07:03,040
which country you're in, what the document is for, 
there can be different ways of actually entering  

69
00:07:03,040 --> 00:07:07,920
dates. But if that information is not available 
to end-users who are interacting with the document  

70
00:07:07,920 --> 00:07:12,800
using a screen reader, that can cause a lot 
of problems and a lot of challenges where they  

71
00:07:12,800 --> 00:07:18,080
are going to be entering dates in the improper 
format. Which can of course lead to confusion.  

72
00:07:18,880 --> 00:07:25,200
So that's another thing to consider when you are 
remediating documents such as forms. Making sure  

73
00:07:25,200 --> 00:07:31,440
that all of those fields are properly labeled.
Another challenge is the language attributes. Now  

74
00:07:32,240 --> 00:07:37,120
words can be pronounced differently depending on 
the language attribute that is applied so consider  

75
00:07:38,560 --> 00:07:44,000
a name like “George.” With the incorrect language 
attribute set, that could be pronounced as  

76
00:07:45,360 --> 00:07:50,640
or something completely different. That doesn't 
make any sense to an end-user. Can lead to a lot  

77
00:07:50,640 --> 00:07:55,120
of confusion. So there's many things that you can 
consider when you're setting up your document in  

78
00:07:55,120 --> 00:08:01,040
terms of making it not just the bare minimum 
for accessibility, but actually going beyond  

79
00:08:01,680 --> 00:08:05,200
and setting it up so that it's actually 
fully usable for those end users.
  

80
00:08:07,920 --> 00:08:14,320
Now here is a list of some of the most common 
PDF accessibility checkers. So these are really  

81
00:08:14,320 --> 00:08:20,160
designed to analyze documents based on 
very specific and rigid sets of criteria  

82
00:08:20,160 --> 00:08:26,320
to determine the document's accessibility. And to 
find and locate the errors within those documents.  

83
00:08:26,320 --> 00:08:31,920
However, there's a lot of things that these are 
not able to actually check for. So just getting  

84
00:08:31,920 --> 00:08:37,520
a passing grade from an accessibility checker 
such as Adobe's accessibility checker, or the  

85
00:08:37,520 --> 00:08:43,040
PAC-3 checker does not actually indicate that 
the document is fully accessible or fully usable.  

86
00:08:43,040 --> 00:08:48,400
I'm so often asked when I'm talking to different 
clients “How do we know when the document is  

87
00:08:48,400 --> 00:08:55,520
accessible?” And these accessibility checkers 
are very popular and they should be used in  

88
00:08:55,520 --> 00:09:01,200
your remediation workflow to check the validity 
of the structures that you're creating. However  

89
00:09:01,200 --> 00:09:08,880
you have to take it a step further to really 
ensure total and full usability. So just a quick  

90
00:09:08,880 --> 00:09:13,360
mention of these accessibility checkers and some 
of the things that they can and cannot check for.  

91
00:09:14,400 --> 00:09:20,560
So there's many things that they're incapable 
of looking for. So for example, as I said before  

92
00:09:20,560 --> 00:09:26,880
you can have an alt text that says “image one,” 
but the accuracy of that alt text is not able to  

93
00:09:26,880 --> 00:09:31,280
be checked for by automated accessibility 
checkers. That is up to the remediator to  

94
00:09:31,280 --> 00:09:37,120
make sure that the alt text is accurate. The 
same goes for heading structure, the URLs,  

95
00:09:37,120 --> 00:09:43,840
table summaries, tooltips on form documents, as 
well as reading order. Automated accessibility  

96
00:09:43,840 --> 00:09:49,280
checkers are not able to determine the nuances of 
reading order because all PDFs can be different  

97
00:09:49,280 --> 00:09:54,960
and unique and have completely different ways 
that they are designed to be read. So these are  

98
00:09:54,960 --> 00:10:00,320
things where accessibility checkers are looking 
for certain things that meet the criteria that  

99
00:10:00,320 --> 00:10:05,680
they're designed to check for, but they're not at 
they're not able to find everything that can cause  

100
00:10:07,280 --> 00:10:11,200
very very serious usability errors later 
down the line for those end users.
  

101
00:10:15,040 --> 00:10:21,200
Now here's a list of common screen readers. 
So screen reading tools are what the  

102
00:10:22,320 --> 00:10:27,440
majority of blind users are using to interact 
with digital content. So these are the most  

103
00:10:27,440 --> 00:10:34,000
common and most broadly used screen readers. 
I do want to mention that NVDA is free and  

104
00:10:34,000 --> 00:10:39,600
open source. As part of our services offering 
where we do PDF remediation for our clients,  

105
00:10:40,560 --> 00:10:48,000
the final step in the validation workflow is to 
actually use NVDA to interact with the document  

106
00:10:48,000 --> 00:10:52,400
and sort of replicate how a blind user would be 
working with that document. Just to make sure  

107
00:10:52,400 --> 00:10:57,520
that the document is in fact fully usable. So 
if you're ever interested in testing out some  

108
00:10:57,520 --> 00:11:01,840
screen readers and seeing how they work, and 
how they interact with your digital content,  

109
00:11:02,480 --> 00:11:05,840
definitely check out NVDA. It is 
free to download and free to use.
  

110
00:11:08,240 --> 00:11:14,800
Now, Equidox, as part of our software 
package, the Equidox Preview panel.  

111
00:11:15,360 --> 00:11:21,120
This is a very important part of our software 
because what the Equidox Preview panel does is,  

112
00:11:21,120 --> 00:11:26,800
it gives you an HTML rendering of the page 
that you're currently working on. And these  

113
00:11:26,800 --> 00:11:31,760
HTML pages are updated in real-time as you are 
working through and remediating the document.  

114
00:11:32,800 --> 00:11:37,760
And the HTML preview is of course usable 
with accessibility checkers, and it's also  

115
00:11:37,760 --> 00:11:42,800
usable for screen reading technology as well. 
So it's a great way of checking your work at the  

116
00:11:42,800 --> 00:11:48,560
point of remediation, so that the remediator, 
even if they are not an accessibility expert,  

117
00:11:48,560 --> 00:11:53,360
they're able to see the structure that they're 
building, and they're able to check the accuracy  

118
00:11:53,360 --> 00:11:59,680
of the content that they're working on. Because 
they get feedback in HTML before they export the  

119
00:11:59,680 --> 00:12:04,560
document. And we're going to work on an example 
and go through some of the steps of how you can  

120
00:12:04,560 --> 00:12:12,160
use the HTML preview to assist you as you are 
working through documents. Now the final step  

121
00:12:12,160 --> 00:12:18,080
when you're done working on documents in Equidox 
is of course outputting or exporting the document.  

122
00:12:18,080 --> 00:12:24,960
So when you're exporting documents from 
Equidox, there are a series of output checks  

123
00:12:24,960 --> 00:12:31,280
that are being applied to that document. And the 
warning messages will arise if you have mistakes,  

124
00:12:31,280 --> 00:12:36,720
structural mistakes, in your document, that can be 
fixed and you can go back into Equidox... into the  

125
00:12:36,720 --> 00:12:42,880
page that those issues were located on. You can 
go back and fix those and re-export the document.  

126
00:12:42,880 --> 00:12:46,640
Now, this is not an exhaustive list of 
all of the things that we're checking for,  

127
00:12:46,640 --> 00:12:51,840
but some of the things that you can find are: 
missing all text, multiple heading levels,  

128
00:12:52,400 --> 00:12:57,040
multiple heading level ones, or illogical 
heading structure. If you have URLs missing  

129
00:12:57,040 --> 00:13:02,800
from your links, if you have form fields missing 
tooltips, if table summaries are not there,  

130
00:13:02,800 --> 00:13:07,840
as well as untagged pages and a number of other 
checks that are being applied. So you have this  

131
00:13:07,840 --> 00:13:12,240
as sort of your backup as you're remediating 
a document. When you export that document, you  

132
00:13:12,240 --> 00:13:17,200
will get feedback from Equidox that it's applying 
some of these checks to make sure that you are not  

133
00:13:18,080 --> 00:13:23,840
making glaring mistakes in how you've structured 
your document. However, you're still free to use  

134
00:13:23,840 --> 00:13:28,880
other third-party validation tools, as well 
as screen readers to finish off the validation  

135
00:13:28,880 --> 00:13:34,640
process. I also want to mention that we do 
have more information in an accessibility blog,  

136
00:13:35,360 --> 00:13:38,640
and so when we send out this slide deck 
to everyone that's on the call today,  

137
00:13:39,520 --> 00:13:43,760
you'll be able to click on this link here 
and open up the blog post and have a look  

138
00:13:43,760 --> 00:13:49,040
through. There's a lot of other resources on our 
website that you are free to browse. So there is  

139
00:13:49,040 --> 00:13:54,720
a link to a blog post about avoiding accessibility 
errors. So check that out when you get a moment.
  

140
00:13:57,120 --> 00:14:01,760
So just to reiterate what are some of 
the things that require manual checks.  

141
00:14:01,760 --> 00:14:06,400
So the accuracy of alt text, the accuracy 
of the heading structure, the URLs,  

142
00:14:06,400 --> 00:14:11,440
the table summary, the tooltips, and reading 
order. Now, these are things that you can check  

143
00:14:11,440 --> 00:14:17,760
in Equidox while you're using the HTML preview. 
So that's one of the great benefits of Equidox, is  

144
00:14:17,760 --> 00:14:22,640
you're taking things beyond just bare minimum 
accessibility quote-unquote “accessibility,”  

145
00:14:22,640 --> 00:14:27,440
and you're actually validating for accuracy and 
checking your work as you move through to make  

146
00:14:27,440 --> 00:14:34,160
sure that the document is in fact fully usable. 
Which is what's most important. So I'm gonna at  

147
00:14:34,160 --> 00:14:38,160
this moment, I'm gonna actually back out of the 
slide deck, and we're gonna go into Equidox.  

148
00:14:38,800 --> 00:14:43,760
And we will take a look at an example. 
 
So what I've done is I've imported a  

149
00:14:43,760 --> 00:14:49,600
document. Just a simple one-page document. And 
I have intentionally sort of made a mess of my  

150
00:14:49,600 --> 00:14:54,640
remediation effort here. If I go into the 
document. I have structured things poorly  

151
00:14:56,080 --> 00:15:00,240
and that's the intent of this, is to show you 
what some of these output warnings will look like,  

152
00:15:00,240 --> 00:15:06,160
and how they can be fixed in Equidox. So keep in 
mind that I've already, I've already worked on  

153
00:15:06,160 --> 00:15:11,280
this document for a few minutes, and I've actually 
improperly set things up. So when I close out of  

154
00:15:11,280 --> 00:15:16,800
the document and if I go to the Output tab, 
when I take this document out of Equidox,  

155
00:15:16,800 --> 00:15:23,760
and I hit “Generate PDF,” what I will see 
is a series of warnings that are popping up.  

156
00:15:25,360 --> 00:15:29,760
And these warnings are just letting me know that 
hey you've got some problems with your document.  

157
00:15:29,760 --> 00:15:34,320
So make sure you go back and fix these before 
you post or distribute this document. Now some  

158
00:15:34,320 --> 00:15:40,640
of these warnings are related to the images. So, 
missing alt text, I have a missing table summary,  

159
00:15:40,640 --> 00:15:47,760
I have an improper merge of two zones, I have OCR 
that I have not actually run an OCR process on,  

160
00:15:48,640 --> 00:15:52,400
and so there's just a number of checks that are 
being applied which I can quickly go back and  

161
00:15:52,400 --> 00:15:57,520
clean up. So keep in mind that those warnings 
are present on my first attempt to export this  

162
00:15:57,520 --> 00:16:01,520
document. But before I post this to the website, 
I want to go back and make sure that I address  

163
00:16:01,520 --> 00:16:08,000
all of those error messages that I found. Now 
a big part of Equidox is of course that HTML  

164
00:16:08,000 --> 00:16:13,840
preview which I mentioned before during the 
slide deck. If I open up the Preview panel,  

165
00:16:13,840 --> 00:16:18,800
which is this button here. If I press the 
Preview, what this will do is open a separate tab.  

166
00:16:18,800 --> 00:16:23,440
And it will give me that HTML rendering of the 
structure that I'm currently building in Equidox.  

167
00:16:24,080 --> 00:16:29,520
Now I can see some glaring issues here with 
my HTML preview right away. First of all,  

168
00:16:29,520 --> 00:16:35,280
my reading order is incorrect, my table is at the 
very bottom of the reading order, when in fact it  

169
00:16:36,560 --> 00:16:41,360
should be followed directly by this “for more 
information” with the links. I know that my links  

170
00:16:41,360 --> 00:16:46,160
are incorrect, they're not going to the correct 
destination. I got that warning message letting  

171
00:16:46,160 --> 00:16:52,080
me know I'm also missing list structure for this 
very complicated-looking nested list. My headings  

172
00:16:52,080 --> 00:16:56,720
are all messed up, and I'm missing alt text for 
my images. So there's a number of things here  

173
00:16:56,720 --> 00:17:01,040
that I need to fix. But I'm going to be able 
to check all of this again in my HTML preview  

174
00:17:01,040 --> 00:17:06,240
as I work through and make these corrections. 
Now starting at the very top of the document,  

175
00:17:06,240 --> 00:17:11,680
this PDF sample document text that I'm looking at 
here, is actually an image. And I decided that I'm  

176
00:17:11,680 --> 00:17:16,960
going to OCR this image so that I can actually 
extract the actual text from it so I've drawn an  

177
00:17:16,960 --> 00:17:23,120
OCR zone around that piece of content. But I have 
not actually converted it into text. So when I hit  

178
00:17:23,120 --> 00:17:28,560
“Convert to Text” the OCR process will run and I 
can actually convert that into something that is  

179
00:17:28,560 --> 00:17:33,840
searchable, selectable, and usable. So that will 
correct the first error, which was that OCR issue.  

180
00:17:34,480 --> 00:17:40,800
Now the next error that I'm seeing is my headings. 
So we need proper and logical heading structure  

181
00:17:40,800 --> 00:17:47,280
in our PDF documents. So just to start here, the 
first heading on the page is a heading level two  

182
00:17:47,920 --> 00:17:52,960
which is incorrect. In fact, it says heading level 
one right in the text itself. We wanna make sure  

183
00:17:52,960 --> 00:17:57,280
that we're setting this to the appropriate 
heading level, and also it's a requirement  

184
00:17:57,280 --> 00:18:02,240
in terms of accessibility to make sure that all 
headings or all documents have at least a heading  

185
00:18:02,240 --> 00:18:07,760
level one. That's a requirement. So what we'll 
do here is change this from a heading level two  

186
00:18:07,760 --> 00:18:12,400
to a heading level one, by simply tapping “1” 
on my keyboard and using my keyboard shortcuts.  

187
00:18:13,840 --> 00:18:20,560
The next issue here is I have this text zone 
which I've improperly merged. I've hit this merge  

188
00:18:20,560 --> 00:18:26,080
checkbox inadvertently, so that is attempting 
to merge this text zone with another zone that  

189
00:18:26,080 --> 00:18:31,200
doesn't actually exist. So if I take that merge 
checkbox off, that will clean up another one of  

190
00:18:31,200 --> 00:18:37,680
those errors where I had an improper merge that 
was going to attempt to merge this text with  

191
00:18:37,680 --> 00:18:42,640
another piece of text that doesn't actually exist. 
So taking that merge checkbox off, we'll clean up  

192
00:18:42,640 --> 00:18:48,640
that next error. Moving down the list here, I have 
another heading level two set, which is fine, so  

193
00:18:49,200 --> 00:18:53,920
this is in fact a heading level two, but if you 
notice my next heading is a heading level four.  

194
00:18:53,920 --> 00:18:59,120
So I've jumped from heading level two to heading 
level four, which is illogical. So I need to reset  

195
00:18:59,120 --> 00:19:03,440
this heading to a heading level three by tapping 
“3” on my keyboard. And I'll do the same thing  

196
00:19:03,440 --> 00:19:08,640
down here where I have another heading level four. 
So I will tap “3” on my keyboard. So then I now  

197
00:19:08,640 --> 00:19:13,760
have a heading level one, a heading level two, 
and then two heading level threes on this page.  

198
00:19:16,080 --> 00:19:20,800
The next thing I want to address are these 
images. Now I have two images on this page,  

199
00:19:20,800 --> 00:19:27,200
and neither of them has been given any alt 
description as of yet. So I'm going to mark this  

200
00:19:27,200 --> 00:19:30,880
image here as decorative. And I'm 
going to “artifact” i. This is just a  

201
00:19:31,440 --> 00:19:36,720
sort of cartoon silhouette of a skyline. And 
this is just there for aesthetic, you know,  

202
00:19:36,720 --> 00:19:41,840
design purposes. It's really not offering 
any information or value to the content  

203
00:19:42,800 --> 00:19:46,880
on the page. So what I'm going to do is, 
just actually hit backspace on my keyboard  

204
00:19:46,880 --> 00:19:54,240
and that will artifact the image and remove my 
requirement of actually applying alt text to it.  

205
00:19:55,440 --> 00:20:01,520
The next image down here is our little mascot... 
we like to call him Equidog. But I will actually  

206
00:20:01,520 --> 00:20:08,800
type in a description for this image. And my 
description will be “black and white dog holding  

207
00:20:08,800 --> 00:20:15,520
a briefcase with an Equidox logo.” So I'm 
taking the time to actually describe that  

208
00:20:15,520 --> 00:20:21,600
image accurately, rather than just putting in 
“image one” or “dot dot” or “one, two, three.”  

209
00:20:22,320 --> 00:20:27,040
Again, these accessibility checkers, they are 
only able to check for the presence of alt text.  

210
00:20:27,040 --> 00:20:31,760
They have no idea if it is accurate or not. So 
that is up to the remediator as you're walking  

211
00:20:31,760 --> 00:20:36,640
through documents, to make sure that you are 
seeing images, understanding the context for  

212
00:20:36,640 --> 00:20:42,960
which they fit in the page, and applying accurate 
and useful alt text to them. Alternatively, if the  

213
00:20:42,960 --> 00:20:47,520
image is decorative, as I've determined that this 
image was, you can artifact it and then you do not  

214
00:20:47,520 --> 00:20:55,280
have to apply alt text to it. Another issue that I 
have on this page is, I have this nested list here  

215
00:20:55,280 --> 00:21:02,000
which I have failed to actually remediate. If we 
go back to the HTML preview, this is how that list  

216
00:21:02,000 --> 00:21:08,720
is currently rendering in HTML. Which is just a 
very strange-looking run-on paragraph. It's not  

217
00:21:08,720 --> 00:21:15,520
going to be navigable for end-users, it's going to 
be very very cumbersome as they try to understand  

218
00:21:15,520 --> 00:21:21,200
the relationship between all of these different 
list items and nested list items. So this does not  

219
00:21:21,200 --> 00:21:26,800
belong in a text zone. So what I'll do is I will 
hit “L” on my keyboard to change the zone type to  

220
00:21:26,800 --> 00:21:32,080
a list. And then I have a List Detector slider 
that will appear. And if I just move this over,  

221
00:21:32,080 --> 00:21:37,360
what Equidox will do is it will use its artificial 
intelligence to analyze this list, and it will  

222
00:21:37,360 --> 00:21:44,000
find all of the nested lists and the list items 
within it. So now I've actually got proper list  

223
00:21:44,000 --> 00:21:50,240
structure defined, whereas before I had just 
a very convoluted-looking paragraph of text.  

224
00:21:52,240 --> 00:21:56,320
Down below here, I have a table, of course, 
but my table is missing a table summary.  

225
00:21:56,880 --> 00:22:02,320
So I've already remediated this table. I can go 
back in and do it over. We can always use our  

226
00:22:02,320 --> 00:22:08,080
Detection sliders to move our sliders around 
to redefine our rows and columns. And then  

227
00:22:08,080 --> 00:22:14,640
if we have things, things such as spanning, for 
example, the years 2017 and 18 need to span across  

228
00:22:14,640 --> 00:22:21,760
the four columns that belong underneath them. So 
if I hold SHIFT and select in these various cells,  

229
00:22:21,760 --> 00:22:26,240
and press “S” on my keyboard, and do the same 
thing, here pressing “S,” that will span across.  

230
00:22:26,800 --> 00:22:31,120
But I need my summary to be turned on. 
So for example, this checkbox here,  

231
00:22:32,080 --> 00:22:38,240
Equidox will automatically write the table summary 
for you based on how you have laid out all of the  

232
00:22:38,240 --> 00:22:44,400
gridlines within your table. And in this case, I 
have two sets of column headers, so if I change  

233
00:22:44,400 --> 00:22:50,800
my column header from “1” to “2,” my table summary 
will automatically update with that information.  

234
00:22:50,800 --> 00:22:55,120
So my table summary can be programmatically 
written for me by Equidox. So there's really  

235
00:22:55,120 --> 00:23:00,720
no excuse to leave the table summary blank. So 
by going back in and turning my auto summarize  

236
00:23:00,720 --> 00:23:06,960
feature on, I've taken care of that requirement 
to provide a table summary. So now I just have to  

237
00:23:06,960 --> 00:23:13,360
close out of the table after saving it. And that 
will return me to the Page Editor. Now down below,  

238
00:23:13,360 --> 00:23:20,640
the one remaining issue on this page is this 
link here, which I have improperly set a URL for  

239
00:23:21,840 --> 00:23:26,960
intentionally. Here I've set this to 
link to page 33 in this document. Well,  

240
00:23:26,960 --> 00:23:32,640
there is no page 33 in this document. This is 
a single-page document, so this is an error to  

241
00:23:32,640 --> 00:23:37,840
have someone going to a destination that does not 
actually exist. So what I can do to fix this, is I  

242
00:23:37,840 --> 00:23:48,080
can actually just update the anchor for this link 
by typing in https:// and then www.Equidox.co.  

243
00:23:48,800 --> 00:23:53,920
And then that will actually lead me to the 
appropriate link. The appropriate destination  

244
00:23:53,920 --> 00:23:58,960
through that link. So now that I've made 
all of those types of corrections, let's  

245
00:23:58,960 --> 00:24:04,400
take another look at the HTML preview. And when 
I go back to the HTML preview, I will see that  

246
00:24:04,960 --> 00:24:09,040
I've got some different things happening here. I 
still have one issue which is the reading order.  

247
00:24:09,600 --> 00:24:14,240
But I can see that I have my heading levels 
defined. My headings are appearing in bolder  

248
00:24:14,240 --> 00:24:19,680
and larger font. Here is that nested list which 
I previously did not have any list structure for,  

249
00:24:20,240 --> 00:24:24,080
but now I can see that I actually have a 
real nested list that will actually be usable  

250
00:24:24,080 --> 00:24:30,240
by end-users who are interacting with a screen 
reader. I have my links down here. If I click on  

251
00:24:30,240 --> 00:24:36,880
that link, it will actually take me to our website 
Equidox.co. So that will actually... Now I can  

252
00:24:36,880 --> 00:24:40,800
confirm the accuracy of that link by actually 
clicking on it and making sure that it does  

253
00:24:40,800 --> 00:24:47,760
in fact arrive at the appropriate destination. 
And down below here I have my table, which I know  

254
00:24:47,760 --> 00:24:52,640
has a table summary because I've actually turned 
that auto-summarize feature on. Now the last thing  

255
00:24:52,640 --> 00:24:57,280
to do is clean up my reading order. And I can do 
that by just simply pressing the “Reorder” button.  

256
00:24:57,280 --> 00:25:02,400
And now we'll reorder this page in a top to bottom 
left to right reading order. And maybe you want to  

257
00:25:02,400 --> 00:25:07,520
make one adjustment to the image. Perhaps you want 
Equidog to be read at the very end of the page.  

258
00:25:07,520 --> 00:25:12,560
Well, let's just change its number. We'll put a 
1 in front of 13 and make it 113, and then when I  

259
00:25:12,560 --> 00:25:18,640
go back to the Preview, it'll be read at the very 
bottom where we think it belongs. But now my table  

260
00:25:18,640 --> 00:25:24,320
is following directly behind the heading that 
is indicating that there is a table. My list is  

261
00:25:24,320 --> 00:25:28,240
directly following my heading that says that 
there's a list, so I'm happy with my reading  

262
00:25:28,240 --> 00:25:34,080
order. Here is that OCR result that I've run 
earlier. I'm using this HTML preview to confirm  

263
00:25:34,080 --> 00:25:38,480
the accuracy and the structure that I've built 
in this document. So you can see the dramatic  

264
00:25:38,480 --> 00:25:44,080
change in how this currently looks versus when 
we began. Where we had issues with everything  

265
00:25:44,080 --> 00:25:50,000
under the sun. I've remediated this page about 
as poorly as you can possibly remediate it,  

266
00:25:50,000 --> 00:25:55,440
but very quickly I'm able to go back in and clean 
things up. Now that I've cleaned everything up on  

267
00:25:55,440 --> 00:26:01,760
this page and I'm happy with it, what I'll do is 
I will save this layout, and then I will X out of  

268
00:26:01,760 --> 00:26:07,120
this document. And I can return to the Output 
tab. So once I return to the Output tab again,  

269
00:26:07,120 --> 00:26:12,880
I just select “PDF,” and I can generate this 
new PDF document. And this time it will come out  

270
00:26:12,880 --> 00:26:18,880
without any of the error messages. So we remember 
before the previous version had error messages  

271
00:26:18,880 --> 00:26:23,360
that were populating down below. This version does 
not have any errors, because I've gone back in and  

272
00:26:23,360 --> 00:26:29,200
corrected them all. And now when I open up the 
PDF document from the link provided, I can see  

273
00:26:29,200 --> 00:26:34,560
nothing visual changes about the document in any 
way, but this will all be accurate, and usable,  

274
00:26:34,560 --> 00:26:40,800
and accessible based on that remediation that I've 
applied. And again, using that HTML preview to  

275
00:26:40,800 --> 00:26:46,400
check the accuracy and the validity of that page 
that you're working on. So this is going a step  

276
00:26:46,400 --> 00:26:51,360
beyond just the automated accessibility checkers. 
You're checking it at the page level as you work  

277
00:26:51,360 --> 00:26:55,920
through the document. And you're knowing that, in 
fact, you have set the appropriate reading order,  

278
00:26:55,920 --> 00:27:01,040
you have tagged your images with descriptions, you 
know that the links are working, you can actually  

279
00:27:01,040 --> 00:27:04,720
click on them to confirm. So there's a number 
of different things that you're doing with that  

280
00:27:04,720 --> 00:27:11,840
HTML preview to take your remediation process well 
beyond just the automated accessibility checkers.  

281
00:27:12,720 --> 00:27:17,040
Now one other thing I'll mention is when you do 
export versions of a document out of Equidox,  

282
00:27:17,040 --> 00:27:22,880
if you go to the History tab, we also give you 
a list of the warnings. So when I exported this  

283
00:27:22,880 --> 00:27:28,800
12 minutes ago with my first attempt. I did have 
eight warnings. And all of those warnings fell on  

284
00:27:28,800 --> 00:27:34,720
page one. So this is a nice little way of kind 
of consolidating the history of the document.  

285
00:27:34,720 --> 00:27:40,480
If it's a very long or very complex document, if 
you're exporting it and you have error messages,  

286
00:27:40,480 --> 00:27:44,800
you'll be able to go directly to the location 
of those errors because we give you a list of  

287
00:27:44,800 --> 00:27:49,440
where those errors are located in the description 
as to what that error is. So you have an idea on  

288
00:27:49,440 --> 00:27:54,800
how to go back and fix it so this is another 
helpful tool within Equidox. To just be able  

289
00:27:54,800 --> 00:27:59,120
to check out the old version of the document and 
make sure that you are in fact addressing all of  

290
00:27:59,120 --> 00:28:03,600
these errors. In this case, they all happen to 
be on page one, so it's pretty straightforward  

291
00:28:03,600 --> 00:28:07,760
just going back to page one and cleaning up 
all of those glaring mistakes that I made.  

292
00:28:09,680 --> 00:28:15,280
Okay, so that will sort of commence the 
demonstration portion on how we use the  

293
00:28:15,280 --> 00:28:24,080
HTML preview and our output checks. So with that 
said I want to return back to the webinar here  

294
00:28:24,080 --> 00:28:30,080
just to wrap things up on the slide deck 
here. Now again, we do appreciate everyone  

295
00:28:30,080 --> 00:28:36,160
taking the time out of their Wednesday to attend 
the webinar and chat with us. So if you have any  

296
00:28:36,160 --> 00:28:42,080
questions or if you'd like to see a more tailored 
demonstration too, with documents that maybe are  

297
00:28:42,080 --> 00:28:46,160
more relevant to you… If you'd like to just 
learn more about Equidox, please feel free  

298
00:28:46,160 --> 00:28:53,520
to reach out to us at EquidoxSales@Onixnet.com or 
through our website, Equidox.co. And like I said,  

299
00:28:53,520 --> 00:29:00,160
we are active on LinkedIn and we do have a website 
that has a ton of resources for learning new  

300
00:29:00,160 --> 00:29:06,880
things about accessibility. Talking more about 
accessibility checkers and PDFs and all of our  

301
00:29:06,880 --> 00:29:13,280
different services that we can offer and help 
your organization with. So with that said, thank  

302
00:29:13,280 --> 00:29:17,040
you very much everyone for attending. And Tammy, 
were there any questions that we need to address? 

303
00:29:17,680 --> 00:29:20,480
[Tammy] No there are only a few 
and I believe I have answered them. 

304
00:29:20,480 --> 00:29:25,440
[Dan] Okay great! Well thank you very much 
again everyone, and we look forward to  

305
00:29:25,440 --> 00:29:39,840
seeing you again next month for our next 
edition of Equidox Webinar Wednesdays!