Update the Accessibility Tools recipe

I am leaving this as draft purely to see how Experience builder pans out.

For Editoria11y to work optimally it should have an inline preview, which works well with Same Page Preview module.

If Experience builder is to land with similar functionality, then we will use that instead.

The question becomes do we add this to add that functionality and then replace it with Experience builder when it is ready?

The issue the Same page review module, no londer seems to be causing an issue. It may be worth having a discussion if the accessibility tools recipe can be updated to include the module now to enhance the current functionality.

The related issue is: 🐛 Incompatibility with autocomplete entity reference fields Active

If it helps -- the 2.2 branch → with the as-you-edit checker now includes default config that will ignore the same page preview frame and live-check the CKEditor fields instead. It also moves the panel over off the preview pane into the editor column. And it avoids covering the Klaro dialogs.

the_g_bomb → closed merge request !74

Thanks @itmaybejj, I've teseted the new 2.2 version. Looks good.

I have added some content to Demo Editoria11y based on the content at: https://editoria11y.princeton.edu/demo/

I have also updated the recipe to include the 2.2 branch. This way a demo can include inline/live feedback.

I'll use this to produce a video for potential inclusion in the Singapore Keynote.

I should have exported the default content without SEO Tools enabled. I have updated the PR so the content doesn't include default metatag content.

Mostly looks fine but I don't think we need to rely on Pathauto.

Almost, but it looks like a line that shouldn't be there is still there.

Assigning to @pameeela for final review.

This is a cool idea :) just suggested that the demo page should be unpublished, do you disagree @the_g_bomb?

Just one other question, since this page exists and obviously has issues, shouldn't I see it on the report? The report is still empty for me:

Back to @the_g_bomb for input.

I don't disagree that the page should be unpublished. I'll update the PR.

I'll also reach out to @itmaybejj about the missing data on the report page. That should have data in it.

I think I have this fixed now in RC6 → .

Thank you for finding this -- I had gotten one report of this previously, but hadn't been able to reproduce the bug. Basically -- if you manually uninstall and install the module, everything is fine, but for some reason via the recipe, the optional config was being ignored. It's...not optional any more.

Also -- I attached a patch with some suggested changes to the demo page → .

@itmaybejj - as @thejimbirch artfully put it, recipes know not of "optional". They bring in all the config from an extension of you do something like config:import:extension_name: '*' in your recipe.yml.

I have updated the recipe to import * config. I also changed the default content as per @itmaybej 's patch.

No objections at the code level. Reassigning to @pameeela to confirm that the problem she saw, is fixed.

Ship it!

Merged into 0.x, thanks!

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