Fluid is an open source community of designers and developers who help improve the usability and accessibility of the open web. We contribute to a variety of open source projects (e.g. jQuery UI, GPII, PhET), and work on our own projects including:
- FLOE: Provides the resources to personalize how we each learn and to address barriers to learning
- Social Justice Repair Kit: The goal is to support youth at risk who have learning differences to re-engage in education through an inclusively designed social justice platform that integrates authentic project-based learning.
- The Inclusive Design Guide
We're looking for students to collaborate with us on the Google Summer of Code 2018 program. Working with Fluid gives you a chance to learn more about accessibility, usability, and inclusivity while writing code with cutting-edge open web technologies. Create cool stuff and make a real impact on users at the same time!
For information about the various ways we communicate with each other, see our Get Involved wiki page.
Make sure to read through the Getting Started on GSoC page for information on joining the Fluid community and preparing to work on a GSoC project.
Inclusive Design Guide Digital-Print copy workflow prototypes
What we're looking for is to be able to provide small scale on-demand printing of the Inclusive Design Guide content. We regularly edit or add content to the Guide and we currently have two versions of the content, web and print. At the moment the print copy needs to be updated separately every time we make changes to the source content. We want to devleop a simple process that ensures that the print copy is always up to date with any changes to the source content. We also want to make it easy for people to print the cards and to be able to pick and choose a subset of the Guide to print to cards if desired. Also, the printable content is slightly different than the web content since we have to reduce it to fit on printable cards, and we need a way to label/tag the printable content.
- Come up with possible workflows and prototypes that facilitate the creation, editing, and printing of the Inclusive Design Guide from a web copy.
- Example Workflow 1: provide a way to mark-up / tag / add metadata on the web copy to identify what to generate the print copy from
- Example Workflow 2: keep two separate copies of the web and print, and maintain a "diff layer" (see desctiption below) to reveal the differences / changes between the web and print copies (in order that the differences can be reconciled).
- Example Workflow 3: a combination of the above
- The web copy will be static HTML (i.e. not using a CMS like Wordpress).
- The print copy will be produced using Adobe InDesign (or other).
- this could also be done by creating an authoring/editing/templating environment into which the web content (or marked up subset of content) could be imported and then massaged into print copy. Normally the web copy has more graphics and text than the print copy because the printing is done on small pieces of paper (about 8.5 inches by 5.5 inches). So there will need to be a way to say what parts of the web content is to be printed, and what parts are for web only.
- Considerations should be given to ease of use, maintainability, accessibility, and standards compliance.
- A GSoC candidate will be responsible to researching workflows, documenting each approach, and implementing prototypes.
Mentor: Dana Ayotte, Jonathan Hung
IRC: danayo, jhung
Skills: HTML, CSS, Print workflows
Is this a coding project? What skills are required?
This is not a traditional coding project. Much of this project is researching possible solutions and workflows that will satisfy the project goal. A prototype or implementation can be created to demonstrate the feasibility of a solution.
What is meant by a "diff layer":
- A "diff layer" is some sort of middleware that tracks changes on either the print side or the web side so that maintainers can ensure that changes are reflected in both online and print.
Import External Data to MyL3
Project Description: ‘My Life Long Learning Lab’ (MyL3) allows learners to become experimental researchers in subject of their own learning. MyL3 not only provides custom tools for learners to track their personal data, but it also allows them to import data from external sources to the system. This would enable learners to track various factors in one place, find potential correlations that may impact their learning, and make adjustments accordingly.
This project focuses on importing data from the following external sources to the MyL3 tracker to get real time data into the system:
Development Mentor: TBD
Design Mentor: Sepideh Shahi
Project Description: AChecker is an online accessibility validator. It currently supports PHP versions up to PHP5. Also, some libraries used by AChecker, such as PHP HTML DOM Parser and PclZip, are no longer supported by their development team, which results in the same issue of being stuck at old PHP versions. This project includes:
- Upgrade AChecker to work with the latest PHP and MySQL;
- Replace or patch non-supported libraries.
Mentor: Cindy Li
How to get started: Interested students should start by cloning AChecker github repository, setting up a local installation, getting familiar with its design and the code base. When ready:
- Pick some simple bugs from AChecker bug tracker to work on. (Note that when using the bug tracker, please first select "AChecker" project from the "Project:" drop down list box at the top right corner.)
- Understand and create a list of parts that need to be upgraded, research on how to upgrade and present the research result in the proposal.
- When upgrading libraries, the order of the preferred ways:
- Replace with PHP built-in features whenever possible;
- Replace non-supported libraries with other libraries that are under active development and support the latest PHP;
- Write technology evaluations when selecting replacement libraries. Some examples of technology evaluation can be found here.
- Patch the library to work with the latest PHP.
Implement dynamic descriptions for an interactive PhET simulation
PhET Simulations creates free interactive math and science simulations. The project has over 55 HTML5 simulations with graphical interfaces that foster learning and exploration. We are now adding dynamic descriptions and content to the simulations so that they are accessible with assistive technology. This project will involve adding screen reader accessible descriptions and real-time alerts.
PhET simulations are implemented with a custom scene graph called Scenery. The Scenery API now supports setting accessible content for objects in the display. The project will involve using this API to enhance existing simulations with accessibility. Students will work on implementing accessible descriptions and alerts from a design document.
Mentor: Jesse Greenberg
How to get started: Interested students should start by familiarizing themselves with the structure of a PhET simulation. All code is open source, here is one example: Balancing Act. Interested students should also review the PhET Development Overview to get familiar with PhET's libraries, code style guidelines, how to set up a development environment.
Build a service for adaptive content and learning supports
Project Description: Many recognized supports for learning and comprehension of content (especially by students with learning differences or people with cognitive disabilities) such as dictionary look-up, translation, spell check, pronunciation and simplification are available via web-based APIs; others are available as open-source modules in various languages.
This project would explore building an application functioning as service to make it easier for different applications to make use of these kind of services, as each third-party service has different patterns for access, rate limiting, the open-source libraries have different APIs and levels of maturity, etc. The application would provide a consistent, simplified API via REST web services for functionality such as (these are examples only, many more possibilities!):
- Returning the three most common dictionary definitions of a word.
- Simplifying text.
- Translating text into other languages.
Some of this project would be working directly with third-party APIs, but a significant part of it would be working out a general design for a service that could grow in the future and add further features related to transforming content to support learning and comprehension. There would also be a research component to identify and categorize third-party services and modules of interest - some examples of online dictionary services and libraries are discussed here. The student would have the opportunity to establish a starting point for future work on an open middleware-type application that could be of significant use in areas such as education and accessibility.
Tag: fluid, scaffoldingapi
Mentor: Alan Harnum
How to get started:
Create Self-Paced "Live Learning" Infusion Tutorials
Project Description: To grow our community and engage with both expert and novice developers, the Infusion documentation site currently provides a mix of documentation and tutorials. Our tutorials are static documents with code examples that can be modified in real time on CodePen. This project would improve upon this by creating self-paced tutorials that encourage the user to verify their understanding of the material using live coding exercises. Live coding exercises present concrete goals to be reached and provide feedback in real time as goals are reached.
This "live learning" harness would require the learner to:
- Review prior art within and outside of the Fluid community.
- Create or extend a simple live coding harness like CodePen or the Fluid Sandbox.
- Define or adapt an existing structure that describes a "live" tutorial, including:
- The learning material to be read.
- Exercise instructions for each live coding scenario.
- The starting code, markup, and CSS for each live coding scenario.
- Clearly expressed goals to be reached in the live coding scenarios, and test conditions that can be used to verify when a goal has been reached.
- Break down one or more existing (or new) tutorials to use this structure, and provide a document to assist others in creating their own "live learning" tutorials.
- Create or extend a mechanism to record which tutorials and parts of tutorials have already been completed, so that learning can be broken up over multiple sessions.
The last point touches potentially on issues like user management and data privacy, for this project it's more likely the progress would be recorded locally, for example using the Web Storage API.
Mentor: Tony Atkins
How to get started: Go through one or more existing Infusion tutorials. Try out at least one of the live examples (usually linked via text like "Live Example of the code below on CodePen").
Project Description: Currently, there are no web-based user interface libraries that are inclusive of the needs of diverse musicians working with different platforms, devices, and interaction modes. This project involves collaborating with the Nexus.js, Flocking, and Fluid communities to add accessibility features to Nexus.js or a similar musical user interface library. Nexus.js provides a useful collection of musical UI components, but in its present incarnation, it is not usable by people with disabilities (such as those who use screen reader) nor by those who prefer to use the keyboard as much as possible. This project will include ensuring that the user interface components are:
- Responsive to different screen sizes and devices (e.g. phone, tablet, and desktop)
- Functional using both touch and a mouse cursor
- Navigable and controllable entirely with the keyboard
- Usable with assistive technologies such as magnifiers and screen readers.
This project may also involve writing adapters, as needed, for Nexus.js that allow it to be used more idiomatically with Fluid Infusion-based components.
To get involved in this project, please see the instructions on the IRC Channel page, which describe how to set up an IRC client so that you can join the #fluid-work chat channel, where many contributors to the Fluid community are available.
Tag: fluid, flocking, nexus.js
Mentor: Colin Clark
How to get started: Learn about Nexus.js. Go through one or more existing Infusion tutorials. Read about ARIA and accessible web user interface development.
Inclusively Design & Build a Game for Kids
Project Description: Young children often learn through play, exploration, and discovery. Kids who use eyegaze or switch interfaces are often limited to using games that have simple interfaces such as 'choose an answer' style games. This does not give kids a chance to play, discover, and explore. How can you create a game with simple enough controls that still preserves the ability to explore and discover through play?
An additional use case involves very young children who are blind. While sighted toddlers are swiping and playing digital games at an early age (and thereby acquiring digital literacy), their peers who are blind are unable to do the same. With the current games, until they have language, children who are blind are unable to acquire digital literacy. How can a game be created that works for toddlers who are blind and helps them begin a journey toward digital literacy?
It would be cool to develop a game for these kids. (This project will likely be done in partnership and close collaboration with Beit Issie in Tel Aviv, Israel and Bloorview Children's Rehabilitation Hospital in Toronto).
Tag: play, kids, education, exploration, fun
Mentor: Primary: Jess Mitchell; Technical: Alan Harnum
Skype: jesshmitchell on irc @jessm and @alanharnum
How to get started: Be excited and curious and willing to learn new things.
Most of the work we do here either uses or directly involves the Infusion Framework and Component Library. These links should get you started learning about Infusion, and should lead you to many more pages.