Showing posts with label 508. Show all posts
Showing posts with label 508. Show all posts

What Do You Mean, Accessibility In Mind?

“Accessibility In Mind”  means thinking about accessibility EARLY in the production process. We work with our clients to create procedures that reduce the time and cost of remediation. Using best practices can save 25-50% on post-production needs, so we like to be involved as early as possible, reviewing drafts, so we can help you understand the remediation process and how a few basic steps can make it go smoothly and quickly.
All AIM-remediated PDFs are guaranteed compliant with Section 508, and with the new “ICT Refresh”, following the specifications of PDF/UA-1 (ISO Standard 14289),  as specifically referenced in the Information and Communication Technology (ICT) Standards and Guidelines (updated Section 508 of the Rehabilitation Act, January 18,2018

The AIM Difference:

#1: Accessibility In Mind is a dedicated Section 508 and PDF/UA compliance service.

We are not a design/print house that does remediation on the side- remediating PDF documents, making them accessible and compliant, is our ONLY service.  Find the home page of our competitors if you want to know what their main business is, then come back to AIM for your Section 508 work!

#2: We are not a middle-man, taking a commission and passing the work on to contractors.

When you work with AIM you are dealing DIRECTLY with Section 508 expert remediators, and paying less– often 30-50% less– than through other vendors. Deal direct, SAVE TIME AND MONEY!

WCAG and Section 508: PDF Requirements

PDF/UA clarifies and simplifies the PDF-specific technical requirements to meet WCAG 2.0.

WCAG 2.0 is regarded as the primary standard for web accessibility by national governments around the world, and is referenced in the U.S. Access Board's new rules that updates accessibility requirements for information and communication technology (ICT) in the federal sector covered by Section 508 of the Rehabilitation Act. The six-year process of updating these requirements constitutes the first refresh since Section 508 was created in 1998. The rule is slated to go into effect in March, 2018, and references WCAG 2.0 and PDF/UA as the standard for compliant PDFs.

Creating PDFs that meet the WCAG 2.0 success criteria requires specific PDF authoring and remediation techniques. WCAG 2.0 was developed as a technology-independent standard and provides individual (normative) success criteria for accessibility which are general enough to apply across technologies, including a growing set of techniques for HTML, CSS, Scripting, PDF, Flash, and more. The Access Board's update states that all electronic documents must "conform to all Level A and AA Success Criteria in WCAG 2.0 or ISO 14289-1 (PDF/UA-1)." This proposal for accessible electronic support documentation is derived from the existing guidelines, but would newly require PDFs to comply with PDF/UA.

WCAG  does not presently represent a complete set which encompass all technical requirements for accessibility in all PDF documents. This is where PDF/UA provides help. PDF/UA provides normative technical specifications for the use of the PDF format, defining proper structure and syntax to enable reliable access. This includes identification of necessary tagging structures, how to specify alternative text for images, how to ensure correct Unicode mappings for character glyphs, and many other file, page and object-level specifications, as well as how Reader applications and assistive technologies can fully process PDF/UA conforming files to maximize accessibility.

PDF/UA defines the technical specifications to enable PDF documents to meet WCAG 2.0, but WCAG 2.0 has additional requirements which require an author’s attention. The areas where WCAG 2.0 has additional requirements include time-based media (guideline 1.2), scripting and actions (e.g. success criteria 3.2.1 and 3.2.2), and certain types of content (e.g. success criteria 2.4.4). For these and other additional requirements, the W3C’s technique documents (both general and PDF-specific techniques) provide guidance for authors interested in complying with WCAG 2.0.

WCAG 2.0 summarizes web accessibility using four broad design principles:
  1. Content must be perceivable.
  2. Interface elements in the content must be operable.
  3. Content and controls must be understandable.
  4. Content must be robust enough to work with current and future technologies.
These concepts are refined and delineated in the PDF/UA specifications; please refer to this article on PDF/UA for more information: http://508compliantdocumentconversion.com/pdfua-and-section-508/

AIIM, the governing body for ISO standards, published a document that shows how to achieve WCAG 2.0 through the use of the PDF/UA standard. It can be found here: http://www.aiim.org/Research-and-Publications/standards/committees/PDFUA/WCAG20-Mapping

New York City Sets the Pace For Accessibility, Requires Conformance With Section 508

New York City takes the lead in accessibility, passing a law in March of this year requiring that its government agency websites and electronic documents meet recognized standards WCAG 2.0 and Section 508.  This is hopefully the start of a trend making the Federal mandate universal, a giant step towards accessibility- state and local governments may follow NYC’s lead, requiring contractors and even public accommodations to conform in the absence of regulations from DOJ.

 New York City becomes the first major municipality in the United States to adopt legislation mandating accessibility standards for all of its government agency websites.  Serving a population of over 8 million, the New York City government includes more than 120 agencies staffed by approximately 325,000 employees.  This legislation will have an impact on City agencies, and access for persons with disabilities to those institutions.  It may also have an impact on future website regulations impacting businesses across the country.

“New York City is an amalgamation of cultures, heritages and languages,” Mayor Bill de Blasio said. “That is why we strive to increase inclusivity, especially when it comes to New Yorkers with disabilities. Whether it’s creating a more accessible City website, or ensuring that events hosted by City agencies have information regarding accessibility for people with disabilities, Intros. 673-A, 683-A, 881-A and 883-A strengthen our efforts to be more inclusive.”

The legislation (Intro. 683-A) was among three disability access bills that Mayor Bill De Blasio signed into law on the same day.  In addition to mandating website protocols, the legislation requires that each City agency designate a “disability service facilitator,” and publicize, among other things, the availability of wheelchair access, communication access real-time translation, sign language interpretation, assistive listening systems, and any other accommodations to be made available for all public events.
The sweeping mandate states that agencies must adopt an "Accessible Website Protocol" within 6 months. The new City law recognizess that the Web Content Accessibility Guidelines 2.0 Level AA (“WCAG 2.0 AA”) is increasingly becoming the de facto standard for website accessibility, despite the continued lack of any regulations from the U.S. Department of Justice setting a legally-required standard for state and local governments under Title II of the ADA.

Under the new law, the City must establish a website protocol within 6 months that incorporates Section 508 of the Rehabilitation Act,  WCAG 2.0 AA, or any “successor” standards.  The Section 508 standard currently applies to the federal government websites and electronic documents, and consists of a list of 16 requirements that are less rigorous than WCAG 2.0 AA.  But last year the Access Board proposed a rule that would, among other things, adopt WCAG 2.0 AA as the new website standard under Section 508.  Thus, if the City incorporates Section 508 in its website protocol, its agency websites may be subject to WCAG 2.0 Level AA once the final Section 508 regulations are issued.

“The City Council is committed to making New York a more inclusive City for all people to work and live,” City Council Speaker Melissa Mark-Viverito said. “This package of legislation will increase language access across City websites and improve access to City services for all New Yorkers.”

Chris Frank, CEO of Accessibility In Mind, a dedicated Section 508 remediation service says "It's no surprise that NYC is being proactive in requiring government services and documents to be universally accessible- it benefits all citizens, not just handicapped ones. It's like the curb cuts that make sidewalks wheel chair-friendly- they are great for walkers and bikers as well. It only makes the city more attractive, as it adds value which everyone shares."

Why Use Accessibility In Mind For Your Section 508 Remediation: The AIM Difference

#1: Accessibility In Mind is a dedicated Section 508 and PDF/UA compliance service.

We are not a design/print house that does remediation on the side- remediating PDF documents, making them accessible and compliant, is our ONLY service.  Look at the home page of our competitors if you want to know what their main business is, then come back to AIM for your Section 508 work!

#2: We are not a middle-man, taking a commission and passing the work on to contractors.

When you work with AIM you are dealing DIRECTLY with Section 508 expert remediators, and paying less-- often 30-50% less-- than through other vendors. Deal direct, SAVE TIME AND MONEY!

http://accessibilityinmind.com/


FAQ: What fonts are compliant with Section 508?

Question: What fonts can I use? I read where you can only use system fonts Calibri, Times, Trebushi etc. and I want to use a different font for a document.

Answer: This is a common question, one that is NOT addressed in Section 508 of the Rehabilitation Act of 1973, as amended in 1998. Here's the pertinent section, "web-based intranet and internet information and applications (1194.22, sub-sections a-p)" right here.  See anything about fonts???

The regulations are not specific; various agencies have created their own interpretations and requirements. In February of this year, the Access Board published their proposal to remedy this, called the "Proposed Information and Communication Technology (ICT) Standards and Guidelines". They state, "Incorporating these standards complies with the federal mandate—as set forth in the National Technology Transfer and Advancement Act of 1995 and OMB Circular A119—that agencies use voluntary consensus standards in their regulatory activities unless doing so would be legally impermissible or impractical." And they even get more specific about their lack of specifics: "the existing 508 Standards, which contain no referenced standards."

How about that for guidance?  The proposed standards do go a long way down the long road that is accessibility, when approved. Until then, common sense is the best "voluntary consensus standard".

HHS "recommends" those fonts, but not using them does NOT mean you aren't in compliance. (HHS checklist: "Does the document utilize recommended fonts (i.e., Times New Roman, Verdana, Arial, Tahoma, Helvetica, or Calibri)?") Even with HHS, failing that checkpoint doesn't mean non-compliance; what makes a document non-compliant is if it is inaccessible. Obviously, the criteria is accessibility. The regulation does not say you have to use any particular font.

Best practice is to see if your client has a checklist or any guidance regarding their interpretation of the regs, and of course, use a readable font. Probably a no-no on the wingdings.....

More information on Section 508: http://508compliantdocumentconversion.com/

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.

EDCS Levels of Service

Total accessibility is the goal of every EDCS remediation. Contrary to common belief, passing an automatic check alone does not ensure accessibility. Un-tagged content, inactive URLs, and incorrect reading order are examples of errors that are overlooked by Adobe Acrobat's autochecks. A document that is blank to a screen reader can be made to pass but is obviously not accessible or compliant.
Structured documents are accessible documents. Comprehensive remediation adds value to documents, for both sighted and sight-impaired users.

Complete remediation includes these services:

  • Determine if the PDF file has been properly tagged. Verify tagged elements are properly sequenced and applied. Ascertain that tag list follows document reading order exactly for optimum reading order and reflow for screen readers
  • Style tags applied appropriately to all text
  • Correct pagination added to thumbnails
  • URLs checked/activated
  • Bookmarks added (documents over 9 pages)
  • Table of Contents made active
  • All internal and external active links made BLUE (optional)
  • Correct properties, initial view settings, correct tab order, "fast view" set, custom properties removed, language set
  • Tables scoped (header and data cells appropriately tagged); all tabular data edited/tagged as tables with scoped columns and rows; tables created where absent
  • Add Alternative Text. Add informative and concise alternative text and descriptions for all non-text elements
  • Artifact all table PATH (border) tags (optional)
  • Removal/artifact all background graphics
  • Complete Adobe Acrobat Pro 11 accessibility report showing no errors or warnings
  • Complete HHS checklist (optional)
  • Spot check with screen reader (JAWS or equivalent)
  • Complete Quality Check
Exclusions or additions to the listed services at client's request. Deliverables include remediated PDF and time-stamped validation reports from Acrobat Pro 11: "Accessibility Full Check", and agency checklist if requested. Please provide guidelines/requirements at time of bid request.

Fillable Form PDFs- add these services:

  • Creation/edit of form fields
  • Tool tips added to form fields.
  • Formatting applied to form field (date, currency, etc.)
Note: Remediation limited to form documents created in Acrobat.

Minimum specifications:

  • No character encoding errors present
  • Document created with editable fonts
  • Alternate text descriptions of graphics/figures included or provided by client
  • Document properties (Title, Author, Subject, Keywords) provided by client

Terms and Conditions

All bid requests will include expected time frame for the job, date of document delivery from client to EDCS and date of remediated document delivery from EDCS to client. Bids provided by EDCS are valid for 30 days. EDCS will evaluate documents requiring remediation and deliver a quotation of price per page for desired level of remediation  and any additional charges that may be incurred to complete the remediation. Our evaluations are thorough, but there are sometimes issues that do not show in our evaluation that may make some documents impractical or impossible to remediate into accessible documents. EDCS reserves the right to inform client of any documents that fall into this category prior to document remediation; documents will not be remediated and remediation charges for these documents will be subtracted from final invoice. At client’s request, and upon agreement from EDCS, documents not remediated due to aforementioned issues, or any pre or post-remediation document processing or editing, will be charged at $100 per hour. Services not specifically required for compliance may be excluded from remediation, at client's request. Documents 50 pages or less are subject to a $50 short-document administrative fee.  
Terms effective 12/11/2013

The Straight Scoop on URLs in Section 508 Compliant Documents

Below is Section 1.8.1 from an SSA Guide to producing compliant Word-PDF documents.What do you think? Is this in conflict with standard HHS compliance checklist? Sounds like fully qualified URLs aren't really that important, and actually make a document LESS accessible. Make sure documents have proper tagging of hyperlinks for common sense accessibility:

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.
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.

Where it is important to have the URL displayed on the printed page, Method #4 is the same as method #3, but with the URL also spoken in the list. This method is perfectly acceptable, so long as the name comes first and the URL comes last in each link.
--------------------------------------------------------------------

B) Development Methods

1.    Right click any hyperlink in the document.
2.    Make sure that in the Hyperlink dialog box the 'Text to display' field has a link name that makes sense when spoken in isolation.
Note: See Rationale, above for an explanation of how links are spoken by Screen Readers.

C) Testing Methods

Examine the document for instances of links that have names like 'Click Here', and/or links that are just URLs, like http://ssahost.ba.ssa.gov/arc/. These links need to be remediated according to Development Methods, above.

Section 508 News: One More Battle in the Fight for Equality in the Workplace

From Gary Wunder, on the NFB.org website, a great article about the realities of accessibility. We're not there yet...

" Government and industry have been slow to acknowledge the technological challenges the blind are beginning to face as we perform the routine duties of keeping a house and cooking our meals, but as early as 1998 the federal government acknowledged the need for technology usable by the blind in places of employment by adopting Section 508 of the Rehabilitation Act. In a nutshell the law says that anything built or purchased by the federal government must be accessible to people with disabilities, including the blind. The law covers everything from office computers to the copy machine, but the reality of federal compliance falls far short of the promises so eloquently proclaimed in the statutes of our land."

"Section 508 must make real in the federal workplace the promises it boldly proclaims as the law of the land."

Read the article

Department of Homeland Security Sued for Section 508 Violations


On April 26, 2013, Michael Leiterman, a lawyer for the Department of Homeland Security (DHS)  filed a suit against his employer, "for violating federal anti-discrimination laws that require the federal government to provide equal opportunity to people with disabilities", citing Section 508 of the Americans with Disabilities Act (ADA)

Section 508 is an amendment to the Rehabilitation Act, passed by Congress in 1998. This amendment specifies that government agencies must make all electronic and information technology available to people with disabilities. Since its adoption in 1998, the digital realm has exploded, making Section 508 compliance even more necessary to ensure accessibility for people with disabilities.

The lawsuit alleges that DHS is in violation of the Act “by purchasing, developing, and implementing inaccessible technology, using inaccessible training and testing platforms and materials, requiring Mr. Leiterman to provide accessibility  testing, troubleshooting, and correction for CBP’s technology, failing to provide reasonable accommodations for his disability, and denying him a promotion because of his disability and the agency’s inaccessible technology.”

Mr. Leiterman, who is blind, has worked at Customs and Border Protection (“CBP”), a division of the United States Department of Homeland Security (“DHS”), since August 2006. The lawsuit alleges multiple instances of violations, including inaccessible documents, intranets, and online training modules.

The brief...

Document Creators: Are you responsible for Section 508 compliance?

Let us be among the first to remind you to check the fine print in the specifications for the document you are creating right now. Is their any federal money involved? That's just one reason to make sure your document is accessible and compliant with Section 508.

These regulations have been in place since 1973, but are just beginning to be monitored and enforced; several lawsuits were required before production contracts started routinely specifying compliance with Section 508

Here's the official word:

Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. § 794d) requires the federal government to ensure that the electronic and information technology that it develops, procures, maintains, or uses is accessible to persons with disabilities. Section 508 also directs the Attorney General to submit reports to the President and Congress on the state of federal agencies' compliance with the Act's requirements. In preparation for its report, the Department of Justice conducts a survey of federal agencies to obtain information on the state of compliance with Section 508, including the Section 508 Electronic and Information Technology Accessibility Standards
.
Each federal department or agency is required by Section 508 to provide the Department of Justice with information that is needed to prepare the reports. Following below is information about the Department of Justice’s Section 508 surveys and reports.

Plan now and avoid the rush this fall- learn more about Section 508 document preparation and remediation at  Electronic Document Compliance Services website.

Work Directly With a 508 Document Specialist


Electronic Document Compliance Services clients work directly with our Section 508 document remediators, streamlining the process and reducing “middle-man” costs.
In addition to remediation of documents for section 508 compliance, EDCS can review your documents and provide  certification of 508 compliancy, guaranteeing accessibility and usabilty.
Passing automatic PDF and 508 checks is just the first step in our complete certification service; our federally-certified staff will test your documents with both automatic and manual procedures to assure they meet or exceed all 16 requirements of Section 508, and provide you with a certificate  and an affadavit affirming compliance.

If you want answers to your compliance questions and quick turnaround, call now and talk to a specialist: 919-410-7408

The Truth About the Refresh: WCAG 2.0 It I!

In January 2017, the U.S. Access Board issued the Information and Communication Technology (ICT) Standards and Guidelines, updating its ex...