Comments for cssgallery.info

Comment on Advanced Titanium Tutorial – Bonjour Networking by JB

JB — Fri, 23 Sep 2011 19:22:26 +0000

Tried to compile this with SDK 1.7.2 and it looks like JSON.parse makes bugs upon resolving messages sent.

No more bug if compiled with 1.6.2 (did not try another sdk)…

Comment on Testing the accessibility of the CSS generated content by David Calhoun

David Calhoun — Thu, 15 Sep 2011 21:46:54 +0000

Doh! I’m actually using generated content for some presentation, and actually don’t want it to be read by VoiceOver on iOS in my case. I would ideally be using an background image instead, but I wanted to cut down on bytesize by using text character in :after content. I can’t use role=”presentation” on the element itself, because only the generated content is for presentation!

Generated content seems to be a tricky thing in general, regardless of whether screen readers read the content or not. :/

Comment on Testing the accessibility of the CSS generated content by Chris Coyier

Chris Coyier — Wed, 31 Aug 2011 22:40:50 +0000

Small addition: genernated content text can’t be selected, which is another kind of accessibility concern.

Comment on Seven days with Titanium – day 6 – animations and transforms by Acebone

Acebone — Fri, 26 Aug 2011 13:25:18 +0000

It seems that animations does not work on the Android platform – is this true or am I doing something wrong?

Comment on Advanced Titanium Tutorial – Bonjour Networking by Mark Pemburn

Mark Pemburn — Thu, 18 Aug 2011 19:29:43 +0000

Hmm. Tried this out on a couple of new iPad 2s on 4.3.3 iOS (Compiled with 4.3 iOS SDK and Titanium 1.7.1 SDK). Didn’t work at all. Kitchen Sink Bonjour test works fine. {sigh}

Comment on Advanced Titanium Tutorial – Bonjour Networking by Bruno

Bruno — Fri, 12 Aug 2011 23:40:03 +0000

Hello Dan.
I cannot put this to work..
I installed on my iPhone and on my iPad and i have no comunication between the 2 devices…

any help with this?
best regards,
B

Comment on How screen readers speak a page with HTML5 and ARIA by balamurugan

balamurugan — Tue, 19 Jul 2011 10:41:13 +0000

It is interesting that NVDA does not even recognise “application” as a landmark. This I didn’t know. Apparently, it does not even appear in the Elements List (press NVDA+F7) as a landmark. It does make sense, though, I think, given the way that NVDA treats role=”application”, namely by having it not engage the virtual buffer at all. The “application” landmark would not be available to NVDA’s landmark navigation commands since it is outside the buffer, as it were. Nor would it be announced by NVDA while reading a page’s document content.

by
pluskb webdesigning

Comment on Testing the accessibility of the CSS generated content by Steven

Steven — Fri, 15 Jul 2011 07:32:18 +0000

“Obviously it is not good practice to generate content in this way because of the way screenreaders handle it, but I would be interested to know if this is in fact amounts to a bug within screenreader software becuase the specification defines this as content so they should be made able to read it.”

I totally agree. As much as I see actual content as belonging to the DOM of the page and anything generated by CSS as presentational (screen readers don’t and shouldn’t read out the entire markup of a page just because it is there in the source) I can totally see uses for it for the purposes of allowing users to override stylesheets on a website to add notes etc. But being that I personally think this should be handled by the browser directly or by a third party utility, I would like CSS content to be treated like padding and positioning … consistence in browsers in one things, but to not have consistence in screen readers is also not helping.

Comment on Testing the accessibility of the CSS generated content by Thierry Koblentz

Thierry Koblentz — Mon, 27 Jun 2011 15:53:36 +0000

I believe ARIA mandates that SR speak generated content.
See this discussion:
http://lists.w3.org/Archives/Public/www-style/2010Nov/0437.html

Comment on Testing the accessibility of the CSS generated content by Richard - Accessibleweb Design

Richard - Accessibleweb Design — Fri, 24 Jun 2011 14:51:52 +0000

Obviously it is not good practice to generate content in this way because of the way screenreaders handle it, but I would be interested to know if this is in fact amounts to a bug within screenreader software becuase the specification defines this as content so they should be made able to read it.