Re: [uf-discuss] hCard, i18n and screen readers

2011-01-16 Thread Toby Inkster
On Tue, 11 Jan 2011 17:06:33 -0800 Jeff codedr...@gmail.com wrote: Doesn't HTML5 microdata use the meta element for this purpose? That doesn't really work outside XHTML. The problem is that the HTML5 parsing algorithm hoists meta elements into the document head. In other words: !doctype

[uf-discuss] hCard, i18n and screen readers

2011-01-11 Thread Jeff
I'm new to hCard.  Let's say I have the following markup: div  h3Téléphone Mobile/h3  div1-408-555-1234/div /div What is the proper way to mark this up such that it is identified as a mobile phone number, but it is also i18n friendly (i.e. it does not require me to put CELL in the text contents

Re: [uf-discuss] hCard, i18n and screen readers

2011-01-11 Thread lists
On Tue, 11 Jan 2011 10:19 -0800, Jeff codedr...@gmail.com wrote: Someone just now pointed me to http://microformats.org/wiki/value-class-pattern#Using_value-title_to_publish_machine-data which indicates that the following is another option: div class=tel  h3 class=typespan

Re: [uf-discuss] hCard, i18n and screen readers

2011-01-11 Thread Jeff
Hi Ben, On Tue, Jan 11, 2011 at 4:32 PM, li...@ben-ward.co.uk wrote: This is the correct way; you don't need to abuse abbr for translation. value-title was worked out partially for this very issue. When we wrote up the pattern we ran thorough testing against screen readers; yes, it's a