WordPress.org Forums » All Posts https://wordpress.org/support/forum/accessibility/feed/ Wed, 14 May 2025 21:04:49 +0000 https://bbpress.org/?v=2.7.0-alpha-2 en-US https://wordpress.org/support/topic/need-free-alternative-to-ally-by-elementor-formerly-one-click-accessibility/#post-18440147 <![CDATA[Need Free Alternative to Ally by Elementor (Formerly One Click Accessibility)]]> https://wordpress.org/support/topic/need-free-alternative-to-ally-by-elementor-formerly-one-click-accessibility/#post-18440147 Mon, 28 Apr 2025 18:13:49 +0000 ip00 I have used the One Click Accessibility plugin for years to provide a basic accessibility toolbar on a WordPress website. Although it wasn’t actively maintained over the last year or two, it continued to serve me well.

Recently, the plugin was acquired by Elementor, rebranded as Ally, and heavily reworked. While this sounded promising at first, unfortunately it introduced significant changes:

  • The plugin is no longer fully free.
  • You must now create an Elementor account to use it.
  • There are new usage caps based on visitor numbers, tied to subscription plans.

Previously, Elementor representatives had stated in the WordPress.org forums that the plugin would remain free, but they have since reversed that position.

Because of this, I am now looking for an alternative that is truly open source and free — something aligned with WordPress community values.

I have tried a few accessibility plugins from WordPress.org, but most of the experiences were underwhelming: many plugins lacked essential features, had outdated interfaces, or felt too bloated for the simple use case I’m aiming for.

What I’m looking for:

  • A lightweight, reliable accessibility toolbar (font resizing, contrast toggles, etc.)
  • Open source, GPL-licensed, and free to use without account requirements or visitor limits
  • Clean, user-friendly, non-bloated

I believe that the core of accessibility should be handled at the development level — through proper semantic HTML, good structure, and real accessibility testing — but a basic toolbar is still a helpful tool for visitors.

If anyone knows of a project that fits, or if there’s an open source effort starting/existing, I’m happy to contribute:

  • Feedback and bug testing
  • UI/UX design
  • General usability advice

Thanks for your suggestions!

]]>
https://wordpress.org/support/topic/product-pages-poor-accessibility-score-88-in-pagespeed-insights/#post-18434874 <![CDATA[Reply To: Product Pages Poor Accessibility Score (88) in PageSpeed Insights]]> https://wordpress.org/support/topic/product-pages-poor-accessibility-score-88-in-pagespeed-insights/#post-18434874 Thu, 24 Apr 2025 23:52:58 +0000 boydedmondson Here they are larger:

Screenshot 1

Screenshot 2

Screenshot 3

OK, I’ll check GoDaddy theme support team.

Thanks!

]]>
https://wordpress.org/support/topic/product-pages-poor-accessibility-score-88-in-pagespeed-insights/#post-18434746 <![CDATA[Reply To: Product Pages Poor Accessibility Score (88) in PageSpeed Insights]]> https://wordpress.org/support/topic/product-pages-poor-accessibility-score-88-in-pagespeed-insights/#post-18434746 Thu, 24 Apr 2025 21:26:35 +0000 threadi Unfortunately, nothing is recognizable in the first screenshot, so I did a test myself. The messages refer to output in the HTML code of the theme. I would therefore recommend that you contact their support. You are obviously using a theme from GoDaddy, which is why I would recommend contacting their support.

]]>
https://wordpress.org/support/topic/product-pages-poor-accessibility-score-88-in-pagespeed-insights/#post-18434706 <![CDATA[Product Pages Poor Accessibility Score (88) in PageSpeed Insights]]> https://wordpress.org/support/topic/product-pages-poor-accessibility-score-88-in-pagespeed-insights/#post-18434706 Thu, 24 Apr 2025 20:29:19 +0000 boydedmondson All my WooCommerce product pages, such as https://nebulasoftware.com/product/displayswitcher/, have poor PageSpeed Insights Accessibility scores of 88, in both mobile and desktop.

See the screenshot for details. https://videos.nebulasoftware.com/watch/cTf0bonjLNd

Are these WooCommerce plugin deficiencies? If so, then can someone fix them?

I worked extensively with ChatGPT to try various fixes, but nothing ever worked. But, I will give a screenshot of ChatGPT’s suggested support request text, in case it provide more useful information.

Screenshot: https://videos.nebulasoftware.com/watch/cTf0bDnjLNL

Thank you!

]]>
https://wordpress.org/support/topic/website-logo-in-nav-bar-takes-more-time-to-load/#post-18428751 <![CDATA[Reply To: Website Logo in nav bar takes more time to load]]> https://wordpress.org/support/topic/website-logo-in-nav-bar-takes-more-time-to-load/#post-18428751 Tue, 22 Apr 2025 06:24:19 +0000 saad650 The slow logo load might be due to a large image size, format (use WebP), or lazy loading. Try optimizing the image and check if it’s being delayed by theme settings or a lack of CDN.

]]>
https://wordpress.org/support/topic/audio-player-controls-not-accessible/#post-18426208 <![CDATA[Reply To: Audio player controls not accessible]]> https://wordpress.org/support/topic/audio-player-controls-not-accessible/#post-18426208 Sun, 20 Apr 2025 07:06:02 +0000 Jayden Blake The basic WordPress audio player does include volume and time slider controls, but they are not fully accessible with screen readers like NVDA. NVDA can read elapsed and total track time but does not detect the sliders, preventing adjustments to playback position or volume.

Solutions:

Use an Accessible Audio Player Plugin – Install plugins like “MediaElement.js” or “WP Accessible Audio Player” that offer improved accessibility with ARIA labels and keyboard navigation.
Custom ARIA Enhancements – Developers can enhance the default player by adding ARIA roles, states, and keyboard focus to sliders for better screen reader compatibility.
Keyboard Shortcuts – Use system-level media keys (e.g., volume up/down) as a workaround to adjust volume, though this doesn’t address the time slider issue.

]]>
https://wordpress.org/support/topic/how-to-add-aria-live-property-to-notice/#post-18426207 <![CDATA[Reply To: How to add aria-live property to notice]]> https://wordpress.org/support/topic/how-to-add-aria-live-property-to-notice/#post-18426207 Sun, 20 Apr 2025 06:59:17 +0000 Jayden Blake The aria-live attribute is missing because the @wordpress/components Notice component isn’t applying politeness=”polite” as expected, likely a bug.

Quick Fix
Wrap the Notice in a <div> with aria-live:

jsx

Copy
import { Notice } from ‘@wordpress/components’;

function AccessibleNotice() {
return (
<div aria-live=”polite” role=”status” aria-atomic=”true”>
<Notice status=”warning” politeness=”polite” isDismissible={false}>
Here is a test notice
</Notice>
</div>
);
}
Steps
Test: Verify with NVDA/VoiceOver; ensure the notice is announced.
Check Version: Update WordPress (e.g., 6.6.2) and Gutenberg (e.g., 18.0+). Retest original JSX.
Report Bug: If still missing, file an issue on Gutenberg GitHub with your JSX, HTML output, and versions.

]]>
https://wordpress.org/support/topic/unable-to-navigate-blocks/#post-18425191 <![CDATA[Reply To: Unable To Navigate Blocks]]> https://wordpress.org/support/topic/unable-to-navigate-blocks/#post-18425191 Sat, 19 Apr 2025 07:01:22 +0000 Armando Update: Apparently, they removed the escape shortcut due to some issues.

https://github.com/WordPress/gutenberg/issues/65603

]]>
https://wordpress.org/support/topic/unable-to-navigate-blocks/#post-18423575 <![CDATA[Reply To: Unable To Navigate Blocks]]> https://wordpress.org/support/topic/unable-to-navigate-blocks/#post-18423575 Fri, 18 Apr 2025 07:24:09 +0000 Armando Hello @devasheesh Kaul and all,

Thank you for the clarification.

Right now, I decided to downgrade to WordPress 6.7.2 until the command for the escape key and to easily navigate the blocks is fixed in a later update.

]]>
https://wordpress.org/support/topic/unable-to-navigate-blocks/#post-18423550 <![CDATA[Reply To: Unable To Navigate Blocks]]> https://wordpress.org/support/topic/unable-to-navigate-blocks/#post-18423550 Fri, 18 Apr 2025 07:06:54 +0000 Devasheesh Kaul Hey @armandovias,

Yeah, the shift was there for the uppercase ‘O’, thus making it ‘Alt + O’ instead of ‘Alt + o’. I should have mentioned that specifically, my bad.

Glad it worked for you!

]]>