w3c / wai-people-use-web-videos

0 stars 5 forks source link

[Global] Deaf needs changing to D/deaf #233

Open jade-mc opened 2 years ago

jade-mc commented 2 years ago

To show the difference between communities.

jade-mc commented 2 years ago

This should be changed throughout the scripts. @nitedog are we going to have a final proof/edit? I haven't been commenting on typos as I go, and there are a few places where the structure might need a little tweaking, (for example, to cut down on the use of... for example!) Happy to re-live my proofing/editing days and take this on if needed.

nitedog commented 2 years ago

@shawna-slh what are the WAI conventions for writing:

shawna-slh commented 2 years ago

Unfortunately it’s not in the Style Guide, and not consistent throughout the site.

Proposal based on recent usage and discussions:

  1. Deaf. So far we have decided that it’s better not to have the complexity of “D/deaf”. Capitalized because more people feel more strongly about it being capitalized.
  2. hard-of-hearing. It’s easier for most people to 'parse' with hyphens. Better not to abbreviate it in almost all uses on the W3C site. If really need to abbreviate it because lots of repetitive use of the phrase in short space, then ‘hard-of-hearing (HoH)’ … ‘HoH’.
  3. deaf-blind (preferred), deaf-blindness (acceptable). e.g.: …user who is deaf-blind. Persona with deaf-blindness. Hyphenated deaf-blind easier to parse than deafblind not. Don't abbreviate DB.

I can open a separate issue on the Style Guide and invite comment.

jade-mc commented 2 years ago

For point 1, D/deaf represents two separate and distinct communities though? And only including one suggests we're ignoring the other...

bruce-usab commented 2 years ago

+1 for enumerated to plan for https://github.com/w3c/wai-website/issues/551

Fair observation that capital-d-Deaf and not-being-able-to-hear are significantly different groups of people. I do not agree that D/deaf captures that nuance, at least not in most settings. Is scene 4 public facing?

jade-mc commented 2 years ago

Isn't that exactly what D/deaf is intended to capture? This will be public facing in that it'll be in the captions and transcript.

bruce-usab commented 2 years ago

Isn't that exactly what D/deaf is intended to capture?

Yes, but it is a very esoteric convention. In most contexts, I think it would be more likely to cause confusion rather than showing the difference between communities.

shawna-slh commented 2 years ago

I do not agree that D/deaf captures that nuance, at least not in most settings. ... a very esoteric convention. In most contexts, I think it would be more likely to cause confusion rather than showing the difference between communities

+1

Additionally, we cover it in:

  1. https://deploy-preview-113--wai-people-use-web.netlify.app/people-use-web/user-stories-six/
  2. https://deploy-preview-113--wai-people-use-web.netlify.app/people-use-web/abilities-barriers-auditory/

straw-proposal: