What's your standard? Accessibility In Mind has you covered for Section 508, PDF/UA, WCAG 2.0, HHS

Ensuring Indemnity With Documentation

Accessibility In Mind offers extensive accessibility reporting supporting all recognized standards, guaranteeing compliance. Whatever your specific requirements may be, AIM can remediate your documents to comply.

• Section 508: Section 508 was originally added as an amendment to the Rehabilitation Act of 1973 in 1986. It requires  Federal agencies to make their electronic and information technology accessible to people with disabilities. The regulations are broad in nature and are interpreted differently by different agencies. AIM can provide Section 508 specific reports certifying compliance.
• PDF/UA: PDF/UA (“Universal Accessibility”) specification, or ISO 14289, was published by the International Organization for Standardization (ISO) in August, 2014. PDF/UA requires Tagged PDF (ISO 32000-1, 14.8), and adds a variety of qualitative requirements, especially regarding semantic correctness of the tags employed. It is the first fully accessible standard ISO has ever published. AIM can provide PDF/UA specific reports certifying compliance.
• WCAG 2.0: The current version,  was published in December 2008 and became an ISO standard, ISO/IEC 40500:2012 in October 2012.It consists of 14 guidelines which are general principles of accessible design, primarily for websites, but applicable to PDF accessibility. AIM can provide WCAG specific reports certifying compliance.
• HHS: The United States Department of Health and Human Services (HHS) maintains a checklist defining their interpretation of Section 508, providing specific guidance on compliant PDF structure. AIM can provide HHS-specific reports certifying compliance.

Every remediated document is delivered with time-stamped Adobe Acrobat Pro 11 full accessibility reports, and NetCentric CommonLook reports are available for all accessibility standards. These reports prove due diligence in compliance with the most stringent requirements, and ensure indemnity from any legal challenges to document compliance.

Accessibility In Mind gives you one less thing to worry about- contact us for more information.

Is there any such thing as "Certification" for section 508 compliance?

Yes, Virginia, there is.

 AIM, formerly Electronic Document Compliance Services, is pleased to announce the availability of certificates of compliance for Section 508, PDF/UA, HHS, and WCAG 2.0. AIM can evaluate and certify compliance of any PDF, providing time-stamped accessibility reports, your insurance against any and all claims of non-compliance, guaranteed.

Contact us for a no-obligation evaluation of your documents.

Getting Multiple Government Agencies on the Same Page Regarding Section 508

Anyone involved in the often onerous task of remediating documents for Section 508 compliance can find themselves aiming at a moving target, depending on the specific requirements of their clients. Section 508 of the Americans With Disabilities Act contains lofty goals for universal accessibility, but does not get down into the weeds with specific guidelines for document creators. That has left the door open for "interpretation" by different agencies, and subsequently makes life difficult for remediators.

A great example comes in creating accessible hyperlinks in documents. Here's what Health and Human Services (HHS) asks in their "PDF File Checklist", section 1.8:

Do all URLs contain the correct hyperlink and display the fully qualified URL     (i.e.,http://www.samhsa.gov and not www.samhsa.gov) 

That's pretty unambiguous. HHS was the first of the government agencies to interpret the regulation and create a checklist, but that doesn't make their interpretation correct, or make documents following their interpretation more accessible than documents that see it differently.

Below is a contrary- and persuasive- argument on hyperlinks from the Social Security Administration, in their guide to creating accessible documents. Consider their logic:

When a Screen Reader is reading text and there is a link, the software will insert the word "Link" in front of the text to alert the user that this is a selectable hyperlink. Another way that Screen Readers can access the links that are in a document is for them to call up a list of links. This list will display only the text that has been marked as a link. It is important that the list of links makes sense to the user when it is read out of context. That is, the name of each link should make sense in the list when it is read in isolation.

Consider the following four examples of the same text and same link rendered using different methods:

1. Please read The SSA Online Accessibility Policy. Click Here

2. Please read The SSA Online Accessibility Policy.
http://www.ssa.gov/webcontent/accessibility.htm

3. Please visit The SSA Online Accessibility Policy.

4. Please visit The SSA Online Accessibility Policy:
http://www.ssa.gov/webcontent/accessibility.htm

If every link in the document was rendered using method #1, the list of links would read like this:

• Click Here

• Click Here

• Click Here

• Click Here

It is easy to see that individual links are not possible to read out of context. If every link was rendered using method #2, the list would read like this:

• http://www.ssa.gov/webcontent/accessibility.htm

• http://ssa.gov/pgm/links_disability.htm

• http://www.section508.gov/

This list also makes no sense in context. While we might be comfortable in normal conversation saying "go to s s a dot gov" we generally do not say to people "go to s s a dot gov slash p g m slash links underscore disability dot h t m". It is too long and it is too difficult to understand. However, when the list of links is presented this way, this is exactly how the Screen Reader will say each link.

If every link was rendered with method #3, the list would be read like this:

• The SSA Online Accessibility Policy

• SSA Disability Benefits

• GSA's Section 508 website

Using this method, all of the links make sense when spoken out of context. This is the best method to use.

What is the lesson here? It's that "compliance" with Section 508 is not defined at the granular level, but a regulation that has many interpretations. Before starting any remediation project, it is best practice to query your client for any specific requirements or checklists that are to be followed. Just remember that the goal is accessibility, with compliance merely being the by-product.