Visual content reproduction - Revision history

Max at 14:54, 9 June 2021

2021-06-09T14:54:46Z

Max at 14:23, 4 June 2021

2021-06-04T14:23:03Z

Max at 14:22, 4 June 2021

2021-06-04T14:22:33Z

Max at 10:42, 25 May 2021

2021-05-25T10:42:39Z

Max at 10:07, 25 May 2021

2021-05-25T10:07:27Z

Max at 11:59, 10 May 2021

2021-05-10T11:59:17Z

Max at 11:58, 7 May 2021

2021-05-07T11:58:43Z

Max at 08:01, 7 May 2021

2021-05-07T08:01:44Z

Max at 16:04, 6 May 2021

2021-05-06T16:04:28Z

Max at 11:45, 28 April 2021

2021-04-28T11:45:20Z

@@ Line 1: / Line 1: @@
 {{Website
 |headline=VisualContentReproduction
-|coordhead=1.000, 49.252, 0.000
+|coordhead=3.000, 49.252, 0.000
 |image1=/wiki/images/VisualContentReproduction.png
 |coordimg1=0, 0, 0

@@ Line 12: / Line 12: @@
 |coordsimplo=0, 0, 0
 |testimonial=
-Ilya is blind [...] (<i>and</i>) uses a screen reader and mobile phone to access the web. Both her screen reader and her mobile phone accessibility features provide her with information regarding the device’s operating system, applications, and text content in a speech output form.
+Ilya is blind [...] <i>(and)</i> uses a screen reader and mobile phone to access the web. Both her screen reader and her mobile phone accessibility features provide her with information regarding the device’s operating system, applications, and text content in a speech output form.
 When accessing web content, the screen reader indicates aloud the structural information on a webpage such as headings, column and row headers in tables, list items, links, form controls, and more that enable her to better navigate the page, complete and submit forms, and access information in an effective manner. She is able to listen to and understand speech output at a very high speed. Ilya encounters problems when websites are not properly coded and do not include alt text descriptions on images. These sites are unnavigable and require large amounts of time to read text from the top of the page to the bottom without navigation cues. Occasionally she finds herself trapped in areas on a webpage unable to move to another area and must abandon the page altogether.
 <a href="https://www.w3.org/WAI/people-use-web/user-stories/#accountant">Source</a>
@@ Line 32: / Line 32: @@
 ==User story==
-Ilya is blind [...] (''and'') uses a screen reader and mobile phone to access the web. Both her screen reader and her mobile phone accessibility features provide her with information regarding the device’s operating system, applications, and text content in a speech output form.
+Ilya is blind [...] ''(and)'' uses a screen reader and mobile phone to access the web. Both her screen reader and her mobile phone accessibility features provide her with information regarding the device’s operating system, applications, and text content in a speech output form.
 When accessing web content, the screen reader indicates aloud the structural information on a webpage such as headings, column and row headers in tables, list items, links, form controls, and more that enable her to better navigate the page, complete and submit forms, and access information in an effective manner. She is able to listen to and understand speech output at a very high speed. Ilya encounters problems when websites are not properly coded and do not include alt text descriptions on images. These sites are unnavigable and require large amounts of time to read text from the top of the page to the bottom without navigation cues. Occasionally she finds herself trapped in areas on a webpage unable to move to another area and must abandon the page altogether.

@@ Line 5: / Line 5: @@
 |coordimg1=0, 0, 0
 |simploduction=<ul>
-<li>This section is about visible information.</li>
+<li>How to deal with visible information.</li>
-<li>People with limited or no sight rely on audible or tactile information.</li>
+<li>People with limited or no sight depend on audible or tactile information.</li>
-<li>Screen readers or Braille displays are used for this purpose.</li>
+<li>Screen readers or braille displays are used for this purpose.</li>
-<li>Written information should therefore always be embedded in such a way that it can be recognised by these devices.</li>
+<li>Written information should be embedded in a way that can be understood by these devices.</li>
-<li>Non-textual visual content should be provided with captions.</li></ul>
+<li>Non-textual visible content should be provided with captions.</li></ul>
 |coordsimplo=0, 0, 0
 |testimonial=
-Ilya is blind. She is the chief accountant at an insurance company that uses web-based documents and forms over a corporate intranet and like many other blind computer users, she does not read Braille.
+Ilya is blind [...] (<i>and</i>) uses a screen reader and mobile phone to access the web. Both her screen reader and her mobile phone accessibility features provide her with information regarding the device’s operating system, applications, and text content in a speech output form.
 When accessing web content, the screen reader indicates aloud the structural information on a webpage such as headings, column and row headers in tables, list items, links, form controls, and more that enable her to better navigate the page, complete and submit forms, and access information in an effective manner. She is able to listen to and understand speech output at a very high speed. Ilya encounters problems when websites are not properly coded and do not include alt text descriptions on images. These sites are unnavigable and require large amounts of time to read text from the top of the page to the bottom without navigation cues. Occasionally she finds herself trapped in areas on a webpage unable to move to another area and must abandon the page altogether.
 <a href="https://www.w3.org/WAI/people-use-web/user-stories/#accountant">Source</a>
 |coordtesti=0, 0, 0
@@ Line 29: / Line 24: @@
 [[File:VisualContentReproduction.png|400px|none|Illustration Visual content reproduction]]
 <div class="text_content">
-==simple introduction==
+==Overview==
-* This section is about visible information.
+* How to deal with visible information.
-* People with limited or no sight rely on audible or tactile information.
+* People with limited or no sight depend on audible or tactile information.
-* Screen readers or Braille displays are used for this purpose.
+* Screen readers or braille displays are used for this purpose.
-* Written information should therefore always be embedded in such a way that it can be recognised by these devices.
+* Written information should be embedded in a way that can be understood by these devices.
 * Non-textual visible content should be provided with captions.
-==testimonial==
+==User story==
-Ilya is blind. She is the chief accountant at an insurance company that uses web-based documents and forms over a corporate intranet and like many other blind computer users, she does not read Braille.
+Ilya is blind [...] (''and'') uses a screen reader and mobile phone to access the web. Both her screen reader and her mobile phone accessibility features provide her with information regarding the device’s operating system, applications, and text content in a speech output form.
 When accessing web content, the screen reader indicates aloud the structural information on a webpage such as headings, column and row headers in tables, list items, links, form controls, and more that enable her to better navigate the page, complete and submit forms, and access information in an effective manner. She is able to listen to and understand speech output at a very high speed. Ilya encounters problems when websites are not properly coded and do not include alt text descriptions on images. These sites are unnavigable and require large amounts of time to read text from the top of the page to the bottom without navigation cues. Occasionally she finds herself trapped in areas on a webpage unable to move to another area and must abandon the page altogether.
 Source: https://www.w3.org/WAI/people-use-web/user-stories/#accountant
-==[[Visual_content_reproduction_References|Reference Collections for Visual content reproduction]]==
+==[[Visual_content_reproduction_References|References for Visual content reproduction]]==
 ===[[Visual_content_reproduction_References#General|General]]===
 ===[[Visual_content_reproduction_References#Captions|Captions]]===

@@ Line 27: / Line 27: @@
 __TOC__
-[[File:VisualContentReproduction.png|400px|left|Illustration Visual content reproduction]]
+[[File:VisualContentReproduction.png|400px|none|Illustration Visual content reproduction]]
-<div class="text_content" style="float:left;">
+<div class="text_content">
 ==simple introduction==
 * This section is about visible information.

@@ Line 1: / Line 1: @@
 {{Website
 |headline=VisualContentReproduction
-|coordhead=25.119, 49.252, 0.000
+|coordhead=1.000, 49.252, 0.000
 |image1=/wiki/images/VisualContentReproduction.png
 |coordimg1=0, 0, 0

@@ Line 24: / Line 24: @@
 |contains=Visual_content_reproduction_References
 }}
 ==simple introduction==
 * This section is about visible information.
@@ Line 49: / Line 52: @@
 ===[[Visual_content_reproduction_References#Text_Alternatives|Text Alternatives]]===
 ===[[Visual_content_reproduction_References#Audio_Description|Audio Description]]===