Accessibility Follow

It should be perfectly possible to create services and applications with AuraPlayer that fulfill WCAG 2.0(A/AA/AAA), Section 508 and similar accessibility standards and requirements.

AuraPlayer's styling and layout can be applied to a wide range of markup structures. This documentation aims to provide developers with best practice examples to demonstrate the use of AuraPlayer itself and illustrate appropriate semantic markup, including ways in which potential accessibility concerns can be addressed.

AuraPlayer's interactive components are designed to work for touch, mouse and keyboard users. Through the use of relevant WAI-ARIA roles and attributes, these components should also be understandable and operable using assistive technologies (such as screen readers).

Because AuraPlayer's components are purposely designed to be fairly generic, AuraPlayer may assist users to include further ARIA roles and attributes, as well as JavaScript behavior, to more accurately convey the precise nature and functionality of their component. This is usually noted in the documentation.

Most colors that currently make up AuraPlayer's default palette—used throughout the framework for things such as button variations, alert variations, form validation indicators—lead to insufficient color contrast (below the recommended WCAG 2.0 color contrast ratio of 4.5:1) when used against a light background. Users may manually modify/extend these default colors to ensure adequate color contrast ratios.