 And this afternoon, we're going to talk about accessible tables in Word and simplifying complex tables. And then we'll also talk about remediating tables in PDF using Adobe Acrobat Pro DC. All right, so I'm going to start this off here and go ahead and share my desktop. Great. Oops. There we go. All right. So again, my name is Davey DeYoung, and I am a member of the IT accessibility team. And I'll be talking about creating accessible tables in Word and simplifying complex tables. And later on with me is going to be Andrew Michaels. He's a student assistant of TWIT, and I'll have him introduce himself a little bit. And he's going to talk more about remediating tables using Adobe Acrobat Pro. So guidelines for formatting tables in Word. So for tables, by default, assistive technology reads a table from left to right and then from top to bottom. And if that relationship between the cells is not defined and the header, then the table is not formatted accurately. So if heading cells aren't associated with those data cells, a user can get lost in a sea of data. So the first guideline when using tables is to not use tables for layout. They should really only be used to display data. And the reason for this is because it creates accessibility barriers. Some examples of that are for users of assistive technology or screen reader users, when they encounter a table, they usually need to adjust their equipment to read in what is called tables mode to access the content. And this makes navigating a table while consuming the information a bit more challenging. And also when you're creating a table, authors can assign a header row to the table and you should and we'll talk a little bit more about that and go through those steps. But authors cannot include headings in a table used for layout. So remember that headings are a critical part for providing structural outline of content. So any paragraph styling for text is also used as navigation cannot be included in a table cell. You can format the table, but the paragraph styles cannot be included within those table cells. Another example is if the document is converted to a tagged PDF, the table structure is also converted and remediation is going to be necessary to re-tag that table and apply the proper semantic structure. So everything is going to need to be pulled out of that table and then re-tagged as a proper heading level or proper paragraph or list whatever happens, it happens to be in. And then alternatively if the document is converted to Braille rather, the document will be in Braille table format and that will need to be remediated to move the table structure as well. So those last two items really are time consuming and really can be kind of a cost barrier as well to accessible content. So really do not really frown upon using tables from layout. Simple tables, simple data tables can be made accessible in Word for Windows, but complex tables cannot and they really should be simplified for clarity. So if you have a table that is nested within a table, this can be again really confusing to screen reader users as it becomes a maze while trying to figure out the navigational coordinates while also trying to access the content. And then we're also going to go over the difference between table design and table layout in Word as well. So table layout, the table layout tab in Word. So to create a table in Word, authors go to the insert tab on the home ribbon and there they'll see a table icon with the dropdown menu. And if they click on that dropdown menu, they'll get a table gallery and there they can draw or they can create their table by selecting the number of rows and columns and then that will insert the table into the document. There's also an option to draw a table, but we recommend not doing that as this does not include the same level of table reading and navigation commands that are necessary that are needed by assistive technology users. And it's also just a really weird tool to use that it isn't very user friendly. Table design affects the look and feel of the table in Word, and it also allows for customization of table formatting. So to access the table design tab, you'll need to highlight the table first. And this is going to add two new tabs to the home ribbon. There are the table design and layout tabs. And on the table design tab by default, the checkboxes for header row, first column and banded rows are automatically checked just like we see here on the image on this particular slide. And usually leaving these checkboxes alone and using the default settings when creating a table in Word is fine for accessibility. So the checkbox for header row just denotes that the first row of the table contains headers that help identify the contents of a particular column. And for accessibility data tables, they have to have that header row to provide contextual structure and this helps AT users when they're navigating within that table. Usually the first column of that's checked that contains row headings and this can remain checked even if the first column does not include a row headings. Banded rows and banded columns alternate the background color of rows and columns but it's important to note that if you choose certain table style options. They may have a different effect depending upon the table style you choose so be aware that selecting a predefined color combo from the gallery that can affect the header row of the table. So you want to make sure to check that if you're going to do any banded rows or columns or any coloring within your table, make sure that you check and make sure that your table header is going to be accurate and we'll go over that in a second. Total row is the last row of the table and if this option is selected that means that the last row will be formatted differently from the body rows, and it's designed to summarize the rows above it. And last column applies to special formatting to the column to summarize earlier columns. Okay, the layout tab in Word includes commands for changing the entire table format and changing the appearance of individual table components such as cells and columns and rows. And the layout tab also includes access to the table properties options and this affects the functionality of the table. Table properties is where authors assign the head row of the table and also where authors can include a table summary, which is really helpful for screen reader users as well. So normally to assign a head row of the table, the user would select the table and then select the layout tab from the ribbon and then select the properties icon, and that will launch the table properties dialog window. In the table properties dialog window, you want to select the row tab. And this is the image that we see here on the slide. This is the table properties dialog window with the row tab exposed. Now, by default, I have the options section on that table properties window then closed in a red rectangle. And by default, the checkbox option for repeat as head row at the top of each page is not selected. So what you want to do is you want to select that check mark and that in that box and that's going to assign the top row of your table as the header row, and it defines the relationship between the header and the corresponding data. You also want to make sure to uncheck the box that says allow row to break across pages. A good table really should not contain a data cell that spans more than one page. So on checking that box will force it to stay within that one page. Continue. So essentially you want to mimic what we see here on that slide. You want to uncheck allow rows to break across pages and then check the box that says repeat header row at the top of each page. Now if you want to include a table summary, which is very helpful and assists assistive technology users by providing meaningful information about the table. Within this table properties box you select the alt text tab, and then you can enter in a short description of the table in the description field. There's also a title field under that alt text option, but you want to leave the title field blank and just include the information about the data table in the description field. Okay. So steps for simplifying complex tables in word. You always want to keep a table's title out of the table itself. You want to keep an assistive technology user to read the subject of the table before deciding whether they want to go to the trouble to read the data inside. And this also provides a way for a user to scan through the document faster as while using heading levels to to determine where they are within the document. You want to make sure that it's keyboard accessible. You can place your cursor in the first table cell and then use the tab key to emulate what it's like for screen reader that would move through the table. Does the, does the cursor move in a logical manner and does that flow makes sense. Step three is the text legible. If you're using banded color. You want to make sure to double check the background and make sure that the text in the background have an appropriate level of contrast. And you want to make sure that you define the header is the header cell text visually different than the data cells. And then step five, assistive technology does not understand empty split or merged cells. So when making calculations to get to the user which can be confusing. So you really should avoid empty cells, merge cells or split cells. Okay, so I'm going to provide a demonstration here in word and you want to make sure that when you're creating tables and word that you're using the desktop client. The version of word can't create accessible tables as there's no way to view the tables property table properties options and define the table header so it's really important that if you're creating word documents that have table tables in there that you're including that you're creating it from from the desktop client. So here we have our document that we use for demonstration purposes this is our regular document here. And you'll notice that I have my regular table, a very simple table here it has three columns and eight rows so nothing to difficult about this. And again just for review in order to create a table, you would simply go to the insert tab. And then from the table drop down menu here's your gallery and then you can just start drawing a table. Simple insert sit there. I want to review with you guys, the the assigning that top row as your header row. And again to do that you would select the table. And when you do that I want to do this again. I want to show you here up in the ribbon here when I select that table, there's going to be a couple of different options that show up. So I've got table design, and this is where those checkboxes are located. Then I have these banded row options and I can choose colors if I want to not going to in this particular case. And then if I go to the layout tab which is also also appears when you select the, the table itself. You'll notice here that I have this properties icon, and if I click on that that's going to open up the table properties dialog box. So you can click on this row tab. And again this is the default setting so the options are. The options for this are the first checkbox says allow row to break across pages you want to uncheck that, again, a good table cell should not span more than one page. And then you want to check the second checkbox that says repeat header row at the top of each page and that's going to automatically turn that top row into your header row. So if I go to the alt text tab, I can enter in a description here and this will be simple table with three columns, and eight rows. And that gives information to assistive technology users about this particular table and informs them that this is a simple table and it's pretty easy to navigate. So no problems with this particular table. We're going to scroll down here and take a look at this other table here. So down here I have a more complex table I've got merged cells. And I have my heading in my table. And I've got all things, all kinds of different things going on here. I also wanted to point out down at the bottom share of my word window I have. Excuse me I have this little indicator here that says accessibility recommendations found click here to investigate so I'm going to go ahead and click there and see what it says. So I've got some accessibility warnings, and they are specific to this table. And it says that there are merge or split cells in the table. Now if I select that particular warning, it's going to tell me exactly where in the table in this document where, where that warning is. And then it's going to give me some information as to why this is an issue. So why should I fix this. It says here tables should have simple structure so that they can be easily navigated and understood by people with disabilities. Merge or split cells can cause unexpected navigation issues. And then it says steps to steps to fix, test and simplify the table structures like the first cell and then press the tab key repeatedly to make sure that move focus moves across the rows, and then down to the next row. The third step here is change cells that are merged or split cells, as needed by selecting merge cells or split cells button from the table layout tab. So I'm going to go ahead and check what it would be like for an assisted technology device or screen reader how how it would interact with this particular table just by pressing the tab key so first of all I'm in the top section, the top row there where it says grades. Try that again. Okay, and then from grades it takes me to homework. And then from there it goes to exams, and then projects, and then it goes back to homework. And then it goes to that second column there with the number one, and then the third column with the number two, and then final. And then what is that the fifth call or six column with the number one, seventh column, number two, and then eight column with the word final. And then it announces 15%, 15%, 15%, 20%, 10%, 10%, 15%. Now, it's important to note when using JAWS or screen reader on a table like this. It will announce right from the get go that this is a non uniform table. So it informs the screen reader user that this table is not a simple table that there are merge cells and indicates that okay I need to do some, some navigating around in these cells and kind of get the relationship to the different words and and and how they are associated within this table. So, in, in this particular case a user might go back and forth several times to try to figure out, you know, is this exam, is this for exam one or project one, and then is, is that 15% of grade for homework, or for exam one or for exam two. It's really difficult to tell when, when you have all these different merge cells that are happening in this particular case. So how would we simplify this table. Let's scroll down here and give a couple of different examples. So first of all, I definitely want to take out the table header in this case this is great so I'm going to take that out of the table and I'm actually going to assign that as a heading. And then you can also kind of visually see how these particular tables would be chunked out. And so I've kind of given a diagram or or a chunked out version of that particular table and it chunks out very nicely into three different tables. So you can see here that I've still got this for exams and projects I still have some merged cells here, and that's still going to cause some problems for screen reader and assistive technologies. So I've got a more simplified version down here I still have grades as a heading level two. And then I've taken these headings out and I've signed those as a heading level three so I've got homework, but then I have this 15% in its own table cell there, which isn't horrible but it's a little odd. And then I have exams as a heading level three and then I have a very simple table here that I can assign my header row to this top rows, as well as this top row and for four exams and projects. So let's simplify is it even more but maybe doesn't look all that great. So I've got a third option here. So in this case, I'm not using any tables at all. What I've done is I'm actually using the columns options so I can show you this by turning on the non printing characters, or the show hide option for the non printing characters and I can see here that this is a section break. I want to highlight this and then if I go to insert. I'm sorry it's an under layout, and then I go to columns I can see here that I've turned this into a three column layout, which is more visually pleasing and kind of mimics the original table itself. But in this case I'm not using a table at all. I just turned that I just written out some text and then I've turned it into a three column, three column item there where I have homework separated from exams and separated from projects, and a screen reader user is going to be able to navigate to each one of these items very easily because I've created heading levels for for each one of these items here so again grades is adding little to homework exams and projects heading level three. So really easy to navigate to those areas. And then the screen reader will read it in successive order from there. So that's pretty much it for creating or for simplifying rather more complex tables in Microsoft Word. And I'm going to go ahead now and stop sharing. Oops. Stop sharing. And then I'm going to hand it over to Andrew. My name is Andrew, and I'm going to be going over the table editing methods in Adobe X about DC now, but first a little bit about me. I'm a third year at UW in the informatics program, and I've been working as the employee student assistant for around a year now. And a little bit about what I do is I work with Adobe about, and I remediate online documentation so that the structure of the document as well as the type structure is in a better way that a screen reader can go through the document correctly. But now I'm going to go ahead and get into the table editing methods. So the first one I'm going to talk about is the table editor. And the table editor allows us to visualize the table structure and data cells of more simple tables. And it also allows us to define each column header or row header, and the span of these column or row headers for either one or many cells. And I'll show a few examples of this in the demo soon. But the table editor can also be accessed through the reading order panel of the accessibility tools in Acrobat. And the nice thing about the table editor and table cell properties is that we're offered a really user friendly UI that allows us to define the scope of different column and row headers as well as the row scan. And the second method I'm going to be talking about is the edit attribute object function. And this function allows us to create more complex table structures rather than the simple ones that would be represented by the table editor. And it's also much safer to use this function rather than the table editor as if you mess up defining the span of a column header using the table editor. That can result in a malformed table, and many times this would result in needing to roll back the document to a previous save to get that table structure back correctly. However, I would say the one drawback of using this method is that it's definitely a little bit slower as we would need to define the scope and span of data cells manually for each cell. And then again, the edit attribute object functions can be found through the properties menu of each tag. And once we select the edit attribute objects function, you'll be offered a menu to manually put in the column scan as well as the scope of each header. And then just before going to the demo, I'm just going to talk about my own general workflow when I'm working with tables in Acrobat. The first thing I usually do is just try to determine how complex a table is using the table editor. And if I see some malformed data cells, then I'll go on to step two and bring out the edit attribute objects feature, which will allow me to edit more complex tables. And while going to the tables, the first thing I always do is make sure that I remediate the column and row headers first. That way I know how the content within a table aligns under each column or row header. And then the fourth thing I do is I make sure that I place the content in the table directly with me directly underneath each table cell. And as we'll see in the demo that I'm about to show, sometimes Acrobat adds extra tags within tables, such as perk up tags that we'll need to get rid of. And then the last step I have here is just a double check, but just making sure that all the header and data cells are tagged correctly and placed in the correct table row just to ensure that the table structure is tagged correctly. And just a brief overview of the demo, I'll be using the table editor to demo on a more simple table structure, and then I'll also be using the edit attribute objects feature on remediating a more complex table structure. So I'm going to go ahead and change my screen to Acrobat. Here I have the physics core syllabus in PDF form now. And I'm going to go ahead and start by remediating this first table here, which is the class schedule. But before I get into the table editor or the edit attribute function, I just want to make sure that we all understand the tag structure. And this table can be found in the tags pane, which is represented by this icon on the left. And clicking it will be able to see all the tags in this document. And it will be under this first table type here, which highlights all the tags within this class schedule table. And if we open up the dropdown, we're going to see the first two types of C is T head and T body. This T head tag here holds groups of heading, as we can see it highlights week topics and reading assignment. And then the T body tag holds the rest of the content. And the one thing to note about these tags is that they are actually optional tags. It would also be perfectly fine to just have the table row and the rest of the table row headers directly beneath the table tag. However, adding in this T head and T body just makes it more obvious where all the headers and all of the other content is within this table. And then the table rows TR represents table row and it just shows each row of table data cells. And then going one step further, if we open up each table row, we'll either see TH or TD. TH representing table header and TD representing table data cell. And those just show individual table cells within the overall table. So now that we have a better idea of how the tags are represented in tables, I'm going to go ahead and find the table editor to determine how complex the table is. So to access the table editor, we go to the accessibility tools in Acrobat and we can click on it. And we would need to go to the reading order option. You can click on this. When you first open the reading order, the table editor actually won't be activated. We'll have to first select one of the tags. So I'm just going to click on this one here. And now we can click on table editor. And as you can see, this table is pretty well represented by the table editor as it's a less complex table. So I'm just going to go ahead and use the table editor to start with these column heading here, week topic and reading assignment. If I click on week, I can right click and click on table cell properties. And this will open up that menu that will allow us to define the scope as well as the stands. If we click on the scope to be a column, this will define a week as a column header. And the row stand and the column stand by default is set to one. So I'll just leave this as one as we can see in the table week only stands one column and one row. And then we can just click OK. And this column header will have been remediated correctly. And the nice thing about the table editor is that we can actually edit multiple column headers at a time if we know that the scope and the stand will be the exact same thing. So I can just click on topics and then I can shift click reading assignment and that will select both column headers. And if we right click and click table cell properties, I can edit the scope and the stand for both of these cells at the same time. So again, I'll just change scope to column and I'll leave row standing column stand by default one because each of these column headers only stands one row and one column. And I'll click OK. And then the next thing I'm going to do is define weeks one through seven as row headers. And again, I'm just going to shift click all of them to select all of them because I know that the scope and the stand is going to be the same for each of these row headers and right click and click table cell properties. But this time the scope I'm going to define as row because I want each of these week headers to be defined as row headers. And then again, I'll leave the default rows down to one and columns down to one and click OK. And then the next thing I'm going to do is check for those extra tags within each table cell. First I'm going to close the table editor by clicking reading order and then the X in the top right. If I open up this first cell here we'll see there is a paragraph type here. And if you open that paragraph we'll see the actual content of week which is highlighted here. We don't need this paragraph tag. We want the content to be directly beneath the table header as we don't want the content to be represented by a week within the paragraph within the table data cell. We just want the content to be directly beneath the table data cell here. So we can just delete that paragraph tag. And unfortunately it will need to do this for every single table cell within the table, whether that be a table header or a table data cell here as well. But for time sake I'm going to move on to the next example I have down here. Just a note that we would need to do that for each table row and going through each table data cell to make sure that we remove those extra paragraph tags. I'll close this table here and I'm going to go ahead and go into this next grade table. And just visually looking at it we can see that it's a more complex table. If I open the table editor by going to reading order. And then again clicking any of the tags to activate the table editor. Selecting table editor. A lot of the cells are actually represented. Okay. But as you can see on the left here, the homework column headers here is a little bit not formed as you can see it's separated into two different cells here. So that's pretty much telling me that it's time to use the other attribute objects function. So I'm going to close the table editor. And I'm going to go ahead and find this cell within the table tags here. So open the drop down, and then open the table header to head drop down and try to find that within the first table row. And as you can see, this table header cell holds the homework column header. And to open the edit aspect objects function, we need to right click on this tag and go to properties. And then the edit aspect objects function to the sound in the middle at the bottom of this drop down for object properties and click on edit attribute objects. And the first thing we need to do is define a new item. And this will allow us to create a new attribute object. And essentially we're doing is we're adding attributes to this column header here. And if we open up the drop down for added attribute object one. Acrobat will, by default, think we're editing the layout of this column header, but we need to make sure we change layout to table, because we want Acrobat to know that we're trying to edit a table object rather than a layout. Then the next thing I'm going to do is manually define the scope for this column header. So again, I'll click as route object one, and then new item, and we'll be offered this menu for adding a key and value pair. The edit attribute function is very similar in how a dictionary works, where we have words mapped to definitions, and the key being the word and the value being the definition. In terms of defining the scope, the key would be just scope and the value in terms of this case would be column. And this would define homework as a column header here. And value type we can just leave as name. And the next thing I'm going to do is define the column span for homework. And then again, clicking attribute object one, new item. This time, instead of scope, I'm going to put call span as that's the key that needs to be used to find a column span. In the value, I'm just going to put one as homework only span one column. But this time the value type will need to be trained to integer because one is an integer. And then we can click OK. The last thing that needs to be done is to edit the row span of the homework header. As you can see that this headers here span two rows. So clicking on attribute object and then new item again. Instead of call span, this time it will be row span. And the value will be two because the header stands over two rows. And then again changing value type to two for the integer value. And then clicking OK. That then we can click OK again to close the menu and then close the option properties. And just to show how the structure of the table has already changed. I'm going to just show it in the table editor again. Clicking reading order and then clicking one of these types of table other. As we see now this homework header here does not split into two different cells and it's just one cell that spans one column and two rows. But the next thing I'm going to do now is edit the next headers in that first row. So exams and projects. And again I'm going to show. Remediating these header is within the edit attribute object. So the first thing to do is to select the exam column header right click properties. And then click on edit attribute objects. Then the first thing to do is click new item to create a new attribute object. And open this drop down and make sure to change layout to table because you want after about to know we're editing a table object rather than a layout. And then click OK. And then we're going to define a new item again for the scope. So you put the key scope and the value as column and this will define exams as a column header. And then click OK. And then the last thing to do is to find the column spam. So we'll have to create a new item again. And this time the key will be call spam to a value of three as exam stands over one, two and final and changing the value type to integer. And that will be all we need to do for that column header and then click OK and close. And then we're going to do the exact same thing for projects. We go to properties and attribute objects, create a new item, change layout to table. Then click on attribute object again and click new item and change scope and the value to column. This defines project as a column header. And then we're going to find the column spam to just three and an integer. And you can click OK to close up the menu. And then the last thing to do is just to again take out the extra paragraph tags. And then I'm going to move into the next table row for the subheadings for one to final and one to final. Right clicking on the data cell going to properties, add attribute objects, create a new item and open the dropdown and change layout to table. And click new item. I'm going to first define the scope for one. And it's going to be a column heading. And then make a new item again for column spam and make the value one as an integer because one only stands over one column and click OK to close this. And then we're going to have to do the exact same thing for the next five column headers. So go to edit objects, create a new item, open the dropdown, change layout to table because we're adding a table object. Then click on attribute object again to create a new item. The time the key will be scope because we're trying to define the scope first for this column header. And then make the value column. And then the last thing for the column spam is to use the key call span over one column and change value type to integer. And then we can click OK to close up the menu. And then we're going to do the exact same thing for final. Open up edit attribute objects, create a new item, change layout to table, new item, and then change the scope to column for a column header, and then change the column span to just one of an integer. Click OK and close out the menu again. And then we'll have to do the same thing for the next column header for one. So go to edit attribute objects, create a new item, open the dropdown, change layout to table because we're adding a table object rather than a layout. Click again on attribute one new item. And we're going to find the scope to be a column scope. Click OK. Then the column span, we're going to define that to be just one in an integer. And then we can close that out. And then for two, we're going to do the exact same thing. We're going to edit attribute objects, new item, change layout to table, and create a new item for the scope. It's going to be a column scope. And then do that again for the column span of one integer and click OK. Close that. And then for the last cell for final, we're going to do the exact same thing again, where you create a new item, open the dropdown and change the object to table. And then define the scope to be column. And lastly, define the call span to be just one. And click OK. And we can close that out. And then looking at the tag span here, we can see that the each of these cells is still defined as a table data cell. What we need to do is just change TV to TH and think about just double clicking and changing the B to H. And this will just change it to a table header rather than a table data cell. And I'm going to go ahead and do that for each of these cells. And then the last thing to do is just get rid of this extra table header here because it's unused by any of the content within the table. And then again, going through each of these types and taking out that extra paragraph time to would also be necessary. But I have one more example, so I'm going to go ahead and move into that. But first, if we check the accessibility checker, we can see that the tables do account for each of the accessibility checks for the table accessibility checks. But moving on to the last example I have here. It's this coffee table here. And it's in a way similar to the last table that I was showing where it's a generally a pretty complex table. And just to prove this point, if we open up the table editor, which can be found in the accessibility tools under reading order. And then just click on any of the tags to activate the table editor. Some of the table cells are represented quite well by the table editor. Whereas the row header here for arabica definitely cannot be represented in any way by the table editor. So this would cost that we need to use the added actual object function. So I'm just going to go ahead and go through each of the rows from top to bottom for each of the headers. So I'll first try to find that copy header in this first table row here. And then I'll right click on the tag, go to properties and go to edit attribute objects. If we're lucky, Acrobat will actually have already defined an attribute object for us, which we can see here. And all we need to do is just change that column span to five. Because as you can see columns, this first column here for coffee stands over one, two, three, four, five columns. If we click OK. And then the last thing we need to do is define the scope. So again, clicking on attribute object one and then new item. And we can just type in scope as the key. And then value of column because it's a column header and click OK. And that's all we need to do for that first heading. Then going into the next row. This row is a little bit more complex. As you can see, there's actually a place holder seller here that spans over this row header for arabica as well as this for a second column here. And the way to remediate this place holder cell. We first open up the attribute object function. And instead of spanning over one column, we would change the one to two so that the Acrobat knows that this place holder cell will span over both arabica and this second column here. And the last thing I would do is just make sure that the scope is defined. We click OK. And then we can close out that attribute object. And then I'm going to go and edit origin type and notes as well. Going to the edit object again, click a new item and again changing layout to table. Just so we ensure that Acrobat knows we're editing a table object rather than a layout. Then clicking on new item to define the scope to column. And then to define the columns again, click a new item again. And the key this time is call span. And just a value of one integer. And we can close out the attributes for that column header. And then for type, we're going to do the exact same thing. Click a new item, open the dropdown, change layout to table. Click attribute object. Click new item and define the key at scope and the value at column. And click OK. And then to define the column span, new item again. This time of the key will be call span, so value of one integer. And then we can close that again. And lastly for notes, we'll do that exact same thing. We'll define a new attribute object, open the dropdown and change layout to table. Then again click attribute object, new item to define the scope of column. And lastly to define the call span. We're going to do a new item call span of one integer. And click OK. And click OK again to close out all those menus. And then we can just take out the extra tags again. And then we'll be able to move on to the next row for the Arabica row header. So you can see it's the content for Arabica as whole in this table data file here. So you just right click, go to properties and add an attribute object. And then create a new item, change layout to table. And then I'm going to define the scope now. So I'm going to make a new item, the key at scope. But this time the value will be row. As we want this cell to be represented as a row header and I'll click OK. And now I'm going to define the row span by clicking on a true object and clicking new item. And the key will be row span rather than the call span that we've been using for a lot of the other headers. And then I'll change the value to be however many rows that this header stands over. So it goes for 1, 2, 3, 4, 5, 6, 7, 8, 9, 10. So we just put a value of 10 here and change value type to integer. And that's all you need to do for that row header. And then making sure that we change this table data cell from TD to H. So that I can about notice that this is a table header. And again, taking out the extra tags here so that the content directly beneath the table header here. And we need to do that for each of the table data cells in every single row. But we have to go through each row here and do the exact same process. But for time sake, I'm going to show one less example for the row header on the second page here. For this row header here, we would need to find this header within one of the table rows. It's in this one here. You can just open up the dropdown, click on the first table data cell, right click, go to properties and go to edit actual objects. Create a new item, open up the dropdown, change the table, again click on actual objects, new item. And again, we're going to define the scope first to be a row scope as you want. This header is going to be defined as a row header, click OK. And lastly, defining the row span. So we're going to use the T of row span. And then we're going to make the value 5 because this row header stands over 5 rows. We're going to click integer and OK to close the menu. And we won't need to redefine the column headers because we'll be using the exact same column headers that are used on the first page of this document. And then lastly, just changing the TB to TPH and taking out the actual content. And if we press the accessibility check, we'll see that we do pass all of the table. Accessibility checks. However, the one thing to note is that the accessibility check or an acrobat does not check for those extra paragraph types. So that will have to be a manual check. But that is what I have for the demo. So I'm going to stop sharing here. Thank you so much, Andrew, for that. That's a great example of how challenging, excuse me, how challenging it is to remediate documents, especially when they have more complex elements such as tables. So I wanted to, we've got some time left, so I wanted to address some questions that we have in the chat. Amy asks, when you run the accessibility checker and a warning shows up to check a simple table, is that just a warning to make sure that the table navigation is correct? Or is it a definitive indication that something is wrong with the table? I've interpreted it as the form of wanting to double check. So that's a great question. So the accessibility checker in Office 365 usually places things in three different categories. Errors, warnings, and tips. So if there's anything in the error category, that is going to potentially break the accessibility of the document and somebody who's using assistive technology might have an issue, a particular issue with moving forward if there's an error. For tables with merge cells, that's considered a warning. So it's not necessarily going to break the accessibility of that document with that table in there. But it is, it's definitely going to cause some issues. So as I mentioned earlier, when someone's using JAWS to navigate a document, and they enter into a more complex table, it will announce right away that this is a non-uniform table. So that kind of reinforces that error or the warning, rather. So it doesn't necessarily break it, but it's going to make it definitely more challenging for somebody who uses assistive technology to interact with more complex items under the warning category. Hopefully that answered that question. And then another question we have, will the columns be the red left to right? So I'm assuming this is during the example where I showed simplifying more complex tables in Microsoft Word. The last item I showed was homework, exams and projects in three columns, rather than in a table. And it is what I've actually done is I've linearized that and just turned it into a three column linear text. And so yes, it will effectively read it from left to right, but really what it's doing is reading from top to bottom. I've just reorganized the flow to be into three columns instead of from top to bottom. So it's just a reflow of that particular text. So it will read it in that accurate order. And Susan says we have users that request tables for accessibility with reading comprehension. Is there a way to have tables be skipped over by screen readers? If so, then we could maybe include the information in both columns and table. I don't know that there's a way to turn off tables being recognized by screen readers. I don't think that there is. And screen reader users can choose to not enter a table. They can skip the table if they want to. So if you wanted to present the information in two different ways, either columns or headings, you might want to let your students know that the same information is presented twice. And then they can have the option to skip the table and then just treat it in a column if that is more particular preference. And the channel asks, how do you know what keys and values are allowed for PDF attribute objects? Do you have a reference guide that you consult for all of these details? Andrew, did you want to answer that one? Sure. I'm pretty sure there are references to guides out there, but for the keys and values that I know, it's just the ones that I showed in the demo which scope as well as the column span or row span ones. And then for the values, just however many rows the column or the row header scans over. Yeah, I'm pretty sure there would be some reference out there, but as far as I know, it's just those are the two keys that I know that are used primarily for tables. Okay, great. I actually put a link in the chat. This is a link to the PDF association. And it is a link to their tag PDF best practices syntax guide. And it does have all of the information in there as far as values and keys for those particular items for that attribute. So it should have more information in there if folks are interested in that. And then, Charles has a very good comment. This extraordinary, the extraordinary complexity of this process is why we strongly encourage folks to use HTML whenever possible. So yeah, so you guys got a real live view of the complexity and the time it takes to remediate, you know, tables that weren't really that completely complicated but there's a lot of steps that need to happen in order for the information to be announced. Accurately. So there's there's a lot of work that needs to be done there. Lori says, does what you just showed us impact reading with the keyboard tabbing. So it shouldn't I'm assuming where you're you're referring to using tab in PDF, if you're trying to navigate in a PDF document or a table. Okay, yeah, so the answer. Yeah, so it should not affect the tab order. It's primarily just to associate for screen readers, different row and different column headers so when the information the data is in is announced, it will be announced with the correct context with the row header and with the column header and row header if that if it has a row header associated with it. And then Joe says if HTML is strongly recommended, are you suggesting that most things be web pages and not word docs or PDF. Yes, that that's what we are recommending. That is what we are suggesting if you can present the information in HTML. It's far more accessible and easier to to navigate a HTML web page than it is word document or PDF. As you know, kind of shown throughout this afternoon there are a lot of inconsistencies with how jaws announces content in word and PowerPoint and PDF. So if there's an update, you know, it kind of changes the behavior of jaws and so we kind of have to reevaluate, you know what, what is happening what is the behavior that we're seeing. And, you know, is this something that we need to make note of so those kinds of inconsistencies and challenges aren't as evident in HTML as as we see in electronic documents. Okay, so we are right at four o'clock and the end of global accessibility awareness day so I want to thank everybody for sticking around and if you stayed for all of our sessions today. Congratulations that's that's quite a marathon for for everybody so thanks again for everybody who showed up today. And again, this information will be posted on our on our website. Hopefully, fairly soon, and join us again next year for global accessibility awareness day 2023. Thanks everyone.