W3C

- DRAFT -

Cognitive and Learning Disabilities Accessibility Task Force Teleconference

22 Apr 2024

Attendees

Present
janina, Eric_hind, julierawe, Jennie, Jeanne, JanMcSorley, DavidSwallow, tburtin, rashmi, JeanneEC, lisa, EA, JohnRochford, Chuck, kirkwood, Rachael, Becca_Monteleone, Frankie
Regrets
Chair
SV_MEETING_CHAIR
Scribe
Eric_hind

Contents


scribe+

Working meeting on literary reviews

<julierawe> https://github.com/w3c/wcag3/discussions/60#discussioncomment-9131447

julieawe: Quick note on discussion thread related to W3C discussions

<julierawe> Please consider thumbs-downing this proposal in Github: https://github.com/w3c/wcag3/discussions/60#discussioncomment-9131447

<julierawe> Votes need to be made today for this to be counted in tomorrow's AG meeting, thanks!

<Becca_Monteleone> https://docs.google.com/document/d/1wu0WYcvCpp-zIz2NzPk2AuTJOrzgh3T4sKQgzCa10ps/edit#heading=h.jhgeh79yam7t

Becca_Monteleone: Purpose of meeting today, walk through of strategies for literature reviews.
... Doc shared, Research plan draft outline. Will walk through steps one by one and share documentation around literature reviews
... Goal, clear picture of specific topics with up to date information.
... Literature review topic: via Search terms, criteria, sources.
... Most reputable source, peer-reviewed academic sources.

<Becca_Monteleone> https://libguides.mit.edu/c.php?g=175963&p=1158594

<Becca_Monteleone> https://docs.google.com/document/d/1B1vCqlU1IF5UmqxhJAy8Khdi-kRQNPalVX8f3lCMr7w/edit#heading=h.9j8rnhzb9sv8

Becca_Monteleone: Reviewed boolean operators as a way to get more usable, granular results in a research search. Provided examples of boolean searches in conversational interfaces issue paper; discussed brackets, wildcards, the relevant boolean operators, etc.
... Next step, search and research; recommend to use more than one database at a time (e.g. WorldCat, Google Scholar) with the same search terms.
... Some databases have more/better options for searching. WorldCat for example, has far more results than Google Scholar might on a given search.

<Becca_Monteleone> https://docs.google.com/spreadsheets/d/1Cu_qVP1WBz2TbsrAjLbbeb55RAlJmu9kfHamriL1Ocs/edit#gid=1686096268

Becca_Monteleone: Quick discussion about finding different terms in same language variations (e.g. American English, British English)

<Jennie> * Eric - I haven't tried this, but I also slip into Canadian spelling for things. I wonder if Google translate could be used? (half joking, but may work)

<Jennie> * Actually I am going to try Google translate now for my most used Canadian spellings.

Becca_Monteleone: From COGA-2 Literature review and update, reviewed the recommended literature recording format (via Sheet)

<Jennie> * Google translate, interestingly, does not distinguish between French from different regions, which impacts meaningful/vocabulary. One suggestion I read from a few years ago indicates you can change your browser language settings as one way to change language.

Becca_Monteleone: From conversation with julierawe, adding geographical information to the sheet

<Rachael> Here is the citation information from the W3C manual of style: https://www.w3.org/Guide/manual-of-style/#ref-section

<Becca_Monteleone> Search terms: https://docs.google.com/document/d/1wu0WYcvCpp-zIz2NzPk2AuTJOrzgh3T4sKQgzCa10ps/edit#heading=h.ndflr0g952rs

Jennie: We may want to support a glossary for search terms, especially when they may be unique to variations on the same language.

<kirkwood> I would add internationalization & localization

<Jennie> My suggestion is to add search terms in the section Lisa started - find it in the link Becca posted above. This can be used by people looking for variability in spelling of terms, or different terms.

Kirkwood: We may also want to have localization and internationalization variations to a glossary

<kirkwood> +1 Jennie “buddy system”

Jennie: How about a buddy system to help introduce those less familiar. Or a contact for help?
... And/Or making someone the main contact/partner for a document or section?

Becca_Monteleone: Suggestion, for a topic you're working on (or pick a paper) and try out some of the techniques we've discussed.

julierawe: Best way to address column K - pulling out some text from an abstract versus creating a few organic sentences?

Becca_Monteleone: Suggest creating a few sentences to ensure the context of someone who isn't working in that field, would be able to understand.

<Becca_Monteleone> https://docs.google.com/spreadsheets/d/1Cu_qVP1WBz2TbsrAjLbbeb55RAlJmu9kfHamriL1Ocs/edit#gid=1686096268

<Becca_Monteleone> Some resources on journal rankings: https://deakin.libguides.com/research-metrics/journal-ranking-list

<Becca_Monteleone> https://subjectguides.library.american.edu/c.php?g=175335&p=1154356

EA: Sometimes there are less well published/less credible articles but they are often very good, relevant articles. Something to keep in mind if the journal doesn't have a high rank.

Kirkwood: For a given source, should we have a specific category for NIH or related public health databases. Per discussion, we may find a place to mention this.

julierawe: For abstracts of interests, how do we indicate that some follow up to have article access found would be appreciated? Per Becca, yes, we should have an indicator.

EA: Perhaps some indicator to note that a given article has information of value that has been extracted, and follow up not needed.

Jennie: How do we indicate that research is in-progress, Becca to add indicator

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.200 (CVS log)
$Date: 2024/04/22 16:08:54 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision VERSION of 2020-12-31
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: janina, Eric_hind, julierawe, Jennie, Jeanne, JanMcSorley, DavidSwallow, tburtin, rashmi, JeanneEC, lisa, EA, JohnRochford, Chuck, kirkwood, Rachael, Becca_Monteleone, Frankie
Present: janina, Eric_hind, julierawe, Jennie, Jeanne, JanMcSorley, DavidSwallow, tburtin, rashmi, JeanneEC, lisa, EA, JohnRochford, Chuck, kirkwood, Rachael, Becca_Monteleone, Frankie
No ScribeNick specified.  Guessing ScribeNick: Eric_hind
Inferring Scribes: Eric_hind

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]
This is scribe.perl Revision VERSION of 2020-12-31 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Default Present: janina, Eric_hind, julierawe, Jennie, Jeanne, JanMcSorley, DavidSwallow, tburtin, rashmi, JeanneEC, lisa, EA, JohnRochford, Chuck, kirkwood, Rachael, Becca_Monteleone, Frankie Present: janina, Eric_hind, julierawe, Jennie, Jeanne, JanMcSorley, DavidSwallow, tburtin, rashmi, JeanneEC, lisa, EA, JohnRochford, Chuck, kirkwood, Rachael, Becca_Monteleone, Frankie No ScribeNick specified. Guessing ScribeNick: Eric_hind Inferring Scribes: Eric_hind WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.) line 213 column 1 - Warning: trimming empty <ol> Info: Document content looks like HTML Proprietary Tidy found 1 warning and 0 errors! One or more empty elements were present in the source document but dropped on output