some pictures

Sources/iOSAccessibilityHandbook/iOSAccessibilityHandbook.docc/Pages/Integration/AdoptionGuide.tutorial

@@ -105,9 +105,8 @@
             @Image(source: chapter-3-1.png, alt: "")
 
             Get familiar with the ideas and **reasoning behind accessibility**.
-            <doc:AccessibleDesign>
-            @TutorialReference(tutorial: "doc:Standarts")
-            @TutorialReference(tutorial: "doc:AccessibleDesign")
+            @TutorialReference(tutorial: "doc:Standards")
+            @TutorialReference(tutorial: "doc:InclusiveDesign")
             @TutorialReference(tutorial: "doc:VoiceOverDesigner")
         }
 

Sources/iOSAccessibilityHandbook/iOSAccessibilityHandbook.docc/Pages/Introduction/AccessibilityFeatures/SwitchControl/SwitchControl.md

@@ -18,7 +18,7 @@ Navigate through iOS by using various switches
                source: "sc-card", 
                alt: "Switch Control with opened popover with actions: Select All, Deselect, Cut, Copy")
     @CallToAction(
-                url: "https://www.apple.com/accessibility/",
+                url: "https://support.apple.com/en-us/HT201370",
                 purpose: link, 
                 label: "General Knowledge")
 }

Sources/iOSAccessibilityHandbook/iOSAccessibilityHandbook.docc/Pages/Introduction/AccessibilityFeatures/VoiceControl/VoiceControl.md

@@ -14,7 +14,7 @@ Use your **voice** to operate iOS
                source: "vc-card", 
                alt: "")
     @CallToAction(
-                url: "https://www.apple.com/accessibility/",
+                url: "https://support.apple.com/en-us/HT210417",
                 purpose: link, 
                 label: "General Knowledge")
 }

Sources/iOSAccessibilityHandbook/iOSAccessibilityHandbook.docc/Pages/Introduction/AccessibilityFeatures/VoiceOver/VoiceOver.md

@@ -18,7 +18,7 @@ A **screen reader** native for iOS
                source: "vo-card", 
                alt: "")
     @CallToAction(
-                url: "https://www.apple.com/accessibility/",
+                url: "https://www.apple.com/accessibility/voiceover/",
                 purpose: link, 
                 label: "General Knowledge")
 }
@@ -50,12 +50,6 @@ Not being able to perceive information **visually** is the hugest obstacle on th
 
 @Image(source: ninety-percent, alt: "")
 
-### Featured
-@Links(visualStyle: detailedGrid) {
-    - <doc:InterfacePerception>
-    - <doc:InterfaceInteractions>
-}
-
 Thanks to the natural order of things **information is formless** and humans have other senses to receive it. Thus screen readers transform the graphic interface into an audial or tactile form. 
 
 @Row {

Sources/iOSAccessibilityHandbook/iOSAccessibilityHandbook.docc/Pages/Introduction/Theory/Accessibility/a11yTerminology.md

@@ -1,6 +1,6 @@
 # Accessibility Terminology
 
-Digital accessibility crash course
+**Digital accessibility** crash course
 
 @Metadata {
     @PageColor(blue)
@@ -22,29 +22,35 @@ Digital accessibility crash course
 
 ## What is accessibility 
 
-**Accessibility** is a property of *things* that measures its **approachability**. Most *commonly *the term is used to refer to those qualities of objects that make them **accessible** for people with **special needs**, for example, **people with disabilities** or **users of assistive technology**.
+**Accessibility** is a property of *things* that measures its **approachability**. Most *commonly* the term is used to refer to those qualities of objects that make them **accessible** for people with **special needs**, for example, **people with disabilities** or **users of assistive technology**.
 
 ### People with disabilities
+@Image(source: microsoft-people, alt: "")
 **Disability** as a term is defined in relation to its **model**. Regardless of the focus of the model -- whether it is more *medical* or *social* -- disability is the reason of **diversity** of people's abilities in **communicating with environment**.
 
 ### Environment
 Environment is *everything* around a person. In perspective of **this book**, we're going to deal with a specific type of environment: **user interfaces**. 
 
 ### User interface
+@Image(source: user-interface, alt: "")
 User interface is everything that happens between a machine and the person using it. The communication happening between these two subjects, which is essentially an exchange of information, consists of providing output and receiving input. 
 
 ### Input and output
+@Image(source: input-output, alt: "")
 People provide input by interacting with the interface and receive output by perceiving the interface. Consequently, a user interface contains elements of informative (which has to be perceived), interactive (which has to be interacted with) and combined nature.
 
 ### Disability
+@Image(source: disabilities, alt: "")
 Disabilities is something that affects the way users perceive or interact with user interfaces. 
 
 ### Users of assistive technology
+@Image(source: assistive-technology, alt: "")
 To enable people with disabilities use interfaces assistive technology is used. Assistive technology are those technological solutions that are aimed to ease the life of people by providing an equitable access to the life activities. 
 
 For example, hearing aids is a technology that helps people who have hearing impairments to hear better.
 
 ### Equity vs. equality
+@Image(source: equality-equity, alt: "")
 Notice that the word **equitable** is used instead of *equal*. It is done because demanding equal access is *delusional*: there is no equation between people. Every single person is different and have their own experience of being. 
 
 ### Inclusion
@@ -63,17 +69,19 @@ Supporting accessibility is an engine of people with disabilities inclusion. If
 Accessibility is an aspect of inclusive design and its adoption affects the general usability of products. The more accessible the product is for minor parts of its audience, the more comfortable the user experience will be for everyone. There is no inclusivity without accessibility.
 
 ### Business profit
+@Image(source: dodo-stats, alt: "")
 Moreover, accessibility of products directly benefits the business. By increasing approachability of the products their producer expands the audience (which increases profit) and provides better customer experience (which also increases profit). 
 
 Just take a look at the studies showing that people tend to trust companies who adopt accessibility by 10% more than those who don't.
 
 ### Lawsuits safety
+@Image(source: lawsuits-stats, alt: "")
 Even if your organisation doesn't care about accessibility, there is a chance that your government does. Sooner or later the business will be hit with a lawsuit that will make you consider accessibility unless the further loss of money and reputation is desired.
 
+
 ### Humanitarian intention
 But most importantly, supporting accessibility is just a good thing to do. It is natural for any society to protect its members, and being a member of humanity requires you to advocate for diversity of your kind -- to make better future. And have better presence, already now.
 
-
 We've just covered the key terminology of the book's subject: accessibility. 
 
 iOS Accessibility Handbook is an educational resource dedicated to help people responsible of iOS applications to integrate accessibility into their products. 
@@ -89,9 +97,11 @@ There is no accessibility bible. Humanitarian sciences research the diversity of
 But there are globally recognised guidelines that are of help to structure your work on accessibility.
 
 ### Human Interface Guidelines
+@Image(source: hig, alt: "")
 First of all, there is Human Interface Guidelines. As a person related to iOS applications development, you might have already heard of this name. Human Interface Guidelines is a collection of knowledge aimed to guide people create products for Apple platforms with according to the company's values experience. (Apple is about inclusion, we've figured it out in the [**iOS Accessibility**](<doc:iOSAccessibility>) article article.)
 
 ### WCAG (Web Content Accessibility Guidelines)
+@Image(source: wcag, alt: "")
 The keystone of digital accessibility. W3C (World Wide Web Consortium) and WAI (Web Accessibility Initiative) have been putting joint and unmeasurable efforts into international standardising of accessibility guidelines. There are the most researched and respected practices. 
 
 ### -- W is for Web. We're talking Mobile.
@@ -102,7 +112,18 @@ For example, iOS devices have the touchscreen. Every single one of them and from
 So we are talking mobile. We just greatly respect and recognise work of W3C. And not only us: people who are going to suit you in case when being unaccessible is illegal in your country are going to look at WCAG too. If there might be an accessibility bible WCAG is its draft.
 
 ### Inclusive Design Principles, Inclusive Components
+@Image(source: heydon-works, alt: "")
 Two resources talking about accessibility in light of inclusive design. Designing inclusively inevitably produces accessible products. Design with accessibility in mind and you won't ever need to refer to accessibility as to something extrinsic, and, therefore, requiring additional efforts. Shout out to Heydon Pickering. 
+@Image(source: inclusive-design-posters, alt: "")
+
+### Microsoft Inclusive Design
+@Image(source: microsoft-inclusion, alt: "")
+
+### Apple Developer Resources
+@Image(source: apple-developer, alt: "")
+
+### Apple Accessibility Support
+@Image(source: apple-support, alt: "")
 
 ## Directions 
 Now go learn and practice. [**Table of contents**](<doc:AdoptionGuide>) is at your service.

Sources/iOSAccessibilityHandbook/iOSAccessibilityHandbook.docc/Pages/Introduction/Theory/iOS Accessibility/AccessibilityInCode.md → Sources/iOSAccessibilityHandbook/iOSAccessibilityHandbook.docc/Pages/Introduction/Theory/AccessibilityInCode.md

@@ -51,12 +51,15 @@ A **user interface** is a part of this program: regardless of where and how the
 Talking about iOS, there are two **frameworks** purposed to build **user interfaces** for iOS applications: **UIKit** and **SwiftUI**. 
 
 ### UIKit
+@Image(source: uikit, alt: "")
 **UIKit** is a classic UI framework that has been there for ages. Written on **Objective-C** (predecessor of **Swift**), imperative, clumsy, and, most importantly, widely recognised. Which means it is researched in **great detail** and has tons of **documentation** of drastically different **interfacial solutions**.
 
 ### SwiftUI
+@Image(source: swiftui, alt: "")
 On the other hand, **SwiftUI** is a *relatively* new product of Apple, introduced in 2019. Written on **Swift**, declarative, human-readable and elegant. Not as well-documented as the former one, but **it doesn't mean that SwiftUI doesn't solve the same problems**.
 
 ### Frameworks dichotomy
+@Image(source: dichotomy, alt: "")
 Even though Apple transfers all their **system interfaces** to SwiftUI day by day, the amount of applications written with UIKit is **prevailing**. Moreover, UIKit's life is not to be stopped in the observable future, so, we have to discuss interfaces built with **both SwiftUI and UIKit**. 
 
 @Image(source: placeholder-image, alt: "")

Sources/iOSAccessibilityHandbook/iOSAccessibilityHandbook.docc/Pages/Introduction/Theory/iOS Accessibility/iOSAccessibility.md

@@ -32,29 +32,29 @@ There are many reasons why one would want to *include* more people — from stra
 
 ## Computer accessibility
 **Computer accessibility**, often referred to as **a11y**, includes a wide range of solutions that are aimed to enhance **approachability of digital products**. It can be done by using **assistive technology**, which is specialised *software* or *hardware*, or a *combination* of both.
-@Image(source: a11y, alt: "A schematic explanation of the word ally being a numeronym: a + ccessibility (which is eleven letters) + y") {
+@Image(source: numeronym, alt: "A schematic explanation of the word ally being a numeronym: a + ccessibility (which is eleven letters) + y") {
     **a11y** is a [**numeronym**](https://en.wikipedia.org/wiki/Numeronym) of **accessibility**
 }
 
 ## Accessibility of iOS
-In the course of the book we are going to discuss **how to make iOS applications accessible**. Due to the current state of technological advancement the task may be narrowed to *adapting* your programs to the use of **assistive technology**, which involves nothing more than following [**specific design guidelines**](<doc:AccessibleDesign>) that support the usage of [**Accessibility Features**](<doc:AccessibilityFeatures>) and promote **inclusivity**. 
+In the course of the book we are going to discuss **how to make iOS applications accessible**. Due to the current state of technological advancement the task may be narrowed to *adapting* your programs to the use of **assistive technology**, which involves nothing more than following [**specific design guidelines**](<doc:InclusiveDesign>) that support the usage of [**Accessibility Features**](<doc:AccessibilityFeatures>) and promote **inclusivity**. 
 
-@Image(source: ios-a11y, alt: "A decorative image showing a smartphone symbol plus accessibility symbol") 
+@Image(source: ios-accessibility, alt: "A decorative image showing a smartphone symbol plus accessibility symbol") 
 
 
 ### History of iOS Accessibility
 [**"A Timeline of iOS Accessibility: It Started with 36 Seconds"**](https://www.macstories.net/stories/a-timeline-of-ios-accessibility-it-started-with-36-seconds/) is a marvellous research done by **Shelly Brisbin** that covers the **path** Apple has been following to make their devices accessible from the very beginning of iPhone story. 
-@Image(source: 36-seconds, alt: "A screenshot of the article's web page")
+@Image(source: ios-history, alt: "A screenshot of the article's web page")
 
 ### Current state
 From June 8, 2009 Apple hasn't stopped for a second in promotion of **inclusive design**. [**Inclusivity**](https://www.apple.com/diversity/) is one of the *core values* the company has been always exposing and [**accessibility**](https://www.apple.com/accessibility/) is an immanent part of it. 
 
 Aiming to make their products as *accessible* so everyone could use it led Apple to unmeasurable efforts put to [**assistive technology**](<doc:AccessibilityFeatures>) support. 
 
-@Image(source: dei-grid, alt: "")
+@Image(source: inclusion-grid, alt: "")
 
 ## Accessibility Features
-As for today, here is the list of some [**Accessible Features**](<doc:AccessibilityFeatures>) **available on iOS**. Its amount is continually increasing year by year. The stack is considered to be one of the most efficient *system* solutions of **assistive technology integration**, which provides sufficient **tools** for presenting **accessible interfaces** in accordance with modern [**accessibility guidelines**](<doc:AccessibilityStandards>).
+As for today, here is the list of some [**Accessible Features**](<doc:AccessibilityFeatures>) **available on iOS**. Its amount is continually increasing year by year. The stack is considered to be one of the most efficient *system* solutions of **assistive technology integration**, which provides sufficient **tools** for presenting **accessible interfaces** in accordance with modern [**accessibility guidelines**](<doc:Standards>).
 @Image(source: features-list, alt: "A large text Keynote slide listing Accessibility Features: Dynamic Type, VoiceOver, Zoom, Spoken Content features, Reduce Transparency, Switch Control, Reduce Motion, On and Off labels, AssistiveTouch, Full keyboard access, Voice Control, Bold Text, Pointer Control, Sound Recognition, Guided Access, Dwell Control, Type to Siri, Sound Actions, Button Shapes, Color Filters, Increase Contrast, Hearing Aids")
 
 ### Field research
@@ -82,10 +82,9 @@ To know more about *key features* -- those of our professional (as app creators)
 ## Wrap-up
 So, here we are. We came to the point where stating the **purpose of this book** is possible. 
 
- [**iOS Accessibility Handbook**](https://vodgroup.github.io/AccessibilityDocumentation/documentation/iosaccessibilityhandbook) is a collection of *guidelines* of how to create **iOS applications** that support [**Accessible Features**](<doc:AccessibilityFeatures>) and promote [**inclusive design**](<doc:AccessibleDesign>). 
-@Image(source: human-interface-guidelines, alt: "A screenshot of Apple's Human Interface Guidelines web page")
+ [**iOS Accessibility Handbook**](https://vodgroup.github.io/AccessibilityDocumentation/documentation/iosaccessibilityhandbook) is a collection of *guidelines* of how to create **iOS applications** that support [**Accessible Features**](<doc:AccessibilityFeatures>) and promote [**inclusive design**](<doc:InclusiveDesign>). 
+@Image(source: hig, alt: "A screenshot of Apple's Human Interface Guidelines web page")
 
 To dive right into the process of **developing accessible applications** don't hesitate to open the [**iOS Accessibility Guide**](https://vodgroup.github.io/AccessibilityDocumentation/tutorials/adaptionstrategy) map. *Everything* is there, you won't be left unprepared.
-@Image(source: roadmap, alt: "A screenshot of the guide's map")
 
 ## Have fun!

Sources/iOSAccessibilityHandbook/iOSAccessibilityHandbook.docc/Pages/iOSAccessibilityHandbook.md

@@ -26,7 +26,7 @@ Make your iOS applications **accessible**
 
 ## Welcome to iOS Accessibility Handbook
 
-[**iOS Accessibility Handbook**](<doc:iOSAccessibilityHandbook>) is an open-source **educational project** about making iOS applications *accessible*. **Accessible application** is such application that works with various *assistive technologies*, such as [**VoiceOver**](https://www.apple.com/accessibility/voiceover), [**Voice Control**](https://support.apple.com/en-us/HT210417) and [**Switch Control**](https://support.apple.com/en-us/HT201370), which enable **people with disabilities** to use the application. 
+[**iOS Accessibility Handbook**](<doc:iOSAccessibilityHandbook>) is an open-source **educational project** about making iOS applications *accessible*. **Accessible application** is such application that works with various *assistive technologies*, such as [**VoiceOver**](<doc:VoiceOver>), [**Voice Control**](<doc:VoiceControl>) and [**Switch Control**](<doc:SwitchControl>), which enable **people with disabilities** to use the application. 
 @Image(source: features-1, alt: "")
 @Image(source: features-2, alt: "")