HTML5 accessibility - January 2013

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

HTML5 Accessibility Support Score

40/100
86/100
45/100
18/100
18/100

Mac Browsers Summary - Safari has the best HTML5 Accessibility Support Score

HTML5 Accessibility Support Score

42/100
27/100
14/100
72/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. Example work arounds for lack of implementation or lack of accessible implementation are linked from the Solutions page.

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: Support Scores for Opera on Windows and Mac and Safari on Windows are no longer being updated (scores as of February 2012) as there is no active effort to implement accessibility support in these browsers.

Windows browsers - Details

New HTML5 feature accessibility support in Windows Browsers
new HTML5 elements	Chrome 21	Firefox 15	IE 10	Opera 11.61 ^note	Webkit r105476 ^note	Notes
`article` element	Not supported	Supported	Not supported	Not supported	Not supported	IE/Opera/Safari: provide the same amount of semantic information to AT as a div element Chrome: exposes element with a `section` role in IA2 Firefox: exposes element with a `document` role in MSAA/IA2
`aside` element	Not supported	Supported	Not supported	Not supported	Not supported	IE/Opera/Safari: provide the same amount of semantic information to AT as a div element. Chrome: exposes element with a `section` role in IA2 Firefox: exposes as ARIA `role="complementary"` via IA2 object attribute and IA2 `note` role.
`audio` element	Not supported	Supported	Supported	Partially supported	Not supported	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 Opera: has keyboard support, but no AT support. Chrome: exposes limited accessibility information for the audio controls but no accessible names and has no keyboard support. IE 10: Exposes controls via accessibility APIs. Complete accessible role, name and description for all controls. Full keyboard support for visible controls
`canvas` element	Partially supported	Partially supported	Partially supported	Not supported	Not supported	IE and Firefox: supports the accessible canvas element sub-DOM Chrome: keyboard access to sub DOM, but no exposure of semantics.
`datalist` element	Partially supported	Partially supported	Supported	Partially supported	Not implemented	Opera: keyboard accessible. Firefox: keyboard accessible. list items exposed correctly, but presence of datalist not indicated when focus is on the edit box, (suggest text field should be exposed as a `combobox` or presence of list indicated by `haspopup` property) Chrome: keyboard accessible. Does not expose datalist as list, does not convey presence of data list from the edit box
`details` element	Partially supported	Not implemented	Not implemented	Not implemented	Not supported	Currently provides the same amount of semantic information to AT as a div element. Chrome: keyboard support, does not expose semantics correctly.
`figcaption` element	Not supported	Supported	Not supported	Not supported	Not supported	Currently provides the same amount of semantic information to AT as a `div` element. Firefox: exposes element as Ia" 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	Supported	Not supported	Not supported	Not supported	IE/Opera/Safari: provide the same amount of semantic information to AT as a div element Chrome: exposes element with a `section` role in IA2 Firefox: exposes element role=group with accessible name from figcaption.
`footer` element	Partially supported	Supported	Not supported	Not supported	Not supported	IE/Opera/Safari: provide the same amount of semantic information to AT as a div element Chrome: exposes element with a `footer` role in IA2 Firefox: exposes as ARIA landmark `role="contentinfo"` Refer to HTML5 Accessibility Chops: section elements
`header` element	Not supported	Supported	Not supported	Not supported	Not supported	IE/Opera/Safari: provide the same amount of semantic information to AT as a div element Chrome: exposes element with a `section` role in IA2 Firefox: exposes element name via IA2 object attribute.
`hgroup` element	Not implemented	Not implemented	Not implemented	Not implemented	Not implemented	not implemented
color `input`	Partially supported	Not implemented	Not implemented	Partially supported	Not implemented	Chrome: has keyboad support, exposes button as role=text in MSAA and a role=section in IA2, does not expose color information on button. Opera: keyboard accessible, but no information exposed to assistive technology.
Date `input`	Partially supported	Not implemented	Not implemented	Not supported	Not implemented	Chrome: keyboard operable, no role states and property informsation exposed for calendar interface. No indication that the control can expose a date picker control. Opera: date picker cannot be activated using the keybaord, no information exposed to assistive technology.
Date and Time `input`	Not implemented	Not implemented	Not implemented	Not supported	Not implemented	Opera: date picker cannot be activated using the keybaord, no information exposed to assistive technology.
Local Date and Time `input`	Not implemented	Not implemented	Not implemented	Not supported	Not implemented	Opera: date picker cannot be activated using the keybaord, no information exposed to assistive technology.
E-mail `input`	Not implemented	Partially supported	Not implemented	Not supported	Not implemented	Firefox: invalid state exposed in accessibility API. Error message (tooltip)not exposed via accessibility API. tootlip error message not keyboard accessible.
Month `input`	Not implemented	Not implemented	Not implemented	Not supported	Not implemented	Opera: date picker cannot be activated using the keybaord, no information exposed to assistive technology.
Number `input`	Partially supported	Not implemented	Not implemented	Partially supported	Partially supported	Opera: keyboard accessible. Chrome : keyboard accessible, role exposed as `progressbar` should be `spinbutton`. Safari: keyboard support.
Range `input`	Supported	Supported	Supported	Partially supported	Partially supported	Chrome: correct role, full keyboard support, slider value exposed. Opera: no role, partial keyboard support, slider value not exposed. Safari: partial keyboard support.
Search `input`	Supported	Supported	Supported	Supported	Supported	The difference between `input type="search"` and `type="text"` is 'primarily stylistic'.
Telephone `input`	Not implemented	Not implemented	Not implemented	Not supported	Not implemented	?
Time `input`	Not implemented	Not implemented	Not implemented	Partially supported	Not implemented	Opera: keyboard accessible. Chrome: keyboard accessible, role exposed as edit box should be spinbutton
URL `input`	Not implemented	Partially supported	Not implemented	Not supported	Not implemented	Firefox: invalid state exposed in accessibility API. Error message (tooltip)not exposed via accessibility API. tootlip error message not keyboard accessible.
Week `input`	Not implemented	Not implemented	Not implemented	Partially supported	Not implemented	Opera: date picker cannot be activated using the keybaord, no information exposed to assistive technology. Chrome : keyboard accessible, role exposed as edit box should be spinbutton
main element
`menu` > context menu	Not implemented	Partially supported	Not implemented	Not implemented	Not implemented	Firefox:
`menu`> list	Not implemented	Not implemented	Not implemented	Not implemented	Not implemented	not implemented
`menu` > toolbar	Not implemented	Not implemented	Not implemented	Not implemented	Not implemented	not implemented
meter element	Not supported	Not implemented	Not implemented	Not supported	Not supported	Chrome: name, role, properties not exposed. Opera:name, role, properties not exposed.
`nav` element	Not supported	Supported	Not supported	Not supported	Not supported	IE/Opera/Safari: provide the same amount of semantic information to AT as a div element. Chrome: exposes element with a `section` role in IA2 Firefox: exposes as ARIA landmark `role="navigation"` via IA2 object attribute, and as a `section` role in IA2 (Unsure about the correctness of this mapping). Refer to HTML5 Accessibility Chops: section elements
`output` element	Not implemented	Supported	Not implemented	Not supported	Not implemented	Firefox: accessibility support implemented - IA2 `section` role, with `aria-live=polite` and hasIA2 `controlled_by relation` defined by `@for` attribute.
`progress` element	Supported	Supported	Supported	Not supported	Not implemented	Chrome: exposes name role, state and value correctly! Opera: name, role and state content not exposed. Firefox: exposes name role, state and value correctly!
`section` element	Supported	Supported	Not supported	Not supported	Not supported	IE/Opera/Safari: provide the same amount of semantic information to AT as a div element 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	Partially supported	Not implemented	Not implemented	Not implemented	Not supported	IE/Opera/Safari: provide the same amount of semantic information to AT as a div element Chrome: keyboard support only Webkit: no keyboard access. No role/name/state information exposed.
`track` element	Partially supported	Not implemented	Supported	Partially supported	Partially supported	IE: supports both WebVTT and TTML Chrome/Opera/Safari: only support WebVTT Refer to WebVTT support in browsers for more details
`video` element	Not supported	Supported	Supported	Partially supported	Not supported	Firefox: keyboard support suboptimal - cannot interact with individual controls. Opera: has keyboard support, but no AT support. Chrome: exposes limited accessibility information for the controls but no accessible names and has no keyboard support. IE 10: Exposes controls via accessibility APIs. Complete accessible role, name and description for all controls. Full keyboard support for visible controls

New HTML5 attribute accessibility support in Windows Browsers
new HTML5 attributes (note: this is not all of them!)	Chrome 21	Firefox 15	IE 10	Opera 11.61^note	Webkit r105476^note	Notes
hidden attribute	Supported	Supported	Not implemented	Supported	Supported	Chrome, Opera, Firefox & Safari: Content within elements that have a hidden attribute are not displayed or navigable. Note: In all supporting browsers CSS `display:none` is applied to elements with the `hidden` attribute.
`required` attribute	Partially supported	Supported	Not supported	Not supported	Not implemented	Firefox: exposes popup message as alert and identifies the field as invalid. Chrome: exposes as IA2 required state, does not expose invalid state or expose popup message. IE: Supported for visual users, but required state not exposed via accessibility APIs. Visible error message not available via accessibility APIs
`placeholder` attribute	Not supported	Partially supported	Partially supported	Not supported	Partially supported	Safari: `placeholder` content is exposed as an accessible name if the `input` does not have an explicitly associated text label, but explicit association using the HTML `label` element is not currently supported in Webkit based browsers on Windows. Only explicit association using the `title` attribute on the `input` overrides the use of the `placeholder` text as the accessible name. Firefox: `placeholder` content is exposed as an accessible name if the `input` does not have an explicitly associated text label using the `label` element. If there is a label associated using the `label` element using the `for/id` attributes, the accessible name is the label text. If the `label` element is wrapped around the control, the accessible name is the label text + the placeholder text. If the control has a `title` attribute the placeholder text is still used as the accessible name and the title text is used as the accessible description. IE: Uses placeholder text as the accessible name for a control when there is no other accessible name provided. Otherewise placeholder text is not expsoed. Note: there are incompatibilities between the IE, Firefox and Safari accessibility implementations of placeholder. Refer to: HTML5 accessibility Chops: the placeholder attribute

New HTML5 attribute accessibility support in Windows Browsers

new HTML5 attributes (note: this is not all of them!)

Chrome 21

Firefox 15

IE 10

Opera 11.61^note

Webkit r105476^note

Notes

hidden attribute

Chrome, Opera, Firefox & Safari: Content within elements that have a hidden attribute are not displayed or navigable.

Note: In all supporting browsers CSS display:none is applied to elements with the hidden attribute.

required attribute

Firefox: exposes popup message as alert and identifies the field as invalid.

Chrome: exposes as IA2 required state, does not expose invalid state or expose popup message.

IE: Supported for visual users, but required state not exposed via accessibility APIs. Visible error message not available via accessibility APIs

placeholder attribute

Safari: placeholder content is exposed as an accessible name if the input does not have an explicitly associated text label, but explicit association using the HTML label element is not currently supported in Webkit based browsers on Windows. Only explicit association using the title attribute on the input overrides the use of the placeholder text as the accessible name.

Firefox: placeholder content is exposed as an accessible name if the input does not have an explicitly associated text label using the label element. If there is a label associated using the label element using the for/id attributes, the accessible name is the label text. If the label element is wrapped around the control, the accessible name is the label text + the placeholder text. If the control has a title attribute the placeholder text is still used as the accessible name and the title text is used as the accessible description.

IE: Uses placeholder text as the accessible name for a control when there is no other accessible name provided. Otherewise placeholder text is not expsoed.

Note: there are incompatibilities between the IE, Firefox and Safari accessibility implementations of placeholder.

Refer to: HTML5 accessibility Chops: the placeholder attribute

New HTML5 feature accessibility support in Mac Browsers
new HTML5 elements	chrome 23.0.1260.1	Firefox 17.0a1	Opera 11.6.1^note	Safari (6)	Notes
`article` element	Not supported	Not supported	Not supported	Supported	Chrome,Firefox,Opera: provide the same amount of semantic information to AT as a div element Safari: Exposed in Mac API as AXRole: "AXGroup", AXSubrole: "AXDocumentArticle", AXRoleDescription: "article".
`aside` element	Not supported	Not supported	Not supported	Supported	Chrome,Firefox,Opera: provide the same amount of semantic information to AT as a div element Safari: Exposed in Mac API as AXRole: "AXGroup", AXSubrole: "AXLandmarkComplementary", AXRoleDescription: "complementary"
`audio` element	Not supported	Partially supported	Partially supported	Partially supported	Firefox & Opera: have keyboard support, but no AT support. Safari & Chrome: Appears to be no keyboard access unless voiceover is running.
`canvas` element	Partially supported	Not supported	Not supported	Not supported	Chrome: partial support, interactive elements in sub dom in tab order, but sub dom content not exposed.
`datalist` element	Partially supported	Partially supported	Partially supported	Not implemented	Opera: keyboard accessible. Firefox: keyboard accessible. Chrome: keyboard accessible. Does not expose datalist as list, does not convey presence of data list from the edit box
`details` element	Partially supported	Not implemented	Not implemented	Partially supported	Firefox,Opera: provide the same amount of semantic information to AT as a div element Chrome & Safari: keyboard support only.
`figcaption` element	Not supported	Not supported	Not supported	Not supported	Chrome,Firefox,Opera, Safari: provide the same amount of semantic information to AT as a div element
`figure` element	Not supported	Not supported	Not supported	Not supported	Chrome,Firefox,Opera, Safari: provide the same amount of semantic information to AT as a div element
`footer` element	Not supported	Supported	Not supported	Supported	Safari & Firefox: exposes as AXRole: "AXGroup", AXSubrole: "AXLandmarkContentInfo",
`header` element	Not supported	Not supported	Not supported	Supported	Currently provides the same amount of semantic information to AT as a `div` element. Safari: exposes as AXRole: "AXGroup", AXSubrole: "AXLandmarkBanner", AXRoleDescription: "banner" Note: is every header element announced as banner?
`hgroup` element	Not implemented	Not implemented	Not implemented	Not implemented	not implemented
color `input`	Partially supported	Not implemented	Partially supported	Not implemented	Opera: partially keyboard accessible (cannot access 'other' button. No information exposed to assistive technology. Chrome: Keyboard support only
Date `input`	Partially supported	Not implemented	Not supported	Not implemented	Opera: date picker cannot be activated using the keybaord, no information exposed to assistive technology.
Date and Time `input`	Not implemented	Not implemented	Not supported	Not implemented	Opera: date picker cannot be activated using the keybaord, no information exposed to assistive technology.
Local Date and Time `input`	Not implemented	Not implemented	Not supported	Not implemented	Opera: date picker cannot be activated using the keybaord, no information exposed to assistive technology.
E-mail `input`	Not implemented	Not implemented	Not supported	Not implemented	? mostly not implemented.
Month `input`	Not implemented	Not implemented	Not supported	Not implemented	Opera: date picker cannot be activated using the keybaord, no information exposed to assistive technology.
Number `input`	Partially supported	Not implemented	Partially supported	Supported	Opera: keyboard accessible. Safari: Note: stepper controls are assigned role seperately from the edit box. The stepper is not currently recognized by VoiceOver.
Range `input`	Supported	Not implemented	Partially supported	Supported	Chrome: correct role, partial keyboard support, slider value not exposed. Opera: no role, partial keyboard support, slider value not exposed. Safari: exposed as AXRole: "AXSlider", AXSubrole: "(null)", AXRoleDescription: "slider"
Search `input`	Supported	Supported	Not supported	Supported	The difference between `input type="search"` and `type="text"` is 'primarily stylistic'.
Telephone `input`	Not implemented	Not implemented	Not supported	Not implemented	?
Time `input`	Not implemented	Not implemented	Partially supported	Not implemented	Opera: keyboard accessible.
URL `input`	Not implemented	Not implemented	Not supported	Not implemented	?
Week `input`	Not implemented	Not implemented	Not supported	Not implemented	Opera: date picker cannot be activated using the keybaord, no information exposed to assistive technology.
`menu` > context menu	Not implemented	Not implemented	Not implemented	Not implemented	not implemented
`menu`> list	Not implemented	Not implemented	Not implemented	Not implemented	not implemented
`menu` > toolbar	Not implemented	Not implemented	Not implemented	Not implemented	not implemented
meter element	Not supported	Not implemented	Not supported	Not supported	Chrome, Safari, Opera: name, role, properties not exposed.
`nav` element	Not supported	Not supported	Not supported	Supported	Chrome,Firefox,Opera: provide the same amount of semantic information to AT as a div element. Safari: exposes as AXRole: "AXGroup", AXSubrole: "AXLandmarkNavigation", AXRoleDescription: "navigation".
`output` element	Not implemented	Not implemented	Not supported	Not implemented	Currently provides the same amount of semantic information to AT as a `div` element.
`progress` element	Supported	Not supported	Not supported	Supported	Chrome & Safari: exposes as AXRole: "AXProgressIndicator", AXSubrole: "(null)", AXRoleDescription: "progress indicator", AXValue (W): "50".
`section` element	Supported	Not supported	Not supported	Supported	Chrome,Firefox,Opera: provide the same amount of semantic information to AT as a div element. Safari: exposes as AXRole: "AXGroup", AXSubrole: "AXDocumentRegion", AXRoleDescription: "region".
`summary` element	Partially supported	Not implemented	Not implemented	Partially supported	Provides the same amount of semantic information to AT as a `div` element. Chrome & Safari: keyboard access only no useful role, state or name information exposed.
`track` element	Partially supported	Not implemented	Partially supported	Partially supported	IE: supports both WebVTT and TTML Chrome/Opera/Safari: only support WebVTT Refer to WebVTT support in browsers for more details
`video` element	Partially supported	Partially supported	Partially supported	Partially supported	Firefox & Opera: have keyboard support, but no AT support. Safari & Chrome: Appears to be no keyboard access unless voiceover is running.

New HTML5 feature accessibility support in Mac Browsers

new HTML5 elements

chrome 23.0.1260.1

Firefox 17.0a1

Opera 11.6.1^note

Safari (6)

Notes

article element

Chrome,Firefox,Opera: provide the same amount of semantic information to AT as a div element

Safari: Exposed in Mac API as AXRole: "AXGroup", AXSubrole: "AXDocumentArticle", AXRoleDescription: "article".

aside element

Chrome,Firefox,Opera: provide the same amount of semantic information to AT as a div element

Safari: Exposed in Mac API as AXRole: "AXGroup", AXSubrole: "AXLandmarkComplementary",
AXRoleDescription: "complementary"

audio element

Firefox & Opera: have keyboard support, but no AT support.

Safari & Chrome: Appears to be no keyboard access unless voiceover is running.

canvas element

Chrome: partial support, interactive elements in sub dom in tab order, but sub dom content not exposed.

datalist element

Opera: keyboard accessible.

Firefox: keyboard accessible.

Chrome: keyboard accessible. Does not expose datalist as list, does not convey presence of data list from the edit box

details element

Firefox,Opera: provide the same amount of semantic information to AT as a div element

Chrome & Safari: keyboard support only.

figcaption element

Chrome,Firefox,Opera, Safari: provide the same amount of semantic information to AT as a div element

figure element

Chrome,Firefox,Opera, Safari: provide the same amount of semantic information to AT as a div element

footer element

Safari & Firefox: exposes as AXRole: "AXGroup", AXSubrole: "AXLandmarkContentInfo",

header element

Currently provides the same amount of semantic information to AT as a div element.

Safari: exposes as AXRole: "AXGroup", AXSubrole: "AXLandmarkBanner", AXRoleDescription: "banner" Note: is every header element announced as banner?

hgroup element

not implemented

color input

Opera: partially keyboard accessible (cannot access 'other' button. No information exposed to assistive technology.

Chrome: Keyboard support only

Date input

Opera: date picker cannot be activated using the keybaord, no information exposed to assistive technology.

Date and Time input

Opera: date picker cannot be activated using the keybaord, no information exposed to assistive technology.

Local Date and Time input

Opera: date picker cannot be activated using the keybaord, no information exposed to assistive technology.

E-mail input

? mostly not implemented.

Month input

Opera: date picker cannot be activated using the keybaord, no information exposed to assistive technology.

Number input

Opera: keyboard accessible.

Safari: Note: stepper controls are assigned role seperately from the edit box. The stepper is not currently recognized by VoiceOver.

Range input

Chrome: correct role, partial keyboard support, slider value not exposed.

Opera: no role, partial keyboard support, slider value not exposed.

Safari: exposed as AXRole: "AXSlider", AXSubrole: "(null)", AXRoleDescription: "slider"

Search input

The difference between input type="search" and type="text" is 'primarily stylistic'.

Telephone input

Time input

Opera: keyboard accessible.

URL input

Week input

Opera: date picker cannot be activated using the keybaord, no information exposed to assistive technology.

menu > context menu

not implemented

menu> list

not implemented

menu > toolbar

not implemented

meter element

Chrome, Safari, Opera: name, role, properties not exposed.

nav element

Chrome,Firefox,Opera: provide the same amount of semantic information to AT as a div element.

Safari: exposes as AXRole: "AXGroup", AXSubrole: "AXLandmarkNavigation", AXRoleDescription: "navigation".

output element

Currently provides the same amount of semantic information to AT as a div element.

progress element

Chrome & Safari: exposes as AXRole: "AXProgressIndicator", AXSubrole: "(null)", AXRoleDescription: "progress indicator", AXValue (W): "50".

section element

Chrome,Firefox,Opera: provide the same amount of semantic information to AT as a div element.

Safari: exposes as AXRole: "AXGroup", AXSubrole: "AXDocumentRegion", AXRoleDescription: "region".

summary element

Provides the same amount of semantic information to AT as a div element.

Chrome & Safari: keyboard access only no useful role, state or name information exposed.

track element

IE: supports both WebVTT and TTML

Chrome/Opera/Safari: only support WebVTT

Refer to WebVTT support in browsers for more details

video element

Firefox & Opera: have keyboard support, but no AT support.

Safari & Chrome: Appears to be no keyboard access unless voiceover is running.

New HTML5 attribute accessibility support in Mac Browsers
new HTML5 attributes (note: this is not all of them!)	chrome 23.0.1260.1	Firefox 17.0a1	Opera 11.6.1^note	Safari (6)	Notes
hidden attribute	Supported	Supported	Supported	Supported	Chrome, Opera, Firefox & Safari: Content within elements that have a hidden attribute are not displayed or navigable. Note: In all supporting browsers CSS `display:none` is applied to elements with the `hidden` attribute.
`required` attribute	Supported	Not supported	Not supported	Supported	Chrome & Safari: Identify the field as required.
`placeholder` attribute	Not supported	Not supported	Not supported	Supported	Safari: supports via AXPlaceholderValue Refer to: HTML5 accessibility Chops: the placeholder attribute

New HTML5 attribute accessibility support in Mac Browsers

new HTML5 attributes (note: this is not all of them!)

chrome 23.0.1260.1

Firefox 17.0a1

Opera 11.6.1^note

Safari (6)

Notes

hidden attribute

Chrome, Opera, Firefox & Safari: Content within elements that have a hidden attribute are not displayed or navigable.

Note: In all supporting browsers CSS display:none is applied to elements with the hidden attribute.

required attribute

Chrome & Safari: Identify the field as required.

placeholder attribute

Safari: supports via AXPlaceholderValue

Refer to: HTML5 accessibility Chops: the placeholder attribute

A work in progress: January 2013

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

Mac Browsers Summary - Safari has the best HTML5 Accessibility Support Score

Overview

Windows browsers - Details

Mac browsers - Details

Support Tables - Legend & notes:

HTML5 Accessibility Support Score calculation: