Add a scope attribute to KendoUI Grid for 508 Compliance

[Kapil]

I need to add a scope attribute  to make the KendoUI Grid 508 Compliant. How do I do that?

<th scope="col" </th>

<th scope="row"></th>

   @(Html.Kendo().Grid <PGC.Administration.ViewModels.UsersVM>()
                        .Name("users")
                        .Columns(columns =>
                        {
                            columns.Bound(p => p.UserName);
                            columns.Bound(p => p.FirstName);
                            columns.Bound(p => p.LastName);
                            columns.Bound(p => p.Email);
                            columns.Bound(p => p.LastLoginDate).Format("{0:MM/dd/yyyy hh:mm}");
                            columns.Bound(p=> p.UserPONames).Title("Program Office Names");
                            columns.Bound(p=> p.UserRoleName).Title("User Role Names");
                            columns.Command(command => { command.Custom("Edit").Click("showCreate");@* command.Destroy().Text(" ");*@ }).Width(150);
                        })

 

[Alexander]

Hi Kapil,

Thank you for taking the time to share the relevant configuration that is currently utilized on your end.

Generally, the Telerik UI for ASP.NET Core Grid is compliant with the Section 508 requirements.

We do have an article where you can find a table that is based on the Voluntary Product Accessibility Template (VPAT) requirements. It provides a detailed explanation of the accessibility features Kendo UI delivers according to Section 508 Web content standards:

• Section 508 and WCAG 2.1 Compliance

Whilst utilizing the "scope" attribute for the integrated header cells within the Grid's DOM structure. You can verify this by running the following online demo:

• Grid Keyboard Navigation Demo - notice that setting the .Navigatable() API configuration provides quick access to available grid features without the need to interact with the mouse. 

And inspecting the rendered markup within the inspector:

I hope this information helps if there are any further encountered issues regarding compliance, please feel free to share additional details. Or, in case I misunderstood the requirement.

Kind Regards,
Alexander
Progress Telerik