[whatwg] [HTML5] Accessibility question
I know the topic has come up a few times, but I'm still wondering if HTML 5 should provide some sort of logic around content that should not be displayed by browsers but should be read by screen readers. Perhaps a noview boolean attribute on each element could be used to tell UAs not to render the content but to report it to screen readers? Or maybe a noview/ element could be used to surround content that shouldn't be displayed but should be accessible to screen readers? Any thoughts? -Nicholas Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs
Re: [whatwg] [HTML5] Accessibility question
On Sun, 16 Mar 2008, Nicholas C. Zakas wrote: I know the topic has come up a few times, but I'm still wondering if HTML 5 should provide some sort of logic around content that should not be displayed by browsers but should be read by screen readers. Perhaps a noview boolean attribute on each element could be used to tell UAs not to render the content but to report it to screen readers? Or maybe a noview/ element could be used to surround content that shouldn't be displayed but should be accessible to screen readers? Wouldn't hiding content from sighted viewers hurt accessibility for sighted viewers? Could you elaborate more on what problem you are trying to solve? -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] Superset encodings [Re: ISO-8859-* and the C1 control range]
Krzysztof Żelechowski wrote: Some characters, like digits, are direction-transparent [...] Inserting an LTR mark before them makes them LTR. Thanks. I would have preferred a solution which did not involve inserting extraneous characters, but I have now added LTR marks to fix the rendering. -- Øistein E. Andersen
