Section 508 Compliance
Section 508 requires that when Federal agencies develop, procure, maintain, or use electronic and information technology, Federal employees with disabilities have access to and use of information and data that is comparable to the access and use by Federal employees without disabilities, unless an undue burden would be imposed on the agency. Section 508 also requires that individuals with disabilities seeking information or services from a Federal agency have access to and use of information and data that is comparable to that provided to the general public, unless an undue burden would be imposed on the agency.
Wyn Enterprise
| Criteria | Conformance Level | Description | Document Portal Resource Portal |
Report Viewer |
|---|---|---|---|---|
| 1. Perceivable | Information and user interface components must be presentable to users in ways they can perceive | |||
| Guideline 1.1 Text Alternatives | Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. | |||
| 1.1.1 Non-text Content | All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. | Partially Supported | Partially Supported | |
| Controls, Input | Partially Supported | Partially Supported | ||
| Time-Based Media | If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.) | Supported by an alternative | Not Applicable | |
| Test | If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content. | Not Applicable | Not Applicable | |
| Sensory | If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content. | Not Applicable | Not Applicable | |
| CAPTCHA | If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities. | Not Applicable | Not Applicable | |
| Decoration, Formatting, Invisible | If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology. | Partially Supported | Supported | |
| Guideline 1.2 Time-based Media | Provide alternatives for time-based media. | |||
| 1.2.1 Audio-only and Video-only (Prerecorded) | (Level A) | For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such. | Supported by an alternative | Not Applicable |
| Prerecorded Audio-only | An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content. | Not Applicable | Not Applicable | |
| Prerecorded Video-only | Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content. | Supported by an alternative | Not Applicable | |
| 1.2.2 Captions (Prerecorded) | (Level A) | Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. | Not Applicable | Not Applicable |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | (Level A) | An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. | Supported by an alternative | Not Applicable |
| 1.2.4 Captions (Live) | (Level AA) | Captions are provided for all live audio content in synchronized media. | Not Applicable | Not Applicable |
| 1.2.5 Audio Description (Prerecorded) | (Level AA) | Audio description is provided for all prerecorded video content in synchronized media. | Supported by an alternative | Not Applicable |
| 1.2.6 Sign Language (Prerecorded) | (Level AAA) | Sign language interpretation is provided for all prerecorded audio content in synchronized media. | Not Applicable | Not Applicable |
| 1.2.7 Extended Audio Description (Prerecorded) | (Level AAA) | Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media. | Not Applicable | Not Applicable |
| 1.2.8 Media Alternative (Prerecorded) | (Level AAA) | An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media. | Supported by an alternative | Not Applicable |
| 1.2.9 Audio-only (Live) | (Level AAA) | An alternative for time-based media that presents equivalent information for live audio-only content is provided. | Not Applicable | Not Applicable |
| Guideline 1.3 Adaptable | Create content that can be presented in different ways (for example simpler layout) without losing information or structure. | |||
| 1.3.1 Info and Relationships | (Level A) | Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. | Supported | Partially Supported |
| 1.3.2 Meaningful Sequence | (Level A) | When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. | Supported | Supported |
| 1.3.3 Sensory Characteristics | (Level A) | Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound. | Supported | Supported |
| 1.3.4 Orientation | (Level AA) | Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential. | Supported | Supported |
| 1.3.5 Identify Input Purpose | (Level AA) | The purpose of each input field collecting information about the user can be programmatically determined when: 1. The input field serves a purpose identified in the Input Purposes for User Interface Components section; and 2. The content is implemented using technologies with support for identifying the expected meaning for form input data. |
Not Supported | Not Applicable |
| 1.3.6 Identify Purpose | (Level AAA) | In content implemented using markup languages, the purpose of User Interface Components, icons, and regions can be programmatically determined. | Not Supported | Not Applicable |
| Guideline 1.4 Distinguishable | Make it easier for users to see and hear content including separating foreground from background. | |||
| 1.4.1 Use of Color | (Level A) | Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. | Supported | Supported |
| 1.4.2 Audio Control | (Level A) | If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. | Not Applicable | Not Applicable |
| 1.4.3 Contrast (Minimum) | (Level AA) | The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. Logotypes: Text that is part of a logo or brand name has no contrast requirement. |
Supported by an alternative | Supported by an alternative |
| 1.4.4 Resize text | (Level AA) | Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality | Supported | Supported |
| 1.4.5 Images of Text | (Level AA) | If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: Customizable: The image of text can be visually customized to the user's requirements; Essential: A particular presentation of text is essential to the information being conveyed. |
Supported | Supported |
| 1.4.6 Contrast (Enhanced) | (Level AAA) | The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following: Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 4.5:1; Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. Logotypes: Text that is part of a logo or brand name has no contrast requirement. |
Supported by an alternative | Supported by an alternative |
| 1.4.7 Low or No Background Audio | (Level AAA) | For prerecorded audio-only content that (1) contains primarily speech in the foreground, (2) is not an audio CAPTCHA or audio logo, and (3) is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true: No Background: The audio does not contain background sounds. Turn Off: The background sounds can be turned off. 20 dB: The background sounds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sounds that last for only one or two seconds. |
Not Applicable | Not Applicable |
| 1.4.8 Visual Presentation | (Level AAA) | For the visual presentation of blocks of text, a mechanism is available to achieve the following: Foreground and background colors can be selected by the user. Width is no more than 80 characters or glyphs (40 if CJK). Text is not justified (aligned to both the left and the right margins). Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is atleast 1.5 times larger than the line spacing. Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window. |
Supported | Supported |
| 1.4.9 Images of Text (No Exception) | (Level AAA) | Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed. | Supported | Supported |
| 1.4.10 Reflow | (Level AA) | Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: Vertical scrolling content at a width equivalent to 320 CSS pixels; Horizontal scrolling content at a height equivalent to 256 CSS pixels. |
Supported | Partially Supported |
| 1.4.11 Non-text Contrast | (Level AA) | The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s): | Supported | Supported |
| User Interface Components | Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author; | Supported | Supported | |
| Graphical Objects | Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed. | Supported | Supported | |
| 1.4.12 Text Spacing | (Level AA) | In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: 1. Line height (line spacing) to at least 1.5 times the font size; 2. Spacing following paragraphs to at least 2 times the font size; 3. Letter spacing (tracking) to at least 0.12 times the font size; 4. Word spacing to at least 0.16 times the font size; |
Not Supported | Not Supported |
| 1.4.13 Content on Hover or Focus | (Level AA) | Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true. | Not Applicable | Not Applicable |
| Dismissable | A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content; | Not Applicable | Not Applicable | |
| Hoverable | If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing; | Not Applicable | Not Applicable | |
| Persistent | The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid. | Not Applicable | Not Applicable | |
| 2. Operable | User interface components and navigation must be operable. | |||
| Guideline 2.1 Keyboard Accessible | Make all functionality available from a keyboard. | |||
| 2.1.1 Keyboard | (Level A) | All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. | Supported | Partially Supported |
| 2.1.2 No Keyboard Trap | (Level A) | If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. | Supported | Supported |
| 2.1.3 Keyboard (No Exception) | (Level AAA) | All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. | Supported | Supported |
| 2.1.4 Character Key Shortcuts | (Level A) | If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true. | Not Applicable | Not Applicable |
| Turn off | A mechanism is available to turn the shortcut off; | Not Applicable | Not Applicable | |
| Remap | A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc); | Not Applicable | Not Applicable | |
| Active only on focus | The keyboard shortcut for a user interface component is only active when that component has focus. | Not Applicable | Not Applicable | |
| Guideline 2.2 Enough Time | Provide users enough time to read and use content. | |||
| 2.2.1 Timing Adjustable | (Level A) | For each time limit that is set by the content, at least one of the following is true. | Not Applicable | Not Applicable |
| Turn off | The user is allowed to turn off the time limit before encountering it; or | Not Applicable | Not Applicable | |
| Adjust | The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or | Not Applicable | Not Applicable | |
| Extend | The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or | Not Applicable | Not Applicable | |
| Real-time Exception | The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or | Not Applicable | Not Applicable | |
| Essential Exception | The time limit is essential and extending it would invalidate the activity; or | Not Applicable | Not Applicable | |
| 20 Hour Exception | The time limit is longer than 20 hours. | Not Applicable | Not Applicable | |
| 2.2.2 Pause, Stop, Hide | (Level A) | For moving, blinking, scrolling, or auto-updating information, all of the following are true. | Not Applicable | Not Applicable |
| Moving, blinking, scrolling | For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential. | Not Applicable | Not Applicable | |
| Auto-updating | For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential; and | Not Applicable | Not Applicable | |
| 2.2.3 No Timing | (Level AAA) | Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events. | Supported | Supported |
| 2.2.4 Interruptions | (Level AAA) | Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. | Supported | Supported |
| 2.2.5 Re-authenticating | (Level AAA) | When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. | Supported | Supported |
| 2.2.6 Timeouts | (Level AAA) | Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions. | Not Applicable | Not Applicable |
| Guideline 2.3 Seizures and Physical Reactions | Do not design content in a way that is known to cause seizures or physical reactions. | |||
| 2.3.1 Three Flashes or Below Threshold | (Level A) | Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. | Supported | Supported |
| 2.3.2 Three Flashes | (Level AAA) | Web pages do not contain anything that flashes more than three times in any one second period. | Supported | Supported |
| 2.3.3 Animation from Interactions | (Level AAA) | Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed. | Not Applicable | Not Applicable |
| Guideline 2.4 Navigable | Provide ways to help users navigate, find content, and determine where they are. | |||
| 2.4.1 Bypass Blocks | (Level A) | A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. | Not Applicable | Not Applicable |
| 2.4.2 Page Titled | (Level A) | Web pages have titles that describe topic or purpose. | Supported | Supported |
| 2.4.3 Focus Order | (Level A) | If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. | Supported | Supported |
| 2.4.4 Link Purpose (In Context) | (Level A) | The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. | Supported | Supported |
| 2.4.5 Multiple Ways | (Level AA) | More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. | Supported | Not Applicable |
| 2.4.6 Headings and Labels | (Level AA) | Headings and labels describe topic or purpose. | Supported | Supported |
| 2.4.7 Focus Visible | (Level AA) | Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. | Supported | Supported |
| 2.4.8 Location | (Level AAA) | Information about the user's location within a set of Web pages is available. | Supported | Supported |
| 2.4.9 Link Purpose (Link Only) | (Level AAA) | A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general. | Not Applicable | Not Applicable |
| 2.4.10 Section Headings | (Level AAA) | Section headings are used to organize the content. | Supported | Supported |
| Guideline 2.5 Input Modalities | Make it easier for users to operate functionality through various inputs beyond keyboard. | |||
| 2.5.1 Pointer Gestures | (Level A) | All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential. | Not Applicable | Not Applicable |
| 2.5.2 Pointer Cancellation | (Level A) | For functionality that can be operated using a single pointer, at least one of the following is true: | Supported | Supported |
| No Down-Event | The down-event of the pointer is not used to execute any part of the function; | Supported | Supported | |
| Abort or Undo | Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion; | Supported | Supported | |
| Up Reversal | The up-event reverses any outcome of the preceding down-event; | Not Applicable | Not Applicable | |
| Essential | Completing the function on the down-event is essential. | Not Applicable | Not Applicable | |
| 2.5.3 Label in Name | (Level A) | For user interface components with labels that include text or images of text, the name contains the text that is presented visually. | Supported | Not Supported |
| 2.5.4 Motion Actuation | (Level A) | Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when: Supported Interface: The motion is used to operate functionality through an accessibility supported interface; Essential: The motion is essential for the function and doing so would invalidate the activity. |
Not Applicable | Not Applicable |
| 2.5.5 Target Size | (Level AAA) | The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when: | Not Supported | Not Supported |
| Equivalent | The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels; | Not Supported | Not Supported | |
| Inline | The target is in a sentence or block of text; | Not Supported | Not Supported | |
| User Agent Control | The size of the target is determined by the user agent and is not modified by the author; | Not Supported | Not Supported | |
| Essential | A particular presentation of the target is essential to the information being conveyed. | Not Applicable | Not Supported | |
| 2.5.6 Concurrent Input Mechanisms | (Level AAA) | Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or required to respect user settings. | Supported | Supported |
| 3. Understandable | Information and the operation of user interface must be understandable. | |||
| Guideline 3.1 Readable | Make text content readable and understandable. | |||
| 3.1.1 Language of Page | (Level A) | The default human language of each Web page can be programmatically determined. | Supported | Supported |
| 3.1.2 Language of Parts | (Level AA) | The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. | Supported | Supported |
| 3.1.3 Unusual Words | (Level AAA) | A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. | Not Applicable | Not Applicable |
| 3.1.4 Abbreviations | (Level AAA) | A mechanism for identifying the expanded form or meaning of abbreviations is available. | Not Applicable | Not Applicable |
| 3.1.5 Reading Level | (Level AAA) | When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available. | Not Applicable | Not Applicable |
| 3.1.6 Pronunciation | (Level AAA) | A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation. | Not Applicable | Not Applicable |
| Guideline 3.2 Predictable | Make Web pages appear and operate in predictable ways. | |||
| 3.2.1 On Focus | (Level A) | When any user interface component receives focus, it does not initiate a change of context. | Supported | Supported |
| 3.2.2 On Input | (Level A) | Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. | Supported | Supported |
| 3.2.3 Consistent Navigation | (Level AA) | Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. | Supported | Supported |
| 3.2.4 Consistent Identification | (Level AA) | Components that have the same functionality within a set of Web pages are identified consistently. | Supported | Supported |
| 3.2.5 Change on Request | (Level AAA) | Changes of context are initiated only by user request or a mechanism is available to turn off such changes. | Supported | Supported |
| Guideline 3.3 Input Assistance | Help users avoid and correct mistakes. | |||
| 3.3.1 Error Identification | (Level A) | If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. | Partially Supported | Supported |
| 3.3.2 Labels or Instructions | (Level A) | Labels or instructions are provided when content requires user input. | Partially Supported | Supported |
| 3.3.3 Error Suggestion | (Level AA) | If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. | Partially Supported | Supported |
| 3.3.4 Error Prevention (Legal, Financial, Data) | (Level AA) | For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: | Not Applicable | Not Applicable |
| Reversible | Submissions are reversible. | Not Applicable | Not Applicable | |
| Checked | Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. | Not Applicable | Not Applicable | |
| Confirmed | A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. | Not Applicable | Not Applicable | |
| 3.3.5 Help | (Level AAA) | Context-sensitive help is available. | Partially Supported | Not Supported |
| 3.3.6 Error Prevention (All) | (Level AAA) | For Web pages that require the user to submit information, at least one of the following is true: | Not Applicable | Not Applicable |
| Reversible | Submissions are reversible. | Not Applicable | Not Applicable | |
| Checked | Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. | Not Applicable | Not Applicable | |
| Confirmed | A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. | Not Applicable | Not Applicable | |
| 4. Robust | Content must be robust enough that it can be interpreted by by a wide variety of user agents, including assistive technologies. | |||
| Guideline 4.1 Compatible | Maximize compatibility with current and future user agents, including assistive technologies. | |||
| 4.1.1 Parsing | (Level A) | In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. | Supported | Supported |
| 4.1.2 Name, Role, Value | (Level A) | For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. | Partially Supported | Partially Supported |
| 4.1.3 Status Messages | (Level AA) | In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus. | Not Supported | Not Supported |