{"id":128,"date":"2017-08-02T10:18:42","date_gmt":"2017-08-02T10:18:42","guid":{"rendered":"https:\/\/blog.phplist.com\/?p=128"},"modified":"2017-08-02T10:21:16","modified_gmt":"2017-08-02T10:21:16","slug":"accessible-phplist-section-508-and-255-government-standards","status":"publish","type":"post","link":"https:\/\/www.phplist.com\/blog\/accessible-phplist-section-508-and-255-government-standards\/","title":{"rendered":"Accessible phpList: Section 508 and 255 Government standards"},"content":{"rendered":"

In the USA, technology procured by federal organisations is required to meet the guidelines in Section 508<\/a> of the Rehabilitation Act and Section 255<\/a> of the Communications Act. These guidelines are designed to ensure that citizens and federal employees who have physical, sensory, or cognitive disabilities can access information comparably to those who do not have disabilities.<\/p>\n

Email newsletters and announcements, sent using software like phpList, are a popular method for federal agencies to communicate directly with citizens. It is important that these emails meet accessibility guidelines. This guide demonstrates how to provide a newsletter or email marketing service to mailing list subscribers in compliance with Section 508 guidelines.<\/p>\n

Subscribers interact with phpList in two ways: by receiving and engaging with email campaign messages, and by managing their mailing list subscription and preferences via phpList web pages. The following sections address each of these in turn.<\/p>\n

Introduction<\/h2>\n

Four\u00a0critical aspects of section 508 are \u00a71194.22 (a) (c), (d), (k) and (n). These provisions require that:<\/p>\n

    \n
  1. A text equivalent for every non-text element shall be provided.<\/li>\n
  2. Any colour based prompts are also provided as black and white indicators.<\/li>\n
  3. Documents shall be organised so they are readable without requiring an associated style sheet.<\/li>\n
  4. A plain text version of your information be available, in this case, your email.<\/li>\n
  5. Input boxes are identifiable with screen readers, for example by being placed in a table.<\/li>\n<\/ol>\n

    Accessibility built in<\/h2>\n

    Indicating mandatory field with an asterisk<\/h3>\n

    phpList indicates mandatory form fields using red text and asterisks. This means that a subscriber with visual impairments can determine which fields on the subscribe page are mandatory without reliance on colour.<\/p>\n

    \"black-and-white-indicators\"<\/a><\/p>\n

    Using a subscribe page with the style sheet disabled<\/h3>\n

    Additionally, phpList subscribe pages work when both style sheets (CSS) and javascript are turned off. While this page may look a little spartan, this can be much easier to use for those with visual impairments. It\u00a0can also be navigated with keystrokes\u00a0only, and so does not require the use of a mouse.<\/p>\n

    \"plain-text\"<\/a><\/p>\n

    Labels and input boxes organised in tables<\/h3>\n

    The subscribe from is inside a table, which means that it is clearer to a screen-reader, which are\u00a0used by blind or visually impaired subscribers, which title belongs which which input box.<\/p>\n

    \"table\"<\/a><\/p>\n

    Important settings<\/h2>\n

    When setting up your subscribe form you can use the option to offer a checkbox or radio button for a text only version of your campaign. This text only version will then be automatically generated and sent to those who have requested it.<\/p>\n

    \"check-box-text\"<\/a><\/p>\n

    Sending a plain text version of your campaigns<\/h3>\n

    In phpList you automatically generate and edit\u00a0a plain text version of each campaign. Most of your subscribers will want the HTML version, this contains images, headings, fonts and colours, which you can design in the campaign editor.<\/p>\n

    \"html-version\"<\/a><\/p>\n

    On the second tab in the campaign creator you can generate and edit the plain text version.<\/p>\n

    \"plain-text-version\"<\/a><\/p>\n

    If a subscriber has indicated that they wish to receive plain text messages by using the checkbox\u00a0on the Subscribe page, they will receive a message without HTML. In this example it would look like this:<\/p>\n

    \"plain-text-email-2\"<\/a><\/p>\n

    All other subscribers would get the HTML version. In this example it would look like this:<\/p>\n

    \"html-email\"<\/a><\/p>\n

    Adding an descriptive text to images<\/h3>\n

    When composing a campaign in phpList it’s easy to meet the requirement for including descriptive “alternative” text for images. Doing so represents images textually for people who cannot see them. When you insert an image into campaign content simply include the description in the “Alternative Text”. This will insert an HTML ‘alt=’ attribute into the code of the message.<\/p>\n

    \"alt-txt-1\"<\/a><\/p>\n

    Image descriptions will then be displayed by screenreader and accessibility software, and will also be displayed if images are blocked by the subscriber’s mail client.<\/p>\n

    \"alt-txt-2\"<\/a><\/p>\n

    Summary<\/h2>\n

    By using a combination of phpList’s built-in accessibility features, and careful content crafting, you can reach a broader range or subscribers in ways they can enjoy. A broad range of public institutions in the USA rely on phpList to meet federal accessibility standards — you can too. Whether your organisation seeks to be accessible by choice or by obligation, it’s easy with phpList!<\/p>\n","protected":false},"excerpt":{"rendered":"

    In the USA, technology procured by federal organisations is required to meet the guidelines in Section 508 of the Rehabilitation Act and Section 255 of the Communications Act. These guidelines are designed to ensure that citizens and federal employees who have physical, sensory, or cognitive disabilities can access information comparably to those who do not […]<\/p>\n","protected":false},"author":4,"featured_media":139,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1,4,2],"tags":[31,72,33,32],"class_list":["post-128","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","category-phplist-com-user-news","category-self-hosted-user-news","tag-accessibility","tag-plain-text","tag-section-255","tag-section-508"],"_links":{"self":[{"href":"https:\/\/www.phplist.com\/blog\/wp-json\/wp\/v2\/posts\/128","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.phplist.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.phplist.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.phplist.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.phplist.com\/blog\/wp-json\/wp\/v2\/comments?post=128"}],"version-history":[{"count":17,"href":"https:\/\/www.phplist.com\/blog\/wp-json\/wp\/v2\/posts\/128\/revisions"}],"predecessor-version":[{"id":372,"href":"https:\/\/www.phplist.com\/blog\/wp-json\/wp\/v2\/posts\/128\/revisions\/372"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.phplist.com\/blog\/wp-json\/wp\/v2\/media\/139"}],"wp:attachment":[{"href":"https:\/\/www.phplist.com\/blog\/wp-json\/wp\/v2\/media?parent=128"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.phplist.com\/blog\/wp-json\/wp\/v2\/categories?post=128"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.phplist.com\/blog\/wp-json\/wp\/v2\/tags?post=128"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}