W3C

- DRAFT -

HTML Accessibility Task Force Teleconference

01 Dec 2014

See also: IRC log

Attendees

Present
janina, ShaneM, JF, nigel, MarkS
Regrets
Chair
SV_MEETING_CHAIR
Scribe
JF

Contents


<trackbot> Date: 01 December 2014

<janina> Shane, we have an ad hoc Zakim code today

<janina> It's 26631#

<ShaneM> kk

<janina> Nygel, we have a Zakim ad hoc today, 26631#

<janina> No problem, there's just Shane and me so far

<ShaneM> 26631 JF

<janina> Code: 26631#

Chair+ Janina Sajka agenda+ Identify Scribe agenda+ Media Accessibility User Requirements: Remaining Comment Responses agenda+ Responses to Commenters

<scribe> scribe: JF

JS: looking to get MAUR wrapped up, possibility to publish before end of year

nigel: what stage of the process are you at now?

JS: we've never actually announced a Last Call, but did solicit comments from the public

we did announce a FPWD, at that time we heard from EO

before PF took over the process to have this published as a note, we received some feedback then

JS: we started out trying to explain to folks that it was a lot more than just captions. We realized that what was needed was a larger inventory of all of the needs (etc.)

nigel: the question was around process - could new comments still come forward? What would happen?

JS: yes, we could still look at them

nigel: may have a few additional comments, around captions
... for example, it would be very useful if, when captions are displayed on a background, that the background can be expanded to give some padding
... thoughts on anti-aliasing of fonts
... the ability to change color combinations for users (i.e. Coga)

JS: noticing a similar thing here with cell phones background colors change and make things harder to read

nigel: not aware of any evidence that anti-aliasing helps with readability

JS: open to more comments

<janina> http://lists.w3.org/Archives/Public/public-html-a11y/2014Sep/0045.html

JS: 2 comments from the public
... need to clarrify that we are talking about pan location in the audio field

<janina> [DV-13] "Allow the user to relocate the description track within the audio field,

<ShaneM> Allow the user to relocate the pan location of the description track within the audio field, with the user setting overriding the author setting. The setting should be re-adjustable as the media plays.

JS: propose we insert the pan location in there

[agreement]

JS: second comment

<ShaneM> http://lists.w3.org/Archives/Public/public-html-a11y/2014Sep/0046.html

SM: will look to reformulate this to match tone of existing doc

JF: disagree that this belongs

SM: tend to agree with John - there is already a section on cognative disabilities in the document - we could add this there
... believe that is already embraced in that section
... section 2.7 Physical impairment

JS: we normally don't talk of specific deases (etc.), but rather functional needs

SM: respond that section 2.7 covers it

[discussion of the 4 suggested additions]

JS: first two are interesting

(a) that media player controls are of a sufficent size to make them clickable by users with neurological disabilities and physical impairments (UX : must) (b) that media player controls have sufficient spacing to prevent input errors by users with neurological disabilities and physical impairments (UX : should)

nigel:

noticing that there are no references anywhere

JS: can apply the same approach as we did to color blindness

<MarkS> https://w3c.github.io/pfwg/media-accessibility-reqs/#A_checklist

<scribe> ACTION: JF to update checklist to reflect new naming of sections [recorded in http://www.w3.org/2014/12/01-html-a11y-media-minutes.html#action01]

<trackbot> Created ACTION-290 - Update checklist to reflect new naming of sections [on John Foliot - due 2014-12-08].

JS: next item - can we formulate some official responses? use a template [sic] as part of that

SM: EO responses where in thier wiki - feels odd to edit that

JS: will ask Shawn

SM: happy to write up the others - have notes on each already

JS: sounds like we have a plan
... hope to have comments from Nigel by next week

Nigel: cannot attend next week, regardless of the time of meeting

SM: let's shift back to 4 PM Boston as planned
... will start on the comments piece then

JS: that's a wrapp

Summary of Action Items

[NEW] ACTION: JF to update checklist to reflect new naming of sections [recorded in http://www.w3.org/2014/12/01-html-a11y-media-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2014/12/01 15:54:06 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/nige/nigel/
Succeeded: s/heps/helps/
Found Scribe: JF
Inferring ScribeNick: JF

WARNING: No "Topic:" lines found.

Default Present: janina, ShaneM, JF, nigel, MarkS
Present: janina ShaneM JF nigel MarkS

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

Found Date: 01 Dec 2014
Guessing minutes URL: http://www.w3.org/2014/12/01-html-a11y-media-minutes.html
People with action items: jf

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]