W3C

- DRAFT -

Cognitive and Learning Disabilities Accessibility Task Force Teleconference

14 Nov 2024

Attendees

Present
Eric, EA, tiffanyburtin, Jan, Jennie, Frankie, julierawe, rashmi, Jeanne, kirkwood, LenB
Regrets
Tiffany
Chair
Jan_McSorley
Scribe
Jan

Contents


<scribe> Meeting: COGA Internationalization Subgroup Teleconference

the COGA subgroup, it is currently being maintained in the COGA Internationalization Subgroup document (https://docs.google.com/document/d/1dGQhCbuxVD2fPDZ55Xg_WetfEz4e7h7K7jydjgc0c0A/edit?tab=t.0#heading=h.ovnviuhge5fs).

Spreadsheet: https://docs.google.com/spreadsheets/d/1ARdgFWjFQb2vOEDQkHYu24ociCeRMDF9xQhaMQgW1MA/edit?usp=sharing

Need to do a search through Content Usable to ensure that we're using problematic words (e.g. Character) correctly

<Zakim> n, you wanted to say we also need to do a search for things like @charicter@

<lisa> Include Symbols and Letters Necessary to Decipher the Words (Pattern)

<lisa> 4.4.7

<lisa> https://www.w3.org/International/questions/qa-ruby

<lisa> https://www.w3.org/International/questions/qa-ruby

<lisa> bopomofo characters to indicate pronunciation.

<kirkwood> FYI (to my question) A: Ruby characters can be ASCII characters, depending on the encoding:

<kirkwood> Symbol and Regexp objects: The default encoding for these objects is US-ASCII if all characters are US-ASCII.

<kirkwood> Filesystem encoding: The default encoding for a string from the filesystem is UTF-8.

<kirkwood> Encoding::ASCII_8BIT: This special encoding is often used for byte strings and considers characters in the ASCII range as ASCII characters

Typographical Support from i18n guidance: https://www.w3.org/TR/international-specs/#typography

<LenB> https://www.w3.org/TR/coga-usable/#examples-29

The group modified the feedback spreadsheet a bit. Jan will update the process document and send out a notice to the subgroup and the community group, reminding everyone about the homework and explaining the changes to the spreadsheet.

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/11/14 17:09:55 $

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: Eric, EA, tiffanyburtin, Jan, Jennie, Frankie, julierawe, rashmi, Jeanne, kirkwood, LenB
Present: Eric, EA, tiffanyburtin, Jan, Jennie, Frankie, julierawe, rashmi, Jeanne, kirkwood, LenB

WARNING: Replacing previous Regrets list. (Old list: John Rochford)
Use 'Regrets+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Regrets+ Jean Cooley


WARNING: Replacing previous Regrets list. (Old list: Jean Cooley)
Use 'Regrets+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Regrets+ Tiffany

Regrets: Tiffany
No ScribeNick specified.  Guessing ScribeNick: Jan
Inferring Scribes: Jan

WARNING: No "Topic:" lines found.

WARNING: Could not parse date.  Unknown month name "11": 14 11 2024
Format should be like "Date: 31 Jan 2004"

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: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


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: Eric, EA, tiffanyburtin, Jan, Jennie, Frankie, julierawe, rashmi, Jeanne, kirkwood, LenB Present: Eric, EA, tiffanyburtin, Jan, Jennie, Frankie, julierawe, rashmi, Jeanne, kirkwood, LenB WARNING: Replacing previous Regrets list. (Old list: John Rochford) Use 'Regrets+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Regrets+ Jean Cooley WARNING: Replacing previous Regrets list. (Old list: Jean Cooley) Use 'Regrets+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Regrets+ Tiffany Regrets: Tiffany No ScribeNick specified. Guessing ScribeNick: Jan Inferring Scribes: Jan WARNING: No "Topic:" lines found. WARNING: Could not parse date. Unknown month name "11": 14 11 2024 Format should be like "Date: 31 Jan 2004" 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: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report 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 43 column 9 - Warning: trimming empty <ol> line 127 column 1 - Warning: trimming empty <ol> Info: Document content looks like HTML Proprietary Tidy found 2 warnings and 0 errors! One or more empty elements were present in the source document but dropped on output. If these elements are necessary or you don't want this behavior, then consider setting the option "drop-empty-elements" to no. About HTML Tidy: https://github.com/htacg/tidy-html5 Bug reports and comments: https://github.com/htacg/tidy-html5/issues Official mailing list: https://lists.w3.org/Archives/Public/public-htacg/ Latest HTML specification: http://dev.w