diff --git a/Sources/iOSAccessibilityHandbook/iOSAccessibilityHandbook.docc/Pages/Introduction/Theory/Accessibility/a11yTerminology.md b/Sources/iOSAccessibilityHandbook/iOSAccessibilityHandbook.docc/Pages/Introduction/Theory/Accessibility/a11yTerminology.md index ca255a4..1702b43 100644 --- a/Sources/iOSAccessibilityHandbook/iOSAccessibilityHandbook.docc/Pages/Introduction/Theory/Accessibility/a11yTerminology.md +++ b/Sources/iOSAccessibilityHandbook/iOSAccessibilityHandbook.docc/Pages/Introduction/Theory/Accessibility/a11yTerminology.md @@ -20,150 +20,93 @@ } -## What is accessibility +## What is accessibility in general -**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** -- whether it is **possible** or not **to interact with the *thing*** for a user of **unknown abilities**. -### 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**. +## Unknown abilities -### 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**. +### Product target audience +Any product has a **target audience**. Nonetheless, those expectations are *excluding* in their nature -- designing for a *particular image* of a user neglects needs of users that **differ**. -### 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 mutual **providing output** and **receiving input**. +### Possible diverseness +**Product audience is essentially unknowable**. Unless there is an *explicit* task to exclude certain user groups, the **diversity** of potential users should be considered. -### 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** (those to be perceived), **interactive** (those to be interacted with) and **combined nature**. +### Diversity barriers +Every person has unique **capabilities** and **experience**. There are **conditions** that cause users encounter **barriers** using products designed without wider consideration. **Accessibility reduces these barriers.** -### Disability -@Image(source: disabilities, alt: "") -Disabilities are *personal conditions* that affect the way users **perceive** or **interact** with user interfaces. +## Digital accessibility in particular +Talking about barriers in **digital products**, they happen on the scope of **user interfaces**. A **user interface** is *everything* that happens between a **product** and its **user**, the *communication* between these two subjects. -### 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 -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. - -@Image(source: equality-equity, alt: "") - -**Every single person is different** and have their own experience of being that is built *not only* by their abilities and disabilities, but countless **receptive** and **processing** factors. - -### Inclusion -Accessibility is about **human rights** and being able to **access** products of civilisation. If you don't want to *exclude* certain people **intentionally**, you should embrace that everyone is **different** and **it is pointless to demand the same from the diverse**. +### Computer interfaces +User interfaces are essentially means of **informational exchange**: providing **input** and receiving **output**. -### People with special needs -Despite the compatibility of **people with disabilities needs** and **assistive technology solutions**, users of assistive technology *cannot* be defined as people with disabilities. +### Accessibility of user interfaces +To be accessible, a product has to provide **equitable access** for a user of being **able to perceive and control the interface**. It is possible to achieve by adopting **accessible design guidelines** and support of **assistive technology**. -**There is no requirement to have a disability to use assistive technology, as well as a person with a disability may not use any of assistive technology.** +## Accessible design +According to **WCAG** (**W**eb **C**ontent **A**ccessibility **G**uidelines), which is the **international standard** of digital accessibility, all accessibility requirements can be grouped into 4 categories: +- perceivable; +- operable; +- understandable; +- robust. -## Supporting accessibility -There may be many arguments *against* support of accessibility, from **insufficient production resources** to **explicit discrimination** of users of assistive technology. But unless there is an intention to *exclude* people with special needs, accessibility got a proven **beneficial potential**. +These are **principles of accessible design**. [**iOS Accessibility Handbook**]() respects, follows and is in agreement with **WCAG**, so will inspect each of them in detail later at the [**Accessible Design**]() page. -### Protecting diversity -Supporting accessibility is an **engine of people with disabilities inclusion**. If your organisational values include such concepts as **d**iversity, **e**quity or **i**nclusion (**DEI**), **accessibility cannot be omitted**. +## Assistive technology +But there are situations where *design means* are **not enough** for an interface to be accessible. Here comes **assistive technology**: software, hardware and combined solutions that *allow* users to be able to have **equitable interaction experience**. -### Inclusive design -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**. **Accessibility is a well-designed (and well-developed) interfaces exclusive**. +### Equity vs. equality +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, thus their **experiences are unique**. -### Business profit -@Image(source: dodo-stats, alt: "") { - Statistics of **visual accessibility settings** of [**Dodo Pizza**](https://dodobrands.io/post/dodopizza/) users in 24 June 2023 -- 24 October 2023 -} -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). +### Users of assistive technology +Most commonly, assistive technology is used by people for whom ***otherwise* user interfaces would be inaccessible**. -Just inspect [**the studies**](https://instituteforpr.org/voya-ipr-disability-report) showing that **people tend to trust companies who adopt accessibility** by 10% more than those who don't. +### -- ... most commonly? +Yep. **Assistive technology *are* for people with disabilities**. But there is no requirement to have a disability to use assistive technology. -### Lawsuits safety -@Image(source: lawsuits-stats, alt: "") -If your organisation doesn't care about accessibility, there is also a chance that your **government** does. Sooner or later the business will be hit with a **lawsuit** that is *supposed* make you consider accessibility unless the further loss of money and reputation is desired. -> Note: Yep, "supposed" because [**it doesn't work**](https://www.lflegal.com/2018/11/webaim-fear/). But as an *accessibility professional* you have to know that there are countries in which accessibility is a **civil right**. Visit Lainey Feingold's [**Global Law and Policy**](https://www.lflegal.com/global-law-and-policy/) overview page to learn more. +**Users of assistive technology** is the term we're going to use when discussing appropriate **technical implementation**. -### Humanitarian intention -But, most importantly, supporting accessibility is "the right thing to do" -- word-by-word quote from [**Apple's documentation**](https://developer.apple.com/library/archive/documentation/UserExperience/Conceptual/iPhoneAccessibility/Accessibility_on_iPhone/Accessibility_on_iPhone.html#//apple_ref/doc/uid/TP40008785-CH100-SW1). +## People with disabilities +Anyway, accessibility focuses on people with **disabilities**. Disability is an ambiguous term with a definition dependant on its **model**. -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 **change lives now**. +### Disability models +Regardless of whether it is [**medical**](jepa.ru), [**social**](jepa.ru), or [**something else**](jepa.ru), as *digital accessibility professionals* we will refer to a disability as to *something* that stands on the way between a **user with disability** and an interface **designed without proper consideration**. -## Wrap-up +### Human-machine interaction +We've already figured out that **barriers** belong to **interfacial space**, which are essentially just **inputs** and **outputs**. Therefore, to *enable* people use an interface **various *perceptional* and *controlling* cases should be considered**. -That was the **key terminology** of the book's subject -- **accessibility**. +### Perceiving interfaces +Humans perceive reality by a *sensory system* consistent of **visual**, **audial**, **olfactory** and **tactile** organs. User interfaces do not smell [yet], so we're only interested in **vision**, **hearing** and **touch** [so far]. -Now we are ready to proceed with [**iOS Accessibility Handbook**](https://vodgroup.github.io/AccessibilityDocumentation/documentation/iosaccessibilityhandbook), which is an **educational resource** dedicated to *help* people responsible of **iOS applications** to **integrate accessibility** into their products. +### Controlling computers +Analogously, humans **perform actions** to reality. Talking about **providing output** to computer interfaces, we use **cognitive processes**, **speaking** and **motor abilities**. -## What's ahead? +### Common disability categorisation +From now on, for structuring purposes we will *refer* to disabilities affecting **accessibility of an interface** by 4 groups: +- **vision disabilities** -- affect **visual perception**; +- **hearing disabilities** -- change the **ability to hear**; +- **cognitive disabilities** -- everything that happens on **brain-level**, both **processing** and **producing**; +- and **mobile (motor) disabilities** -- how people may or may not **use their movable body-parts**, from eyelids that blink to fingers that tap. -### Learn and practice -Integrating digital products with accessibility is a **complex** and **everlasting** job for *everyone* involved in the product processes. +## Disabling conditions -During the course we are going to research accessibility of iOS applications in both **fundamental** and **practical aspects**, so the course content sufficiently covers *everything* that one has to know to make iOS apps accessible. +In this dimension of existence being able to do something always requires **certain conditions**. These conditions can be affected by **physical state** of a person and their **circumstances**. -Moreover, the knowledge contained in this book is based on **universally good design practices**. Perceive the materials as *general* education on accessibility **applied to iOS apps in particular**. +### Situational, temporary and permanent disabilities +This way a disability may be caused by **congenital** (i.e. present from birth) or **obtained health features**, as well as being put into a **particular situation** that has nothing to do with health. -## Universally good practices -Unfortunately, **there is no accessibility bible**. Humanitarian sciences research the diversity of humanity, technological advancement brings up new ways to respect that, **continuously**. +### Different circumstances, same result +Holding a baby in one hand, then ordering a coffee and, in the end, having to hold both the baby and the coffee simultaneously makes a person with two hands as **motor disabled** as a person with no hands. -But there are **globally recognised guidelines** that are of help to *reason* your work on accessibility. +### Same result, different reasons +Same with driving a car. Focusing on the road makes a person **not less blind** than a... blind person. Wait, what? Hold on. -### Human Interface Guidelines -@Image(source: hig, alt: "") -First of all, there is [**Human Interface Guidelines**](https://developer.apple.com/design/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 accordance to the company's *vision***. +### Accessibility for everyone +No, that's right. Don't forget what we are talking about: **digital accessibility**. We don't need to know *why* a person cannot use their hands to use our apps. **We just enable them to do so.** -### Featured +## What's next @Links(visualStyle: detailedGrid) { - -} - -### WCAG (Web Content Accessibility Guidelines) -@Image(source: wcag, alt: "") -The *keystone* of digital accessibility. [**W3C (World Wide Web Consortium)**](https://www.w3.org) and [**WAI (Web Accessibility Initiative)**](https://www.w3.org/WAI/) have been putting joint and unmeasurable efforts into **international standardising of accessibility guidelines**. - -The document states **criteria necessary for digital products to be accessible**. - -### -- W is for Web. We're talking Mobile. -You're right, excuse me. [**WCAG2ICT**](https://www.w3.org/WAI/standards-guidelines/wcag/non-web-ict/) is the standard we're going to take after. The thing is that as far as a user interface of a *contemporary* kind, **it shares its everything on every platform**. There are just **few nuances** that has to be considered talking about a **particular platform**. - -For example, iOS devices have **touchscreens**. Every single one of them and from the very beginning of iOS history. Controlling a device with a touchscreen is a **different experience** than using a laptop or full-sized computer. **Having a touchscreen, as an immanent part of device design, inevitably affects the *design* of its operational system.** - -So yes, we *are* talking mobile. We just greatly **respect** and **recognise** work of WAI. **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 perspective of [**inclusive design**](). **Designing inclusively inevitably produces accessible products.** Design with **inclusion 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**](https://heydonworks.com). -@Image(source: inclusive-design-posters, alt: "") { - Series of printable posters attached to [**Inclusive Design Principles**](https://inclusivedesignprinciples.info) -} - -### Microsoft Inclusive Design -The fortress of **accessibility knowledge** acquired, applied and promoted by Microsoft. [**Inclusive 101**](https://inclusive.microsoft.design/tools-and-activities/Inclusive101Guidebook.pdf) is a *must*. -@Image(source: microsoft-inclusion, alt: "") - -### Apple Developer Resources -Obviously, we're going to research the official [**API documentation**](https://developer.apple.com/accessibility/) in order to *develop* accessibility. -@Image(source: apple-developer, alt: "") - - -### WWDC -But, most importantly, we're interested in **WWDC (World Wide Developers Conference) sessions** labeled with **Accessibility and inclusion** category. - -WWDC happens *annually*, in June, and its web resources suck. Download [**Apple Developer**](https://apps.apple.com/us/app/apple-developer/id640199958) app. Full *scripts* for each session are available. - -### Apple Accessibility Support -Here are some user guides and stories about [**Accessibility Features**](), which we are going to **thoroughly inspect** in order to be *fluent* with [**accessibility of iOS**](). -@Image(source: apple-support, alt: "") - -## Conclusion -Those were the **essential resources** we're going to refer to during the course. There are much more provenly great materials on **inclusion** and **accessibility**, but we're going to mention them locally to not overwhelm you at the start. **So far, have fun!** - -## Next step -@Links(visualStyle: detailedGrid) { - - + - }