Problem/Motivation

Claro is aimed to be an experimental admin theme in Drupal 8.8.0 which according to Drupal development roadmap is aimed to be released on December 4, 2019. Drupal 8.8.0 feature freeze is on the week of October 14, 2019. Claro must reach at least beta status by then to be included in a stable release.

Claro stable criteria

Once the following level of feature completeness has been reached, we will consider tagging stable release for Claro:

  • All core-gates are met
  • Claro supports complex content authoring tasks including most prominent contrib modules (with more extensive validation that includes maintainers of contrib projects)
  • Claro supports all Drupal core admin interfaces
  • All global components supported by Seven have been designed and implemented

When alll that is done we can move to #3167121: Make Claro the default admin theme

Must-have issues for stable release:

Features

Done.

Accessibility

Done.

Usability improvements

Done.

Design improvements

Done.

Technical debt

Done.

Bugs

Done.

Performance

Done.

Completed

Should-have issues for stable release:

Could-have issues for stable release:

Post-stable

Claro beta criteria

Once the following level of feature completeness has been reached, we will consider tagging beta release for Claro:

  • No known data integrity or security issues
  • Everything that requires a big BC break has been solved
  • Claro supports complex content authoring tasks including most prominent contrib modules (limited validation done by maintainers of Claro acceptable at this point)
  • Claro supports most commonly used admin pages
  • All commonly used global components have been designed and implemented

Must-haves for the beta release:

Features
Bugs
Core inclusion

Should-haves for beta stability

Accessibility

Not scoped

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

lauriii created an issue. See original summary.

ckrina’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
finnsky’s picture

Assigned: Unassigned » finnsky
finnsky’s picture

Assigned: finnsky » Unassigned
ckrina’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes

Moved dialog, status report and media support to stable blockers instead of beta blockers based on discussion with @ckrina, @webchick and @Gábor Hojtsy.

ckrina’s picture

Issue summary: View changes
xjm’s picture

Project: Claro » Drupal core
Version: 8.x-1.x-dev » 8.8.x-dev
Component: Code » Seven theme
Priority: Normal » Major
andrewmacpherson’s picture

Issue summary: View changes

Adding #3080100: Assess accessibility of Claro in High Contrast AKA forced colors mode. Some problems found described there already.

saschaeggi’s picture

Thanks @Andrewmacpherson!

ckrina’s picture

ckrina’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
webchick’s picture

Updating the issue statuses.

webchick’s picture

Issue summary: View changes
xjm’s picture

Tagging for FM and RM review once this is all filled out. (I believe @webchick indicated that the product team has already identified their must-haves above.)

One thing that's a must-have for me is that the roadmap include a longterm plan to deprecate and remove Seven. So, there should be a post-stable section that includes stuff like:

  • Testing Claro for a minor or so once it's stable.
  • Resolving should-haves that weren't resolved before stable, as well as major and critical bugs that come up in real-world testing.
  • Any changes needed in core for Claro to be the default experience. (There are things like the Settings Tray, LB, etc. that are designed for Seven, and probably various other expectations.)
  • Making Claro the default admin theme in Standard for new installs.
  • A should-have/meta to gradually update screenshots to use Claro instead of Seven.
  • Deprecating Seven for removal to contrib in D10.

The roadmap should also include any specific bugs, tasks, etc. that would be needed in terms of architecture, documentation, whatever to make Claro a Seven replacement.

Finally, the roadmap also needs an issue to decouple Claro from Classy, since that's a D9 must-have for our longterm theme architecture plans.

shimpy’s picture

Issue summary: View changes

Document for theme regions in claro as compared to seven's. #3084388: Document for theme regions in claro as compared to seven's found this in one of the discussion in Add Claro administration theme to core. So created a issue for same. I am putting this as could be for stable release. Please edit if required.

shimpy’s picture

Issue summary: View changes

I am addressing one of the issue #3080994: Spacing in Claro pushes content down, requiring much scrolling discussed in #3079738: Add Claro administration theme to core commments. which is not mentioned in road map

shimpy’s picture

Addressing one more issue #2958282: Links inside surrounding text fail WCAG Use-of-Color in Seven theme as per comments in #3079738: Add Claro administration theme to core. Marking as Could-have issues for stable release

shimpy’s picture

andrewmacpherson’s picture

Issue summary: View changes

Moving #2958282: Links inside surrounding text fail WCAG Use-of-Color in Seven theme to must-have for stable release, because it relates to WCAG level A.

#19: A post-stable section is a good idea. For accessibility triage, it gives us some extra breathing space for high-impact should-haves.

shimpy’s picture

@andrewmacpherson #24 thanks for moving the issue for correct release.

shimpy’s picture

Issue summary: View changes

#3005403 also affects Claro. That's an example of an issue present in Seven that we should also add as a stable blocker for Claro, because it's borderline-critical (it'd be critical if LB were in Standard, for example). Addressing this issue in Claro Roadmap in must have stable release.

shimpy’s picture

Issue summary: View changes
shimpy’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
saschaeggi’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
effulgentsia’s picture

I think we should add at least some minimal test coverage to the must-have list. Even if it's just a single test function similar to what we have for BartikTest and ClassyTest. Or maybe a subclass of InstallUninstallTest that executes all of the same stuff but with Claro as the Admin theme.

An example of something a test like that would catch is that currently, claro.settings.yml includes a shortcut setting, but Claro does not have a dependency on shortcut module, so that's something that should fail config validation when shortcut isn't enabled.

Unfortunately, I don't think there's a way to easily test config validity outside of running a test. #2414951: Validate configuration schema before importing configuration is an issue to perform validation during import (in the UI, not only during tests), but that's not in core yet, and the latest patch on that issue isn't working correctly. But if we have an automated test, then that should catch it, since we automatically perform config validation during test runs.

lauriii’s picture

Issue summary: View changes

I talked with @ckrina to scope the non-scoped issues.

lauriii’s picture

Issue summary: View changes
andrewmacpherson’s picture

Issue summary: View changes

Starting to add a list of things that we ought to review before marking Claro as beta stage. What I'd like to see is a more detailed level of review. We can spin off child issues to capture the reviews, and I'll clarify the WCAG aspects, and offer testing advice.

Chatted with @lauriii about this, and a lot of it can be done on screen shot evidence. For things like zoom, reflow, text resize, and text spacing.

For screenshots evidence, it will be a good idea to include browser UI, so we see things like evidence of browser zoom level.

More to come, will flesh out in the next few days.

andrewmacpherson’s picture

#3057772: Ambiguous icons for collapsing/expanding menu items is already listed as a usability must-have.

It's also arguably an accessibility failure of WCAG success criterion 3.2.4 Consistent Identification (level AA). Explained in a comment on that issue.

lauriii’s picture

Issue summary: View changes

Added #3086435: Add automated test coverage for Claro to the beta-blockers to address #39.

xjm’s picture

Issue summary: View changes

Per #3079738: Add Claro administration theme to core comments #61 through #63, listing the accessibility testing issues as should-haves for beta, but re-listing them as must-haves for stable also. So the only must-haves are the minimum requirements for core inclusion, the MVP feature-set, and one bug that has been flagged as critical.

Thanks!

xjm’s picture

Issue summary: View changes

Oops, copied a couple issues too many.

lauriii’s picture

svettes’s picture

Status summary:

  • One last remaining blocker for Claro beta-1 release is being worked on by Zoltan, expected completion is EO this week: #3021092: Image field style update
  • Claro Roadmap is updated based on review of issue queue
  • 8.8.0-Alpha1 framework reviews are nearly complete
  • Requirements for 8.8.0-Beta1 still need clarification


Risks related to the 8.8 release:

  • We need clarity on Beta requirements and any work required to meet them asap or this won't get into the 8.8 release, see this issue for details: #3079738 comment #69


Next steps:

All dates are asipriational!

  • Tag Claro Beta-1 when the last blocking issue is resolved (hopefully eo this week or early next week)
  • Clarification on requirements for 8.8.0-Beta1, additional reviews and associated work (see #3079738 comment #69 for details)
xjm’s picture

Requirements for 8.8.0-Beta1 still need clarification

Again, what is unclear? I feel like the beta requirements are very clearly fleshed out in the IS here, and the release managers have already given feedback on what we need for Claro to be included in a tagged release.

xjm’s picture

Last night @webchick reluctantly agreed with me that under experimental policy, #3067386: AJAX rebuild of Views UI form re-renders parts of the form without using Form API, so additional hooks are needed in lieu of hook_form_view_edit_form_alter() could be committed during the theme's alpha phase, since the Views UI not being terrible could be considered part of the MVP and there's no specific requirements for horrible bugs to be fixed before alpha unless they affect security, data integrity, or the upgrade path. However, @webchick indicated that we would strongly prefer it be done before the theme is committed as an alpha module, because it will interfere with testing of the theme.

So based on that, we agreed to make it a should-have for alpha instead of a must-have, but it's still must-have before beta. The IS is accurate already since it lists the beta requirements, not the alpha require,ents.

That said, again, this issue is a priority to fix sooner rather than later compared to the other beta requirements, and having it in before 8.8.0-alpha1 would be ideal.

effulgentsia’s picture

Issue summary: View changes

Adding #3087189: Resolve or work around claro.settings.yml implicit dependency on Shortcut to the must-have list, because it's a potential data integrity issue.

andrewmacpherson’s picture

Issue summary: View changes

Fleshed out a manual test plan for #3087225: [META] Assess Claro's conformance with WCAG Text spacing, Text resize, and Reflow.. More to follow for the Resize text and Reflow criteria.

Re. #45
For these WCAG resize/adaptation robustness criteria, I'm attempting to find achievable approaches for a first-pass survey prior to beta.

A good beta-stage assessment for these would be full-page captures from the Styleguide and Error style modules with a variety of browser/OS settings, or CSS bookmarklets applied.

Those can give us a good overview, before making a more detailed assessment prior to stable. We can approach the various layout and colour adaptation (high contrast) surveys this way.

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.

xjm’s picture

Untagging as per #3079738-80: Add Claro administration theme to core comments #80 and #81. The roadmap is really clear. Be sure to keep adding new issues that are identified to it (e.g. the JavaScript should-haves that were identified by @justafish).

We'll re-review the roadmap when we're targeting a stable release.

lauriii’s picture

Component: Seven theme » Claro theme
lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
effulgentsia’s picture

effulgentsia’s picture

All the beta must-haves are done, so #3088437: Cherry pick Claro to Drupal 8.8.!!!

andrewmacpherson’s picture

Update on some of the accessibility reviews which were marked should-have for beta.

andrewmacpherson’s picture

Issue summary: View changes
Thirugnana Sambandam’s picture

Issue summary: View changes
Thirugnana Sambandam’s picture

Issue summary: View changes
saschaeggi’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
andrewmacpherson’s picture

Issue summary: View changes

Updatin the accessibility issues for stable. Moving remaining accessibility issues from beta.

lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
lauriii’s picture

lauriii’s picture

Issue summary: View changes
geerlingguy’s picture

QQ, don't know if this is the right issue to ask in—is 'dark mode support' something that's considered for the path to stability—or is that a feature addition that might be considered later? And in either case, is there an existing issue for dark mode support in Claro or not? My Drupal sites are one of a few places where things are nice and dark normally, but go to edit a page and wham-o, I get hit with a glaring bright white screen.

saschaeggi’s picture

@geerlingguy something to consider for the future. We already did some exploration on the design side of things for a dark mode but it's still far away from being implemented at this point.

ckrina’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes

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.

Ambient.Impact’s picture

@geerlingguy I too would love a dark mode and have the same experience lately.

saschaeggi’s picture

@Ambient.Impact @geerlingguy a lot happened since my last comment. You can already get a Darkmode if you install the Gin Admin Theme - which is based on Claro.

Ambient.Impact’s picture

@saschaeggi That's pretty awesome, thanks!

lauriii’s picture

Issue summary: View changes

Scoped the issues with @webchick, @Gábor Hojtsy, @ckrina.

lauriii’s picture

Issue summary: View changes

More scoping with @webchick, @Gábor Hojtsy, @ckrina.

lauriii’s picture

Issue summary: View changes
bnjmnm’s picture

Issue summary: View changes

Adding dependee issues to some items in roadmap for better visibility.

bnjmnm’s picture

Issue summary: View changes
Nelo_Drup’s picture

Hi, I don't know if it is the right place, but there is an important bug in /admin/config/content/formats when you create a new format, for example Custom, the tabs of CKEditor plugin settings are all hidden with display none.

Note: this is shown if I put display visibility and in teroria there must be 6 tabs

Ckeditor tabs

bnjmnm’s picture

Issue summary: View changes
bnjmnm’s picture

Issue summary: View changes
bnjmnm’s picture

Issue summary: View changes
bnjmnm’s picture

Issue summary: View changes
bnjmnm’s picture

Issue summary: View changes
rainbreaw’s picture

Issue summary: View changes
andrewmacpherson’s picture

Issue summary: View changes

Discussed #3127466: Required fields are not identifiable on Internet Explorer 11 high contrast with @rainbreaw today. We'd like to bump it to major/must-have, because indicating required fields is a WCAG level-A need. Detailed remarks in comment #14 there.

bnjmnm’s picture

Issue summary: View changes
bnjmnm’s picture

Issue summary: View changes
bnjmnm’s picture

Issue summary: View changes
bnjmnm’s picture

Issue summary: View changes
bnjmnm’s picture

Issue summary: View changes
bnjmnm’s picture

Issue summary: View changes
jwilson3’s picture

If the variable names in the css files can be considered an API, then probably #3155531: Naming convention of color shades in the Drupal Design System (e.g. for Claro) should be on this list as a stable blocker otherwise it might never get fixed once the project become stable.

lauriii’s picture

jwilson3’s picture

Issue summary: View changes
lauriii’s picture

lauriii’s picture

Issue summary: View changes
ckrina’s picture

Issue summary: View changes
yoroy’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes

Discussed with @ckrina, @yoroy, @Antoniya and @saschaeggi and we agreed that we should descope the sidebar region from the stable blocking issues to be something we work on post-stable. Claro does not use, or support sidebars at the moment. We could start to use it, but that needs a lot of effort to make it work well. That should not be part of declaring Claro stable because it can be provided later, and we don't have any stable blocking issues needing it. This is also not a regression because Seven doesn’t provide a sidebar either.

lauriii’s picture

Issue summary: View changes
DyanneNova’s picture

Issue summary: View changes

Removing #3085219: Installer is not very usable in Claro from Must-haves for stable release. This is a must have for making Claro the default theme, but not a must have for a stable release.

lauriii’s picture

lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
batkor’s picture

lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes

Removed #3083039: Allow tabledrag to be disabled from the stable blockers because it is a new feature that shouldn't be specific to Claro.

Also removed #3084910: Insert tabledrag changed mark after the drag handle, and not after the last item in the cell from the stable blockers because there's a way for Claro to change that behavior without having to override the whole tabledrag library.

lauriii’s picture

Issue summary: View changes
andrewmacpherson’s picture

lauriii’s picture

Issue summary: View changes

It seems like #3092296: Improve email address field description at /user/register was marked as a should have for the stable release until it was marked as a blocker for #3082672: Form prefix/suffix redesign in Claro which is a stable blocker. After it was removed from the blockers of #3082672: Form prefix/suffix redesign in Claro, it was kept in stable criteria mistakenly. I'm moving it back to should have issues.

lauriii’s picture

Issue summary: View changes

Discussed #3155531: Naming convention of color shades in the Drupal Design System (e.g. for Claro) in the Claro call today. We don't think it should be a stable blocker because it doesn't have end user impact. Claro will also remain internal after being marked stable, so we can make the change later.

lauriii’s picture

Issue summary: View changes

Discussed with @ckrina, @saschaeggi and @Gábor Hojtsy and we decided to remove #3083044: Prevent line breaks in draggable (first) table cells from the roadmap given that it's a pre-existing problem.

Niklan’s picture

Nelo_Drup’s picture

Title: Roadmap to stabilize Claro » Hoja de ruta para estabilizar Claro

Hi problem with Paragraph and File Entity Browser display corrupt
https://imgur.com/a/xKNhtsD

saschaeggi’s picture

Title: Hoja de ruta para estabilizar Claro » Roadmap to stabilize Claro
saschaeggi’s picture

andrewmacpherson’s picture

Issue summary: View changes

I think #3070558: Implement bulk operation designs should be moved from must-have to could-have. Surely it won't be a disaster if the bulk operation controls are arranged the same way as they are with Seven.

The patch in that issue has caused a lot of accessibility problems. Proposed workarounds are elaborate (and sometimes bizarre), and I'm not convinced they're safe. I'm unwilling to rush this one.

andrewmacpherson’s picture

Issue summary: View changes

#3171726: Claro Shortcuts star fails WCAG Use of Color and Non-text contrast is a WCAG level-A failure, and wasn't added to this roadmap yet.

andrewmacpherson’s picture

#3171726: Claro Shortcuts star fails WCAG Use of Color and Non-text contrast is a WCAG level-A failure, and wasn't added to this roadmap yet.

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.

effulgentsia’s picture

Issue summary: View changes

Moved completed stable-must-haves to a Completed section.

effulgentsia’s picture

Issue summary: View changes

Missed one.

effulgentsia’s picture

Issue summary: View changes
rrafferty313’s picture

Has anyone seen issues between Claro and the Simple hierarchical select Module? We've been experiencing a problem where the select fields disappear and cache has to be cleared to restore them.

effulgentsia’s picture

JeroenT’s picture

I'm also experiencing the bug reported over here: #3183425: [backport] Google Chrome 87 renders fieldset with grey artefacts

Is this something that should be added to the list of bugs in this issue?

andrewmacpherson’s picture

Issue summary: View changes

Adding #3194669: Misuse of explicit colour for active pager item in -ms-high-contrast media query as a must-have, because it involves a WCAG level-A failure. It's easily fixed.

Gábor Hojtsy’s picture

Parenting to easy out of the box :)

volkswagenchick’s picture

Issue tags: +Easy Out of the Box

Adding Easy Out of the Box tag.

ckrina’s picture

Issue summary: View changes

Rearranging issues so the Beta ones already done stay at the end.

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.

GuilhermePuentes’s picture

Olá GALERA da comunidade DRUPAL, essa minha primeira interação com você!
Uma obervação não domino o idioma inglês vou google tradutor.

Gostaria de propor um link de atralho para a pagina de [novo tipo de conteúdo].
Dentro da pagina novo tipo de conteudo navegue até a [aba configurações do menu],
na imagem eu tentei ilustrar minha ideia, no titulo da lista de menus já existentes ao lado colocar ou criar um link de atalho para a pagina [../admin/structure/menu/add] coloquei o icone do lapis veja os prints para ilustrar.
Olivero 9.1.8 (Tema padrão, experimental theme)
Seven 9.1.8 (Tema padão seven)

Disponibilizo o link do meu figma:
https://www.figma.com/file/IgiaaWPcIiien0xoHDF0s9/Theme-Claro-end-Olivero


ENGLISH VERSION

Hello GUYS from the DRUPAL community, this is my first interaction with you!
An observation I do not master the English language I will google translator.

I would like to propose a link to the [new type of content] page.
Within the new content type page, navigate to the [menu settings tab],
in the image I tried to illustrate my idea, in the title of the list of existing menus next to place or create a shortcut link to the page [../admin/structure/menu/add] I put the pencil icon see the prints to illustrate .
Olivero 9.1.8 (Standard theme, experimental theme)
Seven 9.1.8 (Standard seven theme)

I provide the link of my figma:
https://www.figma.com/file/IgiaaWPcIiien0xoHDF0s9/Theme-Claro-end-Olivero

pixelite’s picture

Welcome GuilhermePuentes! I like your idea of linking to menu settings page from the content type config page (although I can't seem to access the Figma link you included).

I think you should probably create a separate issue for this, because this would mean adding a feature/improvement to Claro.

You can also collaborate on UX improvements in the #UX channel on the Drupal Slack (https://www.drupal.org/join-slack).

GuilhermePuentes’s picture

Thanks for the @pixelite reception, I’m happy with your comment, I hope to contribute much more.
I will update the figma link for public beginner failure.

For your guidance on creating a new issue (create a separate issue) I have not yet learned how to create a new resource.

Regarding the slack group, I managed to get in. Thanks for sharing! See you soon!

GuilhermePuentes’s picture

Thanks for the @pixelite reception, I’m happy with your comment, I hope to contribute much more.
I will update the figma link for public beginner failure.

For your guidance on creating a new issue (create a separate issue) I have not yet learned how to create a new resource.

Regarding the slack group, I managed to get in. Thanks for sharing! See you soon!

joelpittet’s picture

Issue summary: View changes
ckrina’s picture

Issue summary: View changes

Adding #3222995: Implement chips based autocomplete designs as a could have so it gets referenced.

ckrina’s picture

ckrina’s picture

Issue summary: View changes

Cleaning up summary from completed tasks.

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.

ckrina’s picture

Issue summary: View changes

Referencing #3254202: Remove IE11 Support from Claro as post-stable work.

lauriii’s picture

Issue summary: View changes

Triaged the stable blockers with @ckrina, @saschaeggi, @Gábor Hojtsy and @bnjmnm.

Moved to should haves:

On top of that, we thought that it would be helpful if the accessibility topic maintainers could triage the accessibility stable blockers and add any issues that need to happen before stable to this issue. We also ran out of time to triage the vertical tabs issues.

mherchel’s picture

We also ran out of time to triage the vertical tabs issues.

Not sure if this is the right place to say this, but we should consider descoping the the vertical tabs issues out of Claro so the the fixes can be used by all other themes (including contrib, and custom themes). There's no reason why the accessibility features and UX improvements should be Claro-only.

joelpittet’s picture

Gábor Hojtsy’s picture

lauriii’s picture

Issue summary: View changes

#3171726: Claro Shortcuts star fails WCAG Use of Color and Non-text contrast was moved to the Shortcut module issue queue because the bug exists in all core themes.

lauriii’s picture

Issue summary: View changes
lauriii’s picture

effulgentsia’s picture

ckrina’s picture

Issue summary: View changes

Removing #3068696: Tables overflow on mobile as stable blocker.

andregp’s picture

Issue summary: View changes
ckrina’s picture

Issue summary: View changes

Update fixed issues.

ckrina’s picture

Issue summary: View changes

Remove some unneeded criteria for stable.

bnjmnm’s picture

Issue summary: View changes

Updated roadmap with should-haves surfaced by the recently closed #3088562: [META] Assess Claro for WCAG colour contrast AA conformance

ckrina’s picture

ckrina’s picture

ckrina’s picture

ckrina’s picture

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.

mherchel’s picture

Can this be closed now since Claro is stable?

ckrina’s picture

ckrina’s picture

Status: Active » Fixed

Finally closing this issue because Claro became stable in #3277053: Mark Claro as Stable. Let's continue improving Claro on the issue queue. Thanks everybody involved by all your work!!

Ambient.Impact’s picture

🙌🎉

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.