Skip to content
This repository has been archived by the owner on Jul 2, 2020. It is now read-only.

Consider removing AccessibilityAPI and AccessibilityControl from Template metadata, and keep only the essential items #32

Closed
JayPanoz opened this issue Jul 9, 2019 · 1 comment · Fixed by #34

Comments

@JayPanoz
Copy link
Collaborator

JayPanoz commented Jul 9, 2019

In passing, seeing your note for AccessibilityAPI, I’m wondering whether we should just keep ARIA and remove all others, along with AccessibilityControl given 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?

Originally posted by @garconvacher in #31 (comment)

@JayPanoz
Copy link
Collaborator Author

JayPanoz commented Jul 9, 2019

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 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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant