Please stand by for realtime captions. 
 Hello. This is Bill Erickson. I would like to welcome you to this webinar. I would also like to thank our sponsors. 
 Our partners in this project include the employee disability Institute at Cornell and the policy of -- Department of -- the American Association of people with disabilities, and Rutgers University school of management. 
 As mentioned, -- the funding. 
 We are very lucky to have with us today. Smith. He is the -- he has over 13 years of experience in working with web design, development, accessibility. He brings knowledge and experience to help others maintained highly successful web content. You see his extensive knowledge, he has provided training to thousands of developers throughout the boroughs. Much of his within work is on the AIM website. If you have any questions, submit them through the web chat. Depending on the question, he will present them at the beginning or the end of presentation. With that, I would like to hand the presentation over to Jared. 
 Thank you. I appreciate the introduction. I am thrilled to be here to talk about web accessibility. As Phil mentioned, web AIM is passionate about web accessibility. This is what we do. We try to help the compliment and maintain web accessibility. We use website evaluations and training in things like this for awareness and dissemination. We have been doing this for 11 years and we have worked with people from everything from small nonprofits to Fortune 500 companies. We are excited to be able to spend the next time talking about web accessibility and focusing on some of the implications for the employers. 
 We invite you to check I -- check out our website. It is a wealth of information that is out there that I think would be a good help to you as you really dive into web accessibility. WebAIM. 
 I think it is important to start with a good definition of accessibility. This is the one we like. It is the development of information systems possible enough to accommodate the needs of the broadest range of future is -- users -- with garlands of age or disability. We are talking about giving people a chance and an opportunity. Regardless of age or disability. We know that from the 2000 census that about 20% of the population has a disability. That is pretty significant. That is one in five Americans will be disability. Many or most of those will be age-related issues. I think this is also significant when you consider the ever increasing age of those that are using the web. We know that 8 1/2% of the population has disability that would affect their ability to use the computer or the web. You might look at it in half percent and say -- that is not very many -- or at that is a lot -- regardless, I think it is significant. I think that for most of you that have websites or people that build and maintain websites or if you aren't a developer your self -- most websites tend to spend some amount of time ensuring that the website is going to be compatible with various web browsers. You have probably spent time in shoring compatibility for web browsers that are used by less than 8 1/2% of the population. Why wouldn't you? If you could spend a little bit of time and expand your content to that percentage of the population, why would you if it is reasonable to do so? I would make the same argument about accessibility for those with disabilities. I think that the 80 to have percent is significant. Another way to look at that -- instead of just expanding what it is that you to do that additional aid in a half percent of the population,if you consider, the Reverend. now is really no  all that accessible. There are a lot of difficulties and frustrations for those with disabilities in at interacting. Those employers and vendors and those in education -- the people out there that are providing highly accessible Web content for people with disabilities is going to -- if you really focus on that in a half percent of the population and provide accessible Web content to them, you can target that audience. 
 To give you an example, a few years ago, there was a symposium on accessibility of touch screen devices. It had some of the most early and minds trying to discuss the issue of touch screen devices and how they could be made accessible. The result of this was that the touch screen devices are a black hole of accessibility. They cannot be made accessible. Shortly, Apple released the iPhone and built-in are very high levels of accessibility for blind users. It turned the whole notion on its head of accessibility in touch screen devices. The iPad is very accessible to those that are blind. If you consider that -- if you want a fancy phone and smart phone that does all these interesting things, what are you going to do? Will you purchase a phone that is not accessible to you or will you purchase a phone that is accessible to you? 
 That is a no-brainer. For the most part, if you are blind, chances are that you are most ugly to buy an iPhone. Apple has seen that vision. In fact, if you go to the iPad website today -- you will see that there are six or seven things that they've market. They have seen that vision of expanding the market and really focusing and targeting and marketing to that population. Who would not do anything to have a niche market of 8 1/2% of the population? Perhaps that is a different way of looking at that. 
 Someone asked a question in the chat -- it is really international. We have hard numbers from the US from the 2000 census, but other studies have been done internationally and the numbers are pretty much consistent. About 20% of the population has a disability and about in the how percent has a disability that might effect.. In that number often is excluded people with cognitive disabilities -- we will talk about this. Actually, the number may be quite higher than that in half percent. 
 -- 8 1/2%. 
 With this definition, we also need to consider that accessibility is a continuum. You can always make your website more accessible -- this means it will not always be perfectly accessible to everyone. That is okay. We understand that there are constraints. You can make something perfectly accessible to everybody. We want to be continually expanding the accessibility of our website. We want to a move along the continuum of accessibility and expand the potential for users to access our websites regardless of age or disability. It is important. We view that as a continuum when someone comes to us and says that their website is accessible -- that does not mean very much. You have to quantify accessibility. Accessible to home? Accessible to what level? That is where Web excessive the -- Web excessive ability guidelines come into place. They are measures of accessibility along this continuum. They are good ones. 
 We will talk about these guidelines. There is a bit of a progression that happens. The first on the list is WCAG -- there is the web content accessibility guidelines 2.0 and the others. We will talk about each of these. 
 WCAG 1.0 -- this is a set of international standards that was formulated by the W3C. It is important to know that it is an international set of guidelines formulated by the group that makes the rules for the web. They have a lot of Probert programming that happens on the web. They also have accessibility guidelines. 
 Version 1.0 was finalized in 1999. Think for a moment about what you were doing on the web in 1999 or with what the web was doing. This was the horse and buggy days of the web. It was a long time ago. The web has changed significantly. It has innovative so much. That should be your first indicator of potential and choose -- it is almost 12 years old. These guidelines are very check point driven. They were about -- there were 100 checkpoints. You could check them off. Yes -- I have done all of these things -- check on them off. Fill in everything. You can save my website is -- accessible? Not necessarily. It is just compliant with the set of guidelines. It has reached one measure along the continuum of accessibility. That is important to know. 
 It was checkpoints are in. That was pretty nice. That meant that you could go through and make sure that you have done the individual to points and it is fairly easy to measure and implement. Within 1.0 there were levels or priorities -- this meant that the checkpoints were divided into different groups. The level a checkpoints -- -- level A checkpoints -- if you did not meet that -- you would exclude someone from the website. On the level AA, if you did not reach them -- you would have frustration or difficulty for someone to access your web content. 
 Then, the level AAA guidelines -- they were a wish list of accessibility. For expanding or enhancing accessibility beyond a minimal level. 
 They were very specific to HTML. If you consider the web in 1999 -- we were building fairly standard webpages with texting and formatting a little bit of presentation and images. We do so more which more than that today. That means that some of the guidelines do not really all apply to some of the new renovations on the web. -- It was very significant in the first thorough comprehensive set of accessibility guidelines, but because of the structure and the focus of these guidelines and the fact that they are now about 12 years old, they are not the best place to be looking right now. 
 So we just moved to section 508 -- this section is federal law. It is in the rehabilitation act. In 2001 -- it is like the model T. Ford days of the web. It was still quite a while ago. Again, because of the basic this -- they are tending to show their age a little bit. Section 50 weight was very legal analyst it -- it was very easy to verify. In section 508 in regard to the web -- and there are other guidelines that apply to other things like hardware and software -- in regards to the web -- there are 16 checkpoints. This means that if you do these things, your website will be compliant in regard to this. It is very easy -- go through and check everything -- then your website is not necessarily acceptable, but it is compliant with section 50 weight. It is very limited in scope. There are only 16 things required. Probably the most significant thing I can think about that -- it means that your website can be section 508 compliance, yet still be very accessible to people with disabilities. Potentially because of that, it could still be discriminatory. It is important that we make that distinction. We consider this continuum of accessibility -- section 508 is not very far along. But, it is big come in many ways the de facto standard because of its application in the federal government. Let me clarify that -- it applies to pro Kermit and federal government. -- Procurement. 
 The really ability should act applies to federal government procurement and purchases. And not much more beyond that. What we have seen over time is that the checkpoints or guidelines within section 50 weight -- section 50 weight have been implemented in other areas. They have an additional scope beyond the federal government. 
 Example would be federal funding. In many cases, the government will say they will give you money to do something, but whatever you -- you have to meet the requirements of section 50 weight. -- 508. It means that the checkpoints will apply to you. It is important to understand the distinction. Many states have come along and adopted owes checkpoints they may have made some minor changes and made it the state law. That does not mean that section 508 applies to state government and state higher education institutions. It means that it is the guidelines apply. This is an important distinction. 
 I may have lost my -- please indicate if you have lost the slide. Give me one moment please. 
 I am not sure what will happen -- let me set this up as best I can. It will take a second. While I get this setup, you can post them in the checkbox. 
 Hopefully, you can see the light again. I will assume that you are. I will continue now.
 Section 508 right now is currently in the process of being updated. Within the next year or two, we will see significant revisions to section 508 -- the real ability should act -- it will expand the checkpoints to be closer to the deadlines of what we see in the current guidelines. WCAG 2.0 Was finalized and December 2000 and. It is much newer. It is up to date. It is applicable to us. 
 They are very principles-based. That means that they are more technology agnostic. They are high level guidelines rather than specific guidelines. They talk about -- these are the types of things that have to happen in order for websites to be accessible instead of saying that these are the types of things that you have to do with your web form. That is useful because the design of these guidelines -- they are structured in a way that hopefully over time will not become dated. As technology choose -- as technologies change -- some of the guidelines would still apply as technology changes. I do not think we will run into the same issues that we have with 1.0. Those do not apply really well to the newer technology. The difficulty with this approach would be guidelines that because they are fairly principled basis it is difficult for you to sometimes figure out -- I am building a web form in HTML -- what should I do? Sometimes it is hard to build the gap between the principles-based guidelines that what you are doing specifically and technology. There are a lot of resources and tools out there that can help you bridge that gap. It may be a little less approachable when used in the high level language that is a little bit difficult to understand. 
 It is intentional. They have done that so that they will have a long shelf life. These guidelines also maintain the levels of A, AA, and AAA.
 So with 2.0 -- this is today and the future of web accessibility. We strongly advise all of our clients -- if you are considering accessibility right now, you should be looking at the web content accessibility guidelines version 2.0 and at least looking at the A end AA guidelines. If there are things that you can do to enhance accessibility -- why would you not want to do that? 
 So, that is a look at 2.0. Next, I want to talk about the Americans with disabilities act. This act is civil rights law. You cannot discriminate against someone based on disability. But, this act predates the web. The word Web and Internet is not found in this act. It does apply to places of public accommodation. It primarily focuses on physical accessibility. Because of the ADA -- there is accessibility to restaurants and restaurants, etc. The big question to get the answer for -- is the web parts of the ADA? Isn't covered by the ADA? Meaning is it a requirement of the ADA that a website not be discriminatory? That is a difficult question. The law does not define this. There are lawsuits and complaints with varying responses. 
 In some cases, the judges has said that it clearly applies and other have said that it has not. We have seen mixed responses to that question. There is not a clear answer. At least in regard to how it applies to public websites. Meaning -- a storefront where you are selling products -- does it have to be accessible? Maybe, maybe not. That trend is to find that this is covered by the ADA, but it is not clear. The ADA clearly a prize in other places. Primarily, employment. Places where this might be significant -- intranet for websites that are necessary for employees to be able to access in order to do their jobs. Consider if you have an employee that went blind. Could they continue to do their job? If they cannot because of an accessibility of Web content, the ADA would apply. ADA prohibits discrimination in employment. It does not necessarily apply to the web, but if someone cannot do their job because of in accessible Web content, the ADA would most certainly apply. Keep that in mind. 
 Going back to the question -- the public website or the is this website -- whatever you provide to the public -- even though we are not sure how the law applies, right now there is a proposal to expand this act to make that Lear and to clarify that the web is a covered entity -- clarify that the web is a covered entity. This proposal came out a couple of months ago. We are watching it make its way through the legal process. The way it is looking, I would suspect that in the next year or two the ADA will probably be amended to clarify that the web is covered. 
 Now, that will mean that depending on how they define Access ability that it would -- and in accessible website with be determined to be discriminatory. That could or would almost certainly open up enters and employers or whatever it might be to complaints and lawsuits. That is significant. We do not know exactly how they will do fine accessibility and how they might apply it in different areas and if there will be deadlines to Apple Memphis. -- Diplomat this. 
 I would strongly suspect that the ADA will reference the only place where accessibility is defined early and federal law -- that is in section 508. Section 508 is currently being updated to mirror the Web content act 2.0. The ADA will probably reference to or be very similar to 2.0. Be looking to that set of guidelines. That is where everything is heading. If you focus on WCAG 2.0, you will be meeting all the needs of 508 and the ADA as well as international law. That is where you need to be looking. Still with the consideration that your site can be compliant and still accessible. We are talking about a continuum. These are measures along the continuum. Keep that in mind. 
 Accessibility is about people, right? It is not about laws or guidelines or checkpoints. It is about the user experience and interactivity of the website. We need to focus on that and make sure that the user is having a good experience regardless of whether we are compliant or not. 
 If you think about all of these laws and guidelines -- it can be overwhelming. It can be daunting. Hopefully, I will break this down anyway to be easier by focusing on principles of accessibility. These four principles are perceivable, operable, understandable, and robust. These principles are accessibility are derived from the accessibility guidelines 2.0.
 We will focus on these four principles initially and how they apply to people's disabilities. It helps you to remember these -- we will make POUR websites. We will make sure that our content meets these principles. Anytime we categorize people, we need to be careful, but it can be helpful as we consider the needs of the users with disabilities in implementing accessibility. The main types of disabilities to consider -- visual, auditory, motor, cognitive, and seizure disorders.
 We will go through these principles in more depth. The first principle is perceivable -- this is about getting the content to their senses a way that it can be useful to them. It does not matter -- you have to get the content to the user's senses before you can remotely begin to become accessible. Initially, we will talk about auditory disabilities. When we talk about auditory disabilities -- this is pretty straightforward. If you have audio or a multimedia content within your website -- someone who is deaf or hard of hearing will have trouble. You need to provide that content in a way that it can become perceivable to them. Primarily, this will be through a visual presentation of the auditory content that will be presented. Bringing that down more -- that means captions for Io and for live audio and text transcripts for all audio content. If you embed a YouTube video into your website, in order for that to be perceivable for those that are deaf or hard of hearing, you would provide captions for the video. Most of you are familiar with closed captioning. It would be a presentation of everything that is spoken in synchronization with the audio as it is spoken within the video. This would also apply to live audio -- that is the only way to make a teleconference online accessible. That would apply to video. You would need synchronize captions. In the audio contact you could try -- you could provide the text transcript. This is a verbatim version of everything that is spoken within the video. Text transcripts -- if you had video -- you would provide captions and the transcript. That is important for couple of reasons. You would provide synchronize captions and the text transcript. That is required in section 508 and the web content and accessibility product guidelines -- to provide accessibility and transcripts for video content. 
 This is what is necessary for audio content to be accessible for those with audio disabilities. We know that there are other benefits to captions and transcripts. In fact, most of the things that we are talking about today, there are additional benefits beyond those meeting the needs of disability -- for captioning -- it is useful if you are in a quiet environment -- if you are in a cubicle -- you can still watch a YouTube video I get the content without necessarily having the audio turned on. Or maybe in a noisy environment -- having the captioning on the ballgame at the noisy sports bar -- this allows it to be accessible to everyone. Captions are also helpful for language issues -- maybe the language of the person in the video is different from the primarily which of the person listening. They be it is a complex content. It is very helpful for those with learning disabilities. So, again, there are additional benefits. Transcripts allowed contents to be searchable -- not only by humans -- maybe it is an hour-long lecture or something like that -- you could search through the transcript to find where the professor said something specific. It is also a searchable by search engines. It could become indexable. The whole world could find your contact because it is presented in a searchable format. Anyway, those are a few additional benefits there are probably more. 
 One thing that is important to note -- excessive billeting for the deaf and blind -- consider for a moment how the comment -- content would be perceivable by someone who is deaf and blind? They cannot hear the content and they cannot see the website. So, the sense that they would use would be touch or feel. You can use a refreshable device -- it creates the braille care occurs and you can read through the text of the webpage or the transcript in they'll -- braille -- and they can read through the content. It is pretty amazing. A deaf and blind person could fully interact with the contact as long as it was compatible with the devices and accessible. Attached transcripts for audio or video content -- that is the only way that somebody that is both deaf and blind could interact with web content. 
 That is pretty straight forward to understand. I will note that captions can be difficult. They can be a little extensive -- expensive. Technology is improving greatly right now for captioning and transcription of multimedia. It is becoming much less expensive to provide these for those with auditory disabilities. 
 Next is visual disabilities. This is primarily where we tend to start we talk about prime web accessibility. There are some things to consider. Usually when you talk about visual disabilities, somebody that is blind will be using the screen reader as an assistive technology. When I say assistive technology -- we are talking about any kind of technology that could help someone with a disability to interact with web contact in a way that they would otherwise be unable to. So, a screen reader is assistive technology. They take the content of a web page and presented at appointed the user. If I cannot see it, my computer can read the content of the webpage to me. That means that the webpages are linear. A screen reader will read the content of the webpage for the most part -- top to bottom left to right are read only reading the tech content of that webpage. The screen reader can only read one thing at a time. The user can only hear one thing at a time to -- it is very linear. Usually, most of us -- when we come to a webpage -- we will scan it visually. They know that they will not look at every navigation. We don't even see those banner ads anymore. We block them out. We look or the things that pertain and argue on the webpage. We do that very quickly and visually. Somebody who is blind -- they cannot visually scan, so as the screen reader reads -- they can navigate to the page in a different way. If it just reads it left right and top to bottom, they can navigate through the webpage using headings and lists. They can look at different structural elements of the webpage. One thing that is used is links -- this kind of is what we have asked the -- this is what we use -- you don't look through the home page -- you look for things that are applicable to what you're looking for. You are looking for navigation and things that will get you closer to the content or functionality that you are looking for. 
 The screen reader does the same thing by ignoring the extra stuff and only have the screen reader read the actionable items -- buttons and things like that. 
 These links on a webpage -- if they are all written in a way -- the text -- click here -- they would hear that. There would be no context as to what that actually does. And to where it actually takes the user. We want to use any full links -- clicking will always be extraneous. It needs to be removed. Make the subject the link itself. Maybe instead of something like four employment -- just make the word say employment link. It will always be shorter. It is very important. Plus, it is helpful for all of us. If you look at a webpage and you see blue underlined text -- you have to visually read it before or after the words in order to figure out what the function of the link is. It is not helpful for anyone -- so avoid it. 
 We also need to provide alternative text for nontext elements. A screen reader cannot analyze an image and determine what the images. If it is an image of -- a cat named fluffy -- if I had the image on the image -- they can analyze the image and determine if it is a cat or a tiger or anything else. So, we as site developers and site administrators need to provide alternative text for those images. That alternative text will be hidden under the hood of the webpage associated with that image and would be read by a screen reader in place of that image. It is very vital for accessibility.
 A few other principle here to consider -- one is that we need to associate text labels with form elements for form controls. If you come to a form and you see the word first name and next we you see a text box -- you know that you should probably put your first name in that text box. While we have done is made a visual association between the text box and the word first name based on positions and proximity. Someone that is blind cannot make out visual approximation. They cannot see how close the elements are. We need to provide an explicit association -- we need to specifically associate the words first name with the text box. Then, it doesn't matter where we position the text. Sometimes we put the label above the form control -- for most of that we put it to the left. The radio buttons and checkboxes -- we put them to the right. Even our visual proximity guidelines change based on what we are doing. But, if we make a explicit or programmatic -- the screen reader can identify the label regardless of where it is positioned. Even somewhere else entirely different. 
 Another thing we want to do is associate data cells to grow and column headers. If you consider a data table like a class schedule -- you can look at that tabular data with rows and columns and probably headers that identify the data. You can look to the piece of data in number five and you can visually scan up and down left and right and identified that this could be the class number for biology 101. We have visually made an association by standing up and down and left and right to determine the headers and the rose. Someone that is blind cannot do that. They cannot do the visual scanning. Again, we can provide a an association that says that this piece of data belongs to the class will number and to the biology 101 header. Then, that information could be identified be the screen reader when it encounters that piece of data. So, again, the other thing that is important to Access ability -- it does not change the visual presentation. This coating and accessibility will have an under the hood association. We also want to ensure that we have sufficient contrast -- this means that there is enough contrast between the text color and background color -- there are specific guidelines for contrasts in some of the guidelines. There are formulas to determine the contrast ratio and levels of requirement for this contrast ratio at different levels. It can be complex to figure out. There are tools out there to help you out with this. It can tell you whether you have met or not met the requirements for contrast. We have developed this on our website -- it is a color contrast check or -- you can enter a color and they will tell you if it will pass or fail. This is important to those with certain types of low vision where it is required for them to have enough contrast in order to differentiate the text from the background. It is also helpful for everybody. We all read things better when there is a sufficient contrast. So again, it is a good benefit to everyone but is primarily for those with disabilities. 
 We also want to ensure that content is not conveyed with color alone. We can use color all we want, but we need to make sure that it is not the only way that we are conveying information. I have examples of this. Here you have won the lottery -- press the green button to accept your prize and press the red button to decline. On the button there are two screens. -- On the screen. Two buttons. They look the same. You are seeing a red button in a green button but you are seeing them as they would be seen if you have the most common form of color blindness. The most common find -- this is the most common form. Certain shades of red and certain shades of green kind of look the same. These are buttons appear the same color. We use red and green most often usually to convey content or meaning -- stop go -- those kinds of things. Red and green are used a lot to convey information. I am not saying that you cannot use red and green -- you some all you want. Use any color you want, but make sure that you are not using the color is the only way to convey information. That is what is happening in this case. If you had to pick a button is the green or red -- is it on the left or right -- if you had to pick one -- which one would you pick? If you had to pick one here -- which one would you pick X. well, on the screen you can see the actual red and green button. The rent is on the left and the green is on the right. Those are the images that you would actually see with the most common form of color deficiency. It is a pretty significant color difference there. How would you make this more accessible without relying on color box the easiest way would be to add labels to the buttons. But the word except on the green button and you would also want to present them in the same order that they are presented in the text. You have green first and read second in the text. You would probably want to put that in the same order for better understand ability. So again, you can use the red and green, but in this case you would not want to use them as the only way to convey information or meaning. Another couple here -- the green mushrooms are okay to eat. The red mushrooms will kill you. Then there is a list of five types of mushrooms. If you had to choose from this list of five mushrooms -- it would be hard unless you really know your mushrooms. It could be difficult to know which ones to pick. It is important because it is between life and death. Here is the actual list with colors. The top and the bottom are red or poisonous -- the ones in the middle are green or edible. Again, this is a case where you can use color if you want, but you cannot use color is the only way to convey information or meaning. This could be made accessible in a few different ways. Probably the most simple and straightforward approach is going to be two separate this in two lists. You could still use the colors if you want to, but now there is something else beyond the colors to convey that. We often have people recommend something like using italics for old or underline. The difficulty with that approach -- if you are blind, you are also colorblind. It seems kind of silly, but if you are blind, obviously you cannot see the color. The screen reader will not generally identify color differences or other stylistic differences with text. So, it will not say that text is red or bold or italicized. If you use the other types of early visual stylistic presentation differences, it probably will not resolve the issue for those that are blind. This can have an impact on those with certain types of low vision. I may see the color blue on a yellow background and that is the color combination that I need in order to be able to perceive content. If that is the case, I override all of your colors and I see it in the color commendation that works best for me. That means that the red and green text disappears. I see the blue on the yellow background. The solution for all three of those color deficiencies and low vision is just to not use color is the only way to convey the information. There are some tools -- color filter tools -- you can use these to view your page as you would view with different forms of color blindness or color deficiency. A really simple test for this is to print your webpage on a black-and-white printer. Is there any information or meaning that is lost when the color information is not there? 
 Another important aspect -- you also want to be careful of text within images. If you put text inside an image and the image is enlarged by someone they need to enlarge because they have low vision, text within images may become pixelated or more jagged and more difficult to read as the image is enlarged. Whereas if you use to text in your webpage -- the true text: large infinitely without difficulty and readability. It maintains its Christmas and sharpness. This is not to suggest that you could use text within images. We are saying that if you can use to text and get the same visual presentation, you should do that. Use true text where you can. In cases where you need stylistic text that cannot be -- the presentation cannot be done with true text -- it is probably logos and things like that -- introduce an image with that text -- make sure that the image is enlarged that it maintains its readability. 
 Those are some key points for receipt -- perceive ability. I wanted to talk about the guidelines -- how they are a little bit old and maybe a little bit dated, but they are still very relevant and useful and they have a minimal threshold of -- in conjunction with our principles -- we are also going to discuss some of these section 508 guidelines -- their first one says that a text equivalent for every nontext element shall be provided. We are talking about alternative text for images. This would also mean transcripts for multimedia. Multimedia will be a nontext element -- the text equivalent would be a transcript. That is item A. of the guideline. I didn't be says that if you have multimedia, you need to provide synchronized captioning with that multimedia. So if you have video it must provide synchronized captioning with the video. 
 I can see -- it says that when pages are designed so that all information conveyed with color is also available without color, for example from context or markup. That is what we were just talking about. Use color all you want, but do not use it is the only way to convey information. 
 The next item -- document shall be organized so that they are readable without requiring an associated style sheet. This means that if you turn off the style -- disable the stylesheet -- and turn off the visual styling and presentation of the webpage, it still maintains its readability. I do not think I have ever seen a web page that fails this requirement. Everything is readable when styles are turned off. It is rare to have it become unreadable. It might not make sense at all -- it could be totally confusing and the layout may be bad -- but it is totally readable. I think the general spirit behind this is that your way page be flexible to allow the user to perform their own stages -- changes. That means that if I override your page colors, it is still readable and usable? If I increase my text size, does it maintain its readability and functionality? I think this is a more useful way of interpreting item B., but in general it is talking about ensuring readability if the style radar is modified. 
 Items G. and H. apply to the data tables. It says that you should identify headers in the markup -- and you should associate the pieces of data with their appropriate headers. Again, the cell that contains number five -- you can associate that to biology 101 in your underline mark a bigger base. That is required as well. 
 Item I -- these deals with frames. These are not as common anymore, but this says that frames the debate you many title that identify what the frame is. This is the navigation frame, main content frame, etc. Things that would identify them and allow a screen reader user to navigate the screens with some sort of identifying information as to what the frame is or what it does. 
 Moving on to the second principle -- operable. Once we perceive the content, we want to be able to interact and navigate. We want to be able to operate in the content. This will apply to those with motor disabilities. The ability to interact with a keyboard or interact with a mouse with that webpage. We are talking about issues of fine motor control and using a mouse, repetition and fatigue, and giving the users control over timing or moving elements within the web age. 
 I want to talk briefly hear about Apple let's see. You can introduce a photo of collective seizure with a strobe in Flushing content. General guidelines here -- it has to flash more than three times per second -- it has to be sufficiently big in the webpage. The color red is also more likely to induce a seizure. We would like to recommend what we call the annoying rule -- if it is big and bright and stroking, it has potential to induce a seizure in the user. Most of you probably are not doing this curve. You probably don't have this kind of webpage, but we are seeing this more and more in Web multimedia and video. Someone put a video in their webpage and it contains a strobe light as a special effect. That is where you want to pay attention to this. This is important. Not only are we talking about accessibility, but we talk about inducing a seizure -- you can really hurt someone. It could be very dangerous to induce a seizure in anyone. 
 A quick story -- I have gained a new respect for this. The statistics that talk about food poisoning after Thanksgiving with leftovers -- you can add me to that list. I got food poisoning after Thanksgiving. I was so sick that I passed out and I had a seizure. I had never experienced that before. It kicked my butt. It was significant. I was recovering for a week from now. It was scary. It was potentially dangerous. I banged up my head and nearly bit off my lip having a seizure. To me, that gave me a newfound respect and a clear warning to everyone -- be careful with the stroking in Flushing content because of the potential impact that it might have on users. 
 Moving on -- with operable, we want to make sure that the webpage is keyboard accessible. But I cannot use a mouse or choose not to use a mouse, I will interact and navigate through the website using a keyboard screen -- the screen reader users will use the keyboard for navigation and interaction. You need to make sure that you can do everything and navigate to all the interactive elements and complete all of the forms and all navigation links using only the keyboard. 
 You also want to make sure that you have a good navigational order -- via navigating to the interactive elements -- you usually do with the tab key in your browser. If the order logical? It is pretty much left to right and top to bottom. It follows the individual flow be paid. They sure that it does not jump around in an order that would not be useful and logical. And be consistent in your navigation elements so that your navigation is in the same order in the same place on the page to write your site. 
 You can allow users to skip overlength the lists and repetitive things. We are talking about -- consider your webpage. Think about your website. Let me back up a little -- as you consider your website, I have a colleague who is quadriplegic. He directs with the webpages with a stick in his mouth. He hits the tab key on his keyboard. Consider your website. Many times would your colleague have to hit the tab key with the stick in his mouth to navigate from the top of your page to where the main content against? Count up all of those items between the top of your page and where the main content begins. Consider the effort at repetition necessary for him to be able to navigate through that content her it I would imagine on most sites it can be significant. It is a few times of having effort in pressing the tab key. But, you can allow users to skip over that navigation and jumped directly to the main content whether it is to skip to the main content -- this is typically one of the first link on the webpage. They can hit the tab key once or twice to get to the link and activate the link and when they activate that -- it would immediately focus on the main content or the new stuff is appearing on the webpage. This allows them to not have to go through all of the stuff in the navigation. It is very useful and important. Especially for keyboard users. This is an area where it is significant to have an impact on visual design. There is a way to hide the link visually. Mouse users would probably never see it -- but with the keyboard user -- the link becomes visible when it receives focus. The keyboard users can use it and no one knows it is there. That is one possible solution if you do not want to present that visually all of the time at the top of your page. 
 Next you want to make sure that you do not remove focus indicators. As you navigate moving the tab keys in the webpages -- by default, this will show a doctor to order around the link or the control that usually has keyboard focus. You can visually see where you are at in the navigation. You can turn off the focus indicator. As the user is navigating to the station -- there is no visual limitation. It essentially makes the patient not keyboard accessible at all. We are seeing this so prevalently on the web right now. There are so many big pages and small ones that are turning off this focus indicator without any regard to the keyboard user. Try this. If you do not see the focus indicator as you tab through, it is a minor change. Technically, it is the property outline of zero that will turn off that. You can easily reenable the focus indicator. 
 Error covering mechanism for forms. Most of our frustrations on the web tend to do with filling out forms -- getting it right in doing all of the requirement elements. To work in it didn't have electricity that artery submit an ensuring to write? It can be confusing. Particularly for those using the keyboard only to fill out that form. So be careful with your error prevention and error recovery mechanisms. Especially with forms. Sure that they are easy to fill out an easy to recover. 
 The last point -- giving users control over time sensitive changes. I am going to give you something from Utah -- I am going to present to you the secret of everlasting happiness. Oh too bad -- I don't know if any of you got it -- you will have to go back acting the archives. The point here -- we sometimes do it on the web? The power of the web is that it is not constrained by time. I can take as much time on a web page or application is I want to. Sometimes we implement these time the descriptions -- this page will automatically redirect -- what do we do that ex-heaven forbid you would give them time to do that before you automatically redirect. That type of thing. This gives she user control over the time sensitive changes. So that I can specify it when things will refresh or redirect. 
 The guidelines that apply under this principle -- image maps. An image map allows you to take an image and to find things within that image. In order for the image maps to be keyboard accessible, they must be server side image maps. That means that it must be within the webpage itself rather than based on the court in its of where the user did something else. It is based on the -- that means that it will only be Mel's successful. Basically, they are saying to use the server site image maps for images. 
 The next one built with flashing contents. It is for photosensitive epilepsy. Make sure that your page does not flicker or flash at a frequency greater than 2 Hz and loader then -- lower than 55 Hz.
 The next item deals with scripting. If you use Java script or any type of scripting to add interactivity or processing or functionality, it has to be accessible and functional with the system technology. You can use JavaScript at all of the others -- this says that you can do that, but you have to make sure that they are accessible. There is no exemption for accessibility because you are doing something cool and fancy. 
 The next item deals with forms. If you provide forms, you have to make sure that they are accessible and that the user can access the information, field elements, and the analogy required for completion and submission of the form, so form labels for form controls -- making sure that it is easy and you have all the information to complete and submit the form. Picture is accessible. 
 The next item deals with skip links -- it gives the user a mechanism to skip over repetitive mechanism links -- 
 The next item -- give users troll over time sensitive changes. Or if you do have a timeout -- make sure that you older the users and give them sufficient time to extend that. It is example of this, if you have been inactive for 10 minutes -- they will time you out unless you click the okay button. Then we will give you 10 more minutes. Something like that. So that the user is alerted to any kind of time requirement and allowed to continue. 
 The next principle -- understandable. This deals with comprehension. The message in the things that we are conveying in the to the user in a way that they are accurate and synced and understandable. This will affect those with cognitive disabilities. This is by far the largest disability group out there. If you took all the disabilities and add them together, it would still not equal the number of those with cognitive disabilities. It is very significant. There are many types of cognitive disabilities. There are things ranging from ADD to memory issues to cognitive processing issues. A wide a way -- -- a wide array -- it is large and significant and to first. This sometimes makes it look old to make a distinct recommendation. It affects everybody. We all benefit from having content that is easy to understand.So General. recommendations -- be careful with movement and other distractors. That little animating graphic  or that enter add that flashes or animates, it might be mildly annoying but for someone else it is a disk extreme at distractibility. It could render the page in accessible. The careful with any type of animation -- animation that could be distractible. Symantec organizations -- we are talking about headings and lists. Things in the page that provides underlying structure and meaning to the page. If you consider visually -- if you came to a long webpage -- you probably scroll fast and look for the bold text and look for the structure and content. That is useful for understandability. I mentioned before that the screen reader users and keyboard users can also navigate by headings. By using true headings in your page to identify the structure of that document is very important for accessibility. It provides better understandability and better organization and it facilitates better keyboard accessibility. Use the true headings -- having leveled on -- level I -- it usually identifies the document title -- second-level headings -- this would identify subheadings. And so on. It is important. This is probably one of the top one or two things I would recommend on your website to greatly enhance your accessibility. 
 Be consistent. That makes sense. Be consistent in your presentation and what you are doing with your webpage. Strive for brevity. Use the simplest line which possible. It is so important. Use the simplest language that is appropriate for that content. There is no requirement that says you have to write it at a sixth-grade reading level but it sure it is written at the level that is most simple for your -- 
 Understandability -- consider web developers -- these are people that are designing webpages. This is your typical web development web design team, right? The crisp white shirts in the quarter office and their -- maybe this isn't your typical development team. Maybe this is more your typical web developer or web designer. I can make fun of this photo. I am about as geeky as they come. We had somebody recently say all those guys aren't developers because they are outside. They couldn't be developers they are outside. The point here is that most people that build Web pages are very familiar with the web. I have a web rows are open all day long. I carry one in my pocket. It is on my iPhone everywhere I go. I understand how it works and I learned strategies for navigating and interacting with content and ignoring the clutter and the extraneous stuff. I have become good at that. When I build webpages -- we need to think outside of the box. We I'd be very familiar with the web. We might need to consider the needs of those not as familiar with the web. We need to think outside the box. Someone like my mother and grandmother -- what with their experience be? The cognitive load that might be present and multiply it by 10 and that might give you an understanding of the level of difficulty that someone with a cognitive does it the leading might have on that website. 
 The final principle is robust. This deals with technology compatibility. It is dealing with technology. I merrily, we are talking about browser and assistive technology compatibility. Make sure that your webpage works with different things that your viewers might use. Does it work in different browsers? Does it work with screen readers and screen enlargers? It is also about following the rules. Have we follow two rules of HTML and -- have we implemented the Web content accessibility guidelines? It also has to do with hardware compatibility is that mobile? How does it work on mobile devices? Other types of platforms and screen types -- things like that. It is looking at right now, but it also keeps its eye on the future. You don't want to fill the webpage if there were be a new screen reader released tomorrow. It is also in looking backwards in ensuring compatibility to those that might need it that are using older technologies. So that is robust this. 
 Here are some guidelines -- but I should back up a little bit -- you may have noticed that there are no guidelines that apply to the principle of understandable. There is nothing in at 508 that stresses the content be understandable and for the most part, in the guidelines version 2.0, there is not much there either. The issues of understandability and cognitive accessibility are pretty complex. They can be pretty difficult. For that reason, for the most part, accessibility guidelines really have not addressed those with cognitive disabilities. For those of us developing these things -- we really need to be aware of that -- primarily because the guidelines do not do a very good job of that. 
 Under robust -- item am -- this requires that if you have something in your webpage other than standard HTML like a flash or Acrobat or QuickTime movie or something like that, that you provide a link so that the user can download the program necessary for them to view or interact with the content. If you have a PDF file -- you should provide a link for that. The next item build -- text only I'll turn it is. -- Text only alternatives. It is kind of obligated. Really what this is saying is that if you have a webpage that can be made accessible, you should make it accessible. That is what the Bible way requires. -- By the weight requires. You cannot create a screen reader version that could be made accessible and say that you are 508 compliant. They did not want the approach to be that everyone creates a text only version and say that all you people with disabilities go research get your accessibility. They did not want that to be the approach. So what this says is that if you are not by the way compliant -- if you create -- with 508 -- you are actually less compliant because you have created a text only accessible alternative to content that could be made accessible. If you have something that could not eat accessible or 508 compliant, then you can do that. They are trying to avoid the idea of separation. Some people get this and everyone else gets this -- they really interactive version and everyone else with disability has text only -- that is not fair. It doesn't sound right. It is potentially discriminatory. The idea is to make your main website accessible if you can. 
 Those are our for principles -- this is the way that individuals with disabilities can react with web. This is beginning the surface. We have and not really gotten into techniques and code. Much of that is available for you on our website. If you want to know how to implement these principles and guidelines, there is a wealth of resources and tutorials on our website. 
 The other thing that I would say with these principles -- considering types of disabilities and primarily the aging population. As we age, we tend to lose vision and hearing and waterfront. And we lose positive option. It is very significant. 
 Real quick I want to talk about what I call the fast track -- things that you could do right now on your website to enhance accessibility. First would be alternative text for images -- key words to remember our content and function. That means that instead of providing alternative text that conveys what the image looks like, you want to convey the content of the image. There is a difference. For example, if it images a photo of me -- the alternative text for a photo of me would be my name -- right? That is the content of the image. If you compare that to a description of the image -- it would be -- white handsome ale. -- Mail. Hopefully you understand the difference. Function would be that if the image is a link that the user then can click on -- you need to pay to convey to the user the function. 
 Form labels -- so that the data is identifiable by the screen when they encounter the form controls. 
 Table headers and associating pieces of data with the appropriate row and column headers. Page headings -- we talked about that. Good heading structure -- heading level I for your document title -- and two and three for good structure and a way to facilitate navigation through the content within the page. 
 Visible link indicator -- if your navigator -- you can tell where you're at in the page and can you do all the things necessary -- all the functionality is available with the keyboard? And good descriptive listings page titles. -- Synced sinks and what the pages about -- this would be the beginning of the list, but there are a few things that you can do right now to greatly enhance the finale of your website. -- Accessibility of your website. Now I will put in a shameless plug for our tool. 
 This is a free tool that we have developed -- we are biased -- we have developed this for our own evaluation and testing and consulting. We have made it freely available for anyone who wants to use it. It is an evaluation tool for accessibility. You can come to the website and type in your website address and hit a button and it will give you visual feedback about the accessibility of that page. It will help you as a human to determine how accessible the webpage is a can identify errors but it can also help rebuild the underlying accessibility of the webpage so that you can better evaluate it. And the body weight -- example -- alternative text -- this is hidden within the webpage. It is kind of embedded with the image within the page. You usually cannot see it in the webpage. But if you are using a screen reader -- it does. The wave can determine how appropriate the alternative text is to the image. It uses a bunch of icons and indicators to inject into your webpage to get you feedback about accessibility. No tool can tell you if you webpage is accessible -- they can do that -- but it can identify accessibility issues and help you determine how accessible your web content is. I recommend it as a tool for used to use. If you have Firefox -- you can download it there. It is a little bit more of a powerful a valuation within your web rouser. -- Web browser. That is a way for you to go out of tested. 
 With that, I will take some questions. I will get to those -- we've got three or four minutes for questions. Please host them in text box. 
 There was a question that came in about color reliance and color deficiency -- what if they are colorblind and only see in black and white? There is a form of color blindness called -- Mono chrome oh -- I think that is what it is called. Someone only sees in shades of gray. Usually, when we talk about color blindness, we talk about color deficiency in which certain color omniscience are a little bit more difficult to differentiate. Another question -- how would the individual note the text of the different colored? I think we addressed that. You could use the color combination for smudges you want -- just don't use them as the only way. Use something else visually significant to identify those changes in content. 
 Next question -- where online can one access some free software to make websites easier -- 
 I don't really have a list. There are a lot of -- there are quite a few out there -- open source software to help people with disabilities. This was more about you building your website for people with disabilities. One tool that I would mention -- NVDA -- is a free open source screen reader that you can use for evaluation and it can be helpful for those with disabilities that I'd want to have access to a very expensive screen reader. 
 Last question -- Web address for cote technique and tutorials -- it is WebAIM.org. I have not seen any other questions. I will stick around for a few minutes. I will turn the time back over for the folks there for some few last comment. 
 Thank you very much, Jerry. That was a great presentation. It was wonderful information. I just wanted to point out a few other related Cornell resources that some of you might be interested in -- we have an online repository of over 200 research reports and policy briefs -- the Web address is listed there --
 That has a wide variety of research supports including several regarding web accessibility. We did a project a number of years ago looking at accessibility of online recruiting for private companies as well stop boards. -- Job boards. The majority of that were not accessible. That might be of interest to some of you. We also have eight are tips -- HR tips -- workplace accommodation -- that is that W. David W.HR tips.org. 
 Disability statistics -- that is the website.
 We also have the national technical assistance policy and research center for employers on employment of people with disabilities -- earn works.com. They are thinking about having a hospital follow-up conducted to in the spring of 2011. Thank you very much for participating. Just wanted to let you know that you will be receiving an e-mail with a link to an online evaluation of this webinar in a day or two. Completed evaluations will help improve the quality of our offerings. Please complete those when you receive them. Thanks again for attending. Hope you have a nice afternoon. 
 [Event concluded]