W3C home > Mailing lists > Public > w3c-wai-au@w3.org > April to June 2013

RE: Implementations may be hard to find for ATAG2 B.2.4.4 Identify Template Accessibility (Enhanced)

From: Greg Pisocky <gpisocky@adobe.com>
Date: Mon, 10 Jun 2013 04:28:11 -0700
To: "Richards, Jan" <jrichards@ocadu.ca>, "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <64BAFF76F7529141BBCFE3457F1D81AD016A9AD60D29@NAMBX02.corp.adobe.com>
Dreamweaver makes a point if identifying accessible templates but it does not identify those without that label as "inaccessible" explicitly. The implication being, those templates with the accessible label are indeed more accessible than those templates which do not have the label.

-----Original Message-----
From: Richards, Jan [mailto:jrichards@ocadu.ca] 
Sent: Sunday, June 09, 2013 10:21 PM
To: w3c-wai-au@w3.org
Subject: Implementations may be hard to find for ATAG2 B.2.4.4 Identify Template Accessibility (Enhanced)

Hi all,

We are getting really close to having potential implementations for all of the SCs...

But one SC I wonder about is:
B.2.4.4 Identify Template Accessibility (Enhanced): If the authoring tool provides any non-accessible templates (WCAG) options and does not include a template selection mechanism, then the non-accessible templates include accessibility warnings within the templates. (Level AAA)

Its purpose is clear...to plug a potential accessibility issue in an otherwise excellent tool (at Level AAA)...but I wonder if the expectation that non-accessible templates will be explicitly labelled is really going to be implemented. 

Cheers,
Jan

(MR) JAN RICHARDS
PROJECT MANAGER
INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)
OCAD UNIVERSITY

T 416 977 6000 x3957
F 416 977 9844
E jrichards@ocadu.ca
Received on Monday, 10 June 2013 11:28:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:40:05 UTC