1 files changed, 1 insertions, 1 deletions
diff --git a/content/notebook/fediverse/in-depth-image-descriptions.md b/content/notebook/fediverse/in-depth-image-descriptions.md
index 9fe7e48..8af09ff 100644
--- a/content/notebook/fediverse/in-depth-image-descriptions.md
+++ b/content/notebook/fediverse/in-depth-image-descriptions.md
@@ -18,7 +18,7 @@ Imagine you're using an online shop.
 What you'll typically see is a list of products where each list item has a small preview image, a product name and some other metadata.\
 Now imagine that the shop displays a long textual description for each product instead.
 This is what the timeline appears like to screen reader users if long image descriptions are used.
-And unlike people seeing the text, they don't have the luxury of skimming to grasp vital information quickly -- they can only skip the rest of the description at any point, or wait for the screen reader to read all of it.
+And unlike people seeing the text, they don't have the luxury of skimming to grasp vital information quickly -- they can only wait for the screen reader to read all of it or until they decide to skip the rest.
 Detailed descriptions are only helpful when the user has decided the content is interesting to them.
 Currently, most fedi frontends put them in the attachment's `alt` attribute, which is fine if the user is currently viewing a single post instead of the timeline.

diff --git a/content/notebook/fediverse/in-depth-image-descriptions.md b/content/notebook/fediverse/in-depth-image-descriptions.md index 9fe7e48..8af09ff 100644 --- a/content/notebook/fediverse/in-depth-image-descriptions.md +++ b/content/notebook/fediverse/in-depth-image-descriptions.md
@@ -18,7 +18,7 @@ Imagine you're using an online shop.
18	What you'll typically see is a list of products where each list item has a small preview image, a product name and some other metadata.\	18	What you'll typically see is a list of products where each list item has a small preview image, a product name and some other metadata.\
19	Now imagine that the shop displays a long textual description for each product instead.	19	Now imagine that the shop displays a long textual description for each product instead.
20	This is what the timeline appears like to screen reader users if long image descriptions are used.	20	This is what the timeline appears like to screen reader users if long image descriptions are used.
21	And unlike people seeing the text, they don't have the luxury of skimming to grasp vital information quickly -- they can only skip the rest of the description at any point, or wait for the screen reader to read all of it.	21	And unlike people seeing the text, they don't have the luxury of skimming to grasp vital information quickly -- they can only wait for the screen reader to read all of it or until they decide to skip the rest.
22		22
23	Detailed descriptions are only helpful when the user has decided the content is interesting to them.	23	Detailed descriptions are only helpful when the user has decided the content is interesting to them.
24	Currently, most fedi frontends put them in the attachment's `alt` attribute, which is fine if the user is currently viewing a single post instead of the timeline.	24	Currently, most fedi frontends put them in the attachment's `alt` attribute, which is fine if the user is currently viewing a single post instead of the timeline.