Accepted

This is an introductory presentation for beginner and intermediate web designers/developers highlighting how users with assistive technology interact with web content. Brief demos of text to speech, screen reading software, speech to text and alternative inputs will be provided. Research studies exploring common web accessibility barriers and solutions will be discussed. Microsoft’s Accessibility Checker will be demoed and how it can be used to create accessible Microsoft & PDF documents.
Learning Objectives-

We are successful to establish our development process for Drupal 9 custom module incl. automated testing for PHPUnit by our own GitLab CI/CD pipeline (like d.o's automated testing).

As a next step, we have learned Behavior-driven development by Behat to automate to run the acceptance tests for Cloud Orchestration modules. The session will cover how we can use the tool like Behat and write the test scenarios.

Multiple stakeholders, competing priorities, not enough time, and not enough resources. How can you effectively do meet every website need? Should you? In this session, we'll dive into a strategy and approach for forming a website roadmap that wisely supports your organization's business and delights your target audiences.

View the presentation

Layout Paragraphs is a contributed Drupal module that combines drag-and-drop editing, Drupal core's layout API, and the Paragraphs module to provide an accessible, easy-to-use authoring experience. Designed to empower marketing and editorial teams everywhere, Layout Paragraphs offers a WYSIWYG interface for publishing highly visual, long-form content.

In this session, we'll demo the capabilities of Layout Paragraphs, explain how it differs from core's Layout Builder, and show participants how to implement Layout Paragraphs in their own Drupal websites.

Drupal includes a powerful toolset for building and extending out-of-the box content types. Content architectures are typically designed around the features of nodes, taxonomy, media, and other core entities. But how do we know when our business-needs have grown beyond the common entity types? When are nodes too lightweight or too heavy handed to meet our site goals? And what are the trade-offs and support issues when creating a new entity type?

WordPress' editorial experience was recently revolutionized with the introduction of the Gutenberg block editor. Under the hood, it uses React as a single-page application (SPA) allowing content teams to create, edit, and delete content with a dynamic component-based approach. This session will demonstrate how a basic custom Gutenberg block is developed and added to a WordPress website.

Your institution probably has a dedicated section of its website, or a stand-alone website that helps recruit new students and guide them through the admissions process. Sometimes a faculty or school will have a similar section of the website that describes the application process and all the programs and requirements. These sections and websites often play the role of the digital front door of your institution. The first touch-point that a potential student has when they’re researching which school to attend.

Calling all members of the WordPress Archipelago in the Drupal Ocean! The WebTech team at University Communications is resurrecting the WordPress Community of Practice. Please join us to hear about our development efforts, share yours, and get to know each other.

At Stanford, students, faculty, and staff rely on numerous applications and systems to get their work done. The usability of those systems directly impacts the experience that people have, and how effectively and efficiently they can complete their work. In this session, you will learn a basic understanding of system usability and how to spot usability issues.

The Office of Digital Education at the University of Colorado recently transitioned from building Request for Information (RFI) forms in Formstack to Webform on https://online.cu.edu/. Not only did this eliminate the Formstack licensing costs, but it allowed us to build a solution that inherits information from the Program Pages the forms are placed on. We were able to reduce number of forms from 170 in Formstack to 4 Webforms that inherit values from the pages they are placed on.