Skip to content

Commit 889dffe

Browse files
authored
Merge pull request #128 from qutax/feature/accessibility
feature/accessibility: Add additional examples & hints to accessible text subchapter
2 parents 6e41a56 + e45731f commit 889dffe

File tree

1 file changed

+5
-1
lines changed
  • versioned_docs/version-2.0/accessibility

1 file changed

+5
-1
lines changed

versioned_docs/version-2.0/accessibility/texts.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,8 @@ The type of font used can significantly impact readability. Sans-serif fonts, su
4545
are generally easier to read on screens compared to serif fonts. Avoiding overly decorative fonts ensures the text is
4646
straightforward and readable.
4747

48+
There are also fonts that are specifically designed with accessibility in mind, such as "[Atkinson Hyperlegible](https://brailleinstitute.org/freefont)" or "[OpenDyslexic](https://opendyslexic.org/)".
49+
4850
- **Good Example**: Using a Sans-serif font for body text.
4951
- **Bad Example**: Using a decorative font like Comic Sans or a complex script font for body text.
5052

@@ -141,6 +143,8 @@ those who may not be familiar with the terms. This practice aids comprehension a
141143
- **Good Example**: "HyperText Markup Language (HTML) is used to create web pages."
142144
- **Bad Example**: "HTML is used to create web pages." (without explaining HTML)
143145

146+
When working with <abbr title="HyperText Markup Language">HTML</abbr>, semantic elements can also be used to describe abbreviations and their meaning, namely `<abbr>`, potentially in combination with `<dfn>`. See also [MDN Web Docs on defining an abbreviation](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/abbr#defining_an_abbreviation).
147+
144148
## Reading Level
145149

146150
### Appropriate Reading Level
@@ -203,7 +207,7 @@ offline without losing important information. Print stylesheets can format conte
203207
The language we use should be respectful and inclusive. Using person-first language and avoiding outdated or offensive
204208
terms helps to create a more inclusive environment.
205209

206-
- **Good Example**: "Person with a disability" instead of "disabled person."
210+
- **Good Example**: "Person with a disability" (people-first language) or "disabled person" (identity-first language).
207211
- **Bad Example**: "Handicapped" or other outdated terms.
208212

209213
[Link to a disability language style guide](https://ncdj.org/style-guide/)

0 commit comments

Comments
 (0)