Respect those who seek the truth, be wary of those who claim to have found it.
We at Zivtech care about accessible websites and strive to make our projects usable by the widest range of people possible. We aim to produce websites that adhere to Section 508 standards and WAI-ARIA guidelines.
Sometimes a client has specific needs for compliance, like a government or university website. In general though, accessibility should be a goal for any website, so that users of any ability can meaningfully interact with the Internet.
With that in mind, you may find yourself focussing on ensuring old browser support, like IE (Internet Explorer) 10 or earlier. You want the widest audience using your website. Yet worldwide browser statistics show IE 8 at around 3-4% usage over the last year. Since IE 9 and 10 auto update to IE 11, their usage is nearly non-existent at this point. (note: Some clients need old browser compliance, but that is less often the case.) At the same time, it's possible that more of your website visitors have low vision. Thus it's arguable you'll get a higher return on your development dollars if you prioritize accessibility rather than IE 8 support.
To provide accessible websites, Zivtech produces a contributed starter theme for Drupal called Bear Skin. It was recently updated to include more accessible markup, and is free for use.Accessibility in the Bear Skin theme
We made our Drupal theme more accessible by focussing on three major sets of updates: semantic markup, 508 compliance, and ARIA. The first two sets, markup and 508 compliance, are really the "low hanging fruits." They provide great enhancements, but require the least effort. Letting Drupal render accessible markup with ARIA is more time intensive, but ultimately provides the best experience for screen readers.Semantic Markup
Semantic markup comprises the intent and purposes of HTML5 standards. These standards introduced several new HTML elements and deprecated some others. Ensuring your theme markup uses semantic HTML is the easiest way to provide a minimal amount of accessibility for people with screen readers or other assistive technology.
My favorite resource for keeping up with HTML5 standards is the HTML5 Doctor website. They provide contextual documentation for standards, including sample markup. It's easy to compare your Drupal theme markup with compliant HTML5 markup, and suss out where you need improvements.
While it may seem like a big task, we found it pretty straightforward to update Bear Skin's markup. For example, the main content area of the page uses the main HTML element. Also, the previous Bear Skin revision used the hgroup element to group titles and subtitles on pages. Yet that element has been removed from the HTML5 spec, and was plucked out of Bear Skin as well.508 Compliance
Many of the requirements for 508 compliance are thought of as best practices for HTML, so it's likely your Drupal theme is nearly compliant already! For example, Section 508 stipulates that images need meaningful alt tags and each form element needs a meaningful label. These two examples are things you hopefully have in your theme already.
While updating Bear Skin, we also went over this 508 compliance checklist provided by WebAIM. Some additional features added to make Drupal 508 compliant were skip links to direct a user straight to the main page content, and ensuring the page is still usable without CSS.WAI-ARIA Integration
The Web Accessibility Initiative section of W3C created ARIA standards as a way to provide screen readers the ability to meaningfully interact with a web page. ARIA standards are very in depth and wide-reaching, and can be somewhat confusing at first glance.
If you're going to review your own Drupal theme for ARIA compatibility, take a look at this spec produced by the W3C, Using WAI-ARIA in HTML. It includes all the basics of ARIA, as well as a short table of commonly used elements.
Landmark roles and aria-* properties are sprinkled throughout Bear Skin, and can provide your own website with a great base-level of support for screen readers.Testing Tools
Before beginning your adventure in making your website more accessible, or after you've made updates for 508 & ARIA compliance, there are some tools available to help validate your work.
While it's not yet perfect, the regular XHTML validator is good about spotting errors in ARIA. Since a lot of Section 508 is also considered best practice for HTML, the validator is even better about spotting a lot of 508 compliance pitfalls.
WebAIM produces a tool for accessibility checking called WAVE. It can review your site for many things, like 508 compliance and ARIA. It also checks more general things like ensuring high enough contrast between text color and its background color.
If your website is in development or behind a firewall, you might not be able to provide a public link for the WAVE website. If that's the case, you can use a toolbar for Firefox or a plugin for Chrome.Accessible Development and Design at Zivtech
Zivtech is experienced with adhering to government standards for accessibility, and it's important to us that people of all abilities can use your website. If you need help making your current website more accessible, or if you want to start a fresh site with a focus on accessibility, contact us for help.Terms: DrupalDrupal PlanetaccessibilitySection 508 Compliancethemingbear skin
Frequently asked questions, or FAQ for short, are fairly common on websites these days. A good FAQ page can help in reducing the number of support requests for basic questions. Whenever I need help on a website, the first thing I look for is the FAQ page before I contact them.
In Drupal, a FAQ page can be created in a few ways. First, you could write the HTML and anchor tags by hand or you could use a module like FAQ Field.
The FAQ Field module comes with a custom field called "FAQ Field" which you can add to any type of entity. It also has a few handy formatters to display the FAQ.
I should also mention that you can use the FAQ module to create these pages. The biggest difference is that the FAQ module has its own content type, whereas, the FAQ Field is based around a field. This is useful for creating FAQs on a Product content type.
In this tutorial, you'll learn how to setup and use the FAQ Field module. We'll add the field to the "Basic page" content type that comes with the standard installation of Drupal.
To be able to render cache all things that can possibly be render cached, Drupal 8 code must:
- set the right cache max-age — to ensure only the cacheable parts of the page are cached
- set the right cache contexts — to ensure content is varied as expected (per language, per role, per timezone, per user …)
- set the right cache tags — to ensure rendered content is invalidated when the data it depends on is modified
Before Drupal 8, approximately zero attention was given to cacheability of the rendered content: everything seen on a Drupal 7 page is rendered dynamically, with only the occasional exception.
By flipping that around, we make developers more conscious about the output they’re generating, and how much time it takes to generate that output. This in turn allows Drupal 8 to automatically apply powerful performance optimizations, such as:
- enabling Drupal’s internal page cache (for anonymous users) by default: d.o/node/606840, which requires cache tags to be correct
- smartly caching partial pages for all users (including authenticated users): d.o/node/2429617, which requires cache contexts to be correct
- sending the dynamic, uncacheable parts of the page via a BigPipe-like mechanism: d.o/node/2429287
(The first of those three will likely happen this week. We’re working hard to make the last two a reality.)Visualization
Caching means better performance, but it also means that without the correct cacheability metadata, the wrong content may be served to end users: without the right cache contexts, the wrong variation may be sent to a user; without the right cache tags, stale content may be sent to a user. Therefore we should make it as easy as possible to analyze the cacheability of a rendered block, entity (node/user/taxonomy term/…), view, region, menu, and so on.
It should work not only for cacheability metadata, but for all bubbleable metadata3: it’d be very valuable to be able to see which part of the page caused an expensive cache context or tag 4, but it’d be at least equally valuable to see which part of the page attached a certain asset5.
Since bubbling happens across a tree, it’s important to visualize the hierarchy. The best hierarchy visualization I know in the web developer world is the Firefox Developer Tools 3D view.
I think a tool for visualizing, analyzing and understanding the bubbleable metadata (cache contexts, cache tags, cache max-age, assets) should work in a similar way. The developer should be able to:
- look at the document in 3D in different layers and/or queries (assets, cacheability as a whole, but also only cache contexts, only cache tags, or only max-age)
- zoom in a specific element, and look at all of its bubbleable metadata
- reposition the 3D view, to look from different angles — humans are very proficient at processing visual data
So, over the past weekend, I worked on a prototype. I read the CSS Transforms spec6 and read a CSS 3D transforms introduction. As somebody with little CSS knowledge and not having touched CSS nor 3D programming in years, it was fun to play with this ) The result:
And finally, a short screencast demonstrating it in action:
Give it a try yourself by applying the attached patch to Drupal 8 at commit daf9e2c509149441d4d9a4d1964895179a84a12c and installing the renderviz module.Want to help?
But it’s a lot of fun to work on, and it’s very different from what most of us tend to work on every day. If you’d like to be able to build sites in Drupal 8 with a developer tool like this, please contact me, or leave a comment :)
A cache tag is expensive if it’s invalidated relatively frequently (which causes all render cache items that have that tag to be invalidated). A cache context is expensive if it causes many variations (for example: per-user caching requires a variation of the render array to be created for every single authenticated user). ↩