Accessibility is essential for developers and organizations that want to create high-quality websites and web tools, and not exclude people from using their products and services. If you’re in charge of your website, you have a lot of things to cover between keeping it up to date, entering and managing content, and making sure it's all accessible.
As part of an inclusive content strategy, how accessible is your media?
A headless CMS allows content creators to manage their content through a familiar admin interface and providing the content via API endpoints, allowing developers to implement a fully customized front-end experience using reusable components and a modern framework as React.
A core feature of Gatsby is its ability to load data from anywhere (GraphQL endpoint in our example). This is what makes Gatsby more powerful than any other static site generators that are limited to only loading content from Markdown files.
A web site, especially a Drupal web site, isn't just a collection of independent web pages with blobs of text; it's a meaningful presentation of structured information. Ideally, for content editors, it also follows the principle of "Enter once, display many times". For example, enter each staff member & their details just once, but display that information on a staff directory page, on each staff member's individual details page, on an emergency contacts page organized by responsibility, etc.
We often talk about websites the way we talk about cars. Are you driving a flashy sports car or a stable hatchback? And is yours a lemon, no matter how pretty the paint job? And if you just got one used, what’s going on under the hood? There’s a way to address these questions about your website, and it’s called a technical audit.
This case study involves working with a chemical company. The initial scope of the application was to collect, analyze data and add visualization using JS charts
We proactively suggested building a chatbot integrated with an application.
Chatbots workes on the “AMA approach [Ask me Anything]” and on simply asking a query, the bot would analyze necessary data to answer.
This year we celebrate 4 years since Drupal 8 was released. A one-click upgrade from older versions is one of its greatest features, thanks to the Migrate module being in core. While Migrate is powerful, it lacks a good UI. In contrib, we have Feeds for importing content. This module does have a UI perfectly tuned for site builders, but it defines its own import framework. Wouldn’t it be great if the two frameworks could be combined together?
This session will cover two challenging topics together: multilingual websites and 508 compliance.
We’ll cover the basics of how supporting websites in multiple languages affect assistive technology and find out if the Google Translate widget will be enough to meet multiple levels of compliance.
UPDATE: The presentation I'd planned to give was about how to be ready for a disaster tomorrow -- and now that we are *in* a disaster, that hardly seems valid -- but perhaps I can pass on other lessons I have learned from previous disasters to be more helpful to everyone today.
Current events are very similar to my experience at ground-zero during Katrina -- and that includes emotionally. This is pretty personal to me -- and deadly real (see below).
Matching is a very common process used in academia for classes, clinics, summer trips, etc. We built several Drupal-based applications, and decided to create a stand-alone module for this process. In this session we will talk about how our module implements solutions to a Stable Marriage Problem https://en.wikipedia.org/wiki/Stable_marriage_problem.
We will go through objects/relationships/code and demo how our applications are using this module.
