Problem/Motivation
This issue is a follow-up issue based on accessibility feedback from rainbreaw.
Dialog UI in standard profile (with Bartik theme) should use an outline around form elements when tabbing, as does demo umami profile.
Demo umami outline.

Standard profile, highlight, but no outline.

Proposed resolution
Suggested improvement, add outline:

Remaining tasks
- Review
- Commit
| Comment | File | Size | Author |
|---|---|---|---|
| #37 | olivaro-radio.png | 30.19 KB | ainsofs |
| #37 | claro-radio.png | 42.04 KB | ainsofs |
| #37 | claro-textbox.png | 30.58 KB | ainsofs |
| #31 | interdiff_28-31.txt | 1.19 KB | kiran.kadam911 |
| #31 | 3077559-31.patch | 451 bytes | kiran.kadam911 |
Comments
Comment #2
oknateSuggested change, in /core/themes/bartik/css/components/ui-dialog.css
Comment #3
oknateComment #4
oknateHere's a patch.
Comment #5
oknateComment #6
oknateComment #7
oknateComment #8
oknateComment #9
oknateFixing this for Seven (which inherits from Classy) too. No screenshot is necessary as it looks nearly identical to the screenshot in #4.
Comment #10
andrewmacpherson commentedReview of patch #8:
Why so many selectors here? Won't a
:focuspseudoclass be enough, without specifying it 3 times for different element types?What about buttons and links?
Comment #13
kiran.kadam911We can directly use like below if we want to consider accessibility focus on all elements.
and if we considering ui-dialog & it's element only then we can use below,
Feel free to add your opinion.
Thanks!
Comment #14
bandanasharma commentedRe-roll the patch for 9.x.1 as per above comments. Outline is added only for ui-dialog as of know. Please review the same.
Comment #16
kishor_kolekar commentedplease review the patch.
Comment #17
meena.bisht commentedComment #18
meena.bisht commentedThis patch works good to me . On using tab, Outline is added for ui-dialog in Bartik and Seven .
Comment #20
meena.bisht commentedComment #21
meena.bisht commentedComment #23
djsagar commentedRe-roll patch 9.2.x.
Comment #24
sulfikar_s commentedHi, I've tested the patch on #23. Rather than the custom commands failure(I think it's a random failure, anyway need more clarification!), It works correctly as per the requirements on the drupal 9.2.x-dev environment. I'm attaching the screenshots below.
Before,

After,

Need more clarification for the custom commands failure. Here, it is shown like this,

Otherwise RTBC+1
Comment #25
gauravvvv commentedI have provided the patch, please verify if it working or not.
Comment #27
rinku jacob 13 commentedVerified and tested patch#25 for drupal 9.3.x-dev version. Patch applied successfully and looks good to me.Adding screenshot for the reference.thanks @Gauravmahlawat.
Comment #28
sakthivel m commented#28 Fixed Custom Commands Failed.
Comment #29
chetanbharambe commentedVerified and tested patch #28.
Patch applied successfully and looks good to me.
Testing Steps:
# Apply Bartik theme -> admin/appearance
# Goto: admin/config/content/formats
# Click on Configure
# Add Image button into Active Toolbar
# Save configuration
# Goto: node/add/article
# Goto: Body field and click on Image button to insert the image
# Check the focus indicators on respective buttons
Expected Results:
# User should see square focus applied on respective buttons
Actual Results:
# User is not able to see focus indicators on buttons
Please refer attached screenshots.
Looks good to me.
Can be a move to RTBC.
Comment #30
lauriiiCI is failing for the latest patch so moving back to needs work
Comment #31
kiran.kadam911Providing updated patch for Bartik theme.
Kindly review the patch.
Thanks!
Comment #33
mgiffordI think this is a WCAG 2.4.11 issue.
Comment #37
ainsofs commentedDiscussed with @larowlan, @seth-hilder and @tinarey. We suspected that the issue is with core as it occurs on all three themes mentioned. We found that 10.0.x have sufficient outlining for form fields in Claro and Olivero themes (see screenshots attached).
As a result we think this is only present in Bartik. Moving this issue to the Bartik queue as it is now a contrib module.
Comment #38
mgiffordTagging for WCAG 2.2
https://www.w3.org/WAI/WCAG22/Understanding/focus-not-obscured-minimum