How complex is the development process using WAI-ARIA ?
Developing cross-browser, custom JavaScript widgets is already a complex undertaking, not a task for the beginning web developer. Including ARIA support adds another layer of complexity, but is itself no more difficult than the basic task of successful widget programming. A useful comparison in terms of time, effort, and skill might be the creation of customized style sheets. However, even without ARIA, most web authors choose not to code from scratch, but to use JavaScript toolkits with powerful pre-built applications. As ARIA support is included in these toolkits, it will further simplify the task, allowing authors to re-use existing widgets without having to program ARIA support themselves. As ARIA becomes more well known and supported, authors will expect built-in ARIA features just as they currently benefit from the debugged cross-browser support in existing JavaScript toolkits. Additional support is available and is in development to mediate the complexity of implementing ARIA. A
Related Questions
- As part of the JDD development process, a team member should have their job title updated. Who decides what a job is to be called, the line manager or Human Resources?
- What is NEPA and how does it apply to the transportation project development process?
- Do WAI-ARIA methods increase the complexity of the development process?
