Your SlideShare is downloading. ×
Wide BSI/JISC Accessibility SIG meeting presentation
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Wide BSI/JISC Accessibility SIG meeting presentation

572

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
572
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Widgets for Inclusive Distributed Environments Elaine Pearson, Franck Perrin, Voula Gkatzidou, Accessibility Research Centre Teesside University, UK
  • 2. Introduction
    • Partners:
      • Teesside University, TechDis, Portland College
    • Aims
      • To use a community based approach to make elearning resources accessible and inclusive to disabled students.
    • Rationale
      • To meet the needs of students with diverse needs to create an environment suitable for all students regardless of how and where they access their learning.
    • Outcomes
      • Suite of bespoke W3C standard widgets (Wookie)hosted on repository
      • Experience of applying standards
  • 3. Context: towards an APLE
  • 4. Context: towards an APLE
  • 5. Widgets definition
    • Tools
      • e.g. clocks, event countdowns, auction-tickers, visual prompts
    • Services
      • e.g. contextualised spell checker
    • Mini - applications (interactive)
      • e.g. paint programme, learning object
    • Fully-collaborative applications
      • e.g. chats, quizzes, and games
  • 6. Agile development methodology
    • Lightweight approach suitable for collaborative project
    • Based on iterative and incremental development
      • Requirements and solutions evolve through collaboration
    • Involved community of practice
      • Staff involved directly in teaching or support of disabled students
    • Informal team approach:
      • Designs formulated
        • (learning designs produced in workshops)
      • Specification outlined
        • (designs classified and prioritised, additional content identified)
      • Prototypes developed
        • ARC developers
      • Feedback illicited
        • designers
      • Amendments made
      • Widget released for evaluation, use, adaptation
  • 7. Development environment
    • Apache Wookie ( http://incubator.apache.org/wookie ):
      • Java server application to upload and deploy widgets
    • Based on the W3C Widgets specification
    • Compatible with many VLEs
    • Widgets can be deployed and run in 3 rd party applications using Wookie
    • Wookie has a REST API that can be used to get or create instances of widgets
  • 8. Outputs
      • Workshops produced more ideas than we expected
      • Wookie as a development platform worked well in most cases
      • Managed to develop (still ongoing) all but one of the 49 designs:
        • Pronounce it– because need API that so far we have not found for free
  • 9. Classification
      • Types: tools, applications and learning objects
      • Purpose:
        • Task management, time management, learning aids (e.g. Digital abacus), independence tools (e.g. Budgeting tool), assistive technology (e.g. Transparent ruler), social network tools (community activism) , content free applications (choices template)
      • Features:
        • Self-contained, Access to DB, Access to Web services, Media Content, GPS, Access to Operating System, On top of application, Dockable, Movable, Resizable, Full screen, VLE compatible, Mobile devices, Multiple browsers, Access to user area
      • Development platform:
        • Wookie, Opera, Windows apps
  • 10. Standards
    • Employ W3C Widgets 1.0 specifications
    • Mostly comprised of HTML and JavaScript, the WIDE Widgets are W3C XHTML 1.0 standard compliant
    • Web Content Accessibility Guidelines (WCAG) 2.0
    • HTML 5 Draft Specifications
    • Opera Widget Specifications 1.0
    • Cascading Style Sheet 2 Specifications
  • 11. Standards (future development)
    • IMS AccessForAll Meta-data (IMS ACCMD) and IMS Accessibility for Learner Information Package (IMS ACCLIP) could be applied to LO widgets for adaptability of content
    • IEEE Standard for Learning Object Metadata (IEEE LOM) could also be applied to LO widgets for sharing and re-use
    • ARIA could be applied to Widgets to ease the use of assistive technologies and dynamically created web controls
  • 12. Examples
    • Intention was to create all widgets using Wookie
    • http://arc.tees.ac.uk/wider
        • Wookie
          • Visual shopping list
    • Opera widgets (access to operating system
      • Community activism
        • Windows applications
          • Magnfying glass
  • 13. Visual shopping list (Wookie)
  • 14. Community activism (Opera)
  • 15. Magnifying glass (windows app)
    • A simple widget that magnifies text and images.
    • Windows app because it needs access to the client screen memory and a number of primitive operating system calls and DLLs.
    • Until W3C widget standards or browser suppliers include a virtual operating system API some ‘widgets’ will need to be developed as native system applications (e.g.Windows applications, I-phone apps or Google Android mobile applications).
  • 16. Touch screen/ one click timer (adaptation)
  • 17. Widgets for Inclusive Distributed Environments Elaine Pearson, Franck Perrin, Voula Gkatzidou, Accessibility Research Centre Teesside University, UK [email_address]

×