Accessible technology

Common barriers to web accessibility are (a) incompatibility with speech recognition or screen reading software, (b) lack of text-based alternatives to media content, (c) poor color contrast or small text size, and (d) transaction timing requirements that do not take into account intellectual disabilities. What does it mean to have an accessible website?  At the most basic level, an accessible website would have these (and other) accessible elements:

• Provides text alternatives for any non-text content;
• Provides alternatives for time-based media;
• Includes content that can be presented in different ways without losing information or structure;
• Is easy to see and hear, including separating foreground from background;
• Permits all functionality from a keyboard if needed (as opposed to a cursor);
• Permits sufficient time to read and use content;
• Is not designed in a way that is known to cause seizures;
• Includes ways to help users navigate, find content, and determine where they are;
• Includes text content that is readable and understandable;
• Operates and appears in predictable ways;
• Helps users avoid and correct mistakes; and
• Is compatible with current and future user agents, including assistive web technologies.

The above from http://www.employerlawreport.com/2015/12/articles/eeo/website-accessibility-regulations-delayed-until-2018-but-businesses-should-not-table-the-issue-until-then/

UserWay provides helpful accessibility plugins (we understand at no cost) that work without refactoring your website's existing code and will increase compliance with WCAG 2.0, ATAG 2.0, ADA, & Section 508 requirements.  https://userway.org/.