id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
14684	"Use <button> rather than role=""button"" where possible"	Mike Gifford		"== Steps to reproduce ==

1. Starting from Drupal 8.1's admin screen
2. View the source of the buttons 

== Expected result ==

<li data-drupal-ckeditor-button-name=""JustifyRight"" class=""ckeditor-button ui-sortable-handle""><button>justify right</button></li>

== Actual result ==

<li data-drupal-ckeditor-button-name=""JustifyRight"" class=""ckeditor-button ui-sortable-handle""><a href=""#"" class=""cke-icon-only cke_ltr"" role=""button"" title=""justify right"" aria-label=""justify right""><span class=""cke_button_icon cke_button__justifyright_icon"">justify right</span></a></li>

== Other details (browser, OS, CKEditor version, installed plugins) ==

Coming from https://www.drupal.org/node/2738667 & https://www.drupal.org/node/2735421


    First rule of ARIA use (never forget):

    If you can use a native HTML element [HTML5] or attribute with the semantics and behaviour you require already built in, instead of re-purposing an element and adding an ARIA role, state or property to make it accessible, then do so.

http://w3c.github.io/aria-in-html/#rule1
"	Bug	closed	Normal		General		duplicate