º£½ÇÉçÇø

When building or assessing web content, it can be easier to check accessibility by examining the code used to build the webpage. This process for assessing web content does require an intermediate skill level for web browser navigation as well as some basic/intermediate understanding of HTML. If you are not comfortable with these, consider using one of the many assessment tools.

The resources on this page consist of a video and text instructions for assessing web content in the Google Chrome Inspect Window, but the principles can be applied to other browsers.

1. To assess online content in any browser, you will need to open the Inspect Window of web page. Make sure you are on the specific page you want to inspect.
   1. For Windows: Press ‘F12’ or “Control+Shift+C)
   2. For Mac: ‘Command+Option+C’
   3. Note: some browsers like Safari require you to add the developer tools in order to access the inspect window.
2. Look at the window to the right/bottom to answer the following questions.
   1. Note: the elements are presented in an expandable list.  Click any right facing arrow to expand the section of the Inspect Window.
3. Are they in HTML format?
   1. Scroll to the top of the inspect window, do you see'<!doctype html>” in the top left.
      1. Note: HTML can be read by screen readers while other formats cannot.
4. Are there headings and bodies that create organization and identify the website/page?
   1. Do you see ‘<head>’ on the left side and near the top of your Inspect Window?
      1. Note: headings are just as important on a web page as they are on a document. They provide quick information about the content on the page.
   2. Do you see ‘<body…” under ‘<head>”?
      1. Note: Accessible web pages should have a body where the content exists.
5. Is the web page divided into logical fields?
   1. When you open the body, do you see “<div>” along the left of your screen?
      1. Note: Each <div> tag along the left should have a corresponding tag at the bottom of the section.
   2. When you hover over any “<div>” does it highlight a logical section of the screen?
      1. Is the page divided into reasons that make sense? Some regions may have multiple divisions.
   3. Are those sections listed in the Inspect Window in a logical way?
      1. Note: The page should be divided in a way that makes sense. The sections on top and to the left should appear first.
6. Do all images have alternative text?
   1. Click the Inspect Window then hover over an image. Does he highlighted portion starting with “<img class=” have an accessible description after “alt=”?
7. Can you press Tab to cycle through links?
   1. Can you press Shift+Tab to go back through the links?
8. Can you navigate any multimedia with your keyboard?
   1. Can you use arrows to skip ahead or back on videos?
   2. Can you use the space bar to stop and start?