Skip to content

Accessibility

bb-at-raft edited this page May 19, 2020 · 5 revisions

According to Usability.gov, "Accessibility relates to how a disabled individual uses something. Section 508 requires that all government websites are accessible to disabled users. Section 504 expands these accessibility requirements to any group receiving federal funding."

We understand that users will likely have differing levels of ability to utilize our software. We based our design on CFPB accessibility guidelines and best practices. We need to consider the following audiences:

  • Print disabled: blind, deaf-blind, low vision, obstructed vision, dyslexic, cognitively disabled and illiterate individuals.

  • Physically disabled: users that have amputations, paralysis, repetitive stress, cerebral palsy, muscular dystrophy, Parkinson's or other problems limiting mobility.

  • Hearing impaired

  • Baby boomers: An increasing number of aging baby boomers are beginning to experience problems with their sight, vision or dexterity.

In order to make our software as accessible as possible, we closely integrate with The Web Content Accessibility Guidelines (WCAG) and, specifically, WCAG 2.0

We make assure our software is accessible by testing it for POUR, the four main principles of the WCAG.

Perceivable

  • We provide text alternatives for any non-text content.
  • Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
  • We make content distinguishable, easier for users to see and hear content including appropriate color palettes.

Operable

  • We make all functionality available from a keyboard.
  • We design content in a way that in not known to cause seizures or physical reactions.
  • We make sure that user can navigate easily to all parts of the application.
  • We consider multiple input modalities so all users can access the functionality.

Understandable

  • We design our content to be plain language and understandable.
  • We create our app to function in predictable ways.
  • We give users appropriate feedback from the software so they can easily complete their tasks.

Robust.

  • We consider the user of other assistive devices when designing our applications.
Clone this wiki locally