{"id":907,"date":"2016-09-14T22:48:56","date_gmt":"2016-09-15T05:48:56","guid":{"rendered":"http:\/\/blogs.lanecc.edu\/webteam\/?p=907"},"modified":"2016-09-14T22:48:56","modified_gmt":"2016-09-15T05:48:56","slug":"click-to-expand","status":"publish","type":"post","link":"https:\/\/blogs.lanecc.edu\/webteam\/2016\/09\/14\/click-to-expand\/","title":{"rendered":"Click to Expand"},"content":{"rendered":"

A few days ago, an astute employee over in Enrollment Services pointed out that our steps to enroll pages<\/a> weren’t completely accessible to the blind. This is an important problem, and a surprisingly tricky one.<\/p>\n

The current legal requirements for web accessibility (including \u00a71194.22, which we’re most interested in) are referred to as Section 508<\/a>. These standards provide some useful guidance on how to help folks with an impairment of some kind. For instance, they describe how images should have an alt text field, except for when that image doesn’t support understanding of the content (e.g. a background or filler image).<\/p>\n

On the other hand, these standards are now old enough to vote, meaning they’re older than Facebook, Twitter, selfie sticks, Google Chrome, iPhones, the Columbus Blue Jackets, and Windows XP. Needless to say, they’re showing their age.<\/p>\n

There’s no way to make click to expand text accessible under current 508 guidelines. Our best option would be to duplicate the page and provide a text only version. Unfortunately, that could lead to a screenreader having to read a lot of unnecessary text.<\/p>\n

The solution relies in the proposed new standards<\/a>. These are still in progress, but the web community is confident they’re going to heavily include something called WAI-ARIA<\/a>. WAI-ARIA provides a way to mark up your pages with extra attributes that screen readers know how to recognize, so the blind can better use interactive pages.<\/p>\n

Returning to our original problem, starting this evening we’re now using the hide-show accessible plugin<\/a> on those pages. This plugin lets you write some fairly simple markup in your page which will then get converted to a click to expand box like on the steps to enroll.<\/p>\n

To use, you’ll first want to click the blue link below the edit box in Drupal that says “disable rich text”. Then, if you want a simple button with some text below it, you’ll want to paste this in:<\/code><\/p>\n

 <p class=\"js-expandmore\">Click on me<\/p>\r\n <div class=\"js-to_expand\">\r\n     here is the hidden content!\r\n <\/div><\/code><\/pre>\n
Then replace “Click on me” and “to show me!” with whatever works for your page. You’ll get something like this:<\/p>\n
\"plus<\/a><\/p>\n
And when you click to expand, you’ll see this:<\/p>\n
\"minus<\/a><\/p>\n
If you’d like a little bit of color, you can also use an h3<\/code> element, which would place that text in an orange box:<\/p>\n
\u00a0\u00a0\u00a0 <h2 class=\"js-expandmore\">Lorem dolor si amet<\/h2>\r\n\u00a0\u00a0\u00a0 <div class=\"js-to_expand\">\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 here is the hidden content\r\n\u00a0\u00a0\u00a0 <\/div><\/pre>\n
Exactly the same as before, but now it’ll look like this:<\/p>\n
\"same<\/a><\/p>\n
This is actually the more correct use – you nearly always want to use an h<\/code> element of some kind when it describes the text after it.<\/p>\n
For really advanced use, you can also add a full class to make the button full width. Or you can add the blue class to make the orange background blue instead. Or both!<\/p>\n
\u00a0\u00a0\u00a0 <h3 class=\"js-expandmore blue full\">Lorem dolor si amet<\/h2>\r\n\u00a0\u00a0\u00a0 <div class=\"js-to_expand\">\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 here is the hidden content\r\n\u00a0\u00a0\u00a0 <\/div><\/pre>\n
would look like this:<\/p>\n
\"blue<\/a><\/p>\n
This is definitely getting into advanced content editing in Drupal, so if you’re stuck don’t hesitate to contact us at webmaster@lanecc.edu.<\/p>\n
Remember, we should always try to use the right tool. For instance, these kinds of show and hide buttons might seem like they’d be perfect for an FAQ. But we already have a different setup for FAQ questions, that takes care of alphabetizing and tracking changes to each question. And remember that many of the visitors to your page won’t bother clicking the button at all. Always spend time simplifying your content to make sure the important message is apparent even without clicking to show your other text.<\/p>\n","protected":false},"excerpt":{"rendered":"
A few days ago, an astute employee over in Enrollment Services pointed out that our steps to enroll pages weren’t completely accessible to the blind. This is an important problem, and a surprisingly tricky one. The current legal requirements for web accessibility (including \u00a71194.22, which we’re most interested in) are referred to as Section 508. … Continue reading “Click to Expand”<\/span><\/a><\/p>\n","protected":false},"author":86,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"footnotes":"","_wpscppro_dont_share_socialmedia":false,"_wpscppro_custom_social_share_image":0,"_facebook_share_type":"","_twitter_share_type":"","_linkedin_share_type":"","_pinterest_share_type":"","_linkedin_share_type_page":"","_instagram_share_type":"","_medium_share_type":"","_threads_share_type":"","_google_business_share_type":"","_selected_social_profile":[],"_wpsp_enable_custom_social_template":false,"_wpsp_social_scheduling":{"enabled":false,"datetime":null,"platforms":[],"status":"template_only","dateOption":"today","timeOption":"now","customDays":"","customHours":"","customDate":"","customTime":"","schedulingType":"absolute"},"_wpsp_active_default_template":true},"categories":[3],"tags":[6,25],"class_list":["post-907","post","type-post","status-publish","format-standard","hentry","category-drupal","tag-accessibility","tag-drupal"],"_links":{"self":[{"href":"https:\/\/blogs.lanecc.edu\/webteam\/wp-json\/wp\/v2\/posts\/907","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.lanecc.edu\/webteam\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.lanecc.edu\/webteam\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.lanecc.edu\/webteam\/wp-json\/wp\/v2\/users\/86"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.lanecc.edu\/webteam\/wp-json\/wp\/v2\/comments?post=907"}],"version-history":[{"count":2,"href":"https:\/\/blogs.lanecc.edu\/webteam\/wp-json\/wp\/v2\/posts\/907\/revisions"}],"predecessor-version":[{"id":913,"href":"https:\/\/blogs.lanecc.edu\/webteam\/wp-json\/wp\/v2\/posts\/907\/revisions\/913"}],"wp:attachment":[{"href":"https:\/\/blogs.lanecc.edu\/webteam\/wp-json\/wp\/v2\/media?parent=907"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.lanecc.edu\/webteam\/wp-json\/wp\/v2\/categories?post=907"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.lanecc.edu\/webteam\/wp-json\/wp\/v2\/tags?post=907"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}