Skip to main content

Section 508 Compliance of the RHIhub Website

Section 1194.22 Web-based Internet information and applications - Detail
Voluntary Product Accessibility Template
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 Every image has an alt description. Complex graphics are accompanied by detailed text descriptions. The alt descriptions succinctly describe the purpose of 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 have empty alt descriptions (alt= "").
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Not Applicable There are no multimedia presentations included in the primary content of the RHIhub website. Selected content hosted on this site from other sources may not meet this 508 criterion.
(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 All information conveyed with color is also available without color. Contrast throughout the site is good.
(d) Documents shall be organized so they are readable without requiring an associated style sheet. Supports Style sheets are not necessary in order to read the RHIhub website. All pages are still understandable when the style sheet is turned off
(e) Redundant text links shall be provided for each active region of a server-side image map. Not Applicable There are no server-side image maps on the RHIhub website.
(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. Not Applicable There are no client-side image maps on the RHIhub website.
(g) Row and column headers shall be identified for data tables. Supports Data tables have the column and row headers appropriately identified (using the <th> tag) and tables used strictly for layout purposes do NOT have header rows or columns.
(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 Table cells are associated with the appropriate headers via the scope="row" and/or the scope="column" attributes.
(i) Frames shall be titled with text that facilitates frame identification and navigation Not Applicable Frames are not used on the RHIhub website.
(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 There are no graphic animations, objects, or pages which cause the screen to flicker on the RHIhub website.
(k) A text-only page, with equivalent information or functionality, shall be provided to make a website 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. Not Applicable Text-only equivalent pages are not necessary because every page on the RHIhub website complies with all other paragraphs of §1194.21.
(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 Most Javascript used on the site is in the head element, and does not require a <noscript> tag. Where Javascript does appear in other areas, it is identified by functional text that can be read by Assistive Technology and an alternative method of accessing equivalent functionality is provided.
PHP scripting used on the site creates dynamic content which is parsed server-side, so only Section 508 compliant pages are served to the client browser.
(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 A link to the Accessibility page, which contains a link to a disability-accessible page where the plug-in can be downloaded, is provided on every page.
All Acrobat PDF files and the content within them are accessible to Assistive Technology, or else an alternative means of accessing equivalent content is provided (HTML).
(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 All forms on the RHIhub website are fully accessible and equivalent to people using Assistive Technology. All form elements have labels associated with them in the markup (i.e. the id and for, HTML elements) or titles where labels are not possible.
(o) A method shall be provided that permits users to skip repetitive navigation links. Supports There is skip navigation provided throughout the web pages, and many access key shortcuts which are fully described on the Accessibility page.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Not Applicable Timed responses are not required anywhere on the RHIhub website and the user has control over the timing of content changes.

Section 508 Compliance of this site provided by: Criterion 508 Solutions, Inc.