– DRAFT –
Cognitive and Learning Disabilities Accessibility Task Force Teleconference

github editors process

<lisa> we need a google doc for longer chnges so we can make editoral changes easily pre github

<rashmi> https://docs.google.com/document/d/1K4tI9SV4lsDXzCdaEAXExeL3f061__Sy06lfGV9mLvY/edit#heading=h.qn1vctt0b01p

<rashmi> Proposed pattern and changes for Content-Usable version 3

<lisa> https://docs.google.com/document/d/1xnoNFwfjJZbfadFiU-qOW49n4-gODbd_4ff5UDyYFTM/edit?usp=sharing

<rashmi> Lisa creating a new google doc for collaborative work for GitHub editorial work for adding and editing content-usable

<rashmi> https://docs.google.com/document/d/18rqamyGgYF1DAUHLhsXmR20FtN9AQSaPc9zpFNN1xgM/edit#heading=h.527yvnol81gl

<rashmi> style guide Link above

<rashmi> We are discussing how different people/organization/cultures refer disability names

wcag coodination

Implied Meaning subgroup will meet during AG calls for month of July

https://docs.google.com/document/d/1P7fOyEPVlqf1aXuJY0SO9LeC-E7EZllg/edit#heading=h.gjdgxs

https://docs.google.com/document/d/1GL-jyZ7CuYb-fms_jTKEe1YTAUZAH0EXkU3yqbRg5f4/edit

AG looked at the 172 outcomes and are trying to group like outcomes into a single outcome

Chuck: We're trying to reduce the number of outcomes to a more manageable level

Let's brainstorm different names for Text and Wording subsections on "Clear language," "Clear meaning," and "Clear content"

Rain: Agree those names aren't very clear

Rain: Maybe we should take all three 3 subsections and do a card sort to resort them

Rain: Can they be consolidated?

Rain: It's hard to know why they're separated

Chuck: I can't answer why they're separated, but your suggestions are hugely appreciated and needed

https://docs.google.com/document/d/1JKJ32DK_A82ahsQ_k0RVPc-ZYpX5uuKtuGOLdo2OqyY/edit

<Chuck> +1

Suggest new subsection that focuses on numerical concepts and numerical formatting

John R: In the number section, some people with dyscalculia don't understand "3" but they will understand "three"

John R: Actually I see it's addressed in the one about numerical concept

Outcome about ambiguous pronunciation: is it OK to nest that under "Text-to-speech"? Or does it need to go under broader category

Chuck: where else to put ambigious pronunciation?

<Chuck> no concerns with suggesting "Word comprehension" subsection

Julie proposal: New subsection called "Word comprehension" that includes common words, acronyms and abbreviations, and ambiguous pronunciation

Julie proposal: New proposal focused on sentence structure?

Rain will help Julie set up card-sorting exercise

<Chuck> Chair's are massive fans of asynchronous work :-)

Rain: Optimal sort is common tool

Rain: Is this group OK with attempting optimal sort approach? Or a slide deck with stickies?

Chuck: Alastair and Rachael have experience with these card-sorting tools

Rain will reach out to them so this group finds it easy to interact with

https://docs.google.com/document/d/1BA4s0xLhg6wrhaogHUBtAMQ9RspbivgNmvHgoOJSyL0/edit

<JohnRochford> https://www.w3.org/WAI/WCAG2/supplemental/patterns/o6p04-voice-menus/

Tiffany mentioned the gaming resource

Len: User Interaction - Games on the Web Roadmap (w3c.github.io)

Julie will send the COGA resources doc to full COGA list to get additional suggestions and will ask for a few minutes at Monday's meeting to review before sending to AG chairs

John R: I added some comments to the Implied Meaning draft