From e0ab74f20b7b1c839328870f60796b376aa40a13 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E2=9C=8C=EF=B8=8F=28=C2=B4=E3=83=AE=60=29?= Date: Sat, 27 Jan 2024 15:03:08 +0300 Subject: [PATCH] Update README.md --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index ee09593..411a785 100644 --- a/README.md +++ b/README.md @@ -8,8 +8,12 @@ Generally the project is dedicated to those who use the mentioned *toolkit* in t ## — How is it supposed to work? Currently our goal is to try out variable methods of documentation wrapping by implementing various **interactive solutions**, such as **step-by-step guides**, wide range of **media types** used and **[VoiceOver Designer](https://github.com/VODGroup/VoiceOverDesigner)** app prototype integration in order to find the most efficient *educational models*. +Screenshot 2024-01-27 at 11 38 37 (2) + The *interactivity* is implemented by heavy relying on **[DocC](https://developer.apple.com/documentation/docc), which is a native rich documentation solution for [Swift projects](https://www.swift.org/packages)**. It uses **[Markdown](https://apple.github.io/swift-markdown/documentation/markdown)** as its *formatting language*. +Screenshot 2024-01-27 at 11 47 07 + Since it is only a *prototype*, having the resource hosted by **[GitHub Pages](https://pages.github.com)** seems to us a great option **to allow anyone to contribute to the project**. **GitHub Pages simply turns a GitHub repository into a *website*, which plays along *open-source development* fittingly**. @@ -23,6 +27,7 @@ To focus on the implementation of assistive technologies. - **Real-life cases** in screens and scenarios involving usage of *assistive technologies*. - **Step-by-step guides** how to apply **Accessibility Features**. + ### Articles To study the concepts. - Accessibility Properties in Code: How to Use Them. A brief overview of **implenting accessibility in apps**.