diff --git a/docs/accessibility.md b/docs/accessibility.md
index 6d969725882..92305d236bb 100644
--- a/docs/accessibility.md
+++ b/docs/accessibility.md
@@ -14,7 +14,7 @@ Android and iOS differ slightly in their approaches, and thus the React Native i
 
 ### `accessible`
 
-When `true`, indicates that the view is discoverable by assistive technologies such as screen readers and hardware keyboards. Note that this does not necessarily mean that the view will be focused by VoiceOver or TalkBack. There are a number of reasons for this, such as VoiceOver disallowing nested acecssibility elements, or TalkBack opting to focus some parent element instead.
+When `true`, indicates that the view is discoverable by assistive technologies such as screen readers and hardware keyboards. Note that this does not necessarily mean that the view will be focused by VoiceOver or TalkBack. There are a number of reasons for this, such as VoiceOver disallowing nested accessibility elements, or TalkBack opting to focus some parent element instead.
 
 By default, all touchable elements are accessible.
 
diff --git a/website/versioned_docs/version-0.80/accessibility.md b/website/versioned_docs/version-0.80/accessibility.md
index 6d969725882..92305d236bb 100644
--- a/website/versioned_docs/version-0.80/accessibility.md
+++ b/website/versioned_docs/version-0.80/accessibility.md
@@ -14,7 +14,7 @@ Android and iOS differ slightly in their approaches, and thus the React Native i
 
 ### `accessible`
 
-When `true`, indicates that the view is discoverable by assistive technologies such as screen readers and hardware keyboards. Note that this does not necessarily mean that the view will be focused by VoiceOver or TalkBack. There are a number of reasons for this, such as VoiceOver disallowing nested acecssibility elements, or TalkBack opting to focus some parent element instead.
+When `true`, indicates that the view is discoverable by assistive technologies such as screen readers and hardware keyboards. Note that this does not necessarily mean that the view will be focused by VoiceOver or TalkBack. There are a number of reasons for this, such as VoiceOver disallowing nested accessibility elements, or TalkBack opting to focus some parent element instead.
 
 By default, all touchable elements are accessible.