Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create accessibility-knowledge-self-assessment.md #10

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Create accessibility-knowledge-self-assessment.md #10

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
abebae2
Create accessibility-knowledge-self-assessment.md
jenweber Aug 23, 2021
cafe928
Simplify wording
jenweber Aug 23, 2021
2d97756
More wording changes
jenweber Aug 23, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
50 changes: 50 additions & 0 deletions content/accessibility-knowledge-self-assessment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
---
title: Accessibility knowledge self-assessment
image:
imageMeta:
attribution:
attributionLink:
featured: true
authors:
- jen-weber
date: Mon Aug 23 2021 13:45:45 GMT-0400 (Eastern Daylight Time)
tags:
- new
---

Some web developers with a significant accessibility knowledge gap may not even realize it. This quick self-assessment includes topics that I consider to be basic accessibility knowledge - things that every front end developer should know and learn.

## Goals

The goal of this assessment is to help turn unknown-unknowns into _known_-unknowns. Whenever you identify that you have a learning gap, then you can do something about it! This is progress.

## The questions

1. What is a landmark element in HTML? Can you name some?
2. How many `main` elements can you use on a page?
3. What are two ways to associate a label with an input?
4. What does aria-hidden do?
5. When should you use `article` vs `section`?
6. What does `alt` on an image do, and why is it important? Should all images have an `alt`?
7. Is ok to put headings (like `h1`) out of order? If so, when?
8. What does it mean to say that an element is eligible to receive focus? Name some focusable and non focusable elements.
9. What are some CSS properties that would make an element invisible to a screen reader/assistive tech?
10. What are the three levels of WCAG success criteria? Can you give an example of something from each level?
11. How do you start up a screen reader on your computer?
12. How do you decide whether something should be a button or a link?

## The answers

Read through the answers to find out how you did! If you miss some of these questions, it's a sign that you could be missing a big part of what it takes to build apps that anyone can use, and should set aside time to learn ASAP.

TODO

## Next steps

TODO

## Do you have something to add?

I'd love to make this list longer. Please open a PR in the blog article repository, add your questions and answers, and include your username in the list.

**Contributors:** (no one yet)