- Issue created by @the_g_bomb
- Merge request !177Issue #3485831: Add a dashboard to the Accessibility Tools recipe. β (Open) created by the_g_bomb
- πΊπΈUnited States phenaproxima Massachusetts
There are no real technical problems here, but the dependencies on core recipes pose some issues that you didn't cause, but we still have to figure out, before I can commit this.
- π¬π§United Kingdom the_g_bomb
I'll give it a blast to make the change requested. I was trying to follow the style of the SEO Dashboard, so I think the Full HTML is possibly only to allow the addition of a class to the a tag. If I alter the existing Basic HTML filter to add the class attribute to the allowed list. That would remove the need for the use of Full HTML.
- π¬π§United Kingdom the_g_bomb
I removed the dependency on the image format, it wasn't needed.
I also changed the full_html dependency to the existing easy_email and it hasn't got the "Limit allowed HTML tags" which removed the needed class. - πΊπΈUnited States phenaproxima Massachusetts
Seems reasonable but we should not be relying on the easy_email format. It's for emails.
- πΊπΈUnited States phenaproxima Massachusetts
Looks good to me from a code perspective; assigning to @pameeela for final review.
- π¦πΊAustralia pameeela
I'm quite hesitant to add another dashboard that really only contains links, and I need to run this by the UX team.
Separately the text format issue is a real problem! Definitely don't want to add basic_html for blocks on a dashboard, and now I see that Full HTML was added back for a different dashboard..... yikes.
- π¬π§United Kingdom the_g_bomb
Happy to park this. The intention is to have a content view here, which will show accessibility issues with a users content. But the module that provides that isn't in existence yet, so I can re-address this when the view is available.
- π¦πΊAustralia pameeela
@the_g_bomb yes basically I think that's what we should do, wait until we have the content view.
But I also think this might be suitable to add to the main dashboard, rather than having a separate one for that.
- πͺπΈSpain penyaskito Seville π, Spain πͺπΈ, UTC+2 πͺπΊ
Once β¨ Provide a Config Action to add/edit a component in a layout Active lands, the recipe could just add a block to the welcome dashboard.
For that instead of a list of links, we decided to use menus in π Define how wireframes links block on the right should be created Active . Probably we want to use the same here.
This depends on β¨ Render menus as a list of CTAs Active landing on the dashboard module. This will create a stacked vertical list of links, not sure if you intended this to be horizontal.That will be implemented for the creation actions in π Provide a "Dashboard CTA" menu for the content creation CTAs Active (no MR yet, sorry)
- Issue was unassigned.
- Status changed to Postponed
11 days ago 1:52pm 12 June 2025 - π¬π§United Kingdom the_g_bomb
FYI, There is now a way to create a list of content and display the A11y issues status, so I may like to bring this out of postponment if there is still appetite for an A11y related block on a Dashboard.
At first thoughts I would wonder how that would be applied to an existing dashboard. Does the recipe need to know where on Dashboard it is going to be applied, given that the Accessibility Tools are an optional recipe and will likely be enabled after everything else has been setup.
- πΊπΈUnited States thejimbirch Cape Cod, Massachusetts
This change record has details on the config action you would use to add it.
- πΊπΈUnited States phenaproxima Massachusetts
I'm happy to pull this out of postponement. We'd need to do additional refactoring to move the dashboard into another module (maybe drupal_cms_admin_ui, so that drupal_cms_accessibility_tools could depend on it) but that could all happen in this issue's scope. For now, implement it in whatever way gets it looking and working how you want. I can assist with the refactoring.