Upgrade Your Drupal Skills

We trained 1,000+ Drupal Developers over the last decade.

See Advanced Courses NAH, I know Enough
Jul 29 2020
Jul 29

It’s been nearly five months since COVID-19 was declared a global pandemic and a national emergency. This, of course, is not how any of us imagined 2020 would play out when marketing plans were put in place at the start of the year. Despite the disruption and tragic human toll during the Spring months, there was widespread expectation that the pandemic would be headed for the history books by the third and fourth quarters.
 
Turns out, the pause from business-as-usual is not going to be brief. The disruption and human toll continues.
 
Whether or not we took the initial lockdown seriously enough, or attempted to reopen too soon, one fact is without dispute at this point: COVID-19 is going to be with us for a while and “normal” could be a long way off. 

So what does that mean for marketers?

Multiple Marketing Dilemmas

When customers and constituents are dealing with mounting upheaval and uncertainty on multiple levels, business-as-usual marketing campaigns run the risk of appearing tone deaf. At the same time, audiences are weary of the multitude of voices weighing in on COVID-19.

So how are the most perceptive and forward-thinking organizations regrouping and rethinking marketing and messaging five months into the pandemic? 

There’s a lot of soul searching going on and, in many cases, there are similarities between positive new directions within organizations and within homes. 

Renew and Refresh

At home, many have decided that now is the time to dive deep into big picture goals such as fitness, new hobbies, online classes, or intellectual pursuits -- tapping into the types of goals that tend to get pushed aside during normal daily life when commuting, socializing, and activities that call for being in close proximity or physically present take up a major chunk of time.  

Organizations are actually taking a similar approach to the “What Now” question. Studies show that to an increasing degree, preparations for the post-pandemic rebound are directed toward better web experiences that are impeccably aligned with user needs and expectations.

There are a host of reasons why website content audits, redesigns, redevelopment, or fixes that are taking many different forms are proving to be the best focus of organizational energy and marketing dollars right now.

Here are our top five:

1. Websites and web experiences are now a defining factor.

Long before the pandemic hit, Promet noted that organizations were increasingly defined by their digital presence. That reality emerged to the forefront as social distancing and shelter-in-place orders created a reliance on online engagements as the primary connection to the world. As websites have been called upon to do more heavy lifting than ever before, opportunities for excellent UX have come into focus, and users’ patience with sub-par experiences has worn thin.

2. This defining factor and digital hub needs to strategically reflect new realities.

COVID-19 has shaken modern life to the core. Historically, new design trends follow massive social upheaval, for good reason. After emerging from a constant stream of dire news, users are looking for bright spots, a breath of fresh air, and a reassurance that life is on track to be back to normal. The post-pandemic climate will present a powerful opportunity for renewal and reinvention. At Promet Source, we are anticipating an overall trend toward brighter colors, whimsical styles, and simplicity. For websites, this might mean a fresh, new color palette, bolder fonts with smoother edges, brighter images, and a renewed organization of previously complex menus and data.

3. Competition will be aggressive and strategic.

Marketing and advertising budgets were slashed at the start of 2020 as consumers lost their jobs, had less to spend, and were discouraged or forbidden from engaging in activities that fuel key sectors of the economy. While the timing of the economic rebound is uncertain, pent-up demand is undeniably huge. When the economy rebounds organizations will need to have a strategic response plan that includes an intentional, up-to date digital presence. 

4. Data and analytics will serve as stronger drivers of strategic decision-making.

Most organizations' websites are set up on Google Analytics, but often key intelligence is missing from the set-up. Now is the time to ensure that the web analytics are aligned to fully leverage user data. Great data and analytics will be required to achieve the next level of decision support intelligence. 

5. For Drupal users, migration to Drupal 9 is inevitable.

Drupal 9 is here. Drupal 7 and 8 are on the way out. Even though the Drupal organization has extended by one year the decommission date for Drupal 7 and 8, migration to the latest version is still required and this current downtime represents the perfect opportunity for upgrading to a far superior CMS and user experience.

At Promet Source, we tend to believe that there is never a bad time to make a website better aligned with market demands and current branding. In the current environment, the factors supporting website upgrades are more compelling than ever before. Contact us and let's talk about possibilities for getting ahead of what’s next. 

Jul 20 2020
Jul 20

Most Drupal devs are familiar with hook_entity_access(and its cousins hook_ENTITY_TYPE_ID_access and hook_node_access). However, it is mostly used for serving “403: Access denied” to browsers.  And we use a separate hook, hook_form_alter to disable edit buttons on admin pages like content overview pages, node form edit and taxonomy form edit:

hook_form_alter vs. hook_entity_access

It would be more beneficial to use hook_entity_access to disable access to the buttons. Disabling view, edit or delete (where applicable) via hook_entity_access will handle the following all at once.

Advantages of using hook_entity_access

1. Serve 403 pages

As mentioned above, this is the typical use for hook_entity_acess. Users will be served 403 if access denied is returned by the hook.

2. All views listing page with entity operations

All views entity operations are already handled.  This is the most significant benefit, as you don’t have to hook_form_alter each of the listing pages in your site.  By default, it will respect hook_entity_access.

hook_entity_access defaultdefault entity operations in views


3. Core Node Form / Taxonomy Form (Any default entity form)

The entity form delete button respects hook_entity_access, as is shown by the following image that depicts the delete button in the Drupal node admin interface.

hook entity access

4. Tabs / Local Tasks


The default core edit/delete tabs also respect hook_entity_access, as is shown by the following image depicting the admin tabs available for editors.
 

tbd

5. $entity->access() checks

$entity->access(‘view|update|create|delete’) respects hook_entity_access. So in code, a deny in hook_entity_access ‘view’ operation will also result in a deny in $entity->access(‘view’).  

At the heart of what we have talked about above relies on this behavior.  All items above internally execute $entity->access() checks.

Caveats on using hook_entity_access:

1. Allow / Deny rules

If at least one module issues a deny, then it will result in access denial, even if your module provides an allow access (other modules should only set a neutral access so that it does not inadvertently deny access to the entity). 

At least one module must provide an allow access to an entity in order to provide access.  If all modules give a neutral response, then it will result in an access denial.


2. $entity->access also respects the node permissions page (for node entities) in conjunction with hook_entity_access()

In the Permissions (/admin/people/permissions) page, you can set whether a certain role has access to edit, delete (own/any) content type.  Internally, this also provides an access result allow when enabled, and the same Allow/Deny rules above apply.

This must be taken into consideration when combining hook_entity_access with permissions page.  So even if you issue a neutral access, you might wonder why something is still giving access.  This might be given through the permission pages.

3. Other operations

By default, Drupal core provides ‘view’, ‘update’, ‘delete’, ‘create’ access.  And you can further filter the access via operation type.  Internally, this translates to $entity->access($operation).  

Modules like content translation provide other entity operations apart from the basic ones above.  In particular, content_translation core provides a ‘translate’ operation. In your hook_entity_access.  You can then expect a value of ‘translate’ on $operation, when for example, rendering the translate button on the pages described above.

You can find hook_entity_operation[_alter] in order to define/alter entity operations.

Additionally, the other operations might intentionally depend on the ‘view’ operation, etc.  In particular, content_translation module also depends on the ‘view’ operation in showing the translate button.  Denying access on view operations will also deny access to the translate button.  So special conditions must be added for such instances.

caching based on theme and entity

 

4. Caching permissions

Be sure to set proper caching to AccessResult returned by hook_entity_access.  

In this example, $entity was added as a caching dependency to AccessResult and also the current theme used.

caching based on theme and entity

Looking for Drupal consultation and support for your complex website development?? Contact us today.

Jul 13 2020
Jul 13

Drupal 9’s big splash in early June sparked a widespread realization that migration needed to move to front burner status in anticipation of a Nov. 2021 decommission date for Drupal 7 and 8. That sense of urgency has been temporarily tabled as the Drupal organization took the widespread uncertainty and upheaval of the global pandemic into account, and moved the end-of-life date for Drupal 7 and Drupal 8 out by one year to November 2022.

So now what?

How does this date extension change how site owners should be approaching migration? What’s in store for Drupal 9? And what else do we need to know right now? 

Subscribing to the Kenneth Blanchard conviction that, “None of us is as smart as all of us,” we reached out this week to some of Promet’s top experts for insights into these and other important issues.

Here’s what they had to say:

Drupal 9 Expert Panelists

Juan Garay, Project Manager, Scrum Master
Luc Bezier, Solutions Architect
Aaron Armstrong, Drupal Developer
John Ross Castano, Web and Support Developer

Q. Now that the Drupal Organization has extended for one year -- from Nov. 2021 to Nov. 2022 -- the decommission date for Drupal 7 and 8, is there a compelling reason to migrate now?

Juan: I wouldn’t suggest migrating to 9 now, as there are many contributed modules that are not available for Drupal 9 yet.

I would tho encourage anyone to migrate from Drupal 7 to 8 ASAP, as the improvements between Drupal 7 and Drupal 8 are far and many.

Also, migrating right now from Drupal 7 to Drupal 8 will make for a much smoother migration path to Drupal 9 in the future, as Drupal 8 to Drupal 9 migrations (content in particular), are meant to be considerably smoother than migrations from previous versions of Drupal.

Aaron: November 2, 2021 is still the date that we need to focus on as the effective end-of-life date for Drupal and 8. Drupal is dependent upon Symfony, and Symfony will no longer be supported after November 2021. Security patches are all that will remain available after that date. My recommendation for any website that’s still on Drupal 7 is to move forward now with a migration to Drupal 8, and then as Drupal 9 matures, build out a Drupal 9 migration timeline. 

Q. What do you view as the primary, overarching benefit of Drupal 8 and 9 over Drupal 7?

Juan: In Drupal 8 and Drupal 9, nearly the entire system uses the Drupal Entity API, which provides a much more robust and flexible framework for building custom solutions.

John Ross: Drupal 8 and 9 have improved over Drupal 7 by leaps in bounds in terms of deployments through Configuration Management (and content). Automatic deployment is a breeze between environments and has become very robust since Drupal 7. This is one of the biggest issues or dilemmas on our multi-environment development workflow when using Drupal 7. Drupal 7 heavily relies on Features and other similar modules, but cannot really provide a “one-size-fits-all” solution for an automatic deployment.

Aaron: The deployment and configuration export/import is the biggest benefit for Drupal 8 and 9. It saves hours upon hours of work, which previously was accomplished with Features. 

Also, there are a multitude of contributed modules in Drupal 7, which are now core modules in Drupal 8. Translations are a huge example. Drupal 8 comes ready, out of the box, for translations. Drupal 7, on the other hand, required loads of contributed modules and configurations to accomplish the same thing. 


Q. Drupal 9 has been described as akin to more of a “point release” from Drupal 8 than the Drupal 7 to Drupal 8 leap forward in features and functionality. So what is new or potentially game-changing about Drupal 9?

Luc: Drupal 9 is not a game changer, in the sense that Drupal 8 was. Drupal depends on Symfony, if you were to very quickly summarize, you could say that Drupal 9 is essentially a new version of Symfony under the hood. Drupal 9.0 has the same features Drupal 8.9, with a clean up of some functions that it was using. The aspect of Drupal 9 that is game changing is the fact that it is the first release for Drupal to be non-breaking. You don’t need to process a major migration to update, it is relatively easy to migrate from Drupal 8 to Drupal 9. 

Aaron: Drupal 9 solidifies some of the features in Drupal 8. As others have mentioned, it also is a very easy upgrade between Drupal 8 and 9. Up to this point, Drupal migrations have been time-consuming process. 


Q. Drupal 7 was released on Jan. 5, 2011, nearly 10 years ago. Can you comment on some of the most significant trends in UI/UX or within Drupal functionality that have emerged since that time?

Juan: Among the most significant developments is the ability to edit content inline, in real-time through the Drupal 8 Layout Builder interface

Luc: During the development of Drupal 8, I remember meeting Alex Pott (Drupal 8 core co-maintainer, and Drupal 8 configuration system co-maintainer). I worked with him on some changes to the configuration system. This system is for me the biggest improvement in the way we build and maintain large websites using Drupal 8 and above.

Aaron: The use of importing and exporting configuration yaml files is the most significant change from Drupal 7. The default back-end theme has improved greatly, along with the number of core modules in Drupal 8 and 9. 


Q. How have businesses and organizations changed in their use of and need for Drupal over the past decade?  

Luc: The complexity of websites have increased, and thanks to Drupal’s level of abstraction, we are also able to build more complex solutions. For example, it is common for large companies or administrations to have more than a dozen of websites now, and using Drupal with tools like Acquia Cloud Site Factory, one company can generate websites on demand.

Aaron: Drupal has always been an enterprise type CMS that works well with larger sites. I think it has continued to work in that space, while allowing for much more complex sites, deployments, and configuration sharing.

There also have been huge leaps ahead with the hosting provided by Acquia and Pantheon. 

Q. What do you view as the most significant Drupal evolutionary developments over the past decade?

Aaron: The possibility of headless Drupal is what first comes to mind, but the configuration management, as well as translations being part of core, are the biggest advancements in my opinion.

Luc: The past decade saw the emergence of static sites generators (Jekyll in Ruby, Hugo in Go). I find it very interesting as it is removing all the overhead of modern websites for performance and maintenance. Nothing will ever be faster than a plain HTML page. A module like Tome (by Samuel Mortenson) bridges the gap between Drupal and the static sites generator solutions, allowing Drupal to be automatically exported as plain HTML. This opens some interesting possibilities for Drupal.


Any other questions on Drupal? Drupal 9? The path to migration? Drupal is in our DNA at Promet Source and we are happy to help. Let us know what we can do for you!  Contact us today


 

Jun 30 2020
Jun 30

When Lehigh University set out to redo its website for prospective undergraduates, one overriding factor was crystal clear to the staff members and stakeholders who were making the key decisions concerning the site. The cohort of digital natives to whom the website needed to appeal, was likely to have different ideas about web navigation and the kinds of site structures that make the most sense. 

There was also no question that the stakes were high for getting it right. Gen Z has high expectations and little patience for web experiences that are confusing. When prospective undergraduates deemed a college website to be sub par, it could stop their search in its tracks. 

As a leading research institution, Lehigh University’s determination to get it right was guided by  an approach that characterizes the university’s angle on most endeavors: questioning assumptions, digging deep, and backing up decisions with research.  

 

High-Stakes Inquiry

Working in concert with Promet Source, Lehigh University proceeded with a three-tiered website usability testing process that included one-on-one recorded interviews with prospective undergraduates, in which interviewees were asked to share their screens and navigate different menu options for specific information. These screen shares were recorded to allow navigational experiences and trouble spots to be analyzed closely, with a greater depth of insight than could be gained from simply stating preferences.


Read the Case Study on Usability Testing with Prospective Students

Additional research included online, self-guided assessments of the same navigation menus from a much wider statistical base of the same cohorts. Stakeholders also participated in a self-guided assessment of menu options to help highlight potential differences in web navigation menus that made the most sense to staff vs. potential undergraduates. 

Interested in gathering data and perspective to ensure that your new site hits the right target with the right audience? Contact Promet Source.
 

Jun 25 2020
Jun 25

Website redesign decisions often percolate for months, if not years, before action is taken and the team dives in for a do-over. Prior to taking the plunge, there tends to be a lot of low-grade dissatisfaction that gains momentum, as more and more conversations focus all the ways that operations would run smoother, marketing would work better, or all of the tasks that could be offloaded to the website if only navigation was simpler or the site was up to date. 

During my many years in the web design and digital strategy world, I’ve witnessed lots of discontent over existing websites. Here are eight indicators that it is truly time to take action.


1. Your information architecture is organized around your org chart and not user needs.

Too often, websites are architected from the perspective of insiders -- organized by department, without stepping back to ask: Who visits the site? What kinds of information are they seeking? How can we align the navigation of the site around what makes sense to users? The best web experiences leverage radical empathy, and begin with Human-Centered Design processes that dig deep and question any all assumptions about how users interact with the websites can it be designed so that information is easier to find and the experience of visiting the site is engaging and value added.
 

2. Your site isn’t mobile responsive or accessible.

Web designs in the current world need to work equally well on a wide range of screen sizes and different orientations -- from tiny hand-held screens to oversized desktop monitors. Responsive websites also tend to load faster, which is a critical component for a positive user experience, as well as a big factor in better SEO rankings. Your site also needs to adhere to current Web Content Accessibility Guidelines (WCAG 2.1) to ensure compliance for users with a wide range of disabilities. 
 

3. Your user interface (UI) is dated or dull

Expectations are high and patience is low in the current world of online engagements. Once web users get accustomed to well-designed, aesthetically pleasing sites, they have little patience for an outdated design elements. Colors, typography, images, and layout need to align with your brand, make sense to users, and present a balanced, uncluttered flow of information. When this not the case, it takes a toll on your business.
 

4. Your user experience (UX) is sub-par

More so than ever before, web experiences that are difficult to navigate can cut visits short, drive away customers, and reflect poorly on your overall brand. Don’t underestimate the degree to which a frustrating web experience can turn off -- or even enrage -- users. At the same time, a web experience that is built upon an understanding of pain points in order to create an engaging, streamlined and uncomplicated experience is a true delight that can significantly boost many aspects of your marketing objectives. 


5. Your content is outdated.

Ensuring that website content is up-to-date may sound like an obvious objective, but when web experiences start to lag behind what’s going on in the organization, the impact can start to snowball. Quickly, it’s not just the content that’s out of date, but the branding, the messaging, and the overall tone might all fall out of alignment -- not to mention lost SEO opportunities. While a redesign can get a website in sync with the current organizational vision, migrating to the most up-to-date CMS ensures a framework for more easily making changes that keep your content up to date.

6. You are increasingly suffering from “website envy.”

When online experiences consistently spark a sense of “Why can’t our site do that?” or “Why doesn’t our site look more like this?” It’s time. Your site can step up, and serve as a strategic driver in an environment in which your web presence is an increasingly defining factor for your organization, your brand, and your values.

7. Your website uses Flash.

Once the dominant software platform for production of animations and embedded web browser video players, Flash has long since fallen from favor. In 2016 Adobe announced that at the end of 2020, it would be ending support for support for Flash. If your website uses Flash, or other outdated technologies, that’s a good sign that you can benefit from a redesign and migration to up-to-date solutions. 

8. Your CMS is no longer supported or is soon to lose support. 

Both Drupal 7 and Drupal 8 are heading toward end-of-life status, after which point, the Drupal community will no longer be maintaining either version. For websites that are currently on Drupal 7, this end date represents a much-needed incentive to migrate over to a far superior CMS and a vast array of new features. Websites that have already migrated to Drupal 8 can count on a seamless upgrade to Drupal 9 that’s more akin to a point release. The migration process is an absolute ideal time to also redesign a site. In fact, combining the two initiatives represents an opportunity to create alignment among functionality, look and feel, branding, UI, UX -- every objective that your website is intended to achieve.

As Vice President of Digital Experience for Promet Source, the most gratifying part of my work involves helping to shepherd the transformation of websites from a source of frustration or simply a functional presence, to a beautiful experiences that ignites new digital possibilities. We’d love to talk with you about challenges with your current site and all that you hope to achieve with a redesign. Contact us today!
 

Jun 18 2020
Jun 18

With this month’s release of Drupal 9, factors fueling migration have moved up a few notches, but as the November 2021 decommission date for Drupal 7 and 8 rapidly approaches, there’s one huge factor that’s superseding all others. Drupal 7 and 8 are both heading toward end-of-life status. 

Now is the time to accept the inevitability of a migration to Drupal 9.

Free Webinar! 6 Steps to Streamline Drupal Migration

While a commercial vendor might step up to provide support for websites that are on a Drupal 7 or Drupal 8 platform, the Drupal community won’t be maintaining Drupal 7 or 8 after Nov. 2021. 

Ultimately, that’s a good thing. If your site is currently on Drupal 8, migration to Drupal 9 will be refreshingly straightforward and seamless. If your site is currently on Drupal 7, a far superior CMS and a vast array of new features are in store. 

Among them:

  • A built-in visual layout builder
  • Enhanced testing and tracking to ensure accessibility compliance 
  • Full multi-lingual support  
  • Assurance of accessibility compliance 
  • Simplified content editing capabilities 
  • Integrated configuration management  
  • The ability to easily control how, when, what, and to whom content is displayed
  • Adept integration of complex functionality and content types
  • Tailored solutions to drive business or engage constituents
  • Excellent security

We covered the straightforward Drupal 8 to Drupal 9 migration process in a blog post earlier this month: Drupal 9 Has Dropped! What to Do Now

For the more than 700,000 websites that are still on Drupal 7, migration looms large on the to-do list. For all practical purposes, Drupal 8 and 9 are a different CMS than Drupal 7. With the complete overhaul of Drupal 7 that resulted in the enterprise-ready Drupal 8, version upgrades are now incremental. 
 

Migration Starting Point

The best and most efficient place to start the migration process is an audit of the current site with the objective of inventorying, categorizing, and rationalizing all content. In a blog post last fall, we compared the initial inventorying process to a household decluttering initiative: A Marie Kondo Inspired Guide to Content Migration.

Dividing the migration process into the following six sequential steps creates a framework for avoiding shortcuts that lead to pitfalls, while ensuring a consistent path forward.

  1. Audit the existing content
  2. Consider the design
  3. Plan the migration
  4. Build a New Content Model
  5. Map the Content
  6. Execute the Migration 

 

Content Audit Considerations

Often, tough choices surrounding what content to keep and what to let go of. 

Fact is, organizations are constantly evolving and the content on a site too often lags behind. Here are some questions to ask for evaluating the relative value of various pages and the content that’s on them:

  • How old is the content? One year? Five years? 
  • How does it rank for page visits?
  • How integrated is the content to your messaging?
  • Are there redundancies?
  • How does it rank on the spectrum of trivial to essential?
  • Does the content drive engagement? Revenue? SEO?
  • Are there regulatory considerations that require the content remain?
  • Are there roles and permissions concerning content governance and workflows?
  • Is this documented?

 

Design Considerations

Migration is the ideal time to redesign a website, or at least to define and determine essential design issues. To cite a few:

  • Is structured content in place?
  • Is CSS used to indicate heading styles, fonts, the color palette, quote style, ordered and unordered lists, buttons, hover states, etc.  Does the design reflect the brand?
  • Is the UX aligned with current expectations and best practices?
  • Would a modern refresh help to engage constituents and clients?

 

Join Us to Learn More!

Thorough time and attention to these initial steps will serve to lay the groundwork for a streamlined website migration that stays on course without pitfalls and unwanted surprises.

Never before has it been more essential for websites to ensure user experiences that offer a straightforward path to desired objectives, compelling content, engaging visuals, and added value. 

Looking for more insights into  wrangling your content, redesigning your site, or mapping out a migration?

Register Now for a FREE Webinar! 
6 Steps to Streamline Drupal Migration 

When:
Wednesday, July 15, 2020
11 a.m. CST

Any Drupal-related questions or concerns in the meantime? Drupal is in our DNA and we are happy to help! Contact us.


 

Jun 09 2020
Jun 09

Drupal 9 is here at last.

The big question within the Drupal sphere as we enter this new phase in the evolution of my favorite CMS: 

What now?

In an environment of Covid-19 quarantines and stay-at-home orders, websites are being relied upon to do more heavy lifting than ever before.  I’m passionate about helping organizations to ensure optimal benefit from their Drupal sites, and as I consult with clients every day on how to most effectively move forward, here are the kinds of questions that I hear most often:
 

Q. What are the most exciting or game-changing features of Drupal 9?

Key benefits of Drupal 9 include: 

  • a built-in visual layout builder, 
  • enhanced testing and tracking to ensure accessibility compliance, 
  • full multi-lingual support, 
  • assurance of accessibility compliance,  
  • simplified content editor capabilities, and 
  • integrated configuration management capabilities.

But the most exciting feature of Drupal 9 is what it isn’t. It isn’t game-changing. The migration from Drupal 8 can be a straightforward process and this represents an important evolutionary development for Drupal. If a site is currently working on Drupal 8.9, then the upgrade to Drupal 9 will be more like a point release -- not that different from going from Drupal 8.8 to Drupal 8.9.

The migration to Drupal 9 will, however, require the removal of any deprecated code or APIs that are still used in the site.


Q. How do I know whether my site relies on deprecated code or APIs, and if so, what do I do about it? 

There are a few options and some great tools to guide you through that process. My Promet colleague, Aaron Couch, addressed that very topic last week in a blog entitled, Drupal 9 Has Dropped! What to Do Now. The process that he outlines is more succinct and straightforward than anything else I’ve read on the topic. 
 

Q. To what extent does Drupal 9 reflect the evolution of the Drupal community?

Many of us know about the pain of migrating from Drupal 7 to 8, and many appear to be actively avoiding it. In fact, there are more than 700,000 Drupal 7 websites that still have not migrated to Drupal 8, even though Drupal 8 is so much better in so many ways. 


Moving forward, migration challenges will never again be such a bottleneck to having access to the benefits of a new release. Drupal 9 represents the cumulation of the vision implemented with the complete overhaul that resulted in Drupal 8.

For all practical purposes, Drupal 8 is a different CMS than Drupal 7. 

Drupal 8 was built as an enterprise-ready CMS, with the idea that future major version upgrades would be incremental, not evolutionary changes, and that’s the case with Drupal 9.
 

Q. Do you anticipate that Drupal 9 will draw in new types of users?

I don’t expect Drupal 9 to be a major event at all, and that is a good thing. It’s simply what comes after Drupal 8.9. Some changes in Drupal 8 over its lifespan, particularly the Layout Builder features that enable very powerful drag-and-drop page-building capabilities, should make Drupal more appealing to organizations that want to distribute content creation and management throughout the organization.
 

Q. So is there a compelling reason to migrate to Drupal 9 from Drupal 8?

Drupal 7 and 8 will both hit end-of-life status at the same time, in November 2021. So staying on Drupal 7 or Drupal 8 won’t really be an option after November 2021.


While the Drupal community won’t be maintaining Drupal 7 or 8 after Nov. 2021,  a  commercial vendor will likely seize the opportunity to provide a commercial support option.

Drupal 9 is just the update that comes after Drupal 8.9. For all practical purposes, you are staying on Drupal 8. It's just that Drupal 8 is constantly evolving, and because we are out of single-digit numbers to the right of the decimal point at 8.9, the next update gets called Drupal 9.0.

Also, the change in digits is a convenient place to clean out the deprecated code in the code base that you should have stopped using by now anyway.


Email me if you want to set up a call to discuss the differences further, or for help with any Drupal-related questions that you might have.

Q. How would you compare a D7 to D8 migration to a D8 to D9 migration?

Imagine you drive a Toyota Camry and fortune smiles on you and are gifted a 2020 Ferrari 488 Pista. It’s still a car, but you will basically need to relearn how to drive. That is D7 to D8 from the developer perspective. The content editor/writer perspective is more like going from the Camry to a BMW. It’s just a nicer version of what you already had.

D8 to D9 will be like taking the Ferrari in for a tune-up.

We at Promet Source are here to help with all any Drupal-related questions and website migration issues. Contact us anytime.


 

Jun 02 2020
Jun 02

The long-anticipated drop of Drupal 9 has arrived. This marks an exciting step in the evolution of Drupal. A migration from Drupal 8 to Drupal 9 is not as complex and cumbersome as previous version releases. Drupal 8 to Drupal 9 will be an upgrade that is more akin to a point release.

If you are not prepared to upgrade to Drupal 9 immediately, you are not alone.

Sign up for a free migration consultation and explore your options for a path forward. 

Both Drupal 7 and Drupal 8 are not slated for end-of-life status until November of 2021, but now is a time to begin planning for a migration and understand what that will entail. To help in that process, we created a Drupal 9 Upgrade Planning Template for migrating from Drupal 8 to Drupal 9.

spreadsheet screenshot for a Drupal 9 migration

The upgrade plan involves the following steps:

Install Upgrade Status or Drupal Check

Installing the Upgrade Status module or the Drupal Check utility is the essential migration planning starting point. The former provides a report in the Drupal user interface to give you a list of what deprecated code you still have. The latter works on the command line. Run the report on your site to see where you stand. It is recommended that you run this check on a lower environment than production if possible.
 

Check Drupal Core and Your Environment

Running Upgrade Status should give you a report that looks like this:

Drupal 9 migration planning

We’ve created an example version of the Drupal 9 Upgrade Planning spreadsheet and added it to our plan:

Drupal 9 Upgrade Planner spreadsheet

 

Upgrading to Drupal 8.9

If you have upgraded your site to the latest version of Drupal 8, you will already have the latest Drupal 9 features. 


New features have been added incrementally to Drupal 8. A key step in upgrading to Drupal 9 is the removal of deprecated functions.

Drupal 9 deprecated code list
 

Check Your Custom Projects

Your custom modules, themes and libraries are the domain that is most under your control. Running the Upgrade Status module will give you a report that looks something like this:
 

Drupal 9 Upgrade Planner spreadsheet

In our example the “My Site Custom” module has 1 warning and 1 error

When we take a look we see that we need to change the name of a function.

Drupal 9 Migration planning

We’ve added this to our Drupal 9 Upgrade Planner spreadsheet.

Drupal 9 migration spreadsheet

Check Your Contributed Projects

Your “Contributed Projects” are modules, themes, and libraries that are created and maintained by the community.

For upgrading to Drupal 9, this is where things get more difficult. Not every Drupal 8 contributed project will be ready for Drupal 9 on day one. Your course of action will depend on your constraints. 

In our example, we get the following report for “Contributed Projects:”
 

Drupal 8 Migration planning

The report reveals that we have 9 projects that contain errors and 23 that have warnings. I’ve added these to Drupal 9 Upgrade Planner sheet.

Drupal 9 migration spreadsheet
 

Address Compatibility Issues of Contributed Modules

To get a better understanding of where contributed modules that produce errors or warnings are in terms of their Drupal 9 compatibility, you can check the module page. If there is not a notice about Drupal 9, there should be an issue in the issue queue. For example, this test project is using “Environment Indicator” version 3.7. A search of the Issue Queue () reveals an issue: “Drupal 9 Deprecated Code Report“ that has a patch that is “Reviewed and Tested by the Community.”

The amount of work to put toward a contributed project (“Low Estimate” and “High Estimate”) and when you would hope to have it upgraded (“Delivery Date”) are up to you.

For Environment Indicator, the Drupal 9 code has been reviewed and needs to be accepted or rejected by the maintenance team.

The actions to take are:

  • Add an additional review of the patch to help get it accepted
  • Apply the current patch to the current codebase
  • Wait for the next stable release

For this example we’ve estimated a couple of hours to update the project during the next stable release.

In Conclusion

Upgrading from Drupal 8 to Drupal 9 will be a lot easier than any previous upgrade. For our example project we have the following estimates:

Drupal 9 migration spreadsheet
 

We can reduce that estimated delivery date by contributing to the upgrade of some of the contributed modules we are using. Promet Source has contributed to a number of “Drupal 9 Upgrade” issues and encourage others to do the same.


We’re Here to Help

At Promet Source, we are passionate about helping clients to optimize their Drupal environments, whether that means the relatively simple shift from D8 to D9, or a migration from an earlier version. While there are still 18 months before the decommissioning of Drupal 7 and 8, keep in mind that waiting until the last minute to do so might be akin to reaching out to an accountant on April 14 concerning the previous year’s tax filing. Take steps now to ensure that thorough focus and attention can be devoted to the migration of your site.

Our team of Drupal 9 migration experts leverages best practices and proven processes for efficiently migrating websites, applications, and content to Drupal 9 -- whether from a previous version of Drupal, another CMS, or a home-grown system. Contact us today to schedule your FREE Drupal 9 migration consultation.  

 

Still on Drupal 7?

You are in good company. We will be addressing that migration process in a blog post later this month.

Feel free to contact us in the meantime for a FREE migration consultation
 

May 27 2020
May 27

Is a design revolution on the way? History says yes.

A new decade tends to usher in new design trends, but 2020 is turning out to be much more than just a new decade. As we look forward to finally breathing a sigh of relief, once Covid-19 heads for the history books, now is the time to prepare for what’s next. 
 
Seismic shifts and societal aftershocks stemming from the global pandemic stand to reframe how we view and interact with the world, and that includes websites. Design is inextricably linked to world events and there is no doubt that the economic, emotional, and political impact of Covid-19 has rocked “business-as-usual” to the very core.
 
During stay-at-home lockdowns, websites were catapulted into the primary means of connection. Chances are, the strengthened online attachments made over the past few months aren’t going away. Moving forward, “normal” will look a lot different than how we remember it. 
 
What does this mean for your website? How can you ensure that your site aligns with emerging expectations, current concerns, and new preferences for staying connected and conducting business?

Looking Back to Look Forward

For perspective on the design approach that will resonate with your audience, let’s take a quick look back to the design revolutions that followed major global upheavals from past decades -- starting with the last time that world was gripped by a pandemic that rivaled Covid-19. Of course, web experiences were not a factor for much of the previous century, but many of the same principles apply. Whether we are talking about color choice, fonts, building facades, or refrigerators, design has a powerful impact, even when -- often especially when -- it registers on a subtle or unconscious level. 

From Pandemic to Prosperity

Immediately following the devastation of World War I, which killed 40 million people worldwide and more than 5 million Americans, one-third of the world’s population became infected with the Spanish Flu. More than 20 million people died as a result, including 675,000 Americans. 


It’s hard to imagine a series of events that sparked a more desperate need for optimism and a determination to reshape a vision for the future that was driven by positive energy. 
 
Enter the Roaring Twenties: Modernist designs, marked by innovation and experimentation vs. realism and the rules of the past were the primary influences during this era. It was a time of fun, flashy and opulent design with gold as a dominant color and art deco as the signature style. 

an representative Roaring 20s illustration of a woman1920s design depicted opulence, sophistication, art deco designs and women stepping out of traditional roles.

 

Then: The Crash

The Great Depression of the 1930s marked a sudden and sweeping turn in economic realities. It sparked another design revolution that reflected efforts to lift up a population who was dealing with tremendous loss and uncertainty. Bright colors and positive messaging were intended to spark optimism and hope.
 
Streamline moderne emerged as a new architectural style that emphasized industrial materials such as concrete and glass, along with smooth curves. A lack of ornamentation and sharp angles aligned with the economic austerity of the times, while unexpected colors injected bright spots into the dreary realities of the day. 

The Blytheville Ark Bus station built in 1937The former Blytheville, Ark., Greyhound Station. Built in 1937 and listed in t he National Register of Historic Places. Public domain Photo by Nyttead, Wikimedia Commons.

A signature Depression-era design achievement was the Sears, Roebuck & Company’s decision to hire industrial designer Raymond Loewy to redesign its Coldspot refrigerator in 1934, in an effort to create excitement about the appliance and encourage consumers to shop. Touted as a “single, smooth, gleaming unit of functional simplicity,” the redesigned Coldspot sparked a fivefold increase in sales for Sears between 1934 and 1936, due to both the redesigned appliance and the effective advertising campaign.


Impact on a far greater scale accompanied the graphic design campaigns created to spark excitement about the National Recovery Administration (NRA). Posters with the Blue Eagle were splashed in major cities all over the United States, and Blue Eagle became a widely recognized symbol of the government’s commitment to helping with jobs that would offer much needed food, shelter, and economic security.

NRA Blue Eagle PosterDepression-era poster widely displayed by retailers to show support for the National Recovery Act.

Onward and Upward

During World War II, iconic propaganda posters fueled the war effort with messages that urged specific actions, while conveying unity, strength and the ultimate triumph of good over evil. 
 
As the war ended, the United States was quickly catapulted into the “atomic age,” which encompassed the years of 1945 through 1963. Atomic Age design trends reflected a determination to redirect the world away from one of history’s darkest chapters, while harnessing the war’s massive destructive capabilities for scientific achievements that would have a positive impact on humanity. Abstract designs, bright colors (turquoise was huge) and graphic elements inspired by science and space emerged as dominant design devices that represented a bright future of boundless possibilities.
 
The “boomerang” emerged as a signature motif of the 1950s, as well as designs that suggested galaxies, planets, stars and space travel. 

1950s boomerang pattern1950s "Atomic Age" designs references galaxies, space and the iconic boomerang motif.


 

Radical and Rebellious

Post-war optimism took a nosedive in the late 1960s and 1970s, as the Civil Rights movement, along with opposition to the draft and the war in Vietnam, fueled widespread unrest and antagonism toward authority. 

Psychedelic designs that featured bright and unexpected colors, kaleidoscopic patterns, and groovy typography reflected an emerging youth culture noted for rebellion and a determination to be seen and heard. 

A 1960s era graphic design"Psychedelic Dingbats," by Hendrike. Wikipedia Commons.

 

The Next Big Downturn

Throughout the 20th century, graphic design served as an essential tool for shifting societal gears following crises and setbacks. As we entered the age of digital communications, rapid change and heightened competition called for far more rapid response to evolving user needs and expectations. 
 
Let’s fast forward to 2008 and the Great Recession that followed the sub-prime mortgage crisis and the near collapse of global financial markets. At this point, the web had long since entered into the mainstream as a critical component of consumers’ connection to the world. The rise of “Web 2.0” was allowing for widespread sharing, interaction, and connection via social media and commenting capabilities.
 
As the Great Recession sparked distrust in mega-corporations and complicated, behind-the-scenes financial dealings, it fueled the rise of simple, web capabilities that offered transparency, no-nonsense, and value. Digital natives for whom online interactions were second nature, drove the growth of direct-to-consumer brands such as Warby Parker. Casper®, and Blue Apron. 

Successful web designs trended toward unintimidating colors, most notably “millennial pink,” along with minimalism and simple, clean graphics. The elegant simplicity of Apple’s design sensibility is emblematic of this era. 
 

What Now? Post Covid-19 Design

At Promet Source, we are in no way suggesting that Covid-19 is behind us, but as we proceed with hope and caution toward that point, we are devoting a depth and breath of empathy and insight into the types of redesigned web experiences that will effectively resonate with audiences. 
 
While the pandemic had and is having a distinctly different impact on every household and every individual, it’s fair to assume that varying degrees of post-traumatic stress will accompany adjustment to the new normal.  
 
It seems no surprise that the Pantone 2020 color of the year appears closely aligned with the reassurance that post-pandemic audiences will be seeking. Classic blue is described on the Pantone website as, “a reassuring presence, instilling calm, confidence, and connection. This enduring blue hue highlights our desire for a dependable and stable foundation on which to build as we cross the threshold into a new era.”

Pantone Color of the year 2020. Classic blueClassic Blue: Pantone 2020 Color of the Year

Calm and confidence is certainly not limited to a single color, but the concept is essential. Successful web experiences will not be looking to further rock anyone’s world. 
 
Confined to their homes, audiences have spent more time on the web than ever before. Chances are, they’ve experienced sites that offered excellent, streamlined navigation, sites that were frustrating to find what they needed, and everything in between. Moving forward, the bar is high, and like never before, audiences will appreciate impeccably designed web experiences. 

As people are confined to their homes and finding online experiences to be their primary connection to the outside world, websites are being called upon to do more heavy lifting than ever before.

Historically, economic downturns, and large-scale disasters of every kind have presented an opportunity for renewal and reinvention. This renewal is reflected in the design of the world around us, from fashion to websites. Our expectation for the post-pandemic era is design trends that evolve towards brighter colors, whimsical styles, and simplicity. For your website, this might mean a fresh, new color palette, bolder fonts with smoother edges, brighter images, and a renewed organization of previously complex menus and data.

At Promet Source, we’re committed and uniquely qualified to work closely with clients to ensure that their websites exceed the expectations of their audiences. Looking to start a conversation on aligning your site with new and emerging realities? Contact us today.
 
 

 

 

May 21 2020
May 21

"Never doubt that a small group of thoughtful, committed citizens can change the world; indeed, it's the only thing that ever has.”
        - Margaret Mead

 

Global Accessibility Awareness Day was inspired by a blog post written in November 2011 by Joe Devon, a Los Angeles based web developer who was frustrated about an overall lack of awareness about accessibility. He posted a blog calling for a day devoted to building a more inclusive digital world. Shortly afterwards, Jennison Asuncion, an accessibility professional from Toronto discovered Joe's blog post, via a Tweet. Together, Joe and Jennison cofounded Global Accessibility Awareness Day and six months later, on May 9, 2012, the first Global Accessibility Awareness Day occurred with about a dozen virtual and in-person events. 

Today,  there are, hundreds of GAAD 2020 events scheduled in every corner of the world, and never before has the imperative of an accessible web been more profoundly apparent. Covid-19 related lockdowns and stay-at-home orders led to an environment in which online resources were the primary connection to the the outside world. Moving forward, it’s anticipated that all users will demand web experiences that align with their varying expectations and abilities.
 

Enlightened Access

It’s wonderful that digital accessibility is inching it’s way into mainstream thinking, but too often, the time and resources associated with making sites and apps accessible is viewed as a burden -- a legal requirement that would gladly be avoided, if possible. The fact is, expanding digital accessibility represents a profound opportunity to take a more expansive, empathetic, and inclusive view of our world and that always leads to good.

We are living in a digital world that shuts out or limits the ability to engage for an estimated 15 percent of the population -- customers, constituents, audiences. 

This translate into business. Worldwide, the disabled represent $490 billion in buying power. And millennials, who value inclusivity and social responsibility more than any generation that preceded them represent $3.28 trillion in buying power. 

Once we get it, that ensuring digital accessibility is not only a legal requirement, it’s the smart thing to do and the right thing to do, our passion for accessibility moves up several notches. And just as accessible ramps at entrances to public buildings serve far more than the wheelchair bound, it’s helpful to understand that accessibility is not just for the “disabled.” 

At Promet Source, we are passionate about web accessibility as an opportunity -- not a “have to.” 

Big-Picture Benefits

Let’s consider some ways that accessibility modifications make digital experiences more engaging and flexible for people of all abilities.

  • Logical layouts and engaging designs are not just pleasant to look at. Any user can get annoyed when needed information is difficult to find and interactions are complicated, but users who have cognitive difficulties or limited computer skills can be frustrated beyond all measure. Be sure to evaluate the user experience from multiple perspectives and angles. 
  • Adequate color contrast is essential for enabling users with a wide range of visual impairments, such as color blindness, to read, navigate, or interact with a site. Low-contrast sensitivity becomes more common with age, but good contrast also ensures accessibility in low-lighting conditions and for users who could be experiencing any number of temporary visual challenges. 
  • Video captions are, of course, essential to enable the hearing impaired to understand the meaning of a video. They also enable videos to be accessible to viewers who are in particularly loud environments, or in settings where silence is required. 
  • Alternate text for images makes a site more accessible for the visually impaired. It can also bring additional context and clarity to digital experiences, while boosting search engine optimization.
  • Technology that converts text to speech is viewed as a requirement for the visually impaired. It’s also helpful for dyslexic users, people who prefer not to read, as well as people who want to multi-task. Coding websites and apps to convert text to speech has the added benefit of helping search engines to detect content.
  • Customizable text capabilities enable users to adjust the size spacing and color or text without loss of function or clarity. There are a wide range of visual impairments that make small text unreadable, and difficulties in reading small type inevitable accompany the aging process for everyone. 
  • Clear language is key to accessibility. Industry jargon and acronyms always need to be explained. Run-on sentences and paragraphs can frustrate users of all abilities and in particular those who have cognitive impairments or learning disabilities. In the current environment, there is no patience or inclination for unraveling complicated text. 

At Promet Source, we believe that the internet is for everyone, and we are thrilled for the opportunity to acknowledge and participate in Global Accessibility Awareness Day 2020. We're passionate about helping organizations to understanding what web accessibility is all about and to bring their websites into accessibility compliance.

Here's one of the ways that we are recommending GAAD be acknowledged: Select one page of your website and test it for accessibility using an accessibility testing tool. And urge others to do the same! Need help finding the right tools or fixing accessibility issues. Contact us today!
 
 

May 04 2020
May 04

Even among teams who are accustomed to working remotely, staying positive and connected can be a challenge when statewide stay-at-home mandates turn lives upside down in a myriad of different ways.

At Promet Source, we took it up a notch this spring, with some new ways to enliven meetings and support each other. The following five initiatives helped us to:

  • Get a glimpse into each others’ lives beyond faces on a Zoom call, 
  • Encourage accountability beyond immediate tasks at hand, and
  • Just make regularly scheduled meetings more fun. 

1. Guess the Workspace

Prior to last month’s all-company meeting, I requested photos of six individual’s workspaces. Near the end of the call, I showed the photos of the workspaces and asked everyone on the call to match the six selected employees to their workspace and submit their votes via the Zoom chat. It was fun to speculate the owner, and in the end we all learned that we know each other better than we thought, because we mostly guessed them right!

Screenshot of employees and their workspaces

2. Meet the Family (Dogs and Children)

We played the above game with pets as well. Better than a picture is seeing them real-time on camera. Recently, I was in a meeting where someone’s baby was connecting with a team member’s dog through the camera. Working around children and dogs is part of this new normal for many of us, and instead of stressing about trying to keep other members of the family quiet and out of the way, we encourage team members to introduce us to current members of their household. Dogs and children bring joy to any meeting. Even if they’re only on camera for a few moments, it brightens everyone’s day!

Screenshot images of four dogs of Promet Source team members

3. Virtual Watercooler Questions

Since we can’t chat by the coffee machine or while sipping a LaCroix, I like to post fun random questions in our Slack Channel. Building rapport through light conversation is a great way to help connect the team with fun facts or experiences that we might have in common. After all, how else are you going to find out that someone else’s first concert was also Cool Kids On The Block?

screen shot from a Slack exchange concerning first album purchases

4. Get Fit Challenge

One of our team members reached out to the group wanting more accountability for his workouts. The cure? He started a “Promet Quarantine Fitness Accountability Challenge.” Participants share their goals and report in every week whether they are meeting them. 

5. Hat-Mandatory Meetings 

Most of us know about being able to change the Zoom background on a call (when settings allow for it), and that can spark some fun conversation. But matching a hat to the background, or simply requiring a hat, can be a fun way to kick off a meeting, and keep us from taking ourselves too seriously.

screenshot of a promet zoom meeting

This is just a glimpse into the many ways that Covid-19 quarantines have have sharpened our commitment at Promet Source to connection and creativity. 

In the meantime, we’re continuing to collaborate with our public sector, higher education, and enterprise clients on the development of amazing websites that redefine possibilities. Interested in what we can do you you? Contact us today.  

Apr 29 2020
Apr 29

Seemingly overnight, much of the professional workforce was catapulted into remote work arrangements. 

For many, this has led to an adjustment curve. At Promet Source, collaborating with co-workers from all over the world is built in to our culture, and over the past several weeks, we’ve taken this opportunity to share insights and ideas for optimizing productivity and connectedness among virtual teams

Free Webinar! Winning at Remote Project Management with Jira and Confluence

Remote work success is largely contingent upon superior project management tools that provide an easily accessible framework for collaboration and information sharing. Our clients count on us for adept management of large scale web design and development projects, and the top two project management tools that we recommend are Jira and Confluence.

Why Jira and Confluence

When effectively aligned and fully leveraged, Jira and Confluence can be relied upon for significant enhancements to efficiency and effectiveness -- providing stakeholders at every level with the ability to drill up or drill down on projects and receive reminders of upcoming deadlines, real-time status reports, productivity updates, and a lot more. 

With Jira and Confluence at the foundation of a project, remote teams are able to move forward with their various sprints as seamlessly as if the entire team was working under the same roof -- often with even greater efficiency. 

Remote work arrangements tend to drive a level of discipline that can fall by the wayside when there is the option of interrupting a co-worker at a nearby workspace to check on the status of a project. With Jira and Confluence, status updates and shared documents are easy to access. There is far less of a chance for work to stop due to an interruption from a team member who wants help accessing information or who stops by with a random inquiry. 

Jira at Work

Big project plans are laid out as a series of sprints, with tasks and individual accountabilities spelled out within each sprint. Generally speaking those sprints represent dependencies -- one needs to be completed for the next one to begin. 

When using Jira, team members are reminded throughout the process of upcoming deadlines. A comprehensive, realtime report is available for checking on the status of any part of the project, and revised as needed.

Within Jira, project managers are able to monitor progress, assign new tasks, and calculate completion dates. 
.
Another essential Jira benefit: transparency. The ability to closely and objectively monitor the progress and contributions of all individuals on a major project can potentially get muddied when multiple expectations and accountabilities are involved. Jira provides a tool for closely tracking individual progress, eliminating the possibility of any team member flying under the radar or becoming overwhelmed with an undue number of tasks.

Aligned with Confluence

While Jira allows for drilling down on the details of a project, Confluence provides perspective on the big picture.

Confluence has been described as a corporate Wikipedia, housing the project’s knowledge base and serving as an easily accessible repository for sharing large files among both team members and clients. 

Confluence serves as a single, cohesive vehicle for communicating with clients. It allows for the creation and sharing within specific project areas, while keeping track of feedback, client deliverables, and the exchange of all assets that support the completion of the project. Images or files that would be too large to send via email can easily be dragged and dropped into Confluence.

Top Tips

  • Document everything. All meeting notes should be uploaded to Confluence, and the notes will automatically be emailed to all clients or team members who are referenced in the notes or listed as attendees. This is an essential step in helping all stakeholders remember what was agreed to and why. 
  • Utilize the search feature in Confluence when necessary, to locate notes from a particular meeting or conversation. Over the course of a project, a vast collection of notes will be created.
  • Leverage the permissions feature and determine which documents will be accessible to which clients and team members.
  • At the start of an engagement, offer clients a tutorial on Jira and Confluence, emphasizing the depth and breadth of efficiency enhancements. Drill down on features such as the calendar in Jira, which specifies not just delivery dates and key meetings, but also indicates travel and vacation schedules for all stakeholders and team members.
  • Understand that while the majority of clients have not yet used Jira and Confluence for project management, the learning curve is short. In the event that there is any pushback from clients at the beginning of a project, that is quickly overcome as the ease and efficiency of the tools are realized.  

More so than ever before, the tools are available that allow for the adept management of major projects from multiple locations. Jira and Confluence provide the foundation for assembling project teams that are based on talent, expertise, and commitment to successful outcomes for the client -- location no longer needs to stand as a limiting factor.

There’s more to learn!

Register Now for a Free Webinar: Winning at Project Management with Jira and Confluence

When:
Thursday, May 28, 2020    12 p.m. CST

Or looking to start a conversation now concerning what’s possible when talented designers and developers leverage the full capabilities of Jira and Confluence? Contact us today. 

Apr 21 2020
Apr 21

Covid-19 has upended daily life, and in many cases, revealed trends that were a long time in the making. 
 
Work-at-home requirements brought the essential need for online connections and services to the forefront. 
 
More so than ever before, county and municipal government websites serve as a virtual town square and the place for: 

  • Keeping informed about events and public health alerts,
  • Taking care of official business,
  • Showcasing major attractions,
  • Attracting future tourism,
  • Supporting local businesses, 
  • Staying connected to the community, and 
  • Drawing attention to praiseworthy people and points of pride. 

Multi-faceted Functions

Back in the day, city halls and county courthouses were architectural masterpieces, situated in the center of town with well-tended gardens, and surrounded by the businesses that fueled the town’s economic engine. 

The Wharton TX county courthouseThe Wharton, Texas County Courthouse. Completed in 1889.

Much of what had been accomplished in and around the limestone and granite structures that were built in the 19th and 20th Century is now taking place online.

As such, officials in places such as Martin County Florida are pouring a high level of focus and commitment into their citizens' experience of their websites -- just as their counterparts from previous eras understood the profound importance of creating a welcoming experience that was efficient to navigate and supported civic pride. 

home page of the Martin County Florida websiteHome page of the Martin County, Florida website

 

New World, Same Needs

Venues have evolved, but many essential needs and expectations of last century’s physical town squares have much in common with today’s virtual ones.

Here are the objectives that are driving excellence among public sector websites in the current era:

  • Support citizens’ pride of place with an engaging, visually appealing experience
  • Serve as the go-to information resource in times of crises and uncertainty
  • Drive collaboration and connection among commerce and community groups
  • Streamline access to a vast range of services that previously needed to be accomplished in person
  • Accommodate the different ways that the full range persona groups who visit the site interact with technology
  • Meet and exceed ADA Section 508 compliance standards and the web content accessibility guidelines (WCAG) that ensure accessibility for people with disabilities
  • Leverage the latest technologies and expertise concerning optimal user experience, navigation, and site flow
  • Align navigation and information flow with user needs vs. the internal organizational structure
  • Bring essential stats and facts to life with illuminating data visualization strategies
  • Build in flexibility to ensure that site administrators can easily and efficiently make changes whenever necessary

This is the starting point. Every state, county, municipality, and public sector website has distinct opportunities to connect with constituents, drive efficiencies, and serve as a trusted information resource. 

Looking to explore new possibilities for your public sector website? Contact us today


 

Apr 13 2020
Apr 13

A crisis can put a website to the test, and never has this been more true than in the current COVID-19 outbreak. As social distancing and stay-at-home orders are fueling a heavier than usual reliance on online communications, people are looking to state and local websites for up-to-date and authoritative information that’s specific to their area.

Due to excellent planning, perspective, and great partnerships, the Martin County Florida website is serving as a trusted resource for residents on COVID-19 information. 

Solid Foundation for COVID-19 Response

When Martin County Florida partnered with Promet Source last year on the redesign of its website, the need for a flexible content management system (CMS) to communicate essential and up-to-the minute information about hurricanes and weather-related events was well understood. This is one reason why the team at Martin County chose Drupal for their web platform. 
 

The Martin County Florida website homepageMartin County Florida's Drupal website homepage

While the COVID-19 crisis was not anticipated, a high level of foresight and planning has served Martin County well. Since Martin County Florida is in a hurricane prone region, a communication strategy and website plan was already in place, along with yearly practice drills. Residents have relied heavily on the site in the past, and never more so than in the current environment.  

This emergency preparedness perspective has been a strong asset in developing a website that is providing residents with quick and comprehensive information on COVID-19. 

The recent outbreak of COVID-19 has driven a sharp increase in the number of visitors to the site. Between February 23rd and April 5th, 2020, the website had more than 375,000 sessions. A sharp increase than the previous month when COVID-19 was not yet considered by most people in the United States to be a significant threat, noted Jennifer Hagedorn, web content specialist. She added that the recent spike in web visits exceeds that of any other hurricane or crisis event by 44%. 

Surge in Mobile Usage

There has also been a shift in the number of visits to the site from a mobile device. Pre-pandemic, about 40% of visits were from a mobile device, that figure now stands at about 70%, and represents a 200% increase in mobile usage over the previous month. This recent surge in mobile usage has been factored into how information is being presented on the site. 

To facilitate the increased mobile usage, the website content editors at Martin County began to utilize shorter blocks of content and placing content within an accordion-style page layout for mobile users to scroll through multiple topics and quickly locate what they were looking for.
 

Accordion Design Interface for Mobile Friendly ContentAccordion style user interface design ideal for mobile users and to consolidate topics for easy browsing

While there are many metrics indicating that the website is proving itself to be successful in providing residents with the information that they need, Jennifer pointed out that there has been noteworthy feedback by residents who have reached out to express their appreciation for the quality of the content on the website and the frequency of the updates. 

Success Factors

Key among the factors that have driven the success of the Martin County Florida website:

  • The ability to build new pages as needed and create page alerts facilitated a high-functioning emergency response system. 
  • Martin County also set up a single, easy-to-navigate Coronavirus page for all updates and information, which kept track of only the most up-to-date information and deleted all out-dated information and announcements to prevent confusion from website visitors accessing outdated information and articles on their site.
  • The Drupal CMS and WYSIWYG editor provides for a high degree of flexibility, enabling non-technical members of the communications team to perform in-line editing, simply create new pages, add them to the menu, update alerts, and easily embed videos and insert images.
  • The communications team can easily collaborate and are given the appropriate level of permissions for their role so they can help edit content, and those with a higher level of permissions can publish approved content to the live site.
  • The Drupal site uses Paragraphs, a Drupal module, that allows regions of a page to be interchangeable by content editors and does not require complicated code by technical developers to quickly build in functionality and apply custom arrangements on site pages.
  • For purposes of ensuring messaging validity, all communications are consistently branded and include the Martin County seal both on the website and social media images.
  • Website messaging is closely aligned with shareable, social media graphics and posts that are shared to help reach more people with the critical messaging and updates.
  • Residents can sign up for regular text messaging, offered via a third-party provider. The county has branded this capability “Alert Martin,” and these mobile text messages provide critical updates with links back to the website for the full story. This functionality offers one explanation for the increased traffic from mobile devices.
  • The “ALERT” region on the home page provides emergency and informative alerts and is color coded by level of importance: blue for general information, yellow for health and safety updates, and red for critical issues and warnings that require immediate attention. 
Alert system for websiteMartin County’s color coded alert system notifying site users of crucial health, safety, and general county updates.

By including these features on their website, along with many more, their site has received positive feedback from local residents saying they were very happy with Martin County’s COVID-19 emergency response and found the site easy to use and access the information they were looking for. The site was also recognized with industry awards for visual aesthetic and superior digital experience, proving to be not only nice to look at, but also usable and useful in a time of need.

COVID-19 is a moving target that is being attacked on many fronts. Never before have local governments had a greater opportunity and responsibility to ensure that their websites provide a trusted and single source of truth while providing a flexible content management experience for the site’s managers.

Looking to ensure your website is ready to communicate in a crisis? Contact us today.

Apr 08 2020
Apr 08

COVID-19 has fueled, among many things, a hefty appetite for data and analytics.

Having witnessed a rapid-fire evolution from a few, isolated cases in another corner of the world, to a pandemic that has the globe in its grips, data visualizations are now helping to tell the story and reveal the kinds of big data insights that are now possible. 

Near the top of the list of data visualizations that are providing an updated perspective on the Coronavirus is the Johns Hopkins University interactive global map, which offers a global view of the pandemic, along with the ability to drill down for a closer look at the spread of the virus within specific countries and regions. 

Johns Hopkins University COVID-19 Map

A screen shot of the Johns Hopkins University Covid-19 MapThe above screen from the the Johns Hopkins University interactive COVID-19 map is from April 8, 2020, and is among the interactive graphics on the site that depicts the global spread of the pandemic.  

 

Tracking Movement Via Cell Phone Data 

An April 2, 2020 article in an online edition of the New York Times, offered another angle from which to view the response to the Coronavirus in the United States. Using mobile phone GPS data, a color-coded map of every county in the United States, depicted miles traveled for the week of March 23, as an indicator of the degree to which people were adhering to shelter-in-place recommendations or orders.
 

A screen shot from a New York Times online article of a county-by-county map of the U.S. and movement over a weekend based on cell phone data.GPS data provided insight on a county-by-county basis into the degree to which mobility and travel had been impacted by the recommendations to stay home. 

Modeling Steps to Curtail the Spread

This third example is from a March 14, 2020 article in an online edition of the Washington Post, designed to demonstrate the impact of various degrees of social distancing. The article entitled, “Why outbreaks like coronavirus spread exponentially, and how to ‘flatten the curve,’” included animations of dots that demonstrated the impact of various levels of human contact on the spread of a hypothetical virus.

Screen shot from a Washington Post article that shows 4 models of the spread of a disease resulting from varying levels of social distancing. The four interactive graphics above represent the outcome of the different degrees of response designed to mitigate against a rapid spike in the spread of the virus.

Untapped Potential

While big data is fueling insights, that would have been difficult to fathom as recently as a decade ago, a depth and breadth of analytics and actionable data are within closer reach than many realize.  

Potentially rich data sources that too often go underutilized include:

  • Google analytics,
  • A/B testing,
  • Sales tracking, 
  • Live chat,
  • Customer surveys,
  • Heat mapping of visitors’ website activity,  
  • Competitor assessments,
  • Usability testing, and
  • User interviews. 

At Promet Source, we are passionate about helping clients to uncover and unlock the full potential of their data and analytics. We are also experts at creative visualization strategies that help clients and constituents to clarify complexities and understand information from new angles. 

Interested in igniting new data- and analytics-driven possibilities? Contact us today.

Mar 31 2020
Mar 31

Recent challenges sparked by widespread work-at-home mandates are revealing an essential need to ensure productivity and engagement for remote meetings.

Many of us are familiar with the internet meme video, A Conference Call in Real Life.  It may resonate as all too real (but still very funny!). 

With the right approach, however, remote meetings can be productive, engaging, and spark creativity. 

                  Register for a Free Webinar: Design Thinking for Optimal Online Collaboration

Since distributed teams and remote work environments are how we’re already accustomed to working here at Promet Source, we’ve been able to adapt many onsite Design Thinking meeting techniques, using Human-Centered Design activities and adjust them to a virtual format. We often accommodate remote teams who have attendees in varying areas throughout the globe that find it impossible to all get together for an onsite meeting, but still need to put their heads together to define an organization’s priorities or innovate together toward common goals.

On many levels the uncertainty and upheaval of our recent change in workplace environments represents limitation, but one of the main principles of design thinking is that creativity thrives in an environment of time constraints and limitations, which provides the opportunity for innovation and creativity when a few key guidelines are followed. 

Planning and Facilitation

A productive meeting has an agenda. Create a written agenda and share it with participants prior to the remote meeting, as well as at the beginning of the meeting itself. Be sure to include time slots for each discussion item, even if it is only 10 minutes.

Follow the agenda items closely and assign someone the “time keeper” function to give a 2-5 minute warning before the planned agenda item is due to time out and stick to it! 
 

Use Interactive Tools for Alignment

Oftentimes, the loudest voices in the meeting or those of upper management are the only opinions that get heard. Utilize online tools to facilitate discussions and to ensure every voice and opinion can be shared, regardless of hierarchy and position.   

Interactive tools can also help document what is being discussed in real-time without “note taking” so attendees can see what is being discussed and agreed upon. 

Creating an interactive forum also allows open discussion, presentation of ideas, and collecting maximum input from participants. If the users can contribute anonymously to the meeting, it allows for critical evaluation of ideas as a neutral and anonymous format.

Interactive tools we like to use during online meetings include:

FunRetro

  • Originally a Sprint Retrospective board we have co-opted for interactive meetings.

Google Sheets & Docs

  • Allows multiple users in a document at the same time for meeting collaboration.

InVision

  • In addition to a good design and prototyping tool, InVision also has a great virtual whiteboard that allows multiple people to draw on the whiteboard at the same time.

Prioritize & Gain Consensus

Working with the group to prioritize items that come up during the discussion helps to gain group consensus. Act as a facilitator for the meeting, listen to what is being said, and put your opinion aside in order to encourage participation and optimize input. Create follow-up activities for what the group sees as most important and assign next steps assigned to team members. Let them come up with a solution and present it back to the group in this or a future meeting.

Remember, online meetings can be productive and innovative when we allow the space for people’s ideas to be heard and thrive. Leveraging the right tools along with an intentional focus on connection and engagement sets the stage for memorable meetings that get participants to perk up and be on their A Game.

Design Thinking offers a whole new perspective on running a meeting. Engagement and connection are a particular imperative in the current environment and never has there been a better time to put design thinking to work. 

               Register for a Free Webinar: Design Thinking for Optimal Online Collaboration

[embedded content]

Design Thinking for Optimal Online Collaboration

When:

Tuesday, April 14, 2020    12 p.m. CST

In this webinar you will learn to:

  • Leverage interactive, online tools for meeting facilitation
  • Adapt design thinking techniques for the virtual meeting environment
  • Facilitate team activities that enhance online engagement
  • Understand the core of design thinking to facilitate more successful ideas
  • Implement a meeting format that sparks creativity and accelerates the evolution of ideas from good to great
  • Develop a process for creating joint ownership of ideas
  • Apply key steps for ensuring follow up and accountability

Interested in starting the conversation now? Contact us today to learn more about how you and your team could benefit from a Human-Centered Design / Design Thinking Workshop facilitated by Promet.
 

Mar 24 2020
Mar 24

ADA web accessibility compliance ultimately requires that developers get into the weeds of the 78 guidelines that make up WCAG 2.1. Visual checks and quick scans provide a solid starting point, however, and serve as key indicators of underlying accessibility violations. 

Here’s an overview of the essential factors to consider with developing or auditing a website for accessibility.

  • Contrast
  • Non-text content
  • Link purpose
  • Labels and instructions
  • Information and relationships
  • Keyboard navigation

Contrast

Contrast ratio refers to the luminance of the foreground text against its background. This guideline states that text and images with text need to have to have a contrast ratio of 4.5:1 for small text (less than 18 points, if not bold, and less than 14 points, if bold), and 3:1 for large text. For the highest level of compliance (AAA), which is not required in most instances, the contrast ratio for small text needs to be 7:1.

Tools for checking color contrast ratios include contrast checker and WEBAIM’s Color checker.

Sample Contrast Checker Output

Sample output from a color contrast checker tool

Content that does not consist of a sequence of characters, such as images and form controls,  is covered by non-text content guidelines. Non-text content needs to have a text alternative that serves verbally describes the image, otherwise known as “alt-text.”  If the image is decorative or only used for visual formatting, then it can have a null alt (alt=””) or implemented in a way that it can be ignored by assistive technologies, such as a screen reader.

Sample code for the following image:

<img src=”location/of/image.jpg” alt="Illustration of man sitting in wheel chair and woman standing against background projecting a checklist diagram.">

Illustration of a man in a wheelchair and a woman reaching out with website wireframes in the background

Link Purpose

Screen readers users should be able to determine the purpose of a link based on the text alone.

For this reason, generic link text such as “read more,” “learn more,” or “click here” is not WCAG compliant. To avoid confusing those who use screen readers, content editors also need to keep in mind that if the same link text is used more than one time on a page, the destination for those links needs to be the same.
 

Labels and Instructions

Clear instructions and labels need to be in place for controls that require user input. Instructions also need to provide specific formats, that indicate exactly how information such as dates, phone numbers, and email addresses need to be entered. 

Important points to keep in mind:

  • Labels should be properly associated to their specific fields
  • Related form elements should be contained in a fieldset and should have labels properly associated with them.
  • When input fields are compulsory they should be coded properly as required. Error messages should also be clear to users and contain instructions and sample formats on how to fill in the field properly.

Information and Relationships

The focus here is the semantic structure of the page as it appears to users of assistive technologies. 

Headings

Screen reader users rely on headings to navigate and scan content to understand the flow of information on a page. As such, headings should be logically structured within the H1 to H6 HTML hierarchy. There should only be one H1 heading on a page, and there should not be any skipping of the descending order of headings within that hierarchy. An H1 followed by an H3 might confuse a screen reader user into thinking that they skipped an important part of the content.

Tables

When a page contains a table or multiple tables, it is important that these tables be identified based on the data they contain. Tables should have captions that serve as the general description. It is sometimes an option to use  <summary> to supplement table descriptions, but this option is not widely supported by assistive technologies.

Keep the following points in mind concerning tables on a webpage: 

  • Layout tables should be avoided. When tables are used to format content, they might cause some confusion to screen reader users. Instead of using tables to format your content, use CSS.
  • Designate row and column headers to data tables using the <th> element. 
  • Associate data cells with the headers using the <scope> attribute.
  • Avoid nested tables. The more complicated the table, the more inaccessible it becomes.

Semantic Markups

Formatting is important for the look and feel of the page but the underlying code should contain the same information as the visual presentation of content. Headings should have proper heading markups. Lists should be marked with <ul>, <ol>, or <dl>. For emphasized texts use <strong>, <em>, <blockquote>, <code>, etc.

Landmarks

Landmarks provide another way for screen reader users to navigate a page. It has previously been recommended to use HTML5 and WAI-ARIA landmark roles together (e.g. WAI-ARIA role="navigation" on HTML5 'nav' elements) but with the widespread adoption of HTML5 this is no longer needed. There should be only one main landmark on the page, and all page content should be included in landmarks. 

The focus here is the semantic structure of the page as it appears to users of assistive technologies. 

 

Keyboard Navigation

Landmarks provide another way for screen reader users to navigate a page. It has previously been recommended to use HTML5 and WAI-ARIA landmark roles together (e.g. WAI-ARIA role="navigation" on HTML5 'nav' elements) but with the widespread adoption of HTML5 this is no longer needed. There should be only one main landmark on the page, and all page content should be included in landmarks. 
 

There's Much More to Learn!

Promet Source is passionate about ensuring the accessibility of online experiences for people of all abilities, while helping clients to avoid ADA Accessibility legal action. We’re available to help in ways that include training, development, consultation, support, and workshops.  

Contact us today to let us know what we can do for you.

Mar 17 2020
Mar 17

Current realities are rapidly shifting for all of us. What to do now? What can we expect? 

During a time of crisis, the quality of communications can have a huge impact, and not just in the moment. The effects of what is said and what is not said will linger, and reveal much about the organization, its leadership, and individuals involved. 

A crisis and challenge on the magnitude of a global pandemic stands to bring out the best in us or the worst in us. There are the immediate concerns surrounding staying safe and helping to ensure the health and well-being of those around us. Then, of course, there are a myriad of business and financial concerns. Life goes on. Promises still need to be kept.

At Promet Source, we are committed to reaching out and being our best selves during this time. It’s a commitment that starts at the top with clear and honest communications.  

This commitment calls for a higher degree of empathy and outreach. What are people going through? What do they need to know? How can we help?

Empathy PLUS Honesty

During times of uncertainty, people look for answers and reassurance, and it’s tempting to want to provide that. Keep in mind that making promises and commitments that may not be kept is likely to be interpreted as dishonesty and deception, both of which are particularly difficult to forgive. Now is the time for integrity.

As businesses around the world scramble to meet obligations and keep teams productive and connected while working from remote locations, the right messaging matters more than ever before. 

Great communication also calls for a focus on connectedness: focusing on what it is that we have to offer and how that translates into our role as corporate citizens.

Resources and Expertise

At Promet Source, we’ve reached out to our sphere recently, pointing out that our team is distributed and that due to our well-established business processes for working remotely, we’re positioned to consult on the systems and technical tools that we’ve found to be the most effective for staying connected and optimizing productivity. 

Our communications team can also serve as a critical resource during this trying time, helping with strategic messaging and communications plans for optimizing culture and strengthening client relationships.

New Concerns, New Paradigms

It's important that we actively acknowledge that team members are facing new sets of challenges that extend beyond working at home. In many cases, school-aged children are at home. There are likely to be constant interruptions and new expectations for homeschooling. 

There are also big concerns about coronavirus symptoms and the impact of recent exposures. 

Even among those who remain healthy and symptom-free, let there be no doubt that this pandemic is having a major impact on everyone’s lives. Team members with high-stakes deliverables who are now facing a whole new set of realities need to know that they are not alone. 

These new realities call for new ways of connecting, being present, and adding value. It’s a challenge that few could have anticipated, but that many are working through and revealing considerable character in the process.

Did you know that Promet’s communication team can help with strategic communications support? Contact us today to schedule a workshop, or simply to start a conversation. 

Mar 11 2020
Mar 11

There’s nothing like the threat of a global pandemic to bring the topic of working remotely to the forefront. 

This week, in response to the rapid spread of the coronavirus disease (COVID-19), companies from all over the world are scrambling to get systems and policies in place to ensure that work can continue in the event that quarantines are imposed or decisions are made to exercise caution and curtail the threat of workplace transmission of the disease. 

Remote work options are inherent to the Promet Source culture. We’ve benefitted for years from a culturally diverse staff and the opportunity to source the best talent without bias to location. As other organizations are rapidly moving in this direction, here are five strategies that we've learned for optimizing the remote work opportunity.

1. Communicate Often and Communicate Well

Compensating for the fact that you are not engaging with co-workers in the hallways, over lunch, or during daily stand-ups requires excellent and intentional communication. In fact, don't hesitate to over communicate with both your team and your supervisor. Assume nothing. Set clear expectations. Stay in touch, and be sure not to overlook the importance of casual conversations and humor. A productive work environment is not all work no play and you should get to know your remote colleagues just the same as you would those who work in the office or workspace next to yours.

2. Maintain Face-to-Face Connections

Promet’s president, Andrew Kucharski is insistent on the use of Zoom video conferencing for all meetings -- even ad hoc check-ins. This serves multiple purposes. Of course, it keeps us on our A Game and mitigates against any work-at-home temptation to stay in PJs and slippers all day. More importantly, we are inherently more connected when we see each other’s faces and facial expressions. We’re also more prone to converse and know what’s going on in each other’s lives and to remain accountable to each other.

Promet Source PMO working remotely with her dog, Lumen, by her sideDemonstrating another big advantage of working remotely from home, Pamela Ross, Promet Source PMO Director, takes a break with her dog Lumen at her side.

3. Leverage Technology

This one is huge. The concept of telecommuting has been around for a decade or two, but more so than ever before, we have access to tools that make us wonder why we’d ever waste a potentially productive hour or so every day sitting in traffic or taking public transportation to an office. Teleconferencing, shared calendars, collaborative document authoring tools and Slack are among the multitude of tech resources that enable a global staff to thrive.

4. Acknowledge and Affirm

Remember that all of the same principles of leadership and human dynamics apply when working remotely. Who among us isn’t energized by public acknowledgement, appreciation, and various forms of affirmation? At Promet Source, we encourage shout outs on the companywide Slack channel and through software that is specifically designed to engage employees and emphasize the company culture. New team members are welcomed and introduced during a “two-truths-and-a-lie” activity during company wide video conference calls, and managers are coached to consistently acknowledge team members for their contributions.

5. Recognize Relevant Strengths

Working remotely is a privilege that requires maturity and an excellent work ethic. Not everyone fares well in an environment that lacks the structure of a traditional office. Leadership needs to hire accordingly and cultivate an environment in which the responsibilities and advantages of working remotely are emphasized and built into expectations for every role.

At Promet Source, we do a lot more than develop and design accessible websites that win awards. Our Human-Centered Design workshops help to define the dynamics and the direction for success in any organizational endeavor. Contact us today to learn more. 

Mar 04 2020
Mar 04

The process of auditing a website for ADA accessibility compliance, as described by the W3C(R) Website Accessibility Conformance Evaluation Methodology (WCAG-EM) 1.0  falls into two essential categories: automated and manual. The automated part of the process is relatively straightforward. It’s simply a matter of leveraging the right tools for diagnosing non compliance with WCAG 2.1. The next and indispensable step tends to be open-ended and undefined. 

The WCAG-EM is the definitive to the evaluation process.

[WCAG-EM documentation]... is intended for people who are experienced in evaluating accessibility using WCAG 2.0 and its supporting resources. It provides guidance on good practice in defining the evaluation scope, exploring the target website, selecting representative samples from websites where it is not feasible to evaluate all content, auditing the selected samples, and reporting the evaluation findings. It is primarily designed for evaluating existing websites, for example, to learn about them and to monitor their level of accessibility. It can also be useful during earlier design and development stages of websites. 

The process is very well defined and W3C(r) provides a sample reporting tool for audits. 
 
We, at Promet Source like to tinker and apply small changes, without deviating from the process to improve the report and make it easier to use and read. Our version of the Website Accessibility Evaluation Report Generator is Google Doc based, provides an executive summary, a simple dashboard of results and is FREE! This template from Promet reflects WCAG 2.1 guidelines, and designed  for use by accessibility analysts and developers to detect errors missed by automated testing.

As a part of our commitment to advancing inclusivity and web experiences that are accessible to a full range of differently abled web users, we are making this tool available to all.
 

Small preview of the tool

 

Why Manual Accessibility Testing Matters

Manual accessibility testing goes deeper and wider than automated scans. It includes:

  • Keyboard testing
  • Color contrast testing
  • Screen reader testing
  • Link testing
  • Tables and forms testing
  • Cognitive testing
  • Mobile testing

The types of non-compliance issues, which are detected by manual testing tend to have the greatest likelihood of exposing site owners to ADA accessibility lawsuits.
 
Keep in mind that diagnosing a website for accessibility and fixing any noncompliance issues that are uncovered is not a one-size-fits-all endeavor. 

Every site has a distinct set of strengths and challenges, and in the current environment, the stakes are high for getting it right. That’s why we at Promet Source believe that tapping the expertise of a Certified Professional in Accessibility Core Competencies (CPACC) is the most efficient and effective path for bringing a site into compliance. We follow a distinct WCAG 2.1 auditing and remediation process that consists of a series of value-added steps in a specific order.  

Circle process graphic depicting web accessibility testing

 

Value-Added Elements

There is a high degree of added value that occurs during and following an accessibility audit. The education, consultation, and opportunity to dig deep and deconstruct aspects of a site that no longer serve the organizational mission fuels a better and wiser team of developers and content editors. For a number of reasons, web accessibility also enhances SEO.
 
In the current climate, websites are highly dynamic and serve as the primary point of engagement for customers and constituents. Constantly evolving sites call for an ongoing focus on accessibility, and an acknowledgement that staff turnover can erode the education, expertise, and commitment to accessibility that is in place at the conclusion of an audit. 
 
For this reason, a bi-annual or annual audit is a highly recommended best practice. 

Interested in kicking off a conversation about auditing your site for accessibility? Contact us today.
 

Feb 14 2019
Feb 14

A commercial came on the radio recently advertising a software application that would, basically, revolutionize data management and enable employees to be more efficient. My first thought was, “How can they possibly promise that when they don’t know their customers’ data management processes?” Then, it became clear. The business processes would have to be changed in order to accommodate the software.

Is that appropriate? Is it right that an organization should be required to change the way it conducts business in order to implement a software application? 

Sometimes yes. Sometimes no. 

The following four factors can serve as an essential guide for evaluating the need for change and ensuring a successful transition to a new solution. 

  1. Process Analysis
  2. Process Improvement
  3. Process Support
  4. Change Management

1. Process Analysis

Before committing to the latest and greatest software that promises to revolutionize the way you do business, make sure you’ve already documented current processes and have a clear understanding of what’s working well and what can be improved. Over the last few decades, several methodologies have been created and used to analyze and improve processes. Key among them: Six Sigma, Lean Manufacturing, and Total Quality Management (TQM).

How to Streamline Process Analysis

In simple terms, document the way you create, edit, and manage your data. Task-by-task, step-by-step, what does your team do to get the job done? If you see a problem with a process, keep documenting. Improvements, changes, redesigns come in the next step.

Steps to Document Processes

At the core of all process documentation is the process flowchart: an illustration with various boxes and decision diamonds connected with arrows from one step to the next. Collect as much data and as many contingencies as possible to make this flowchart as meaningful and robust as possible.

Diving Deeper

Integrated Definition (IDEF) methods look at more than just the steps taken to complete a task within a process. IDEF takes the following into account:

  • Input - What is needed to complete the steps in the task? Understanding this information can highlight deficiencies and can highlight flaws in effective completion of a particular step. 
  • Output - What does the task produce? Is the outcome what it needs to be?
  • Mechanisms - What tools are needed to perform the steps in the task? Can new technology make a difference?
  • Controls - What ensures that the steps within the task are being performed correctly?

Swimlane or Functional Flowcharts

In addition to the four items from IDEF data, knowing who performs a task is also important. As you draw the boxes and connect them with arrows, place them in a lane that represents the “Who” of process. Knowing who does what can reveal possible over-tasking and/or bottleneck issues in production and efficiency.

Getting Started

Whiteboards and Post-it can be an easy place to start process documentation. With today’s high definition smartphone cameras, you can sketch flowcharts, take a picture, and then share with stakeholders for their review and input. Once you have collected all relevant information, tools such as Visio or Lucidchart can make complicated process flows easier to create and visualize. 

2. Process Improvement

When you know how your current processes are performed, you can start to make improvements--whether incremental or a complete redesign (A.K.A reengineering). 

Low-hanging Fruit

Some needed improvements will likely be obvious. For example, someone on the process team says, “I didn’t know that you were doing that? I do it, too.” Duplication of effort doesn’t require metrics to be collected to determine that steps can be taken to enhance efficiency.

However, most processes require some form of metric collection to determine where improvements can be made. Metrics can include research costs, development time frames, quality assurance oversights, or frequency of downtime.

Knowing What to Change

If the needed improvement isn’t obvious, metrics can help guide the decision-making process. For example, how much time does it take to complete a process today? Could that be improved? Brainstorm ideas on how to shorten the time. Test the change and remeasure. 

Too often, data is collected with the intent of measuring the success of the process, but the data being collected is does not reflect objectives. For example, if the goal of a website or a particular page is to teach, metrics concerning the number of page visits does not indicate the degree to which that goal is being achieved. A more telling metric would be the amount of time a visitor spends on the lesson pages. Even more revealing would be the number of quizzes passed after a visitor engaged with the lessons.  

Before choosing metrics to be collected, understand your goal, determine the level of improvement you want to see, then start measuring that which will actually inform your goal.

3. Process Support

Key to process improvement is an analysis of how technology is can enhance productivity and efficiencies. 

For example: “We can cut three days worth of effort for three employees if we integrate the XYZ software into our process.” This kind of statement sounds like a worthy goal, assuming the cost to transition doesn’t exceed the long-term savings it can help realize. 

Calculating the Cost of Change

Open source software applications start out with a great price tag: Free. However, unless you use the application as is, there is always a cost associated with turning it into what you need. There are many more factors to consider than the upfront cost of the software. 

Costs can include:

  • Training on new processes
  • Training on the new software application acquired to support the new process
  • A drop in productivity and efficiency until the new process/application is adopted and accepted by your staff
  • Technology needed to support the new application
  • Keep in mind: The list of ancillary costs that are involved in the transition are unlikely to appear at the top of the salesperson’s brochure.

Return on Investment

ROI assessments will vary. Two values are needed to make this computation: cost and benefits. 

Once you've computed the short-term and long-term costs, you need to determine the benefits you gain. In a situation where investment directly translates into profit, this calculation can be straightforward.

However, sometimes the benefits are cost savings: “We used to spend this. Now we spend that.” When this is the case, instead of a cost/benefit ratio, a breakdown calculation might be required to determine how long it will take to recoup costs. 

The most complicated analysis will result from benefits such as an increase in customer satisfaction in which the benefit does not have a direct monetary value.

4. Change Management

When a team cannot see the benefit or resists change, new initiatives face an uphill battle. That’s why circling back to the process analysis phase and ensuring the buy-in of those who are being counted on to use the new application is a critical success factor.

Keep in mind that employees may not have access to the big-picture business goals that management sees, but change has the greatest chance of being realized if those who will be required to support it are informed as to why it needs to happen and included, at some level, in the decision-making process. 

Indeed, change management doesn’t start when the new application is ready to be implemented. Change management starts when:

  • All the costs of change are considered;
  • The full scope of process changes are identified;
  • Training is planned and delivered; and 
  • The campaign for change acceptance is designed and initiated.

Conclusion

You might be the boss. You might believe that the software application just discovered is what  your company or your department needs. As much as that matters, you need buy in. You need the support of the people who make your business possible. You also need to engage in a disciplined analysis of the processes that will be impacted, along with anticipated improvements and the level of support that will be deployed.

From ensuring that clients’ entire online presence is compliant with ADA accessibility guidelines to web solutions that optimize impact in the ever-evolving digital environment, we at Promet Source serve as a powerful source of transformative digital possibilities. Contact us today to learn what we can do for you.

Jan 23 2019
Jan 23

Besides Title, the most common field label found on a content type form is Body. Of course, this is where you place the body of your content. It’s your blog post, your how-to instructions, or maybe an event description. You know exactly what needs to be provided in this field because you are the trained author. What happens when the scenario includes many authors with varied skills?

Without clearly visible instructions for the form and the form fields, content authors can make mistakes. There are four default features in Drupal 8 that provide instructions for content authors.

Help

Body field configuration interface

When configuring a field, all fields except Title, you can include help text. The help text appears under the field, just like you see here on the configuration form where the help text for the help text field says, “Instruction to present to the user below this field on the editing form.”

Pros

The label of a field might not communicate the full intent or purpose of the field, so adding instructions in the help field can go a long way to ensuring an author uses the field correctly. 

For example, the Tags field on the Article content type provides default help text: Enter a comma-separated list. For example: Amsterdam, Mexico City, "Cleveland, Ohio" This provides instructions for entering tags correctly. 

However, if you need to add additional instruction regarding the context of the tags, you can include a statement like, “Do not use terms already offered in the Topics field.” 

Cons

The common placement of instructions below a field isn’t always noticeable. For example, the screenshot below shows the body field with help text below. Is it eye catching? Obvious?

Body field on the Add node page.

The size of a field can make providing easy to see instructions a challenge. And, if you need to make an accessible content type, the help text feature needs a little work to make it WCAG compliant. 

Placeholder

Configuration options for Body field on the Manage form display

Using placeholder text inside the field is another option. Although this feature is not available for all field types, it does enable you to include 128 characters of instructions. Located on the Manage Form Display tab for the content type, it’s just one configuration option available.

Pros

As mentioned in the Help section above, the Title field doesn’t have a help text option. However, the placeholder feature is available to provide tips on title strategies. Or, if the instruction is short and simple, such as a date format of MM/DD/YYYY can help users quickly understand the sequence of the date parts.

Cons

It’s only 128 characters and if the field size is less that that, not all of the instructions will be visible. On the topic of visibility, the Placeholder feature is not read by a screen reader. And, unless you do some browser specific CSS overrides, the contrast of Placeholder text might not meet WCAG color contrast criterion.

Lastly, when a user clicks in the field to enter data, the placeholder text disappears.  

Default Values

Body field default content configuration interface

The default value feature for fields is a great way to speed up data entry when the same entry is expected frequently. However, it can also be used to communicate instructions to the content author. You can go as far as providing a content template where the appropriate formatting has already been applied. 

Pros

Uniformity. Clarity. An experienced author will have their own way of conveying their thoughts, but that way isn’t always what’s best for an organization. Or, a newbie writer might need a little help to get started.

Notice the instructions for the often forgotten Summary feature. If you require a summary, include instructions like those shown in the example above and the Summary field will be open and ready when the content author uses the content type.

Also, unlike the Placeholder option, clicking in the field does not make the instructions disappear. 

Cons

The content author needs to remember to delete the instruction text. A small price to pay.

Content Type Explanation/Guidelines

Submission field settings for the content type

According to the Form Instructions tutorial provided by W3C, “Where relevant, provide overall instructions that apply to the entire form.” Each content type has the option to include a form explanation or submission guideline, as the field label suggests. 

Pros

Content add form with submission guidelines sample text.

The form explanation appears just above the Title field and outside the <form> element, which is needed for accessibility. You can also include HTML elements to format your instructions. 

Cons

If you need to format your form instructions, you will need to enter your own HTML as there is no HTML editor bar.

Conclusion

Not all forms are self-explanatory. Not all field purposes can be easily deduced. Drupal provides several options for providing guidance to your content authors, each with their own pros and cons. 

As you plan the way your finished content will be presented to site visitors, remember to plan your content type forms. Just because a content author receives training when the site is delivered, that doesn’t mean they will remember everything they learned. Form instructions help.
 

Jan 17 2019
Jan 17

Promet and Drupal go way back. We were at some of the first DrupalCons. We were an Acquia partner back when nobody had heard of Acquia. Most of our work today is building large, complex Drupal sites. (We are branching out though. Feel free to talk to us about Wordpress or other web development needs!) We love Drupal, and we’ve used it to build everything from simple to very complex websites.

However, Drupal 8 has changed the Drupal ecosystem. Drupal 8 is designed for engaging digital experiences. What does that mean? Mostly it means complex or mission-critical web applications. You can be a 2-person company working out of a basement, but if your website is everything to the business, there may be a good argument to build that site on Drupal 8. 

Drupal 7 was a swiss army knife. You can effectively do anything from a small blog site to the largest most complex sites online with it. Drupal 8 is more like a finely sharpened carbon steel Chef’s knife. It still does a lot, but you really shouldn’t use it to peel an apple.

Was that analogy too tortured? Anyway, we are still a Drupal first agency. However, there are definitely use cases where Drupal 8 is not the answer. Compare your project to the examples below to get an idea if Drupal 8 may be the right CMS for your website.

A small 5-10 page “brochure” site that may be updated once a quarter, if that.

This should not be a Drupal 8 site. Wordpress is probably the most common recommendation in this situation, however, I would recommend a different route. If you truly won’t be doing more than the occasional quarterly update, I’d recommend a static site generator (SSG) such as Pelican or GatsbyJS. Wordpress still comes with the overhead of keeping a database-backed web application updated and secure. For a few pages updated a few times a year, I would generate that site with the SSG and push the resulting HTML pages to a web server. With just HTML exposed on the server, your only security concern is if somebody compromises your server account. There is no database or CMS to hack. Your hosting costs are minimized this way too.

A small 50-250 page website that is updated frequently.

On the small end of this spectrum, Wordpress is the most common recommendation. As you get to the 250-page end there starts to be an argument for Drupal 8, especially if you are dealing with some more complex content types. Be careful though. A cheaper Wordpress shop will buy a $30 theme and tweak it to fit your needs. This can work fine, as long as the theme they buy was well constructed based on Wordpress best practices. Often those purchased themes are kind of a mess at the code level. 

If the site is small with static content that is highly trafficked, you can do something really interesting by using the GatsyJS SSG as a front end to Drupal. You can manage the content via Drupal, but publish it as static HTML pages via Gatsby to minimize hosting overhead and improve performance.

A large site with hundreds or thousands of pages that are updated rarely.

Drupal 8 will be the normal recommendation here, and it’s a perfectly valid recommendation. Drupal will allow you to publish structured content across the entire site, plus use taxonomy to relate content. If you need to manage user permissions about who can do what with the content, Drupal 8 becomes a great answer.

But what if you are publishing documentation that will almost never change? Do you really need the overhead of an enterprise-grade CMS that will get used rarely once the site launches? I think the static site generators are a really interesting solution to this use case. Pelican, to reference the SSG I’m most familiar with, can implement tags to relate content, and can identify different authors if it is a multi-author scenario, It has no concept of user permissions though. I’m not aware of any major sites that have been done this way, but it seems like a very low overhead answer to the publish a lot of content once and then mostly forget about it scenario. If you have a project like this let’s talk!

You have a large complex site that has a variety of content types that integrate with 3rd party systems, and it’s crucial to your business that the site stays available and performant.

This is the Drupal 8 wheelhouse. This is what Drupal 8 does best. You can think of Drupal 8 as a box of standard Lego bricks. What you build with it is only limited by your imagination, time and resources. (How big is that box of Lego bricks?) A few of the scenarios that Drupal excels at include:

  • Multi-author websites where you need granular control of publishing and editing permissions by either individual users or groups. This extends to workflow issues where you need a publishing workflow for editorial oversight.
  • E-commerce applications where you are generating significant revenue from the website.
  • Integrated solutions where the website needs to share or sync data with other business systems such as a CRM or AMS.
  • Multi-site applications where you need to manage dozens to hundreds of websites that will all share common elements while allowing for localized control of specific content elements on specific websites.
  • Multi-output applications (decoupled Drupal!) where you need to deliver the same content to disparate devices such as web browsers, mobile apps, digital signage,  voice-activated devices such as an Amazon Echo or Google Home device; and future devices we might not have thought of yet. I can see us interacting with websites via voice activation in our cars in the not too distant future, if it's not already being done. 
  • Multi-lingual websites where you need to manage translated content.

Hey Chris, you didn’t mention SquareSpace, Wix and similar services for smaller sites.

That is correct, I didn’t. Promet is an open source consulting firm, and personally, I’m an open source advocate. I avoid proprietary solutions when an open source option exists. That said, if you need to publish a small static website and want to take the path of least resistance with SquareSpace or similar, I don’t think it’s a particularly bad idea.  If your content got locked up in one of those services the site is presumably small enough that starting over won’t be that painful. But I’m not going to recommend those services, at least not in writing ;)

If you have any questions about what to do with your website please get in touch.
 

Dec 19 2018
Dec 19

Imagine if you will, you have an Events link on your main menu. Someone clicks on it and the Events landing page is loaded in their browser. How was this page built? With Drupal, you have several options. 

If you are the kind of person who likes to have a say in the way things are done, be it from a previous bad experience or idle curiosity, the following will help you engage in the planning aspects of your Drupal site. So, let’s look at five recipes for building landing pages in Drupal.

  • Node page
  • Node Plus View Block
  • A View Page Plus a Block
  • Panel Page
  • Custom Theme Page

Node Page

Content pages in Drupal are called nodes. You fill out a form (e.g., a content type) online, save, and you have an article or event or some other kind of page. This page has a URL. That’s important to remember. Every page in a website has to have a URL. 

How

Using Drupal’s default Basic Page content type, you fill out the form. Give the page a title of About Us. Fill in the body field with information about you or your company. Add it to the main navigation menu with a check of a box. Lastly, you create an URL alias. Instead of the default format of /node/3, you want /about-us. Save and you see your new landing page.

Yes, it’s boring, but we’re just getting warmed up. 

Why

Simple page. Simple technique. Easy to create and edit. Easy to translate in a multilingual site. And let’s not forget the other cool things you can do with a node.

Node Plus a View

Building on the previous example, let’s build an Events landing page. Obviously, this kind of page is going to be a little more complicated. Here are the requirements: a title, some introductory text, and a list of Events that you created using an Events content type. You will have many events so using a manual approach to creating and updating a list of events is not a fun idea.

How

With this scenario, you use the Basic Page content type and create a node titled Events. Using the body field, you add some text that describes your events. Like before, check the box to add this node to the main navigation. Give your page the URL alias of /events. Save and the first part of the configuration is complete.

The next step in the configuration process is a little more complicated, but it’s the concepts you need, not the details at this time.

Drupal has a module called Views. It’s an incredible tool that lets you create an SQL query on the database and then create a display for the results of that query. For this landing page, you need events for the future, not the past, so you filter accordingly.

Given we already have a Drupal feature with its own URL (the event node), we don’t need another. That means you will create a block display for the SQL query results. Blocks can be small bits of information or larger, more complicated displays. They can even hold forms. What they don’t have is a URL. They only show up because a page is there to host them.

Without going into all the particulars, you will place the block so it appears under the body field. If you want to know more about how this done, please join us in a Drupal 8 Site Building Best Practice training class.

When you go to the yoursitename.com/events URL, you will see the Events node and the view block that lists the upcoming events. With some styling, you can make the two features (node and view) appear as one, seamless page.

Why

Some will argue that you could have made a View page versus using this two-step process. And, in the next example, you will. In this scenario, you looked ahead and saw that the introduction text would not be a fixed blurb. You will change it from one season to another and your staff will not have the skills to edit a View.

So, this scenario worked nicely for your business process and staff.

A View Page Plus a Block

Let’s change up the requirements as a means of introducing another build option. You need a list of events, but instead of some introduction text, you need an image banner. There are several ways to accommodate this new image requirement, including adding to the previous scenario. In this example, we will use a View page and a block.

How

Create an SQL query, grabbing all the events scheduled for the future. Instead of displaying the list of events in a block, you create a page with a URL of /events and place it on the main navigation menu.

Next, create the block that will display your image banner. Like with most requirements, Drupal provides several alternatives to meeting them. For this scenario, assuming you are using Drupal 8, create a new block type called Image Banner. Add an image field to the new block form and set the field display to show only the image.

Create a block, using your new block type. Upload the image you need for the Events landing page. This process is very similar to creating a node. The input form looks similar as well. 

Place the banner image block either above or below the page title block to match your design. This is a quick and easy way to insert an image above the title of the page if that is your choice. 

Why

A View page isn’t like a node. It doesn’t have fields. You can add a header and footer text, but it’s not the same as adding a field to a node. Bottom line, a View show the results of a query - typically that of nodes. So, if you need to display information other than the query results, you might need to use methods like described above, by adding blocks or combining a node with a view.

Another reason for mixing and matching features to create a landing page is display. By default, a Drupal page - node or view - is broken into two parts: Title block and Main Page Content block. If we had chosen to add an image to the available header text box in the view, the image would appear below the page title. Yes, you can do some template coding and rearrange things a bit, but why would you if you could simply place a block and accomplish the same goal.

The point of all this is, remember that content comes in parts in the Drupal world, and quite often, a simple mix and match strategy is all that needed.

Taxonomy View Page

A technique that can be overlooked is the use of the default taxonomy term page. A term is a word or phrase used to describe the content in the node. By default, a term page displays when someone clicks on a term link shown on a node. The page provides a list of nodes tagged with that term. 

Let’s see how this default feature might be used to create landing pages by changing our focus from Events to types of content.

How

Imagine that you have three types of content that will be placed in a body field: How-to Lessons, News, and Blogs. Instead of creating three separate content type forms, you add a field that assigns terms to the content, declaring it a How-to Lesson, for instance.

By default, the How-to Lesson term has its own landing page. In Drupal 8, the term page is a View page and can be modified to meet your display layout needs.

Let’s take this scenario one step further. It’s come to your attention that you need a banner image and introduction text to appear above the list of nodes tagged as How-to Lesson. In this scenario, you can add an image field to the term and use the description field for your introduction text.

The results are very similar to what we have created in the previous scenarios: a page title, and image, some text, and a list of nodes. Place the page URL on the main menu and you have a landing page. 

Hopefully, this demonstrates the need to think about your processes before choosing a configuration strategy. There are several steps involved but it’s actually quite easy to learn how to do in a Drupal training class.

Why

Websites can be complex and that might mean multiple content types. However, imagine that one of your staff is blogging the latest insight on gardening strategies and it morphs into a how-to lesson. If they created the blog post in the Blog content type, they would need to move that content to the How-to Lesson content type instead. 

If this is something that might happen, create one content type for narrative content and use terms to distinguish between them. If you do, you can then take advantage of the term’s default pages, as demonstrated in this example.

Panel Page

So far, our examples assumed simple displays. What if you want to create a landing page whose content is built solely from blocks. Basic text blocks. View blocks. Blocks from other modules. Again, there are several ways to make this happen, especially if your theme (that bundle of code that controls the look and layout of your site) has the appropriate regions to organize your blocks in the way you need.

For now, let’s assume you need something unique.

How

Panels is a module that you can add to Drupal. It provides a graphic user interface (GUI) and allows you to create a page with its own URL that can be assigned to the main menu. Remember, if you need a page in Drupal, it has to come from something that can have its own URL. You can also create a custom layout to display blocks.

The process to complete this task is too complicated to step through here, but it can be learned in a Drupal training class.

Why

Some will say that you should create the theme regions you need versus using Panels, and they would have a valid point. However, if by now you are intrigued with the build process and are wondering if you might be able to do it yourself, then a tool such as Panels doesn’t require you to know how to customize a theme. 

Of course, with training, a custom theme is something you can manage. In fact, let’s consider one way of using a custom theme to create a page on your site.

Custom Theme Page

Let’s take a moment to consider the Drupal theme. Without going into all the details of theme development, at a minimum, you need to know that the theme defines the regions (header, navigation, sidebars, content, footer, and more) used to organize and display blocks. It also manages the templates used to say what gets rendered in the region.

For example, there is a page template. This renders the region if there is a block assigned to show in said region. You can add as many regions you want in order to accommodate the various block layouts you need.

You can also create a template for a single page. Let’s consider this strategy for a moment. 

How

Assume that you created a node using the Basic Page content type and titled it Resources. In the theme, you create a template specific to this node. At this point, it’s all about hand coding. You create a template that renders all the blocks you have created to display on this page. Then, with some CSS, you style the blocks in a layout of your choosing.

With the Resources node assigned to the main navigation menu,  you have the page you need because its custom template is hard coded.

Why

To be honest, although this blogger has seen this approach used, it is not conducive to making quick changes to the page. Why is it listed as an option? Because, depending on who you hire to create your site, you might end up with a vendor that uses this technique. Be it on purpose to gain maintenance business from you or just from lack of Drupal building experience, you could end up with a site that does not take advantage of Drupal’s flexibility.

Make sure you are specific in your requirements regarding the use of custom code if this is a concern.

Planning and Promet

The five options conveyed here are not the only options you have available. Moving forward, consider taking an active role in the development strategies chosen to create your site to ensure you receive a solution you can manage. 

Remember to build in time in your schedule to have development strategies discussed before they are implemented. If your developer is reluctant to let you in on their plans for meeting your requirements, they might not be the vendor for you. 

If you still have questions, check out Drupal 8 Makes it Easier and The Path to Migration to learn more about your options and considerations for your project.

Promet offers a unique planning engagement that we call our Architecture Workshop. This workshop is a customized engagement that engages all of your stakeholders in the Discovery Process. We do a 3-5 days of intensive onsite exercises with stakeholders (for your busy C-level folks we customize the agenda to bring them in where they are needed during this onsite). Then the team goes away and produces a set of deliverables that includes a full-field level Architecture Blueprint of the website(s). Whether you choose to use a waterfall or agile development methodologies - you have everything you need to build the website everyone has agreed upon. 

Not building your site and stressed out about getting an accurate quote? Investing in this kind of Workshop will make sure that you get the right Partner, and the best price.

For more planning information email [email protected].

Dec 19 2018
Dec 19

Have you ever tried logging in or registering to a website and you were asked to identify some distorted numbers and letters and type it into the provided box? That is the CAPTCHA system.

The CAPTCHA helps to verify whether your site's visitor is an actual human being or a robot. Not a robot like you see in the Terminator movie but an automated software to generate undesired electronic messages (or content). In short, CAPTCHA protects you from SPAM.
 

Distorted texts and numbers, for example, could not be recognized by bots so by providing this we are sure that only a human can log in or register.


This works! But there are some downfalls to this. For one, it's not user-friendly to visitors who are visually impaired. Reading distorted numbers and letters can be annoying to regular users, how much more to a user with a visual disability. The last thing we want from our visitors' is form abandonment, that is, leaving without even the chance to enter.
 

The solution? reCAPTCHA!
 

Drupal's reCAPTCHA module uses the Google reCAPTCHA to improve the CAPTCHA system. The reCAPTCHA module is a very efficient addon to the original CAPTCHA module.

With reCAPTCHA, we have the choice to provide a simple checkbox that asks our users if they are a robot or not. this is so much easier than asking our users to read distorted characters. We can also provide several random images and ask our users to check a specific image. This kind of test could not be passed by a robot, but we humans can!

Why trouble with bots? You may ask. The CAPTCHA system provides security, including but not limited to:

                -  Preventing Comment Spam in Blogs.
                -  Protecting Website Registration.
                -  Protecting Email Addresses From Scrapers.
                -  Online Polls.
                -  Preventing Dictionary Attacks.
                -  Search Engine Bots
                -  Worms (malware computer program) and SPAMs (undesired messages/content).

So how do we set up reCAPTCHA for our forms? Read along for an easy and detailed guide in setting up reCAPTCHA for your forms. this tutorial provides screenshots of every of every step of the way.
 

Install
 

Download and install CAPTCHA and reCAPTCHA module.

Using your favorite installation mode the Drupal UI, copy/paste from drupal.org, Drush, or Composer. Just remember that to use reCAPTCHA, you need the CAPTCHA module.

If your site is set using the PHP dependency manager called composer (like we do at Promet Source), add reCAPTCHA and the CAPTCHA module will be added automatically as dependencies:

$ composer require drupal/recaptcha


 

Enable
 

With Drush, you can enable the reCAPTCHA module by running the command in your terminal.

$ drush en recaptcha

Drush is fantastic to interact with Drupal and work faster. Learn more: Drush Made Simple).

You can also enable the module in the UI at "/admin/modules".

Search for Recaptcha, Click the checkbox and click 'install'.
 

Enabled reCAPTCHA module


Configure
 

Go to "admin/config" and choose CAPTCHA module settings.
 

CAPTCHA module settings


In the form protection default challenge type drop-down, choose reCAPTCHA from module reCAPTCHA. Don't forget to click 'Save configuration'.
 

CAPTCHA settings


After saving, click the reCAPTCHA tab.
You will be asked for the 'Site key' and 'Secret key'.
Click on the link Register for the reCAPTCHA, you will then be automatically redirected to Google.

Register your website for reCAPTCHA

Write your domain name in 'domains'.
 

A screenshot of the form where the site has to be registered for reCAPTCHA


You will be provided with the site key and secret key. Go back to "admin/config/people/captcha/recaptcha" and fill up the "Site key" in the general settings.

Click save.
 

CAPTCHA keys

Then go to CAPTCHA Points.

Choose which form you would like to use your reCAPTCHA.

TEST!!

To test, simply open your website and try visiting the form where you enabled the reCAPTCHA.

In this tutorial, the form that I choose to use reCAPTCHA is the login form.

reCAPTCHA displayed in a login page

Additional step: For local testing ONLY

If you want to do the above steps in your local environment, you have to disable the domain name validation in your reCAPTCHA configuration in google.com

Click the Advance settings and disable the domain name validation.
 

CAPTCHA for local testing


Don't forget to test by accessing your form in an incognito browser.

And there you have it, reCAPTCHA configured! Your Drupal 8 project is now protected by Google's reCAPTCHA system.

Say no to bots, yes to human...

Questions?
Drop them in the comments section below this article :)

Special thanks to Luc Bezier for contributing to this post before publication.

 

Nov 15 2018
Nov 15

Did someone test your website for accessibility conformance without your knowledge and then inform you that your organization is prime for an accessibility lawsuit? Are they offering to help you fix the issues found on your website? 

That notification and offer might be valid, but it also might not be the entire picture. One free test grade might not reflect how your site is doing in all its accessibility subjects because automated testing tools can't find all the problems. We believe in assessing all topics of accessibility before recommending a sit down to discuss your options on how to proceed.

How do we do it? 

We don't rely on automated testing to reveal the true nature of a website's issues. We manually test it as well. We look at what makes your website unique and try to understand its mission before creating a scorecard you can use in your decision-making process.

This card reflects several perspectives including the issues anyone with an automated testing tool can see, including you. Many are free to use and quite robust in their feedback. Give one a try. For example, Code Sniffer.

But don't stop there. Our scorecard also reflects a sample of other accessibility issues not seen by the tool.

Last but not least, we look at how you are delivering your website. This part of the review is critical to understanding whether fixing or rebuilding the site is going to be your most cost-effective solution.

Website Grade

Just like the report card you got as a kid, we use grades to convey the accuracy and quality of your work, or in this case, your website. As you can see below, there are degrees of quality: A through D. No F, for failure. We assume no site is that bad.

A – Accessible & modern platform, main issues residing solely in the content
B – Accessible & modern platform, but issues with template items such as menus, sidebars, and in-line styling
C – Accessible & modern platform, but many features need to be replaced or reworked to achieve compliance
D – Antiquated platform, non-responsive, easier to rebuild vs. fix

The Scorecard is not intended to act as a thorough report or formal recommendation, simply a high-level overview. It's our tool to facilitate a conversation with you and help you choose the best path to remediation.

For example, we might find that you are using a content management system tuned to meet the accessibility criterion, but your content developers aren't using appropriate techniques when posting. Fixing existing content issues without “fixing” the reason the issues exist just means your site will continue to have problems.

Or, the example could be far worse. We hate to say it in this day of accessibility lawsuits, but there are still platforms out there that don't follow the rules. If your site was created using an antiquated approach, it might be more cost effective to rebuild rather than create workarounds in your current system.

Our Passion

Here at Promet Source, we are passionate about accessibility. We offer an array of services and remediation options that can be shaped to fit your needs. But, be warned, we are not a quick fix/band-aid company. We believe in enabling you to move forward knowing that you have a fully accessible site and the means to keep it accessible.
 
The decision process associated with such an undertaking can feel overwhelming. That's why we offer the scorecard as part of your remediation process. It's your tool to use in helping others in your organization to understand the level of effort you are facing by moving forward. 

We find that when all stakeholders have an understanding and are vested in doing the right thing, the future of a website is easier to envision. 

We look forward to talking to you about that phone call you got by surprise or that unsolicited email full of ill tidings. Don't worry, we can help you understand and make informed decisions.
 

Nov 15 2018
Nov 15

Did someone test your website for accessibility conformance without your knowledge and then inform you that your organization is prime for an accessibility lawsuit? Are they offering to help you fix the issues found on your website? 

That notification and offer might be valid, but it also might not be the entire picture. One free test grade might not reflect how your site is doing in all its accessibility subjects because automated testing tools can't find all the problems. We believe in assessing all topics of accessibility before recommending a sit down to discuss your options on how to proceed.

How do we do it? 

We don't rely on automated testing to reveal the true nature of a website's issues. We manually test it as well. We look at what makes your website unique and try to understand its mission before creating a scorecard you can use in your decision-making process.

This card reflects several perspectives including the issues anyone with an automated testing tool can see, including you. Many are free to use and quite robust in their feedback. Give one a try. For example, Code Sniffer.

But don't stop there. Our scorecard also reflects a sample of other accessibility issues not seen by the tool.

Last but not least, we look at how you are delivering your website. This part of the review is critical to understanding whether fixing or rebuilding the site is going to be your most cost-effective solution.

Website Grade

Just like the report card you got as a kid, we use grades to convey the accuracy and quality of your work, or in this case, your website. As you can see below, there are degrees of quality: A through D. No F, for failure. We assume no site is that bad.

A – Responsive & modern platform, main issues residing solely in the content
B – Responsive & modern platform, but issues with template items such as menus, sidebars, and in-line styling
C – Responsive & modern platform, but many features need to be replaced or reworked to achieve compliance
D – Antiquated platform, non-responsive, easier to rebuild vs. fix

The Scorecard is not intended to act as a thorough report or formal recommendation, simply a high-level overview. It's our tool to facilitate a conversation with you and help you choose the best path to remediation.

For example, we might find that you are using a content management system tuned to meet the accessibility criterion, but your content developers aren't using appropriate techniques when posting. Fixing existing content issues without “fixing” the reason the issues exist just means your site will continue to have problems.

Or, the example could be far worse. We hate to say it in this day of accessibility lawsuits, but there are still platforms out there that don't follow the rules. If your site was created using an antiquated approach, it might be more cost effective to rebuild rather than create workarounds in your current system.

Our Passion

Here at Promet Source, we are passionate about accessibility. We offer an array of services and remediation options that can be shaped to fit your needs. But, be warned, we are not a quick fix/band-aid company. We believe in enabling you to move forward knowing that you have a fully accessible site and the means to keep it accessible.
 
The decision process associated with such an undertaking can feel overwhelming. That's why we offer the scorecard as part of your remediation process. It's your tool to use in helping others in your organization to understand the level of effort you are facing by moving forward. 

We find that when all stakeholders have an understanding and are vested in doing the right thing, the future of a website is easier to envision. 

We look forward to talking to you about that phone call you got by surprise or that unsolicited email full of ill tidings. Don't worry, we can help you understand and make informed decisions.

Email us for help!
 

Nov 13 2018
Nov 13

Partnership combines comprehensive UI design, UX, and digital strategy, with web development proficiency, to produce a holistic experience for clients.

Chicago, Illinois — November 13, 2018 — In September 2018, Promet Source acquired DAHU Agency, a strategy-focused, user experience and design agency that enhances the services offered to its clients. By expanding their services in UX and UI, and bringing new offerings in-house for digital strategy, WordPress development, messaging, and branding –  Promet aims to better serve their clients evolving needs as marketing and web technologies continue to converge and the need to provide functional, dynamic websites increases.

 

In his vision for Promet to be a strong digital agency focused on creating great user experiences through meaningful web applications, Andy Kurcharski, President of Promet, seeks to accelerate growth and innovation by providing comprehensive digital services to his clients.  Andy has more than 20 years of technical leadership experience from startups to Fortune 50 firms with industry experience in banking, telecommunications, government, and association technology management. Andy’s e-commerce experience dates to 1998 with the implementation of highly scalable enterprise solutions.

 

“In today’s technology landscape, we are seeing that our clients and their customers expect more from their websites” Kurcharski expressed. “Our addition of a new team to our existing core of web developers will help us to proactively approach new websites with a holistic mindset combining our technology expertise with great design and function to ultimately increase client success online.”

 

DAHU Agency, based in Dallas, Texas, not only provides Promet with an office central to service their clients in the Southwest region but also brings expertise in design and digital strategy to help optimize user experience within an organization’s website.

 

Mindy League, CEO, and founder of DAHU Agency offers a highly thoughtful and adaptive approach to constantly evolving technologies and user behaviors. Her experience in building solutions for clients such as HP, Emerson, IBM, and Home Depot, contribute to a depth of perspective into the challenges and opportunities faced by top global brands. Mindy will join Promet as the Director of User Experience and Design.

 

DAHU’s distinct approach to engaging with clients has been described as “radical empathy” and it is this philosophy and mindset that complements Promet’s dedication to delivering groundbreaking results to their clients. Whether examining the impact of corporate strategies on customers and the broader enterprise or developing products, Promet aims to step into their clients’ businesses with a fervent dedication to excellent experiences and high-impact results.

 

Click here for full press release. 


 

Nov 01 2018
Nov 01

Your company brand encompasses the entire perception of your organization through the eyes of your customers, clients, and employees. Branding consists of more than just your logo and typeface selections; it is how the public (usually users and/or customers) experiences your business. How you position your brand can certainly define the customers’ experience of your organization. However, consider first planning great experiences for your users and customers in order to develop a more customer-centric brand identity. Changing to this strategy requires a solid understanding of your users and customers as well as a thoroughly considered mission statement prior to developing your brand.

UNDERSTAND YOUR USERS AND CUSTOMERS

Knowing who your business is intended to cater to will help you to plan all the touchpoints your customers and clients will have with you, from the in-person experience to the web and social media experience to even the look and feel of business cards you hand out. For example, if your target audience consists of Millennials, your language and messaging would be different than if it consisted of top-level executives and managers. User experience research techniques can be used to help define different customer/client personas. These personas can be used essentially as avatars for your customer base. As new services or features are developed, keep these personas in mind to ensure that these new offerings align with their needs and desires. At times, new personas might replace or get added to the list.

RELY ON YOUR MISSION STATEMENT

Your mission statement defines the core purpose of your business. There’s a delicate balance required between keeping it broad enough to encompass your long term vision, yet narrow enough to define your identity for both your employees and your customers. A good mission statement represents what you stand for in specific, actionable ways. It paves the way for how your employees interact with your customers. The length of your mission statement may range from a sentence or two to several paragraphs, a good rule of thumb would be to keep it as succinct as possible in order to avoid providing too narrow a focus and thus reducing strategic flexibility. Also, keep in mind that your mission statement can evolve over time to adjust for the market, your competitors, and your customer’s needs and desires.

DESIGN YOUR USER AND CUSTOMER EXPERIENCES

The broad definition of User and Customer Experience includes how your customers interact with all facets of your business. Rely on your mission statement and understanding of your customers to help define how you want those interactions to occur instead of leaving it to chance and risking a negative experience. For instance, if you wish to present your organization as caring and supportive to your user base, friendlier language and a welcoming user interface on your website or software would communicate your caring and empathic intent.

User and Customer Experience is about setting and meeting the users’ expectations through clarity of messaging and purpose. Keeping the customer experiences in mind at all times when developing your business processes will help ensure that your customers stay positively engaged with your organization.

By tailoring your business strategies around your customers’ expectations and the driving force behind your mission statement, you can create specific user and customer experiences.  These experiences reinforce their expectations and your mission statement, creating a sustainable, healthy feedback loop. For example, McDonalds recently responded to customer requests by running focus groups to test the viability of providing all-day breakfast service to their fans. Before simply agreeing to these requests (the first of which were posted in 2007!), McDonalds tested the viability of the service through focus group and user testing in small markets in order to ensure that the service could be provided within customer expectations. This is a great example of using feedback and relying on thorough user and customer research to improve brand perception through ensuring consistent customer experience, even for new offerings.1

By leveraging this valuable feedback loop to guide the underlying framework of your business decisions, you can ensure that your organization adjusts to changing expectations and trends, keeping your brand fresh and relevant for as long as possible – while keeping your customers engaged.

1The Story of How McDonald’s All-Day Breakfast Came to Be

 

 

Oct 20 2018
Oct 20

The most common way to post content on a web page is via HTML text, images, audio, and video. No matter your approach to content delivery, you probably know that your approach needs to be accessible. Did you know that non-web content such as Adobe PDF documents needs to be accessible as well?

Is your restaurant menu downloadable? Do you post your meeting agendas? What about event brochures or product catalogs? PDF files are great for such purposes and need to be accessible.

Did you know that the rules you follow to create accessible HTML content, also apply to non-web content such as Word and PDF files? You might be wondering how one makes non-web files like PDFs accessible. That’s where the Web Content Accessibility Guidelines (WCAG) comes into play. Of course, not all will apply such as Bypass Blocks and Captions for video but the WCAG criterion will be your guide. 

Let’s consider some of the guidelines that will apply to non-web documents.

Applicable WCAG Criterion

When creating documents, you need to cover the basics. 

  • Declare the document’s language.
  • Include a title for your document
  • Use Header styles instead of manually bolding a header or changing its font size
  • Ensure that said headers are orderly, that you don’t jump from header 2 to header 4, for instance
  • Include a brief description of your images via alternative text 
  • Ensure color contrast ratios are met
  • Identify the meaning of shapes and icons that you might use
  • Declare header row in any data tables you create
  • Resist the urge to use tables to manage your content layout
  • Ensure that embedded links have a clear purpose (no “Click here” links)
  • Remember not to leave inline bookmarks hanging without its partner link

The more complicated the PDF, such as those with forms, you will need to meet another criterion.  However, for your basic content document, hopefully, you are thinking that this list doesn’t sound too bad. If not, you have help. If you miss something while creating your PDF, Adobe Acrobat has an accessibility testing tool that will remind you to check things it can’t, tell you if it sees something wrong, and will give you help to fix the issues.

But, let’s not get ahead of ourselves. The first step in the process of creating the accessible PDFs.

Create a Source File

Microsoft Office, Corel, Google, and Adobe are just a sampling of product vendors whose applications can create PDF files after its user has created a source file. Perhaps you are using one of these or some other application. As long as your source file can be made to accommodate the requirements listed above before you export a PDF, then you are well on your way to creating an accessible document.

Save As or Export a PDF

If you create an MS Word document, for example, the process is to save as a PDF. If you create an InDesign document, the process is to export. Whatever the vernacular, convert your source file into a PDF.  

Convert does not mean print to PDF, nor does it mean scan to PDF. Both of these options create an image of the text. That means assistive technology cannot see the text. 

Sadly, not all conversion processes work perfectly. That means testing and repair is required.

Test and Touch up the PDF

Even if you have a simple Word document with sections and subsections divided by headers, you can still run into issues once the file has been converted to PDF. Use the accessibility testing tool in Adobe Acrobat to check for hidden issues. 

For instance, by default, the Acrobat accessibility test result will likely tell you to check your color contrast - assuming you are using color in your document. It might also say you don’t have a title when you do. FYI, the title being requested is part of the document’s metadata. Lastly, it will likely ask you to check the logical reading order of your content. 

You might think that checking the logical reading order can be ignored. You created a document whose content is presented in a logical order. How could it have possibly changed? Just to be sure, you scroll through the PDF and see that all is well. 

Logical reading order isn’t about what you see, it’s about the order assistive technology will read the content. So, be sure to click on Reading Order in the Accessibility options in Acrobat. Make sure that the numbers assigned to each item on the page convey the actual order. You would be surprised how often the reading order differs from what you see.

There could be other issues the test reveals. Don’t worry about not knowing how to fix all the issues it finds. Acrobat provides links to short tutorials that explain how to remedy an accessibility problem it has found. 

However, before you fix something in the PDF, make sure it was formatted correctly in the source of the source file. It if is not, fix it there and convert again.

Conclusion

If you have a choice between placing content on your site via a PDF versus HTML text, consider the HTML text first. HTML text is more accessible than a file that has to be downloaded. Plus it is easier to format HTML text and images to be accessible.

If faced with a multi-page source file that can’t easily be ported into HTML text, then plan ahead. Allow time to inspect your PDF’s reading order and remedy any accessibility issues before you put it online.

Not sure you have a problem? Email our Accessibility Experts - they can evaluate your site, and provide you with an Accessibility Scorecard. If you know your documents are a problem, we can estimate the cost of remediating those documents. 

Oct 18 2018
Oct 18

A web page in Drupal is made up of several parts. For instance, you have the header and navigation that appears on each page. You have the main content region that holds your articles or the details associated with your events. On either side of the content, you might have sidebars with blocks suggesting related content or a call to action. 

Typically, each part of the page is created or managed by different members of your website team. The developers that originally created your site will have set up your header and menu, for example. You might have a trained IT member of your team tasked to create and place blocks in the sidebars as needed. Then, when a content author publishes an article, those blocks appear as planned on the article.

A setup like this taxes your IT team and limits your content authors. Let’s explore how content types, fields, and views can empower your authors to influence the block that appears in the sidebars from article to article.

Planning Your Blocks

A simple exercise in the planning process is to ask the question, when X-type of content is published, what blocks should also appear? Traditionally, this would mean a fixed set of blocks configured to be visible on that content type or based on the URL alias.

But, what if you need a more granular approach to creating and enabling blocks? What if you wanted your content author to create and enable blocks without having to train them to be a Drupal builder?

Let’s explore an example scenario where you list all the blocks you might need from one article post to another:

  • More like this
  • Related training
  • Call to action
  • Archive
  • Guest speakers

A few of these blocks can be set up during development to activate automatically. For example, if the article is tagged as a container garden, then other articles tagged as such will appear in a "More Like This" block. But what about Calls to Action? Let’s take a closer look at those blocks that can’t be predicted with ease.

Related Training

You could design a Related Training block much like the More Like This block where training events would be listed in the block just because they have been tagged with the same term. 

What if the content is a how-to piece giving a sneak preview to one of the more simpler tasks that will be taught in a series of training events? In this scenario, the author wants to control which event to advertise, but she doesn’t want to include that advertisement in her narrative.

So, in the narrative content type, you add a field that allows the author to reference the training event nodes that are directly associated with the content of the how-to lesson. Following the same concept as in the previous example, you hide the event reference field and print it via a Views block. The block appears in a predestined spot on the page.

With this approach, with some planning, the block can be configured to include a thumbnail image taken from the events in question along with date and time information, making it more than a list of the titles that appear in the reference field.

Call to Action

Your content author has created an article about a new technology that will be presented at the conference. You are not presenting a session, but you will be hosting a networking event for attendees who want to extend their conference experience and meeting others in the field. The article is not the event. There’s an event node in another section of the site.

You want a Call to Action block to appear with this article, giving site visitors a link to sign up for the networking session. The common practice would be to create an advertising block and then place that block to be visible for this specific article.

Another strategy would be to add a field set to the content type you use for your narratives such as blogs, news, and how-to lessons. You would add an image field, a text field, a link field, and an on/off field. They would not be set to show. Instead, a contextual view block would be created, one on the lookout for someone to fill in the call-to-action fields and turn it on.

The Call to Action block will show up at the author’s discretion in a place on the page decided by the User Experience designer during the planning phase of your website development project.

Archive

Drupal 8 ships with a predefined View called Archive. It provides a block that lists months and includes a number representing how many nodes were published in that month. By default, all nodes are included but that doesn’t mean you can’t add filters to limit what gets included in the count.

Not all narrative content will be enhanced by including an Archive block, therefore having it enabled by default, could take up screen space needed for other more useful blocks. So, how does a content author turn this block on and off as needed? 

First, identify the scenarios where your users would benefit from being able to find previous narratives in common with the one they are viewing.  Then, using the same strategy applied for the Call to Action block, add an on/off field for the Archive block. Edit the Archive View to look for this field to be set to on.

This scenario and the previous one will depend on your trust in the author to know when to turn on Call to Action and/or Archive. That’s where business rules come into play and ensuring all know how to follow them. 

Guest Speakers

This time, your content author is creating an event with multiple guest speakers. You have decided that creating a speaker page for every guest could amount to many nodes that aren’t worth maintaining. Instead, you want to link to the speaker’s own website.

Of course, you could make this information available is a list of links as part of the event, but given all the data you are already including, it’s been decided that highlighting the speakers in their own blocks is a better option.

Using the same strategy enabled in the Call to Action scenario, you create a set of fields: image, text, link, on/off. This time, however, you need the ability to have multiple speakers so you need this set of fields to repeat. There is a module called Paragraphs that will be your friend in this example.

Paragraphs allow you to create a set of fields that can be repeated on the page. Instead of including them in the display, you use a View to show the information in a block.

Performance

You might be starting to wonder about the performance of your site with all these queries on the database. And, you would be right to be concerned if you had no caching plan in place. Outside of Drupal, you have caching tools such as Varnish that can help deliver your pages quickly.

Have a Plan

When it comes to Drupal, using your imagination is key to empowering your content authors. Start by mapping your processes. Ask yourself what has to be available in order to execute the process differently.

Remember, you don’t have to teach your content authors how to create and place blocks. You can plan ahead and give them simple options within the environment they will already be working. Assuming default processes are your only option can frustrate your users.

Need Help?

Promet offers best practice Training to help give your team the know-how to be prepared for these scenarios. Want to run scenarios like this by our experts to get advice on pages, or even plan a new website from the ground up? Promet is happy to create small and large planning exercises for you and your team to get the most out of your Drupal site.

Oct 15 2018
Oct 15

If someone sues you because your website has accessibility issues, it usually means they need you to fix said issues. Sadly, there will be those lawsuits where the complaint is trigger more by the desire of monetary compensation from a settlement than the present accessibility issues, but in either scenario, there has to be grounds for the complaint which means something needs remediation on your site. 

Why are we stating the obvious? Because it's not obvious to all who find themselves with a letter or lawsuit claiming that their website is inaccessible and therefore discriminates against individuals with vision, hearing, and/or physical disabilities under ADA Title III.

Defenses against inaccessibility claims that have been seen in the news include:

  • Websites aren’t included under ADA Title III
  • Even if they are, it’s moot in this case

ADA Title III Defense?

On October 31, 2017, a letter was sent to The Honorable Jeff Sessions, Attorney General, United States Department of Justice, and signed by sixty-one Members of Congress, urging the DOJ “to restart the process of issuing regulatory guidance regarding the Internet under Title III of the ADA.”1

Restart? Yes. 

In this same letter, the sixty-one Members of Congress reminds the Attorney General that the DOJ, in their 2010 ANPR, states “Although [DOJ] has been clear that the ADA applies to websites of private entities that meet the definition of ‘public accommodations,’ inconsistent court decisions, differing standards for determining Web accessibility, and repeated calls for [DOJ] action indicate remaining uncertainty regarding the applicability of the ADA to websites of entities” included in Title III. 

Unfortunately, the 2010 Advance Notice of Proposed Rulemaking2 where “the Department encourages small entities to provide cost data on the potential economic impact of adopting a specific requirement for website accessibility and recommendations on less burdensome alternatives, with cost information,” has been given a status of inactive under Trump’s Unified Regulatory Agenda released in July 2017.3 

On July 19, 2018, another letter was sent to the The Honorable Jefferson B. Sessions, III by the Attorneys General of 18 states and the District of Columbia on the same topic sent by the Members of Congress.4

If the DOJ recognizes that Title III is unclear, is it no wonder that site owners still try to claim that websites aren't included in Title III? No. 

However, as you read about website accessibility cases in the news, it’s clear that the courts have decided that it does. Whether it was the Winn Dixie case in June of 20175 that set the precedence or that the plaintiff in this case has brought other similar suits since then, it doesn’t matter. Compliance with the World Wide Web Consortium’s Web Content Accessibility Guidelines (WCAG), level AA is here to stay. Whether its WCAG version 2.0 or the recent 2.1, courts are ruling that these guidelines must be met.

So, what other defense can a business make to stop a website accessibility lawsuit? Other than remediating the problem?

Moot Defense?

If you aren’t a lawyer, you might be scratching your head right now. Moot? Don’t worry, you’re not the only one. Let’s start with a simple example.

Carroll v. New People's Bank, Inc.6

Filed in November, 2017 and terminated in April, 2018. First, please note the length of time required to adjudicate this case, only to have it dismissed. Here is a brief look at what transpired.

  • “NPB's website contains accessibility barriers, which Carroll alleges prevent him from using screen reading software to freely navigate the site.”
  • “NPB informed Carroll of its intent to develop a new website by letter in November 2017, prior to the filing of his lawsuit. In this letter, NPB stated that they had "voluntarily made a number of improvements" to the website and had "retained a third-party to develop a new website for the bank which [would] further improve [the website's] accessibility and client service feature-set."”
  • “Carroll argues that this new website does not render his claim moot because there is no guarantee that NPB will not revert to its former inaccessible website in the future.” 
  • “NPB has moved to dismiss the Complaint for lack of standing.”
  • “NPB contends that, in any event, Carroll's claim is now moot based on its voluntary upgrades made to the website after this action was filed, which upgrades Carroll does not dispute.”

Obviously, there’s more to this case than the snippets provided here. In fact, the case is interesting reading. Bottomline, NPB responded to Carrol’s letter, fixed the site, and the case was dismissed.

Haynes v. Hooters of America, LLC7

This next case isn’t as straightforward as Carroll’s claim being moot. This one is about getting sued twice for the same issue. Here is brief look at the ruling.

  • “On April 4, 2017, Haynes sued Hooters in the United States District Court for the Southern District of Florida …” In short, Haynes wanted Hooters to fix the accessibility issues on their site.
  • “Prior to the initiation of Haynes’ suit, on August 22, 2016, a different plaintiff filed a separate and nearly identical website-inaccessibility lawsuit against Hooters. Less than three weeks after the filing of that suit, the parties reached an agreement and settled their dispute (“Gomez Settlement Agreement”) ...”
  • “Hooters moved to dismiss Haynes’ suit, arguing that, because Hooters was in the process of actively implementing a remediation plan for its website, pursuant to the Gomez Settlement Agreement, there was no live case or controversy and Haynes’ claim must be dismissed on the mootness grounds.” They had until September 2018 to fix their site.
  • The district court agreed with Hooters and dismissed the case.
  • But, Haynes didn’t agree, and neither did the Eleventh Circuit in their June, 2018 ruling that “the case is not moot.” 

Again, there is more to this case that is briefly summarized here. In short, Haynes had no way to know or to ensure that the remedies being planned would resolve the issues he was having with the site. Therefore, his claim was valid. Yes, you can get sued twice for the same thing if the issue is still present on your site. 

Lessons Learned

There are four lessons worth mentioning. 

Audit Your Site Before You Get Sued

There is no argument that it’s going to cost you money to have your site audited appropriately for accessibility issues and ultimately remediated if problems exist. You could wait to see if you get caught but at that point, your costs include legal fees plus the audit and remediation.

Other costs include the negative publicity that can ensue. Web accessibility cases are hot topics and will remain so due to the lack of specific ADA regulations from the DOJ. People want to know how courts are ruling and that means numerous blog posts and speculation where your business’ name is spattered over the Internet.

Website Accessibility Insurance

Insure your site. You heard right. Insurance. You have a site right now. You think all is well. You have processes in place that audit content as it goes live to ensure there aren’t any issues. You have run an automated tool on sample pages and everything looks okay.

However, as a person that drives a car or owns a home knows, you can never predict when something is going to go wrong. That’s why you have insurance.

Don’t believe that such insurance exists? Think again. Beazley Insurance is working with Promet Source to offer insurance against ADA website compliance claims. Said policy includes up to $25,000 coverage for an accessibility audit and remediation if someone files a claim against you.

“In 2017, 7,663 ADA Title III lawsuits were filed in federal court — 1,062 more than in 2016.”8 “If ADA Title III federal lawsuit numbers continue to be filed at the current pace, 2018’s total will exceed 2017 by 30%, fueled largely by website accessibility lawsuit continued growth.”9 Add to these numbers the cases brought in state courts and it’s not hard to believe that you could get sued in the near future.

Move Quickly

If you get a letter, move quickly to remediate those items specifically noted. In the case of Carroll v. New People’s Bank, even if Carroll could prove standing, in the long run, NPB responded quickly and fixed the issues in the letter. 

Has Hooters moved quickly? How much money do you think Hooters could have saved in legal fees by taking down their inaccessible website and quickly replacing it with a simple, accessible website until their new site could be designed, developed, and launched? You decide.

Quick Might Not Be Fast Enough

It’s clear that people with disabilities are no longer hesitating to file suit for an inaccessible website. Whether they have standing or not, you could be faced with one lawsuit after another until you can audit your site and remediate it accordingly. And, given the findings in Haynes v. Hooters of America, LLC, the courts might let each lawsuit stand. So, circling back to the first lesson, have your site audited using automated and manual testing, get it fixed if issues are found.

Conclusion

Until the DOJ responds to the pleas of lawmakers across the nation to create specific regulations regarding website accessibility, courts will continue to review other cases to determine what’s moot or not. Don’t wait to find out. Get audited. Fix the issues.

If you don’t know what to do, Promet’s Accessibility Audit, Remediation, and Training Roadmap will help you end a current lawsuit and prevent any future lawsuits.
 

Footnotes

1. https://www.cuna.org/uploadedFiles/Advocacy/Priorities/Removing_Barriers_Blog/ADA%20DOJ%20ES-RD%20Letter%20-%20FINAL.pdf
2. https://www.ada.gov/anprm2010/equipment_anprm_2010.htm
3. https://www.reginfo.gov/public/do/eAgendaMain
4. https://www.cuna.org/uploadedFiles/Advocacy/ADAAGLetter71918.pdf
5. https://www.adatitleiii.com/tag/winn-dixie/
6. https://casetext.com/case/carroll-v-new-peoples-bank-inc
7. https://law.justia.com/cases/federal/appellate-courts/ca11/17-13170/17-13170-2018-06-19.html
8. https://www.adatitleiii.com/2018/02/ada-title-iii-lawsuits-increase-by-14-percent-in-2017-due-largely-to-website-access-lawsuits-physical-accessibility-legislative-reform-efforts-continue/
9. https://www.adatitleiii.com/2018/07/website-access-and-other-ada-title-iii-lawsuits-hit-record-numbers/
Sep 19 2018
Sep 19

You can’t build a website without a plan. A plan derived from requirements collected and a design created. You also need a development and testing plan that reflects the appropriate strategies for meeting said requirements and design. After you launch your website, you need a maintenance plan to ensure that your code remains secure, your content remains accessible, and your future features are integrated correctly.

Of all the development methodologies, past and present, there is not one that supports the development of software without requirements and design. When choosing a methodology, be it one based on the 12 principles listed in the Agile Manifesto, or not, you will not be able to avoid the effort of creating plans.

Agile Misunderstandings

Among the many misunderstandings regarding Agile methodologies is the aspect of planning. The belief that upfront planning isn’t needed and therefore time can be saved on a project is a misunderstanding of the iterative and incremental approach to software development. Think about it that for a moment. Can you create or build anything without some kind of plan? Be it simple or extensive?

It’s also a misunderstanding that said plans, if any, don’t need to be documented. If you choose an Agile methodology, you will quickly learn about Epics and the Backlog. Epics are large user stories while the backlog is a list of requirements derived from said user stories.

So, Agile isn’t about skipping the planning aspects of the project. It’s about changing the way the planning and development are conducted. And, the first step in the process of planning your site is gathering the appropriate players together.

The Right People

If you are going to put out a request for proposal, you need to include some of the requirements. Perhaps not all the details, but enough that a vendor who wishes to bid on your project can anticipate potential costs. Later, these initial requirements will fleshed out with the vendor whose bid you choose.

So, who needs to be in the room when you start brainstorming what you need? Who will ensure all requirements are identified? 

  • The money person would be good. They will know the budget and can remind you of the fact as the ideas start to mount.
  • The content manager is important. You will need to understand the tasks involved in creating and posting your content. For instance, how will you manage the publication of your content once it is uploaded to your site?
  • Let’s not forget the person who is in charge of your current site. This is the stakeholder who knows where the bodies are buried. They know why the current site is what it is and if certain aspects of the site can't change.
  • Other process owners. Depending on the tasks that your site will support, such as e-commerce or document download, who knows the most about how these tasks should be performed?
  • The naysayer. The squeaky wheel. Who is your Eeyore. “It will never work.” Get them in the room because you want the devil’s advocate. You want to hear what might not work and why.

Bottomline, anyone responsible for an aspect of the site, be it backend support or frontend interactions, get them in the room. You want to cover all your bases.

Agile Upfront Planning

“In 1998, Alistair Cockburn visited the Chrysler C3 project in Detroit and coined the phrase ‘A user story is a promise for a conversation.’”1 Then, in 2001, Ron Jeffries, one of the original signatories of the Agile Manifesto, proposed a ‘Three Cs’ formula for user story creation: card, conversation, confirmation, making user's stories part of the world of Agile methodologies. Coupled with use cases, Agile planning seeks to identify requirements and design before development begins.

However, as you will see, the level of requirements detail depends on several factors such that not every minute decision is made at the start. Let’s look at this idea more closely.

User Stories

User stories are typically brief statements written from the user’s perspective. For example, “As the content author, I need to be able to edit a page so that I can add a header image.” The documentation of such statements can be facilitated with index cards, Post-it notes, wireframe sketches on printer paper, or anything that meets your team’s needs.

A collection of such user stories helps to confirm the scope of the project and can reveal foundational requirements such as which framework or platform to use. Such stories also reveal relationships and thus where shared code will be used, for instance. 

At this point in the planning process, the team might decide to start developing. Such a decision is made possible by today's systems and platforms with plugin and play capabilities. They provide a way to support the user story tasks so that said tasks needn't be reinvented via a use case.

If user stories are unique and more detail is needed, creating use cases is the next step.

Use Cases

If system default tasks are not what is envisioned or additional tasks need to be supported, the team may choose to clarify the user stories via use cases - details of actions and events that define how a user interacts with the system. 

Deeper investigation into the requirements can help define a development path that supports both the overall system architecture required but also the specific tasks required of the system.

Once the stakeholders and development team have gained a common understanding of what is required, the user stories and use cases are converted into epics and the necessary backlog of development tasking.

So, Agile methodologies support the requirement and design phases listed in the Waterfall methodology, it just does it by engaging methods that have proven easier for end users to envision as they communicate what it is they want from the product being created. 

Of course, this isn’t the only time during the iterative and incremental development approach where planning takes place.

Agile Planning in Development

With epics and a backlog populated, the development team plans a series of iterative and/or incremental development efforts, commonly referred to a Sprints. The way the Sprints are defined depends on the overall development strategy required to build out the product, in this case, a website.

Before each Sprint, the existing requirements (based on user stories and use cases) are reviewed and specific strategies are chosen for meeting said requirements. This might include a conversation where details are clarified or added to use cases.

After each Sprint is complete, the product owner is asked to confirm that expectations have been met. If not, requirements and design aspects can be changed to correct misunderstandings or to acknowledge a new idea or need. In other words, additional planning is interjected into the development cycle and the project is adjusted.

In addition, lessons learned are collected and decisions are made regarding how-to strategies for the next Sprint. You might be thinking that enabling changes to the original plan might introduce scope creep. And, you would be right. It can.

Planning and Scope Creep

Scope creep is similar to what happens when you think you are buying the base model of a new car and you leave the lot having spent 20% more than planned because you decided on several add-on features. 

Several factors can influence the possibility of scope creep on a website. Let’s consider two related to planning.

  • Insufficient upfront planning. We aren’t talking about getting into the details of how features on your site are developed in this instance. Instead, it’s about ensuring that all user stories have been identified along with supporting decisions. For instance, if the user needs to be able to categorize an article, has the supporting requirements such as the information architecture been defined? 
  • Incorrect stakeholders at the planning table. The budget folks will have a different take on requirements than say an end user. Content manager will be able to enlighten decision makers on processes that are required to ensure a specific level of content quality. Without the appropriate people involved in the planning process, you might find that a Sprint doesn’t meet expectations.

Conclusion

An Agile approach to website development relies on planning to be successful, however, not all planning is required before development starts. Of course, there are risks associated with moving quickly into development, one being scope creep. 

The power of Agile methodologies isn’t about being able to skip steps that a waterfall methodology is criticized for enforcing. It’s about being flexible. It’s about being able to adjust as forgotten requirements are remembered. And, it’s about continuous feedback, ensuring what was originally thought to be a good idea, still works. 

Promet and Planning

Promet offers a unique planning engagement that we call our Architecture Workshop. This workshop is a customized engagement that engages all of your stakeholders in the Discovery Process.We do a 3-5 days of intensive onsite exercises with stakeholders (for your busy C-level folks we customize the agenda to bring them in where they are needed during this onsite). Then the team goes away and produces a set of deliverables that  includes a full-field level Architecture Blueprint of the website(s). Whether you choose to use a waterfall or agile development methodologies - you have everything you need to build the website everyone has agreed upon. 

Not building your site and stressed out about getting an accurate quote? Investing in this kind of Workshop will make sure that you get the right Partner, and the best price.

Footnotes

1 
https://en.wikipedia.org/wiki/User_story
Aug 30 2018
Aug 30

Perhaps you’ve heard that the W3C (World Wide Web Consortium) has updated their Web Content Accessibility Guidelines (WCAG) 2.0. 

  • On April 24th, 2018, W3C posted a proposed extension of Web Content Accessibility Guidelines (WCAG) 2.0, referred to as WCAG 2.1.
  • On June 5th, 2018, WCAG 2.1 was no longer considered a proposal. WCAG 2.1 includes 2.0 and 17 new criterion.

When will I need to update my website?

Is there a law someplace that answers this? An official interpretation? A lawsuit that references the new criterion?

To date, in the United States, there is an understanding that WCAG 2.0, levels A and AA, is the required version and levels of accessibility required to create an ADA compliant website. Court case summaries posted by the legal community say this is so.

But, as of August 2018, this reviewer can’t find a court case that references WCAG 2.1. 

Should you sigh in relief? No. Right now, the courts are interpreting Titles II and III and hearing complaints. Will a judge bring his or her hammer down on one of the new criterion if you aren’t compliant with it? Quite possible. One would hope for a reasonable ruling: no penalties and perhaps a date allowing you time to fix the issue given the newness of the additional criterion.

As soon as this happens, you have your precedence. You have your clock. Of course, until Section 508 is updated, federal site owners are protected, but that doesn’t mean said site owners should ignore the new criterion as they update or rebuild their sites.

What kind of changes will we see?

WCAG 2.1, according to https://www.w3.org/TR/WCAG21/, “was initiated with the goal to improve accessibility guidance for three major groups: users with cognitive or learning disabilities, users with low vision, and users with disabilities on mobile devices.”

The fact that these new criterion were added with mobile devices and users in mind should not come as a surprise. In 2015, the W3C released Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile. They’ve been working accessibility for mobile devices for some time. 

Are we talking about a lot of change?

Depends on what you are doing on your site. It’s possible you have nothing to do or change in order to meet one or more of the 17 additional criterion. Perhaps you are hoping that most of the 17 criterion are level AAA and you won’t be held accountable. Let’s clear this one up right now. Twelve of the 17 are A or AA.

At this point, we could simply list the new criterion by the principles of POUR (Perceivable, Operable, Understandable, Robust) or by level, leaving you to mentally map the criterion to how you think about your site and its functionality.

Instead, the following is offered in hopes to provide a unique and helpful perspective on the new criterion.

  1. Interactions and Orientation
  2. Content Structure
  3. Visibility
  4. Cognitive

Each criterion will be briefly explained. You will benefit from reviewing the criterion’s Understanding pages as that is where you will find a more precise set of instructions.

Interactions and Orientation

Your site is “touched” and “viewed” using multiple methods.

The oldest method being via mouse or touchpad and the pointer they control on a computer monitor. Next up is the keyboard and monitor. WCAG 2.0 included criterion 2.1.1 Keyboard, for example, to address keyboard tabbing on websites. 

Given the fact that mobile devices and touchscreens are pervasive in the world today, it’s no surprise that several of the new criterion are focused on “touching” and “viewing” said technology.

  • 1.3.4 Orientation (A)
  • 1.3.5 Identify Input Purpose (AA)
  • 2.2.6 Timeouts (AAA)
  • 2.1.4 Character Key Shortcuts (A)
  • 2.5.1 Pointer Gestures (A)
  • 2.5.2 Pointer Cancellation (A)
  • 2.5.4 Motion Actuation (A)
  • 2.5.5 Target Size
  • 2.5.6 Concurrent Input Mechanisms (AAA)

Success Criterion 1.3.4 Orientation (AA)

Bottom line, don’t prevent someone from viewing your content in the display orientation of their choosing. Of course, there are exceptions, but if you don’t have to lock your content in portrait or landscape display, then don’t. This isn’t a feature you would accidently enable, especially if your site is responsive.

Success Criterion 1.3.5 Identify Input Purpose (AA)

You know when you fill out a form online that includes your name and maybe your address and all you have to do is start typing and you are given the option to autocomplete the form? Autocomplete is a feature in HTML5.2. This works because there is a defined purpose to the field.

Criterion 1.3.5 is about ensuring the purpose of the field is clear. They reference the autocomplete technology as a means of satisfying this criterion. However, the intent is “to help people recognize and understand the purpose of form input fields. … form input fields require programmatically determinable information about their purpose.”

If you have forms on your website, you might want to look into whether you are already using HTML5.2 and providing input purposes.

Success Criterion 2.2.6 Timeouts (AAA)

Not everyone can interact with your site forms quickly. It can take time to fill in a field thus creating lengthy interactions.

So, are you collecting job applications online via a form? Are your visitors entering data for anything that might take more than a minute or two? This one's for you. 

It’s likely that you are already advising your visitors that there is a time limit for interacting with your site, if indeed there is one. If not and there is a chance that their efforts will be in vain if the session times out, you need to warn them. If you are storing their data as they go along and thus there are no concerns if they walk away and return the next day, providing a timeout notice is not required.

Success Criterion 2.1.4 Character Key Shortcuts (A) 

Are you adding keyboard functions to your pages? No? Then you are good to go. If yes, then you have a new criterion to review. You don’t want to override an existing keyboard shortcut implemented by assistive technology. This criterion give you guidance in the changes you might need to make.

Success Criterion 2.5.1 Pointer Gestures (A)

What are pointer gestures? Have you ever used two fingers to zoom in or out on your mobile device screen? If you are providing an interface, such as a map, where the user would want to zoom in or out, you might need to add a single input option. According to W3C, including [+] or [-] buttons will accommodate this criterion. For other examples, visit 2.5.1’s Understanding page.

Success Criterion 2.5.2 Pointer Cancellation (A)

Have you ever clicked on a link and upon pressing down you wish you hadn’t? Perhaps you know that moving away from the link as you release your click will cancel your request. Well, in this criterion, they are focusing on actions you might have added to your page via Javascript, for example. Actions that would prevent a click or touch from being cancelled.

If you have, you need to edit your code to not include a down event such as touchstart or mousedown. W3C includes other alternatives to tweaking your code. Instead of repeating the official details here, please visit 2.5.2's Understanding page.

Success Criterion 2.5.4 Motion Actuation (A)

Do you have an app? Is your site presented via an app? If yes, this one might apply to you. This criterion is focused on interfaces that respond to device movements. Not a common feature on websites presented via a browser but definitely a possibility in apps you might be using to present your content.

If you have added functionality to your app that, for example, advances a user to the next page when they tilt their devise, then you need to pay attention to this one. Users need the option to advance to the next page via the user interface and not when their hand accidently moves, mimicking a tilt.

To prevent your application from behaving as such in a mobile device,  you need to add a setting that disables the response to movement.

Success Criterion 2.5.5 Target Size

On a full screen display, it’s easy to imagine large buttons, for example, being acceptable from a design perspective. Shrink that web page down into a small mobile device and that button can become a tiny dot that someone has to hit with a finger or other handheld pointer.

If you have buttons or links or other features that require interaction, they need to be big enough to be touchable - even on the small mobile screens. The Understanding page for 2.5.5 presents a couple scenarios that you should review if you have such interactive links on your pages.

Success Criterion 2.5.6 Concurrent Input Mechanisms (AAA)

To say this is a level AAA criterion seems odd to this reviewer. Why would you prevent someone from using an external keyboard to enter data or interact with your site versus the in-device touchscreen? If you aren’t doing this on purpose and your site doesn’t care what a user uses (mouse, keyboard, touch), then you can check off a level AAA criterion.

If you have an essential reason for such a restriction, then, okay. Although the criterion doesn’t say you have to explain yourself, the instructions for such interactions might be a place to make this clear.

Content Structure

It’s not just words that convey meaning. It’s the style and shape of the content. You might recall two criterion introduced in WCAG 2.0 that focused on ensuring that a user of a website would not miss out on what the content is saying or implying.

  • Criterion 1.3.1’s intent is “to ensure that information and relationships that are implied by visual or auditory formatting are preserved when the presentation format changes.”
  • Criterion 1.3.2’s intent is “to enable a user agent to provide an alternative presentation of content while preserving the reading order needed to understand the meaning.”

Two new criterion have been added on this note. 

  • 1.4.10 Reflow
  • 1.4.13 Content on Hover or Focus

Success Criterion 1.4.10 Reflow 

If your site or app is already responsive, you are well on your way with this one. As long as your content fits in a user’s screen such that only one form of scrolling is required, then you are set.

Your goal is to accommodate a 320 CSS pixel vertical width. Or, 256 CSS pixel height. 

Criterion 1.4.10 is extending the efforts made by criterion 1.3.1 Info and Relationships and 1.3.2 Meaningful Sequence in hopes of ensuring content and functionality are not lost. This time, it’s about resizing versus removing visual and layout styles. If your responsive breakpoints are such that a user need to scroll in two directions to experience your content, then you need to update your code.

Success Criterion 1.4.13 Content on Hover or Focus

Do you provide popup content such as tooltips? You know when you hover over an image or text and you get additional information clarifying the image or text?

If you need to use this type of content delivery, WCAG 2.1 is recommending guidelines that will make such content easier to “see.” For example, when the popup tip appears, ensure that it remains until the user moves away from it. Also, don’t let the users pointer block the content in the popup. 

Of course, more details and explanation can be found on the criterion’s Understanding page.

Visibility

Not everyone can see small text. Not everyone can easily distinguish text from its colored background. WCAG 2.0 gave us three criterion to follow in an effort to accommodate such users of web content.

  • 1.4.4 Text Resize
  • 1.4.3 Contrast (Minimum)
  • 1.4.6 Contrast (Enhanced)

In WCAG 2.1, the following are added to this list.

  • 1.4.11 Non-text Contrast (AA)
  • 1.4.12 Text Spacing (AA)
  • 2.5.3 Label in Name (A)

Success Criterion 1.4.11 Non-text Contrast (AA)

You are already abiding by the contrast criterion for text and images of text if you are meeting WCAG 2.0. 1.4.11 makes some addition to contrasts.

First, you know when you hover over a button or link and it changes? That is a state change. You are going to need to ensure the change meets a 3:1 contrast ratio. Next, it’s not just about color on color but now there is a need to consider color next to color.

The Understanding page for 1.4.11 gives examples such as pie charts and icons lined up next to each other. The potential design impacts discussed on this resource page are definitely worth a read. Too many considerations to list here.

Success Criterion 1.4.12 Text Spacing (AA)

Similar to 1.4.4 Resize text, 1.4.12 wants to ensure that changes in the spacing between lines, paragraphs, letters, or words, they won’t lose content of functionality. So, you might need to check your CSS to ensure the following are possible:

  • Line height (line spacing) to at least 1.5 times the font size;
  • Spacing following paragraphs to at least 2 times the font size;
  • Letter spacing (tracking) to at least 0.12 times the font size;
  • Word spacing to at least 0.16 times the font size.

Success Criterion 2.5.3 Label in Name (A)

This next criterion isn’t as direct as the last two when it comes to visibility of content, but reminds us of the fact that there is more than one way to “see.”

Depending on how your pages were made, you might have both visible and invisible labels on your site. Visible for those who can see the label, such a sign-up button, and invisible, a version of the label that assistive technology reads. Similar to when you create a link to a page and ensured the link and the page title were the same, visible and invisible labels need to match.

What happens when they don’t? A user speaks the label they see and their assistive technology looks for the same words. When visible and invisible labels differ, the technology can’t find what the user needs. 

Cognitive

You don’t have to have cognitive impairment to not understand something. In WCAG 2.0, three criterion are worth noting when it comes to understandable writing.

  • 3.1.3 Unusual Words (AAA)
  • 3.1.4 Abbreviations (AAA)
  • 3.1.5 Reading Level (AAA)

Just because they are AAA level criterion, that doesn’t mean they should be dismissed. They are three of the easiest AAA criterion one can strive towards.

WCAG 2.1 has added criterion that this reviewer feels fits with enabling users of your content to gain a better understanding of what it is your are conveying.

  • 1.3.6 Identify Purpose (AAA)
  • 4.1.3 Status Messages (AA)
  • 2.3.3 Animation from Interactions (AAA)

Success Criterion 1.3.6 Identify Purpose (AAA)

It’s likely that you have at least one of the following on your site: user interface components (e.g., buttons, link, fields), icons, or regions. And, if you are following the requirements of 4.1.2 Name, Role, Value, you are defining most if not all of these.

However, what you might not being doing is providing information about what the component represents, such as an image link represents a link to the homepage. This criterion wants you to convey more than a name, even if the name seems to convey the applicable meaning. Remember, assistive technology is not Artificial Intelligence. It’s needs you to tell it what it can’t surmise on its own.

Success Criterion 4.1.3 Status Messages (AA)

If you are using a content management system designed for accessibility, like Drupal 8 for example, then you should be okay. If not, you will need to update your code to declare your system messages via a role or other appropriate properties that can be understood by assistive technology.

Success Criterion 2.3.3 Animation from Interactions (AAA)

Does this criterion address an interaction or is a cognitive distraction? Perhaps both.

Do you have things that move on your pages? Do objects fly in from the side as someone scrolls? Criterion 2.2.2 Pause, Stop, Hide from WCAG 2.0 applies when the page initiates an animated object. You might have heard of this one. 2.3.3 is intended to prevent animation from being displayed on the pages in the first place.

If you have a dynamic page with moving parts, you need to look into this one. You might need to add to existing animation controls and allow users to keep them from appearing. Of course, this is level AAA, but it’s worth considering as sudden movements can trigger vestibular (inner ear) disorders and cause dizziness, nausea, and headaches.

Conclusions

If you manage a federal site subject to Section 508, that doesn’t mean you shouldn’t take the additional 17 criterion into consideration when updating or building your site. As for everyone else, WCAG 2.1 is the recommended set of criterion. With the chance that someone might claim your site is non-compliant based on 2.1, you need to look into bringing your site up to date.

Remember, some of the new criteria are, by default, not going to be in play on your site. Many of them have to do with added bits of code that override default browser behavior that at one time were deemed acceptable. So, WCAG 2.1 doesn’t have to be scary.

Aug 30 2018
Aug 30

Since its launch, many have written about all the great technology that has been added to Drupal 8. You will find articles online talking about such added features as headless and responsive and accessible. You will read about modules that have been added to core, contributed modules once part of the standard recipe for configuring a Drupal site.

And, that's all good news if you are developer assessing building blocks and code. But, what if you are a business owner, marketing executive, or technical decision maker and don't speak Drupal yet? 

You have a laundry list of features and functionality you want supported by your site and you just need to know if, and a little bit of the how, Drupal 8 is going to meet your needs. Although a planning workshop and Drupal builder course could help you gain a strong understanding of Drupal, you aren’t there yet.

Recognizing this might be you, this article:

  • Shares some of the most common and not so common requirements that you might be facing, and
  • Talks about how Drupal can help support your processes and goals.

Common and Uncommon Features Don’t Scare Drupal

Drupal is a content management system, content being the operative word. However, Drupal doesn’t see content as a blog post or an event. It sees content as data. Data comes in all sorts of shapes and sizes. It carries multiple types of meanings, from the spoken word to value that triggers an action.

When it comes to identifying that which Drupal can’t do, this reviewer only has to stretch her imagination and a solution presents itself, often using existing functionality either from Drupal’s core and from millions that call themselves part of the Drupal community.

In order to demonstrate Drupal’s potential without the aid of video, the remainder of this article will address several capabilities - simple and a little more complex - in hopes that it will help you recognize that Drupal can meet your needs.

When working with managers such as yourself, request often start out as, “I want …” and finish with one or more of the following:

A Mobile Friendly Site 

You are likely one of the majority who surf the net using a mobile device like a smartphone and thus you know what it's like to visit sites that don't fit your screen. Perhaps you have decided that you don’t want to be that business that can't be easily experienced from any device.

Screen shot of default Drupal 8 homepage in it's most narrow display.

Drupal 8 makes it easier than ever to make responsive sites. Responsive means your web pages flex and reshapes automatically to fit your screen. Although responsive functionality was available in previous versions of Drupal, Dries Buytaert, the inventor of Drupal, decided that Drupal 8 would bring mobile to the top of his improvement list.

One of the first steps taken to make this possible was making the jump to HTML5 in order to gain such advantages as engaging the applicable input device when a site is viewed on a tablet or smartphone. 

Check out the screenshot showing Drupal 8 default homepage reduced down to fit on a smartphone.

Different Types of Content

This request often goes without saying and when it comes to Drupal, its response is, “Bring it on!” Any type of content you want, it’s yours. Plus, there is more than one way to get it done depending of the type of data you want to use to define said content.

Let’s consider an example. Story telling. This could mean that you have bloggers, new reporters, media reviewers, etc. At the core of this type of content, they are the same. It’s just the words and tone and organization that often makes these different. 

If you want a separate form to collect each type of content, then you can do that. Even if all the data fields you define are the same in each, Drupal doesn’t care. You can also collect this type of content using just one form with an additional field that lets you categorize the type of content.

This is a very simple example, but hopefully it’s already making you think about how your content can be viewed as data collected in fields versus what you might be used to doing with MS Word or other content management systems.

Since Drupal 7, this type of functionality was part of Drupal’s core. In Drupal 8, the coding structure has changed, enabling your developers to tap into the objects that make this possible and invent unique content collection tools that integrate with Drupal’s permissions and other default features.

Accessible Content Formatting

There are two methods associated with formatting worth mentioning: field-based and manual application. When content formatting comes to mind, you likely think of making text bold or creating bulleted lists. That’s cool. Drupal 8 has that covered by default.

Drupal 8’s text formatting is better than ever. Style your content in MS Word and copy/paste it into your Drupal 8 content form. Don’t do this with previous versions of Drupal, you could end up with a mess of code. Also, Drupal continues to offer settings that control which content author can, for example, add images to their blogs, or not. 

When it comes to using fields other than the traditional long text fields, you can apply styling via templates and CSS. Or, you can rely of the fact that Drupal 8 is WCAG 2.0 ready (likely to be 2.1 ready in the future) and much of the formatting you need is already in place.

Collecting Data Other Than Content

Drupal 7 not only added the ability to add fields for content collection forms, but it also added the ability to add fields to user accounts so that additional data can be collected and possibly displayed for your content authors. Drupal 8 continues this functionality but with the same object oriented strategies implemented for content.

Categorize Content

Categorizing content is at the heart of Drupal. Each Drupal site ships with one Taxonomy that can host multiple vocabularies (containers that hold terms). You can have as many terms (words or short phrases that describe or categorize content) as you need.

Drupal 7 included the ability to add fields to terms so, for example, you can associate an image of an orange with the term: orange. Drupal 8’s contribution, besides better backend code, it a new display page. When someone clicks on a term, they land on a page that displays all content tagged with that term. Drupal 8 makes it possible for you to easily modify that display right out of the box. 

Block Content 

Blocks are bits on content or functionality that can be added to a page. They typically appear alongside the main body of content, or below it, above it. Historically, you would create a block, for example that says, “Welcome to my site. Become a member …”. That block could be placed in one location, let’s say the right sidebar. By default, there wasn’t much more your could do without additional modules.

Drupal 8 has changed the block system. When this reviewer learned by how much, she couldn’t stop smiling. Okay, she might have shouted with glee. 

Anyway, not only can one block be placed in multiple regions at the same time, - in a sidebar and in a footer and in the region that displays the main content - it can display something other than the text. You can now display an image via a field. Or, a video. Or, an attached PDF file.

Yes. You heard right. You can add fields to blocks, made possible by the same object oriented strategies put in place for content, users, and terms. You can also have different types of blocks, just like you can have different types of content forms.

But that’s not all! If you have a block intensive website and you ever want to get a list of said blocks and the content they content in one report, you can query the database and get that list by using the feature called Views. The Views module used to be a contributed module, a staple in 99.9% of all Drupal sites - in this reviewer’s opinion.

Multilingual Site

With each major release of Drupal, the ability to develop a multilingual site got easier. Drupal 8 has not disappointed. Where Drupal 7 required up to eight or so contributed modules to create a multilingual site that was 99% correct, Drupal 8 has four in its core to make it happen.

Coding practices that used to prevent text from being translated are a thing of the past if a module contributor wants their module to be accepted by the community.

It was possible in the past and even easier now.

Manage Content Development

It’s one thing to be able to structure your data you see fit, it’s another to manage the development of said content or data. Aside from the creative nature of content development, you have the ever present need for copy editing. And, if you believe that your content authors can easily catch their own typos, think again.

It’s fortune that the Drupal community recognized the need to manage the process from “I have an idea” to a published work. Drupal 8 has jumped on the workflow wagon by including a workflow option you can turn on and configure. 

Whether your authors compose in MS Word or in Drupal’s content form, the first, second, or even the third draft shouldn’t be seen by the public. You can tell Drupal to save as unpublished. You can collect copies of every draft version by default and switch between them until you are ready for editing.

With additional functionality from the community, you will be able to do things like send notices with draft content is ready for review. You wouldn’t be the first to have this requirement and users of Drupal have been making this happen for years.

Reuse Content in Multiple Displays

This is not the first mention of content reuse. Drupal is all about content reuse. Break your content into structured data and you can find and filter until your heart's content. And, you can then share your queries with the whomever you wish.

Views has been around since Drupal 4, but has always been a contributed module. There are good reasons for waiting to integrate Views into Drupal’s core and now that it is here, Drupal out of the box is that much better.

Most notable is the administrative pages. Hard-coded in the past, the pages that list content and blocks and users and more are now made with Views. They are database queries made into page displays and thus allow you to easily customize your admin pages.

ADA Accessible Site

Accessibility has been mentioned already, but if you didn’t notice, it’s worth mentioning again. Taking a mobile first perspective when designing Drupal 8 was only one priority. Accessible web pages was right up there as well.

The developers of Drupal 8 have taken accessibility seriously. They have reviewed WCAG 2.0 and W3C’s WAI-ARIA. The Drupal community wants your site to be easily read by assistive technology and ARIA was a big step in the right direction.

Deep down, you know how important it must be to make web pages that everyone can experience. What you might not have heard about is the fact that the number of lawsuits for non-compliance has increased and continues to do so.

It’s not just about federal government sites anymore. It’s all sites. Drupal 8 provides a strong foundation to creating an accessible site from the start.

One System, Multiple Frontend Interfaces

You don't want two systems: one that will present your information in a web browser and one that will present your content in a mobile app. Data reuse is a key feature in Drupal and Drupal 8 takes the next step.

Drupal is now what some call “headless” and others call “decoupled”. It doesn't matter which word you use as this functionality is a technical thing that your developers can take advantage of when they present your data through multiple interface frameworks. 

What does this mean? It means you can serve up your content to an app who’s interface was created with a framework designed for mobile devices while at the same time, present content in a browser the traditional way. One blog post, two tools to manage said display. 

This simple example does not suggest that you can only have two frontend interfaces to your content. If you are looking for a central repository for your digital content and you want to deliver it to multiple platforms, Drupal 8 makes it easier than ever before.

Wow, talk about content management. Create it and edit it once and use it over and over.

Affordable Upkeep

This might be the last topic, but that doesn’t mean it’s an afterthought. Like many software applications, significant changes occur from one major release to the next. Unlike many software applications, you don’t have to start over to use the next version.

For a time, you could actually upgrade your Drupal site to the next major release. This reviewer went from Drupal 4.5 to 4.7 to 5.0 to 6.0 before migrating to Drupal 7. Drupal’s backend restructuring to keep up with today’s technology introduced some challenges when it came to taking a Drupal site from version 6 to version 7 and the developers listened to the complaints.

So, Drupal 8 has a few features worth noting as they can impact the cost of managing and maintaining your site.

  • Drupal 8 ships with a Migrate modules to help you tap into Drupal 8’s new functionality by making it easier to migrate.
  • Drupal 8 ships with a Configuration Synchronization module that allows you to launch a version of your site and easily add new features as resources allow.
  • Drupal 8’s path to Drupal 9 isn’t going to come in one giant leap like past major releases. Drupal 8’s development is taking semantic path with releases such as 8.1, 8.2, 8.3, and so on until 9.0 is reached.

These three strategies alone make Drupal more cost effective than ever before. Your development team will have a learning curve to come up to speed on the semantic coding process, but otherwise, they will find Drupal 8 to much more conducive to long term commitments. 

Conclusion

If you want a system that can build just about anything, like one can do with LegosTM , then Drupal 8 is where you want to be. If you have a simple blog site or a content rich site viewed by the world, Drupal can handle it.

The advantages discussed above just scratch the surface of what is possible. Other requirements that Drupal can handle include:

  • Advanced permission settings
  • Powerful content development and layout options
  • Integration with other systems
  • Mash ups - pulling content from other sources
  • eCommerce
  • And more

So, if your requirements are anything like what was discussed above, or if you have something truly unique, let us know. We love a challenge.

Jul 31 2018
Jul 31

When it’s time for a new site, the word “migration” is often dropped in conversations. Every organization looking at a migration in the future will have their own reasons for doing so, their own history, their own future goals. In this article, we will present the following topics as a means to empower you to recognize aspects of website migration you might otherwise overlook.

  • What can a new site look like after a migration.
  • Triggers for a migration project.
  • Paths that might be taken.
  • Creating the right team.

The first two topics are going to feel like the chicken and the egg. Which one comes first? Given the linear nature of articles, they will be presented in said order, but that does not mean the order will match the scenario faced by many.

What can a new site look like after a migration?

Amazingly, not everyone has the same vision of what a new site might mean. Managing expectations from the start is critical to a successful migration project. Below are some common scenarios that can constitute a “new site” and/or “migration” that you might face in your project.

You will find that the following three categories can account for most changes.

  • Server environment change
  • Web platform change
  • Design and/or functionality change

After this, the triggers that might cause one or more of these changes is presented.

Server Environment Change

The process of taking an existing site and moving it from one web server to another would be considered a server environment change. It could entail moving your site from your own web servers to an external vendor.

From a new site perspective, this scenario doesn’t seem to fit. Technically, it doesn’t. Same code, same site. However, to your users, it might feel new if the site’s performance has improved. Your site could actually look different, assuming pages weren’t loading fully due to slow performance.

From a migration perspective, this is text book. You physically move - migrate - to a new server. In the process, you will receive upgraded or new web server features that will need to be configured to work with your site. A few examples include:

  • Caching services
  • Security configurations
  • Development, testing, and production processes.

Your website’s code might be the same, but the environment in which it lives has changed and therefore it cannot be assumed that there won’t be some work to make everything fit and function as required.

Web Platform Change

First, let’s assume that web platform refers to some type of content management system (CMS). The process of migrating from one CMS to another can yield a site that looks the same, but is it?

From the new site perspective, at a minimum, the code-base is different. The configuration strategy is different. The opportunities to improve or enhance your current circumstances can be different. Given the expense, your new system should be ready to allow for your growth in order to justify the expense.

From a migration perspective, to move your site structure, content, interactions, etc. from one CMS to another is a migration, by definition. Depending how similar the systems and how complicated the existing website, the effort to make the move can be extensive.

Example migration and level of effort scenarios might include:

  • Blog Site - Migrating a blog site from one CMS to another is likely the least complex scenario. Most CMSs are designed around enabling users to post their stories, articles, and blogs with ease so the leap should not be overwhelming.
  • e-Commerce/Product Site - The level of effort for this type of move will likely be more labor intensive than a blog site. You might be thinking, “A product is a product,” but the way the sale is managed can vary from system to system. Check out processes may differ. The way the product is loaded into the system may be simple in one, but the other CMS might offer more sales options that you need to consider.
  • Multi-function Site - Sites that provide some combination of blogs, products, events, community, manuals, custom integrations, and more will present even more challenges when moving from one system to another.

The pattern should be clear. The more complex the site that is being migrated, the greater the level of effort. This can include new planning effort, where you dig into the metadata level of content and features. Some CMSs are designed for data micromanagement and you will want to take advantage of the data reuse functionality such a system provides.

Design and/or Function Change

This is one place you will want to manage expectations up front. The scope of work implied by the word design can send your migration project into overruns very quickly. And, the idea of functionality (from a site visitor perspective or a content author’s perspective), can be interpreted many ways.

So, from a new site perspective, design and function will create the most obvious new-site feel. Whether it’s the layout of your pages, your branding, the way your information is organized and accessed, or the new online tools you add, a significant change will occur.

From a migration perspective, the move is to go from one site to another. This scenario is often combined with the first two: server change and platform change. Even if it is not, the effort for such a move is not unlike the process of planning, designing, and building a site from scratch. Even if ideas and content and branding are transferred unchanged, a version of the original website’s implementation process will need to be executed.

Triggers for a migration project.

Based on the discussion above, it might seem obvious what the triggers for change might be. That is true, to some extent. However, there are triggers that can cause a server change while others can cause a system change. Or, both.

Performing a trigger review is a good way to explore the potential, “What about …,” comments that can bubble up during development and trigger yet more change and scope creep. In this section, five triggers for change are presented, along with the type of migration that might be required:

  • Analytics
  • Search engine optimization
  • Technology
  • Mobile first
  • Organizational goals

Analytics Triggers

Web analytics are the statistical data collected about website usage. If the site is not being used, can an organization justify the expense of maintaining said site? Not likely, unless the implied triggers for change from said analytics are implemented.

Triggers of this nature can include:

  • Bounce rate - Site visitors are not spending enough time on site pages. They aren’t reading or watching or interacting as desired.
  • Low or no visits - Pages on the site are not being visited at an acceptable rate. They are either not being found, or their topics don’t meet the visitor’s needs.
  • Low or no mobile device visits - Of the visits, users are arriving on the site via a laptop or desktop. This could be justified given the site purpose, or it could be connected to the bounce rate concern, where people leave the page because it is not easily visible in a mobile device.

To remedy these situations, an analysis needs to be completed. Depending on the findings, the following migrations might apply.

  • Server change - If statistics are off due to poor performance - pages not loading in a timely manner, for example - a new server environment might do the trick. Cached pages are easier and faster to send.
  • Platform change - If statistics are off due to inaccessible pages, pages read by accessibility technology, new code is likely needed. Be it the code for the page structure or the code used to present the content, non-accessible pages can be costly in the long run due to lawsuits, for example.
  • Design and/or function change - If statistics are off due to an unfriendly Information Architecture that make site navigation cumbersome, or due to page layouts that don’t fit in the small screens of today’s mobile devices, a new design will be on your list of changes.

Search Engine Optimization Triggers

When a website lands on the first page of Google’s search results, you can claim success. You have made it. Your site will have visitors. You product will sell. You can now lean back and relax. Not really. Vigilant monitoring is needed as search algorithms are constantly changing.

What happens if when you aren’t on the first page or if you slip from your pedestal? Something will need to change. What kind of changes? If only there was an easy answer to this question, you would be rich.

There are some efforts you might need to undertake, however. For example:

  • Platform change - Using a system that can deliver a semantic web solution is one step towards making a website more understandable. If a search engine can interpret the content of the website (e.g, “price” actually means product price), it’s more likely to index the content of its pages such that they can be delivered to users in search results. How do you think Google creates the images display or the shopping display? With page content it can understand.
  • Design and/or function change - In a 2018 blog post, Google stated, “Our advice for publishers continues to be to focus on delivering the best possible user experience on your websites and not to focus too much on what they think are Google’s current ranking algorithms or signals.”

The changes you need to make will come from an analysis which will include analytics and possibly user feedback. At the end, you should know what is wrong with your current site and how you might make it better.

Technology Triggers

Technology issues can trigger a website migration. With the current rate of change in web-related technology, an older website might already be facing issues that are triggering questions like, “Will our site crash in the near future and leave our customers hanging?”

There are several technology triggers that might send you into migration mode. Here are three examples:

  • Non-secure code - Hackers are always looking to see if they can break into your site. Be it a server hack or a site hack, it can happen. And, if you think only open source products are vulnerable, think about the number of security updates you accept from Microsoft on a regular basis.
  • Too much success - Your CMS was meant for blog posts, not community forums or product sales. You are growing. Your system needs to grow with you.
  • Accessibility problems - Yes. This has been mentioned before but given the increased number of accessibility related lawsuits against website owners, it’s worth repeating. Accessibility is just about page hits, it’s the law.
  • Lack of mobility - “Mobile first” is the phrase of the day and rightly so. Most web users today are using mobile devices to surf the net. Are they surfing you?

The type of changes that might be triggered from the list above can span all three: server change, platform change, and/or design and functionality change.

Mobile First

This drum has already been thumped, but it’s worth mentioning again. We have seen it. “Hey, I was on my phone the other day and saw this cool site. It fit great on my little screen. Can we do that for our site?”

The answer is yes. Given the trend for users to use a mobile device before they reach for their desktop computer, you need join the party. Several technology changes will need to be made to your site.

  • Layout plans - Where do the sidebars go when the page is in a narrow display?
  • Responsive breakpoints - When does the layout of your page change?
  • Menus - That horizontal menu bar will need to change shape in order to be viewable.
  • Media adjustments - Are you still offering up media that doesn’t run on a mobile device? Videos, Flash animations, not all formats work. And, don’t forget images. Those 4MG images aren’t going to fly to a mobile device with ease.

What does this mean for migration? Assuming you have the server environment that can manage the increase in your page hits from going mobile, you might need the following:

  • Platform change - If you aren’t working in a CMS that allows for mobile first design, you will need to change your CMS.
  • Design and/or functionality - As hinted above, page layouts,menus, media will need to be redesigned to accommodate the smaller environments.

Organizational Goals Triggers

The last trigger worth mentioning is the need to meet organizational goals. There is some overlap here with goals pertaining to Analytics and SEO. Other goals might include:

  • Additional services - An organization that talks about books might want to add the option to purchase said books versus providing links to external e-commerce service.
  • Additional resources - Instead of just selling products, the organization wants to provide an education focused community and tutorials.
  • Membership services - Some content might be worth selling right from the browser. The addition of a membership to the website and its valued resources might be the next step to reaching organizational goals.

In each of the examples above, all three types of changes might be required. A new system to provide the new functionality hosted on a server environment that can better handle said changes. Plus, when such changes are required, it’s likely that other design aspects will need to change, hitting all three types of migration.

Paths that might be taken

Once the migration requirement is identified, there are basically two paths to be taken:

  • Do it all now
  • Do it in phases

Do it all now

There are two scenarios that easily lend themselves to this approach.

  • Migration projects such as server changes are at the top of this list. Copy the site to the new environment, test it, fix it if necessary, and go live.
  • If the site will undergo minimal changes, getting it all done now is the likely path.

Of course, any scenario discussed above can follow this path to completion. With the right plans, anything is possible.

Do it in phases

There are several scenarios where this approach might be the best approach. Here are three examples.

  • Technology threats - The current site has been hacked and off line. Instead of spending time trying to fix a potentially outdated website, select the most important features of the site and spin up a new site as quickly as possible. Then, bring the remainder of the features online as they are completed.

  • Legal issues - Lawsuits against non-accessible websites can encourage the need to move quickly. While a new site is being created on a platform that supports accessible websites, two things can occur:

  • Budget - The business is growing, but the budget is still tight. Start with the new look and feel on the new platform and server. Get the basics up and running. Then, bring the new features online as resources permit. Two goals to meet in this scenario”

Creating the Right Team

Last, but certainly not least, is the team of managers, user experience experts, designers, developers, and possibly trainers. Who will you need? Without a plan, without an exercise of “What about …?” and “What if …?” scenarios, you aren’t going to know who you will need.
 

Architecture Workshops

From Stakeholder Mapping to the Delivery of Field-Level Blueprints the Architecture Workshop is designed to take your goals and objectives for your website and provide you solid plan. Whether you develop your website in-house or use an outside firm, this workshop will help you get your stakeholders on the same page, and give your website/project manager a blueprint to ensure you get the most out of your developers.

Private Drupal 8 Immersion Training for your team

  • Get your developers trained on the latest technology by the best Drupal trainers
  • Learn what new innovations you can implement with Drupal 8

 

 

May 31 2018
May 31

Does an accessibility issue on my website mean I need to build a brand new one? This might be one of many questions rolling around in your head as you read the email or letter informing you that your site has an accessibility problem.

 

Don’t panic just yet. It could be something simple, but you need to have all the facts. You need a plan of attack and that starts with a site audit.

Site Audit

Unless that letter is the result of a site audit, you need to set that wheel in motion. Conduct both automated and manual testing to confirm the claim and to determine if there are other problems waiting to be discovered.

Once you have a list of issues you need to address, you can decide if a new website would be easier and more cost effective than trying to fix your current site. Even if the list is long, starting from scratch might not be the answer.

Factors to Consider

Two simple factors in the rebuild decision process:

  • The content management system used to create your site pages
  • Content items in those pages.

After these are considered, site functionality and design can raise its ugly head and influence the direction you need to take. Let’s take a quick look at each factor to get you started.

Content Management System

If the issues reported are being generated by the content management system and are not a reflection of how the site was configured by the developer, ask yourself the following questions to see if there is cure.

  1. Is my CMS proprietary or open source?
  2. If proprietary, did the CMS provider promise accessibility when you purchased the system aso you can get the provider to resolve the problem?
  3. If open source, is there a patch or update you can apply to solve the problem on your own?

 

Simplistic questions? Yes, but they are merely a starting point. If you don’t see a solution after asking these questions, then you will likely need a new site on a different CMS. This doesn’t mean that you can’t transfer your current design to a new system, but it might be time to evaluate your site functionality to see if improvements can be made.

Content

If the issues presented in the letter and/or audit point to types of content that you created and inserted into the CMS, then there’s a chance that you won’t need a rebuild. Again, assuming the site has been configured to accommodate accessibility requirements, then it’s a matter of fixing your content and reposting. For example, if the issues focus on the following, then you can create a plan to fix your issues.

  • Content structure
  • Images
  • Downloadable files
  • Video
  • Audio
  • Uploaded animation

You still might need some developer time if configuration changes need to be made. For example, did someone forget to include the option for the alt attribute to be included with an image? If the changes are extensive, again, it might be time for a new site. Sometimes it’s actually easier to create than it is to edit.

Functionality

Are the issues you are facing tied to site interaction or services, i.e. online forms or interactive maps? Circling back to the CMS, could the issue be that the CMS wasn’t designed to do what you need it to do and will never let you meet accessibility requirements?

At this point, you can decide to either remove the functionality that is causing the problem or you can move to a system that can accommodate your needs.

Design

Just because you can, that doesn’t mean you should. Visual, flashy stuff on the page can be enticing to the user who can actually experience it. Are the issues you are facing linked to the that cool slideshow or mega menu? Depending on your CMS, there might be fixes to your cool features or there might not be.

Like with functionality, ask yourself what is required of your site and then what your CMS can do. You might be applying fixes to your design or you might be moving onto another solution.

In closing …

Facing the need to rectify accessibility issues on your site can feel overwhelming. Even the idea of tweaking all those PDF files to be accessible might want to send you to an early happy hour to drown your frustrations. Don’t worry. You don’t have to face this challenge alone. With training and expert help, you can avoid costly problems in the future.

May 17 2018
May 17

Does your website provide a “place of public accommodation”?

I am online.

Just because your site isn’t made up of brick and mortar, that doesn’t mean you don’t have to comply with the Americans with Disabilities Act Title III, or so said District Judge Scola in 2017 when he concluded that Winn Dixie had violated the ADA by having an inaccessible website.

As the Department of Justice considers updating Title III, the courts are moving ahead with hearing plaintiffs and defendants and handing down rulings. According to Seyfarth Shaw LLP, at least 814 federal website accessibility lawsuits were filed in 2017. New York and Florida lead with 335 and 325 respectively.

I will find the money to fix my site if I get caught.

If you believe that the court costs you might incur if caught are less than the cost of fixing your site right now, think again. The check you write for IT services is only part of the cost you will face if you lose. Imagine the cost of negative publicity?

My website’s target audience can see and hear.

If money and reputation isn’t your motivator, imagine what your life would be like if you couldn’t access content on the web. You can see. You can hear. You have use of your fingers. Imagine one day you don’t. Accidents happen. We all age. Who will you curse for preventing you from accessing content, filling out a form, finding directions? Don’t be that company that prevents others from accessing your goods and services.

I wouldn’t know where to begin.

We know that technology and web accessibility can be overwhelming at best and scary at worst. Consider the following important things you can do now to meet your accessibility goals.

  • Statement of Web Accessibility - A statement from your business regarding accessibility objectives for your site. Keep in mind the effort and resources needed to meet that goal.
  • Hire a Third Party Vendor - Just because your development team says your site is ADA compliant, that doesn’t mean it is. Think of it as hiring an editor because you can’t see your own editorial mistakes.
  • Conduct an Audit - Expert eyes is the key to finding the issues. Both automated and manual testing is required.
  • Remediate Issues - Let your development team fix the issues or hire the experts. You need to demonstrate that you are working to rectify issues in the event that someone comes knocking on your virtual door with a lawsuit.
  • Verify and Document Remediation - Now that your site has been fixed, the ADA related changes need to be verified and documented.
  • Get Trained - Your site keeps changing. Do you know how to ensure your site is compliant moving forward? Training management, content authors, and site developers are the key to ensure your site becomes accessible and stays that way.
  • Maintain - Just because you are trained, that doesn’t mean the occasional content issue won’t arise. Stay on top of your ever-changing site with regular accessibility audits and seek help if you need it.
May 17 2018
May 17

Accessibility badges are gaining attention. These little icons on a web page boast that the page is WCAG 2.0 compliant. As such, the site owner is demonstrating that they recognize the need to provide accessible content.

How does one get a badge to put on their web pages? Assume for a moment that the site owner has actually made an effort and that the badge isn’t a hoax, the process is fairly straightforward. The site owner (or their accessibility consultant) audit the site’s web pages and confirms that WCAG’s criterion has been met.

With sophisticated, automated tools available to anyone with a web browser, web pages can be assessed for accessibility compliance quickly and easily. Or so some believe. Before you start celebrating, let’s briefly explore what it takes to ensure that a single page on your site is WCAG 2.0 compliant and thus badge worthy.

Automated Tool Testing

Automated accessibility testing tools have their place in the auditing process. They are quite valuable from a time-saving and educational perspective. How so?

The automated tools read your code. When they see specific HTML elements, they are programmed to look for code that would suggest that the element has been used in an accessible way. When they see the code is broken, they advise the auditor of the issue and can even suggest a way to remedy the situation. Sounds a little like automated copy editing tools that find typos and grammar issues.

Gotta love that, right? Just like with writers of text, writers of code and online content can’t catch every typo or forgotten attribute. And, if an automated tool can catch the obvious issues, that’s definitely helpful. Let’s look at a few examples that many will have on their pages.

Automated Tool Examples

  • Images - If the tool sees the <IMG> element, it wants to see that the ALT attribute has been included and that there is a description within the alt quotes. Easy check.
  • Segmented Content - If you have segmented content on your page, tools can pick up errors such as using the <h3> element when an <h2> is expected.
  • Audio Files - If the tool detects an audio file on your page, it might warn that the presence of a transcript is needed.

Automated tools can find many issues, but not all.

Manual Testing

Although automated tools catch obvious issues, a full audit requires skilled human intervention. Many of the issues a human will address are warnings expressed by the automated tool. Warnings are provided when the tool can’t be sure if there is an issue or not, and it wants a human to review.

Another aspect of manual testing has nothing to do with said warnings. Automated tools can do only so much and quite often, it’s the automated tools’ “failure” that gets a site owner into trouble.

Manual Testing Examples

Using the three examples above, let’s see how a human is needed to ensure accessibility on a page is being met.

  • Images - What the tool can’t do is determine if the description included in the alt attribute is valid. An image of a mountain range might have an alternative description of, “A beautiful day exploring nature.” This description is about the photographer’s experience, not the image itself.
  • Segmented Content - The tool can’t confirm that the <h3> is a typo or if the <h2> is simply missing. For instance, was there a copy/paste issue while transferring the blog from MS Word? By actually reading the content, a human can determine the real issue and correct it.
  • Audio File - Maybe you have a transcript attached to the page as a PDF. What the automated tool can’t tell you is if the PDF is accessible. It might be able to determine that a screen reader can navigate to the PDF and verify its link, but that doesn’t mean the content in the downloadable file can be read.

Earn Bragging Rights

Conduct a complete audit. Don’t assume that just because you created the right code that your page or its content is accessible. The three examples above only scratch the surface of what an automated tool can and cannot do. Take the time to learn what it means to be accessible, how to ensure accessibility on your site, and how to maintain said accessibility.

Beware of Snake Oil

There are a lot of companies out there that sell products that claim they do accessibility. They may sell a bolt-on widget that doesn’t really work, tell you that automated testing will suffice, and even manually test your site without giving solid advice for how to truly be compliant.

 

The Accessibility Team at Promet Source will get you everything you need to be compliant. Our audit will tell you what needs remediation, and the report we produce will even tell you exactly what you need to do to fix it.

Mar 27 2018
Mar 27

We're packing our bags and heading south! Will you be at DrupalCon Nashville? Don't miss Promet's lineup of sessions, training or stop by and see us in the exhibit hall at booth #710.

This year, Promet Source is supporting DrupalCon as a silver sponsor and host of the annual First Time Attendees social. We're also proud to announce our following schedule of events, including hosting the annual First Time Attendees Social, providing professional training and sessions throughout the week.

Monday, April 9th

Training: Drupal 8 Crash Course for Content Managers, Marketers & Project Managers

Are you responsible for project management, content, or vendor selection and preparing to work with Drupal? This one-day training delivers all of the tools you need to get started. Delivered by an Acquia Certified Drupal Developer, this training will answer the questions you didn’t even know to ask. Targeted to the non-developer, this training is perfect for individuals that need to get up and running in Drupal - fast!

- Time: 9:00am-5:00pm

- Location: Music City Center

Training: Advanced Web Accessibility Training for Drupal Developers

This training is designed to help developers shift their thinking to build accessibility compliant digital content.  During this full day training developers will gain hands on experience in using automated evaluation tools, learning how to incorporate Drupal core and contributed modules that assist with accessibility into their sites, identifying accessibility issues at the code level, and finally developing their sites with accessibility always in-mind.

- Time: 9:00am-5:00pm

- Location: Music City Center

Sign Up Today! If you haven't already, be sure to sign up and snag one of the few remaining spots for training

First Time Attendee Social hosted by Promet Source

To help ease newcomers into DrupalCon, we've put together an orientation designed to explain all DrupalCon's many moving parts and introduce you to a new friend or two. We think starting out the week with a buddy makes networking and navigating an unfamiliar event so much easier!

- Time: 3:30pm-5:00pm

- Location: Level 3 Foyer of Music City Center

Tuesday, April 10th

FREE Workshop: What am I getting myself into? A Drupal Crash Course for Content Managers

Are you responsible for project management, content, or vendor selection and preparing to work with Drupal? This session delivers all of the tools you need to get started. Delivered by an Acquia Certified Drupal Developer, this session will answer the questions you didn’t even know to ask! Learn more.

Time: 10:45am-12:00pm

Location: Room 103B - Music City Center

Wednesday, April 11th

Session: D8 Commerce meets Artistic Expression - Online Shopping with Corning Museum of Glass

Join the CMoG development team and Promet Source as we discuss the journey to roll out a newly redesigned e-commerce site for the Museum powered by Drupal 8 and Commerce 2.0 that showcases the works of art available for purchase online as well as signups for classes and events hosted by the Museum.  We’ll talk about its integration with the Museum’s internal ERP systems as well as some of the technical challenges encountered along the way. Learn more.

Time: 2:15pm-3:15pm

Location: Ambitious Digital Experience Stage - Music City Center Exhibit Hall

Session: More Social, Less Media - Harnessing Human Connection to Achieve Marketing Success

In this session, we'll talk about how to cut through the noise that can often be caused by trying to keep up with industry trends, and how to get to the heart of what your organization - large or small - really has to offer to the world. The unique, collective experience of the people around you (or just yourself!) is hands down the most marketable asset that will give your business the edge it's been looking for. Learn more.

Time: 2:50-3:15

Location: 205AB - Music City Center

What is DrupalCon? 

The Drupal community is one of the largest open source communities in the world. We're developers, designers, strategists, coordinators, editors, translators, and more. Each year, we meet at Drupal camps, meet ups, and other events in more than 200 countries. But once a year, our community comes together at the biggest Drupal event in the world: DrupalCon North America. This year, from April 9-13, we'll be in Nashville, TN. 

Whether you’re an existing Drupal user, developer, designer, site builder, or are maybe just a little Drupal-curious, you won’t want to miss out on this unique event.

Let's meet up! 

The Promet Source team will be flying our flag at DrupalCon again this year and would love to meet up with you! Get in touch to set up a time to chat or simply drop by and see us at booth #710. We look forward to seeing you in Nashville and supporting the Drupal community together!

Pages

About Drupal Sun

Drupal Sun is an Evolving Web project. It allows you to:

  • Do full-text search on all the articles in Drupal Planet (thanks to Apache Solr)
  • Facet based on tags, author, or feed
  • Flip through articles quickly (with j/k or arrow keys) to find what you're interested in
  • View the entire article text inline, or in the context of the site where it was created

See the blog post at Evolving Web

Evolving Web