346
edits
Changes
→How to process
There are 3 ways an AT can handle a new role:
# Basic accessibility: just fall back on the role it inherits from-- this is not wrong, but does not offer large improvements# Good accessibility: use the provided JSON semantics for the role and its properties# Enhanced accessibility: via special application code for new role
#* If role becomes popular, core AT code can deliver support
#* User or vendor-defined AT scripts that operate on a per-webpage or per-role basis
== Accessibility API Support (ATK/AT-SPI and IAccessible2) ==
Need to fill this out -- the idea is to use object attributes and events to indicate changed attributes.
