Accessibility - WCAG (Web Content Accessibility Guidelines) 2.0, Level AA

It is core to bswift’s values to ensure that all the people that we serve have equal access to our services and to our information. Although bswift is not a covered entity under ACA 1557, we have taken many steps to ensure the most universally accessible web and mobile experience.  We are continually improving our websites and mobile applications to conform to accessibility standards.  We have adopted Web Content Accessibility Guidelines (WCAG) version 2.0 AA as our company standard.

We do not ensure compliance on behalf of our clients who wish to perform extensive customizations to their site.

ADA (American Disabilities Act) has no actual rules for accessibility, but they use WCAG 2.0 as a guide on what is accessible. Section 508 was updated to reference WCAG 2.0 Level A and Level AA guidelines.

The following is a list of common and easily corrected accessibility issues that we should keep in mind when designing or coding.
If you have questions, please contact Joy Dodge (jdodge@bswift.com)

Ensure text and images of text provide sufficient contrast

Adequate contrast is necessary for all users, especially users with low vision. Refer to our default bswift Colors.

Provide alternative text for images

All images within a page must be given an alternate text equivalent. Text equivalents for non-text elements communicate the meaning of images to users who cannot perceive the image such as users of screen readers. Proper equivalents provide text which contributes the same level of understanding to the content of the page as the image itself. In instances where the image does not contribute to the understanding of the content and is purely decorative, it needs to be marked in a way to indicate its purely decorative purpose. - AMP

View Examples

Do not skip heading levels

Headings provide document structure and facilitate keyboard naviation by users of assistive technology. When levels are skipped, users of assistive technology may not understand the relationship of content.

Ensure that all headings contain informative content

Assistive technology users often navigate by heading elements. An empty heading presents no information and may introduce confusion.

Ensure that all links contain informative content

If a link contains no text, its function or purpose will not be presented to assitive technology users.

View Examples

Ensure all active elements receive keyboard focus

An element that can be activated via mouse must also be actionable via keyboard. Do not emulate links by attaching JavaSript event handlers to non-semantic elements.

View Examples

Provide valid label for form controls

Form labels provide visible descriptions and larger clickable targets for form controls. Without a properly associated text label, the function or purpose may not be presented to assitive technology users.

View Examples

Media (Audio and Video)

  • Provide synchronized captions and transcripts of videos
  • Ensure audio is not played automatically on load
  • Ensure multimedia playback can be controlled