You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 2, 2020. It is now read-only.
In passing, seeing your note for AccessibilityAPI, I’m wondering whether we should just keep ARIA and remove all others, along with AccessibilityControlgiven this issue in epub-revision.
Totally agreed!
I know this sounds like “avoiding misuse by obfuscation” but I’m wondering how many people will check the doc first instead, especially as in most cases, they should be removed as they don’t apply.
Maybe it would be better to keep only the essential and comment all that is optional?
I’d agree keeping only the essential is probably the best option, DX-wise, as authors will have to opt-in i.e. uncomment to add metadata that applies, and not remove the ones that don’t.
JayPanoz
changed the title
Consider removing AccessibilityAPI and AccessibilityControl from Template metadata
Consider removing AccessibilityAPI and AccessibilityControl from Template metadata, and keep only the essential items
Jul 9, 2019
Totally agreed!
Maybe it would be better to keep only the essential and comment all that is optional?
Originally posted by @garconvacher in #31 (comment)
The text was updated successfully, but these errors were encountered: