I was asked by @tim.plunkett on Slack to look at an issue for #2905922: Implementation issue for Layout Builder

I did a quick review and ran into some issues that Tim said were related to the Off-Canvas dialog in the Settings Tray module.

I just noticed that it is still marked "Needs accessibility review" but seems to be marked stable. As I mentioned to Tim, I'm not sure who is regularly checking "Needs accessibility review" at this point. We're a pretty small team and it is difficult enough to keep up with "accessibility".

What Tim did is correct. If you need us to do a review, please reach out to the Accessibility Slack Channel. Before something gets marked stable, please let's make sure it has had some review and that we remove the "Needs accessibility review" tag.

Anyways, I think these 3 issues (still with the numbering from my comment #2905922-73: Implementation issue for Layout Builder:

1) the "Choose a layout" panel that popus up after clicking on "Add Section" has no focus or hover states. It is very difficult to find out where you are and how to close the window. Some simple CSS should fix this.

4) When adding a block to a layout there is the same problem with lack of focus/hover that is mentioned in #1. It actually might be there but it is very faint and there is a bit of a delay so hard to notice.

5) As Tim pointed out in slack, there are some color contrast issues. #46a0f5 on #222222 doesn't pass.

Please let me know if there are any questions.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mgifford created an issue. See original summary.

andrewmacpherson’s picture

I don't know if (1) and (4) are going to affect all possible content in the settings tray. Ideally I think we'd get a standard set of styles for the settings tray.

(5) I can't find #222222 anywhere. Which element is this about? #46a0f5-on-#222 has a fairly good contrast ratio of 5.8:1 (passes WCAG AA), but I don't know which element we're talking about.

andrewmacpherson’s picture

The close button "X" has an inconsistent focus style.

In Webkit/Blink it has a solid blue border, with rounded corners. I can't see any CSS for it, so I assume it's the default browser style. It's a nice style, but we need to ensure the blue colour has sufficient contrast against #2d2d2d settings tray title background (.ui-dialog.ui-dialog-off-canvas .ui-dialog-titlebar).
In Firefox, the close button has no discernible focus style. It's baffling, because I can't see any CSS which would override the default 1px dotted outline.
TODO: what does it look like in IE11 and Edge?

andrewmacpherson’s picture

The button and link styles inside of the settings tray content are communicated by a slight colour change alone. If you avert your eyes from the screen, then look back again, it's not clear what has focus. This will likely be a failure of WCAG 2.1 SC 1.4.12 User Interface Component Contrast (Minimum).

Our blue-oval primary buttons in Seven get a halo when focused, which is clearer because it's a shape change. (The outlines which browsers provide by default also work this way.)

We need to review focus styles across the entire admin UI as part of #2864791: Implement new Success Criteria from WCAG 2.1. Tagging,

andrewmacpherson’s picture

mgifford’s picture

Just adding a screenshot for #5.

Screenshot with color contrast

Good point about the close button "X", we are talking about this one, right? I couldn't see a focus in Firefox for any of the elements here. I've got pretty good eyes, but without knowing where I am, it very hard to know where I am. I think that there's a delay which is screwing it up for me:

Top of Off Canvas Dialog

I think you wanted to tag wcag21 in #4 above.

tedbow’s picture

I created #2915759: :focus is is hard to see for links in the off-canvas dialog before not sure if we want to mark as a duplicate or keep it open.

xjm’s picture

Thanks @andrewmacpherson and @mgifford. The offcanvas library is marked stable because it doesn't expose anything to end users by itself, but Settings Tray will be the first module that exposes it to end users, so any serious accessibility issues need to be addressed before Settings Tray itself can be stable.

  • From this list, I'd say the contrast ratio issue is the most serious if it's still present. It hurts my eyes, actually. I think it still needs an issue filed?
  • I think the inconsistent styling for the focus highlighting for the [x] button is a bug, but core dialogs have a similar (worse?) issue in as reported in #2863354: Add border to dialog [x] close button for hover and focus states so that one doesn't need to be a stable blocker.
  • I'm unsure about #2915759: :focus is is hard to see for links in the off-canvas dialog, but it definitely is a bug, and we probably need to take into account colors for it when fixing the contrast ratio anyway. The difficulty caused by that issue is probably compounded by the other tabbing issues (since it's difficult to predict where the focus will go and worse if you can't easily see where it's gone). As far as I understand from @tedbow the remaining tabbing issues are related to the Contextual module, but the fact that they're outstanding probably means the insufficient focus styling becomes serious enough to block stable.

Since we sort of have two metas, this and #2928409: [META] Accessibility issues for Settings Tray , my suggestion would be to mark this as a duplicate once a dedicated issue is filed for the contrast ratio.

Thanks everyone!

samuel.mortenson’s picture

Created #2934178: Contrast issues with off-canvas dialog styling to address the contrast ratio issues.

xjm’s picture

Status: Active » Closed (duplicate)

Alright, I updated #2928409: [META] Accessibility issues for Settings Tray and I think that's enough to mark this as a duplicate. Thanks everyone!

xjm’s picture

Status: Closed (duplicate) » Active

Ah wait, I think we need to file one more issue for the close button to match the new designs for the dialog system. Once it's filed (doesn't need to be fixed) then we can mark this as a dupe.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

mgifford’s picture

Issue tags: +color contrast, +wcag1412

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.