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'
alert
alertdialog
application
article
banner
button
cell
checkbox
columnheader
combobox
command
complementary
composite
contentinfo
definition
dialog
body
element.directory
document
feed
figure
figure
MAY be user-navigable.form
grid
gridcell
group
heading
img
input
landmark
link
list
listbox
listitem
log
main
marquee
math
menu
menubar
menuitem
menuitemcheckbox
menuitemradio
navigation
none
note
option
password
presentation
progressbar
radio
radiogroup
range
region
roletype
row
rowgroup
rowheader
scrollbar
search
searchbox
section
sectionhead
select
separator
slider
spinbutton
status
structure
switch
tab
table
tablist
tabpanel
term
text
textbox
timer
toolbar
tooltip
tree
treegrid
treeitem
widget
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