1.4.13 Printing

WCAG 2.1 Review: Introduction 

WCAG 2.1 now has a first public working draft and ​the working group are inviting comments and feedback via Github

As I'm developing software to test sites for accessibility, I'm reviewing the 28 new proposed criteria for WCAG 2.1, primarily to determine how testable the criteria are using either automated or manual methods. ​

This post concerns a specific criterion: ​1.4.13 Printing. 
To view my feedback on other criteria and more background info, go to my listing of feedback

The Criterion

  • 1.4.13 Printing
  • Suggested Priority Level: AA
  • Text: If content can be printed, the following are true:
    Resized: Content can be resized up to 200% without loss of content or functionality;
    Changes Reflected: User changes to letter spacing, line spacing, font family, and color are reflected in the printed content.

My Thoughts

This is one of those criteria that is a little unclear on whether the onus is on the developer or the user agent that is being used to serve up the printable version. 

From reading the documentation, I believe it is more that the developer shouldn't put anything in a print stylesheet that would prevent things from resizing or having different letter spacing etc. I'd suggest it should be renamed to "Support Printing" to make this distinction clearer.  

It feels to me like the main thing that the criterion is trying to do is prevent the cases where the developer has explicitly overridden styles in the print stylesheet that would prevent zoom and things like font changes. As suggested already on Github, this should be worded in such a way that the developer doesn't have to keep tweaking print stylesheets to cope with the shortcomings of user agents. 

Other than that, I'm pretty happy with this as a criterion, it just needs the wording firming up.

Click here to add a comment

Leave a comment: