W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2014

RE: How important is aria-hidden, when already hidden with CSS?

From: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Mon, 1 Dec 2014 14:50:00 +0000
To: Mitchell Evan <mtchllvn@gmail.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <BY2PR03MB2721EEE03D1FF32D80565479B7D0@BY2PR03MB272.namprd03.prod.outlook.com>
Ø  For practical accessibility: which AT accesses the DOM directly?

JAWS is one screen reader that does use the DOM in addition to accessibility APIs.


Ø  For conformance: is the CSS alone enough to meet WCAG success criteria?

Your technique needs to meet the SC and be accessibility supported -- then you have a strong case to state you have met the guidelines.  To my knowledge using ARIA or any other specific techniques are not required to meet the guidelines as long as the criteria is met in an accessible manner.

Jonathan

From: Mitchell Evan [mailto:mtchllvn@gmail.com]
Sent: Wednesday, November 26, 2014 7:43 PM
To: w3c-wai-ig@w3.org
Subject: How important is aria-hidden, when already hidden with CSS?

I have content with CSS display:none; visibility:hidden. The WAI-ARIA spec says add aria-hidden, to ensure support support for assistive technologies (AT) that access the DOM directly.

For practical accessibility: which AT accesses the DOM directly?

For conformance: is the CSS alone enough to meet WCAG success criteria?

@mitchellrevan
Received on Monday, 1 December 2014 14:50:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:53 UTC