Galvanize Product Designer Accessibility Guidelines
Preface
These guidelines were developed for product designers at Galvanize. It was meant to provide basic guidance and introduce them to accessibility/WCAG standards.
How to use this guide
All of the items listed under “Do” are techniques that will help you pass the standards. Items listed under “Don’t” are automatic fails if done. Items listed under “Avoid” will not trigger a fail but are best avoided because they go against best practices.
Colour (FAQ)
Some people have reduced or lack of sensitivity to certain colours (“colour blindness”). Other people have increased sensitivity to bright colours.
Do:
- Use a combination of visual cues to convey information such as colours/icons/text/labels/errors.
- Underline links that are embedded within a sentence/block of text because some users may not be able to discern a difference in text colour.
- Use brightness shifts as a method to convey different states of a ui element such as hover, focus, active, etc. (Best practice)
Don’t:
- Use colour as the only way to convey information (e.g. status, feedback).
- Use colour as the only way to identify required fields or errors.
Avoid:
- Using pure black text on pure white backgrounds.
This guideline fulfills the following WCAG guidelines:
Contrast for text (FAQ)
People don’t always screen readers when they have trouble seeing the screen. This is true especially f it’s situational (e.g. low contrast monitors, glare on their screen from the environment, etc.).
Do
- Ensure sufficient colour contrast between design elements, so that users with low acuity can see and use our apps.
- Meet all WCAG 2.0 minimum contrast ratios for text and background colours.
– Fonts that are 18 points or larger: 3:1 contrast ratio
– Fonts that are 14 points bold or larger: 3:1 contrast ratio
– All other text and images of text: 4.5:1 contrast ratio
– Use placeholder text to only provide examples of expected value types. - Icons or other critical elements should comply with contrast standards.
Don’t
- Allow any of the colour contrast ratios to fail.
- Use placeholder text to provide instructions.
- Use placeholder text as a replacement for form labels.
Avoid
- Using thin text weights for regular-sized text.
The contrast ratio standards were created for normal weighted fonts, there are no standards set for fancy or thin fonts. We have not found a tool that will test against fancy/thin fonts, the current tools only run comparisons against the regular or bold font weights. So even if fancy/thin fonts technically pass our contrast checkers it does not mean that they are actually usable. It is best to avoid thin/fancy fonts for regular-sized text and very thin large fonts. - Avoid using pure black text on a pure white background.
Dyslexic users are sensitive to the brightness of the high contrast colours. Pure black#000text on a pure white#fffbackground can cause words to swirl or blur together for many dyslexic users.
Exceptions
- Incidental text as defined by WCAG does not have nor have to meet contrast requirements (W3C).
- — Disabled user interface component text (e.g. disabled buttons).
- — Purely decorative text that serves only an aesthetic purpose, providing no information and having no functionality.
- Decorative illustrations. While decorative elements, such as logos and illustrations, don’t have to meet contrast ratios they should be distinguishable if they possess important functionality.
- Non-essential UI elements.
- Branding.
For more information on contrast minimums see Understanding SC 1.4.3.
This guideline fulfills the following WCAG guidelines:
Non-text contrast (FAQ)
Do
- Meet all WCAG 2.1 non-text content contrast ratios for UI components and graphical objects.
- All components that are available for user interaction must still pass a 3:1 contrast ratio.
- — UI components that are disabled do not need to pass contrast.
- — Note that any text within the UI component still needs to pass at a 4.5:1 contrast ratio.
- Charts and icons must pass a 3:1 contrast ratio.
- — If it’s a pie chart, the user must be able to see where one slice begins and another ends. The exception is if the pie chart has both visible labels and values that show the same equivalent information as the pie chart slices.
Don’t
- Have any icons that don’t have a contrast ratio of 3:1.
- Have any enabled UI components fail a contrast ratio of 3:1
- — Note: In the context of WCAG, inactive means disabled
Avoid
- Putting text in graphics.
- Gradients in icons. If gradients are used, you need to make sure the lightest part of the gradient still passes a 3:1 contrast ratio.
- Removing all borders around interactive items such as buttons and input fields. People with cognitive disabilities have trouble recognizing controls without a border. For example, you should put borders around buttons, put borders around form inputs, etc.
Exceptions
- The graphic is for aesthetic purposes that does not require the user to see or understand it to understand the content or use the functionality.
- The graphic is part of a logo or brand name (which is considered “essential” to its presentation).
- Photos of people are scenery (but need
alttags). - Colour gradients that represent a measurement (like heat maps).
This guideline fulfills the following WCAG guidelines:
Charts
Colours should be chosen with colour blind users in mind. Contrast should be sufficient for users who have low visual acuity. Options should be included for users who are blind and require the help of screen readers.
Do (Article)
- Have options to turn on patterns, textures, or grayscale.
- Use a range of clearly contrasting colours and hues.
- Have sufficient contrast between elements (e.g. bars, axes and labels).
- Provide a title or short description to identify the chart.
- Provide a long description which is the textual representation of the essential information conveyed by the chart. (W3C tutorial)
- Use a combination of colours, shapes and labels to convey information.
- Provide a “View Data Table” option.
- Make sure the chart has a visible focus and consistent navigation.
- Line charts include the use of different line styles such as solid, small dashes, large dashes and dots.
- Make text and objects as thick or big as possible.
Don’t
- User colour as the only way to convey information.
- Leave out the “View Data Table” option.
Avoid
- Placing bad colour combos closely together: (Article)
– Green & Red
– Green & Black
– Green & Brown
– Green & Blue
– Blue & Purple
– Blue & Grey
– Green & Grey
– Light Green & Yellow - Situations where important information is conveyed only in the form of colour.
Examples
This guideline fulfills the following WCAG guidelines:
Motion (FAQ)
Animations are an extremely powerful communication tool. It helps users understand the transition from one screen to another or when panels open or close. It can also make our users feel sick or triggered so be careful how you use it.
Do
- Be purposeful with your animations and use it as a tool for communication:
- — To show continuity and relationships between objects via entry and exit animations.
- — Reduce cognitive load and confusion by effectively communicating user feedback.
- — Guide the user focus to show hierarchy and relationships between screens and elements on the screen.
- — Convey visual hierarchy by animating the order of page elements as they load.
- — Communicate transitions between states.
- Reduce contrast for any flashing content.
- Avoid fully saturated reds for any flashing content.
Don’t
- Have anything that flashes more than 3 times within 1 second.
- Autoplay “big” animations (where a large area of the screen moves).
Avoid
- Large areas of motion that include:
- — Parallax background animations: when the background moves slower than the foreground.
- — Scroll-jacking: This is when the background animates at a speed unrelated to your scrolling efforts.
- Animations that move in a different direction than the user scroll.
Awesome article on vestibular disorder (motion-triggered illness)
Designing Safer Web Animation For Motion Sensitivity
Animation that involves only non-moving properties, like opacity, colour, and blurs, are unlikely to be problematic.
This guideline fulfills the following WCAG guidelines:
Consistent (FAQ)
Being consistent allows our users to learn how things work on one feature and apply that knowledge to other features.
Do
- Keep navigation items in the same relative order.
- Use of sub-nav sections in larger navigation menus.
- Place components that have the same functionality in the same places:
— Company logo
— Top navigation
— Search
— Page title
— Skip navigation controls
— Skip to navigation links.
— etc. - Label things consistently:
— Buttons
— Form fields
— Icons
— etc. - Use icons consistently
- Use consistent alt text for icons
Don’t
- Change the relative order of navigation links in a component that is used across different pages.
- Label buttons with the same functionality differently.
This guideline fulfills the following WCAG guidelines:
Predictable (FAQ)
Surprises are great but not when they change the user’s context and confuse them.
Do
- Change context only when it is clear that such a change will happen in response to the user’s action (use “activate” instead of “focus”).
- Give users advanced warning before opening a tab/window
- Open new windows only when necessary.
Don’t
- Change context on focus
- Change context on input
- Forget to tell the user what will happen before you change the context of a page if the change is triggered by a form control.
- Automatically open a new window when the user changes the selection of a:
— Radio button
— Checkbox
— Item in a<select>list - Open a new window as soon as a page loads (no automatic popups either).
- Auto-focus anything besides the current element or view.
This guideline fulfills the following WCAG guidelines:
Forms (FAQ)
Clear labels, error messages and tips benefits everyone.
Be clear
- Distinguish between optional and required fields.
- Provide clear, concise and simple labels for each field (placeholders aren’t enough).
- Show examples of correct data formats (e.g. dates, phone numbers, etc.).
— If there are many fields with the same data format requirements then provide instructions at the beginning of the form. - Position labels so that it’s obvious the relationship between label + field:
— Before input fields (text, textarea, select, etc.) to the left or above.
— After radios and checkboxes (to the right). - Group related fields, radio buttons and checkboxes together using (
<fieldset>and<legend>). - Provide success messages for user logins, quizzes, new objects created, edits saved, contact requests sent, etc.
Be helpful
- Highlight missing required fields.
- Tell the user right away if something is missing or entered incorrectly (on blur).
- Write meaningful descriptive error messages.
- Provide suggestions on how to fix errors:
— Formatting (MM/DD/YY)
— Expected data type (only numbers are accepted
— Spelling (did you mean…?)
— Search results (0 results, try…) - If the user submits the form and there are errors:
— Keep previously entered data unless it’s a security-related field (e.g. password).
— Insert an error message including the number of errors.
— Move focus to the error message.
— Insert a linked list of fields with errors so that users can navigate easily right to the error field.
Be sure
Anytime a user is engaging in a legal, financial or data action you must allow a way for them to reverse that action, check that action before completing and then provide a confirmation of the completed action.
Get Jayde Ly’s stories in your inbox
Join Medium for free to get updates from this writer.
When submitting legal documents, performing financial transactions, making purchases or making changes to data:
- Allow users to cancel the action.
- Allow users to review and make changes before submitting (e.g. filing tax returns or test answers).
- Allow users to confirm that they’ve reviewed everything (e.g. Terms of Service and using a checkbox).
- Allow users to recover deleted data (e.g. archive or soft deletes).
- Tell users what will happen if they delete something (e.g. deleting this will…).
- Ask users to confirm before performing an irreversible action (e.g. are you sure?).
Don’t
- Only indicate that a field has an error by putting an asterisk on its label or turning the label red.
- Forget to provide a clear descriptive text label for a set of fields that make up one single item (e.g. phone numbers, credit card expiration dates, etc.)
This guideline fulfills the following WCAG guidelines:
Cognition
Avoid using justified text
Justified text is difficult to read for dyslexic users. This is because it creates large uneven spaces between letters and words. When these spaces line up above one another. They can cause dyslexic readers to repeatedly lose their place when reading.
Avoid using all capital letters
Users with cognitive disabilities, such as dyslexia, have problems with all caps regardless of text size. Also, some screen readers read capitalized text letter-by-letter. This occasionally happens when CSS is used for capitalization. Text in all capital letters is more difficult to read for most people, with and without disabilities.
If you must use all caps then limit it to 1 or 2 words with adequate letter spacing for better readability and not in close proximity to other blocks of all caps text. Also, you will need to consider how the goal of using all caps will be achieved for languages that do not have the concept of all caps such as Chinese and Japanese.
Avoid using pure black text on a pure white background.
Dyslexic users are sensitive to the brightness of the high contrast colours. Pure black #000 text on a pure white #fff background can cause words to swirl or blur together for many dyslexic users.
Wayfinding
Help users understand where they are, where they want to go and how to get there.
Do
- Give all pages a descriptive
<title>Page - App - HighBond</title> - Give all pages a
<h1>Page Name</h1>that’ll be used as part of the<title>. - Break up long pages with clear and descriptive headings (h1, h2, h3, etc).
- Have a “Skip to Content” link to take users to the main content area.
- Use expanding/collapsing blocks for menus as appropriate.
- Create links using the object or destination’s name instead of “Click here…”.
- “Learn more.” links are wrapped in a
<p>tag and inserted it at the end of the paragraph. - Use different types of menus (e.g. purple app bar, main menu, side menu, etc.) to let users navigate our pages.
- Include the ability to search documents, modules, pages, etc.
- Highlight buttons, links or other controls when a user hovers over it.
- Make it obvious which element has the keyboard focus.
Don’t
- Give a page
<title>that does not identify its content. - Use ambiguous links at the beginning of a sentence (e.g.
Click hereto go to). - Identify content or objects only by their shape, size, location or orientation.
- Remove the default browser focus outline without replacing it with a custom one that is also highly visible (don’t make it too subtle).
Avoid
- Instructions that rely on sound
This guideline fulfills the following WCAG guidelines:
Timing (FAQ)
Give users enough time to do what they need to do and let them control what’s playing on the screen.
Do
Give users enough time to respond:
- Tell users how much time they have to complete a task.
- Warn them when that time limit is almost reached.
- Allow the user to extend or disable the time limit unless it’s a real-time-based event or critical to the business that users are not able to get an extension.
- Give users at least 20 seconds to respond.
- Allow users to “hit any key” as a response.
Allow users to control any content that moves
- Provide controls for pause, stop, start, next and previous or allow users to hide the content.
- Minimize the usage of blinking things and keep them under 5 seconds.
Allow users to control auto-updating content
- Provide the ability to pause, stop, or change the frequency of updates (e.g. scoreboard).
Don’t
- Log users out without warning them and provide 20 seconds for them to respond.
- Automatically page refreshes or redirects that weren’t triggered by the user performing an action.
- Fail to provide controls to pause or stop moving content that lasts longer than 5 seconds.
Avoid
- Adding time limits where possible.
- Content that moves without users triggering the action.
- Auto-play content that lasts longer than 5 seconds.
This guideline fulfills the following WCAG guidelines:
Audio and Video (FAQ)
Everyone should be able to consume the content in an audio or video recording.
Do
Provide transcripts for audio and video recordings.
- Identify who is speaking.
- Include a word-for-word record of everything the speakers say.
- Note any other significant sounds such as applause, laughter, questions from the audience, etc.
- Place the transcript or link to the transcript close to the audio or video.
- Provide only a short description for animations or illustrations that support text tutorials and point users to the text tutorial for more information.
Also, do
- Provide a full detailed text description of video-only content.
- Provide synchronized captions for all video that has audio unless that video is used as a visual aid for text already on the page.
- Tell the user if no sound is used in a video clip.
Don’t
- Provide less information in long descriptions or transcripts than what is contained in the audio, video or image.
- Auto-play sounds that last longer than 3 seconds.
Exceptions
- HighBond will not provide a second, user-selectable, audio track that includes audio descriptions for videos.
This guideline fulfills the following WCAG guidelines:
Public facing pages
All previous accessibility guidelines apply when designing public facing plus a few more.
Do
- Create a site map
- Provide links to related pages (e.g. related articles).
- Have a table of contents (e.g. in Help Docs)
- Tell the user when all form fields are required.
- Mark optional fields as
(optional).
This guideline fulfills the following WCAG guidelines:
Navigating the UI (FAQ)
These guidelines are meant as best practices. Refer to the FAQ for more details.
- Don’t show sighted users
Skip to Contentlinks. - Use the object’s or destination’s name as the link instead of
Click hereorRead morewhere possible. - Put
Learn moreor other ambiguous links at the end of a sentence. - Know the difference between a
Navigation BarandSite Map. - Don’t identify content only by its shape, size, location, or implementation.
- Don’t provide instructions only through sound.









