Draft #2: Our AAC handout

Colleagues:

With cc to E.A. Draffan, so I'm retaining our intro text ...

We've discussed preparing a simple brochure handout demonstrating how
different symbol sets can be used to express the same concept. We have
not discussed what text we will use to illustrate how multiple
symbol sets exist to say the same thing.

The concept is to print hundreds of cards to be handed out at
conventions, beginning with the upcoming W3C TPAC in Seville. We want to
illustrate to user agent developers that the very same text appears
differently when rendered by different AAC symbol sets. That has proven
a concept not easily grasped by many from words, so we want to
illustrate it graphically!

Below is an Draft #2 of the text we propose to present on both sides of
the card. One side will have Bliss representations, and we're
considering ARASAAC for the other side, if E.A. agrees that's a good
idea.


DRAFT DRAFT DRAFT

We must support Augmentative and alternative communication (AAC) in
various kinds of web content, for instance in nested media "Chapter"
marking because AAC users tend to rely heavily on media, not long blocks
of text. As a general rule, AAC users are unlikely to want "War and
Peace" expressed in their AAC symbol set of choice. Rather, they tend to
look for AAC support in media and in procedural content such as sets of
instructions, e.g. in recipes.
 
 <END DRAFT #2>

All comments and suggestions welcome!

Janina

-- 

Janina Sajka (she/her/hers)
Accessibility Consultant https://linkedin.com/in/jsajka

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Linux Foundation Fellow
https://www.linuxfoundation.org/board-of-directors-2/

Received on Monday, 24 July 2023 19:15:59 UTC