Comments on: Thoughts around universal access on mobile from Accessibility 2.0 http://www.iheni.com/universal-access-on-mobile-accessibility-20/ Fri, 03 Feb 2012 10:38:50 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: The Tink Tank » Accessibility 2.0 http://www.iheni.com/universal-access-on-mobile-accessibility-20/comment-page-1/#comment-42052 The Tink Tank » Accessibility 2.0 Mon, 03 Jan 2011 15:27:10 +0000 http://www.iheni.com/?p=1728#comment-42052 [...] Discussion focused on the challenges of building one web for everyone. Personalisation came through strongly as a potential way forward, with the thought that data from one original source could be tailored to suit an individual’s requirements. Bandwith concerns were raised when the suggestion of using CSS to control delivery of content specific content was made. It was also pointed out that many people use mobile sites out of preference on their desktops because of the perceived improvement in accessibility. Read Henny’s notes from the panel discussion: Thoughts around universal access on mobile. [...] [...] Discussion focused on the challenges of building one web for everyone. Personalisation came through strongly as a potential way forward, with the thought that data from one original source could be tailored to suit an individual’s requirements. Bandwith concerns were raised when the suggestion of using CSS to control delivery of content specific content was made. It was also pointed out that many people use mobile sites out of preference on their desktops because of the perceived improvement in accessibility. Read Henny’s notes from the panel discussion: Thoughts around universal access on mobile. [...]

]]> By: Screen reader software usage shifts on desktop and mobile » iheni :: making the web worldwide http://www.iheni.com/universal-access-on-mobile-accessibility-20/comment-page-1/#comment-18894 Screen reader software usage shifts on desktop and mobile » iheni :: making the web worldwide Wed, 04 Nov 2009 15:11:16 +0000 http://www.iheni.com/?p=1728#comment-18894 [...] some. And for me at least 2009 feels like the year that we all sat up and paid attention to the potential of mobile for people with disabilities. The Ms. Minogue Factor if you [...] [...] some. And for me at least 2009 feels like the year that we all sat up and paid attention to the potential of mobile for people with disabilities. The Ms. Minogue Factor if you [...]

]]> By: Will mobile innovate desktop browsing? | SMLXL - Engagement Marketing and Communication principles from Alan Moore http://www.iheni.com/universal-access-on-mobile-accessibility-20/comment-page-1/#comment-17413 Will mobile innovate desktop browsing? | SMLXL - Engagement Marketing and Communication principles from Alan Moore Sat, 03 Oct 2009 17:02:27 +0000 http://www.iheni.com/?p=1728#comment-17413 [...] thoughts on interface without interference (and here) – from Iheni – what you might call Userbility + [...] [...] thoughts on interface without interference (and here) – from Iheni – what you might call Userbility + [...]

]]> By: The Tink Tank » Blog Archive » Accessibility 2.0 http://www.iheni.com/universal-access-on-mobile-accessibility-20/comment-page-1/#comment-17110 The Tink Tank » Blog Archive » Accessibility 2.0 Sun, 27 Sep 2009 18:34:34 +0000 http://www.iheni.com/?p=1728#comment-17110 [...] Discussion focused on the challenges of building one web for everyone. Personalisation came through strongly as a potential way forward, with the thought that data from one original source could be tailored to suit an individual’s requirements. Bandwith concerns were raised when the suggestion of using CSS to control delivery of content specific content was made. It was also pointed out that many people use mobile sites out of preference on their desktops because of the perceived improvement in accessibility. Read Henny’s notes from the panel discussion: Thoughts around universal access on mobile. [...] [...] Discussion focused on the challenges of building one web for everyone. Personalisation came through strongly as a potential way forward, with the thought that data from one original source could be tailored to suit an individual’s requirements. Bandwith concerns were raised when the suggestion of using CSS to control delivery of content specific content was made. It was also pointed out that many people use mobile sites out of preference on their desktops because of the perceived improvement in accessibility. Read Henny’s notes from the panel discussion: Thoughts around universal access on mobile. [...]

]]> By: Isofarro http://www.iheni.com/universal-access-on-mobile-accessibility-20/comment-page-1/#comment-16862 Isofarro Thu, 24 Sep 2009 09:58:15 +0000 http://www.iheni.com/?p=1728#comment-16862 Hi Henny, yes these are mainly what we are seeing on the desktop. I have no idea about mobile - that's something you could have a chat to Ricardo about tomorrow, he's our mobile guru. Maybe we can learn something from the XMPP/Jabber guys. Everyone using XMPP uses something that looks like an email as their identifier: username@jabberserverdomain. But for every device/client you have, each of those can be targetted specifically with some client identifier tagged on to the end of the jabber id, so something like exampleuser@example.com/home would be an IM client at home. Then preferences can be applied at the user level or at the device specific level - so you'd have a shorter contacts/friends list on a mobile than a desktop client. (cf: http://en.wikipedia.org/wiki/Extensible_Messaging_and_Presence_Protocol#Decentralization_and_addressing ) I think this goes back to the concepts of global user profiles, with aliases/subdivisions for devices/clients/useragents. Maybe this is something to be done in conjunction with OpenId and aliases. Being able to configure both a personal preference and a device/browser specific preference. Hi Henny, yes these are mainly what we are seeing on the desktop. I have no idea about mobile – that’s something you could have a chat to Ricardo about tomorrow, he’s our mobile guru.

Maybe we can learn something from the XMPP/Jabber guys. Everyone using XMPP uses something that looks like an email as their identifier: username@jabberserverdomain. But for every device/client you have, each of those can be targetted specifically with some client identifier tagged on to the end of the jabber id, so something like exampleuser@example.com/home would be an IM client at home. Then preferences can be applied at the user level or at the device specific level – so you’d have a shorter contacts/friends list on a mobile than a desktop client. (cf: http://en.wikipedia.org/wiki/Extensible_Messaging_and_Presence_Protocol#Decentralization_and_addressing )

I think this goes back to the concepts of global user profiles, with aliases/subdivisions for devices/clients/useragents. Maybe this is something to be done in conjunction with OpenId and aliases. Being able to configure both a personal preference and a device/browser specific preference.

]]>