From f1b0f8775a8b0d6e054b49e75c1cd82fe0af18fc Mon Sep 17 00:00:00 2001 From: Marten Date: Mon, 9 Sep 2024 01:46:09 +0200 Subject: [PATCH] Corrected spelling and word flow (#35797) * Corrected spelling and word flow * Apply suggestions from code review --------- Co-authored-by: Hamish Willee --- files/en-us/web/accessibility/aria/roles/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/accessibility/aria/roles/index.md b/files/en-us/web/accessibility/aria/roles/index.md index 5bd7a939b19aeb7..82ef2d77f7e9406 100644 --- a/files/en-us/web/accessibility/aria/roles/index.md +++ b/files/en-us/web/accessibility/aria/roles/index.md @@ -73,7 +73,7 @@ These are included for completeness, but in most cases are rarely, if ever, usef ### 2. Widget roles -The various widget role are used to define common interactive patterns. Similar to the document structure roles, some of these roles duplicate the semantics of native HTML elements that are well supported, and should not be used. The difference between the two lists is that, generally, the widget roles require JavaScript interaction and the document structure roles don't necessarily. +Widget roles are used to define common interactive patterns. Like document structure roles, some widget roles have the same semantics as well-supported native HTML elements, and therefore should be avoided. The key difference is that widget roles typically require JavaScript for interaction, while document structure roles often do not. - [scrollbar](/en-US/docs/Web/Accessibility/ARIA/Roles/scrollbar_role) - [searchbox](/en-US/docs/Web/Accessibility/ARIA/Roles/searchbox_role)