1
00:00:03,249 --> 00:00:08,160
[Dan Tuleta] Okay so I'm showing it that it's 
two o'clock. So I think we should get started.  

2
00:00:08,160 --> 00:00:14,480
Thank you everyone for joining us again for 
another rendition of Equidox Webinar Wednesdays.  

3
00:00:15,440 --> 00:00:19,760
This month we are talking about Going 
Beyond the Checklists and trying to simplify  

4
00:00:19,760 --> 00:00:26,560
WCAG. As always my name is Dan Tuleta and I'm a 
sales engineer here with the Equidox team. If you  

5
00:00:26,560 --> 00:00:32,080
have any questions related to this webinar or if 
you would like to have an additional consultation  

6
00:00:32,080 --> 00:00:37,120
or meeting with us to discuss your documents... 
your accessibility challenges... please feel free  

7
00:00:37,120 --> 00:00:45,360
to reach out to us at EquidoxSales@Onixnet.com. 
We also have our website www.Equidox.co and we're  

8
00:00:45,360 --> 00:00:50,160
very active on all of the social media networks. 
So please feel free to connect with us there.  

9
00:00:52,320 --> 00:00:57,840
Now before we get before we begin, I just want 
to mention our parent company Onix Networking.  

10
00:00:57,840 --> 00:01:02,320
Onix is headquartered in Cleveland, Ohio 
and we are primarily known as a pro... as  

11
00:01:02,320 --> 00:01:08,080
a premier partner of Google. So we are a cloud 
consultancy that kind of, across the board,  

12
00:01:08,080 --> 00:01:14,000
offer a lot of different cloud consulting, cloud 
consultancy services, and solutions. And Equidox  

13
00:01:14,000 --> 00:01:18,720
is a division within Onix. So our mission 
here at Equidox is to ensure that digital  

14
00:01:18,720 --> 00:01:25,040
information reaches everyone via accessibility 
solutions. We have a PDF remediation software  

15
00:01:25,040 --> 00:01:30,240
called Equidox and we also offer a variety 
of services primarily around PDF documents.

16
00:01:33,840 --> 00:01:38,080
So just a quick slide here to mention some 
of the organizations that we work with.  

17
00:01:38,800 --> 00:01:43,680
We cross over many different verticals and we 
work with many different sizes of organizations.  

18
00:01:43,680 --> 00:01:49,120
So no matter how big or small your company or 
organization is, we are here to help. So please  

19
00:01:49,120 --> 00:01:53,840
feel free again to reach out to us to connect 
and talk more about your accessibility needs.

20
00:01:56,160 --> 00:02:01,760
Now before... if you've joined us before you know 
that I like to talk for the duration of these  

21
00:02:01,760 --> 00:02:05,920
webinars every month. So we're gonna give you a 
break from my voice for a few minutes here and I'd  

22
00:02:05,920 --> 00:02:12,000
like to introduce our Director of Accessibility 
Ryan Pugh. Ryan directs our Equidox remediation  

23
00:02:12,000 --> 00:02:16,800
team. He's also an accessibility consultant 
and he can provide a lot of services around  

24
00:02:16,800 --> 00:02:23,040
website testing, document remediation 
expertise, and a number of other areas  

25
00:02:23,040 --> 00:02:26,960
within digital accessibility. Previously 
of the National Federation of the Blind,  

26
00:02:26,960 --> 00:02:32,640
Ryan was an Access Technology Analyst for many 
years. And so Ryan, I'm gonna just hand it over  

27
00:02:32,640 --> 00:02:35,840
to you to kind of go through these different 
topics that we're going to talk about today.

28
00:02:35,840 --> 00:02:41,520
[Ryan Pugh]  

29
00:02:41,520 --> 00:02:42,400
Great, thank you, Dan.

30
00:02:45,840 --> 00:02:52,320
When we're talking about WCAG and 
creating accessibility on your content,  

31
00:02:53,280 --> 00:02:59,920
your goal should always be to create an equivalent 
experience when possible. Whether that's creating  

32
00:02:59,920 --> 00:03:04,800
something brand new from scratch, a new document 
or resource, or remediating one for accessibility.  

33
00:03:06,720 --> 00:03:12,560
The WCAG guidelines tell us that all users should 
have access to the same information. And that that  

34
00:03:12,560 --> 00:03:20,240
experience should be the same. That's not always 
possible. I have here an example of the Mona Lisa.  

35
00:03:21,680 --> 00:03:28,320
And as marketing people and content creators 
can tell us, a lot of time and effort is spent  

36
00:03:28,960 --> 00:03:33,520
crafting an image or a document making 
it eye-catching and intuitive... clear...  

37
00:03:33,520 --> 00:03:39,120
easy-to-use... memorable... persuasive. 
When you're engaged in writing, books  

38
00:03:39,120 --> 00:03:44,880
are drafted redrafted, proofread, drafted 
again, rewritten for clarity, for density.  

39
00:03:45,520 --> 00:03:51,600
If you're creating forms or questionnaires, we 
almost always see at the beginning “this form or  

40
00:03:51,600 --> 00:03:57,600
survey will take two minutes or less.” There is 
clear intent that it be clean, easy, and usable.  

41
00:04:00,320 --> 00:04:02,320
When you're deciding on a remediation approach,  

42
00:04:02,320 --> 00:04:06,800
you should be considering all of those factors 
into how you're making your content accessible.

43
00:04:08,960 --> 00:04:13,120
It's not always fully possible to create 
an equivalent experience. It's difficult to  

44
00:04:13,120 --> 00:04:15,760
evoke an emotional response through alt text.

45
00:04:18,080 --> 00:04:22,240
Or to communicate human emotions on a 
face through the written word alone.  

46
00:04:22,800 --> 00:04:32,800
I've seen large studies that have been conducted 
and in-depth analysis of this particular painting,  

47
00:04:32,800 --> 00:04:40,240
which have concluded that Mona Lisa’s smile is 83 
percent, happy nine percent disgusted, six percent  

48
00:04:40,240 --> 00:04:45,360
fearful, two percent bored. I'm not certain 
where those numbers have come from exactly. I  

49
00:04:45,360 --> 00:04:50,320
don't know how they've made that determination. 
When I look at this I see a fancy piece of art.

50
00:04:54,320 --> 00:05:00,000
If the intent of your usage of 
this particular picture is to  

51
00:05:00,000 --> 00:05:04,000
communicate the complexities of human 
emotions, you should be considering  

52
00:05:06,000 --> 00:05:10,240
when writing your alt text for the image 
or the structure surrounding the image,  

53
00:05:11,280 --> 00:05:15,680
all of the range of human emotions that can 
be communicated. If your goal is simply to  

54
00:05:15,680 --> 00:05:23,840
present a fancy piece of art, then you can 
begin and end with just “fancy piece of art.”

55
00:05:28,640 --> 00:05:29,920
(can we move to the next slide, please)

56
00:05:34,800 --> 00:05:52,080
Accessibility is about function and 
usability, not checklists. This is a  

57
00:05:52,080 --> 00:05:58,240
difficult topic to understand for many people. 
When tasked with making something accessible,  

58
00:05:59,120 --> 00:06:03,920
what is usually presented is either 
a list of guidelines or worse,  

59
00:06:03,920 --> 00:06:09,120
a checklist of things you have to do to make 
your document or your content accessible.  

60
00:06:09,920 --> 00:06:15,440
And that can serve as the starting point for a 
remediation effort or an accessibility effort,  

61
00:06:15,440 --> 00:06:21,840
but should not be the total end goal. And we've 
got a list of examples here. The checklists are  

62
00:06:21,840 --> 00:06:27,280
the start for items such as “elements being 
completely skipped,” “accuracy of heading  

63
00:06:27,280 --> 00:06:32,240
structure...” “Whether there's alt text,” 
“validity of links,’ “logical reading order…”  

64
00:06:33,280 --> 00:06:38,000
We'll be going into a little more depth on most of 
these throughout the course of this presentation,  

65
00:06:39,840 --> 00:06:43,920
but just to dig in on that first one a little bit.

66
00:06:48,640 --> 00:06:55,600
A checklist may tell you that all content has to 
be tagged, or it may tell you that all-important  

67
00:06:55,600 --> 00:07:00,800
content may be tagged. But that leaves room 
for human interpretation as to what might be  

68
00:07:00,800 --> 00:07:07,760
important. And it may lead to people creating a 
cluttered experience where decorative images or  

69
00:07:09,360 --> 00:07:14,720
purely visual objects are also tagged or exposed  

70
00:07:14,720 --> 00:07:19,280
when they aren't actually providing 
any meaning or usage to an end-user.

71
00:07:23,680 --> 00:07:31,360
It is often very easy to check off the 
boxes within the checklist without filling  

72
00:07:31,360 --> 00:07:36,080
fulfilling the intent... without creating 
something usable, intuitive or clear.  

73
00:07:36,640 --> 00:07:42,640
Not all big bolded text is a heading. Not all 
reading orders are fully logical for any user.  

74
00:07:43,520 --> 00:07:49,440
And some tooltips are open for interpretation. 
A date next to a form field is clear intent  

75
00:07:55,600 --> 00:07:59,520
but there may be specific syntax 
or structural requirements there  

76
00:07:59,520 --> 00:08:01,440
that aren't communicated by the word “date.”

77
00:08:04,160 --> 00:08:05,680
(Can we have the next slide, please)

78
00:08:11,440 --> 00:08:18,880
The Web Content Accessibility Guidelines. These 
should be the starting point of your accessibility  

79
00:08:18,880 --> 00:08:25,760
journey, not the end goal. And as mentioned, 
much confusion arises because WCAG can be  

80
00:08:25,760 --> 00:08:35,280
presented purely as a checklist. The WAI 
has a list of each of the criterion in order  

81
00:08:35,840 --> 00:08:40,320
and each of them has subsections that 
contain lists of sufficient techniques.  

82
00:08:41,840 --> 00:08:45,120
And what really matters when 
you're trying to understand WCAG  

83
00:08:45,120 --> 00:08:49,840
relative to the sufficient techniques for the 
checklist mentality... Each and every one of  

84
00:08:49,840 --> 00:08:54,720
those pages begin with one or more paragraphs 
describing the intent of success criteria.  

85
00:08:56,720 --> 00:08:59,920
Those paragraphs will tell you 
what you're supposed to be doing  

86
00:09:00,960 --> 00:09:05,120
whilst the sufficient techniques are 
indicative examples of how to do it.

87
00:09:07,760 --> 00:09:19,840
The intent of success criterion 
for WCAG 111 tells us that  

88
00:09:21,200 --> 00:09:24,400
all non-text content should 
have a text equivalent.  

89
00:09:27,200 --> 00:09:35,840
And this is easily interpreted as placing alt 
text onto images and tooltips on the form fields.  

90
00:09:48,960 --> 00:09:55,920
But that frequently leads to an experience 
which is not intuitive, and to materials not  

91
00:09:55,920 --> 00:10:01,760
usable. A classic example of this would be 
a complicated infographic. It may contain  

92
00:10:01,760 --> 00:10:08,160
hundreds of succinct pieces of information. 
It may be a singular graphic which contains  

93
00:10:09,440 --> 00:10:16,800
10, 12, 100 different sub-images all of 
which are... all of which communicate  

94
00:10:16,800 --> 00:10:21,440
their own unique piece of information. And 
when analyzing this visually, you can move from  

95
00:10:22,000 --> 00:10:25,840
one section of an infographic to another. 
You can analyze it piece by piece.  

96
00:10:26,560 --> 00:10:31,840
If you follow the written word of the 
checklist that “all images must have alt text,”  

97
00:10:33,360 --> 00:10:38,800
you would end up creating a singular alt text and 
place it on the entire complicated infographic.  

98
00:10:39,840 --> 00:10:43,760
And this would not result in an 
equivalent experience. Because  

99
00:10:43,760 --> 00:10:49,840
alt text is read out by screen readers as a 
singular block of text, without formatting.  

100
00:10:50,720 --> 00:10:55,360
It can't be broken into subsections 
of its own. You can't move directly to  

101
00:10:58,960 --> 00:11:05,440
one particular eye-catching piece or another. In 
those cases, fulfilling the intent of providing  

102
00:11:05,440 --> 00:11:11,040
text alternatives for all information would be 
to split that image up into multiple images,  

103
00:11:12,800 --> 00:11:18,080
providing unique and distinct alt text 
for each of them, so that each individual  

104
00:11:18,080 --> 00:11:22,720
piece of that information is communicated 
uniquely and can be navigated to with ease.  

105
00:11:24,320 --> 00:11:28,640
We have one of my favorite quotes here on 
the slide. “The power of the web is in its  

106
00:11:28,640 --> 00:11:33,840
universality. Access by everyone regardless 
of disability is an essential aspect.”  

107
00:11:34,720 --> 00:11:40,000
If you begin with that mentality, 
trying to ensure that everyone can  

108
00:11:40,000 --> 00:11:45,520
access the information in an equivalent 
way, or as close as possible, you'll have  

109
00:11:45,520 --> 00:11:49,720
much higher levels of engagement and much higher 
levels of understanding from diverse groups.

110
00:11:49,720 --> 00:11:55,840
( move to the next slide, please)

111
00:11:58,800 --> 00:12:05,600
All of the guidelines within WCAG are broken down 
into one of four pillars. Perceivable, operable,  

112
00:12:05,600 --> 00:12:11,520
understandable, and robust. Okay, guidelines 
success criteria are organized around the  

113
00:12:11,520 --> 00:12:15,120
following four principles which lay 
the foundation necessary for anyone  

114
00:12:15,120 --> 00:12:25,200
to access and use web content. Anyone who wants to 
use the web must have content that is perceivable.  

115
00:12:25,920 --> 00:12:29,840
Information and user interface components must 
be presented in ways that they can perceive.

116
00:12:32,000 --> 00:12:36,880
Operable: user interface components 
and navigation must be operable.  

117
00:12:37,680 --> 00:12:42,320
Understandable: Information and the operation 
of user interface must be understandable.  

118
00:12:43,120 --> 00:12:48,480
Robust: Content must be robust enough it can 
be interpreted reliably by a wide variety of  

119
00:12:48,480 --> 00:12:55,440
user agents including assistive technologies. That 
probably sounds like a lot of jargon. We'll dig  

120
00:12:55,440 --> 00:12:58,400
a little more into these in turn.
(switch to next slide)

121
00:13:01,120 --> 00:13:07,200
What is perceivable? Users must be able to 
perceive the information being presented.  

122
00:13:07,200 --> 00:13:14,720
It can't be invisible to all their senses. 
This one seems very intuitive and obvious.  

123
00:13:17,840 --> 00:13:23,600
Obviously, we cannot present information that 
can’t be perceived, and that leaves us with  

124
00:13:25,280 --> 00:13:28,800
a number of potential barriers when 
we're talking about disabled groups.

125
00:13:33,520 --> 00:13:38,560
For PDFs, this means meaningful information 
cannot be hidden from assistive technology users.  

126
00:13:42,720 --> 00:13:49,520
You have to tag relevant content and, don't tag 
repetitive elements. Tag images that provide  

127
00:13:49,520 --> 00:13:54,560
information, don't tag decorative images. 
And all form fields must have tooltips.

128
00:13:56,000 --> 00:14:06,240
Now what this really means is that once 
you've factored in the ways in which people  

129
00:14:06,240 --> 00:14:14,080
will attempt to access information, you should 
have that information be accessible through at  

130
00:14:14,080 --> 00:14:22,880
least one sense. A deaf person will be able to 
understand a sign language translator on a video,  

131
00:14:23,680 --> 00:14:30,880
whereas a blind person would be able to 
understand audio description. We bump into  

132
00:14:30,880 --> 00:14:35,600
greater barriers and greater thresholds 
for accessibility implementation when  

133
00:14:35,600 --> 00:14:41,360
we encounter a deaf-blind person who can't 
use either of these. And we should consider  

134
00:14:41,360 --> 00:14:46,480
combinations or confluences of disabilities 
when determining what is perceivable to who.

135
00:14:50,800 --> 00:14:55,120
At this point, I'm not aware of any way 
to smell or taste the internet. If anyone  

136
00:14:55,120 --> 00:15:00,800
has any information about that please let 
me know! (move to the next slide, please)

137
00:15:06,000 --> 00:15:11,200
Operable: users must be able to operate the 
interface. It cannot require an interaction  

138
00:15:11,200 --> 00:15:17,040
that users cannot perform. For PDFs, this 
means that embedded links must function.  

139
00:15:17,760 --> 00:15:24,880
Table of content links in larger documents must 
also function, and larger is normally defined as  

140
00:15:24,880 --> 00:15:29,280
20 pages or more. And all interactive 
objects must be keyboard accessible.  

141
00:15:29,840 --> 00:15:35,440
Users must be able to access, for example, 
form fields, with a keyboard. Now, this can  

142
00:15:37,040 --> 00:15:40,080
also create a number of additional 
barriers when we're discussing  

143
00:15:40,080 --> 00:15:46,400
what is or is not keyboard accessible. The 
intent of the success criterion is that  

144
00:15:50,080 --> 00:15:55,360
regardless of the interface being used, 
all information is accessible. And that  

145
00:15:55,360 --> 00:15:59,920
means certain functions are out 
of the realms of possibility  

146
00:16:01,120 --> 00:16:08,000
for users, depending on what system they're 
on, what resources they're using. At this time  

147
00:16:08,000 --> 00:16:15,360
it is not possible to execute a single right-click 
operation through a touch screen. Drag and drop  

148
00:16:15,360 --> 00:16:23,920
operations are still not possible through a 
GUI using a blow tube. And it is extremely  

149
00:16:23,920 --> 00:16:30,880
difficult for an amputee to simultaneously press 
the left shift and the number pad 5 on a standard  

150
00:16:30,880 --> 00:16:39,600
QWERTY keyboard. But we should be considering what 
people will be using to access the resources when  

151
00:16:40,320 --> 00:16:50,000
we are building out into points of interaction. 
(can we move to the next slide, please)

152
00:16:50,000 --> 00:16:55,040
What is understandable? Users must 
be able to understand the information  

153
00:16:55,040 --> 00:17:02,560
as well as the operation of the user interface. 
And this one absolutely depends on the audience.  

154
00:17:04,960 --> 00:17:11,600
Your starting point here will be to ensure that 
the languages are correctly set. French text being  

155
00:17:11,600 --> 00:17:18,080
read in English or “Fringlish” is completely 
meaningless to both English and French users.  

156
00:17:18,080 --> 00:17:27,320
Some loaned words are going to be... are going to 
lose their meaning or lost in translation. “C’est  

157
00:17:27,320 --> 00:17:34,240
la vie” can easily be pronounced as “Sest la vye” 
by a straight text-to-speech engine. A piñata  

158
00:17:37,360 --> 00:17:45,200
has a similar barrier of bad pronunciation. 
A slang, jargon, or complicated terminology  

159
00:17:45,200 --> 00:17:51,760
or structure like legalese should only be 
used where it's necessary to communicate…  

160
00:17:54,640 --> 00:18:00,160
where that structure is necessary for the 
intended means of communication. Acronyms  

161
00:18:00,160 --> 00:18:06,000
without explanation should always be avoided, 
and once again tooltips for form fields.

162
00:18:14,000 --> 00:18:21,520
I did a search on a Department of Defense website 
and found that there are 29 different definitions  

163
00:18:21,520 --> 00:18:30,720
for the acronym “ACS.” And whilst that may be 
easy and intuitive to identify exactly which one  

164
00:18:30,720 --> 00:18:37,120
applies to you if you are part of the armed 
forces in a specific division, somebody outside  

165
00:18:37,120 --> 00:18:41,840
reading that document is not going to have the 
context necessary to make that determination.

166
00:18:44,400 --> 00:18:49,440
Does ACS stand for Airborne Control 
System? Auxiliary Crane Ship? Assistant  

167
00:18:49,440 --> 00:18:56,080
Chief of Staff? Air Commando Squadron? 
It's very difficult to tell. The real  

168
00:18:56,080 --> 00:19:01,440
barrier when it comes to understandability 
is identifying who the intended audience is.  

169
00:19:02,320 --> 00:19:09,840
Whilst legalese makes little to no sense to 
the average school child, somebody who is  

170
00:19:10,400 --> 00:19:16,560
an active practicing lawyer is going to 
have a relatively easier time navigating it.  

171
00:19:20,240 --> 00:19:25,840
And this comes back to that all-important intent 
mentioned earlier. Who do you intend to use it,  

172
00:19:25,840 --> 00:19:30,000
what is the expected knowledge or 
experience level of your intended user?

173
00:19:32,480 --> 00:19:33,680
(can we have the next slide)

174
00:19:37,760 --> 00:19:42,720
Robust: Users must be able to access 
the content as technologies advance.  

175
00:19:44,240 --> 00:19:48,400
This aspect of work is more for developers 
than content creators. For PDFs,  

176
00:19:49,040 --> 00:19:54,000
you want to make sure the content displays as 
authors intend. Actional elements function as  

177
00:19:54,000 --> 00:20:01,440
the author intends. Buttons, links, tables of 
contents should all function. And should all  

178
00:20:01,440 --> 00:20:06,160
perform their operations regardless of which 
mechanism you're using to interact with them.  

179
00:20:07,360 --> 00:20:11,840
And they should remain compatible with current 
and future browsers, web-enabled devices,  

180
00:20:11,840 --> 00:20:18,320
and assistive technologies. We've all... I'm sure 
we've all encountered the barrier of a web page  

181
00:20:18,320 --> 00:20:28,240
that says “for better usage move to our mobile 
version” or “to finish this try in our app.”  

182
00:20:29,120 --> 00:20:35,520
Asking people to change which system that they 
are using in order to access the information  

183
00:20:35,520 --> 00:20:40,320
or functionality creates additional barriers 
for everyone, but this is especially acute for  

184
00:20:41,120 --> 00:20:47,840
users of assistive technologies who may not 
have an alternative to their screen reader.

185
00:20:49,760 --> 00:20:50,320
(next slide)

186
00:20:50,320 --> 00:20:58,480
[Dan Tuleta} So Ryan, I think this is where I was 
gonna jump back in and kind of and talk about how  

187
00:20:58,480 --> 00:21:03,920
the four pillars of WCAG can kind of apply 
in a more practical sense to PDF documents.  

188
00:21:04,480 --> 00:21:11,520
And of course, mentioning our PDF remediation 
tool Equidox. To kind of just describe how  

189
00:21:11,520 --> 00:21:15,120
that tool can be used to make sure 
that all of your documents are  

190
00:21:15,120 --> 00:21:19,520
in alignment with the four pillars of 
WCAG to the greatest possible extent.  

191
00:21:21,280 --> 00:21:27,200
So one of the things that was mentioned before 
are skipped elements. So skipped elements. They  

192
00:21:27,200 --> 00:21:31,840
may fail an accessibility checker, but they 
may not. So this is one thing that I notice  

193
00:21:31,840 --> 00:21:37,520
in working with a lot of different PDFs 
on a day-to-day basis.. is there can be  

194
00:21:37,520 --> 00:21:43,280
corners cut in any sort of remediation or tagging 
process. Where entire chunks of information,  

195
00:21:43,280 --> 00:21:48,240
entire pages, can be completely skipped. Maybe 
they were determined to be too hard to remediate,  

196
00:21:48,880 --> 00:21:54,160
or maybe an auto-tagging process did not pick 
up that content for whatever reason. But it  

197
00:21:54,160 --> 00:21:58,560
is important to make sure that while you are 
remediating a document using a tool like Equidox,  

198
00:21:58,560 --> 00:22:06,080
that you aren't skipping over important elements 
that are conveying meaning to the end-user. So as  

199
00:22:06,080 --> 00:22:10,640
I said before these, skipped elements may or may 
not fail an accessibility checker. So when we talk  

200
00:22:10,640 --> 00:22:16,720
about going back to this reliance on accessibility 
checkers. So something like skipped content...  

201
00:22:16,720 --> 00:22:23,840
if that content is artifacted, it may be leaving 
important information out of the document for that  

202
00:22:23,840 --> 00:22:33,440
end user. Another component of PDFs is of course 
heading structure. So there are hard and fast  

203
00:22:33,440 --> 00:22:39,920
rules about heading structure as it relates to PDF 
accessibility. Now here on this slide... we have a  

204
00:22:39,920 --> 00:22:45,440
single-page document (and of course PDF documents 
can get much longer than one single page). So this  

205
00:22:45,440 --> 00:22:51,680
is a pretty low-level example but it does point 
out the difference in heading structure and the  

206
00:22:51,680 --> 00:22:58,400
difference in heading levels as they make up that 
heading structure. So the typical rule is that you  

207
00:22:58,400 --> 00:23:03,520
have one heading level one within a document. 
That is typically something that is on the  

208
00:23:03,520 --> 00:23:10,000
front page. It's usually in big bold font, but not 
always. That's why we're talking about the need  

209
00:23:10,000 --> 00:23:14,720
to go through these documents and look at them 
with some human interaction, and making sure that  

210
00:23:14,720 --> 00:23:19,440
you are actually, in fact, tagging the true 
heading level one and not simply relying on  

211
00:23:19,440 --> 00:23:23,600
“oh this is big bold font so everything that's 
big and bold font gets marked as a heading.”  

212
00:23:24,480 --> 00:23:28,480
The document title is not the same thing as a 
heading level one. That's another thing to keep  

213
00:23:28,480 --> 00:23:34,880
in mind. So there is a difference as it relates to 
PDF accessibility, and then of course there has to  

214
00:23:34,880 --> 00:23:41,520
be a hierarchical structure to the headings. So 
you have a single heading level one. Within that,  

215
00:23:41,520 --> 00:23:46,960
you have sub-categories of heading level twos, and 
within those heading level twos, you can have even  

216
00:23:46,960 --> 00:23:50,880
further levels of subcategories going 
all the way down to heading level six.  

217
00:23:51,440 --> 00:23:56,240
So you're building almost like an outline of the 
document. And this is used for navigation. So it  

218
00:23:56,240 --> 00:24:00,560
makes these documents operable by the end-user 
because then they can freely move about the  

219
00:24:00,560 --> 00:24:07,280
document and get to sections of information that 
they are really interested in hearing. So just an  

220
00:24:07,280 --> 00:24:13,920
example that I use on a regular basis, is if you 
imagine an entire textbook in a digital format.  

221
00:24:13,920 --> 00:24:21,920
Well, if someone needs to get to chapter 16, and a 
subsection within a subsection of that chapter 16…  

222
00:24:21,920 --> 00:24:27,360
The heading structure is what allows them 
to leapfrog past the first 15 chapters,  

223
00:24:27,360 --> 00:24:31,840
and then drill down within chapter 16, once 
they found chapter 16 in the heading structure,  

224
00:24:32,560 --> 00:24:38,080
and get to that particular paragraph or bit of 
information that they were looking for. We do have  

225
00:24:38,880 --> 00:24:43,920
an entire webinar similar to this on heading 
structure. So there is a link in the slide  

226
00:24:43,920 --> 00:24:48,560
deck which will be provided to everyone that is 
attending today. So if you'd like to talk more  

227
00:24:48,560 --> 00:24:53,360
about heading structure or learn a bit more 
we did do an entire webinar dedicated to it.

228
00:24:56,000 --> 00:25:02,560
Now alt tex. So Ryan talked quite a bit about 
alt text. So, of course, the alt text must be  

229
00:25:02,560 --> 00:25:08,080
applicable to the content, and it should of course 
capture the intent or the message of the image,  

230
00:25:08,080 --> 00:25:14,640
and context of course always matters. So what 
we're looking at here in this little example  

231
00:25:14,640 --> 00:25:22,800
is a very complicated map of the New York subway 
system. Now depending on the context and the  

232
00:25:22,800 --> 00:25:30,560
intent of this image, that can really determine 
what you are placing in there for in alt text. If  

233
00:25:30,560 --> 00:25:36,640
the intent of this image is to provide navigation 
instructions for someone that is navigating the  

234
00:25:36,640 --> 00:25:42,960
very complex New York City subway system, that 
is quite an alt text that would be required.  

235
00:25:42,960 --> 00:25:48,240
You might have to describe different relationships 
between points, how far away distances are, where  

236
00:25:48,240 --> 00:25:54,880
each of these different stations lets out on the 
street… It's quite a project to try to describe  

237
00:25:54,880 --> 00:25:59,760
everything that is happening in this image. 
However, if this is just a tiny little thumbnail  

238
00:25:59,760 --> 00:26:05,120
image in the corner of a brochure that is sort 
of advertising the use of the subway system,  

239
00:26:05,120 --> 00:26:11,040
chances are it's not really intended to be used 
for navigation purposes. Therefore that can  

240
00:26:11,040 --> 00:26:14,960
change up your approach to the alt text, where 
you would simplify it and you might write just  

241
00:26:14,960 --> 00:26:20,720
“an overhead view of the New York City subway 
system” and keep it very simple, keep it concise  

242
00:26:20,720 --> 00:26:26,800
and just describe that there is a “high-level 
map of the of the subway system” and then you can  

243
00:26:26,800 --> 00:26:31,280
move on to other elements in the document knowing 
that the intent of that image was not to provide  

244
00:26:31,280 --> 00:26:38,800
turn-by-turn directions for an end-user. We do 
have another webinar as well and a blog related  

245
00:26:38,800 --> 00:26:43,360
to alt text so we will provide that link as well. 
It will be in the slide deck when you receive it.

246
00:26:46,080 --> 00:26:51,360
So, links and URLs. Links of course should be 
interactive. They must have correctly defined  

247
00:26:51,360 --> 00:26:57,840
destinations they should indicate where their 
destination is leading and things like “click  

248
00:26:57,840 --> 00:27:05,360
here” or “contact us” are not particularly useful, 
because what are they clicking here for? And who  

249
00:27:05,360 --> 00:27:11,280
are they contacting when they click on the 
“contact us” link? So links should be unique,  

250
00:27:11,840 --> 00:27:15,520
and it should be very clear as to 
what this link is taking that user to.  

251
00:27:16,560 --> 00:27:21,840
Oftentimes there will be links within documents 
that will say “next page” or “previous page.”  

252
00:27:22,560 --> 00:27:29,440
But a link that says “link to page 27” is of 
course more useful than “next” or “previous  

253
00:27:29,440 --> 00:27:33,920
page.” If a user is looking at a list of all of 
the links within the document, and every single  

254
00:27:33,920 --> 00:27:40,400
page has a “next” and a “previous” link on it, 
that is going to be utterly useless to them,  

255
00:27:41,120 --> 00:27:45,360
as each one of those links is not unique and 
it doesn't actually take them to a particular  

256
00:27:45,360 --> 00:27:50,720
location that that is easily understood by 
them. Because every single link says “next”  

257
00:27:50,720 --> 00:27:57,040
or “previous.” So things like “links to page 
27,” for example, are definitely more helpful.

258
00:27:59,520 --> 00:28:05,280
Logical reading order is another thing that is 
critical in terms of PDF accessibility. Not every  

259
00:28:05,280 --> 00:28:11,120
page is going to be left-to-right, top-to-bottom. 
A very simple and easy easily understood flow of  

260
00:28:11,120 --> 00:28:19,040
that reading order. For example, newspapers or 
magazine articles, or you know tri-fold brochures  

261
00:28:19,040 --> 00:28:23,040
where oftentimes the cover page is over on the 
right-hand side when that document is viewed  

262
00:28:23,040 --> 00:28:28,640
in a digital format. So when you think about the 
logical reading order, this is an example here of  

263
00:28:28,640 --> 00:28:35,200
a very complicated-looking cover of a newspaper. 
So without a properly defined reading order,  

264
00:28:35,200 --> 00:28:40,880
a screen reader is liable to just read clear 
across left-to-right. There are four separate  

265
00:28:40,880 --> 00:28:46,960
articles here on this page, as well as, obviously, 
very large headings and titles at the top of the  

266
00:28:46,960 --> 00:28:52,800
page. So the order in which all of this content 
is going to be read cannot really be relied  

267
00:28:52,800 --> 00:28:58,320
upon unless you go through and set the proper 
reading order to read the far left column first,  

268
00:28:59,040 --> 00:29:03,520
then moving into the middle column, the middle 
section with that article, moving over to the  

269
00:29:03,520 --> 00:29:09,840
right to that third and fourth column after that. 
So going through a document and making sure that  

270
00:29:09,840 --> 00:29:15,760
you have set the proper reading order is is is 
truly critical for the usability of that document.

271
00:29:18,000 --> 00:29:21,600
Keeping content together. Now 
when you're designing documents,  

272
00:29:21,600 --> 00:29:28,080
of course, not everything is going to be perfect. 
You might have to merge text, for example. So  

273
00:29:28,880 --> 00:29:34,320
multiple column splits, text running over onto 
the next page. You might have images embedded  

274
00:29:34,320 --> 00:29:40,160
within the document and the text needs to be sort 
of placed around it. Links can go across different  

275
00:29:40,160 --> 00:29:45,680
lines, and of course tables and lists and all 
different types of elements can be split across  

276
00:29:45,680 --> 00:29:51,280
multiple pages. So it's important to make sure 
that you are trying to keep this content together  

277
00:29:51,280 --> 00:29:55,360
with the use of the merge feature. Which 
is very easy to use within Equidox. So  

278
00:29:55,920 --> 00:30:01,200
that's just another thing to keep in mind, that 
if you have a sentence or a paragraph that runs  

279
00:30:01,200 --> 00:30:05,680
out of room in whatever column it may be and 
picks up in the next column or on the next page,  

280
00:30:06,240 --> 00:30:11,040
making sure that you group that content together 
is very helpful to an end-user. Otherwise,  

281
00:30:11,040 --> 00:30:15,040
it will be treated as two totally separate 
elements, when in fact it should be read as one.

282
00:30:17,200 --> 00:30:25,040
Fillable forms. Of course, fillable forms are 
in a PDF format, they can be quite complex. But  

283
00:30:25,040 --> 00:30:29,440
all items should be interactive and the 
critical part of PDF forms are tooltips.  

284
00:30:30,080 --> 00:30:36,400
And tooltips should be very specific. So if 
you think of a form that is just asking you for  

285
00:30:36,400 --> 00:30:42,160
“name,” well whose name is it? the applicant's 
name? Is it their guardian's name? Is it…  

286
00:30:44,000 --> 00:30:47,520
which name is it? Is it the middle 
name? The last name? Middle initial?  

287
00:30:48,320 --> 00:30:53,200
Buyer name versus seller name? If you're 
assigning a purchase agreement, for example,  

288
00:30:53,920 --> 00:31:00,320
formatting needs to be specified within tooltips. 
So if you're asking for a date, are you asking for  

289
00:31:00,320 --> 00:31:06,960
the day-day, the month-month,year-year? Do you 
want four digits for the year instead of two?  

290
00:31:06,960 --> 00:31:12,800
Do you want the month before the date? So if you 
have people that are just able to fill out this  

291
00:31:12,800 --> 00:31:18,240
form without any specific formatting, then that 
can cause a lot of confusion for the administrator  

292
00:31:18,240 --> 00:31:21,760
who is actually receiving that form. Because 
someone has filled it out incorrectly because they  

293
00:31:21,760 --> 00:31:28,080
did not follow any sort of specific formatting 
because that document was not remediated and  

294
00:31:28,080 --> 00:31:34,560
that tooltip did not provide that context for that 
user who is filling out that form. And of course,  

295
00:31:34,560 --> 00:31:39,520
tooltips should not be repeated. So if you have 
multiple fields asking for the address... for  

296
00:31:39,520 --> 00:31:44,400
example, billing address versus shipping address, 
you don't want to just say “address” for both of  

297
00:31:44,400 --> 00:31:49,680
those tooltips. You want to be very specific and 
provide explicit instructions as to how that user  

298
00:31:49,680 --> 00:31:55,360
should be filling out that particular field versus 
another one that might be just like it in terms of  

299
00:31:55,360 --> 00:32:00,560
how they're interacting with it> But, in fact, 
it's asking for a completely different address.

300
00:32:02,800 --> 00:32:07,840
Table structure is another critical component. 
Tables can be quite complex. Luckily,  

301
00:32:07,840 --> 00:32:13,280
with Equidox, we make it a lot easier to remediate 
tables than any other tool on the market,I would  

302
00:32:13,280 --> 00:32:21,360
argue. So table structure will have things such 
as headings. Table headers, as well as table data.  

303
00:32:22,000 --> 00:32:26,880
You can have merged cells within tables. Links 
can be placed inside of tables. Table summaries  

304
00:32:26,880 --> 00:32:31,680
are important. They provide necessary and helpful 
information in reading the table. So if there's  

305
00:32:31,680 --> 00:32:37,200
any sort of unique layouts or design elements 
within that table, that's when the table summary  

306
00:32:37,200 --> 00:32:41,840
becomes very helpful. So that could be merged 
cells, headings, numbers of columns or rows,  

307
00:32:43,600 --> 00:32:47,360
it's really up to the individual table. But 
if you look at the example here on the right,  

308
00:32:47,920 --> 00:32:54,800
this has four separate columns of table data. But 
there are two rows of column headers. So 2017 is  

309
00:32:54,800 --> 00:33:00,640
a column header that spans four rows. And you have 
individual column headers for the quarters within  

310
00:33:00,640 --> 00:33:06,640
the 2017 year. And of course, your row headers are 
on the far left as it breaks down the individual  

311
00:33:06,640 --> 00:33:12,160
departments. So it's important to identify those, 
have those headers so that as a user is navigating  

312
00:33:12,160 --> 00:33:16,400
the table data they understand exactly where they 
are oriented within the table. They understand  

313
00:33:16,400 --> 00:33:21,200
which column headers or which column they are 
within and as well as the row that they are in.  

314
00:33:23,120 --> 00:33:29,760
We do have a link here provided to a Smart Table 
Detector Webinar. So it's a table-specific webinar  

315
00:33:29,760 --> 00:33:32,800
if you have more questions or are interested 
in learning more about our table editing  

316
00:33:32,800 --> 00:33:38,480
capabilities. So with that said, in the interest 
of time here (we are a few minutes past) so I do  

317
00:33:38,480 --> 00:33:44,080
apologize. I've been a bit long-winded but I do 
appreciate everyone for taking the time to join  

318
00:33:44,080 --> 00:33:49,920
us today. As always EquidoxSales@Onixnet.com if 
you have any questions or if you'd like to set  

319
00:33:49,920 --> 00:33:54,640
up a personal one-on-one call. We can take 
a look at your documents, we can talk about  

320
00:33:54,640 --> 00:34:01,760
your accessibility needs. We have our website 
www.Equidox.co, and as I said before, please feel  

321
00:34:01,760 --> 00:34:06,400
free to connect with us on LinkedIn and Twitter, 
and all of the social media networks. We're very  

322
00:34:06,400 --> 00:34:10,560
active on there. And you can always stay up to 
date on what's coming next with the Equidox team.  

323
00:34:10,560 --> 00:34:13,840
So with that said, thank you very much. Tammy 
were there any questions or should we wrap up?

324
00:34:13,840 --> 00:34:20,400
[Tammy Albee] We did not have any questions. 
There were a few issues with the images,  

325
00:34:20,400 --> 00:34:25,440
but for anyone that was hoping to see a little 
more on a couple of those slides, the remediated  

326
00:34:25,440 --> 00:34:29,440
slide deck will be made available to everyone who 
registered. So if you're wondering what some of  

327
00:34:29,440 --> 00:34:33,840
those images were, you should be able to see them 
there even if they didn't show up on your screen.

328
00:34:33,840 --> 00:34:38,240
[Dan Tuleta] Okay, all right well, 
great well thank you so much, everyone,  

329
00:34:38,240 --> 00:34:47,840
for joining and we will we'll see you next month!