Evaluating Web Accessibility for Specific Mobile Devices Markel Vigo , A. Aizpurua, M. Arrue and J. Abascal Laboratory of ...
Introduction International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Generally, web content is ...
Mobile Web vs Web Accessibility International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 Guidelines Arch...
Guidelines International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Mobile Web Best Practices MW...
Guidelines & Evaluation International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Related work: t...
Guidelines & Evaluation International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>mobileOK Basic ...
Guidelines & Evaluation International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>MWBP 1.0 are fu...
Architecture: overview International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Source Code Retr...
Source Code Retriever International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Objective: retrie...
Device Information Retriever International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Two ways t...
Extending mobileOK Basic tests International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>The impl...
Guidelines Instantiator International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>mobileOK Basic ...
Guidelines Instantiator International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Example for the...
Evaluation Engine International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Summary: </li></ul><u...
Case Study International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Nine web pages have been eva...
Case Study International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Looking carefully at results...
Last remarks International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>The tool can be used for t...
Conclusions & Future Work International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Summary: </li...
Evaluating Web Accessibility for Specific Mobile Devices Markel Vigo , A. Aizpurua, M. Arrue and J. Abascal Laboratory of ...
Upcoming SlideShare
Loading in …5
×

Evaluating Web Accessibility For Specific Mobile Devices

4,472 views
4,387 views

Published on

Published in: Business, Design
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
4,472
On SlideShare
0
From Embeds
0
Number of Embeds
15
Actions
Shares
0
Downloads
79
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

Evaluating Web Accessibility For Specific Mobile Devices

  1. 1. Evaluating Web Accessibility for Specific Mobile Devices Markel Vigo , A. Aizpurua, M. Arrue and J. Abascal Laboratory of HCI for Special Needs International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 University of the Basque Country
  2. 2. Introduction International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Generally, web content is developed with desktop computers in mind </li></ul><ul><ul><li>Server-side services or proxies transform content </li></ul></ul><ul><ul><li>User Agents provide new features for better user experience: fast navigation mechanisms or content linearization </li></ul></ul><ul><li>Mobile Web and Web Accessibility for physically impaired users share similar problems </li></ul><ul><li>Problems that able-bodied user may have are similar to those found by people with disabilities </li></ul>Guidelines Architecture Case Study Conclusions Introduction
  3. 3. Mobile Web vs Web Accessibility International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 Guidelines Architecture Case Study Conclusions Introduction Mobile Web Web accessibility Small display size causes disorientation on the user Lack of context disorientates visually impaired users Lack of pointing device forces users to use keyboards. Navigation is slowed down Screen reader users suffer information overload : navigation bars and menus. Typing is a tedious task due to low text input rate Users with motor disabilities face analogous problems Due to low bandwidth images tend to not to be loaded Not providing alternatives for visual content raises accessibility barriers Lack of colour support may cause information loss Information conveyed with colour causes problems to colour-blind users Lack of support causes information loss Assistive technologies tend to have problems with newer technologies
  4. 4. Guidelines International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Mobile Web Best Practices MWBP 1.0 were released by the W3C </li></ul><ul><li>mobileOK test are techniques to conform with MWBP 1.0 </li></ul><ul><ul><li>mobileOK Basic: mobileOK Basic conformance  “functional user experience” </li></ul></ul><ul><ul><li>mobileOK Pro: techniques are to be released </li></ul></ul><ul><li>Rely on the “Default Delivery Context” </li></ul>Usable screen width : 120px minimum Mark-up language support: XHTML Basic 1.1 Character-encoding: UTF-8 256 colours minimum CSS level 1 support Scripting is not supported Guidelines Architecture Case Study Conclusions Introduction
  5. 5. Guidelines & Evaluation International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Related work: there are several tools that evaluate web pages against mobileOK Basic tests </li></ul>Guidelines Architecture Case Study Conclusions Introduction TAW MWI ready.mobi EvalAccess MOBILE
  6. 6. Guidelines & Evaluation International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>mobileOK Basic test are intended for development purposes BUT </li></ul><ul><li>There are different flavours of mobile devices </li></ul><ul><li>These test produce problems when mobile devices deviate from DDC </li></ul><ul><ul><li>Newer models  false positives </li></ul></ul><ul><ul><li>Legacy devices  false negatives </li></ul></ul>Guidelines Architecture Case Study Conclusions Introduction
  7. 7. Guidelines & Evaluation International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>MWBP 1.0 are full of statements regarding device features. E.g.: “ Do not use tables unless the device is known to support them ” </li></ul><ul><li>Objective: a tool that evaluates mobileOK Basic tests considering the specific features of mobile devices when required </li></ul><ul><li>mobileOK Basic test are extended, focusing on the device-dependent tests </li></ul>Guidelines Architecture Case Study Conclusions Introduction
  8. 8. Architecture: overview International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Source Code Retriever </li></ul><ul><li>Device Information Retriever </li></ul><ul><li>Evaluation Engine </li></ul>Device-Tailored Evaluation Device-tailored Report Guidelines Architecture Case Study Conclusions Introduction Mobile Device’s brand name and model
  9. 9. Source Code Retriever International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Objective: retrieve the source code in the same way that a mobile device would get it </li></ul><ul><li>Some web servers identify the ‘user-agent’ HTTP header and deliver different web content </li></ul>Source Code Retriever XHTML file WWW <ul><li>The Source Code Retriever retrieves a web resource simulating the access of a determined device by manipulating the “user-agent” HTTP header </li></ul>Guidelines Architecture Case Study Conclusions Introduction
  10. 10. Device Information Retriever International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Two ways to obtain information about a determined mobile device: </li></ul><ul><ul><li>UAProf profiles  extended CC/PP profiles using prf namespace </li></ul></ul><ul><ul><li>WURFL (Wireless Universal Resource file)  XML file </li></ul></ul><ul><li>Heterogeneous information sources </li></ul><ul><li>Required data are extracted and a CC/PP file is created </li></ul><ul><li>Both sources have complementary information </li></ul>Guidelines Architecture Case Study Conclusions Introduction CC/PP file Device Information Retriever Jena WURLF API WURLF profiles UAPRof profiles
  11. 11. Extending mobileOK Basic tests International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>The implications that devices characteristics have on the mobileOK Basic tests have analyzed </li></ul><ul><li>New CC/PP based vocabulary has been created to express certain concepts </li></ul><ul><li>Examples </li></ul><ul><ul><li>CONTENT_FORMAT_SUPPORT  access:picFormatSupport </li></ul></ul><ul><ul><li>NO_FRAMES  prf:FramesCapable </li></ul></ul><ul><ul><li>OBJECTS_OR_SCRIPTS  prf:JavaScriptEnabled </li></ul></ul><ul><li>Information to be retrieved are the issues that the DDC captures: character encoding, image format support etc. </li></ul>Guidelines Architecture Case Study Conclusions Introduction
  12. 12. Guidelines Instantiator International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>mobileOK Basic test are implemented using UGL (Uniform Guidelines Language) </li></ul><ul><ul><li>It has slots so that values can be put in guidelines </li></ul></ul><ul><li>Device data from the CC/PP file is used to fill in slots in the mobileOK test </li></ul><ul><li>Once the guideline is completed XQUERY tests are dynamically created </li></ul>XQUERY tests mobileOK tests CC/PP file Guidelines Instantiator Guidelines Architecture Case Study Conclusions Introduction
  13. 13. Guidelines Instantiator International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Example for the IMAGE_MAPS test </li></ul>XQUERY tests mobileOK tests CC/PP file Guidelines Instantiator <access:pntSupport > true </access:pntSupport> <test_case id=&quot;8&quot;> <evaluation_type>auto</evaluation_type> <evaluation_result>error</evaluation_result> <profile_feature type=&quot; access:pntSupport &quot;/> <value> </value> <element> <label>OBJECT</label> <test_elem>check attribute</test_elem> <related_attribute> <atb>ismap</atb> </related_attribute> </element> </test_case> CC/PP excerpt UGL excerpt let $tmp:=web_doc.xml//OBJECT[@ismap] return if(not( ))then for $i in $tmp return <error>{$i/@line, $i/name()}</error> XQUERY test true true Guidelines Architecture Case Study Conclusions Introduction
  14. 14. Evaluation Engine International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Summary: </li></ul><ul><li>Web resource is retrieved changing HTTP headers </li></ul><ul><li>Information regarding the device is retrieved from profile repositories and a CC/PP file is created </li></ul><ul><li>Slots in guidelines specifications are filled in with CC/PP data and XQUERY tests are automatically created </li></ul><ul><li>XHTML file is evaluated against the dynamically created queries and a device-tailored report is obtained </li></ul>Evaluation Engine Evaluation Report XQUERY tests mobileOK tests CC/PP file Device Information Retriever Guidelines Instantiator Jena WURLF API WURFL profiles UAPRof profiles <ul><li>Once we have a set of XQUERY tests evaluation is straightforward using XSLT processors </li></ul>Guidelines Architecture Case Study Conclusions Introduction Source Code Retriever XHTML file WWW
  15. 15. Case Study International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Nine web pages have been evaluated with 3 different mobile devices </li></ul><ul><ul><li>D 1 : less support than the DDC </li></ul></ul><ul><ul><li>D 2 : similar to the DDC </li></ul></ul><ul><ul><li>D 3 : more features than the DDC </li></ul></ul>Guidelines Architecture Case Study Conclusions Introduction mobileOK Basic Specific Evaluations for mobileOK Basic D 1 , D 2 , D 3 D 1 D 2 D 3 www.google.com 4 4 4 4 www.youtube.com 3 2 3 2 www.flickr.com 4 4 5 4 www.amazon.com 9 10 9 9 www.gmail.com 9 5 9 5 www.facebook.com 7 7 6 6 m.yahoo.com 6 6 6 6 m.twitter.com 8 6 8 6 www.wikipedia.org 428 363 358 280
  16. 16. Case Study International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Looking carefully at results… </li></ul><ul><ul><li>Mobile versions of traditional web pages have fewer errors with respect to desktop web pages </li></ul></ul><ul><ul><li>Devices with less support than the DDC tend to produce more errors  false negatives ↓ </li></ul></ul><ul><ul><li>while those with better support and more characteristics yield fewer errors  false positives ↓ </li></ul></ul>Guidelines Architecture Case Study Conclusions Introduction
  17. 17. Last remarks International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>The tool can be used for the development of accessible applications </li></ul><ul><li>Main purpose is to plug this tool in a more general framework </li></ul><ul><ul><li>Goal: obtain user and device tailored accessibility scores as the user interacts </li></ul></ul><ul><li>Demonstration of a prototype: </li></ul><ul><li>http://sipt07.si.ehu.es/mobile/ </li></ul>Guidelines Architecture Case Study Conclusions Introduction
  18. 18. Conclusions & Future Work International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 <ul><li>Summary: </li></ul><ul><ul><li>The presented tool deals with device specific accessibility issues </li></ul></ul><ul><ul><li>mobileOK Basic tests have been extended </li></ul></ul><ul><ul><li>False positives and false negatives diminish </li></ul></ul><ul><li>Future Work </li></ul><ul><ul><li>mobileOK Basic tests contain many references to HTTP headers content. Currently our approach deals with mark-up issues </li></ul></ul><ul><ul><li>mobileOK Pro are expected to be released </li></ul></ul>Guidelines Architecture Case Study Conclusions Introduction
  19. 19. Evaluating Web Accessibility for Specific Mobile Devices Markel Vigo , A. Aizpurua, M. Arrue and J. Abascal Laboratory of HCI for Special Needs International Cross-Disciplinary Conference on Web Accessibility, W4A 2008 University of the Basque Country Any question?

×