Section 508 Compliance (VPAT)

Date: 08/22/2011

Name of Product: Google Sites (additional product VPATs)

Point of Contact: Abhishek Surana (surana@google.com)

Summary Table
Criteria Supporting Features Remarks
Section 1194.21 Software Applications and Operating Systems Applicable Partial support
Section 1194.22 Web-based internet information and applications Applicable Partial support
Section 1194.23 Telecommunications Products Not Applicable
Section 1194.24 Video and Multi-media Products Not Applicable
Section 1194.25 Self-Contained, Closed Products Not Applicable
Section 1194.26 Desktop and Portable Computers Not Applicable
Section 1194.31 Functional Performance Criteria Applicable Partial support
Section 1194.41 Information, Documentation, and Support Applicable Supports with exceptions
Section 1194.21 Software Applications and Operating Systems
Criteria Supporting Features Remarks
(a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually. Supports with exceptions Users can create and edit a site, create and edit pages using keyboard. Manage Site has some limitations.
(b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer. Supports Google Sites does not interfere with or deactivate the accessibility features of the operating system.
(c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that Assistive Technology can track focus and focus changes. Supports with exceptions Focus tracking is visible on standard HTML components and some elements in Manage Site section. Not clearly visible on all UI elements.
(d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to Assistive Technology. When an image represents a program element, the information conveyed by the image must also be available in text. Does not support No information on identity, operation and state is available on Google Sites UI elements.
(e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance. Supports Google Sites bitmap images are consistently used to represent certain functions, such as toolbar formatting options.
(f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes. Does not support No sufficient text information is exposed in Google Sites.
(g) Applications shall not override user selected contrast and color selections and other individual display attributes. Supports with exceptions Google Sites UI remains mostly visible in Windows High Contrast mode, as well as respecting most color settings.
(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. Supports Google Sites has no core features that utilize animation.
Section 1194.21 Software Applications and Operating Systems (continued)
Criteria Supporting Features Remarks
(i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Supports Google Sites does not rely on color coding as the only means of conveying information.
(j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided. Supports Google Sites provides themes with full font and color customization.
(k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz. Supports Google Sites has no flashing or blinking text, objects or other elements
(l) When electronic forms are used, 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. Does not support Forms for page content input are not accessible for Assistive Technology.
Section 1194.22 Web-based Internet Information and Applications
Criteria Supporting Features Remarks
(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). Supports All core interactive elements of Google Sites have text equivalents.
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Does not support Inserted video content does not support display of closed captions.
(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 Core Google Sites functionality does not rely on color alone to present information.
(d) Documents shall be organized so they are readable without requiring an associated style sheet. Does not support As Google Sites is a web-based application (not a document), its UI relies heavily on the use of associated style sheets.
(e) Redundant text links shall be provided for each active region of a server-side image map. Supports Google Sites does not use image maps.
(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 Google Sites does not use image maps.
(g) Row and column headers shall be identified for data tables. Supports Row and column headers can be added to inserted data tables by editing the HTML.
(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 Markup for association of data cells and headers can be added by editing the HTML.
(i) Frames shall be titled with text that facilitates frame identification and navigation. Supports No frames designed for interactivity are used for Google Sites core features.
(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 Google Sites UI does not cause screen flicker with a frequency greater than 2 Hz and lower than 55 Hz.
(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. Does not support As Google Sites is a web-based application (not a document), its UI and data cannot readily be represented and maintained in a text-only page.
(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. Does not support Much of the core scripting functionality critical to interacting with Google Sites is not usable from the keyboard alone, nor through interaction with Assistive Technology.
(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 Google Sites core functionality does not require that an applet, plug-in or other application be present.
(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 with exceptions Some of the forms required to fully customize your Google Site through Settings do not have proper form labels.
(o) A method shall be provided that permits users to skip repetitive navigation links. Supports with exceptions Google Sites includes shortcut keys. Does not make good use of headings.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Supports Google Sites does not require a timed response as part of its core functionality.
Section 1194.31 Functional Performance Criteria
Criteria Supporting Features Remarks
(a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided. Supports with exceptions Basic operations are read by screen reader.
(b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided. Supports Google Sites supports the use of screen magnifiers.
(c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or hard of hearing shall be provided Supports Google Sites does not rely on sound alone to access any of its core functionality.
(d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided. Supports Google Sites does not rely on audio to present information.
(e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive Technology used by people with disabilities shall be provided. Supports Google Sites does not require user speech.
(f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided. Supports The parts of Google Sites that cannot be operated using the keyboard alone have significantly large target areas that would not cause problems for people with fine motor control or limited reach and strength.
Section 1194.41 Information, documentation, and support.
Criteria Supporting Features Remarks
(a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge. Supports Google Help Centers provide electronic versions of all product support documentation.
(b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge. Supports Google Help Centers provide information on accessibility features in the documentation. Electronic versions of all product support documentation are provided.
(c) Support services for products shall accommodate the communication needs of end-users with disabilities. Supports with exceptions Google Help Centers are compatible with screen-reader technology. However, only electronic versions of all product support documentation are available.