1 00:00:00,800 --> 00:00:07,600 Equidox by Onix. Reach everyone. [Dan Tuleta] Thank you, everyone. Welcome to another edition   2 00:00:07,600 --> 00:00:13,760 of Equidox Webinar Wednesdays. Today we are  going to be covering a couple of new features   3 00:00:13,760 --> 00:00:20,560 and some old ones as well. Mainly the Table of  Contents feature, which was a popular request for   4 00:00:20,560 --> 00:00:25,920 a lot of users. We're going to be talking a little  bit about links and footnotes and footnote links,   5 00:00:25,920 --> 00:00:30,320 as well as the Zone Source feature which I  don't believe we've covered in any of our   6 00:00:30,320 --> 00:00:36,320 previous webinars. We have a new addition to that  Zone Source drop-down menu called Actual Text.   7 00:00:36,320 --> 00:00:43,440 So I'm going to go through a couple of practical  use cases for these new features and we'll get   8 00:00:43,440 --> 00:00:49,680 everyone kind of up to speed on how they work  and how to use them. As always, if if anyone   9 00:00:49,680 --> 00:00:55,360 would like to chat with us one-on-one, have a  more formal discussion on exactly how Equidox   10 00:00:55,360 --> 00:01:00,000 might fit into your organization, please  feel free to reach out to us at any point   11 00:01:00,560 --> 00:01:07,120 at EquidoxSales@Onixnet.com. You can  also visit our website www.Equidox.co,   12 00:01:08,080 --> 00:01:12,400 and feel free to call us or get in touch with  your account manager at any point. We're also very   13 00:01:12,400 --> 00:01:18,000 active on LinkedIn and social media. If you'd like  to just stay up to date on the latest happenings   14 00:01:18,000 --> 00:01:22,480 within Equidox. So that said I'm going to get  started here. I'm going to close out of this   15 00:01:23,600 --> 00:01:30,320 Powerpoint and I'm going to jump into Equidox.  Now I'm going to start here with a document.   16 00:01:30,320 --> 00:01:35,280 The main kind of new feature that we've introduced  to Equidox is the Table of Contents feature.   17 00:01:36,080 --> 00:01:41,760 Previously we were able to tag what would be  considered a Table of Contents, but now we're   18 00:01:41,760 --> 00:01:49,520 actually able to export with the proper TOC and  TOCI tag types within within the PDF, so that when   19 00:01:49,520 --> 00:01:55,600 you run an accessibility report or check through  the the tag structure of the of the document,   20 00:01:55,600 --> 00:02:02,400 you will see the actual Table of Contents tagged  correctly. This can be quickly explained as   21 00:02:02,400 --> 00:02:07,920 simply as tagging the Table of Contents as a  list, and then simply pressing a check box to   22 00:02:07,920 --> 00:02:13,360 mark it as a Table of Content. As and that will  automatically convert that list into a TOC in   23 00:02:13,360 --> 00:02:18,800 the TOCI tag types. But I'm going to go through a  quick example just to show everyone how it works.   24 00:02:18,800 --> 00:02:21,840 And it's right here on this first page. So  I'm just going to open up this first page,   25 00:02:22,800 --> 00:02:27,120 and this document is for the most part  remediated from start to finish, but I   26 00:02:27,120 --> 00:02:33,120 do have this one element that I've completely left  out. And that is of course the Table of Contents.   27 00:02:33,840 --> 00:02:39,360 Now what I'm going to do to tag this Table  of Contents is, I'm going to click and drag   28 00:02:39,360 --> 00:02:45,840 a zone and just create a single zone over the  entire Table of Contents. And then I will hit   29 00:02:45,840 --> 00:02:51,760 “L” on my keyboard so I'm changing it to a List  Zone. Or you can of course hit the drop-down menu   30 00:02:51,760 --> 00:02:57,920 and change it to a List. And now, since this is...  from a technical standpoint we are tagging this as   31 00:02:57,920 --> 00:03:03,200 a list for the time being, but we don't have any  list labels, as is pretty common with Table of   32 00:03:03,200 --> 00:03:09,120 Contents. So if you don't have any bullet points  or numbers or roman numerals to identify the   33 00:03:09,120 --> 00:03:14,720 individual list items, the list detector is not  going to work as well because it's not quite sure   34 00:03:14,720 --> 00:03:21,840 how to deliminate between individual list items.  But if that's the case, never fear because you can   35 00:03:21,840 --> 00:03:27,840 still manually create list items through the list  items field down here. So in this case, I have   36 00:03:27,840 --> 00:03:32,560 six different items in this Table of Contents. So  I can simply hit the arrow key to indicate that I   37 00:03:32,560 --> 00:03:38,080 want six items in my list, and then you're able  to just drag these sliders into place. So if you   38 00:03:38,080 --> 00:03:41,760 just start moving these up and down and just  placing them exactly where they need to go.   39 00:03:43,520 --> 00:03:47,840 So now I've identified the six distinct  items in my list, and when I take a look   40 00:03:47,840 --> 00:03:54,800 at the HTML preview, what I see is essentially  a list. So nothing too different than what you   41 00:03:54,800 --> 00:03:59,520 would typically encounter whether you're  using the detection slider or not, but you   42 00:03:59,520 --> 00:04:05,520 see basic list structure here. And now the key for  converting this into an actual Table of Contents…   43 00:04:05,520 --> 00:04:10,320 When we go to export the document, you're actually  just going to hit this check box here where it   44 00:04:10,320 --> 00:04:14,960 says Convert to Table of Contents. So when you  create a list now you're going to have this option   45 00:04:15,520 --> 00:04:21,360 to hit this check box to convert your TOC into the  proper tag structure. So that when you export it,   46 00:04:22,080 --> 00:04:26,560 it will show you the exact tag structure that  you're looking for with that Table of Contents.   47 00:04:26,560 --> 00:04:33,120 In the Table of Contents items. Now once you've  hit that checkbox, nothing is going to visually   48 00:04:33,120 --> 00:04:37,680 change in your HTML preview. So you're not  going to get that confirmation from the HTML.   49 00:04:38,480 --> 00:04:44,960 However, if you look at the tag structure…  So I've previously exported this file just to   50 00:04:44,960 --> 00:04:50,640 show you what the tag structure will look like. So  if I open up the actual tag structure for this for   51 00:04:50,640 --> 00:04:56,160 this specific page, this is the same page here…  What you're going to expect to see is your TOC   52 00:04:57,680 --> 00:05:01,600 tagging over here on the left-hand side when  you're looking at the individual tag structure.   53 00:05:02,320 --> 00:05:08,480 So you can clearly see that you have TOC  and TOCI tags within this area here. So   54 00:05:09,280 --> 00:05:13,040 that is something that you can look forward to if  you have documents that contain Table of Contents.   55 00:05:13,040 --> 00:05:18,960 You can now properly tag them with the correct  tag type. And also just to show you that the   56 00:05:18,960 --> 00:05:23,840 accessibility report, once you've remediated the  full document. I just always like to remind people   57 00:05:23,840 --> 00:05:30,800 that when you run an accessibility report on a  document, all PDFs, oftentimes, or well actually   58 00:05:30,800 --> 00:05:36,880 every time, you're going to see two question marks  next to two items on that accessibility report.   59 00:05:37,920 --> 00:05:42,320 This is a question that I am asked on a regular  basis. So I just like to remind people that   60 00:05:42,320 --> 00:05:47,520 these question marks are not error messages.  They are not; they're not like warning you that   61 00:05:47,520 --> 00:05:53,040 your document is inaccessible. They are simply  reminding you that the logical reading order   62 00:05:53,040 --> 00:05:57,600 is something that requires a manual check,  and then the color contrast is also something   63 00:05:57,600 --> 00:06:02,320 that requires a manual check. So oftentimes  people will export a document from Equidox,   64 00:06:02,320 --> 00:06:06,080 and they'll see a tag structure that looks like  this. And they're just concerned that there's   65 00:06:06,080 --> 00:06:10,800 still two errors with their document. But it's  typically always going to be that logical reading   66 00:06:10,800 --> 00:06:16,160 order and the color contrast which are going  to be present in every document no matter what.   67 00:06:16,160 --> 00:06:19,840 So this is just something that it's just letting  you know that you need to take a deeper look   68 00:06:19,840 --> 00:06:24,000 if you're concerned about the color contrast or  just making sure that you're checking the reading   69 00:06:24,000 --> 00:06:28,080 order of these pages. That is not something that  can be programmatically checked for within any   70 00:06:28,080 --> 00:06:36,240 accessibility checker that you're probably using.  Okay so that is a very quick example of a Table of   71 00:06:36,240 --> 00:06:42,720 Contents. Now this being a in only an eight-page  document, Table of Contents for documents that are   72 00:06:42,720 --> 00:06:49,520 under 20 pages from a technical standpoint do not  need to be linked. Meaning that the actual items   73 00:06:49,520 --> 00:06:55,200 themselves are interactive where you can click  on them and direct the user to that specific   74 00:06:55,200 --> 00:07:01,840 page where that content is. So if you have  documents that are larger, and are over 20 pages,   75 00:07:02,960 --> 00:07:08,240 you you will definitely want to make sure that you  are creating interactive links within your Table   76 00:07:08,240 --> 00:07:13,600 of Contents... within the list. So that the end  user who is navigating the document, if they are   77 00:07:13,600 --> 00:07:18,480 reading through their Table of Contents and the  section that they are looking for is now on page   78 00:07:18,480 --> 00:07:27,040 400, they can go directly to that page by clicking  that interactive item. So if you have a document   79 00:07:27,040 --> 00:07:31,280 that does contain a linked Table of Contents,  which is often the case if you have a very   80 00:07:31,280 --> 00:07:35,520 large document, you might find that the Table of  Contents and the links that are in the document   81 00:07:35,520 --> 00:07:40,240 are already there for you. That's great, because  those links will be present for you on import   82 00:07:40,240 --> 00:07:44,080 and you can just rely on those links  that were there from the source file.   83 00:07:44,080 --> 00:07:49,520 However, if you have a document that does not  actually contain a linked Table of Contents,   84 00:07:49,520 --> 00:07:54,560 you can still create it. So if this is  if this is something that you need to do,   85 00:07:55,360 --> 00:08:00,400 what you all you really have to do is just  draw a zone outside of the Table of Contents,   86 00:08:00,400 --> 00:08:04,960 drag it inside of the list item, and  now you have a text zone inside of the   87 00:08:04,960 --> 00:08:10,480 list item. And then if you just hit “U” on your  keyboard, or hit the drop-down menu and change   88 00:08:16,000 --> 00:08:21,680 theProperties that will appear, and you have a URL  and an anchor, so that you're able to add in the   89 00:08:21,680 --> 00:08:27,840 exact destination of this link. So in this case  this particular element goes to page one. We're   90 00:08:27,840 --> 00:08:32,720 on page one, so this is a bit redundant, but if  I want to type in the anchor point I just type in   91 00:08:33,840 --> 00:08:41,280 “#Page_1” and that is the prefix that is required  for linking, like within the document itself. So   92 00:08:41,280 --> 00:08:49,600 to link to a different page within the document  the prefix is “#Page_1” and I can just repeat that   93 00:08:49,600 --> 00:08:56,000 again really quickly. So if I just go... let's  just use this one for example policy if I just   94 00:08:56,000 --> 00:09:05,200 hit “U” on my keyboard to change it to a link  and I hit “#Page_2,” so I'm able to turn those   95 00:09:05,200 --> 00:09:11,680 into actual interactive links. And if you look at  the preview, (I've got some spacing issues here)   96 00:09:12,960 --> 00:09:18,720 but the idea is that you've actually turned it  into a link itself. The item itself is now a link.   97 00:09:21,200 --> 00:09:25,760 So that when the end user is interacting with  this, they can actually click on this item and it   98 00:09:25,760 --> 00:09:32,720 will take them to the direct page they're trying  to navigate to. Now there's also... the question   99 00:09:32,720 --> 00:09:37,840 comes up a lot... about how do I deal with links  in a document in general. Not necessarily related   100 00:09:37,840 --> 00:09:44,960 to Table of Contents. So if you have documents  that already contain links within the source file,   101 00:09:44,960 --> 00:09:50,240 Equidox will import those links. And it will  have the anchor point that that link is actually   102 00:09:50,240 --> 00:09:57,920 directed to. It will contain a link zone similar  to this around the actual interactive content.   103 00:09:57,920 --> 00:10:02,400 And it will have the anchor point pre-defined  for you based on that source file. However,   104 00:10:02,400 --> 00:10:07,760 if you have a document that you would like to add  a link to, to make sure that you can, for example,   105 00:10:07,760 --> 00:10:13,680 link directly to an email address or link to  a web page, an external web page, for example,   106 00:10:13,680 --> 00:10:19,120 you can still create those manually if needed.  And all you need to do in order to create those   107 00:10:19,120 --> 00:10:24,160 links is just draw a zone over some content.  So, for example, this is something in the footer   108 00:10:24,160 --> 00:10:28,960 down here. But if I just wanted to turn this  Synovus into an actual interactive link, I just   109 00:10:28,960 --> 00:10:34,880 draw a zone. I can hit “U” on my keyboard for the  keyboard shortcut, and now I can type in “https:/”   110 00:10:36,400 --> 00:10:45,200 and then “www.synovus.com.” And then when  you look at the preview, you will have   111 00:10:45,200 --> 00:10:49,920 an actual interactive link here. And if you click  on this, it will take you to their actual website.   112 00:10:51,040 --> 00:10:56,880 So that is one way of manually creating links. And  as I said before, if the link is already encoded   113 00:10:56,880 --> 00:11:01,520 into the source file, you do not need to worry  about it, like in terms of creating it manually.   114 00:11:02,080 --> 00:11:06,480 It will already have the link zone type and  will have the anchor point waiting for you.   115 00:11:07,760 --> 00:11:14,000 Now another question that comes up a lot  regarding somewhat similar to links, are footnotes   116 00:11:14,000 --> 00:11:19,520 and footnote links. Which is another common  element type in documents. Now this page here   117 00:11:20,240 --> 00:11:24,800 doesn't have an actual dedicated footnote on  it, but we can still pretend that things are   118 00:11:24,800 --> 00:11:29,360 footnotes. So for example if we just pretend  that this “page one” was actually a footnote,   119 00:11:30,160 --> 00:11:35,920 all I have to do is draw a zone around it to just  tag that content. It's by default a text zone,   120 00:11:35,920 --> 00:11:41,520 of course, but if I change the zone type to  a Footnote in the drop-down menu, that is now   121 00:11:41,520 --> 00:11:46,880 marking this as a footnote. And then let's just  pretend that in the document here I have the word   122 00:11:46,880 --> 00:11:54,000 “consultants” is a footnote link that is directing  that end user down to the footnote at the bottom   123 00:11:54,000 --> 00:11:59,520 of the page. I would then change this zone type  to a Footnote Link. And once I've done that,   124 00:11:59,520 --> 00:12:05,040 I have... the Footnote Link Properties will appear  and this drop-down menu will give me a list of   125 00:12:05,040 --> 00:12:10,160 all of the viable candidates that I have to link  to. So if I have 10 footnotes on a single page,   126 00:12:10,160 --> 00:12:14,560 this list will contain all 10 of those footnotes.  And you just make sure that you link the footnote   127 00:12:14,560 --> 00:12:21,440 link to the correct footnote in that corresponding  list. You can tell the name by the actual, or the   128 00:12:21,440 --> 00:12:26,880 the correct footnote by the actual zone name. So  this is another thing that people might not be too   129 00:12:26,880 --> 00:12:31,200 familiar working with. But you can actually change  the name of a zone just to make it more clear as   130 00:12:31,200 --> 00:12:36,480 to which zone you're linking to. So they just get  a default setting when you import the document.   131 00:12:36,480 --> 00:12:42,560 The exact zone name is predefined by Equidox. But  if you want to change it to make it more obvious,   132 00:12:42,560 --> 00:12:48,400 you can. So you can say like “footnote 1,” for  example, and then when you hit the drop-down menu,   133 00:12:49,360 --> 00:12:53,440 you'll now see in the list you have “footnote  one.” So you can label your footnotes, like you   134 00:12:53,440 --> 00:12:58,400 know, in a way that makes sense to you. See that?  You know you're directing the end user from that   135 00:12:58,400 --> 00:13:02,640 footnote to that footnote link... to the correct  footnote. So now when you hit this drop-down,   136 00:13:02,640 --> 00:13:08,320 and if you look at the preview again, we will  see that now “consultants” is actually linked.   137 00:13:08,320 --> 00:13:10,480 And then down here is that  footnote that I've created.   138 00:13:11,360 --> 00:13:15,520 So that is that is sort of the logic of  using the Footnote and the Footnote Link   139 00:13:16,880 --> 00:13:22,080 feature within Equidox. So I hope that helps.  If anyone has any further questions about that,   140 00:13:22,080 --> 00:13:26,800 we are happy to chat in more detail. If you have  specific examples that you would like to cover…   141 00:13:28,560 --> 00:13:34,880 Now the other thing that we wanted to make sure  that we went over today was the change in the Zone   142 00:13:34,880 --> 00:13:39,120 Source menu. So I'm going to jump out of  this document and jump into something else.   143 00:13:41,040 --> 00:13:49,360 This document here, and the Zone Source for those  of you on the call that have used the Zone Source   144 00:13:49,360 --> 00:13:54,960 feature before, you are probably very familiar  with the three options that we used to have,   145 00:13:54,960 --> 00:14:02,080 which were PDF, OCR, and Custom. We have since  added a new zone type, or a new zone source type,   146 00:14:02,080 --> 00:14:07,760 which is called Actual Text. So I just want to  make sure that everyone's aware of how to use   147 00:14:07,760 --> 00:14:13,920 these different features within Equidox. So “PDF”  is your default zone source for the majority   148 00:14:13,920 --> 00:14:19,200 of PDF documents. And what “PDF” means, is that  it's just pulling the data from that source file.   149 00:14:19,840 --> 00:14:25,440 So when you have a document like this, you have  a text zone here for the “breakfast takeout,”   150 00:14:25,440 --> 00:14:30,720 for example. Nothing is special about this zone.  It's just a standard text zone. And if I look at   151 00:14:30,720 --> 00:14:36,960 the preview, I get on the preview exactly what  I saw in the PDF. I get “breakfast takeout.” So   152 00:14:36,960 --> 00:14:42,400 that's the zone source. Meaning it's just pulling  that data from the file itself. Now the other   153 00:14:42,400 --> 00:14:48,080 zone sources that you're probably mostly familiar  with are Custom, where you're actually able to   154 00:14:49,280 --> 00:14:58,320 insert additional context into the document by  typing something into the Custom Zone Source. So,   155 00:14:58,320 --> 00:15:03,280 for example, a reason where you might want to  use a custom zone on a document like this...   156 00:15:04,240 --> 00:15:08,800 I'm actually going to turn my Zone  Types off just so you can see better.   157 00:15:08,800 --> 00:15:13,920 If anyone has seen a menu in the last 10  years or, so it's very common now to see   158 00:15:14,640 --> 00:15:20,880 a sort of a key like this. Where it tells you that  there are gluten-free options, vegan, vegetarian,   159 00:15:20,880 --> 00:15:26,960 nut-free... maybe dairy-free. All these different  types of options that you might find on a menu.   160 00:15:27,840 --> 00:15:34,080 So a good use for the Custom Zone Source might  be to add in something here. Because as an end   161 00:15:34,080 --> 00:15:37,440 user that's navigating through this with a  screen reader, they're just going to have   162 00:15:37,440 --> 00:15:42,880 these four options read aloud to them. But without  much context as to what is this referring to.   163 00:15:43,520 --> 00:15:47,360 Gluten-free ,vegan, vegetarian, nut-free.. It's  like. “okay great... well what is that actually?   164 00:15:47,360 --> 00:15:53,440 What does that actually mean?” Well what you can  do is you can type it... create a blank zone,   165 00:15:53,440 --> 00:16:02,320 for example, and you can make that a custom zone.  And now you can type in a dietary preferences   166 00:16:04,640 --> 00:16:11,760 key. (If I can spell preferences correctly.)  And then let me make sure that my reading   167 00:16:11,760 --> 00:16:15,840 order is correct. So this is more obvious.  So I'm going to fix this very quickly,   168 00:16:17,600 --> 00:16:23,600 and when I look at the preview, here is that  “dietary preferences” key that I've added in.   169 00:16:24,400 --> 00:16:29,120 So you're able to add in that additional  context for this page to let that end user   170 00:16:29,120 --> 00:16:32,640 know that they're about to hear some random  words: gluten-free, vegan, vegetarian,   171 00:16:32,640 --> 00:16:37,040 and nut-free. And that gives them a better idea  as to what they're about to hear. And you know,   172 00:16:37,040 --> 00:16:42,320 sort of, what it might mean for this menu that  they're about to start reading through. Now that's   173 00:16:42,320 --> 00:16:47,840 one way of using the Custom Zone Source. There  are many ways of using the Custom Zone Source.   174 00:16:48,800 --> 00:16:53,040 For example, another…. just another practical  thing that you might do to a document like this…   175 00:16:53,040 --> 00:16:58,560 Perhaps this restaurant has a Braille menu as  an option as well. So maybe at the very top of   176 00:16:58,560 --> 00:17:08,720 the page you can type in a Custom Zone where  it says “Braille menu available upon request.”   177 00:17:10,400 --> 00:17:13,840 And then let me just make sure that's in the  correct reading order... so when I look at   178 00:17:13,840 --> 00:17:18,320 the preview now, the first thing that that end  user is going to hear when they arrive at this   179 00:17:18,320 --> 00:17:22,640 menu is that if they want a Braille menu, it is  available upon request. So you've taken something   180 00:17:22,640 --> 00:17:27,840 that is not at all included in the content of this  document, and you've added it in to provide just   181 00:17:27,840 --> 00:17:32,000 additional help... additional resources to  that end user who is navigating through this   182 00:17:32,000 --> 00:17:36,960 page non-visually. If they would prefer a Braille  menu, they now have that option. And they are...   183 00:17:36,960 --> 00:17:40,960 that is well known to them because it's the first  thing that is read aloud to them. So that content   184 00:17:40,960 --> 00:17:46,800 is not actually existing on this PDF, but I'm able  to add it in without making any visual alterations   185 00:17:46,800 --> 00:17:51,280 to this document. Nothing is going to change for  a sighted user that is looking at this document.   186 00:17:51,280 --> 00:17:55,680 Text is not suddenly going to appear up here in  the top margin. It is just going to be there for   187 00:17:55,680 --> 00:18:00,480 end users who are using assistive technology, to  let them know that they do have other alternative   188 00:18:00,480 --> 00:18:07,920 formats if they would like to access this document  via a Braille menu. So that's just one other   189 00:18:07,920 --> 00:18:12,960 sort of idea that you could use it for. Perhaps  another way that you could use it is to add in,   190 00:18:12,960 --> 00:18:18,000 like, contact information for the menu. Maybe  someone shares this menu on Facebook or something,   191 00:18:18,000 --> 00:18:22,880 and there's no there's no phone number  or website or email address or anything   192 00:18:22,880 --> 00:18:27,600 available to get in touch with this restaurant.  So what you might end up doing is just putting a   193 00:18:27,600 --> 00:18:36,880 Custom Zone Source to say, you know, call us to  place your order, at you know 1-800-GOOD-FOOD.   194 00:18:39,280 --> 00:18:46,000 And then when you look at the preview down at the  bottom, now you've inserted in that extra context.   195 00:18:46,000 --> 00:18:52,400 So nothing is there in terms of a phone number  or contact information towards this restaurant,   196 00:18:52,960 --> 00:18:59,120 but you're able to add additional value simply  using that Custom Zone Source. Now the other zone   197 00:18:59,120 --> 00:19:04,880 sources... I'm going to save OCR for the very  end... But the newest Zone Source is actually,   198 00:19:05,840 --> 00:19:11,680 is actually called Actual Text. And Actual  Text and Custom have a lot of similarities.   199 00:19:11,680 --> 00:19:15,920 The difference between Actual Text and Custom  is...What you're going to want to do now is,   200 00:19:15,920 --> 00:19:20,720 you're going to want to use Custom when you are  adding something in that has no actual content   201 00:19:20,720 --> 00:19:25,520 there already. So where you place that Custom zone  matters. If you're placing it over a blank space   202 00:19:26,240 --> 00:19:32,160 on the page, you can use Custom. You can use  Actual Text to edit something that might already   203 00:19:32,160 --> 00:19:37,680 be present. So there's already content on these  in these zones. So if you use the Actual Text,   204 00:19:37,680 --> 00:19:41,200 you can actually edit what is read aloud  through the screen reader to the end user.   205 00:19:41,840 --> 00:19:47,280 So, for example, we remember this key, this  dietary preference key, at the top of the page...   206 00:19:47,280 --> 00:19:53,280 you have these like symbols for “G” for gluten  free and then this sort of creative little “V”   207 00:19:53,280 --> 00:19:59,840 looking shape for vegan, and a “V” with a circle  around it for vegetarian. Now these little symbols   208 00:20:00,400 --> 00:20:04,240 are not going to be encoded in the text  themselves. If we look at the preview,   209 00:20:04,240 --> 00:20:09,760 there's no actual indication... there's no actual  encoded text that's telling them that this is a   210 00:20:09,760 --> 00:20:16,640 vegan plate or this is a vegetarian plate. So what  you can do is you can use the Actual Text zone   211 00:20:16,640 --> 00:20:24,640 type to actually take an element that is already  there. So this market fruit and berries plate,   212 00:20:24,640 --> 00:20:30,000 it's already there. And you're able to actually  add in that. This is in fact a gluten-free   213 00:20:31,920 --> 00:20:39,520 and a vegan dish. Now nothing is going to  change in the HTML preview. So nothing is going   214 00:20:39,520 --> 00:20:44,640 to be visually altered. But when you export the  file, and you look at the actual tag structure,   215 00:20:44,640 --> 00:20:48,560 what you will see is that the what is  going to be read aloud to the end user   216 00:20:48,560 --> 00:20:52,400 is now this new information that you  have provided with the gluten-free   217 00:20:52,400 --> 00:20:57,200 and vegan dish. So you've actually taken the  time to type that in to provide that additional   218 00:20:57,200 --> 00:21:02,880 context. Otherwise someone that might have a nut  allergy or a dairy allergy or a gluten allergy   219 00:21:02,880 --> 00:21:08,080 they might be ordering a plate that is full of  gluten and they're not even aware of it because   220 00:21:08,080 --> 00:21:13,200 these little encoded, or these little non-encoded  symbols, mean really nothing to the end user who   221 00:21:13,200 --> 00:21:18,160 can't visually see them on the page. So that is  what an actual... the Actual Text is used for,   222 00:21:19,120 --> 00:21:23,760 you know, there are other practical uses for  this. Like, for example, if you wanted to add in,   223 00:21:23,760 --> 00:21:29,040 you know, dollar signs so that they're aware  that this number 10 is actually regarding... is   224 00:21:29,040 --> 00:21:34,960 actually related to the price that they're going  to pay. So you can type in a dollar sign for the   225 00:21:36,320 --> 00:21:40,480 price just to provide that additional context.  Otherwise they might be thinking like am I   226 00:21:40,480 --> 00:21:45,520 ordering 10 plates of fruit and berries. You  know it's... it could be somewhat ambiguous.   227 00:21:45,520 --> 00:21:51,440 So you can add in things like dollar signs.  Other things that you might choose to edit   228 00:21:51,440 --> 00:22:02,320 are, if we just... let's see here. This is the  element here that I wanted to talk about. So   229 00:22:03,120 --> 00:22:08,560 if you read through this specific menu item,  you get to the end here, and it's going to read   230 00:22:09,120 --> 00:22:14,720 “mushrooms, peppers, onions, tomatoes, bacon,  hammer, sausage, 15, additional toppings,” too.   231 00:22:16,480 --> 00:22:22,240 That could be read in a number of ways. Someone  might think that you can get an additional 15   232 00:22:22,240 --> 00:22:25,840 toppings for two dollars. That could be  that could be misconstrued in that way.   233 00:22:26,560 --> 00:22:30,720 So if you look at the Actual Text for  that, for this one specific element,   234 00:22:31,440 --> 00:22:35,680 (you might need to copy and paste it from  the HTML) and now you're able to actually   235 00:22:35,680 --> 00:22:42,640 paste it into this field here. And you can edit  it as such. So you could now type in the “15”   236 00:22:43,520 --> 00:22:50,080 by adding the dollar sign and then you can also  put a colon or a slash or something to indicate   237 00:22:50,080 --> 00:22:57,920 that additional toppings are now two dollars,  by typing that additional context in. So this   238 00:22:57,920 --> 00:23:02,560 is what you can use the Actual Text for. And  it is not it is not specifically for, you know,   239 00:23:02,560 --> 00:23:07,280 restaurant menus. This is just a practical  example. And what you might use it for.   240 00:23:07,280 --> 00:23:11,040 You can find... you can certainly find real  reasons to use it within your document.   241 00:23:11,040 --> 00:23:14,720 But it's just a new feature that we want to make  sure that everyone is aware of how it works,   242 00:23:14,720 --> 00:23:19,040 and what is the distinction between the  Custom Zone Source and the Actual Text.   243 00:23:19,680 --> 00:23:23,840 Keeping in mind that when you make edits to  the Actual Text, they are not going to appear   244 00:23:23,840 --> 00:23:28,160 in the HTML preview. But they will be there  in the PDF document when you export the file.   245 00:23:30,640 --> 00:23:36,080 So one other... a couple of other just practical  examples of when you might use Actual Text.   246 00:23:36,080 --> 00:23:41,920 Acronyms, for example. So if you have, like,  acronyms that are describing, you know,   247 00:23:41,920 --> 00:23:46,720 something important within that document document.  Acronyms can be ambiguous. You know, a single   248 00:23:46,720 --> 00:23:51,680 acronym could relate to 50 different things,  depending on the context. So what you can do is,   249 00:23:51,680 --> 00:23:55,520 you can take that zone that's covering up that  acronym, and then you can actually go into the   250 00:23:55,520 --> 00:24:00,320 Actual Text and type out the words that that  acronym is representing. So instead of it just   251 00:24:00,320 --> 00:24:05,920 saying “lol” you can actually type in laugh out  loud. You know, just for one random example.   252 00:24:07,760 --> 00:24:13,120 Also another way that you could use it are  stylized letters. So if you can visualize   253 00:24:13,120 --> 00:24:19,040 like a a document that contains the first letter  of the document is like a big creative “B” instead   254 00:24:19,040 --> 00:24:23,680 of it saying breakfast here. If we just had  like a big creative artistic “B” and then the   255 00:24:23,680 --> 00:24:30,480 rest of the word was breakfast, and that b is not  actually part of the... it's not part of the text,   256 00:24:30,480 --> 00:24:34,960 it might actually be an image… So you can select  the “breakfast” and actually add in the “B” so   257 00:24:34,960 --> 00:24:40,320 that will be actually read aloud correctly.  Other things might be to remove hyphens. So   258 00:24:40,320 --> 00:24:45,040 if you have breaks in words that are ending at  the end of a line, and it jumps down to another   259 00:24:45,040 --> 00:24:49,760 line ,and that word has been cut in half, you can  remove that hyphen so that when the screen reader   260 00:24:49,760 --> 00:24:54,640 user is reading it, they're not hearing two halves  of a single word. They're hearing one smooth   261 00:24:54,640 --> 00:25:00,000 word being read all the way through. So this is  exactly what the Actual Text zone source is for.   262 00:25:00,000 --> 00:25:04,640 You can probably find a number of reasons to  use it in. Ways to use it within your documents.   263 00:25:04,640 --> 00:25:08,800 I just wanted to share a couple of a couple of  examples and hopefully this kind of gets your...   264 00:25:10,000 --> 00:25:12,640 this gets you up to speed with this new  feature, and gets you thinking about   265 00:25:12,640 --> 00:25:18,560 how this might apply to you. Now the  last zone source that we want to cover   266 00:25:18,560 --> 00:25:22,640 is OCR. And I'm actually going to leave this  document. So I'm going to jump out of here,   267 00:25:24,560 --> 00:25:29,760 and I am going to jump go to the import  page, and I'm going to actually import a   268 00:25:29,760 --> 00:25:36,960 document that is in fact an OCR page. So OCR  stands for “optical character recognition.”   269 00:25:37,680 --> 00:25:42,080 And this is... this will happen when you have  a document that doesn't actually have any   270 00:25:42,080 --> 00:25:47,760 encoded text in it. So there's no text  elements within this page. It might be a scan,   271 00:25:48,320 --> 00:25:54,000 it might be an infographic that actually contains  text within that image… But what you'll find is,   272 00:25:54,000 --> 00:25:59,760 that there is no actual searchable selectable  text in that page. And if that's the case,   273 00:25:59,760 --> 00:26:04,320 what Equidox will do is it will assume that  it's an OCR situation. And you might get an   274 00:26:04,320 --> 00:26:09,040 import message that looks like this. Where it says  “there's no content on page, one sending to OCR.”   275 00:26:09,680 --> 00:26:13,920 So when I go into the document now (this  is the page that we just imported),   276 00:26:15,360 --> 00:26:18,960 when I jump into the document now, I see  now that I have an OCR little flag here,   277 00:26:18,960 --> 00:26:24,400 letting me know that this is an OCR page. And  when I open up the document, I have this big   278 00:26:24,400 --> 00:26:28,720 image zone. As you can tell there's this  large zone that's covering the entire page.   279 00:26:30,000 --> 00:26:35,680 And then behind it I actually have a layer that  is now a blue zone. There are three separate blue   280 00:26:35,680 --> 00:26:39,680 zones. So what I'm going to do is I'm going  to get rid of the image zone by hitting that   281 00:26:39,680 --> 00:26:44,400 checkbox. And now I'm just left with the text.  And now Equidox recognized that there was no   282 00:26:44,400 --> 00:26:50,160 actual text on this page so it automatically  ran an OCR process. And when I look down here   283 00:26:50,160 --> 00:26:57,440 at the Zone Source it's already preset as an OCR  zone for me. And it's given me that text already   284 00:26:57,440 --> 00:27:02,000 inside of this field. And I'm able to edit this,  or change this. If there are spelling errors,   285 00:27:02,640 --> 00:27:07,600 for example. Like the word is... it looks  like here that the “L,” the lowercase “I” was   286 00:27:07,600 --> 00:27:13,360 recognized as a one. So I can just hit backspace  and replace it with a lowercase “I” down here in   287 00:27:13,360 --> 00:27:18,160 the little text field. I'm able to make those  small edits to this page. Which is something   288 00:27:18,160 --> 00:27:24,080 to keep an eye on when you have OCR. Hopefully  you don't have a lot of OCR. This is definitely   289 00:27:24,080 --> 00:27:28,960 a challenge for accessibility. But something that  Equidox is certainly capable of handling. Now when   290 00:27:28,960 --> 00:27:35,760 you have an OCR page, you can also use the Zone  Detector and Equidox will still recognize where   291 00:27:35,760 --> 00:27:40,960 the text is located on the page. However, when  you use the Zone Detector, you will lose those   292 00:27:40,960 --> 00:27:46,960 initial results that the initial OCR scan gave  you. So if you look inside of the OCR zone now,   293 00:27:46,960 --> 00:27:52,800 there's actually no text in there. You can either  hit “convert to text,” for this one single zone,   294 00:27:52,800 --> 00:27:58,640 or on the Page Tab you can hit “OCR all zones.”  And it will OCR the entire page for you based on   295 00:27:58,640 --> 00:28:04,240 where those zones are located. So once you've done  that, you can take a look at the preview, and you   296 00:28:04,240 --> 00:28:09,120 will have... all of that text is now searchable,  selectable. Whereas before it was simply an image   297 00:28:09,120 --> 00:28:16,800 of text. So this is how we can use the OCR feature  within Equidox to kind of work around those   298 00:28:16,800 --> 00:28:22,800 problems with OCR pages, which can be quite pesky  when you're trying to make a document accessible.   299 00:28:22,800 --> 00:28:27,840 No one wants to deal with scanned pages. They  are a pain. They do take a little bit more time   300 00:28:27,840 --> 00:28:33,280 to kind of make sure that you have everything  accurately typed out and spelled correctly. But   301 00:28:33,280 --> 00:28:38,560 this is something that Equidox is capable of. Now  we're just about at 2:30. Tammy were there any   302 00:28:38,560 --> 00:28:43,840 questions throughout the webinar on anything that  I can explain further or should we just wrap up? 303 00:28:46,360 --> 00:28:55,280 [Tammy] I believe Ryan has fielded most of the  questions. It looks like there are two open,   304 00:28:55,280 --> 00:29:01,600 which I'm sure he is working on. But while he's  doing that, we could let everybody know that   305 00:29:02,320 --> 00:29:09,840 our next webinar will be in mid-February. And I  believe we are going to do a 2020 Features Review.   306 00:29:10,560 --> 00:29:18,640 Just review all of the new features that were  added in 2020, for those who haven't seen them,   307 00:29:19,280 --> 00:29:22,800 or for people who want a little more in-depth  explanation of some of those features. 308 00:29:23,960 --> 00:29:29,360 [Dan] Okay great so yeah we look forward to  February's webinar as well. So I hope everyone   309 00:29:29,360 --> 00:29:34,800 can join us, and just to wrap up, here thank you  again, everyone, for joining today for another   310 00:29:34,800 --> 00:29:39,440 Equidox Webinar Wednesday. Please feel free  to reach out to us with any questions. Or if   311 00:29:39,440 --> 00:29:44,800 you'd like more of a one-on-one demonstration  or discussion to talk about how Equidox can fit   312 00:29:44,800 --> 00:29:50,560 into your organization. Please don't hesitate  to reach out to us. Our contact information is   313 00:29:50,560 --> 00:29:57,200 readily available on our website www.Equidox.co,  or email us directly at EquidoxSales@Onixnet.com.   314 00:29:57,200 --> 00:30:00,480 So with that, I thank you very much  and we will meet again in February. 315 00:30:03,000 --> 00:30:08,320 [Tammy] Great thanks a lot, Dan. Thanks, everyone.  [Dan] Thanks, everyone! [Tammy] There is one   316 00:30:08,320 --> 00:30:16,800 question that was not answered yet, so I have  sent them the email for EquidoxSales@Onixnet.com.   317 00:30:16,800 --> 00:30:20,640 You can email there and get that  question answered, or any other   318 00:30:21,680 --> 00:30:27,440 questions. Or you can also access our  support within the Equidox software. 319 00:30:28,520 --> 00:30:31,440 [Dan] Thanks, everybody. See you next time, bye!