Notes on Optimal User Experience for Digital Properties

Updated: Jan 18, 2021


Compass indicating a knowledge of where you are and where you are going = Accessibility
Your Accessibility Baseline

The basis of accessibility of any digital property is to ensure you have not placed a barrier between the content and the user. All users must be able to access the content regardless of the method used. Microsoft Accessibility identifies the following areas affecting method of use:

Vision, Hearing, Neurodiversity, Learning, Mobility, and Mental Health.

Designers and Developers must provide an environment which allows not only a visual experience but also allows:

  • All elements to be accessed by Keyboard and finger swipes as well as mouse and Screen reader and dictation software

  • All elements to be controlled by the user and have captions and transcripts (no auto-play of video or sound)

  • All information must follow Plain Language guidelines

  • All elements must follow a logical pattern with simplicity as the main focus and all items must be in the tab order to be keyboard accessible (The less-is-more, logical concept improves clarity, helps with distraction, concentration, and understanding)

  • All elements must follow responsive design principles to provide an equal experience for all screen sizes.

  • All hyperlinks must clearly state the location, not rely on color alone to indicate a link (underlines and color), and have unique text (no click here or more)

  • All images which provide information must have descriptive Alt text

  • All buttons must be coded as buttons not links styled as buttons

  • Any PDF, word processing, spreadsheet, or slide presentation documents must be tagged and have all accessibility elements in place.

Resources:

Accessibility Technology & Tools - Microsoft Accessibility

Home | plainlanguage.gov

HTML Responsive Web Design (w3schools.com)

Screen sizes and break points for responsive design - UWP applications | Microsoft Docs

Xcode Overview: Building for Multiple Screen Sizes (apple.com)

Support different screen sizes | Android Developers

PDF/UA in a Nutshell – PDF Association

Required Fixes for Office Files | HHS.gov

Web Content Accessibility Guidelines (WCAG) 2.1 (w3.org)

WCAG-EM Overview: Website Accessibility Conformance Evaluation Methodology | Web Accessibility Initiative (WAI) | W3C



12 views0 comments