Problem/Motivation

Proposed resolution

Remaining tasks

Comments

cilefen created an issue. See original summary.

cilefen’s picture

cilefen commented
Issue tags: +Accessibility, +508 Compliance
mgifford’s picture

mgifford
he/him
Primary language English
commented

What scanning tool did you use for this?

andrewmacpherson’s picture

andrewmacpherson commented

@mgifford I don't think an automated scanning tool was used for these. None of the referenced child issues mention an automated scanning tool. The title came from @cilefen who started them in this [meta] issue.

andrewmacpherson’s picture

andrewmacpherson commented
Title: [meta] Fix 508 compliance issues from automated scans » [meta] Fix 508 compliance issues
mgifford’s picture

mgifford
he/him
Primary language English
commented

@andrewmacpherson - True.. Not sure why I thought that this was based on an automated test...

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

mgifford’s picture

mgifford
he/him
Primary language English
commented

Aren't all WCAG 2.0 AA issues essentially now Section 508 issues? I'm not sure what the value is in tracking country specific legislation, particularly if it is mirroring the global standard.

Adding links:
https://www.section508.gov/content/build/website-accessibility-improveme...
https://github.com/mgifford/section508-to-wcag2aa

andrewmacpherson’s picture

andrewmacpherson commented
Status: Active » Closed (outdated)

Yes, from what I gather the 508 refresh means WCAG 2.0. In any case, it looks like most of these issues are based on the old version of section 508.

I agree, tracking country-specific regulations is too much admin/legalese overhead, and I don't think any particular country deserves special attention. I expect we'll continue to hear "508" in issues from USA-based community members, that's just the phrase people are used to. We can continue to point out that Drupal's accessibility gate talks about W3C guidelines. (Of course, country-specific guidelines can still be cited as supporting information, but we only commit to W3C stuff officially.)

@cilefen opened this meta issue when we had a raft of new issues with 508 in the title, submitted by @cortezj and @kershme, who were brand new community members. I don't think we need to keep this open any longer, the list of child issues will still be here after we close it.

Let's mark it Closed (outdated) - because 508 has aligned with WCAG.