See also: IRC log
<trackbot> Date: 11 April 2013
<janina> Meeting: HTML-A11Y Task Force Teleconference
<scribe> scribe: Léonie Watson
JS: The F2F is coming up.
Meetings with Web Apps and HTML WG.
... We're looking at alt bugs that the Text sub-team has
surfaced.
... Web Apps has a draft that we're interested in from an
accessibility angle.
... It may be an API for CJK input.
JF: Tab Atkins proposed Cascading
Attribute Sheets (CAS).
... It abstracts an element's attributes into a separate sheet,
then hooks them to the element via the class attribute.
... Think it has potential for ARIA and/or accessibility.
... Wonder whether we should go back to Tab and/or Web Apps to
say we've looked at it?
JS: Recall some email traffic on
the TF list a while back.
... Think focus now will be hard whilst we get ARIA 1.0 to the
finishing line.
... So think we're looking at ARIA 2.0.
JF: CAS can embrace more than ARIA, so think it might be a potential HTML5.1 feature.
JS: No discussion, but please be
mindful that this specification extension is out there.
... We're running this on a tight timetable. We'd like to move
it to LC as soon as the W3C process permits, as soon as two
weeks away.
JS: FYI we have worked up a
written statement of what our publications are.
... Now is a good time to perfect it. Comments welcome.
JS: Following the conversation
with Mark Watson last week, has anyone had the opportunity to
look at the documents relating to this?
... Does anyone has the URI?
... Do we need alternative media to be encrypted?
... We'll need to return to this.
... Can we keep it a technology issue by duing due dilligence
on where the alternative media might need to be encrypted?
JB: You can encrypt the main media in such a way that access with a screen reader is perceived to be an attack.
JF: The DAISY Consortium has a policy around DRM, are there any documented difficulties with that policy?
JS: No, not really.
JF: I asked Mark about
transcripts.
... My concern is the animosity that exists around this topic.
Suggest we look at the use cases. Don't want to create a
problem that doesn't exist though.
JS: A recent thread the phrase
"late binding" came up. Needing to support a third party that
supplies content after the original source is released.
... I think this helps us.
JF: If media source A uses encryption method A, but the alternate content is encrypted using encryption method B, the result could be messy.
JS: That's what the HTML5 spec is
intended to get aay from.
... The W3C is creating a tool, it's technology/encryption
agnostic.
... Having two encryption methods for the the original content
and its alternate content wouldn't be conformant.
JF: But the encryption APIs would be conformant.
JS: Could you look into this and put some concrete information together around it?
JF: Sure.
JS: First, do we have a need to
encrypt an alternate media source?
... Second, how should that alternate be encrypted?
JB: We need some background and some specific information to proceed on.
<MarkS> https://www.w3.org/Bugs/Public/show_bug.cgi?id=8827
MS: We'd like the text to be removed, but want to checkwith Steve that it isn't being addressed through his work with Robin.
JS: Accepted.
<MarkS> https://www.w3.org/Bugs/Public/show_bug.cgi?id=10455
MS: Raised in response to the deprecation of longdesc. Recommend closing now Image Description extension is FPWD.
JS: Accepted.
<MarkS> https://www.w3.org/Bugs/Public/show_bug.cgi?id=10853
MS: Also raised in response to longdesc being deprecated. Recommend closing it.
JB: Suggest we're clear about the exact status change we're making.
<MarkS> https://www.w3.org/Bugs/Public/show_bug.cgi?id=10967
MS: Another longdesc related bug. Recommend closing it.
JF: This bug includes content like video, audio etc. None of these are covered by the current Image Description extension.
JS: We're confident that current
browser and AT longdesc implementations will see the Image
Description extension through LC and into the full spec.
... If we extend its remit, that may not happen. We should get
longdesc back into the spec then extend its capability.
... Should e postpone it?
LW: Suggest we open a fresh bug when the time comes. We can add space in the bug triage area of the wiki so it doesn't drop off our radar.
<Judy> https://www.w3.org/Bugs/Public/describekeywords.cgi
JS: Good idea.
JF: Suggest using reviewerSatisfied keyword.
This is scribe.perl Revision: 1.137 of Date: 2012/09/20 20:19:01 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/latebinding/late binding/ No ScribeNick specified. Guessing ScribeNick: LJWatson Found Scribe: Léonie Watson Present: Janina_Sajka Judy_Brewer Léonie_Watson Mark_Sadecki John_Foliot Michael_Cooper Found Date: 11 Apr 2013 Guessing minutes URL: http://www.w3.org/2013/04/11-html-a11y-minutes.html People with action items:[End of scribe.perl diagnostic output]