From 69ecc438bcd3b17a9b9c59f594212e12e8fa5318 Mon Sep 17 00:00:00 2001 From: Nicolas Cusan Date: Tue, 22 Sep 2020 10:40:51 +0200 Subject: [PATCH] fix typo --- Readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Readme.md b/Readme.md index 1f25f2d..7c7ad06 100644 --- a/Readme.md +++ b/Readme.md @@ -111,7 +111,7 @@ Creating two different styles for `h1` is made easy, only the properties for the ### Buttons -`button` tags have a lot of default styles that can make them cumbersome to use from a styling perspective, especially if they should look like plain things or need to wrap some other content, but `button` tags are the recommended elements to use as click targets for user interactions. Falling back to using `` even with `role="button"` is [not recomended](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/button_role) from an accessibility standpoint as screen readers will recognize `button`s as interactive elements by default and treat them accordingly. `a` should be used when there is the need to link to a page via `href`. +`button` tags have a lot of default styles that can make them cumbersome to use from a styling perspective, especially if they should look like plain links or need to wrap some other content, but `button` tags are the recommended elements to use as click targets for user interactions. Falling back to using `` even with `role="button"` is [not recomended](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/button_role) from an accessibility standpoint as screen readers will recognize `button`s as interactive elements by default and treat them accordingly. `a` should be used when there is the need to link to a page via `href`. destyle.css resets buttons completely to make them usable as any other element * see note [below](#caveats).