On August 1, 2008 a revised edition of New York's Policy and Standard for web site accessibility took effect. The Policy received a new number, NYS-P08-005, and the Standard's new number is S08-005. The individual checkpoints within the Standard were also renumbered, as you will see in the summary of changes below.
Note: This policy was revised as of May 2010. For more information, please see our New York State and 508 page.
| Standard | Comment |
|---|---|
| 4.1 Text Equivalents for Non-Text Content | |
| 4.1.1. A text equivalent will be provided for all non-text element(s). Non-text elements will include, but are not limited to, images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), and programmatic objects, ASCII art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video. | The reference to "Applet" has been dropped, since "applet" is now a deprecated element. |
| 4.1.2. Ensure that equivalents for dynamic content are updated when the dynamic content changes. | |
| 4.1.3. Ensure that pages with scripts or other programmatic objects are usable with current assistive technology. | The new language is simpler, and in essences states "Just make sure it works." Also removed is the reference to manually-updated alternative pages, which are now discouraged. |
| 4.1.4. A text equivalent will be provided for all non-text element(s) through the following means: alt, longdesc, or in element content. | |
| 4.1.5. An alt attribute will convey the same information, in a textual manner, as intended by the non-text element. | |
| 4.1.6. Graphics which are strictly for decoration, such as bullets, will have an alt attribute defined with no value (e.g., alt=""). | Historically, a space was required in the alt text to prevent validators from having a fit. This is no longer true, and in fact, the null string is now preferred. |
| 4.1.7. An alt attribute, within an image element, will not exceed 150 characters. | |
| 4.1.8. A longdesc attribute is required within an element if alt text exceeds 150 characters. A descriptive link will also be provided. | |
| 4.1.9. From the date of this standard forward, alternative text versions of web sites, if used, should be dynamically generated to insure that each site contains equivalent information and functionality at all times, available for use by people with disabilities, mobile users, users with low-bandwidth connections, and those users who simply prefer a non-graphical interface. Manually updated alternatives are discouraged. | This is a new standard included to encourage the dynamic generation of alternative sites, if such sites are used. Text-only alternative sites that must be maintained independently have notoriously fallen behind and not been maintained, thus interfering with the delivery of information to disabled people. Such sites are discouraged, especially compared with a site where alternatives can be generated dynamically. |
| 4.2 Use of Color for the Conveyance of Information | |
| 4.2.1. Information will be conveyed in a manner that is not solely dependent on color as the primary means of informing a user how to interpret information. | |
| 4.2.2. Foreground and background colors will provide sufficient contrast. | |
| 4.3 Document Structure | |
| 4.3.1. Web pages will be created using the most current web document specifications (e.g., HTML, XML, XHTML). | |
| 4.3.2. HTML pages should include a document type declaration (sometimes referred to as a DOCTYPE statement) and are valid according to the HTML version specified by the document type declaration. XHTML, SVG, SMIL, and other XML-based documents reference a Document Type Definition (DTD) or other type of XML schema. In absence of a document type declaration, HTML pages must still enable user agents, including assistive technologies, to accurately interpret and parse content. | This is a change from the previous standard, which required all pages to include a valid doctype declaration. However, keep in mind that if you do not include a doctype declaration, you will not be able to use an automated tool to test your pages. To provide assurance that your content will be usable by people with disabilities using assistive technology, you will need to have your content tested using assistive technology, preferably by a person with disabilities. |
| 4.3.3. The use of deprecated elements or attributes is not allowed (e.g., the usage of FONT, CENTER and APPLET are deprecated). | |
| 4.3.4. Web pages will be created using style sheets to achieve formatting and stylistic effects whenever possible. | |
| 4.3.5. All natural language usage will be clarified using the lang attribute when the written language is not English. | |
| 4.4 Navigation and Links | |
| 4.4.1. Web pages will be designed to enable users to skip repetitive navigation links, for example, by using a "skip navigation" or "skip to content" link close to the top of the page. | This standard has not changed, but examples have been added to clarify its intent, which is to allow visitors to skip long navigation sections to reach the content with a minimum of key strokes. |
| 4.4.2. All text links will indicate the destination or purpose. | |
| 4.4.3. All state agency web pages will allow the user to return to that state agency's home page. | |
| 4.4 was removed because it was considered redundant. The issues addressed by 4.4 are covered by standard 12. 2. | |
| 4.5 Flicker/Blink | |
| 4.5.1. Web site screen elements will not have a flicker rate with a frequency between 2Hz and 55Hz (2 to 55 flashes per second). | |
| 4.5.2. A mechanism will be in place to allow users to turn off screen elements that flicker | |
| 4.5.3. The use of the blink element is prohibited. | The blink element is also deprecated. |
| 4.6 Timed Responses | |
| 4.6.1. When a programmed timed response is used on a web page, a notification will be provided on that web page identifying the time limits and providing the option to extend or remove the limit. | |
| 4.6.2. Client-side auto-refresh or client-side auto-redirect will not be used without a mechanism in place to first alert the user. | |
| 4.7 Tables | |
| 4.7.1. All data tables should have a summary attribute. | The word "data" has been added. Best practice for labeling format-only tables has evolved to the point where it is now considered better not to provide the summary attribute. The change in this standard reflects the new thinking. |
| 4.7.2. In data tables appropriate markup must be used to provide context for each table cell. | Standards 7.2, 7.3 and 7.4 all described how to make a data table accessible, but in reality, there are many techniques, all valid, and some more appropriate than others in certain settings. Rather than dictate how a table will be marked up, the new standard simply states that this will occur, and leaves how up to the developer. |
| 4.8 Frames, Context, and Orientation | |
| 4.8.1. If frames are used: a. Each frame must be identified with a descriptive title attribute that describes the purpose of each frame(s) and how they relate to each other. b. For title text greater than 150 characters a longdesc attribute will be used. |
Standard 4.8.1 that required the use of the noframes tag has been removed. Since properly marked up frames are accessible, it was felt that the prescription of the element was unnecessary. Frames still need to be accessible; the new wording does not change that. |
| 4.9 Image Mapping | |
| 4.9.1. Image mapping will be client-side based. | |
| 4.9.2. Redundant text links will be provided for each active region of a client-side image map. | |
| 4.10 Audio Only Information will not be conveyed by single audio (audio clip sounds to provide instructions, warnings or other information) alone. |
|
| 4.11 Multimedia | |
| 4.11.1. Audio State agencies will provide synchronized text captions for multimedia content containing speech, or other audio necessary to understand the content, in accordance with the following schedule: a. By January 1, 2007, 25 percent of all multimedia content containing speech, or other audio, will be captioned. b. By January 1, 2009, 50 percent of all multimedia content containing speech, or other audio, will be captioned. c. By January 1, 2010, 100 percent of all multimedia content containing speech, or other audio, will be captioned. |
References to 2005 have been removed, and the requirement that all such content is properly rendered accessible by 2010 has been added. |
| 4.11.2. Video/Visual State agencies will provide a video description for multimedia content that contains video, or other visual information necessary for the understanding of the content, in accordance with the following schedule: a. By January 1, 2007, 25 percent of all multimedia content containing video, or other visual information necessary for the understanding of the content, will include a video description. b. By January 1, 2009, 50 percent of all multimedia content containing video, or other visual information necessary for the understanding of the content, will include a video description. c. By January 1, 2010, 100 percent of all multimedia content containing video, or other visual information necessary for the understanding of the content, will include a video description. |
References to 2005 have been removed, and the requirement that all such content is properly rendered accessible by 2010 has been added. |
| 4.11.3. Webcasts State agency webcasts will have synchronized captioning of the speech, or other audio content contained in the webcast, in accordance with the following schedule: a. By January 1, 2007, 25 percent of all webcast hours residing on the web site will include captioning. b. By January 1, 2009, 50 percent of all webcast hours residing on the web site will include captioning. c. By January 1, 2010, 100 percent of all webcast hours residing on the web site will include captioning. |
References to 2005 have been removed, and the requirement that all such content is properly rendered accessible by 2010 has been added. |
| 4.11.4. Webcasting Open Meetings As of the effective date of this standard, all state agency open meeting webcasts, as defined by the State Open Meetings Law and required by Executive Order 3, will have synchronized text captioning of the speech, or other audio content contained in the webcast or linked from the agency web site, within seven days of the event. |
This new standard brings the accessibility standards in line with the standards for web casting public meetings. No change other than having all the wording in one place. |
| 4.12 Scripting | |
| 4.12.1. If web pages utilize scripting languages to display content or create interface elements, the information that is provided by the script will be identified with functional text that can be read by assistive technology devices. | |
| 4.12.2. All functionality of the web page must be operable through the keyboard, or a keyboard interface. In the event that functionality provided by scripting languages cannot be read by assistive technology devices, there must be an alternative means of accomplishing the same task that can be read by such devices. | This standard has been rewritten considerably in an effort to better state the goal, that pages with scripts are accessible or alternative means of performing the same function are made available, as opposed to the means this is accomplished. |
| 4.12.3. A mechanism (e.g., a text notice – "the following link will open a new browser window") will be in place to alert the user prior to the opening of an additional web browser window or a redirect that disables a browser's back button. Instructions must be provided to allow user to return to the original page. | This standard has been rewritten to clarify the original intent, which was open to misinterpretation. The original intent — that people using assistive technology can navigate in expected ways — is now much clearer. |
| 4.12.4. If a web page or web-based application generates an operating system-based alert panel, focus must be moved to the alert panel. | Another situation where AT users could get lost has been added. Without focus being sent to a pop-up operating system-based panel, the page and application could be waiting for a response, and the user of AT would be totally unaware, and completely incapable of manipulating the page. This standard insists on moving the focus so the panel can be read and dispensed with. |
| 4.12.5. All documents with client-side scripting will provide equivalent content or functionality in another format. | This standard has been updated to remove the reference to the noscript tag. The intent is to allow the developer to meet the goal of the standard without prescribing the method that goal is met. |
| 4.13 Forms | |
| 4.13.1. On-line forms will allow people using assistive technology devices to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. | |
| 4.13.2. A label element will be used for all input elements. | |
| 4.13.3. Form elements will be in logical tab order. | |
| 4.14 Downloadable/Embedded Objects | |
| 4.14.1. Word processing documents, spreadsheets, and programmatic objects (e.g., Flash or Shockwave objects) must be served in a manner that can be read and used with assistive technology whenever possible. When documents that cannot be read with assistive technology are used, links to accessible versions of the documents are required. | The standard has been updated in response to the improved accessibility of proprietary formats. Where most proprietary documents in the past could not be read by AT, that is now longer true, and in some cases, these formats are actually easier to manipulate. Documents that cannot be read without AT still need alternatives present on the web site. |
| 4.14.2. When hardware, software and assistive technology devices are controlled by a state agency, downloadable documents (e.g., word processing documents, spreadsheets, Portable Document Format (PDF)) available through an intranet or extranet will be allowed. | |
| 4.14.3. Agencies with web sites that use downloadable or embedded objects must provide reasonable accommodations for individuals who do not have the software necessary to read or use the objects, either on the web site directly or by providing contact information that gives such individuals access to the information or function. | Understanding that most formats can now be read by AT, but that not everyone has the most up-to-date technology available, this standard allows agencies to provide a non-web-based alternative when visitors do not have the technology necessary to read the pages. The underlying assumption is that the objects are accessible, but there may be individuals without the proper tools to be able to use them. In that case, contact information or some similar method most be provided so the individual can still execute the function or obtain the information provided by the objects. |
| 4.14.4. Documents in Portable Document Format (PDF) should be properly marked up to support assistive technology whenever possible. If PDFs are created from scanned images, a link to an accessible version of the document is required. | This new standard expressly requires that scanned PDFs be represented on the web site in another format that is accessible. It is an explicit restatement of standard 14.1 in the most popular case to remove any doubt whether certain PDFs are acceptable without alternative versions on the web site. |