ARIA in HTML helps developers and is proposed as a W3C recom
Oct 31, 2024 3:16:58 GMT
Post by nurnobisorker14 on Oct 31, 2024 3:16:58 GMT
Accessibility is a central topic of today's Web and should no longer be taken lightly as much as possible (it is even an obligation for public service websites). The Web Applications working group has worked on a document that defines the rules of use of the Accessible Rich Internet Application (WAI-ARIA 1.1) and the Digital Publishing WAI-Aria Module 1.0 both in the W3C recommendation since October 2017. Here, it is therefore " ARIA in HTML " which is submitted to the W3C recommendation as a working document to help and support web developers in terms of accessibility .
The goal of the working group and this potential future recommendation is to bring together all the best practices and good practices to be implemented in terms of the use of the role and aria-* attributes in HTML . Indeed, these attributes allow you to specify roles for HTML blocks that bulk email campaigns are not sufficiently explicit, and can help people with difficulties or disabilities to better understand a website (often via automated systems). Overall, ARIA has many additional HTML attributes that make the content and widgets of a site accessible to everyone.
ARIA should not be used as a priority when designing a website, not because it is useless, but because its support is relatively heterogeneous from one browser and operating system (OS) to another. The rule to remember is always the same: prefer the use of precise semantic HTML elements rather than using descriptive ARIA attributes. For example, if you use the <header> tag in HTML, there is no point in adding role="header" to it because the meaning is already explicit via the tag (and above all, understood by all browsers, etc.). On the other hand, if you use a neutral tag like <div> or <span> instead of <header> , it becomes legitimate to add the corresponding role attribute to specify the role of the block.
The ARIA document in HTML recalls the rules of good usage , such as not assigning roles that would directly conflict with the semantics of a tag (for example, indicating a role="footer" in a <header> tag that would make no sense...), but also not adding redundant and explicit roles (for example, indicating a role="list" to a <ul> list tag ).
What is very useful in the document proposed to the W3C recommendation is that it brings together a snapshot and a shortcut of all the best practices for setting up the role and aria-* attributes . The strong point being two tables that group together all the values or names of attributes that can be set up for each HTML element (the following screenshot shows a part of it), whether for role or for aria-* .
The goal of the working group and this potential future recommendation is to bring together all the best practices and good practices to be implemented in terms of the use of the role and aria-* attributes in HTML . Indeed, these attributes allow you to specify roles for HTML blocks that bulk email campaigns are not sufficiently explicit, and can help people with difficulties or disabilities to better understand a website (often via automated systems). Overall, ARIA has many additional HTML attributes that make the content and widgets of a site accessible to everyone.
ARIA should not be used as a priority when designing a website, not because it is useless, but because its support is relatively heterogeneous from one browser and operating system (OS) to another. The rule to remember is always the same: prefer the use of precise semantic HTML elements rather than using descriptive ARIA attributes. For example, if you use the <header> tag in HTML, there is no point in adding role="header" to it because the meaning is already explicit via the tag (and above all, understood by all browsers, etc.). On the other hand, if you use a neutral tag like <div> or <span> instead of <header> , it becomes legitimate to add the corresponding role attribute to specify the role of the block.
The ARIA document in HTML recalls the rules of good usage , such as not assigning roles that would directly conflict with the semantics of a tag (for example, indicating a role="footer" in a <header> tag that would make no sense...), but also not adding redundant and explicit roles (for example, indicating a role="list" to a <ul> list tag ).
What is very useful in the document proposed to the W3C recommendation is that it brings together a snapshot and a shortcut of all the best practices for setting up the role and aria-* attributes . The strong point being two tables that group together all the values or names of attributes that can be set up for each HTML element (the following screenshot shows a part of it), whether for role or for aria-* .