-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
new file: disabled-vs-aria-disabled-on-form-elements.md
- Loading branch information
Showing
1 changed file
with
12 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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/) | ||
|