From 2dccf4699d60cc6a1c3ad2f5b4301c3b2da71538 Mon Sep 17 00:00:00 2001 From: Angelos Orfanakos Date: Sat, 25 May 2019 20:44:12 +0300 Subject: [PATCH 1/3] Remove redundant "reading" word from hooks faq (#2036) --- content/docs/hooks-faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/hooks-faq.md b/content/docs/hooks-faq.md index 422073a90..12e1db0b7 100644 --- a/content/docs/hooks-faq.md +++ b/content/docs/hooks-faq.md @@ -656,7 +656,7 @@ Note that in the above example we **need** to keep the function in the dependenc ### What can I do if my effect dependencies change too often? {#what-can-i-do-if-my-effect-dependencies-change-too-often} -Sometimes, your effect may be using reading state that changes too often. You might be tempted to omit that state from a list of dependencies, but that usually leads to bugs: +Sometimes, your effect may be using state that changes too often. You might be tempted to omit that state from a list of dependencies, but that usually leads to bugs: ```js{6,9} function Counter() { From 23b242edc4c7eeee5798953ba205e36cc71016b8 Mon Sep 17 00:00:00 2001 From: Brendan Falkowski Date: Sat, 25 May 2019 15:48:27 -0700 Subject: [PATCH 2/3] Say "disconnecting" not "plugging out" your mouse (#2037) The previous phrase "plugging out" is uncommon in English. Saying "disconnecting" is better than "unplugging" because many mouse users have wireless mice, and is more accurate. --- content/docs/accessibility.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/accessibility.md b/content/docs/accessibility.md index 18442b9a1..11668c0c3 100644 --- a/content/docs/accessibility.md +++ b/content/docs/accessibility.md @@ -421,7 +421,7 @@ There are a number of tools we can use to assist in the creation of accessible w By far the easiest and also one of the most important checks is to test if your entire website can be reached and used with the keyboard alone. Do this by: -1. Plugging out your mouse. +1. Disconnecting your mouse. 1. Using `Tab` and `Shift+Tab` to browse. 1. Using `Enter` to activate elements. 1. Where required, using your keyboard arrow keys to interact with some elements, such as menus and dropdowns. From df670efc5c8b64414704c18f0a0b7757d2ed9c88 Mon Sep 17 00:00:00 2001 From: jakubdrozdek Date: Mon, 27 May 2019 17:11:49 +0200 Subject: [PATCH 3/3] Resolve conflicts --- content/docs/accessibility.md | 7 ------- 1 file changed, 7 deletions(-) diff --git a/content/docs/accessibility.md b/content/docs/accessibility.md index df4a897dd..ab424685a 100644 --- a/content/docs/accessibility.md +++ b/content/docs/accessibility.md @@ -431,14 +431,7 @@ Instrukcja sprawdzenia aplikacji: 3. Używaj klawisza `Enter` do aktywowania elementów. 4. W razie potrzeby używaj klawiszy strzałek do interakcji z niektórymi elementami, takimi jak menu i listy rozwijane. -<<<<<<< HEAD ### Pomoc przy tworzeniu {#development-assistance} -======= -1. Disconnecting your mouse. -1. Using `Tab` and `Shift+Tab` to browse. -1. Using `Enter` to activate elements. -1. Where required, using your keyboard arrow keys to interact with some elements, such as menus and dropdowns. ->>>>>>> 23b242edc4c7eeee5798953ba205e36cc71016b8 Część testów dostępności możemy wykonać bezpośrednio w naszym kodzie JSX. Często kontrole dostępności dla ról, stanów i właściwości ARIA są wbudowane w środowisko IDE obsługujące JSX. Dodatkowo, mamy do dyspozycji również inne narzędzia: