On this page:  Compliance Testing I Failed Checkpoints I User Verification I Warnings I Reporting

Checking for Compliance (QS-13)

After verifying that the correct tags are being used in the document, based on its structure, and after assuring that those tags are in the correct reading order in the Tag Tree, it is necessary to run a Validation to make sure that the other accessibility conformance criteria are being met.

  1. Click on the Windows tab in the Ribbon,
  2. Click on Standards.  Screen shot of the Windows Tab on the ribbon and the button for Standards is highlighted.
  3. In the right side “Standards” panel that opens, click the dropdown arrow next to “Standards,”
  4. Click the dropdown arrow next to “Accessibility” and select the desired Standard for validation.  In this example, we’ll choose WCAG 2.0.  Note:  In this guide, we’ll remediate to WCAG because it is a higher standard and is more globally recognized than the Section 508 criteria used in the U.S.  Users who need to validate to an alternate conformance level (508, PDF/UA, or HHS) may choose that standard for their reporting purposes.  Screen shot of the WCAG 2.0 validation option as well as buttons for Incremental and Full Validation in the Standards Panel.
  5. Click “Full Validate” at the lower right hand corner of the Standards tab.
  6. The Results panel will automatically open across the bottom of the document.
  7. In the “Filter by:” box, click the dropdown arrow and uncheck “All.”
  8. Check the boxes for Failed, User Verify, and Warning.  Click anywhere else to hide the dropdown menu.
Screen shot of the Results menu when running a verification. The dropdown menu is expanded showing all checkpoint options, passed, failed, user verify, etc.

Failing Checkpoints: (QS-14)

  1. Click on the first Failed incident.  The image of the main stage at the top of the screen is selected.  Hovering over the Description box reveals the tooltip stating that the figure does not have alternative text.
    1. Double click on the error to open the Fix Wizard.  Step 1 shows Fix options to provide Alt. text, convert to a different tag type, or to untag the content.  In this case, we’ll provide Alt. Text.  Click Next.
    2. Step 2 gives the option to provide Alt., Actual, or Expansion text.  Leave the option for Alt. Text and click Next.
    3. Click in the Alt. Text box in Step 3 and type the appropriate Alt. Text.  For this image, something along the lines of, “Image of the Rock On, D.C. Music Festival Main Stage” would be appropriate.
    4. Click Finish  Screen shot of step 1 in the fix wizard for the first error - an image with no alt text.
  2. The next Failed element is for the A105.8 radio station logo – again, a figure missing Alt. Text.  Follow the previous steps to give the figure the required Alt. Text.  (“Logo of radio station A105.8, the Armadillo” might be appropriate Alt. Text here.)
  3. If the table was generated using the Advanced Version: The third failed item is for the table that was generated earlier not having header cells.  As mentioned, data tables need to have column and/or row headers in order to be accessible and compliant tables.
    1. Double click on the error to again launch the Fix Wizard,
    2. In the Fix Options dropdown, choose “Table is a data table (with column/row headers)”
    3. Click Next,
    4. Step 2 provides various options for header configurations (row, column, both, etc.).  This table contains only column headers so click Next.
    5. The default number of column header rows is 1, which is correct in this case, so click Finish.
  4. If the table was created using the Standard Version:  The next set of errors are for cells that do not have headers associated with them.
    1. Choose “Table contains column headers only” and click Next,
    2. Leave the default number of column header rows set to 1
    3. Check the box in the lower left corner “Apply fix to all similar issues”
    4. Click the radio button for “Use current values”
    5. Click Finish
  5. The last failed item is for the Metadata of the document, specifically that the Viewer Preferences dictionary of the Catalog dictionary does not contain DisplayDocTitleKey.  There is only one option for fixing this problem in the document so click Finish.

“User Verification” Checkpoints: (QS-15)

After all of the Failed items have been fixed, there are a number of items that require User Verification.  Validating a document cannot be an entirely automated process because a machine cannot, for example, verify that the Alt. Text on an image is really appropriate for that image.  We can automatically test whether or not Alt. Text is present for the image, but verifying that something is really correct sometimes requires human interaction.  Likewise, while a machine can check a document to see whether or not color has been used, it cannot verify whether or not information is lost due to the use of color (for example, red being the only way that negative numbers are conveyed in a table).  This is why checking the things that require “user verification” is very important.

  1. Click on the first User Verification item brings us back to the image of the main stage.
  2. Right Click on the Description and scroll to Status.  The Status dialog will open.
  3. Check the description – here it is asking whether or not the Alt. Text that was provided with the figure is appropriate.  This is to prevent things like Alt. text that does not really convey the information in the image or perhaps Alt. Text that is just the URL or the local path to the file where the image came from.  Screen shot of the Status Dialog box asking the user to verify accuracy of Alt text.
  4. Assuming that the Alt. Text is appropriate (because it was correctly entered in a previous step), in the Status dropdown, choose Passed.
  5. Click Ok.
  6. Opening the Status Dialog for the next User Verify actually shows the web address for the Radio Station Q99.4.  Seeing as the URL for the logo is not appropriate Alt. Text, in the Status Dialog, choose Failed.  Screen shot of the Status Dialog dropdown menu.
  7. Click Ok.
  8. Now, in the Results panel, at the top of the list, notice there is a failure for the logo that was just addressed in the previous step.
  9. Click on the Failed error.
  10. In the Properties Panel on the right side of the screen, type the appropriate Alt. Text in the Alt. Text field.
  11. To refresh the Validation Results, click WCAG (in the Standards Panel) and choose Incremental Validate.  Note:  Running an Incremental Validation will only check the items that have changed since the last validation was run.  Choosing a Full Validation will start the validation process over again from the beginning.
  12. After running the Incremental Validation, the first User Verification item is for the Q99.4 logo that was just fixed in Step 14.  Assuming that the Alt. Text is now correct, right click, choose Status, and Pass the Alt. Text.
  13. Click Ok.
  14. The next two items to verify are for the other images in the document.  The first one is for the radio station A105.8 and that Alt. Text was added when fixing the Failed items (and may be set to Passed).  The second error shows the Alt. Text of “Dog” for the logo belonging to Pet Wearhouse.  This Alt. Text is incorrect and should be fixed, just like in steps 10-17.
  15. The next item is asking the remediator to verify that information is not being lost due to color contrast issues, color, format, layout, etc.  Seeing as this is not an issue in this document, change the status to Passed.
  16. Similar to the previous verification item, this test is asking specifically about the contrast ratio and making sure that there is enough contrast, visually, so that content is easily read.  Again, we can pass this item.
  17. Next, we are asked whether or not the Title of the document is appropriate.  It is, so we can pass this item as well.
  18. Next is to verify that the language setting (in this case English) is correct.  This can be passed as well.

Warnings: (QS-16)

Now that the User Verification items have all been addressed, we can move on to the Warnings.

The first warning is for the ListNumbering Attribute.   According to PDF/UA, ordered lists (with numbers, letters, or Roman numerals) need to have their listnumbering attribute assigned.  Because the list in this document is unordered (using bullets) we do not need to assign the list numbering attribute. 

  1. Right click on the item
  2. Choose Status
  3. In the Status Dialog, change the Status to “Not Applicable”
  4. Click Ok.

Note:  To assign the ListNumbering Attribute, in the Properties Panel, use the dropdown menu to select the appropriate type of list.

According to WCAG and PDF/UA, Tables should have Summaries (especially if they are long and/or complex).   

  1. Double click on the Warning to open the Fix Wizard,
  2. Type the summary in the Summary field,
  3. Click Finish.

Notice:  After the Summary was added to the table, there is a new User Verification requesting to certify that the table summary is correct.  Assuming that it is, change its status to Passed.

Depending on the verification used, this next Warning may or may not appear:  The next set of Warnings are all for untagged Paths (the black lines under the title at the top of the page).  CommonLook PDF Global Access is asking us to verify that these images do not convey information and should be artifacted (and not read by a screen reader). 

  1. Select the first Warning associated with the Paths,
  2. Hold down the Shift key and select the last warning associated with the Paths (this will select all of these warnings),
  3. Right click, and open the Status Dialog,
  4. Change the Status to Passed,
  5. Click Ok.
The last Warning states that Page 1 contains content but does not define header or footer pagination artifacts.  Pagination artifacts are specifically designated for headers, footers, and/or watermarks in a document.  Because this particular document does not contain these elements, then this is correct (that things are not marked as pagination artifacts) and we can set the status to Passed.  
Congratulations!  At this point, all of the errors in the document should have been corrected.

Reporting Compliance (QS-17)

Once the remediator has finished fixing the document and running the appropriate validation, a report may be generated showing the various checkpoints and their status (passed, failed, verified, etc.).

  1. Using the WCAG standards from the previous section, in the Results Panel, check the box next to All.
  2. Below will be the list of all items passing, failing, not tested, etc.  Scrolling down the list will show that all checkpoints in the document have either been passed or are not applicable.
  3. Generate a report by clicking on the “Report” button immediately to the right of the “Filter by” menu.  A window will open asking for the file name and location with which to save the report.  The report is then generated as an html file that can be opened in any browser and does not have to be remediated as another PDF document.  Screen shot of the Results panel with the Button for Report highlighted.
  4. Complete the Save As information as needed and click Save.  Tip:  At NetCentric Technologies, when we are contracted to remediate a document for a client, we return the accessible PDF and the validation report to the client, so that there is no question as to whether or not the document passes.  This may be a good practice for you to use with your department, client, etc. 
  5. The document is now remediated.  If not already done, Save the work in CommonLook PDF Global Access and close.