From 9dd7d3d66f5d549f98599d29aead110248a27b21 Mon Sep 17 00:00:00 2001 From: Florent Dubost Date: Mon, 19 Aug 2024 17:15:35 +0200 Subject: [PATCH] Update _posts/2024-08-20-js-nation-react-summit-2024.md Co-authored-by: Etienne D. --- _posts/2024-08-20-js-nation-react-summit-2024.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/_posts/2024-08-20-js-nation-react-summit-2024.md b/_posts/2024-08-20-js-nation-react-summit-2024.md index dc2ec9430..8e492ce19 100644 --- a/_posts/2024-08-20-js-nation-react-summit-2024.md +++ b/_posts/2024-08-20-js-nation-react-summit-2024.md @@ -160,7 +160,7 @@ Sid highlights specific examples, such as [navigating tab lists](https://www.w3. What we remember from this talk: -- importance of using correct HTML elements and ARIA roles for accessibility, -- implementation of ARIA roles like `tablist`, `tab`, and `aria-selected`, -- significance of keyboard navigation and ARIA states/properties in accessibility, -- design considerations for accessibility, including using `aria-disabled` over `disabled`. +- Importance of using correct HTML elements and ARIA roles for accessibility +- Implementation of ARIA roles like `tablist`, `tab`, and `aria-selected` +- Significance of keyboard navigation and ARIA states/properties in accessibility +- Design considerations for accessibility, including using `aria-disabled` over `disabled`