This assessment covers the Engineering Village application. The application shows some issues for accessibility, but very few stand out as major problems when it comes to navigating with a screen reader or using only the keyboard. There have been obvious efforts to use ARIA to make user interface components accessible, and it works well for the most part. There are however still issues, as this report demonstrates.
Top 3 Issues:
- Unreliable use of title attributes to convey additional information – In an attempt to provide more contextual information to support navigation, the application relies heavily on title attribute values to provide complementary information. While this is a conformant approach to coding, the support for title attribute values varies greatly from one assistive technology to the next, making this strategy unreliable at best for screen reader users.
- Inconsistent identification of UI components for screen readers – In an attempt to make content more accessible to screen reader users, the application provides them with added information that often times does not match with what sighted users can see. That creates a dissonance in the information conveyed that could prove problematic when sighted users support non-sighted users going through the interfaces.
- Declaration of states with screen readers – Throughout the application, a lot of feedback is provided visually, through updates in content, of actualization of information. Very few of those changes of context are conveyed to screen reader users. As a result, non-sighted users may miss key information, or be misled into thinking that nothing happened following their triggering of a call to action.