What else do we need?
•Need a standardized approach to informing AT about events
–i.e. Similar to the workings of MSAA and APIs for GUI apps in Ms-Windows
•Browsers should have a cursor so AT does not have to implement one
–e.g. screen readers need to have a “virtual cursor” in IE
–Future versions of Firefox will have a cursor in the browser space
•Need a standardized approach to the UI provided by browsers and the meta-UI provided by AT
–There are differences across screen readers just as there are across browsers
•Do we need an RFC on how AT should provide a meta-UI
–Standards bodies might design this but AT vendors would need to comply
•Authoring tools – another important story
–Good tools can make it easy for you to get accessibility right without knowing the detail
•A consideration of user needs – what do users really want from the future web?