New to Telerik UI for ASP.NET CoreStart a free 30-day trial

Grid Accessibility

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

The Grid is compliant with the Web Content Accessibility Guidelines (WCAG) 2.2 AA standards and Section 508 requirements, follows the Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA) best practices for implementing the 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 Grid is a composite component that consists of 4 logically separated structural elements:

  • Toolbar (role=toolbar);
  • Group header (role=toolbar);
  • Data Grid (role=grid);
  • Pager (role=application);

Grid Toolbar

Grid Toolbar follows the specification of the ToolBar component.

ToolBar accessibility specification

SelectorAttributeUsage
.k-grid-toolbarrole=toolbarThe toolbar is a collection of command buttons and inputs.
aria-labelClarifies the purpose of the toolbar.
aria-controls=.k-grid-content>table idPointing to the id of the element with role=grid.

Grid Grouping Header

Grid Grouping Header follows the specification of the ToolBar component.

ToolBar accessibility specification

SelectorAttributeUsage
.k-grouping-headerrole=toolbarThe Grouping header is a ToolBar (collection of buttons).
aria-labelClarifies the purpose of the header.
aria-controls=.k-grid-content>table idPointing to the id of the element with role=grid.
.k-grouping-header .k-chip-list .k-chiprole=buttonIf the element used is not <button>, then the role must be specified.
.k-grouping-header .k-chip-listrole=none/The ChipList default listbox role is removed to keep the toolbar --> button roles hierarchy.
titlePresent on the element or its child if sorting is enabled for that field.

Data Grid (excluding Toolbars and Pager)

The element with role=grid must not include the ToolBar and the Pager elements as those do not belong to the role=grid element itself.

In the Telerik UI for ASP.NET Core Grid, the role=grid is assigned to the <table> in the k-grid-content element.

Grid element

SelectorAttributeUsage
.k-grid:not(.k-treelist) .k-grid-content>tablerole=gridThe role specifies the element is a Data Grid.
.k-grid-aria-rootaria-colcountThe total number of columns in the Grid. Needed only for Virtual columns and Hidden columns scenarios, when not all columns are rendered in the DOM. If the total number of columns is unknown, the value of aria-colcount must be set to -1.
aria-rowcountThe total number of rows in the table (header rows + master rows + detail rows + data rows + footer rows + aggregates rows). Needed only when Paging (and more that 1 page is present in the component), Virtual rows, or Master/Detail rows (Hierarchical Grid, Detail Template Grid) are enabled. If data is also Grouped, the proper number of all rows could not be calculated. In that case the value must be set to -1.

In scenarios when master and detail rows are present in the Grid (Hierarchical Grid, Detail Template Grid), the aria-rowcount (the total number of rows) must be calculated: 2 * (total number of items) + header rows + footer rows. That is because for each item in the Grid there is a master row and a detail row duplicating this way the number of rows.

If the Grid is composed of a single table (there is no separate <table> element for its header), no role attributes should be set on its inner elements(<thead>, <body>, <tr>, <th>, and <td>). Their semantic meaning will be used instead.

Grid header

SelectorAttributeUsage
.k-grid-header-wrap>tablerole=presentation/noneNegates the default semantic role of the <table> element.
.k-grid-header-wrap>table>theadrole=rowgroupRequired as the owner <table> element has its semantic role removed.
idId must be present on the element, so that it can be properly referenced in the role=grid element.
.k-grid-header-wrap>table>thead>trrole=rowRequired as the owner <table> element has its semantic role removed.
aria-rowindexRow number including all headers, data (including master and detail) rows, and footers starting from 1. Needed only when Paging (and more that 1 page is present in the component), Virtual rows, or Master/Detail rows (Hierarchical Grid, Detail Template Grid) are enabled. If data is also Grouped, the proper indexing could not be calculated. Hence, the attribute must not be set.
.k-grid-header-wrap>table>thead>tr>th:not(.k-hierarchy-cell):not(.k-group-cell):not(.k-drag-cell)role=columnheaderRequired as the owner <table> element has its semantic role removed.
aria-sort=none/ascending/descendingPresent if sorting is enabled for that column.
title or aria-labelPresent on the element or its child if sorting is enabled for that field.
aria-colindexCol number, based on leaf columns, starting from 1. Needed only for Virtual columns and Hidden columns scenarios, when not all columns are rendered in the DOM. Otherwise, can be interpreted from the DOM structure. Can be calculated by summing previous columns colspans.
aria-haspopup=dialogThe attribute must be present if the column has a ColumnMenu.
aria-haspopup=dialogThe attribute must be present if the column has a FilterMenu and no ColumnMenu.

Grid locked header

SelectorAttributeUsage
.k-grid-header-locked>tablerole=none/presentationNegates the default semantic role of the <table> element.
.k-grid-header-locked>table>thead>tr>throle=columnheaderRequired as the owner <table> element has its semantic role removed.
title or aria-labelPresent on the element or its child if sorting is enabled for that field.
aria-colindexCol number, based on leaf columns, starting from 1. Needed only for Virtual columns and Hidden columns scenarios, when not all columns are rendered in the DOM. Otherwise, can be interpreted from the DOM structure. Can be calculated by summing previous columns colspans.
idId must be present on the element, so that it can be properly referenced in the respective <tr> element in the k-grid-header-wrap <thead> element.
.k-grid-header-locked .k-header[data-role='columnsorter']aria-sort=none/ascending/descendingPresent if sorting is enabled for that column.
.k-grid-header-locked .k-header[data-role='columnmenu']aria-haspopup=menuThe attribute must be present if the column has a ColumnMenu.
.k-grid-header-locked .k-header[data-role='filtermenu']aria-haspopup=dialogThe attribute must be present if the column has a FilterMenu and no ColumnMenu.

Grid filter row

Even if part of the <thead>, the Filter row must be composed of <td> elements.

SelectorAttributeUsage
.k-grid-header-wrap>table>thead>tr.k-filter-row>tdrole=gridcellRequired as the owner <table> element has its semantic role removed.
aria-labelHas a label indicating that the cell is part of a filter row.

Grid locked filter row

Even if part of the <thead>, the Filter row must be composed of <td> elements.

SelectorAttributeUsage
.k-grid-header-locked>table>thead>tr.k-filter-row>tdrole=gridcellRequired as the owner <table> element has its semantic role removed.
aria-labelHas a label indicating that the cell is part of a filter row.
idId must be present on the element, so that it can be properly referenced in the respective <tr> filter row element in the k-grid-header-wrap <thead> element.

Grid content

SelectorAttributeUsage
.k-grid:not(.k-treelist) .k-grid-content>tablerole=gridThis is the main focusable Grid element (see above).
.k-grid-content>table>tbodyrole=rowgroupRequired as the owner <table> element has its semantic role removed.
.k-grid-content>table>tbody>trrole=rowRequired as the owner <table> element has its semantic role removed.
aria-rowindexRow number including all headers, data (including master and detail) rows, and footers starting from 1. Needed only when Paging (and more that 1 page is present in the component), Virtual rows, or Master/Detail rows (Hierarchical Grid, Detail Template Grid) are enabled. If data is also Grouped, the proper indexing could not be calculated. Hence, the attribute must not be set. In scenarios when master and detail rows are present in the Grid (Hierarchical Grid, Detail Template Grid), both master and detail rows must always be indexed. For example, if the first master row has aria-rowindex=2, even if its detail row is not present in the DOM, the next master row must have aria-rowindex=4. When rendered, the detail row must receive the missing index between the two master rows. In this example it would be aria-rowindex=3.
.k-grid-content tr.k-selectedaria-selected=trueSet on the currently selected row(s). Only used wen selection mode is set to row.
.k-grid-content-locked + .k-grid-content traria-ownsIf the Grid contains locked columns, the attribute points to the ids of the locked cells belonging visually to the same row.
.k-grid-content>table>tbody>tr>tdrole=gridcellRequired as the owner <table> element has its semantic role removed.
aria-colindexCol number, based on leaf columns, starting from 1. Needed only for Virtual columns and Hidden columns scenarios, when not all columns are rendered in the DOM. Otherwise, can be interpreted from the DOM structure. Can be calculated by summing previous columns colspans.
td.k-selectedaria-selected=trueSet on the currently selected cell(s). Only used when selection mode is set to cell.
.k-master-row .k-hierarchy-cell,.k-grouping-row>tdaria-expanded=true/falseOptionally for cells holding grouping criteria values and for Master row cells in Detail template scenario.
.k-drag-cellaria-labelMust be present in a Drag Row scenario on the cell containing the drag handle.

Grid locked content

SelectorAttributeUsage
.k-grid-content-locked>tablerole=none/presentationNegates the default semantic role of the <table> element.
.k-grid-content-locked>table>tbody>tr>tdrole=gridcellRequired as the owner <table> element has its semantic role removed.
aria-colindexCol number, based on leaf columns, starting from 1. Needed only for Virtual columns and Hidden columns scenarios, when not all columns are rendered in the DOM. Otherwise, can be interpreted from the DOM structure. Can be calculated by summing previous columns colspans.
idId must be present on the element, so that it can be properly referenced in the respective <tr> element in the k-grid-content <tbody> element.

The Aggregates totals are placed within a <tfoot> element in the Content <table>.

SelectorAttributeUsage
.k-grid-footer-wrap>tablerole=none/presentationNegates the default semantic role of the <table> element.
tfootrole=rowgroupRequired as the owner <table> element has its semantic role removed.
idId must be present on the element, so that it can be properly referenced in the role=grid element.
tfoot>trrole=rowRequired as the owner <table> element has its semantic role removed.
aria-rowindexRow number including all headers, data (including master and detail) rows, and footers starting from 1. Footer rows are always the last ones in a Grid. Needed only when Paging (and more that 1 page is present in the component), Virtual rows, or Master/Detail rows (Hierarchical Grid, Detail Template Grid) are enabled. If data is also Grouped, the proper indexing could not be calculated. Hence, the attribute must not be set.
tfoot>tr>tdrole=gridcellRequired as the owner <table> element has its semantic role removed.
aria-colindexCol number, based on leaf columns, starting from 1. Needed only for Virtual columns and Hidden columns scenarios, when not all columns are rendered in the DOM. Otherwise, can be interpreted from the DOM structure. Can be calculated by summing previous columns colspans.
SelectorAttributeUsage
.k-grid-footer-locked>tablerole=none/presentationNegates the default semantic role of the <table> element.
.k-grid-footer-locked>table>tfoot>tr>tdrole=gridcellRequired as the owner <table> element has its semantic role removed.
aria-colindexCol number, based on leaf columns, starting from 1. Needed only for Virtual columns and Hidden columns scenarios, when not all columns are rendered in the DOM. Otherwise, can be interpreted from the DOM structure. Can be calculated by summing previous columns colspans.
idId must be present on the element, so that it can be properly referenced in the respective <tr> element in the k-grid-footer-wrap <tfoot> element.

Pager

For the Grid Pager WAI-ARIA spec, please review the Pager component.

Pager accessibility specification.

Grid selection aggregates

The selection aggregates are placed within a .k-grid-selection-aggregates element after the Grid .k-grid-aria-root element.

SelectorAttributeUsage
.k-grid-selection-aggregatesaria-live=politeEnsures that changes in the calculated selection aggregates are announced by assistive technologies.

Resources

WAI-ARIA specification for grid

Section 508

The Grid is fully compliant with the Section 508 requirements.

Testing

The Grid has been extensively tested automatically with axe-core and manually with the most popular screen readers.

To report any accessibility issues, contact the team through the Telerik Support System.

Screen Readers

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

EnvironmentTool
FirefoxNVDA
ChromeJAWS
Microsoft EdgeJAWS

Test Example

To test the Grid component, refer to the Grid Accessibility Demo.

Keyboard Navigation

For details on how the Grid keyboard navigation works, refer to the Grid Keyboard Navigation article.

See Also