• Resolved karlemilnikka

    (@karlemilnikka)


    Thanks for yet another good update of the Spectra plugin.

    I understand that AI stuff is the hot thing right now, but are you planning a release more focused on addressing bugs and improving the markup?

    There are many Spectra blocks that are almost ready to use in-production that just lack a few final tweaks, so they follow the a11y guidelines, have better support for keyboard navigation, have paragraph blocks inside the accordion panes/tab panes, and have selectable element types (div/aside/section).

    • This topic was modified 10 months ago by karlemilnikka. Reason: Grammar
Viewing 6 replies - 1 through 6 (of 6 total)
  • Mehedi Hasan

    (@thebengalboy)

    Hello @karlemilnikka

    I’m Mehedi Hasan, Product Manager of Spectra. Thank you for being with us and sharing your ideas on how we can improve Spectra. We truly appreciate your contributions.

    Besides the AI and all the new features we are releasing and have in the pipeline, we are also focused on bug fixes and improvements with equal effort. New features are not our only priority; bug fixing and improvements are as well. If you follow the release changelog, you’ll see that every release includes bug fixes and improvements, along with new features.

    Regarding Accessibility:
    I can assure you that accessibility is a top priority for all BrainstormForce products. If I’m not mistaken, you previously reported an accessibility issue with Modals and Popups, which we have recently fixed (it is yet to be released). Similarly, if you find any specific issue, please feel free to let us know. We’d be happy to resolve them.

    Could you share more about the markup improvements and how you envision having the paragraph blocks inside the accordion panes/tab panes, and with selectable element types? I want to understand your request better so we can plan it more effectively.

    Again, thank you for being part of the Spectra community. We are grateful to have you with us.

    Regards,

    Mehedi Hasan

    Thread Starter karlemilnikka

    (@karlemilnikka)

    Thanks for the reply.

    You have a couple of open tickets regarding the accessibility issues I found in the blocks we considered using. It would be great if you could look into them. They’ve been left open for months.

    When adding text into the Tabs blocks, Accordion blocks and Inline notice blocks, the text is put directly into a div. You cannot break the text into multiple paragraphs. If you want to give the impression of multiple paragraphs, you must fall back to adding line breaks. The equivalent blocks from your competitors (Kadence Blocks and Generate Blocks) put the text in paragraphs.

    Addressing the mentioned issue would even open up for including other block types in the future, for example image blocks and code blocks (already offered by the mentioned competitors). You gave us a perfect example of why this is needed when you published https://wpastra.com/docs/blog-archive-improvements/. In the first version, you included the filters at the bottom in the Inline notice block, causing '__return_true' (valid syntax) to turn into ‘__return_true’ (fatal error). You solved it by moving the filters to a code block outside the inline notice.

    Please ignore the part about selectable element types. That’s an issue in Astra, not Spetra. Spectra handles this exactly as it should.

    Thanks for taking your time to read this and I look forward to future updates.

    Mehedi Hasan

    (@thebengalboy)

    @karlemilnikka Thank you for getting back and sharing the details.

    Accessibility: If you have already reported that to us, rest assured we will solve it soon.

    Paragraph:

    1. I’ve tested the Tabs block, and adding an enter between the text divides it into two paragraphs. Reference- https://d.pr/i/Jroz1Q
    2. I found the problem with ‘Inline Notice’. It is used?<br>?instead of dividing the content into two paragraphs. We will improve this in the future.?

    Please feel free to ask if you have any further questions. Or please mark the topic as done.

    Thank you

    Thread Starter karlemilnikka

    (@karlemilnikka)

    Thanks for the reply.

    I look forward to the accessibility improvements. I’m glad to hear that they’ll be solved soon. The tickets have been left unattended for three months, so I thought you’d forgot about them.

    Good to know that the tabs block isn’t affected by the paragraph issue. I misremembered it as being affected just like the mentioned accordion block (FAQ block) and inline notice. I checked some other blocks as well and found them to have the same issue, e.g., the review block.

    Speaking of the tabs block and accessibility issues, please consider updating it to follow the accessibility guidelines for markup and navigation.

    Hi @karlemilnikka

    Thank you so much for your invaluable feedback! We’re taking the accessibility issues you reported seriously and will be working on them soon. We’re also looking at ways to improve the markup.

    Thread Starter karlemilnikka

    (@karlemilnikka)

    Adam Preiser told me the Spectra team is working on accessibility focused updates.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Bug-fix focused update’ is closed to new replies.