Summary: | Content block accessibility helpers | ||
---|---|---|---|
Product: | Koha | Reporter: | Martin Renvoize (ashimema) <martin.renvoize> |
Component: | Tools | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | claire.hernandez, dcook, philip.orr |
Version: | Main | Keywords: | Academy |
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | ||
Bug Depends on: | |||
Bug Blocks: | 23003 |
Description
Martin Renvoize (ashimema)
2023-08-16 13:01:32 UTC
TinyMCE actually have an accessability checker tool.. though it looks like a premium plugin to me.. likely licensed? https://www.tiny.cloud/docs/tinymce/6/a11ychecker/ It's an interesting idea. I've been adding element/attribute filtering to the HTML Content blocks, so the UI for this is certainly on my mind these days... Maybe out of scope of this bug, but: If the WYSIWYG editor can cause problems with accessibility especially for HTML customizations for the OPAC, would it be better to be able to choose Texteditor / Codemirror specifically only for HTML customizations and WYSIWYG for "everything else"? The way it is currently, system preference AdditionalContentsEditor sets the default editor for all additional contents, so news, HTML customizations, etc. Maybe it would be better to separate the HTML customizations and pages part into a new system preference? I added a new bug for my previous comment: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38218 as it's probably out of scope here :) |