The html5 category of WAVE items (which previously included HTML5 and ARIA items) has been removed and a new aria category replaces it. The new aria category includes existing ARIA items, plus new ones as documented below.
The following WAVE items have been renamed and moved from the defunct html5 category to the structure category:
html5_header -> header
html5_nav -> nav
html5_main -> main
html5_aside -> aside
html5_footer -> footer
aria_search -> search
The following WAVE items have moved to new output categories:
table_layout - from structure to alert. This better encourages the disuse of layout tables.
longdesc - from feature to alert. Due to poor support.
The following are new WAVE items (with categories):
aria_menu_broken (error) - Indicates an ARIA menu lacking required menuitem children.
region_missing (alert) - Indicates the lack of regions/landmarks in the page.
aria_describedby (aria) - Indicates the presence of aria-describedby attribute. The existing aria_label item will identify elements with aria_label and aria_labelledby.
aria_button (aria) - Indicates the presence of role="button".
aria_live_region (aria) - Indicates the presence of role="alert", role="alertdialog", or aria-live attributes.
aria_menu (aria) - Indicates the presence of role="menu" attribute.
aria_hidden (aria) - Indicates the presence of aria-hidden="true" attribute.
aria_expanded (aria) - Indicates the presence of aria-expanded attribute.
aria_haspopup (aria) - Indicates the presence of aria-haspopup attribute.
The server_image_map error item has been removed. These are generally non-existent on the web.
Chrome rendering engine The API will feature a Chrome rendering engine for back-end analysis. This supports faster and more accurate accessibility evaluation.
User agent string customization
You can pass a &useragent= parameter to override the default up-to-date Chrome on Mac user agent string. This, along with setting viewport sizes, can allow better analysis of mobile web content.
New evaluation rules as documented above
CSS selector outputs
Get details/counts for WAVE items, plus CSS selector values for each item with &reporttype=4. CSS selectors can be used to associate WAVE items/errors with specific page elements.
Numerous bug and performance fixes
The API is now faster, more accurate, and has fewer false positives than ever before. The contrast checking logic has been entirely rewritten to avoid the majority of false positives.
If you have feedback or recommendations on the WAVE API Specification, please contact us.