Snippets

A repository of styled and “styled” form control patterns, and how they are announced by screen readers.

Why?

Form controls are necessary in many interfaces, but are often considered annoying, if not downright difficult, to style. Many of the markup patterns presented here can serve as a baseline for building more attractive form controls without having to exclude users who may rely on assistive technology to get things done.

A11Y Nutrition Cards is an attempt to digest and simplify the accessibility expectations when it comes to component authoring. Based on the WAI ARIA Authoring Practices Guide.

Accessibility can be a complex and difficult topic. The Accessibility Project understands this and wants to help make it easier to implement on the web. Our goal is to accomplish this with three principles in mind:

1. Digestible. We strive to feature short, digestible pieces of content.
2. Up-to-date. The project is hosted on GitHub so information can be current with the latest standards.
3. Forgiving. People make mistakes, so we seek to be encouraging.

This seems like a really valuable resource on what ARIA attributes are required and optional in working with various role attributes.

Hello, and thank you for downloading this font.

This font is free for PERSONAL USE ONLY!

But if you want to get a commercial license, it’s available at: http://www.stereo-type.fr
The commercial version contains a huge set of alternate glyphes and a wide range ligatures and swashes to create your own style ! You’ll be also able to edit PDF files with the font embedded.

This font is inspired by the work of Sean Delloro and with his authorization.
You can have a look at his Instagram page : https://www.instagram.com/seandllr/

I made it with love, so I hope you’ll love to use it !

Clement | StereoType

This is pretty neat: you can use pointer-events: visiblePainted; to make only the filled (painted) part of an SVG respond to the pointer.

A standalone version of the readability library used for Firefox Reader View.

[…]

To parse a document, you must create a new Readability object from a document object, and then call parse(). Here’s an example:

var article = new Readability(document).parse();

This article object will contain the following properties:

• title: article title
• content: HTML string of processed article content
• length: length of an article, in characters
• excerpt: article description, or short excerpt from the content
• byline: author metadata
• dir: content direction

If you’re using Readability on the web, you will likely be able to use a document reference from elsewhere (e.g. fetched via XMLHttpRequest, in a same-origin <iframe> you have access to, etc.).

I just found out that NASA.gov is apparently built on Drupal 7. That’s pretty awesome.