@progress/wct-a11y-spec/dist/jquery/aria/foatingactionbutton_aria.md

Contains accessibility and keyboard navigation specification of Telerik and Kendo web components.

The Kendo UI for jQuery FloatingActionButton component is [WCAG 2.1 AAA](https://www.w3.org/TR/WCAG21/) and [Section 508](http://www.section508.gov/) compliant. The component also follows the [WAI-ARIA best practices](https://www.w3.org/WAI/ARIA/apg/) for implementing the keyboard navigation for its component role, and is tested against the popular screen readers.

## Wai-Aria


The FloatingActionButton features two distinct modes of operation: button only and button with menu.

### Button only mode

| Selector | Attribute | Usage |
| -------- | --------- | ----- |
| .k-fab | `role=button` or `nodeName=button` | Or omitted if `<button>` DOM element is used. |
|  | `aria-label` | The attribute must be present when no text is initially visible on the button. |
|  | `aria-disabled=true` | Rendered only when the button is disabled and the `disabled` attribute could not be used (applicable for `<button>` or `<input type="button">` elements). |

### Button with Menu mode


In this mode the FloatingActionButton must implement the specification for the **DropDownButton** component.

[DropDownButton accessibility specification]({{dropdownbutton_a11y_link}})

## Resources

[ARIA practices Navigation Menu Button Example](https://www.w3.org/WAI/ARIA/apg/example-index/menu-button/menu-button-links.html)

## Section 508


The FloatingActionButton is compliant with the [Section 508](http://www.section508.gov/) requirements

## Testing


The component has been extensively tested automatically with static code analyzers and manually with the most popular screen readers.

> Any Accessibility Issues could be reported in [Telerik Support System](https://www.telerik.com/account/support-center).

### Screen Readers

| Environment | Tool |
| ----------- | ---- |
| Firefox | NVDA |
| Chrome | JAWS |
| Microsoft Edge | JAWS |