惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

J
Java Code Geeks
量子位
MongoDB | Blog
MongoDB | Blog
N
Netflix TechBlog - Medium
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
B
Blog
A
About on SuperTechFans
腾讯CDC
The GitHub Blog
The GitHub Blog
云风的 BLOG
云风的 BLOG
雷峰网
雷峰网
Last Week in AI
Last Week in AI
H
Help Net Security
WordPress大学
WordPress大学
博客园 - 司徒正美
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
H
Hackread – Cybersecurity News, Data Breaches, AI and More
T
Tailwind CSS Blog
博客园 - 【当耐特】
S
SegmentFault 最新的问题
美团技术团队
M
MIT News - Artificial intelligence
L
LangChain Blog
博客园 - 聂微东

Joe Dolson Web Accessibility

My Calendar 3.8.0 and My Calendar 3.5.0 released - Joe Dolson Web Accessibility Able Player v5.0.0 released! - Joe Dolson Web Accessibility Able Player: 1 year later My Calendar Pro v3.4.0 Released Chat about Able Player at CSUN 2026? Able Player 4.8.0 and Able Player for WordPress 2.3.0 Released My Calendar 3.7.0 & My Calendar Pro 3.3.0 released Judging severity in accessibility issues Is it an evil overlay? How can you tell? My Calendar 3.7.0 Beta Why WordPress Themes Require Underlines on Links “The primary threat for accessibility on the web is neglect.” Able Player 4.7.0 & Able Player for WordPress 2.2.0 Released!
Able Player 4.8 – Release Candidate & Call for Translators
Joe Dolson · 2026-01-12 · via Joe Dolson Web Accessibility

I’m just getting the release candidate for Able Player 4.8 ready. This isn’t as large a release as the last one, but it does include some pretty significant changes!

The most significant changes are in internationalization and in my progress towards removing jQuery and cookies.

The release is currently scheduled for February 2nd, 2026; but could get pushed if there are new bugs in the release candidate that need fixing first.

Internationalization

Until this release, translations have existed as properties on the player object, and were just referenced in the code as keys, e.g. this.tt.mediaType. In the code, this made it difficult to know exactly what the text you were manipulating would be.

I’ve added a translation method accessed as this.translate( 'mediaType', 'Default Text', [ args ] ). This allows me to know what the translatable text is in context, and is helpful for translators to figure out how text is being used.

It also allows me to start removing the concatenated strings in Able Player. Previously, the translations were frequently fragments that were concatenated together as needed. But that’s a problem for many languages – word order and changes due to gendered languages can cause all sorts of headaches if you’re trying to handle translations this way.

As part of this process, I’ve also added a lot more translatable strings to the packages, none of which are currently translated.

To make it a little easier to see things in context, I’ve added a demo page where the player can be viewed in translation, as well.

While Able Player is translated into 20 languages (yay!), most of those language files are significantly incomplete. I could use some help getting them updated!

View the current translations on Github.

Removing the Cookie Dependency

Able Player has used cookies to allow users to set preferences. These are all purely functional cookies, but they add an extra dependency on js-cookie, and many users would prefer to just not use cookies.

In version 4.8, cookies are optional. User preferences are stored in localStorage by default. The main difference between localStorage and cookies is that cookies can be read by the server. If you’re using Able Player in a context where the server may need to store a user’s preferences, add the js-cookie dependency. If not, use localStorage.

Decreasing jQuery Dependencies

My long-term goal is to remove jQuery as a dependency. That’s still a long ways away, but as a step in that direction, I’ve reduced usage so that you can use the “slim” build of jQuery instead of the full build.

The “slim” build excludes the effects, Ajax, and deferral modules. All relevant code has been migrated to native JavaScript.

In case it’s not obvious, you can still use the full build of jQuery – but it’s not necessary.

Changelog

You can read the full changelog on Github. This is a summary of changes, but you can browse the commit history or the milestone to get details about what has changed.