search

plone / plone.recipe.codeanalysis

provides static code analysis for Buildout-based Python projects, including flake8, JSHint, CSS Lint, and other code checks
https://pypi.org/project/plone.recipe.codeanalysis/
11 stars 5 forks source link

Accessibility checks #155

Closed gforcada closed 2 years ago

gforcada commented 9 years ago

It would be cool if templates could be checked for potential accessibility errors.

@polyester is there any library for that? If possible without involving a browser?

polyester commented 9 years ago

I'm not aware there's a tool that checks individual templates. There's https://addyosmani.github.io/a11y that checks against URL's, which could possibly be run as part of acceptance/install test, but individual templates would be hard I think.

gforcada commented 9 years ago

Yeah seems like.

I found this http://blog.pivotal.io/labs/labs/accessibility-testing-javascript which lists a few options (I guess not for template-based but URL based):

I also found this, which seems interesting as well: http://pa11y.org/

Noting them here as a later reference whenever I have time to look at it again.

polyester commented 9 years ago

quailjs is great, but is for content. We should really try to bundle that with TinyMCE, but my grunt-fu is limited.

gforcada commented 9 years ago

@polyester as I understood it, if we create enough dummy content and then fire phantomjs we could check the accessibility status of those pages right? and if we run that on CI it would mean we could pin point where accessibility problems where introduced.

gforcada commented 2 years ago

I guess this is no longer the place to add this, a github action, pre-commit hook, or plain integration of tooling is best nowadays 😄