Dealing with non-functional requirements: three experimental studies of a process-oriented approach
Proceedings of the 17th international conference on Software engineering
Usability of E-Government Web-Sites for People with Disabilities
HICSS '03 Proceedings of the 36th Annual Hawaii International Conference on System Sciences (HICSS'03) - Track 5 - Volume 5
Nonfunctional Requirements: From Elicitation to Conceptual Models
IEEE Transactions on Software Engineering
Accessibility and design: a failure of the imagination
W4A '04 Proceedings of the 2004 international cross-disciplinary workshop on Web accessibility (W4A)
Accessibility designer: visualizing usability for the blind
Assets '04 Proceedings of the 6th international ACM SIGACCESS conference on Computers and accessibility
What's the web like if you can't see it?
W4A '05 Proceedings of the 2005 International Cross-Disciplinary Workshop on Web Accessibility (W4A)
W4A '05 Proceedings of the 2005 International Cross-Disciplinary Workshop on Web Accessibility (W4A)
Accessibility challenges and tool features: an IBM Web developer perspective
Proceedings of the 2010 International Cross Disciplinary Conference on Web Accessibility (W4A)
A tool to support the web accessibility evaluation process for novices
Proceedings of the 16th annual joint conference on Innovation and technology in computer science education
Proceedings of the 11th Brazilian Symposium on Human Factors in Computing Systems
An approach to improve the accessibility and usability of existing web system
Proceedings of the 31st ACM international conference on Design of communication
Hi-index | 0.00 |
Initial research on Web accessibility was focused on testing completed Web pages. More recently, the focus is moving to integrating accessibility features into coding tools such as Dreamweaver 8 and plugins notably LIFT. Thus accessibility is being considered slightly earlier in the development process. However, the state of Web accessibility is still disappointing even on websites that have followed the guidelines and or used evaluation and coding tools. We are proposing an approach to start considering accessibility much earlier. Our purpose is to address accessibility in the context of what is to be done and who will be participating. In this paper, we present views of Web developers about this approach. We then show (using a case study) how Web developers can elicit accessibility requirements alongside functional requirements and integrate the two to obtain conceptual models with explicit traces of accessibility requirements integrated with functional requirements. Finally we discuss lessons learnt from the case study and common benefits of the approach for Web accessibility and Web projects.