Skip to content

chore(Toolbar): add scroll buttons #2747

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Feb 10, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,80 @@
---
title: Wai-Aria Support
page_title: Telerik UI for Blazor FloatingActionButton Documentation | FloatingActionButton Accessibility
description: "Get started with the Telerik UI for Blazor FloatingActionButton and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
tags: telerik,blazor,accessibility,wai-aria,wcag
slug: floatingactionbutton-wai-aria-support
position: 50
---

# Blazor FloatingActionButton Accessibility

@[template](/_contentTemplates/common/parameters-table-styles.md#table-layout)



Out of the box, the Telerik UI for Blazor FloatingActionButton provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.


The FloatingActionButton is compliant with the [Web Content Accessibility Guidelines (WCAG) 2.2 AA](https://www.w3.org/TR/WCAG22/) standards and [Section 508](https://www.section508.gov/) requirements, follows the [Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA)](https://www.w3.org/WAI/ARIA/apg/) best practices for implementing the [keyboard navigation](#keyboard-navigation) for its `component` role, provides options for managing its focus and is tested against the most popular screen readers.

## WAI-ARIA


This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.


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` | Omitted if the `<button>` DOM element is used. |
| | `aria-label` or `title` | The attribute must be present when no text is initially visible in the button. |
| `.k-fab.k-disabled` | `aria-disabled=true` | Rendered only when the button is disabled and the `disabled` attribute cannot be used. Applicable for the `<button>` or `<input type="button">` elements. |

### Button-with-Menu Mode


In the button-with-menu mode, the FloatingActionButton must implement the specification for the DropDownButton component.

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

## Resources

[WAI-ARIA Authoring 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 fully compliant with the [Section 508 requirements](http://www.section508.gov/).

## Testing


The FloatingActionButton has been extensively tested automatically with [axe-core](https://github.com/dequelabs/axe-core) and manually with the most popular screen readers.

> To report any accessibility issues, contact the team through the [Telerik Support System](https://www.telerik.com/account/support-center).

### Screen Readers


The FloatingActionButton has been tested with the following screen readers and browsers combinations:

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



## Keyboard Navigation

For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.

## See Also

* [FloatingActionButton Overview](https://demos.telerik.com/blazor-ui/floatingactionbutton/overview)
* [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
2 changes: 2 additions & 0 deletions components/toolbar/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,8 @@ The Blazor ToolBar provides parameters to configure the component:
| `Adaptive` <br /> (deprecated) | `bool` <br /> (`true`) | Toggles the overflow popup of the ToolBar. The component displays an additional anchor on its side, where it places all items which do not fit and overflow. [Template items](slug://toolbar-templated-item#notes) don't participate in this mechanism and they are always rendered in the ToolBar itself. This parameter is deprecated in favor of `OverflowMode`. |
| `Class` | `string` | The CSS class to be rendered on the main wrapping element of the ToolBar component, which is `<div class="k-toolbar">`. Use for [styling customizations](slug://themes-override). |
| `OverflowMode` | `ToolBarOverflowMode` <br /> (`Menu`) | The adaptive mode of the Toolbar. |
| `ScrollButtonsPosition` | `ToolBarScrollButtonsPosition` enum <br /> (`Split`) | Specifies the position of the buttons when the ToolBar scroll adaptive mode is enabled. |
| `ScrollButtonsVisibility` | `ToolBarScrollButtonsVisibility` enum <br /> (`Visible`)| Specifies the visibility of the buttons when the ToolBar scroll adaptive mode is enabled. |

### Styling and Appearance

Expand Down
4 changes: 4 additions & 0 deletions knowledge-base/textbox-validate-on-change.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,10 @@ res_type: kb
<td>Product</td>
<td>TextBox for Blazor</td>
</tr>
<tr>
<td>Product Version</td>
<td>2.30 and older</td>
</tr>
</tbody>
</table>

Expand Down
15 changes: 15 additions & 0 deletions src-a11y/configs/floatingactionbutton.aria.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
title: Wai-Aria Support
component: FloatingActionButton
from: /aria/floatingactionbutton_aria.md
dest: ../components/floatingactionbutton/accessibility/wai-aria-support.md
slug: floatingactionbutton-wai-aria-support
position: 50
after: |
## Keyboard Navigation

For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview](slug://accessibility-overview#keyboard-navigation) article.

## See Also

* [FloatingActionButton Overview](https://demos.telerik.com/blazor-ui/floatingactionbutton/overview)
* [Accessibility in Telerik UI for Blazor](slug://accessibility-overview)
Loading