Compare commits
2 Commits
29640a2fc9
...
6526d3fdad
| Author | SHA1 | Date |
|---|---|---|
 E.L. Guerrero
|
6526d3fdad
|
|
|
E.L. Guerrero
|
ac43ba4122
|
|
|
@ -4,11 +4,7 @@ tags:
|
|||
- meta
|
||||
draft: true
|
||||
created: 2024-07-09, 18:47
|
||||
updated: 2024-07-09 19:47
|
||||
updated: 2024-08-09 15:39
|
||||
---
|
||||
# Colophon
|
||||
This is an Obsidian vault running some templating plugins and enhancements.
|
||||
|
||||
## Plugins
|
||||
- Templater
|
||||
- Dataview
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ tags:
|
|||
- meta
|
||||
draft: true
|
||||
created: 2024-07-09, 18:45
|
||||
updated: 2024-07-09 20:17
|
||||
updated: 2024-08-09 13:40
|
||||
---
|
||||
# Index
|
||||
|
||||
|
|
@ -20,5 +20,11 @@ updated: 2024-07-09 20:17
|
|||
### 1.6 Templates
|
||||
## 2 Week 0
|
||||
### 2.1 Outline
|
||||
### 2.2 Prerequisites
|
||||
## README
|
||||
|
||||
## 3 Week 1
|
||||
### 3.1 WAS Body of Knowledge
|
||||
### 3.2 WAS Certification Exam 2024
|
||||
### 3.3 WAS Credential Content Outline
|
||||
### 3.4 WAS Prerequisites
|
||||
|
||||
## 4 README
|
||||
|
|
|
|||
|
|
@ -1,9 +1,10 @@
|
|||
- 2024-07-09 at 20h18 · [[README]]
|
||||
- 2024-07-09 at 20h17 · [[Index]]
|
||||
- 2024-07-09 at 19h47 · [[Colophon]]
|
||||
- 2024-07-09 at 19h45 · [[Prerequisites]]
|
||||
- 2024-08-09 at 15h39 · [[Colophon]]
|
||||
- 2024-08-09 at 15h38 · [[WAS Prerequisites]]
|
||||
- 2024-08-09 at 15h38 · [[WAS Credential Content Outline]]
|
||||
- 2024-08-09 at 15h38 · [[README]]
|
||||
- 2024-08-09 at 14h40 · [[Outline]]
|
||||
- 2024-08-09 at 14h00 · [[WAS Body of Knowledge Document]]
|
||||
- 2024-08-09 at 13h40 · [[Index]]
|
||||
- 2024-07-09 at 19h31 · [[Base]]
|
||||
- 2024-07-09 at 19h28 · [[Outline]]
|
||||
- 2024-07-09 at 18h48 · [[Glossary]]
|
||||
- 2024-07-09 at 18h44 · [[Code Block]]
|
||||
- 2024-07-09 at 18h44 · [[Citation]]
|
||||
|
|
|
|||
10
README.md
10
README.md
|
|
@ -4,10 +4,15 @@ tags:
|
|||
- meta
|
||||
draft: false
|
||||
created: 2024-07-09 16:24
|
||||
updated: 2024-07-09 20:18
|
||||
updated: 2024-08-09 15:38
|
||||
---
|
||||
# a11y-study
|
||||
Following [Africa Kenyah](https://github.com/codingtherapist)’s [webAccessibilityStudyGroup](https://github.com/codingtherapist/webAccessibilityStudyGroup), this is a way for me to document as I learn about Digital Accessibility.
|
||||
|
||||
## About
|
||||
Following [Africa Kenyah](https://github.com/codingtherapist)’s [webAccessibilityStudyGroup](https://github.com/codingtherapist/webAccessibilityStudyGroup), this is a way for me to document as I learn about Digital Accessibility as well as a prep for the [IAAP Web Accessibility Specialist (WAS) Certification](https://www.accessibilityassociation.org/s/wascertification).
|
||||
|
||||
## Changelog
|
||||
**09 AUG 2024**: The next [WAS Certification Exam](https://www.accessibilityassociation.org/s/certification-apply) is on 13 November - 4 December, and applications close 20 November (17:00 EDT).
|
||||
|
||||
## Acknowledgements
|
||||
- [Alex Tait](https://www.atfreshsolutions.com/)
|
||||
|
|
@ -21,4 +26,5 @@ PGP: 4C24 AB6C DA78 B89E 2F9E 0E31 DF38 8059 7F55 9E10
|
|||
|
||||
## Licence
|
||||
Copyright © 2024 E.L. Guerrero.
|
||||
|
||||
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation Licence, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation Licence”.
|
||||
|
|
|
|||
|
|
@ -1,9 +1,10 @@
|
|||
---
|
||||
title: Outline
|
||||
tags:
|
||||
draft: true
|
||||
tags:
|
||||
- meta
|
||||
draft: false
|
||||
created: 2024-07-09, 18:47
|
||||
updated: 2024-07-09 19:28
|
||||
updated: 2024-08-09 14:40
|
||||
---
|
||||
# Outline
|
||||
|
||||
|
|
@ -16,8 +17,9 @@ updated: 2024-07-09 19:28
|
|||
#### 1.2.2 Accessibility Axioms
|
||||
#### 1.2.3 Accessibility, Usability, Inclusion
|
||||
### 1.3 Digital Accessibility
|
||||
#### 1.3.1 Components
|
||||
#### 1.3.1 Componentsw
|
||||
##### 1.3.1.1 Assistive Technology
|
||||
###### 1.3.1.1.1 How do disabled people use digital products?
|
||||
##### 1.3.1.2 User Agents
|
||||
##### 1.3.1.3 Design and Development
|
||||
##### 1.3.1.4 Authoring Tools
|
||||
|
|
@ -68,7 +70,7 @@ updated: 2024-07-09 19:28
|
|||
### 4.4 QA Testing and Frameworks
|
||||
## 5 Content
|
||||
### 5.1 Authoring Content
|
||||
#### 5.1.1 Plain English
|
||||
#### 5.1.1 Plain Language
|
||||
#### 5.1.2 Text Hierarchy
|
||||
#### 5.1.3 Accessibility Statements
|
||||
### 5.2 Alternative Text, Captions, and Descriptions
|
||||
|
|
|
|||
|
|
@ -1,8 +0,0 @@
|
|||
---
|
||||
title: Prerequisites
|
||||
tags:
|
||||
draft: true
|
||||
created: 2024-07-09, 18:48
|
||||
updated: 2024-07-09 19:45
|
||||
---
|
||||
# Prerequisites
|
||||
|
|
@ -0,0 +1,120 @@
|
|||
---
|
||||
title: WAS Body of Knowledge Document
|
||||
tags:
|
||||
- iaap
|
||||
- was
|
||||
draft: true
|
||||
created: 2024-08-09, 12:22
|
||||
updated: 2024-08-09 14:00
|
||||
---
|
||||
# WAS Body of Knowledge Document
|
||||
|
||||
|
||||
## 1 Creating Accessible Content
|
||||
### 1.1 Understand and interpret accessibility specifications and techniques
|
||||
#### 1.1.1. Overview
|
||||
|
||||
#### 1.1.2. The W3C
|
||||
|
||||
#### 1.1.3. Web Content Accessibility Guidelines (WCAG) 2.2
|
||||
|
||||
#### 1.1.4. W3C overview of the Web Content Accessibility Guidelines
|
||||
|
||||
#### 1.1.5. WCAG Versioning
|
||||
|
||||
#### 1.1.6. Accessible Rich Internet Applications (WAI-ARIA) 1.1
|
||||
|
||||
#### 1.1.7. Authoring Tool Accessibility Guidelines (ATAG) 2.0
|
||||
|
||||
#### 1.1.8. Normative versus non-normative documents
|
||||
|
||||
|
||||
### 1.2 Create accessible JavaScript, AJAX, and interactive content
|
||||
#### 1.2.1. Support for JavaScript in accessibility APIs and assistive technologies
|
||||
|
||||
#### 1.2.2. Study topics related to JavaScript, AJAX, and Interactive Content
|
||||
|
||||
|
||||
### 1.3 Integrate accessibility into the quality assurance process
|
||||
#### 1.3.1. Study topics related to accessibility quality assurance
|
||||
|
||||
|
||||
### 1.4 Choose well-supported accessibility techniques
|
||||
#### 1.4.1. Study topics related to accessibility support
|
||||
|
||||
|
||||
### 1.5 Create interactive controls/widgets (standard or custom) based on accessibility best practices
|
||||
#### 1.5.1. Study topics related to interactive controls/widgets
|
||||
|
||||
|
||||
### 1.6 Create accessible single-page applications (SPA)
|
||||
#### 1.6.1. Study topics related to single-page applications
|
||||
|
||||
|
||||
### 1.7 Create web content that is compatible with the strategies used by persons with disabilities to access web content
|
||||
#### 1.7.1. Vision
|
||||
|
||||
#### 1.7.2. Blind users
|
||||
|
||||
#### 1.7.3. Blind users with a touch screen
|
||||
|
||||
#### 1.7.4. Screen reader and browser combinations
|
||||
|
||||
#### 1.7.5. Recommended combinations to guarantee better compatibility
|
||||
|
||||
#### 1.7.6. Screen reader considerations
|
||||
|
||||
#### 1.7.7. Low vision users
|
||||
|
||||
#### 1.7.8. Reading
|
||||
|
||||
#### 1.7.9. Cognition
|
||||
|
||||
#### 1.7.10. Motor
|
||||
|
||||
#### 1.7.11. Hearing
|
||||
|
||||
|
||||
## 2 Identify accessibility issues/problems
|
||||
|
||||
### 2.1 Identify interoperability and compatibility issues
|
||||
#### 2.1.1. Study topics related to strategies used by people with disabilities
|
||||
|
||||
#### 2.1.2. Keyboard accessibility
|
||||
|
||||
#### 2.1.3. Touch device accessibility
|
||||
|
||||
|
||||
### 2.2 Determine conformance to accessibility specifications based on accessibility issues found
|
||||
#### 2.2.1. Identify the success criterion for every accessibility failure
|
||||
|
||||
#### 2.2.2. Differentiate between WCAG 2.0, WCAG 2.1
|
||||
|
||||
#### 2.2.3. Distinguish between failures (of success criteria) from optional best practices
|
||||
|
||||
#### 2.2.4. Study topics related to determining the level of conformance to accessibility specifications
|
||||
|
||||
|
||||
### 2.3 Test with assistive technologies
|
||||
#### 2.3.1. Study topics related to testing with assistive technologies
|
||||
|
||||
|
||||
### 2.4 Test for end-user impact
|
||||
#### 2.4.1. Study topics related to testing the end-user impact
|
||||
|
||||
|
||||
### 2.5 Use accessibility testing tools effectively
|
||||
#### 2.5.1. Automated Testing
|
||||
|
||||
#### 2.5.2. Manual Testing Tools
|
||||
|
||||
#### 2.5.3. Study topics related to accessibility testing tools
|
||||
|
||||
|
||||
## 3 Remediate (fix) accessibility issues
|
||||
|
||||
### 3.1 Prioritise accessibility issues based on level of severity
|
||||
#### 3.1.1. Study topics related to prioritizing accessibility issues based on the level of severity
|
||||
|
||||
### 3.2 Recommend strategies and/or techniques for fixing accessibility issues
|
||||
#### 3.2.1. Study topics related to recommending strategies and/or techniques for fixing accessibility issues
|
||||
|
|
@ -0,0 +1,41 @@
|
|||
---
|
||||
title: WAS Credential Content Outline
|
||||
tags:
|
||||
- iaap
|
||||
- was
|
||||
draft: true
|
||||
created: 2024-07-09, 18:48
|
||||
updated: 2024-08-09 15:38
|
||||
---
|
||||
# WAS Credential Content Outline
|
||||
|
||||
## 1 Creating Accessible Web Solutions (40%)
|
||||
**A.** Guidelines, principles and techniques for meeting success criteria (including WCAG 2.1, WAI-ARIA, ATAG, basic concepts, limitations of the specific guidelines, principles, and techniques, what is normative vs. non-normative; what is included in different levels (A, AA, AAA)).
|
||||
|
||||
**B.** Basic knowledge of programming (at a conceptual level; principles and concepts related to programming; impact of specific coding practices on web solutions vs. writing specific code).
|
||||
|
||||
**C.** Accessibility quality assurance (i.e., assuring the quality of accessibility throughout the development life cycle, difference and overlap between user experience and accessibility).
|
||||
|
||||
**D.** Accessibility supported technologies (including user's assistive technologies and accessibility features; combination of assistive technologies and users agent; design decisions in choosing technologies that support accessibility; e.g., not choosing Flash when something else has better accessibility support, differences in assistive technology supports and behaviors, differences in support for touch when screen reader is on vs. off).
|
||||
|
||||
**E.** Standard controls vs. custom controls (e.g., using standard controls when possible; if using custom controls build them using WAI-ARIA best practices).
|
||||
|
||||
**F.** Single page applications (e.g., focus control, delays for AJAX-Screen Reader compatibility, live announcements).
|
||||
|
||||
**G.** Strategies of persons with disabilities in using web solutions (e.g., navigation of screen reader users, headings and landmarks, coping strategies, user preferred methods vs. website specific methods, using keyboard vs. mouse).
|
||||
|
||||
## 2 Identify accessibility issues in web solutions (40%)
|
||||
**A.** Interoperability and compatibility issues.
|
||||
|
||||
**B.** Identifying guidelines and principles regarding issues (including WCAG 2.1, WAI-ARIA, ATAG, basic concepts, limitations of the specific guidelines, principles, and techniques, what is normative vs. non-normative; what is included in different levels (A, AA, AAA)).
|
||||
|
||||
**C.** Testing with assistive technologies (e.g., navigation of screen reader users, headings and landmarks, screen magnifiers, high contrast, using keyboard vs. mouse).
|
||||
|
||||
**D.** Testing for end-user impact (e.g., low vision, cognitive, mobile/touch).
|
||||
|
||||
**E.** Testing tools for the web (both automated and manual tools, i.e., what they are and what are their limitations; e.g., unit testing, browser based tools, spider tools, bookmarklet, automated tools used to monitor site vs. external tools).
|
||||
|
||||
## 3 Remediating issues in web solutions (20%)
|
||||
**A.** Level of severity and prioritization of issues (e.g., cost benefit; legal risk, user impact, what is the problem, what to focus on first).
|
||||
|
||||
**B.** Recommending strategies and/or techniques for fixing issues (i.e., best solution, solution that most widely useful, feasibility of solution, fixing vs. redesign, how to fix it).
|
||||
|
|
@ -0,0 +1,27 @@
|
|||
---
|
||||
title: WAS Prerequisites
|
||||
tags:
|
||||
- iaap
|
||||
- was
|
||||
draft: true
|
||||
created: 2024-08-09, 12:43
|
||||
updated: 2024-08-09 15:38
|
||||
---
|
||||
# WAS Prerequisites
|
||||
Hands-on experience and knowledge of programmatic code elements, WCAG 2.1 standards, and contextual implications for end users of assistive technology are all required.
|
||||
|
||||
Minimally qualified WAS Candidates should have documented roles and responsibilities as first-person experience for the job tasks listed in the WAS Content Outline, WAS Body of Knowledge, and this high level of responsibilities in 10 of the 13 following areas:
|
||||
|
||||
- HTML code. This does not mean writing HTML code.
|
||||
- JavaScript. This does not mean writing JavaScript code.
|
||||
- Accessibility/usability testing in iOS environments.
|
||||
- Accessibility/usability testing in Android environments.
|
||||
- Accessibility/usability testing in Windows environments.
|
||||
- Accessibility/usability testing with multiple forms of assistive technology.
|
||||
- Familiarity and experience with browser specific assistive technologies.
|
||||
- ARIA and its proper use.
|
||||
- ATAG, understanding the importance of.
|
||||
- Understanding and implementation of WCAG 2.1 Standards.
|
||||
- Understanding and implementation of accessibility best practices.
|
||||
- Web accessibility auditing and remediation.
|
||||
- Understanding the impacts of web accessibility on disabled people.
|
||||
Loading…
Reference in New Issue