All pages on this SummaCare website are accessible to individuals with disabilities in accordance with Section 508 of the Rehabilitation Act. Striving for the highest accessibility standards, its features include:
a. A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content.
In developing the SummaCare website, we have ensured that every image, Java applet, Flash file, video file, audio file, plug-in, etc. that conveys content has an equivalent alt description or text description, or is described in the adjacent text. Complex graphics (graphs, charts, etc.) are also accompanied by detailed text descriptions, either through a description in the body of the page, a link to a description on a separate page, or the longdesc attribute [See Note 1].
The alt descriptions succinctly describe the content conveyed by the objects, without being too verbose (for simple objects) or too vague (for complex objects). Alt descriptions for images used as links are descriptive of the link destination. Decorative graphics with no other function are inserted as background images using CSS or have empty alt descriptions (alt= ""), but they never have missing alt descriptions. Images with text alternatives in element content are given empty alt text (alt= "").
b. Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
SummaCare website video files have synchronized captions and audio files have captions and/or transcripts.
c. Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
Color is not used solely to convey important information, and sufficient contrast is provided.
d. Documents shall be organized so they are readable without requiring an associated style sheet.
Our style sheets may be used for layout, but the document is still understandable (even if less visually appealing) when the style sheet is turned off.
e. Redundant text links shall be provided for each active region of a server-side image map.
Separate text links are provided outside of the server-side image map to access the same content that the image map hot spots access. Client-side image maps cannot be used to provide the same hot spot areas (see section f).
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.
Client-side image maps are used on the SummaCare website. Appropriate alt text is provided for the image, as well as each hot spot region.
g. Row and column headers shall be identified for data tables.
Data tables have the column and row headers appropriately identified (using the th tag). Tables used strictly for layout purposes do not have row or 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.
Our data table cells are associated with the appropriate headers (e.g. with the id, headers, scope and/or axis attributes).
i. Frames shall be titled with text that facilitates frame identification and navigation.
Each frame is given a title that describes the frame’s purpose or content.
j. Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
No elements on the SummaCare website flicker at a rate of 2 to 55 cycles per second, thus reducing the risk of optically-induced seizures.
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. [See Note 2]
A text-only version is created only when there is no other way to make the content accessible or when it offers significant advantages over the "main" version for certain disability types. The text-only version provides equivalent content and is up-to-date with the "main" version. The text-only version provides the functionality equivalent to that of the "main" version. An alternative is provided for components (e.g. plug-ins, scripts) that are not directly accessible.
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.
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). [See Note 3, 4, 5].
A link is provided to a page where the plug-in can be downloaded. All Java applets, scripts and plug-ins (including PDF files and PowerPoint files, etc.) and the content within them are accessible to assistive technologies, or else an alternative means of accessing equivalent content is provided.
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.
All our form controls have text labels. Form elements have labels associated with them in the markup (i.e. the id and for or label elements). Dynamic HTML scripting of the form does not interfere with assistive technologies and is keyboard accessible.
o. A method shall be provided that permits users to skip repetitive navigation links.
A link is provided to skip over lists of navigational menus or other lengthy lists of links.
p. When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
The user has control over the timing of content changes.
SummaCare is committed to ensuring that our website is accessible to all viewers. If you have any questions or suggestions, please contact us, as we are continually striving to improve the experience for all our visitors.
Note 1: Until the longdesc tag is better supported, it is best to use it in conjunction with a standard link to a longer description.
Note 2: “Text-only” and “accessible” are NOT synonymous. Text-only sites typically only help people with certain types of visual or cognitive disabilities. They are usually not helpful to users with disabilities.
Note 3: Standalone media players are usually more accessible than embedded media players.
Note 4: A PDF file can be made accessible to screen reader users, but it may be best to include an accessible HTML version of a document instead of or in addition to PDF.
Note 5: PowerPoint files are currently not directly accessible unless the user has a full version of the PowerPoint program on the client computer. It is recommended that an accessible HTML version be provided instead of or in addition to the PowerPoint version