WCAG 2.0 AA Compliance Verification Project

The main goal for the project is to verify and audit WCAG 2.0 AA compliance of 10 resources (slide decks) that have been transcribed into an accessible format. This includes verifying the correct shape/structure of graphs, correct semantic MathML, and correct semantic HTML5. Visually impaired students seeking this position should get at least one sighted peer to also apply so that they can verify visual elements.

Semantigram Website Development

The main goal for the project is to create a website for the new Semantigram project, aimed primarily at the visually impaired. The website must have two high contrast styles, be fully accessible and WCAG 2.0 AA compliant, and be written using a static site generator. Additionally, the site may not contain JavaScript, must function without external server access, and must be mobile-responsive. The website should also not use a CMS like Wordpress or Tailwag.

Rust Text-to-Speech (TTS) Project

The goal of this project is to build a simple Text-to-Speech (TTS) system using the Rust programming language. The code must be written using Rust and no_std, and the TTS must be completed using pure Rust. The TTS must support at least English but a second language, French preferred, would be good as well. The project is for Bytetools Technologies Inc., a company dedicated to helping blind and visually-impaired students with their post-secondary schooling in STEM subjects.

Minutes Tracking System (Bytetools)

We would like students to help in the creation of a new API for our company. This API will consist of at least 3 major sections: Jobs, Employees, Minutes. We need to be able to bill for a fairly specific amount of time for each of our employees so that initial work, QA, review, etc. can all be listed on an invoice and our employees get payed fairly. The creation of the invoices will be relegated to a separate system and will not be required as part of this project.Students should be prepared to:Create an API design proposal.A simple mock-up with "fake" responses (no database) is not required, but is preferred.Implement the API so that it can be accessed from any programming language using JSON (de)serialization.Give direction on how to maintain the project going forward, including but not limited to which libraries and frameworks were used in the creation of the API and any potential breaking changes announced from those libraries in the near future.