From 8023d0f61c8d64108bf5f9ee9ae051e803f17acf Mon Sep 17 00:00:00 2001 From: byt3h3ad Date: Sat, 11 May 2024 04:11:03 +0530 Subject: [PATCH] new file: disabled-vs-aria-disabled-on-form-elements.md --- html/disabled-vs-aria-disabled-on-form-elements.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 html/disabled-vs-aria-disabled-on-form-elements.md diff --git a/html/disabled-vs-aria-disabled-on-form-elements.md b/html/disabled-vs-aria-disabled-on-form-elements.md new file mode 100644 index 0000000..32a6ef5 --- /dev/null +++ b/html/disabled-vs-aria-disabled-on-form-elements.md @@ -0,0 +1,12 @@ +# disabled vs aria-disabled attributes + +Generally, Kitty shares the following guidelines on when to use which attribute: + +- Use `readonly` on elements which's values still matter to the user and should be sent to the server. + +- Use `disabled` on elements which's values became irrelevant for some reason. + +- Use `aria-disabled` on elements which's interactivity is essential to succeed, because they'll stay focusable and can still trigger validations. + +[source](https://kittygiraudel.com/2024/03/29/on-disabled-and-aria-disabled-attributes/) +