This repository has been archived by the owner on Aug 10, 2020. It is now read-only.
Code/ proposal: develop accessifyhtml5.js in parallel with a JSON Schema
#17
Comments
nfreear
added a commit
to nfreear/accessifyhtml5.js
that referenced
this issue
Apr 23, 2013
* https://github.com/nfreear/accessify-wiki/blob/master/schema/ * Specifically, new allowed attributes - `ATTR_SECURE` .. * ..Attributes: target, accesskey, longdesc * Ignore `_note` comments * Flag to replace or concatenate fixes
nfreear
added a commit
to nfreear/accessifyhtml5.js
that referenced
this issue
Jul 23, 2013
* Bug yatil#16, Return a hash of success/warning/error messages to aid debugging, * Bug yatil#17, modify accessifyhtml5.js in parallel with JSON Schema - new SECURE_ATTR * http://closure-compiler.appspot.com - SIMPLE_OPTIMIZATIONS
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As part of Accessify-wiki I'm developing a JSON Schema - to allow fix-files authored in YAML format to be validated. Find it here,
I'd like to propose some code edits for
accessifyhtml5.jsbased on the Schema development, specifically:ATTR_SECURE:target- for pop-up windows etc.target=NameNotBlank,accesskey- still in HTML5 in spite of problems,longdesc- http://w3.org/TR/html-longdesc_CONFIG_property within the YAML fixes containing meta-data,_CONFIG_.ignore_defaultspropertyThe text was updated successfully, but these errors were encountered: