Skip to content

Commit

Permalink
folders
Browse files Browse the repository at this point in the history
  • Loading branch information
crescentheaded committed Feb 24, 2024
1 parent c26494a commit cbff284
Show file tree
Hide file tree
Showing 47 changed files with 52 additions and 144 deletions.
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
@Tutorial(time: <#number#>) {
@Intro(title: "<#text#>") {
AvSpeechSynthesizer talk here.
@Tutorial(time: 10) {
@Intro(title: "How To Adapt Audial Content") {
An application may contain as many sounds as a person without hearing impairments can imagine. Sound notifications, reactions, background music, content with an audial channel - everything that plays a crucial role in perceiving a "sound" application may be neglected. If not by a hearing impairment, then by an assistive technology that adds more information to the auidial layer. So let's see how to make sounds accessible for everyone.

@Image(source: <#file#>, alt: "<#accessible description#>")
}

Expand Down
Original file line number Diff line number Diff line change
@@ -1,11 +1,6 @@
@Tutorial(time: 15) {

@Comment {
https://meryl.net/captioned-videos-complete-guide/
}

@Intro(title: "Visual Content Captioning") {
<#text#>
@Intro(title: "Writing Accessible Texts") {
Even though there is no problem for screen readers to speak textual information there are a few moments one should consider to make reading comfortable for everyone. Text layout, fonts used, proper language - let's discuss everything that may become an obstacle for a user.

@Image(source: <#file#>, alt: "<#accessible description#>")
}
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
@Tutorial(time: 15) {

@Comment {
https://meryl.net/captioned-videos-complete-guide/
}

@Intro(title: "Visual Content Captioning") {
Not only functional images such as interface controls require textual description. Images that are purely decorative are also inaccessible for people who have no ability to see them. So let's dive into the art of translating visual experience and allow everyone to enjoy pictures, animations and videos in your app.

@Image(source: <#file#>, alt: "<#accessible description#>")
}

@Section(title: "<#text#>") {
@ContentAndMedia {
<#text#>

@Image(source: <#file#>, alt: "<#accessible description#>")
}

@Steps {
@Step {
<#text#>

@Image(source: <#file#>, alt: "<#accessible description#>")
}
}
}
}

This file was deleted.

This file was deleted.

This file was deleted.

Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
@Tutorial(time: 15) {

@Intro(title: "Elements Described For Assistive Technology") {
@Intro(title: "Interface Described For Assistive Technology") {
In this tutorial we're going to discuss unquestionably the most important thing to make an interface accessible — properly **describe its elements** for both users and assistive technology.

## What elements are considered accessible?
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -30,4 +30,6 @@ Overview
### Motor
### Cognitive

## Grid

## To roadmap
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
@Tutorial(time: <#number#>) {
@Intro(title: "<#text#>") {
@Tutorial(time: 20) {
@Intro(title: "Setting Up Guided Access") {
<#text#>

@Image(source: <#file#>, alt: "<#accessible description#>")
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
@Tutorial(time: 10) {
@Intro(title: "🔒 I Want Accessibility To Be Considered") {
@Intro(title: "Making The World Accessible") {

}

Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
@Tutorial(time: <#number#>) {
@Intro(title: "<#text#>") {
@Tutorial(time: 10) {
@Intro(title: "Controlling Accessibility With Accessibility Tree") {
<#text#>

@Image(source: <#file#>, alt: "<#accessible description#>")
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
# Accessible Design Guidelines

Talking about iOS applications development support of Accessibility Features is not something extrinsic that comes from adaption but an immanent part of universal design. Building apps using UI frameworks natively suggests accessibility. Default structures used to build interfaces often include sufficient solutions for the elements to be accessible without developers intervention. But even if there is additional work on accessibility being done it something isn't enough for the application to be truly accessible.

In this tutorial we're going to cover some of the aspects of apps design that are essential to be considered if you want your product to be accessible.

This file was deleted.

This file was deleted.

Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
@Tutorial(time: 15) {
@Intro(title: "How To Describe Visual Content") {
Some guidelines here.
@Tutorial(time: 20) {
@Intro(title: "Accessible Mistakes Correction") {
FUCK time limits

@Image(source: <#file#>, alt: "<#accessible description#>")
}
Expand Down
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
@Tutorial(time: 20) {
@Tutorial(time: 15) {
@Intro(title: "🔒 VoiceOver Designer") {

}
Expand Down

This file was deleted.

Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
@Tutorial(time: 10) {
@Intro(title: "How To Adapt Audial Content") {
@Intro(title: "Inspect Accessibility Right In Xcode") {
<#text#>

@Image(source: <#file#>, alt: "<#accessible description#>")
Expand Down

0 comments on commit cbff284

Please sign in to comment.