| Requirements | Solutions |
| Issues | Prescriptions |
Adding an ARIA role overrides the native role semantics in the accessibility tree which is reported via the accessibility API, and therefore ARIA indirectly affects what is reported to a screen reader or other assistive technology.
<h1 role=button>text</h1>
Becomes button with a label of 'heading text'
alertalertdialogapplicationarticlebannerbuttoncellcheckboxcolumnheadercomboboxcommand complementarycomposite contentinfodefinitiondialogbody element.directorydocumentfeedfigurefigure MAY be user-navigable.formgridgridcellgroupheadingimginput landmark linklistlistboxlistitemlogmainmarqueemathmenumenubarmenuitemmenuitemcheckboxmenuitemradionavigationnonenoteoptionpasswordpresentationprogressbarradioradiogrouprange regionroletype rowrowgrouprowheaderscrollbarsearchsearchboxsection sectionhead select separatorsliderspinbuttonstatusstructure switchtabtabletablisttabpaneltermtexttextboxtimertoolbartooltiptreetreegridtreeitemwidget window Managing focus is required. Has to be added with JavaScript
The 1st rule of ARIA use is if you can use a native HTML element or attribute with the semantics behavior already built in, do that instead!
— Estelle Weyl (@estellevw) February 25, 2016
I remember when 3G was primary mobile speed. It was slow but still worked, so why now when my phone says 3G it becomes completely useless.
— Stephen Gundee (@StephenGundee) March 23, 2016