Windows Browsers Summary - Firefox has the best HTML5 Accessibility Support Score

HTML5 Accessibility Support Score

  • Chrome + Opera 67/100
  • Firefox   88.5/100
  • Internet Explorer  37/100

Overview

This site is a resource to provide information about which new HTML5 user interface features are accessibility supported in browsers, making them usable by people who rely upon assistive technology (AT) to use the web.

Note: Browser's may not have practical accessibility support for HTML features on particular operating systems. Refer to Rough Guide: browsers, operating systems and screen reader support for details.

It is not intended to dissuade developers from using new HTML5 features. Sometimes there are better choices, sometimes developers have to add a little extra to make the feature useful or usable, and other times features have simply not been implemented by any browser or only by browsers that do not yet support assistive technologies. As a consequence it may not yet be practical to use a particular HTML5 feature.

The information in the support table is updated on a semi-regular basis, to keep up with support improvements made in browsers as new versions are released.

Support Tables - Legend & notes

NOTE: Safari on Windows is no longer included as there is no active effort to implement accessibility support in this browser. Opera is now under Chrome as it uses Chrome's rendering engine and any accessibility support it may have is provided by Chrome's accessibility implementation.

Windows browsers - Details

New HTML5 feature accessibility support in Windows Browsers
new HTML5 elements Chrome 35Opera 20 Firefox 31 IE 11 Notes
article element

IE: provides no semantic information via accessibility APIs (related bug)

Firefox: exposes element with a document role in MSAA/IA2

aside element

IE: provides no semantic information via accessibility APIs (related bug)

Firefox: exposes as ARIA role="complementary" via IA2 object attribute and IA2 note role.

audio element

Firefox:

  • Exposes controls via accessibility APIs, but individual controls cannot be interacted with via the keyboard.
  • keyboard access is provided via Firefox specific shortcuts
  • Exposes element name as an IA2 object attribute
  • role=grouping

Chrome:Exposes controls via accessibility APIs, but individual controls cannot be interacted with via the keyboard.

  • IE 11: Exposes controls via accessibility APIs. Complete accessible role, name and description for all controls.
  • Full keyboard support for visible controls
canvas element Supported

IE, Chrome, Firefox: supports the accessible canvas element sub-DOM.
Firefox
also supports drawfocus ring and hitregion()

 

datalist element Supported

Chrome: keyboard accessible. Does not expose datalist as list. (related bug)

details element

Chrome: keyboard support, does not expose semantics correctly.Currently provides the same amount of semantic information to AT as a div element. chrome bug: Issue 350435

 

dialog element Supported

Chrome: exposes correct role for dialog and traps focus in dialog in the modal state.
Note: Currently Chrome keyboard support is incomplete, does not move focus back to trigger control on dialog close.

 

figcaption element

IE: provides no semantic information via accessibility APIs.
Chrome: Currently provides the same amount of semantic information to AT as a div element.Chrome bug

Firefox: exposes element as IA2 caption role and the element name as an IA2 object attribute, exposes the figcaption content as an accessible name for its parent figure.

figure element not supported

IE: provides no semantic information via accessibility APIs.
Chrome: provide the same amount of semantic information to AT as a div element.
Chrome bug

Firefox: exposes element role=group with accessible name from figcaption.

footer element Supported

IE: provides no semantic information via accessibility APIs (related bug)

Firefox: exposes as ARIA landmark role="contentinfo" when not a child of article or section elements

header element Supported

IE: provides no semantic information via accessibility APIs (related bug)

Chrome: exposes element with a section role in IA2

Firefox: exposes as ARIA landmark role="banner" when not a child of article or section elements

color input

Chrome: has keyboad support, exposes button as IA2 color chooser exposes color information in RGB as accValue.

Firefox: keyboard accessible, exapsed as a button but color value not exposed to AT. Refer to bug 559767

Date input

Chrome/Opera: keyboard operable, spin buttons exposed correctly (except for accname). No role state and property information exposed for calendar interface. No indication that the control can expose a date picker control.

 

Date and Time input

not implemented

 

E-mail input Firefox: supported in Version 27: see resolved bug Expose whether the input is a search, url, tel, etc.
Chrome bug filed
Month input

Chrome/Opera: keyboard operable, spin buttons exposed correctly (except for accname). No role state and property information exposed for calendar interface. No indication that the control can expose a date picker control.

 

Number input

Chrome: exposed as editable text (not spinbutton) works with keyboard (arrow keys). chrome bug 71954:

Range input

all good

Search input Firefox: supported in Version 27: see resolved bug Expose whether the input is a search, url, tel, etc.
Chrome bug filed
Telephone input Firefox: supported in Version 27: see resolved bug Expose whether the input is a search, url, tel, etc.
Chrome bug filed
Time input Chrome: keyboard operable, spin buttons exposed correctly.
URL input

Firefox: supported in Version 27: see resolved bug Expose whether the input is a search, url, tel, etc.

Chrome bug filed

Week input

Chrome: keyboard operable, spin buttons exposed correctly (except for accname). No role state and property information exposed for calendar interface. No indication that the control can expose a date picker control.

 

mark element Currently provides the same amount of semantic information to AT as a span element. Firefox bug filed: make <mark> element accessible
main element Firefox and Chrome: implements as role=main.
IE: provides no semantic information via accessibility APIs (related bug)
menu - popup menu Firefox: does not indicate presence of popup menu.
menu - toolbar not implemented
menuitem element Firefox: Supports menu item role and keyboard interaction.
meter element

Firefox/Chrome: role exposed as meter in MSAA, properties not exposed. Firefox bug 1 (API) and Firefox bug 2 (UI)

 

nav element Supported

IE: provides no semantic information via accessibility APIs (related bug)

Firefox: exposes as ARIA landmark role="navigation" via IA2 object attribute

output element

Firefox: accessibility support implemented - IA2 section role, with aria-live=polite and hasIA2 controlled_by relation defined by @for attribute.

Chrome: not supported, Chrome bug filed.

IE: not supported, IE bug filed

progress element

all good

section element

IE: provides no semantic information via accessibility APIs (related bug)

Chrome: exposes element with a section role in IA2

Firefox: exposes element with a paragraph role in IA2 (Unsure about the correctness of this mapping). Refer to HTML5 Accessibility Chops: section elements

summary element

IE: provides no semantic information via accessibility APIs (related bug)

Chrome: keyboard support only. chrome bug: Issue 350435

 

track element

IE: supports both WebVTT and TTML

Chrome/Firefox: only support WebVTT

Refer to WebVTT support in browsers for more details

video element

Firefox: keyboard support suboptimal - cannot interact with individual controls.

Chrome: no keyboard support.

IE 11: Exposes controls via accessibility APIs. Complete accessible role, name and description for all controls. Full keyboard support for visible controls