For these designs, I have focused them all on being text based, and to the extent possible, minimalism. Optimizing for these features, in particular, seeks to be accessible to blind users, for it should (hopefully) work well with screen readers, and we only present as little content as we possibly can such that they may be able to navigate the page quickly.

The main site navigation has two main navigation bars. The top bar will contain on the left notifications and messages indicator with links to the respective pages, and to the right your standard user account management. The right bar will contain simple text links to all of the main components of the site, and clicking on any link will load the relevant content into the "Content" section.

The messages page is barebones, showing only the sender, subject and date. Ideally there may be a search function of sorts for this, but that will very much depend on feasibility. Compose view is only three fields, which is enough to just barely get the job done.

The home page will contain the sign in/sign up page. The main focus will be these two mechanisms in the middle of the page, in a widget that can switch tabs between the two. The benefits of this design is that it should make signing in/up super simple. We only ask of the user as little as we really need to in order to create an account, or access their account. There will additionally be some links at the bottom of the page with the standard contact, about, etc... that lead to the relevant content.



This is the main calendar overview page. At the top there's an "add event" link which takes you to a page where you can fill in all of the details and have it be added to the calendar. 

The display mode draws heavily from the Google calendar "agenda" view, as that itself is a text representation of the calendar and fits our purposes well in this case. We initially first show the next seven days on the agenda, and at the bottom there are links to display even more days. Next to the event relevant details are displayed, such as if the event has not been assigned to a parent (and as such transport needs to be assigned) or if the event is assigned to you it makes note of that (bolding or otherwise highlighting the event) and displays all of the relevant "at-a-glance" information. This page was designed also with the idea that one could simply print out what is shown on that pane and carry it around, for the benefit of low-tech parents.

  • No labels