Category: UI and UX

For designers who work in the healthcare industry, creating UX design to accommodate HIPAA laws has become a gold standard. Protecting patient privacy is a given and designing software to transmit information securely is no longer a rare skill, rather just a specialty. However, as of January 18, 2018, there is now a new challenge to overcome: compliance with 508 standards for healthcare organizations. These standards now require federal websites and software to be accessible by people with disabilities.

508 Standard Compliance Explained for Healthcare

The Rehabilitation Act of 1973 was the first law that required that all federal agencies provide individuals with disabilities with reasonable accommodation. These regulations were updated in 1998 to include section 508, the Electronic and Information Technology Accessibility Standards, which extended the existing regulations to digital and electronic technology. However, since it has been nearly two decades since its last update, the Access Board implemented a new “refresh” to the 508 standards, which went into effect on January 18, 2018. These new standards for UX design on healthcare websites and apps bring the language up to date for websites and software applications.

To be compliant with 508 Standards, your website and application must be accessible by people:

• Without vision
• With limited vision
• Without perception of color
• Without hearing
• With limited hearing
• Without speech
• With limited manipulation
• With limited reach and strength
• With limited language, cognitive, and learning abilities

Furthermore, if your website or application requires hardware, this hardware must meet compliance standards as well. Hardware devices with user interfaces must also be compliant and/or allow for a user to attach and utilize their own assistive devices (e.g. a screen reader).

How 508 Applies to Healthcare

With the new update, all government healthcare organizations and the vendors that they use are now required to be in compliance with 508 standards. This not only impacts federal organizations but any software, device, or website which is used by federal healthcare services including Medicaid, Medicare, insurance exchanges, veterans, military healthcare, and more.

All organizations and their vendors will need to update their software and websites to be in compliance or face government fines.

UX design for 508 Compliance

The challenge that organizations now face is that very few UX designers are familiar with UX design for 508 compliance. It’s a highly skilled type of designing and requires comprehensive understanding how different design aspects impact people with varying levels of disability. For example, there are strict guidelines on how websites can use strobing images, as more than three flashes per second is a known trigger for seizures. A designer must also understand how adaptive devices, such as screen readers, will read the text on their screen and the design must accommodate for this.

In order to facilitate the movement of organizations to compliance, the government has released a variety of toolkits for references. At the top of this, it is stressed that designers must first understand the core foundations for web accessibility: perceivable, operable, understandable, and robust. Within these foundations, they are then to adhere to the following guidelines:

508 Compliant Web Design Standards

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.

• Time-based media: Provide alternatives for time-based media.
• Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
• Distinguishable: Make it easier for users to see and hear content including separating foreground from background.
• Keyboard Accessible: Make all functionality available from a keyboard.
• Enough Time: Provide users enough time to read and use content.
• Seizures: Do not design content in a way that is known to cause seizures.
• Navigable: Provide ways to help users navigate, find content, and determine where they are.
• Readable: Make text content readable and understandable.
• Predictable: Make Web pages appear and operate in predictable ways.
• Input Assistance: Help users avoid and correct mistakes.
• Compatible: Maximize compatibility with current and future user agents, including assistive technologies.

While the toolkits provide great information on how to get started, in order to ensure compliance it is best to work with an expert UX designer in healthcare with experience with 508 standards. For more information and a free estimation on bringing your site or application up to 508 standards, schedule a free consultation. Give us a call at (800) 863-6914 or email us at info@accelone.com .

How Developers & UX Designers build in harmony and deliver on the promise of products people love.

Bridging the gap between the “creatives” and the “techies” is one of the greatest challenges to overcome when effectively defining, designing, developing, and delivering products people love to use. The respective members of cross-functional development teams are not only trained in completely different processes, but they also have two extremely different mental models and methods in which their goals are established and rewarded.

Designers are both intrinsically and professionally trained to focus on the human user of the technology. Developers, on the other hand, are focused on the features and functions of the technology itself. These two hemispheres of the same system can create friction within the team, cause miscommunication, and slow down product development.

Creating a great product, of course, it is not as simple as only getting the two sides to work together. The other players in this sandbox are the business executives, marketing and sales professionals, growth hackers, and product owners. These players are often the most ignored and yet are mission-critical to creating marketplace awareness of the product and successful adoption. Creating balance and harmony between these players is essential for driving and delivering the ultimate product experience.

Better together

Fundamentally, all members of the product or application’s cross-functional team are dedicated to delivering the same result: product experiences that people love. However, it can be challenging to get all team members communicating effectively to make cohesive decisions about product development.

To help facilitate this process, I created the “Better Together” mandate. This mandate serves as a basis for all input and decision drivers that must be balanced and understood throughout the end-to-end development lifecycle (THINK/MAKE cycle). This mandate requires that all team members be involved in the entire THINK/MAKE cycle and provides a framework for making decisions.

This simple process, using the “Better Together” mandate principles, starts with an IDEA (that is presented from any source – usually the business leaders – but truly from any player). The cross-functional team then immediately engages to validate if it is worthy and what is involved from a BXT (business, eXperience, technology) 360-degree view. This requires THINKing it through together. Designers often lead this portion of the cycle due to design thinking and HCD (human-centered design) methods being the key input components. However, the technologist should be heavily engaged and contribute to the process so that everyone stays on the same page and agrees with the proposed solutions. There are no hand offs if everyone goes through the THINK processes together.

Some teams struggle to keep a technologist engaged during the THINK portion of the cycle. One way to help with buy in and participation from the developers, is by managing this cycle as SPRINT 0. Most developers know they are to do a SPRINT 0 before planning the Sprint 1 through X rhythm, to clearly define and validate what is to be built. And most developers are at a loss for how to effectively process this Sprint 0 needed. The light seems to come on when they are stepped through the design thinking approach and they usually fully embrace and participate in the process.

Including ALL of the cross-functional creation team members (DESIGN and BUILD) at every step can increase project costs and is therefore an investment choice. However, my experience proves time and again that to have the team engaged in every part of this cycle has paid off huge dividends in realizing the goal of their work together.

The following article will be served up in three parts: Part 1: THINK, Part 2: MAKE, Part 3: LOVE. My goal is for all members of the design, development, and business teams to understand the fundamentals of how the THINK/MAKE cycle works and to ensure that everyone understands their role within the cycle. This understanding is, without a doubt, the key to effectively creating successful experiences that people love. This harmonic approach of playing “Better Together” can remove the built-in blockers of most real-world processes.