W3C

- DRAFT -

SV_MEETING_TITLE

07 Mar 2016

See also: IRC log

Attendees

Present
Janina
Regrets
Chair
Lisa_Seeman
Scribe
JohnRochford, Lisa_Seeman

Contents


<Lisa_Seeman> agenda: this

<Lisa_Seeman> next item

<Lisa_Seeman> next item

<Lisa_Seeman> https://www.w3.org/blog/2015/09/tpac-2016-dates-and-location-announced/

<Lisa_Seeman> scribe: JohnRochford

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/track/actions/open

<Lisa_Seeman> michael are you there

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Main_Page#Current_schedules

Lisa: I will have a coordination call with Michael afterwards
... ddahl has open action items

<Lisa_Seeman> https://rawgit.com/w3c/coga/master/gap-analysis/table.html

Lisa: Next issue is to look at tables
... 1st table - anyone need more time to look at that?

<Lisa_Seeman> https://rawgit.com/w3c/coga/master/techniques/index.html

Lisa: To create Table 1, I looked at security in techniques document

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Proposal_for_WCAG

Rich: First link in Table 1 goes to Lisa's C: drive.

Lisa is describing work put into Table 1

Lisa: Does Table 1 make sense?
... Who thinks that it does make sense?

Rich: For this example, the content ties into the information above it in a clean way.

Correction: KurtM said "For this example, the content ties into the information above it in a clean way."

Lisa: Let's look at Table 7, which was harder / more difficult.
... I have to go back and redo Table 7.

Lisa is describing work she performed on Table 7.

KurtM: Lisa, are you matching slow readers with comprehension?

Lisa resumes describing Table 7 work.

Lisa: Are people happy with Table 7?
... Do the tables (7 & 1) make sense to people?

<Lisa_Seeman> scribe error

<Lisa_Seeman> it was kurt

<Lisa_Seeman> https://rawgit.com/w3c/coga/master/gap-analysis/table.html

<Lisa_Seeman> debie: the tables are realy long , so much in a cell

<Lisa_Seeman> lisa: we could move out the discusion

<Lisa_Seeman> scribe: Lisa_Seeman

debie: the tables are realy long , so much in a cell

lisa: we could move out the discusion

kurt: when would people look at the links - it dig deaper?

and should be be after

Lisa: I wouldnt, people need to see it

for one row

debie agrees with kurt

John R link to the bottem for the

Lisa: have a link to it from the user need

John R: likes the table anoying horisontal table. but why do we need it

for other userg groups who will complain whjy need things

john: to much information

maybe each table will be its own page

<scribe> scribe: JohnRochford

ddahl: Is it redundant to have explanatory text and links to that text (external to the page)?

Lisa: A problem is that the link URLs will change.

<Lisa_Seeman> https://rawgit.com/w3c/coga/master/gap-analysis/table.html

Michael: Global copy and replace would not be too hard.
... Editing tables is a pain in the arse.
... You could move all the content to GitHub now.
... It is easier to share editing in GitHub than it is in the Wiki.
... I recommend not overwhelming the table with content; and instead using links. Also, you could have dynamic tables.
... A common approach is to have a twistie that opens up more content.

<Lisa_Seeman> scribe: Lisa_Seeman

i like the idea of more content palled in real time

jquery will support it

michale: libarier or html summaries might do ti

1.4.3 Instructions, labels, navigation and important information are provided with a clear writing style that includes:

miss out the bullet pints

<MichaelC> <details>1.4.3 Instructions, labels, navigation and important information are provided with a clear writing style</details>

<MichaelC> <details>

<MichaelC> 1.4.3 Instructions, labels, navigation and important information are provided with a clear writing style

<MichaelC> <details>

<MichaelC> <summary>

<MichaelC> 1.4.3 Instructions, labels, navigation and important information are provided with a clear writing style

<MichaelC> </summary>

<MichaelC> bullets

<MichaelC> </details>

kurt: that will make more digestible

<MichaelC> It´s a HTML 5.1 feature: https://www.w3.org/TR/html51/semantics.html#the-details-element

<MichaelC> Probably need a script ¨polyfill¨ for backwards compatibility, but can manage ti

lisa: doing it by script will keep it current

even if the wording on the souce changes

1.4.3 Instructions, labels, navigation and important information are provided with a clear writing style that includes:

more

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/03/07 18:09:49 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: JohnRochford
Inferring ScribeNick: JohnRochford
Found Scribe: Lisa_Seeman
Inferring ScribeNick: Lisa_Seeman
Found Scribe: JohnRochford
Inferring ScribeNick: JohnRochford
Found Scribe: Lisa_Seeman
Inferring ScribeNick: Lisa_Seeman
Scribes: JohnRochford, Lisa_Seeman
ScribeNicks: JohnRochford, Lisa_Seeman

WARNING: No "Topic:" lines found.

Present: Janina

WARNING: Fewer than 3 people found for Present list!


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting

Got date from IRC log name: 07 Mar 2016
Guessing minutes URL: http://www.w3.org/2016/03/07-coga-minutes.html
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


[End of scribe.perl diagnostic output]