W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2008

[whatwg] @Irrelevant [was: Re: Thoughts on HTML 5]

From: James Graham <jg307@cam.ac.uk>
Date: Fri, 29 Feb 2008 11:58:25 +0000
Message-ID: <47C7F361.80708@cam.ac.uk>
html at nczonline.net wrote:

> I would like something to indicate that text should not be rendered by the UA
> 
but still remain accessible. Content that should be available to screen readers
but not have a visual representation is, in fact, relevant.

Indeed, which is why such content would not have @irrelevant set. It is content 
that should be ignored in all UAs would have @irrelevant set. At the moment AT 
generally tries to infer semantics from the presentation layer (this is 
display:none so it must be irrelevant), which is why hacks like the one you 
describe are needed. The irrelevant attribute allows these semantics to be 
encoded at the markup layer.

The biggest problem I can see with this argument for @irrelevant is that it's 
not quite clear to how to get from where we are today (AT takes account of CSS 
CSS display properties rather than markup) to the behavior described above. If 
rendering display:none content that doesn't have the irrelevant attribute set 
results in a significantly worse web experience than not doing so then AT 
vendors will presumably be reluctant change behavior. We probably need some 
investigation into the effect that this change would have on the user experience 
for AT users.

-- 
"Eternity's a terrible thought. I mean, where's it all going to end?"
  -- Tom Stoppard, Rosencrantz and Guildenstern are Dead
Received on Friday, 29 February 2008 03:58:25 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:01 UTC