W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > July 2014

Re: ( LC-2891)

From: <joshue.oconnor@cfit.ie>
Date: Fri, 25 Jul 2014 09:05:12 +0000
Message-Id: <E1XAbRA-0008O1-Q2@jessica.w3.org>
To: Wilco Fiers <w.fiers@accessibility.nl>
Cc: public-comments-wcag20@w3.org
 Dear Wilco Fiers  ,

The Web Content Accessibility Guidelines Working Group has reviewed the
comments you sent [1] on the Last Call Working Draft [2] of the Techniques
for WCAG 2.0 published on 16 Jan 2014. Thank you for having taken the time
to review the document and to send us comments!

The Working Group's response to your comment is included below.

Please review it carefully and let us know by email at
public-comments-wcag20@w3.org if you agree with it or not before 8th Aug
2014. In case of disagreement, you are requested to provide a specific
solution for or a path to a consensus with the Working Group. If such a
consensus cannot be achieved, you will be given the opportunity to raise a
formal objection which will then be reviewed by the Director during the
transition of this document to the next stage in the W3C Recommendation


For the Web Content Accessibility Guidelines Working Group,
Michael Cooper
W3C Staff Contact

 1. http://www.w3.org/mid/E1WDZEb-000710-9B@stuart.w3.org
 2. http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140107/


Your comment on SCR21: Using functions of the Document Object Model (DOM)
to add content t...:
> This technique is a clear “Don’t do X”, in this case
> document.write and innerHTML. Which would make it a failure technique,
> except that using document.write / innerHTML is more a question of
> accessibility support then of conformance to any specific criterion. I
> imagine this technique was created to inform developers about the
> innerHTML problem. But it’s done in a format that seems
> inappropriate for it; as a script technique.
> For all techniques content can be generated using innerHTML, so limiting
> this to 1.3.1 seems odd. Also, this technique doesn’t actually
> provide a solution to 1.3.1. If you were to insert a heading without
> header markup, that would be an accessibility problem, even if it was
> done using DOM. It would probably be more appropriate to scratch this
> technique as it is and create an article in which this problem is
> explained. This article can then be referenced to from other documents.
> This comment is part of the project for the Accessibility Support
> Database.

Working Group Resolution (LC-2891):
Thanks for your comment.  As we discussed, we are moving this issue to the
tracking system for issues raised by Working Group members. [1] We will
address this using that process. 

[1] https://www.w3.org/WAI/GL/track/issues/35 

Received on Friday, 25 July 2014 09:05:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:15:01 UTC