Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does Ace checks metadata values? #202

Closed
laudrain opened this issue Jul 20, 2018 · 2 comments
Closed

Does Ace checks metadata values? #202

laudrain opened this issue Jul 20, 2018 · 2 comments

Comments

@laudrain
Copy link

Please provide the following details if possible or relevant:

[1.0.2] the version of Ace impacted by the issue (as returned by the ace -v command).
[v8.7.0] the version of Node used to run Ace (as returned by the node -v command).
[MacOS 10.3.6] your operating system and version.

  • [] if the issue is a bug when running Ace: the error message as produced in the log file (you can enable debug logging with the --verbose option).
  • [] if the issue is about the HTML report: the browser(s) and version(s) you used.
  • [] if possible, let us know if you can share a sample input file to help us reproduce the issue.

Wrong metadata values aren't reported today by Ace.
For instance:
<meta property="schema:accessibilityFeature">401</meta>
is ok for Ace.

Could it be possible to check the values using WebSchemas/Accessibility?

@laudrain
Copy link
Author

laudrain commented Aug 3, 2018

In this issue, i'd like to add:

alternativeText

This wrong value for accessModeSufficient isn't reported by Ace.

@laudrain
Copy link
Author

This one is also critical.
vNext ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant