Comments on: The accessibility of HTML 5 autofocus

By: Technikwürze 158 – Formulare total 2 (Barrierefreie Formulare) » Technikwürze – Web Standards Podcast

Tue, 22 Jun 2010 07:38:00 +0000

[...] The accessibility of HTML 5 autofocus – Bruce Lawson [...]

By: WebAIM: Blog - Future Web Accessibility: HTML5 <input> Extensions

WebAIM: Blog - Future Web Accessibility: HTML5 <input> Extensions — Thu, 27 May 2010 18:47:07 +0000

[...] that there are some accessibility concerns with autofocusing in general, and this won’t change those one way or the other, but in the [...]

By: 5 little-known features of HTML5 « blog | odadia

5 little-known features of HTML5 « blog | odadia — Mon, 03 May 2010 11:40:55 +0000

[...] and con’s of autofocus, however Bruce Lawson has already done a great job of explaining the issues around autofocus accessibility on his [...]

By: [extern] Technikwürze – Formulare total 1+ 2 - sprungmarker

[extern] Technikwürze – Formulare total 1+ 2 - sprungmarker — Sun, 03 Jan 2010 16:40:09 +0000

[...] Lawson hat in seinem Artikel The accessibility of HTML 5 autofocus bereits mit dem Attribut autofocus zu kämpfen. Mit diesem Attribut setzt man nach dem Laden der [...]

By: Bruce

Bruce — Mon, 01 Jun 2009 21:08:55 +0000

Thanks Adrian – cocked up tbe versions of the files. Hopefully, role=”main” is there now in the right place.

By: adrian_h

adrian_h — Fri, 29 May 2009 23:04:06 +0000

interesting that the newly fixed version has a different screenreader issue though in that my particular screenreader (JFW) recognises the form fields to be such in that it allows me to type in to them (the virtual cursor mode is disabled) but the screenreader doesn’t actually activate its “forms mode” EG the sound and splen “forms mode” alert aren’t given uless you use cursor keys to move away from and back to the field (tabbing doesn’t fix it), this is true for all fields – suspect it’s a JFW and ARIA suppport issue and actually although using jfw v10 I’m not using the latest build so just maybe… also note that your ‘content’ landmark seems to be end the end not the start of your content, EG before all the copywrite guff.