Google Docs

Get started

Google Docs: Presentations

Section 508 Compliance

Date: 10/28/2011
Name of Product: Google Docs (Presentations) (additional product VPATs)
Point of Contact: Jeffrey Harris, Product Manager, Documents and Presentations

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. Does not support Using core functionality in the document edit area and surrounding UI is not readily done from the keyboard alone, especially for navigating slide content and formatting options in the UI.
 
(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 Docs (Presentations) 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. Does not support Google Docs (Presentations) has very little focus tracking, most of it not clearly visible.
(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 Most core UI components do not expose necessary information available to Assistive Technology.
(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 Docs (Presentations) 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 Not all sufficient text information is exposed in Google Docs (Presentations), such as e.g. text attributes.
(g) Applications shall not override user selected contrast and color selections and other individual display attributes. Supports with exceptions Google Docs (Presentations) remains partially visible (slide content, thumbnail view) in a low vision setting (e.g. 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 Docs (Presentations) 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 Docs (Presentations) 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 Docs (Presentations) does not allow for applying color themes to the product itself, but for font and slide colors/themes a range of color options is provided.
(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 Docs (Presentations) has no flashing or blinking text, objects or other elements with a blink frequency greater than 2 Hz and lower than 55 Hz.
(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. Supports with exceptions Most form functionality in Google Docs (Presentations) is accessible to those using 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 Docs (Presentations) have text equivalents.
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Supports Google Docs (Presentations) core features does not include any multimedia presentations, and inserted videos does support the display of 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 Google Docs (Presentations) does not rely on color coding as the only means of conveying information.
(d) Documents shall be organized so they are readable without requiring an associated style sheet. Supports Google Docs (Presentations) provides an HTML viewer that supports documents being readable without requiring an associated style sheet.
(e) Redundant text links shall be provided for each active region of a server-side image map. Supports Google Docs (Presentations) 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 Docs (Presentations) does not use image maps.
(g) Row and column headers shall be identified for data tables. Supports The tables in Google Docs do include programmatically connected row and column headers as part of their data table grid.
(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 The tables in Google Docs do include programmatically connected row and column headers as part of their data table grid.
(i) Frames shall be titled with text that facilitates frame identification and navigation. Does not support Google Docs (Presentations) uses some untitled frames.
(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 Docs (Presentations) 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 Docs (Presentations) 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. Supports with exceptions Most core functionality of Google Docs (Presentations) that rely on scripting is accessible to Assistive Technology users. Exceptions include collaborative features and some dialog workflows.
(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 Docs (Presentations) 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 interact with your Google Docs (Presentations) through dialogs do not have proper form labels.
(o) A method shall be provided that permits users to skip repetitive navigation links. Supports  
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Supports Google Docs (Presentations) 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. Does not support Most core functionality of Google Docs (Presentations) is not accessible to Assisitve Technology users.
(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 Docs (Presentations) 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 Docs (Presentations) 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 Docs (Presentations) does not rely on audio alone 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 Docs (Presentations) 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. Does not support Using core functionality in the document edit area and surrounding UI is not readily done from the keyboard alone, especially for navigating slide content and formatting options in the UI.
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.  


Appendix:

Keyboard Shortcuts
Keyboard shortcuts help you save time by allowing you to never take your hands off the keyboard to use the mouse. You'll need a Standard 101/102-Key or Natural PS/2 Keyboard to use the shortcuts.

Note: If you use a Mac, you can use the shortcuts below by replacing Ctrl with Command key (or 'Apple' key).

Function Shortcut
Bold Ctrl B
Copy Ctrl C
Italicize Ctrl I
Insert new slide Ctrl M*
Save Ctrl S
Underline Ctrl U
Paste Ctrl V
Cut Ctrl X
Move down one screen Page Down
Move up one screen Page Up
Exception for the Mac

* Ctrl M: Insert comment (Cmd M is used to minimize a window).