React Button - Accessibility

• - All component features meet the requirement
• - Some component features may not meet the requirement
• - Accessibility requirement is not supported

The Button component complies to all Section 508 and WCAG 2.x standards criteria.

A user can use the following keys to interact with the Button component:

Use the registerKeyHandler(key, handler) method to implement a custom handler for a key.

import { ..., ViewChild, AfterViewInit } from '@angular/core';
import { DxButtonModule, DxButtonComponent } from 'devextreme-angular';
// ...
export class AppComponent implements AfterViewInit {
    @ViewChild(DxButtonComponent, { static: false }) button: DxButtonComponent;
    // Prior to Angular 8
    // @ViewChild(DxButtonComponent) button: DxButtonComponent;
 
    ngAfterViewInit () {
        this.button.instance.registerKeyHandler('backspace', function(e) {
            // The argument "e" contains information on the event
        });
        this.button.instance.registerKeyHandler('space', function(e) {
            // ...
        });
    }
}
@NgModule({
    imports: [
        // ...
        DxButtonModule
    ],
    // ...
})

The Button component supports screen readers and complies to WAI-ARIA standards.

The Button's aria label depends on the properties you use. If you specify the text property, its value is copied to the aria-label. If you do not specify text, but set the icon property, the icon can affect the aria label, depending on the value:

• SVG
  The content of the title tag is copied to the aria label.

• DevExtreme icon, font icon
  The icon name is copied to the aria label.

• Path to the icon file
  The file name is copied to the aria label.

In other cases, use elementAttr to specify the aria-label directly.