If an element can have roles set it is stated in the intro, for example the button element intro inc

These attributes communicate role, state and property proshow producer semantics to assistive technologies via the accessibility APIs implemented in browsers. proshow producer The W3C HTML specification provides information proshow producer about which ARIA attributes are allowed to be used on each HTML element in section 3.2.7 WAI-ARIA proshow producer . Developer (un)friendly information
The requirements specified in section 3.2.7 WAI-ARIA are not in a form which could be considered web developer friendly . They are presented in 2 large tables and only include features proshow producer that have constraints. i.e. if you can use any ARIA attribute, the element proshow producer is not listed, this is because the primary purpose of this information is for browser and conformance checker implementers, not developers like you and I. Furthermore to find out what ARIA attributes can be used on a particular element, in the past would involve navigating away from an element definition to the ARIA section proshow producer then going through the tables to find the desired element or attribute, to locate its ARIA rules. Developer friendly information
Over proshow producer the past few months the W3C HTML specification has been updated to include the ARIA information, formerly tucked proshow producer away or absent, now presented in your face , in the introductory section of each element definition.
In the example below, proshow producer the introductory section of the picture element definition now includes information about allowed ARIA roles and property attributes, so developers can quickly find the info without having to hunt about in the spec. In the case of the (newly added) picture element, the role attribute cannot be used and only global ARIA attributes are allowed. The same ARIA information can be found in the introductory section of every element in the HTML specification.
If an element can have roles set it is stated in the intro, for example the button element intro includes all allowed ARIA role values and indicates the default role for the element, which in most circumstances does not need to be set. Each role is linked to a description, within proshow producer the ARIA reference section , of the HTML spec, which also includes a list of allowed aria-* attributes for each role value, proshow producer with additional links to the ARIA specification information for all role, states and properties.
The intent of these additions to the HTML specification is to make it easier for developers to get at the information they need to make accessible things with HTML. Feedback welcome! Further Reading Using ARIA in HTML – a practical guide for developers on how to add accessibility information to HTML elements using ARIA. WAI-ARIA 1.0 Authoring Practices – proshow producer An author’s guide to understanding and implementing Accessible Rich Internet Applications widget design patterns HTML 5.1 section 3.2.7 WAI-ARIA Category Elements proshow producer Steve Faulkner
This article was written by Steve Faulkner . An Australian living in London, works for The Paciello Group, a well-known web accessibility consultancy, and is a co-editor of the HTML5 spec at W3C 5 Responses on the article Using ARIA in HTML
Thanks for the post Steve. I’d proshow producer really like to see more and better use of ARIA across the web but have found that it’s not been well described in terms of the developer community needs. This is a really good enhancement to the HTML spec which, I hope, will see increased and improved use of ARIA.
Providing ARIA info on element proshow producer level is great but I find it confusing that almost all HTM5 tags comes with a “default-do-not-set-note” even though it aligns with the note on Strong Native Semantics
In the majority of cases setting an ARIA role and/or aria-* attribute that matches the default implicit ARIA semantics is unnecessary and not recommended as these properties are already set by the browser.
Looking at how IE fails to provide semantic information via accessibility on HTML5 elements , the Using WAI-ARIA in HTML Recommendations Table and the first exception in The First Rule of ARIA is where I’m lost.
I would think adding roles is like backward compatibility proshow producer until browsers get’s truly modern like this: <nav role="navigation"> <header role="banner"> (once on the main header) <main role="main"> (once) <article role="article"> <aside role="complementary"> <footer role="contentinfo"> (once on the main footer)
You can use these tags: <a href = "" title = "" > <abbr title = "" > <b> <blockquote cite = "" > <cite> <del datetime = "" > <em> <i> <q cite = "" > <strong>
Accessibility proshow producer Attributes Boilerplates Browser Compatibility proshow producer Comment CSS Elements Events forms interviews JavaScript APIs Marketing Misc multimedia Questions Quick Tips Reviews Simplequiz Specification Changes Structure Validation WAI-ARIA
Alex Gibson Bruce Lawson Cennydd Bowles Chris Bewick Derek Johnson Ian Devlin Jack Osborne Mark Boas Mike Robinson Oli Studholme Peter Gas