VPAT — Section 508

This VPAT is for you if you are a procurement officer for either a US federal government agency, or a state, city, or county agency seeking services that comply with US Section 508 accessibility guidelines for Web development, including:

Web programming (Website applications)

Web coding (HTML5, XHTML, CSS, JavaScript, jQuery)

Website remediation (website repairs)

Webmaster services (website maintenance)

VPAT Summary for Web Development Services

Charlottesville SEO Web Development, LLC, is a small, woman and minority owned business in Central Virginia. We take great pride in delivering Web development services that are 100% compliant with Section 508 accessibility guidelines. We guaranty the website coding we deliver will be fully compliant with each applicable guideline specified in Section 508 of the Rehabilitation Act.

Section 508 Forward Compliance – WCAG 2.0 Level AA

As agencies scramble to meet updated Section 508 Guidelines, modeled after international Web Content Accessibility Guidelines, WCAG 2.0 Level AA, rest assured the website programming we deliver is fully compliant with these more stringent guidelines, set forth by the World Wide Web Consortium (W3C).

Section 1194.22 Web-based Internet Information and Applications

For detailed explanations of the guidelines below, please visit http://www.access-board.gov/sec508/guide/1194.22.htm.

Definitions

“Supports”

The product or service fully meets the letter and intent of the Criteria.

“Supports with Exceptions”

The product or service does not entirely meet the letter and intent of the Criteria, but does provide some level of access.

“Supports through Equivalent Facilitation”

The product provides alternative methods to meet the intent of the Criteria.

“Does not Support”

The product or service does not currently meet the letter or intent of the Criteria.

“Not Applicable”

The Criteria do not apply to the specific product(s) or services.

VPAT for Web Development Services

Criteria	Supporting Features	Remarks and Explanations
(a) A text equivalent for every non-text element shall be provided (e.g., via “alt”, “longdesc”, or in element content).	Supports	We provide appropriate and descriptive text equivalents for non-text elements. We insert relevant “ alt ” text for simple images and use long descriptions when required. Long descriptions are provided in context wherever possible and otherwise through a text link. PDF files are tagged for accessibility. When image maps are required, we use client-side image maps, if possible, and code these to include relevant text equivalents.
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.	Supports	We provide appropriate alternatives for multimedia presentations. For video, we provide synchronized captions. For prerecorded audio, we provide a transcript.
(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.	Supports	We never use color as the only means to convey information.
(d) Documents shall be organized so they are readable without requiring an associated style sheet.	Supports	All web documents are tested with style sheets disabled to ensure that a logical reading order is maintained.
(e) Redundant text links shall be provided for each active region of a server-side image map.	Supports	We do not use server-side image maps unless a client requires us to do so, in which case redundant text links are inserted.
f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.	Supports	We do not encourage the use of image maps. If a project requires image maps, we use client-side image maps whenever possible.
(g) Row and column headers shall be identified for data tables.	Supports	We markup data tables with appropriate tags to display row and column headers.
(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.	Supports	For complex data tables, we use markup to associate headers and data cells such as the “scope” attribute. We also markup each column and heading.
(i) Frames shall be titled with text that facilitates frame identification and navigation	Supports	We discourage the use of frames. If a client requests frames, we use the “title” attribute to indicate the function of each frame.
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.	Supports	We avoid techniques that cause the screen to flicker.
(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.	Supports	Preparing a text-only version of content is seldom necessary. When such a page is required, we provide it and also insert reminders within the code to update the text-only page whenever the primary page is updated.
(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by Assistive Technology.	Supports	When scripts are present, we ensure that features are keyboard operable and accessible with assistive technology. If this cannot be achieved, we work with the client to ensure a no-script version of the content is available.
(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with 1194.21(a) through (l).	Supports	We insert links to download required applets and plug-ins whenever appropriate.
(n) When electronic forms are designed to be completed on-line, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.	Supports	Form fields and controls are explicitly associated with labels. We also use titles to convey information as appropriate.
(o) A method shall be provided that permits users to skip repetitive navigation links.	Supports	We insert a set of “skip links” that enable assistive technology users to access or bypass repetitive navigation links.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.	Supports	Most form controls do not require a timed response. When an application requires a time limit, we incorporate an alert system and enable users to request more time to complete the timed task.