Skip to main content

Oregon State Flag An official website of the State of Oregon »

Oregon.gov Homepage

Section 508 & WCAG 2.0 Compliance

Overview

The 4.x Starter Template follows the U.S. Section 508 of the Rehabilitation Act (which include the W3C Web Content Accessibility Guidelines 2.0).

The following table shows the Section 508 and WCAG 2.0 Compliance level of support for features and web parts included in the Starter Template. The report is based on results from tests performed on our Basic Usage demos.

WCAG 2.0 Standard

WCAG Specification

Perceivable

Web content is made available to the senses - sight, hearing, and/or touch Text Alternatives

Feature/Solution Rubric for Perceivable Principle
Success Criteria Recommendations Author-Dependent Current Planned Path to Success
1.1.1 Non-text Content
(Level A)
  • All images, form image buttons, and image map hot spots have appropriate, equivalent alternative text.
  • Images that do not convey content, are decorative, or contain content that is already conveyed in text are given null alt text (alt="") or implemented as CSS backgrounds. All linked images have descriptive alternative text.
  • Equivalent alternatives to complex images are provided in context or on a separate (linked and/or referenced via longdesc) page.
  • Form buttons have a descriptive value.
  • Form inputs have associated text labels.
  • Embedded multimedia is identified via accessible text.
  • Frames are appropriately titled.
 Yes Yes
  • Starter Template passes (alt, aria-expanded, aria-hidden, aria-haspopup)
  • Task Box web part passes if author completes necessary fields (alt)
  • Form Builder web part passes (label, button descriptions, aria-describedby, aria-live)
  • Tota11y plugin aids author to catch errors.
  • Note: Images sourced from Socrata via Data Tables web part contain null alt text, however will not pass.

Time-based Media

Feature/Solution Rubric for Time-Based Media
Success Criteria Recommendations Author-Dependent Current Planned Path to Success
1.2.1 Prerecorded Audio-only and Video-only
(Level A)
  • A descriptive text transcript (including all relevant visual and auditory clues and indicators) is provided for non-live, web-based audio (audio podcasts, MP3 files, etc.).
  • A text or audio description is provided for non-live, web-based video-only (e.g., video that has no audio track).
 Yes Yes
  • Starter Template passes (no video/audio is employed)
1.2.2 Captions (Prerecorded)
(Level A)
  • Synchronized captions are provided for non-live, web-based video (YouTube/Vimeo videos, etc.)
 Yes Yes
  • Starter Template passes (no video/audio is employed)
  • Future release will include moreaccessible video/audio playerwith caption support
1.2.3 Audio Description or Media Alternative (Prerecorded)
(Level A)
  • A descriptive text transcript OR audio description audio track is provided for non-live, web-based video
 Yes Yes
  • Starter Template passes (no video/audio is employed)
1.2.4 Captions (Live)
(Level AA)
  • Synchronized captions are provided for all live multimedia that contains audio (audio-only broadcasts, web casts, video conferences, Flash animations, etc.)
 Yes Yes
  • Starter Template passes (no video/audio is employed)
1.2.5 Audio Description (Prerecorded)
(Level AA)
  • Audio descriptions are provided for all video content
    NOTE: Only required if the video conveys content visually that is not available in the default audio track.
 Yes Yes
  • Starter Template passes (no video/audio is employed)
1.2.6 Sign Language (Prerecorded)
(Level AAA)
  • A sign language video is provided for all media content that contains audio.
 Yes Yes
  • Starter Template passes (no video/audio is employed)
1.2.7 Extended Audio Description (Prerecorded)
(Level AAA)
  • When an audio description track cannot be added to video due to audio timing (e.g., no pauses in the audio), an alternative version of the video with pauses that allow audio descriptions is provided.
 Yes Yes
  • Starter Template passes (no video/audio is employed)
1.2.8 Media Alternative (Prerecorded)
(Level AAA)
  • A descriptive text transcript is provided for all pre-recorded media that has a video track.
 Yes Yes
  • Starter Template passes (no video/audio is employed)
1.2.9 Audio-only (Live)
(Level AAA)
  • A descriptive text transcript (e.g., the script of the live audio) is provided for all live content that has audio.
 Yes Yes
  • Starter Template passes (no video/audio is employed)

Adaptable

Feature/Solution Rubric for Adaptable
Success Criteria Recommendations Author-Dependent Current Planned Path to Success
1.3.1 Info and Relationships
(Level A)
  • Semantic markup is used to designate headings (<h1>), lists (<ul>, <ol>, and <dl>), emphasized or special text (<strong>, <code>, <acronym>, <blockquote>, for example), etc. Semantic markup is used appropriately.
  • Tables are used for tabular data. Where necessary, data cells are associated with their headers. Data table captions and summaries are used where appropriate.
  • Text labels are associated with form input elements. Related form elements are grouped with fieldset/legend.
 Yes Yes
  • Starter Template passes
  • Data Tables web part passes
  • Tota11y plugin aids author.
1.3.2 Meaningful Sequence
(Level A)
  • The reading and navigation order (determined by code order) is logical and intuitive.
 Yes Yes
  • Starter Template passes
  • Left-hand navigation page layouts pass
  • Off-canvas navigation passes
1.3.3 Sensory Characteristics
(Level A)
  • Instructions do not rely upon shape, size, or visual location (e.g., "Click the square icon to continue" or "Instructions are in the right-hand column").
  • Instructions do not rely upon sound (e.g., "A beeping sound indicates you may continue.").
 Yes Yes
  • Starter Template passes
  • Site-wide & State-wide alerts pass

Operable Interface forms, controls, and navigation are operable Keyboard Accessible

Feature/Solution Rubric for Forms, Controls, & Navigation
Success Criteria Recommendations Author-Dependent Current Planned Path to Success
2.1.1 Keyboard
(Level A)
  • All page functionality is available using the keyboard, unless the functionality cannot be accomplished in any known way using a keyboard (e.g., free hand drawing).
  • Page-specified shortcut keys and accesskeys (accesskey should typically be avoided) do not conflict with existing browser and screen reader shortcuts.
 Yes Yes
  • Starter Template passes
  • No shortcut keys employed
2.1.3 Keyboard (No Exception)
(Level AAA)
  • All page functionality is available using the keyboard.
 Yes
2.1.2 No Keyboard Trap
(Level A)
  • Keyboard focus is never locked or trapped at one particular page element. The user can navigate to and from all navigable page elements using only a keyboard.
 Yes
2.1.3 Keyboard (No Exception)
(Level AAA)
  • All page functionality is available using the keyboard.
 Yes

Enough Time

Feature/Solution Rubric for Timing
Success Criteria Recommendations Author-Dependent Current Planned Path to Success
2.2.1 Timing Adjustable
(Level A)
  • If a page or application has a time limit, the user is given options to turn off, adjust, or extend that time limit. This is not a requirement for real-time events (e.g., an auction), where the time limit is absolutely required, or if the time limit is longer than 20 hours.
 Yes
2.2.2 Pause, Stop, Hide
(Level A)
  • Automatically moving, blinking, or scrolling content that lasts longer than 5 seconds can be paused, stopped, or hidden by the user. Moving, blinking, or scrolling can be used to draw attention to or highlight content as long as it lasts less than 5 seconds.
  • Automatically updating content (e.g., automatically redirecting or refreshing a page, a news ticker, AJAX updated field, a notification alert, etc.) can be paused, stopped, or hidden by the user or the user can manually control the timing of the updates.
 Yes
2.2.3 No Timing
(Level AAA)
  • The content and functionality has no time limits or constraints.
 Yes
2.2.4 Interruptions
(Level AAA)
  • Interruptions (alerts, page updates, etc.) can be postponed or suppressed by the user.
 Yes
2.2.5 Re-authenticating
(Level AAA)
  • If an authentication session expires, the user can re-authenticate and continue the activity without losing any data from the current page.
 Yes

Seizures

Feature/Solution Rubric for Seizure Prevention
Success Criteria Recommendations Author-Dependent Current Planned Path to Success
2.3.1 Three Flashes or Below Threshold
(Level A)
  • No page content flashes more than 3 times per second unless that flashing content is sufficiently small and the flashes are of low contrast and do not contain too much red.
 Yes Yes
  • Starter Template passes
  • Alert icon animation flashes at a rate of 1.2 fps, equaling .83hz
  • Panel fade animation flashes at a rate of 1.2 fps, equaling .83hz
2.3.2 Three Flashes
(Level AAA)
  • No page content flashes more than 3 times per second.
 Yes Yes
  • Starter Template passes
  • No pages flash more than 3 times per second.

Navigable

Understandable Content and interface are understandable Readable

Feature/Solution Rubric for Readability
Success Criteria Recommendations Author-Dependent Current Planned Path to Success
3.1.1 Language of Page
(Level A)
  • The language of the page is identified using the HTML lang attribute (<html lang="en">, for example).
 Yes
3.1.2 Language of Parts
(Level AA)
  • The language of page content that is in a different language is identified using the lang attribute (e.g., <blockquote lang="es">).
 Yes Yes
3.1.3 Unusual Words
(Level AAA)
  • Words that may be ambiguous, unknown, or used in a very specific way are defined through adjacent text, a definition list, a glossary, or other suitable method.
 Yes Yes
3.1.4 Abbreviations
(Level AAA)
  • Expansions for abbreviations are provided by expanding or explaining the definition the first time it is used, using the <abbr> element, or linking to a definition or glossary. NOTE: WCAG 2.0 gives no exception for regularly understood abbreviations (e.g., "HTML" on a web design site must always be expanded).
 Yes Yes
3.1.5 Reading Level
(Level AAA)
  • A more understandable alternative is provided for content that is more advanced than can be reasonably read by a person with roughly 9 years of primary education.
 Yes Yes
3.1.6 Pronunciation
(Level AAA)
  • If the pronunciation of a word is vital to understanding that word, its pronunciation is provided immediately following the word or via a link or glossary.
 Yes Yes

Predictable

Feature/Solution Rubric for Precdictable Principle
Success Criteria Recommendations Author-Dependent Current Planned Path to Success
3.2.1 On Focus
(Level A)
  • When a page element receives focus, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user.
 Yes Yes
3.2.2 On Input
(Level A)
  • When a user inputs information or interacts with a control, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user unless the user is informed of the change ahead of time.
 Yes Yes
3.2.3 Consistent Navigation
(Level AA)
  • Navigation links that are repeated on web pages do not change order when navigating through the site.
 Yes Yes
3.2.4 Consistent Identification
(Level AA)
  • Elements that have the same functionality across multiple web pages are consistently identified. For example, a search box at the top of the site should always be labeled the same way.
 Yes Yes
3.2.5 Change on Request
(Level AAA)
  • Substantial changes to the page, the spawning of pop-up windows, uncontrolled changes of keyboard focus, or any other change that could confuse or disorient the user must be initiated by the user. Alternatively, the user is provided an option to disable such changes.
 Yes Yes

Input Assistance

Feature/Solution Rubric for Input Assistance
Success Criteria Recommendations Author-Dependent Current Planned Path to Success
3.3.1 Error Identification
(Level A)
  • Required form elements or form elements that require a specific format, value, or length provide this information within the element's label.
  • If utilized, form validation errors are presented in an efficient, intuitive, and accessible manner. The error is clearly identified, quick access to the problematic element is provided, and user is allowed to easily fix the error and resubmit the form.
 Yes
3.3.2 Labels or Instructions
(Level A)
  • Sufficient labels, cues, and instructions for required interactive elements are provided via instructions, examples, properly positioned form labels, and/or fieldsets/legends.
 Yes
3.3.3 Error Suggestion
(Level AA)
  • If an input error is detected (via client-side or server-side validation), provide suggestions for fixing the input in a timely and accessible manner.
 Yes
3.3.4 Error Prevention (Legal, Financial, Data)
(Level AA)
  • If the user can change or delete legal, financial, or test data, the changes/deletions can be reversed, verified, or confirmed.
 Yes
3.3.5 Help
(Level AAA)
  • Provide instructions and cues in context to help in form completion and submission.
 Yes
3.3.6 Error Prevention (All)
(Level AAA)
  • If the user can submit information, the submission is reversible, verified, or confirmed.
 Yes

Robust Content can be used reliably by a wide variety of user agents, including assistive technologies Compatible

Feature/Solution Rubric for Robust Principle
Success Criteria Recommendations Author-Dependent Current Planned Path to Success
4.1.1 Parsing
(Level A)		 Yes Yes
4.1.2 Name, Role, Value
(Level A)
  • Markup is used in a way that facilitates accessibility. This includes following theHTML/XHTML specifications and using forms, form labels, frame titles, etc. appropriately.
 Yes Yes