From f0518fbe99d30f2ef91fec6e8d4de097afa06d00 Mon Sep 17 00:00:00 2001 From: Knut Gravel <31062373+qutax@users.noreply.github.com> Date: Sat, 14 Sep 2024 15:44:41 +0200 Subject: [PATCH 1/3] Include identity-first language as good example MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit "The phrased “disabled people” is an example of identity-first language (in contrast to people-first language). It is the preferred terminology in Great Britain and by a number of U.S. disability activists." See also: https://ncdj.org/style-guide/#disabledpeople --- versioned_docs/version-2.0/accessibility/texts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-2.0/accessibility/texts.md b/versioned_docs/version-2.0/accessibility/texts.md index f5210b0c..750351aa 100644 --- a/versioned_docs/version-2.0/accessibility/texts.md +++ b/versioned_docs/version-2.0/accessibility/texts.md @@ -203,7 +203,7 @@ offline without losing important information. Print stylesheets can format conte The language we use should be respectful and inclusive. Using person-first language and avoiding outdated or offensive terms helps to create a more inclusive environment. -- **Good Example**: "Person with a disability" instead of "disabled person." +- **Good Example**: "Person with a disability" (people-first language) or "disabled person" (identity-first language). - **Bad Example**: "Handicapped" or other outdated terms. [Link to a disability language style guide](https://ncdj.org/style-guide/) From 6a4a1b59c6024daaeef674b2a8f166879edc2cfb Mon Sep 17 00:00:00 2001 From: Knut Gravel <31062373+qutax@users.noreply.github.com> Date: Sat, 14 Sep 2024 15:48:02 +0200 Subject: [PATCH 2/3] Add examples for accessibility-focused fonts --- versioned_docs/version-2.0/accessibility/texts.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/versioned_docs/version-2.0/accessibility/texts.md b/versioned_docs/version-2.0/accessibility/texts.md index 750351aa..395fadb1 100644 --- a/versioned_docs/version-2.0/accessibility/texts.md +++ b/versioned_docs/version-2.0/accessibility/texts.md @@ -45,6 +45,8 @@ The type of font used can significantly impact readability. Sans-serif fonts, su are generally easier to read on screens compared to serif fonts. Avoiding overly decorative fonts ensures the text is straightforward and readable. +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/)". + - **Good Example**: Using a Sans-serif font for body text. - **Bad Example**: Using a decorative font like Comic Sans or a complex script font for body text. From e45731fe2070005020ef70b0e306dcfba4ddc1da Mon Sep 17 00:00:00 2001 From: Knut Gravel <31062373+qutax@users.noreply.github.com> Date: Sat, 14 Sep 2024 15:54:25 +0200 Subject: [PATCH 3/3] Add hint about semantic HTML for abbreviations --- versioned_docs/version-2.0/accessibility/texts.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/versioned_docs/version-2.0/accessibility/texts.md b/versioned_docs/version-2.0/accessibility/texts.md index 395fadb1..41807681 100644 --- a/versioned_docs/version-2.0/accessibility/texts.md +++ b/versioned_docs/version-2.0/accessibility/texts.md @@ -143,6 +143,8 @@ those who may not be familiar with the terms. This practice aids comprehension a - **Good Example**: "HyperText Markup Language (HTML) is used to create web pages." - **Bad Example**: "HTML is used to create web pages." (without explaining HTML) +When working with HTML, semantic elements can also be used to describe abbreviations and their meaning, namely ``, potentially in combination with ``. See also [MDN Web Docs on defining an abbreviation](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/abbr#defining_an_abbreviation). + ## Reading Level ### Appropriate Reading Level